USB Drives not always being recognised by vDos on W10

[paddy885]

Hi - first thing to say is great product Jos.

I have a Foxpro 2.6 system that is working fine with just 1 problem. The system takes periodic and daily securities to a USB Disk (Memory Stick)- Windows  Drive D:. Windows can see the drive but vDos often doesn't. 

The sequence of events seems to be that if no memory stick is in place or it is changed while the Foxpro app is running vDos cannot see it although windows does. Most of the time if the memory stick is inplace when the Foxpro app is started it seems to see the drive - not always

Unfortunatly the usb memory sticks need to really be changed as part of the process e.g. insert "parts" memory stick ... now insert the "past orders" memory stick ... etc 

Anything I can do to find/resolve this problem I am happy to do - BTW it is happening on more that one PC and I can replicate it on my test pc.

The autoexec.txt is as follows 

use c: c:\

use d: d:\


cd \fox26

C:\BOS\PROGS\FOXR.EXE -t -cc:\bos\progs\configa.fp c:\bos\progs\bos.app

exit


and the config.txt is simply

WINDOW = 75

MOUSE = ON


I suspect that the problem is something to do with the media change - vDos not seeing the change once started

Paddy

[Jos]

The USE command tells vDos that when the drive letter to the left is referred by the DOS program, to pass instead the path to right to Windows.

The Windows path has to be valid the moment of USE, and when the DOS drive letter is referred to.

I cannot replicate your issue. Make sure the Windows drive letter is not changed switching the memory stick, becoming for instance E:.
You could also start vDos with the log option (…./vDos.exe log) and have a look at the generated vDos.log file.

Jos

[paddy885]

Jos - that is the problem - if no USB memory stick (Drive d) is inserted when vDos launched - no access - Memory stick installed and then run vDos all OK - so initial problem resolved

Many thanks

Paddy