Medical Billing Program can't run networked

[vinyltap]

Hi, I have an old DOS medical billing software that runs great on a XP network.  It will run as a stand alone on my Win 7 or 10 computer, but "locks" when I trying to run networked. I've attached 2 screenshots.

It's not too suprising. In XP, I need to add a whole host of commands in the config.nt file like device=systemroot...himem.sys, dos = high,umb, files = 180. Also, it needs the mem /c before running, which apparently helps the program see more memory...?

It's a 3 station license.

Thanks, JW

Attachments:

[Jos]

The settings in config.nt shouldn’t be needed, see www.vdos.info/faqs.html - “Miscellaneous” - “Files = and other directives, once in config.sys”.
Mem /c just lists the memory used by programs, probably once used to look for problems (too little memory).

If the program runs standalone, it should also run networked.

In Windows XP the program needed a drive letter (F: ?) mapped to the network share. Did you also make that drive letter available in vDos by USE F: \\share-name\?
If the program was started by a batch file that set some environment variables, add those also to autoexec.txt.

If it still doesn’t work, change the Target property of the vDos shortcut (“C:\vDos\vDos.exe”?) to “C:\vDos\vDos.exe /log”. Start the program and post the generated vDos.log file. That will probably show what’s wrong.

Jos

[vinyltap]

Hi, one issue might be windows networking? From Win10, I can map the Win7 computer which is the server with my DOS program. But I can't see Win10 from 7, even though I've enabled 40 or 56 bit sharing.

In win10, I think I've succesfully mounted the Win7 drive as G: with the syntax USE: G: \\P8COREPRO\C P8Core Pro (P8COREPRO is the win7 computer)

So in my Win10 autoexec.txt, I change drive letter to G:, then cd\vDos\rpm, and when I try to run the executable M.exe (not trying a batch file anymore), the program opens but still locks out.

My logic is, I'm running vDos from the network computer to access the dos program on the server, would this be correct?

Attachments:

[vinyltap]

this is my autoexec.txt

USE G: \\P8COREPRO\C P8Core Pro
G:
CD\VDOS\RPM
M.EXE

[Jos]

Best to leave the encryption at the default of 128-bit.

Problem will be that your program isn’t started correctly. It needs some switches, another drive letter (N: is mentioned in your screenshot), or some environment variable set.
If RPM.BAT was used before to start the program, you could post that.

And, as mentioned before, change the Target property of the vDos shortcut (“C:\vDos\vDos.exe”?) to “C:\vDos\vDos.exe /log”. Then start vDos by that shortcut, the program and post the vDos.log file in C:\vDos.

Jos

[vinyltap]

Hi, the log is:

vDos 2019.05.01
0.03 C: => (Local) C:\vDos\
0.04 G: => (Remote) \\P8COREPRO\C P8Core Pro\

