Msg: Re: vDos-lfn instead of vDosXy

Well, thanks guy, that path instruction does correct the problem. After the release of the vdos version on which vdos-lfn is based, both vdos and wordpad would load from autoexec.txt, but once you switched from wordpad to vdos (alt+tab), wordpad would be inaccessible until ending the vdos session -- alt+tab would toggle between the desktop and the vdos window. To get wordpad back, vdos had to be ended.

In any case, using the line Carl proposed allows both windows to co-exist again, though at this point I'm not sure why the earlier load command didn't work.

From: Carl Distefano
To: xywrite@xxxxxxxx
Sent: Saturday, April 30, 2016 11:48 PM
Subject: Re: vDos-lfn instead of vDosXy

Reply to note from Edward Mendelson mailto:em36@xxxxxxxx Sat, 30 Apr
2016 20:51:35 -0400

> ... you can start a Windows program from autoexec.txt in vDos
> with the command he mentioned.

Actually, if you situate the command after the PATH statement in
AUTOEXEC.TXT, you can use bare filenames (assuming, of course, that the
referenced files are in the path); e.g.:

cmd.exe /c start notepad.exe

--
Carl Distefano
mailto:cld@xxxxxxxx