unable to use keyboard in some software

[itarcenco]

Greetings everyone,

first of all thank you Jos for creating vDos, big savior !

kindly advise if anyone has encountered issues with any keyboard input in vDos ? or numpad specifically?

i am able to get most of my software work properly except certain ones that will accept mouse movement but no key entry is recognized as soon as you open the software(

although in vDosplus (sorry to mention this here) - the keyboard entry is recognized but not the numpad))) in the same software

wandering if anyone encountered the issue and help sort it out

screen with the ver of vDos attached.

and a copy of the software bank.exe is the lauch file

Best Regards!

Attachments:

[Jos]

It seems your program uses INT9/IRQ1 to communicate with the keyboard. To my knowledge only Visual Basic programs do so.
And no idea why, the BIOS provides for all functionality to conveniently communicate with the keyboard w/o messing around with the keyboard UART and servicing hardware interrupts.

Although your program hooks into the INT9/IRQ1 interrupt service routine, that is never called by vDos. So your program won’t see any keystrokes.
vDosPlus adapted the keyboard routines of DOSBox to support INT9/IRQ1, probably you have to load a keyboard driver separately. It will be discussed at the vDosPlus forum at SourceForge.

vDos itself won’t support INT9/IRQ1. It’s just too silly, while you would be the second one or so with this ‘problem’.

Jos

[itarcenco]

Jos, thanks a lot for the information

And i really you appreciate all your work

Good luck everyone!)

PS: A quick follow up for those who encounter the same issue, set up the config.txt of vDosPlus with option KEYMODE = 1 (can take 0-disabled; 1-XyWrite/Nota Bene; 2-WP); that fixes the issue with the keyboard and numpad, at least with my instance..

[steve]

Hi Itarceno,

From the screen shot you posted it looks very much like a TurboVision screen. If so, which version of TV and with which Borland compiler?

Thanks,
Steve Dyson

[itarcenco]

Hi Steve, 

yeah, thats TurboVision & Borland turbo pascal not sure which version though, since i'm not the developer, but i can ask .. if needed 

Best regards, 

[steve]

Hi Itarceno,

I was hoping you were going to say the c++version of TV, too bad!
It would have been useful for me to tie up with another c++ developer using TV.

Cheers,
Steve

[Chris]

Jul 22, 2018 16:44:17 GMT 1 Jos said:

It seems your program uses INT9/IRQ1 to communicate with the keyboard. To my knowledge only Visual Basic programs do so.
And no idea why, the BIOS provides for all functionality to conveniently communicate with the keyboard w/o messing around with the keyboard UART and servicing hardware interrupts.

Although your program hooks into the INT9/IRQ1 interrupt service routine, that is never called by vDos. So your program won’t see any keystrokes.
vDosPlus adapted the keyboard routines of DOSBox to support INT9/IRQ1, probably you have to load a keyboard driver separately. It will be discussed at the vDosPlus forum at SourceForge.

vDos itself won’t support INT9/IRQ1. It’s just too silly, while you would be the second one or so with this ‘problem’.

Jos

I'm the third one or so …
Some old progs written with QuickBasic oder VisualBasic do so too.

Chris

[Jos]

“Some old progs written with QuickBasic oder VisualBasic do so too”.

QB compiled programs should just run (only the IDE not). But what Basic programs did survive the transfer to Windows and are actually still used?

Just the fact you can come up with some (Basic) program that doesn’t run in vDos is no motivation to spend any/much time to get that running in vDos.

BTW, when Basic is mentioned, I lose interest, sorry.

Jos

[Wolstan]

Actually, I make four. Qbasic45 loads, the mouse works, you can retrieve previously written programs and run them. But you can't edit them. Input within the program works.

The old Forum has an extensive thread on this.

Perhaps the demand is bigger than immediately apparent?

Please?

[Jos]

As mentioned before: vDos is primary intended to run existing DOS programs still in use.
QBasic IDE not accepting keyboard input is of no interest to me.
Besides, you got alternatives if you want to modify those programs. Do that in DOSBox, or some Windows code editor. Eventually calling vDos to compile the program, shouldn’t be that hard to setup.

Jos

[vdoscharles]

Hello everyone, I have a problem when trying to access vdosplus through remote access using an iPad. Vdosplus is installed on Windows 10 and works normally, but when I try to access it through Microsoft's RDClient, the keyboard stops working, only the Enter and delete keys work. Does anyone have any idea what I could do?

[Jos]

No support for vDosPlus here.
You could ask its developer Wengier Wu for this issue.
vDosPlus is based on an older vDos version. Could be it has been solved meanwhile, the method the iPad RDPclient sends keystrokes to the remote host…

Jos