I'm really impressed with this new version. it is just so fast and lightweight in size
started the DOS old system PC and found a empty folder C:\TMP made it in vDos and everything now works.
two problems remain:
i need to use the PROM programmer software and GAL programmer software and they need to talk to the Coms port in my W7 computer to get at the programming devices. W7 device manager calls it COM1 how is this addressed in vDos
For some reason this latest version of vDos you sent me does not seem to be creating its C:\vDos folder that contains a windows accessible image of the vDos C: disk image. Is there something I need to flush left over from the earlier version on vDos i was working with or is it fussy about which directory it was started in (i initially started it in "downloads") could this have poisoned something to stop the C:\vDos win folder being created. However if i create a folder in the vDos system C:\ it pops up in the Windows C:\ directory as an empty shared folder which i can fill from the windows side but all C:\ vDos folders i create pop up in the windows C:\ directory including my TMP one.
To use COM1 in vDos as COM1 of Windows, you have to add to config.txt: COM1 = "COM1":
Note: The trailing colon is mandatory, and the serial COM1 has to be setup correctly before vDos is started.
The Windows C:\vDos folder is created by the vDosSetup installation program. vDos doesn’t create any files or folders out of its own, but eventually the #LPTx/COMx.asc/txt files with printing. vDos C: is by default the Windows folder vDos.exe is started from. But you can change that by USE C: Windows_path/ in autoexec.txt.