VB DOS program doesn't work

[victor9000]

Hi,

I'm still using my highly customized 'old' DOS enterprise software for my business and will stay with it because I couldn't find any Windows software that does the same.

Until now I used vDosPlus for a long time but wanted to switch to vDOS because there's no development in the former and I'd like to use RL.

Now I have a big problem:
The software was written by me in the 90s with MS VB for DOS and uses some forms for text editing etc..

With vDOSplus everything works fine.

With vDos everything works until I call one of the forms. Then vDos freezes the application, no keyboard response or anything else.

I can only kill it via taskmanager.

The main difference I see is that vDos only has 3845k XMS / 0 EMS & 105k far memory & where vDosplus has 16.133k XMS / 16.777k EMS & 160k far memory.

Does anybody have an idea what goes wrong here?

Walter

[Jos]

The text editing functionality, like that in MS compilers, will be based on MS EDIT code.
Instead of INT 16, that uses the low level INT 9 to communicate with the keyboard.
MS EDIT code is linked to INT 9, but that code never gets executed since vDos doesn’t emulate INT 9.
Too much information is lost by using INT 9, and it needs KEYBX.EXE to be loaded for non-US keyboards.
vDosPlus reinstated the original DOSBox code that mimics INT 9.

Record Locking should be no issue with vDosPlus since vDos supports that as of its first release.

Don’t know about the memory figures, vDos provides for 16KB XMS and 16KB EMS. Older versions only one of those at a set amount. Without EMS the UMB (upper) memory size would be 96+64=160KB.

Jos