|
Post by lhsisson on Aug 24, 2018 16:34:44 GMT 1
Hi, new to vDOS and this forum. Have an old DOS program I wrote in the '90's in Borland Pascal that we have kept alive running it in an XP Pro VMWare VM which is overkill. However, works fine that way including mouse. Program uses dBase III for its db using Topaz and some other libraries. Just found vDOS a few days ago and so far program seems to run fine in vDOS. Tried DOSBox previously and it would not work so we are excited about vDOS so far--kudos for a great program! Have run into one problem so far which, though not a show-stopper, would be nice to fix. When MOUSE=ON mouse works great until one tries to go into an edit mode the program has for editing existing records (either by clicking edit button or selecting it with arrow keys and Enter). At that point program stops with and error 202 which, it looks like is a stack overflow problem. When MOUSE is not enabled the same edit mode works without errors. Any suggestions?
Thanks!
|
|
|
Post by Jos on Aug 24, 2018 17:36:54 GMT 1
Not really, normally programs use the mouse interface provided by vDos. That ‘operates’ outside the DOS VM, so it can’t be the cause of an error (like stack overflow) related to the emulated CPU. Only a few programs install a mouse driver of their own. Like WordPerfect, mostly to show a mouse cursor (block) of its own. But no errors reported with those programs so far. If you can provide for some setup to replicate the error, I could have a look.
Jos
|
|
|
Post by lhsisson on Aug 24, 2018 18:18:47 GMT 1
Ok, that helps. Based on your response, I will look back over my code to see if I'm installing/using some mouse handling code--seems like I might have done that but it's been many years so don't remember. Thanks!
|
|
|
Post by lhsisson on Aug 29, 2018 14:13:47 GMT 1
Update: did a little snooping. Program is written in Borland Pascal and uses 3 different libraries including one named Saywhat? for screen handling. Found the documentation for SayWhat? and found that it looks for the Microsoft mouse driver. Found mouse.com and tried loading it in vDOS with LOADHIGH. That produced a "DOS MCB list corrupted" error. Should LOADHIGH work for mouse.com in vDOS? Maybe I have the wrong mouse.com? Any thoughts? Thanks!
|
|
|
Post by Jos on Aug 29, 2018 16:43:54 GMT 1
Basically vDos provides for MS mouse driver functionality itself. So no need to load mouse.com, while I question how mouse.com is supposed to communicate with the fake hardware that would connect to a mouse in the DOS past. If SayWhat? calls the obvious Int 33 to check for the presence of a MS mouse driver, it should just be satisfied.
LOADHIGH should allow to load programs in upper memory, but no idea what ‘weird’ things mouse.com will do to try communicating with the ‘actual’ mouse.
Jos
|
|