My program doesn't run

[rubberfish]

After reading your printing.pdf for the current version of vDos I thought I would run my program in the current version of vDos to see if the printing result is any different/better than under vDosPlus 2015.11.01.

I downloaded vDos from the download link www.vdos.info/download.html and ran vDosSetup. I allowed the default to update to the latest version and create the shortcut. Your included demo program runs fine. My program doesn't run at all and there isn't any error message. I didn't find an uninstall option. I deleted the folder and ran the installer again this time unchecking the option to upgrade to the latest version. Again the demo runs but my program doesn't.

My setup:

Following your FAQ I copied my program folder into the vDos folder. Result vDos\Finance

After launching vDos, exiting the demo program and typing dir I see the Finance folder listed.

Cd Finance and I'm in the folder.

Yes after entering the dos command dir I see the programs executable file pcact.exe.

After typing PCACT.EXE I'm immediately returned to the command prompt without an error message.

Yes
I also tried running the batch file that is traditionally used to start
the program after modifying the paths to reflect the programs new
location in C:\vDos\Finance but the result was the same.

Under vDosPlus 2015.11.01 this is all that I needed to do to run it.

Change to the programs directory: CD FINANCE

Run the program: PCACT.EXE

Any suggestions to make my program run in the current versions of vDos?

[Jos]

No idea why your program would quit w/o an error message.
Start vDos with the log option (“…vDos.exe”/log), perhaps the generated log file will show what’s going wrong. Else you could post your program to check.

Jos

[rubberfish]

Thank you. Here is the log:

vDos-Base
=========
C: => (Local) C:\vDos\

Execute: DP26YI.EXE - /s
Int 1B => 2a0d:0004 (Delayed logging w/o DOS call)
Int 22 => f000:0003 (Delayed logging w/o DOS call)
Open failed: DPTEST\DP{S0001.TMP(2) => C:\vDos\DPTEST\DP{S0001.TMP(2)
Open failed: DPTEST\DP{T0001.TMP(2) => C:\vDos\DPTEST\DP{T0001.TMP(2)
Open failed: DPTEST\DP{I0001.TMP(2) => C:\vDos\DPTEST\DP{I0001.TMP(2)
Int 1B => f000:0000 (Delayed logging w/o DOS call)

Execute: pcact.exe
Program not executed/loaded (5): pcact.exe
==================
vDos ended by EXIT (0)

[Jos]

The reported DOS error code is 5: Access denied.

That is mostly generated by vDos (not Windows). Somewhat misleading since it can indicate several errors while attempting to load or start a program, like an invalid file header, relocation table.

With PCACT.EXE it is an invalid header: The image size is defined as 162 pages of 512 bytes, with the last page containing 480 bytes, so totaling 82,912 bytes. The file size however is 82.672 bytes. Don’t think those 240 bytes ever existed, and were somehow lost in the past by copying the program from one system to another. Probably the linker used to build the program in the very past mixed up bytes with words.

Still, the header is incorrect, since the relocation data table size would have a negative value. This obviously is missed by with NTVDM and earlier vDos versions. I corrected the file header so the last page is correctly defined to contain 240 bytes instead.

[rubberfish]

Wow! I can't thank you enough for fixing the file so it runs now in vDos.

vDos prints absolutely perfectly to my Daisy Wheel printer with these settings:
In the Silver Reed EXP 400 (Generic text only printer driver) I set the port to Standard TCP port using the static IP address of the print server the printer is connected to.
I added this command to config.txt: LPT1 = SEL: "Silver Reed EXP 400" RAW

Thanks for going the extra mile and fixing my file. Donation sent.

[Jos]

Thanks for your donation. Though isn’t it time to replace that noisy and slow Daisy Wheel by a modern inkjet or laser printer?

Jos

[rubberfish]

It is only used to print an occasional check. An increasingly rare need. The ability to adapt it to any check layout is the programs value. No special check forms to purchase at high cost and quantity. Will even print on a personal check once set up for it. I just discovered that the programs used to make those adjustments don't run under vDos though. I suppose they have the same problem with the the file header.

[Jos]

I suppose the Daisy Wheel printer supports Epson codes. So any printer would do.
Then again, no checks in the Netherlands for some 30 years. You could need a carbon copy, whatever.

The supporting programs will probably suffer the same linker mishap.
Attached DOS program UNP.EXE will at least show what’s wrong with the EXE header, UNP I PCACT.EXE:

Your original PCACT.EXE:
processing file : PCACT.EXE
DOS file size   : 82672
file-structure  : executable (EXE)
EXE part sizes  : header 512 bytes, image 82400 bytes, overlay -240 bytes

Modified:
processing file : PCACT.EXE
DOS file size   : 82672
file-structure  : executable (EXE)
EXE part sizes  : header 512 bytes, image 82160 bytes, overlay 0 bytes

Jos

Attachments:

unp.exe (20.34 KB)

[rubberfish]

I tested all of the exe files in the folder and this is the only one not working. According to unp.exe it appears to have the same -240 bytes problem as PCACT.EXE had. Can I fix that with unp.exe?

processing file : ACT-EDIT.EXE
DOS file size : 42000
file-structure : executable (EXE)
EXE part sizes : header 512 bytes, image 41728 bytes, overlay -240 bytes

[Jos]

UNP.EXE can’t fix the header, I only used it to show what’s wrong.
You need a hex editor to change the third and fourth byte (0xE0 and 0x01) of the file to 0xF0 and 0x00.
Or post the file, I’ll change them for you.

Jos

[rubberfish]

I'll post the file.

[Jos]

Good you did, the third and fourth bytes were different with this file.

Jos

[rubberfish]

Works. Thank you!

Have a good day.