|
|
Post by doug on Apr 21, 2021 19:30:58 GMT 1
I'm running a foxpro 2.5 accounting system on win10 64 bit multi user. Vdos and VdosPlus work just fine except on record locking. Makes no sense since I moved to vdosplus because is it works better with multi user record locking. However , using either vdos or vdos plus, same freeze up happens.
Any ideas?
|
|
|
|
Post by Jos on Apr 21, 2021 20:22:13 GMT 1
vDosPlus is basically an older vDos version (2015) with added stuff, so no way it would work better with record locking.
Locking a record cannot stall vDos. The DOS API File region locking function is primarily passed on to the Windows API since that is the OS managing the drive, or will be forwarded to the OS managing the remote drive. If Windows API returns an error, vDos will give it 2 more tries after a small pause. Then return an error condition to the DOS app.
How did you establish the freeze up is caused by record locking?
Jos
|
|
|
|
Post by doug on Apr 27, 2021 17:50:48 GMT 1
I attempted to edit a customer record from two clients at the same time. When running in Win 98 or Win XP, the record lock works, in Vdos and VdosPlus, it locks the record and gives the normal message it can't be accessed, then freezes up.
|
|
|
|
Post by Jos on Apr 27, 2021 18:19:05 GMT 1
I guess FoxPro(X) will be the largest user group of vDos. And no reports of this odd behavior.
As said, locking a record cannot stall vDos. If it did, FoxPro wouldn’t even get an error condition and be able to display an error message to that effect.
You could start vDos on the second PC with the log option (….vDos.exe /log) and submit the generated vDos.log file after vDos/FoxPro freezes.
Jos
|
|
