On that topic soda... think back if you will about our disscussion about the install files I made.
Is this the registry entry you where talking about. "HKEY_CURRENT_USER\Software\HiTech Creations\Aces High II"
If so then that's what I can add to the install files that will already know where to put things.
Will probably need another guinie pig.
midi
Looks like that's the one, it has both the version and path listed. Knowing the path would allow the install program to place the files in the right spot assuming HTC doesn't change the subdirectory where they are stored later down the road.
However there is still one little obstacle to overcome, if people setup .wav files for the mission. The .mis file would still refer to the wrong path even though the install program puts them in the right place using the registry. The only way around this would be for the install program to edit the mission file(.mis) to put in the right path, which would be kind of akward for an install program needing to do.
The mission editor does allow you to build the .mis into a .res file. I think when it's built into a .res file it uses a relative path to find the .wav files, so you do not need to edit anything. If that is the case the install program would work as long as people deployed their mission's using the .res file instead of the source file (.mis). The install program would not have to modify anything and only would need to worry about putting the files in the right place using the registry entry.
anyways just a thought...