I try to use VDosPlus 2017.08.01 buil 2018.03.01 and btrieve Record Manager 5.10a. From time to time I got the Btrieve error 2 (I/O error occurred during disk read/write). I have a clue, that it apear when I switch on 4dos.
I myself still use one DOS financial program that also relies on the Btrieve Record Manager. And, what are the changes, I was this afternoon in contact with one who finalized the migration of NTVDM PC’s to Windows 10 64-Bit in a small (NAS, 4 users) network. Btrieve is still in use w/o problems by some.
Complicating factor with Pervasive is of course the Windows interface at the client PC’s. You could have a look at: www.vdos.info/faqs.html - Miscellaneous - Btrieve/Pervasive. "Work and (final) testing" is essentially completed. Though I found the layer/bridge (Btrieve TSR replacement) a bit limited to only Pervasive. I contacted Mertech (https://www.mertech.com/migrate-btrieve-to-sql/) for their BTR2SQL alternative. That replaces the Pervasive server/database by MySQL, or some other variant. They conducted a flawless test with Btfiler (DOS general Btrieve manager) - vDos - their interface DLL and MS SQL Server. I still would prefer to do also some BTR2SQL testing myself, but I already doubt there will be real interest in vDos support of Pervasive server.
So the Pervasive/BTR2SQL bridge will be incoorporated in the next vDos release (though at a extra license price given the work and limited interest). It's then just adding a line Btrieve = Pervasive/BTR2SQL interface DLL to config.txt. For instance btrieve = W3BTRV7.DLL, then of course omit loading the DOS Btrieve TSR (it’s all transparent to the DOS program).