Execute: M.EXE
1.89 Int 0 => 1aad:010c
Int 23 => 1aad:0113
Int 24 => 1aad:00db
Int 3F => 1aad:0104
Delayed logging, set w/o DOS call:
Int 22 => original
1.96 Int 1B => 19f4:0143
Int 3F => 1a57:02e6
Int 24 => 1ce5:0884
Int 0 => dfd:034c
Int 2F unhandled call 7A00
Int 21 unhandled call E308
2.43 OpenFile failed: VDOS\RPM\DAT\CLINIC.DIA(5) => \\P8COREPRO\C P8Core Pro\VDOS\RPM\DAT\CLINIC.DIA(5)
2.53 OpenFile failed: VDOS\RPM\DAT\CLINIC.DIA(5) => \\P8COREPRO\C P8Core Pro\VDOS\RPM\DAT\CLINIC.DIA(5)
2.64 OpenFile failed: VDOS\RPM\DAT\CLINIC.DIA(5) => \\P8COREPRO\C P8Core Pro\VDOS\RPM\DAT\CLINIC.DIA(5)
2.75 OpenFile failed: VDOS\RPM\DAT\CLINIC.DIA(5) => \\P8COREPRO\C P8Core Pro\VDOS\RPM\DAT\CLINIC.DIA(5)
2.85 OpenFile failed: VDOS\RPM\DAT\CLINIC.DIA(5) => \\P8COREPRO\C P8Core Pro\VDOS\RPM\DAT\CLINIC.DIA(5)
2.96 OpenFile failed: VDOS\RPM\DAT\CLINIC.DIA(5) => \\P8COREPRO\C P8Core Pro\VDOS\RPM\DAT\CLINIC.DIA(5)
3.07 OpenFile failed: VDOS\RPM\DAT\CLINIC.DIA(5) => \\P8COREPRO\C P8Core Pro\VDOS\RPM\DAT\CLINIC.DIA(5)
3.23 OpenFile failed: VDOS\RPM\DAT\CLINIC.DIA(5) => \\P8COREPRO\C P8Core Pro\VDOS\RPM\DAT\CLINIC.DIA(5)
3.34 OpenFile failed: VDOS\RPM\DAT\CLINIC.DIA(5) => \\P8COREPRO\C P8Core Pro\VDOS\RPM\DAT\CLINIC.DIA(5)
3.45 OpenFile failed: VDOS\RPM\DAT\CLINIC.DIA(5) => \\P8COREPRO\C P8Core Pro\VDOS\RPM\DAT\CLINIC.DIA(5)
3.56 OpenFile failed: VDOS\RPM\DAT\CLINIC.DIA(5) => \\P8COREPRO\C P8Core Pro\VDOS\RPM\DAT\CLINIC.DIA(5)
3.68 OpenFile failed: VDOS\RPM\DAT\CLINIC.DIA(5) => \\P8COREPRO\C P8Core Pro\VDOS\RPM\DAT\CLINIC.DIA(5)
3.79 OpenFile failed: VDOS\RPM\DAT\CLINIC.DIA(5) => \\P8COREPRO\C P8Core Pro\VDOS\RPM\DAT\CLINIC.DIA(5)
3.90 OpenFile failed: VDOS\RPM\DAT\CLINIC.DIA(5) => \\P8COREPRO\C P8Core Pro\VDOS\RPM\DAT\CLINIC.DIA(5)
4.01 OpenFile failed: VDOS\RPM\DAT\CLINIC.DIA(5) => \\P8COREPRO\C P8Core Pro\VDOS\RPM\DAT\CLINIC.DIA(5)
4.15 OpenFile failed: VDOS\RPM\DAT\CLINIC.DIA(5) => \\P8COREPRO\C P8Core Pro\VDOS\RPM\DAT\CLINIC.DIA(5)
4.23 OpenFile failed: VDOS\RPM\DAT\CLINIC.DIA(5) => \\P8COREPRO\C P8Core Pro\VDOS\RPM\DAT\CLINIC.DIA(5)
4.34 OpenFile failed: VDOS\RPM\DAT\CLINIC.DIA(5) => \\P8COREPRO\C P8Core Pro\VDOS\RPM\DAT\CLINIC.DIA(5)
4.45 OpenFile failed: VDOS\RPM\DAT\CLINIC.DIA(5) => \\P8COREPRO\C P8Core Pro\VDOS\RPM\DAT\CLINIC.DIA(5)
4.56 OpenFile failed: VDOS\RPM\DAT\CLINIC.DIA(5) => \\P8COREPRO\C P8Core Pro\VDOS\RPM\DAT\CLINIC.DIA(5)
4.67 OpenFile failed: VDOS\RPM\DAT\CLINIC.DIA(5) => \\P8COREPRO\C P8Core Pro\VDOS\RPM\DAT\CLINIC.DIA(5)
4.78 OpenFile failed: VDOS\RPM\DAT\CLINIC.DIA(5) => \\P8COREPRO\C P8Core Pro\VDOS\RPM\DAT\CLINIC.DIA(5)
4.89 OpenFile failed: VDOS\RPM\DAT\CLINIC.DIA(5) => \\P8COREPRO\C P8Core Pro\VDOS\RPM\DAT\CLINIC.DIA(5)
5.00 OpenFile failed: VDOS\RPM\DAT\CLINIC.DIA(5) => \\P8COREPRO\C P8Core Pro\VDOS\RPM\DAT\CLINIC.DIA(5)
5.10 OpenFile failed: VDOS\RPM\DAT\CLINIC.DIA(5) => \\P8COREPRO\C P8Core Pro\VDOS\RPM\DAT\CLINIC.DIA(5)
5.21 OpenFile failed: VDOS\RPM\DAT\CLINIC.DIA(5) => \\P8COREPRO\C P8Core Pro\VDOS\RPM\DAT\CLINIC.DIA(5)
5.32 OpenFile failed: VDOS\RPM\DAT\CLINIC.DIA(5) => \\P8COREPRO\C P8Core Pro\VDOS\RPM\DAT\CLINIC.DIA(5)
5.43 OpenFile failed: VDOS\RPM\DAT\CLINIC.DIA(5) => \\P8COREPRO\C P8Core Pro\VDOS\RPM\DAT\CLINIC.DIA(5)
5.54 OpenFile failed: VDOS\RPM\DAT\CLINIC.DIA(5) => \\P8COREPRO\C P8Core Pro\VDOS\RPM\DAT\CLINIC.DIA(5)
5.65 OpenFile failed: VDOS\RPM\DAT\CLINIC.DIA(5) => \\P8COREPRO\C P8Core Pro\VDOS\RPM\DAT\CLINIC.DIA(5)
6.70 OpenFile failed: VDOS\RPM\LOCK1.LOG(5) => \\P8COREPRO\C P8Core Pro\VDOS\RPM\LOCK1.LOG(5)
CreateFile failed: VDOS\RPM\LOCK1.LOG(5) => \\P8COREPRO\C P8Core Pro\VDOS\RPM\LOCK1.LOG(5)
OpenFile failed: VDOS\RPM\ERROR1.LOG(5) => \\P8COREPRO\C P8Core Pro\VDOS\RPM\ERROR1.LOG(5)
CreateFile failed: VDOS\RPM\ERROR1.LOG(5) => \\P8COREPRO\C P8Core Pro\VDOS\RPM\ERROR1.LOG(5)
Int 24 => 0:0000
Int 0 => original
Int 1B => original
Int 23 => original
Int 24 => original
Int 3F => original
9.45 vDos killed by CLOSE (5)

