At 9:02 PM +0100 23/8/1999, Kevin Miller wrote:
>On Monday, Aug 23 1999, Dave Cragg wrote:
>> The docs say the dll must be on the $PATH environmental variable.
>> However, the $PATH variable doesn't inlude the path to the standalone
>> exe file. I just added the "directory" to $PATH on startup, something
>> like this:
>>
>> get the directory
>> replace "/" with "\" in it -- for Windows
>> put it & ";" before $PATH
>>
>> This works, but not having a complete grasp of the environment
>> variable concept, I'm not sure if this is the best way to do this, or
>> if there might be any unwanted consequences.
>>
>> Any confirmations, warnings, or otherwise appreciated.
>
>The way I always do it is to put the external in the same directory as the
>executable. When in non-standalone mode, thats the MetaCard program folder,
>when a standalone, the same directory as the app itself. Then add it to the
>Externals property.
>
That's what I thought, but when I tried it, the external commands
weren't recognized in the standalone. (This is with Win NT 4.0 and MC
2.2.4) That's what prompted me to look at the $PATH variable. In the
standalone, it didn't include the path to the executable, only the
paths to the WinNT folder and the System32 folder. (Is this how it
should be?) When I added the above script in the startUp handler, it
worked fine.
Perhaps I ought to take a look at it again.
Cheers
Dave Cragg
_____________________________________________
The LACS Centre (Business English Training Resources)
mailto:[EMAIL PROTECTED]
http://www.lacscentre.co.uk
_____________________________________________
