|
Post by roblwhitney on Jun 11, 2021 19:14:53 GMT 1
Trying to bring a 1970's DOS app into the Window 10 world using vbScrinting. Setup a VM, install vDos. The demo ran successfully. I created a script with this code:
Set WshShell = WScript.CreateObject("WScript.Shell")
WshShell.Run ("C:\vDos\vDos.exe")
The autoexec.txt file reads:
USE W: C:\OLDSTUFF
@echo OFF
CLS
rem This is the end of AUTOEXEC_BARE.TXT. Batch lines are added after this.
echo 'Made it to here'
PAUSE
When I invoke vDOS from Windows, the batch file executes.
But when I run the vbScript above, vDOS opens to a C:\ prompt, but the autoexec.txt doesn't execute.
Any thoughts?
Thanks!
|
|
|
Post by Jos on Jun 11, 2021 19:42:06 GMT 1
You confused me with “Setup a VM, install vDos”. I hope you didn’t setup a VM for vDos in Windows 10, but in MacOS or something.
As vDos.exe is started, the Windows current directory is normally first set to that vDos.exe is located in. Or eventually at least to where autoexec.txt is located.
I suspect your script doesn’t do that. So vDos.exe ends up in some directory, not C:\vDos, and can’t find its autoexec.txt. To verify you could do the USE command at the vDos command prompt.
Jos
|
|
|
Post by roblwhitney on Jun 14, 2021 15:24:06 GMT 1
I created a Windows 10 VM using VMware ESXi 7.0. Once I had the VM created, I install vDos. It ran the demo correctly. I have moved the vscript into the vDos directory, and it seems to be working now. Thanks!
|
|