DexImport problems

[Guest]

Hello all:Since downloading Vol!Edit, (last week), I have lost the use of "DexImport". (When I downloaded DexImport orginaly, I inserted it into the tool subfolder for Fly!II). Now, every time I try to import a *.dex file using DexImport, I get the following error message; "Can't open D:sytemsAirport.POD, error code 0x3 in: D;projectfly2PodLibmapped file.cpp, line 69"! At the time I was attempting to import the Airport.dex file found in the root Fly!II folder. I don't understand! I have a "D" drive but it's clean, (nothing is on the drive).I went into the Register, did a seach for the above paths and found nothing. As i stated before, my "D" drive is clean. I attempted to import Airport.dex file with Vol!Edit and was told that DexImport could not be found. Same thing happens when I try to import the Comm.dex and Taxiway.dex files. I removed DexImport from my unit, and reinstalled DexImport to another folder without any luck. now, everytime I attempt to use DexImport, I get the same error message. Has anyone out there had the same or simular problem?????? If so, how did you solve the problem. I didn't try this yet but maybe what I should do is uninatall Vol!Edit, and then try to use Deximport. Sure would be nice if I could use both. If deximport within Vol!Edit would work, that would be all I probably would need. What do you think??? I am lost without the use of DexImport!!Any help, work-a-rounds or ideas would be greatly apprieciated!!!!!! Sometimes, I just don't understand how I get myself in such a mess!Thank you in advance.Curtis

[Guest]

Hello CurtisYou wrote :I removed DexImport from my unit, and reinstalled DexImport to another folder without any luck. You must place Deximport in Fly directory so Deximport will be happy.For VolEdit did you open OptionsDirectory init ?Didier

[Leen3131cs 107]

Hallo Curtis and Didier,Quote from DexImport instructions html:Installation:Unzip the files to the directory of your choice. This no longer needs to be your Fly2 directory. Regards

[Guest]

The path to Fly in the registry is incorrect.DexImport gets the location of Fly II from the key:HKEY_LOCAL_MACHINESOFTWARETerminal RealityFly! IIPATHYou need to either fix this value to point to your Fly2 directory, or delete the key, in which case DexImport will let you browse to find it when it starts up next time.-Frank

[Guest]

Thank you Frank:Going to the Registry and editing HKEY_LOCAL_MACHINESOFTWARETerminal RealityFly!IIpath worked!!!!!!Thanks again.Curtis