[Jos]

Your program several times tries to open CLINIC.DIA. So that will be essential for its operation. But there’s no such file at the location VDOS\RPM\DAT\CLINIC.DIA (DOS), so neither \\P8COREPRO\C P8Core Pro\VDOS\RPM\DAT\CLINIC.DIA (Windows).
Find out where CLINIC.DIA is actually located. Perhaps M.EXE relies on relative paths, or the RPM directory has to be in the root of the drive:
USE G: \\P8COREPRO\C P8Core Pro\vDos\
G:
CD RPM
M.EXE

But you can still compare what is different with the old situation?

Jos

[vinyltap]

Hi, thanks for your quick reply. I modified autoexec.bat to your suggestion but unfortunately getting same result

Here's my autoexec.bat

REM USE G: \\P8COREPRO\C P8Core Pro
REM G:
REM CD\VDOS\RPM
REM M.EXE

USE G: \\P8COREPRO\C P8Core Pro\vDos\
G:
CD RPM
M.EXE

I also added a picture showing the clinic.dia in the correct rpm\dat\ path

[vinyltap]

Here is the new log:

vDos 2019.05.01
0.03 C: => (Local) C:\vDos\
G: => (Remote) \\P8COREPRO\C P8Core Pro\vDos\

Execute: M.EXE
1.23 Int 0 => 1aad:010c
Int 23 => 1aad:0113
Int 24 => 1aad:00db
Int 3F => 1aad:0104
Delayed logging, set w/o DOS call:
Int 22 => original
1.37 Int 1B => 19f4:0143
Int 3F => 1a57:02e6
Int 24 => 1ce5:0884
Int 0 => dfd:034c
Int 2F unhandled call 7A00
Int 21 unhandled call E308
2.35 OpenFile failed: RPM\DAT\CLINIC.DIA(5) => \\P8COREPRO\C P8Core Pro\vDos\RPM\DAT\CLINIC.DIA(5)
2.46 OpenFile failed: RPM\DAT\CLINIC.DIA(5) => \\P8COREPRO\C P8Core Pro\vDos\RPM\DAT\CLINIC.DIA(5)
2.57 OpenFile failed: RPM\DAT\CLINIC.DIA(5) => \\P8COREPRO\C P8Core Pro\vDos\RPM\DAT\CLINIC.DIA(5)
2.75 OpenFile failed: RPM\DAT\CLINIC.DIA(5) => \\P8COREPRO\C P8Core Pro\vDos\RPM\DAT\CLINIC.DIA(5)
2.85 OpenFile failed: RPM\DAT\CLINIC.DIA(5) => \\P8COREPRO\C P8Core Pro\vDos\RPM\DAT\CLINIC.DIA(5)
2.96 OpenFile failed: RPM\DAT\CLINIC.DIA(5) => \\P8COREPRO\C P8Core Pro\vDos\RPM\DAT\CLINIC.DIA(5)
3.07 OpenFile failed: RPM\DAT\CLINIC.DIA(5) => \\P8COREPRO\C P8Core Pro\vDos\RPM\DAT\CLINIC.DIA(5)
3.23 OpenFile failed: RPM\DAT\CLINIC.DIA(5) => \\P8COREPRO\C P8Core Pro\vDos\RPM\DAT\CLINIC.DIA(5)
3.34 OpenFile failed: RPM\DAT\CLINIC.DIA(5) => \\P8COREPRO\C P8Core Pro\vDos\RPM\DAT\CLINIC.DIA(5)
3.45 OpenFile failed: RPM\DAT\CLINIC.DIA(5) => \\P8COREPRO\C P8Core Pro\vDos\RPM\DAT\CLINIC.DIA(5)
3.56 OpenFile failed: RPM\DAT\CLINIC.DIA(5) => \\P8COREPRO\C P8Core Pro\vDos\RPM\DAT\CLINIC.DIA(5)
3.68 OpenFile failed: RPM\DAT\CLINIC.DIA(5) => \\P8COREPRO\C P8Core Pro\vDos\RPM\DAT\CLINIC.DIA(5)
3.79 OpenFile failed: RPM\DAT\CLINIC.DIA(5) => \\P8COREPRO\C P8Core Pro\vDos\RPM\DAT\CLINIC.DIA(5)
3.90 OpenFile failed: RPM\DAT\CLINIC.DIA(5) => \\P8COREPRO\C P8Core Pro\vDos\RPM\DAT\CLINIC.DIA(5)
4.01 OpenFile failed: RPM\DAT\CLINIC.DIA(5) => \\P8COREPRO\C P8Core Pro\vDos\RPM\DAT\CLINIC.DIA(5)
4.12 OpenFile failed: RPM\DAT\CLINIC.DIA(5) => \\P8COREPRO\C P8Core Pro\vDos\RPM\DAT\CLINIC.DIA(5)
4.23 OpenFile failed: RPM\DAT\CLINIC.DIA(5) => \\P8COREPRO\C P8Core Pro\vDos\RPM\DAT\CLINIC.DIA(5)
4.34 OpenFile failed: RPM\DAT\CLINIC.DIA(5) => \\P8COREPRO\C P8Core Pro\vDos\RPM\DAT\CLINIC.DIA(5)
4.45 OpenFile failed: RPM\DAT\CLINIC.DIA(5) => \\P8COREPRO\C P8Core Pro\vDos\RPM\DAT\CLINIC.DIA(5)
4.56 OpenFile failed: RPM\DAT\CLINIC.DIA(5) => \\P8COREPRO\C P8Core Pro\vDos\RPM\DAT\CLINIC.DIA(5)
4.67 OpenFile failed: RPM\DAT\CLINIC.DIA(5) => \\P8COREPRO\C P8Core Pro\vDos\RPM\DAT\CLINIC.DIA(5)
4.78 OpenFile failed: RPM\DAT\CLINIC.DIA(5) => \\P8COREPRO\C P8Core Pro\vDos\RPM\DAT\CLINIC.DIA(5)
4.89 OpenFile failed: RPM\DAT\CLINIC.DIA(5) => \\P8COREPRO\C P8Core Pro\vDos\RPM\DAT\CLINIC.DIA(5)
5.00 OpenFile failed: RPM\DAT\CLINIC.DIA(5) => \\P8COREPRO\C P8Core Pro\vDos\RPM\DAT\CLINIC.DIA(5)
5.10 OpenFile failed: RPM\DAT\CLINIC.DIA(5) => \\P8COREPRO\C P8Core Pro\vDos\RPM\DAT\CLINIC.DIA(5)
5.21 OpenFile failed: RPM\DAT\CLINIC.DIA(5) => \\P8COREPRO\C P8Core Pro\vDos\RPM\DAT\CLINIC.DIA(5)
5.39 OpenFile failed: RPM\DAT\CLINIC.DIA(5) => \\P8COREPRO\C P8Core Pro\vDos\RPM\DAT\CLINIC.DIA(5)
5.50 OpenFile failed: RPM\DAT\CLINIC.DIA(5) => \\P8COREPRO\C P8Core Pro\vDos\RPM\DAT\CLINIC.DIA(5)
5.60 OpenFile failed: RPM\DAT\CLINIC.DIA(5) => \\P8COREPRO\C P8Core Pro\vDos\RPM\DAT\CLINIC.DIA(5)
5.71 OpenFile failed: RPM\DAT\CLINIC.DIA(5) => \\P8COREPRO\C P8Core Pro\vDos\RPM\DAT\CLINIC.DIA(5)
OpenFile failed: RPM\LOCK1.LOG(5) => \\P8COREPRO\C P8Core Pro\vDos\RPM\LOCK1.LOG(5)
CreateFile failed: RPM\LOCK1.LOG(5) => \\P8COREPRO\C P8Core Pro\vDos\RPM\LOCK1.LOG(5)
OpenFile failed: RPM\ERROR1.LOG(5) => \\P8COREPRO\C P8Core Pro\vDos\RPM\ERROR1.LOG(5)
CreateFile failed: RPM\ERROR1.LOG(5) => \\P8COREPRO\C P8Core Pro\vDos\RPM\ERROR1.LOG(5)
Int 24 => 0:0000
Int 0 => original
Int 1B => original
Int 23 => original
Int 24 => original
Int 3F => original
6.73 vDos killed by CLOSE (5)

