| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | vm02: calling all IIcs - Take 2 |
Thanks again to Tom for trying this out. Maybe I can convince him to try this one out: http://schmenk.is-a-geek.com/tarfiles/VM02ALPHA3.DSK.zip I also discovered a couple of other issues now fixed. Certain ROM routines will disable interrupts. Some of my sample classes that call ROM routines for low res and hi res graphics all of the sudden stopped responding to interrupts. I now re-enable interrupts after every native method. I also discovered that my comparison opcodes would adjust the stack pointer, then compare the values that were now above the stack. Tsk, tsk. When an interrupt would occur during the comparison, the values would get trashed. Glen Bredon wrote a nifty little TSR style program that would hook the VBL interrupt to keep time. His notes mentioned problems with various IIc models. He actually didn't bother calling the mouse firmware to service the interrupt on a IIc. The VBL interrupt would continue interrupting anyway. So I now look to see if any hardware claimed the interrupt. If not, I assume it's the VBL interrupt. Hope this works, Dave... --- SBBSecho 2.12-Win32* Origin: Derby City Gateway (1:2320/100.2008) SEEN-BY: 10/1 3 34/999 106/1 120/228 123/500 140/1 222/2 226/0 236/150 249/303 SEEN-BY: 250/306 261/20 38 100 1404 1406 1410 1418 266/1413 280/1027 320/119 SEEN-BY: 393/11 396/45 633/260 267 712/848 800/432 801/161 189 2222/700 SEEN-BY: 2320/100 105 200 2905/0 @PATH: 2320/100 261/38 633/260 267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.