|
|
Post by karpensteel on Oct 28, 2022 17:56:37 GMT 1
Our current situation is as follows
app.exe is stored on a shared network drive W:\app\app.exe
We have XP machines on the network with shortcuts to a .bat file stored on a separate shared drive X:\app\app72.bat
app72.bat points back to W:\app\app.exe
I'm wondering if and how it's possible to use vDos on a Windows 10 machine to connect to these same paths so I don't have rework and move any locations.
I assume I would need to define these paths within the autoexec.txt, but I'm not sure exactly how to do it.
The vDos installs can remain local to the Windows 10 machines, they just need to be able to access the shared DOS program and its associated database.
All the original infrastructure was put in 15+ years ago by people no longer at the company for this custom DOS application so I'm hesitant to move any files or change folder/drive locations etc.
Thank you for any help.
|
|
|
|
Post by Jos on Oct 28, 2022 18:34:02 GMT 1
Since your app is initiated from X:\app, I suggest you install/copy vDos.exe, config.txt and autoexec.txt to there.
So those files reside alongside app72.bat (and don't have local duplicates around the network).
Create shortcuts to the vDos.exe in X:\app. Clear autoexec.txt and add these lines:
REM At vDos startup X:\app will be the Windows Current Work Directory. To get a corresponding DOS/vDos X:
USE X: ..\
REM The W: drive letter is also required, we could do this by:
REM USE W: W:\
REM Better to not rely on Windows redirected drive letters. So instead (\\server\share corresponds to Windows W:):
USE W: \\server\share
REM Start the application:
CALL app72.bat
REM Exit vDos:
EXIT
If all runs correctly, it would of course be a big benefit for simplicity and future understanding to move app72.bat to autoxec.txt. And move X:\app to W:.
Jos
|
|
|
|
Post by karpensteel on Oct 31, 2022 16:42:25 GMT 1
Jos,
Thank you so much for the concise instruction. I have gotten the program working from the network location with a shortcut to the shared vDos.exe file.
The only issue I'm running into now is with Printing. In it current state our DOS program is printing directly to a network printer which is recognizes. This printer has changed over the years, but its IP address on the network has remained the same. My guess is that somewhere in the DOS application its pointing a LPT to an IP? I have reviewed the Printing PDF included in the install folder as instructed in the FAQ area. Based on what I read, I expected printing to continue without need for adjustment since everything related to that should be coming from DOS application itself rather than vDos. However, I've had no success printing so I'm wondering if I need to change something in the config.txt. That said, non of the references there seemed to relate to printing to the IP of a network printer.
|
|
|
|
Post by Jos on Oct 31, 2022 17:10:11 GMT 1
DOS programs generally only print to LPT or COM ports.
So my guess is some NET USE LPT1: …. is active at the XP machines.
Issue NET USE at the command line to verify that.
If so, add a Text Only printer connected to that IP address (or published network name).
Or use the printer if already installed in LPT1=SEL: "Printer_name".
Jos
|
|
