Why would you care about the drive letter?
I have kix-based software that performs many different software product installs, and it can run from CD/DVD, network share, flash, even floppy if you can find one without knowing the drive letter it was launched from. ALL of the scripts are written to avoid any disk reference - it all runs from the root of the "current" drive where the script was launched from. Any batch files are written to run from the folder they were called from or lower - never a higher reference.
The exception to this is /BIN, a folder where the Kix32.exe and any other external commands are kept. These are references as "/bin/prog.exe" when they are needed.
After 10 years of using this internally and at several clients, we'd never needed to know the drive letter where the script ran from. The point is - using drive letters will complicate the process. Think about "/" and not "F:/" and you'll be better off.
If Kix32 and the .KIX file are on the flash, the @CURRDIR and @SCRIPTDIR macros will provide the path where the script was started and is currently executing from. They both begin with the drive letter.
Glenn
_________________________
Actually I
am a Rocket Scientist!
