External RUN command not working on Newest Version

[advlaser]

After installing the newest version of VDOS (2022.05.1), I found the FoxPro external RUN command isn't working. 
This is easily tested from the command prompt.
    RUN f:\arprogs\itemhist.exe  
(Drive F is mapped in the autoexec.txt)

This command runs fine in 2021.05.01. Any ideas on this? Thanks!

PS - the faster Paste from the clipboard of 2022.05.01 is a nice improvement.

[Jos]

Testing at the FoxPro command prompt doesn’t show "Bad command or file name"?

What if you do "DIR f:\arprogs\itemhist.exe"?

Eventually do "RUN use" to verify the DOS F: assignment.

Jos

[advlaser]

DIR shows ITEMHIST.EXE
RUN USE shows my mappings

[Jos]

That’s unexpected. What if you start vDos with the log option (….\vDos.exe /log). And have a look at the generated vDos.log file for “itemhist.exe”.

I suppose itemhist.exe is a DOS program. What did it do before?

Jos

[advlaser]

Actually the program I called is a windows app (VFP 9). In my previous example I had simplified the directory structure. These are the actual files and directories.

This is interesting, notice how the executable file name is ITEMHI on the load exec line and ITEMHI(5) on the fail line...

LOADEXEC: C:\COMMAND.COM /C F:\DOSAPPS\ARWIN\ITEMHIST\ITEMHIST.EXE
LOADEXEC: F:\DOSAPPS\ARWIN\ITEMHIST\ITEMHI
EXEC failed: F:\DOSAPPS\ARWIN\ITEMHIST\ITEMHI(5)
TLB table reset due to PSP switch (9e5d-b4)
TLB table reset due to PSP switch (b4-9e5d)

Here is the actual run command I used: RUN F:\DOSAPPS\ARWIN\ITEMHIST\ITEMHIST.EXE
I think everything after 36 characters is getting truncated. If I run an EXE with a shorter path it works.

For instance this command works fine.
RUN ..\arwin\itemhist\itemhist.exe

[Jos]

The (final) command line is indeed limited to 31 characters.

You can download this vDos copy that also raises the environment size to 1KB:
www.vdos.info/files/20220301/vDos.exe

Jos