| View previous topic :: View next topic |
| Author |
Message |
noveltech Contributor

Joined: 16 Sep 2002 Posts: 105
|
Posted: Tue Sep 17, 2002 2:14 am Post subject: set path or temp path within the vds script |
|
|
Is it possible to set path or temp path within the vds script.
Example: To run various exe's in various locations.
temp path = c:\windows;c:\windows\system;c:\anywhere;c:\anywhere\anywhere
after vds script exits...above temp path terminates.
regards, mike with noveltech. |
|
| Back to top |
|
 |
Mac Professional Member

Joined: 08 Jul 2000 Posts: 1585 Location: Oklahoma USA
|
Posted: Tue Sep 17, 2002 9:03 am Post subject: |
|
|
Not sure about anything past Windows 9x...
If this is a DOS program (which would run under a
new instance of command.com) you can use a batch
file to set the path AND run the program, such as this
(%path% contains the current path):
| Code: |
set path=%path%;c:\anywhere;c:\anywhere\anywhere
yourprog.exe
|
You could then run the batch file from VDS.
When a new instance of COMMAND.COM starts, it inherits
the env vars from the original one (which is set before
Windows starts). Any changes made are ONLY to the
current instance of COMMAND.COM, and are lost when it
closes. Calls from VDS such as:
RUN command /c set path=whatever
would be lost before the next VDS line could be executed.
If this is a Windows program, I don't think you're going
to affect the path once Windows has started, because
you don't have access to the original command.com, and
I don't think there's any reference to the current path in
the registry or elsewhere (not sure about this though).
Anybody else have any ideas?
Cheers, Mac  _________________ VDSug.dll does file IO, check/disable menu items,
non-VDS dlls, draw functions and more...
Free download (30k dll size) at:
http://www.vdsworld.com/download.php?id=361
 |
|
| Back to top |
|
 |
Garrett Moderator Team
Joined: 04 Oct 2001 Posts: 2149 Location: A House
|
Posted: Tue Sep 17, 2002 5:31 pm Post subject: |
|
|
Windows ME does not use the autoexec.bat file nor the config.sys file. It
places any info that was in these two files into it's registry. And it's not
100% effective at always grabbing new entries into these two files and
adding them to the registry.
I'm pretty sure that NT4 and Win2k still use the two files, but I can't say
about WinXP.
You may have to take note of Window's versions and then either use the
autoexec.bat file, or place the proper reg entries.
-Garrett |
|
| Back to top |
|
 |
Garrett Moderator Team
Joined: 04 Oct 2001 Posts: 2149 Location: A House
|
Posted: Tue Sep 17, 2002 5:35 pm Post subject: |
|
|
Just as a note, be sure not to use "Set Temp Path" as that will tell
windows to use whatever path you put into that as a temp folder.....
Meaning, when programs need to unpack like install files and such, it will
unpack them to whatever directory you made the temp folder.
-Garrett |
|
| Back to top |
|
 |
|