|
Post by john on May 15, 2019 22:14:58 GMT 1
In the past few days I installed vDos on my new computer (the May 5, 2019 version) and after adjusting the config.txt files to handle some new and changed parameters I began running my dBase 4 programs. Unfortunately, the new version of vDos no longer supports the mouse even though I have MOUSE = ON specified. I found an installation file on my old PC for the 2015 version of vDos, which always worked well with my dBase programs, reinstalled it, readjusted the config.txt files, and now the mouse works fine. Apparently, something has changed between the 2015 and 2019 versions of vDos that makes the mouse fail for dBase 4.
|
|
|
Post by Jos on May 16, 2019 0:19:44 GMT 1
You are the first to report a dBase 4 mouse issue. No specific vDos version, only 2015 functioning. I suspect a dBase setting to blame, will look at the (supposed) mouse issue.
Jos
|
|
|
Post by Jos on May 16, 2019 8:56:22 GMT 1
Found it, the mishap is only in 2019.05.01 and will most likely only effect dBase4. The fix will be included in the next version.
Jos
|
|
|
Post by john on May 16, 2019 16:16:04 GMT 1
Thanks, Jos. I'll continue running the 2015 version for now and watch for the next version.
|
|
|
Post by herman on May 17, 2019 7:16:45 GMT 1
In my dBase V application, clicking the mouse in menus works with vDos version 20190501.
Regards Herman
|
|
|
Post by Jos on May 17, 2019 23:16:54 GMT 1
dBase 4 frequently calls Int 16h, the BIOS keyboard interface, sometimes while the interrupt enable flag is cleared. A dBase4 mishap: Interrupt handling by the CPU should only be disabled in specific situations and for a short time. vDos 2019.05.01 traps some interrupts, bypassing the halt/exit of the emulated CPU to handle the interrupt. But it didn’t at first consider interrupts could be disabled, while an actual interrupt enables interrupts once completed.
Jos
|
|