[Jos]

The paths seem to be correct/match. Windows CreateFile() API function however returns error 5, file not found.
The only thing that stands out are the spaces in “C P8Core Pro”.
Spaces normally can’t be used in paths w/o surrounding the path in quotes. Though that mostly concerns the Windows command line processor (a space indicating the end of a parameter).
The CreateFile() documentation doesn’t mention spaces needing extra consideration. Shouldn’t be needed since the FileName parameter has a binary zero indicating its end.

Change the share name “C P8Core Pro” of P8COREPRO’s C drive to “C”, or for instance “C_Drive”, at least w/o spaces.
So it would also become USE G: \\P8COREPRO\C\vDos\ or USE G: \\P8COREPRO\C_Drive\vDos\in autoexec.txt.

If that doesn’t fix the problem, send me the RPM directory. Probably only CLINIC.DIA will be needed in RPM\DAT.

Jos

[vinyltap]

Hi, I dont want to keep you up too late if you're in the Netherlands. this will be my last post til AM your time tomorrow.

Unfortunately I tried both & they didn't work. They mounting syntax seems more complicated than in XP. Do you think it might work if both are Win 7 Computers? I prefer not to give out my DOS software for now, even tho I know it's virtually worthless to other people. Thanks.

[Jos]

Can you post the new vDos.log file.

