PMC Tactical forums

I've got an error with the installer of SRTM Israeli Theater.

There is a step where it is executing something like
But my falcon install is in i:\Falcon4. So I got the error message :

Invalid Falcon dir! c:\MicroProse\Falcon4

I had the same problem. My installation of Falcon this in the E:

Hum - - do you have a way to move or trick the installer that Blueprint made into thinking that it is using C:\MicroProse\Falcon4 ?

If you have a C: drive on on your computer can you move a dummy falcon install there and possibly adjust your registry with an entry to make it think it has falcon installed there?

The installer I built is a basic NSIS that executes Blueprints installer - - all I did was package it to make it easier to use. But, it only works for the standard C:\MicroProse\Falcon4 directory - - - I guess I didn't take into account folks with alternative installs. Sorry about that.

It might be possible to rework the installer for other directories. I look at that. Right now I am really busy with the ITO2 conversion to RV format so I am going to be on that task for a little while. Be patient and let me see what I can come up with.

I moved it to c:\microprose in order to get the SRTM terrain, and then back to where it was. With registry keys update of course...

It worked.

I just mentioned it for futur update/fix .

Couby i don't think you need any registry keys... just the folder

C:\...terrdata\Israeli\terrain

And it should work...

I see what you mean I_Hawk . Anyway that's already done and it worked .

This is not my util or so, but its exactly the same situation as with SPTinstall which requires the original Falcon 4 registry entries. This kind of utils need to be fixed.

In this case - Blueprints SRTM installer works just fine - but isn't a one-click. It requires rather lengthy input to the exe command line in order for it to work.

I elected to write a script in NSIS that fills in the exe command line in so it would be one-click. The alternative is to issue out Blueprints SRTM installer and let the user figure out how to make it work. That might be easier. The vast majority of folks will probably use the standard C:\MicroProse\Falcon4 directory and that was the target audience for the SRTM installer in NSIS.

Ranger -

I can help make a script that gets the registry value of the current F4 directory and use that in the command line, if you want.

Check out the first post in the Installers thread and I can show you the parts of the script that do it.

:thumbs:

Tom - sounds great - - I am focused on this DB thingy. I will get to it but it will be a little while . . .