CompuServe Messages

Robert, thank you for your efforts to help me with my amouse problem. I appreciate this very much. As my bridgeboard is an A2286 only, I don't run a memory manager. I use the bridgeboard mainly for converting files to the Amiga from 5.1/4" MS-DOS formatted disks. The second purpose running the bridgeboard, is to test MS-DOS based programs I wrote for compatibility. The trident card I got in my Amiga is some SVGA, it will display 600 x 800 VESA mode (6Ah) just fine (no mouse of course). I wonder if ACad will do some direct accesses to the mouse driver beyond simply managing it through int 33h. There are some other things you have to attend using the amouse driver. – The mouse pointer will only move to any new location when explicitly calling the mouse driver. So you have to poll the driver to make the pointer move continiously, – Mouse functions 05h (Get Button Press Information) and 06h (Get Button Release Information) don't work reliably – one has to code a workaround for this. The fact the cursor blinks when there is some other action on the display simply results from the need that you have to turn the mouse pointer off each time you do any rendering on the screen, to protect the mouse pointer's buffer from containing the old image, which would be visible again when you move the mouse. It's no hardware sprite as with the Amiga. When writing a program, you can reduce the visible blinking by only turning the mouse pointer off when it is in the area you are rendering. There is a function (10h – Conditional Off) in each mouse driver which will support this. Well, I think I finally have to disassemble and reverse engineer the amouse driver to look for a possible patch. Bad job, though. Thanks again for your suggestions. – wkc – … via AP from Hamburg, Germany