VBDOS environment in vDos (EMS issue?)

[dominicraf]

I would like to be able to run the VBDOS programming/debug environment ('IDE') in vDos - VBDOS.EXE. It loads and VBDOS shows its normal opening screen but then immediately hangs - won't even close with the top right X - you have to use Task Manager to end vDos.

I have tried adding EMSMAGIC settings in autoexec.txt (with EMSMAGIC.EXE in the vDos directory), but it doesn't help. Nevertheless the nature of the failure makes me suspect some memory issue, and VBDOS definitely does use EMS. (I have it running perfectly in NTVDMx64, courtesy of EMSMAGIC, and also in DOS VMs.)

Any suggestions welcome.

[Jos]

It’s no memory issue; the IDE of VBDOS hooks into the low level INT 9 to communicate with the keyboard. Will be for capturing (stealing) some key combinations for debugging.

vDos however doesn’t generate INT 9, so the IDE will wait for something that isn’t going to happen. For instance WPDOS also hooks into INT 9, but still uses INT 16 to communicate with the keyboard.

Nothing to do about that, VBDOS IDE is one of two/three programs that insists on solely relying on INT 9. Fot the IDE you could use DOSBox instead.

Jos

[dominicraf]

Thanks Jos for the quick reply and explanation, as you say I will have to use another platform for VBDOS IDE.

[dominicraf]

Sorry to reopen this one, but now I have VDOS working peachily for compiled VBDOS programs and it would be a complete solution if only I could run VBDOS IDE in VDOS too. I can run VBDOS IDE in other environments (DOS VM, NTVDMx64, DOSBox-X) but this is not ideal for testing because there are subtle differences in behaviour of the environments (+ none of the others are as nice to use as VDOS). Any chance that INT9 generation could be added into VDOS so I can edit my programs in VBDOS IDE? I promise to register for a network copy if this can be done!

[Jos]

I have to disappoint you, INT9 emulation won’t come.
Too much information Windows already gathered and passed on is lost by INT9 whose only input is the scan code of pressed or released keys.
You would need for instance an external (DOS!) keyboard driver to support a non-standard US keyboard.

Jos

[dominicraf]

Oh so sad! :-(

How DOSBox-X manage it? VBDOS IDE loads without crashing in DOSBox-X, and they offer a menu option to send special key combinations (most critically CTRL+BREAK, so you can break out of a running program in VBDOS back to the debugger environment).

[Jos]

You would have to ask the DOXBox-X team. But I reckon it will be the same as with DOSBox, especially the Unicode information is just dropped/lost at emulating INT9.
It will only contain code to deal with standard US keyboards, all others need an external keyboard driver.

Jos