To your reservation: Eventually experiment what can be left out, while the program should still more or less run. Surely don’t post it on this forum, but then send it to me directly, for instance by wetransfer.com.

Jos

[vinyltap]

vDos 1 G P8COREPRO C vDos.log (96 B)vDos 2 G P8COREPRO C_Drive vDos.log (96 B)vDos 3 rpm set as root directory.log (3.85 KB)Hi Jos,

Attached are 3 logs, 1 is USE G: \\P8COREPRO\C\vDos\ and 2 USE G: \\P8COREPRO\C_Drive\vDos\. These did not connect. For the 3rd try & log, I put vDos in the billing program directory in case it prefers to run out of C:\RPM or G:\RPM

this is how my autoexec.txt looks

REM 1)
REM USE G: \\P8COREPRO\C\vDos\

REM 2)
REM USE G: \\P8COREPRO\C_Drive\vDos\

REM 3) vDos is in RPM (dos billing software) root directory
USE G: \\P8COREPRO\C P8Core Pro\rpm

Thanks, James

[Jos]

For USE G: \\P8COREPRO\C\vDos\ to work, the share name at the server PC has to be set to “C”.

Go to the Windows Explorer, right click the C drive, Share with, Advanced sharing…, Advanced Sharing, change the name.
Restart both PC’s, so Windows caching won’t interfere. Open \\P8COREPRO\C on the client PC in Windows Explorer, go to the vDos directory and double click vDos.exe.
Since that works locally on the server PC, it should also on the client PC.

If it indeed works, eventually right click the same vDos.exe, Send to, Desktop (create shortcut).

Jos

[vinyltap]

Hi Jos,

Thanks for all your help so far, I changed server share name to just "C". Unfortunately didnt help. Before I go any further think it's prudent to try Win 7 to Win 7 server & client. This Win10 computer I just got, heard the networking could be tricky. Will get back to ya.

BR, James