3 replies to this topic

[DesertJerry]

After AutoPatcher was installed I noticed that in many folders there were .APM files; identified in Explorer as APM files.

Figuring this really didn't identify things I went to Folder Options > File Types and created a new registerd file type: .APM and identified it as AutoPatcher Module.

Since many, if not all, programs that have their own file extensions usually go through a similar process to identify their peculiar file extensions and have that information written directly into wherever it is File Types are stored I was wondereing why AutoPatcher does not do the same.

In the translations folder: what are .APL, APT, amd .MSL files?

The same could be said for APUP after it is used to update things; why are .RTI and .VER not identified?

[M2Ys4U]

I think there are a couple of reasons why they're not identified. 1) The end user shouldn't really ever have to see them, for the most part; and 2) other programs may wish to use the same extension for something completely different - I know Photoshop uses .apm files for something.

You can identify and associate .apm using the Module Editor if you wish.

.apt are used for translations, .rti for cryptographically checking that the modules are valid, and .ver for version information IIRC

.apl and .msl I don't know about

Edited by M2Ys4U, 08 December 2007 - 03:02 PM.

[DesertJerry]

M2Ys4U, on Dec 8 2007, 03:02 PM, said:

You can identify and associate .apm using the Module Editor if you wish.

When I open Module Editor and select File > Open the files being looked for are .AMC - not .APM - so what good is this?

I have editor.exe version 2.0.0.9 so I'm assuming this is the latest.

[M2Ys4U]

errm. Been a while since I fiddled with the module editor. I forget what the difference between .amp and .amc is, sorry.