vDOS can not start a program on my desktop

[jiger]

I installed vDOS on my Windows 10 laptop, 64 bit, and it works perfectly. When I installed vDOS on my Windows 10 desktop, 64 bit, there is a program that can´t be run, although it works perfectly on the laptop.

I am using C:\vDos\Astro\pca.bat on both machines. PCA reads the following:

ECHO OFF
PCAWEL
PCAMAIN
IF exist history.tmp del history.tmp

When trying to run PCA on the desktop, I get the an error message saying that PCAWEL and PCAMAIN can not be run in a 64 bit system. I then go to compatibility settings and set these files to be run under a Windows 95 state.

My autoexec.txt file is:

cd astro
c:\astro\pca
exit

When starting vDOS, I just get c:\> on the screen.

My laptop has no problem to run this program without any compatibility settings. Both machines have the latest updates from Microsoft.

What is the problem with the desktop?

[Jos]

The error message indicates vDos passes PCAWEL and PCAMAIN on to Windows to be executed. That off course won’t work, no matter what compatibility setting.

I suggest you copy the c:\vDos directory of your laptop to an USB stick/drive, then start vDos on both machines from there. So eliminating any possible differences like for instance the vDos version.

Jos

[jiger]

I have copied the functioning directory from my laptop to my desktop and the vDos version is the latest. The essential question is: why does the desktop pass PCAWEL and PCAMAIN to Windows for execution when the laptop doesn´t??

Can that be fixed in any way?

Could I have the functioning vDos directory on my c:\Dropbox (which both machines can access)? If so, exactly how should this be "spelled" or how would it affect the autoexec file?

Jiger

[jiger]

Dropbox works in the laptop but not in the desktop - same error.

Jiger

[Jos]

vDos calls the Windows GetBinaryType() API function to determine if PCAWEL/PCAMAIN is a DOS or Windows program (or even something else).
No problems so far with this function, except when the DOS program is hosted on a Linux server.

Windows on the desktop returns PCAWEL/PCAMAIN isn’t a DOS program, or doesn’t know what it is.
First try what temporary disabling your anti-virus program will bring. You didn’t mention the extensions, if they are .exe, change them to .com. Lastly submit one of the programs, but I’m afraid that testing it at my side won’t bring much (recognized as DOS programs).

Jos

[jiger]

Inactivating the antivirusprogram didn´t help. The programs in question are .exe (from 1996) How do I change them to .com? B t w, I do have another Dos program with .exe-file (from 1992) that works well also in the desktop.

I attach the files here.

Jiger

[emendelson]

Simply rename the programs from WHATEVER.EXE to WHATEVER.COM, I think. (Make sure that they don't get renamed WHATEVER.EXE.COM, but only WHATEVER.COM.) But Jos will explain if something more is needed.

[Jos]

Didn’t find anything off with the two files, so it has to be the desktop Windows (in combination with?).

If renaming to .com didn’t work (the files just remain executables with relocation information), try these two files. Packed versions of the originals, so they’ll have complete different header information etc.

Jos

[jiger]

To my great astonishment and gratitude, the compact files do work!!
Do you have any idea about this difference between the laptop and the desktop?

Anyway, THANK YOU!

Jiger

[Jos]

My only guess was that you had already set compatibility mode for PCAWEL/PCAMAIN before running them in vDos. So GetBinaryType() would return an incorrect executable type. But I checked, and this doesn’t seem to influence GetBinaryType(), while Windows also stores the compatibility mode setting inclusive the file path.
So no idea what's off with your desktop, though not worth further investigation since it seems an unique situation.

Jos