Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!uupsi!sunic!dkuug!imada!micro From: micro@imada.ou.dk (Klaus Pedersen) Newsgroups: comp.sys.atari.st.tech Subject: Re: Bug in Overscan software. Message-ID: <1991May19.163606.18142@imada.ou.dk> Date: 19 May 91 16:36:06 GMT References: <1991May14.193547.29278@imada.ou.dk> <3365@quepasa.cs.tu-berlin.de> Sender: news@imada.ou.dk (USENET News System) Organization: Dept. of Math. & Computer Science, Odense University, Denmark Lines: 59 ki@opal.cs.tu-berlin.de (Karsten Isakovic) writes: >In article <1991May14.193547.29278@imada.ou.dk> micro@imada.ou.dk (Klaus Pedersen) writes: >>There have been some talk about Overscan here lately, that reminded me >>that I found 2 bugs in the driver software. The bugs are in the same 10 >>lines of code, and they are kind of strange! >Hello Klaus, >the actual driver for the autoswitch-overscan is 51! versions away from the >old one released into netland. I found lots of bugs ;-) I my version I have fixed these : o a bug that ment that some programs wrote one pixel outside the screen, have been fixed. o the software is 68010/20/30/40 clean. o the software works on TOS 1.4 and __later__! (it don't use undocumented system variables to enlarge the screen memory any more!) o it is now possible to disable Overscan, from within a bad program (last resort, as it is not possible to tell accs and the AES about the new screen size). o it is also possible to enable/disable Overscan from the desktop (general, because it is possible to init. AES and accs). o the hook into VDI now preserves ALL address registers! o the driver is now 3700 bytes, of which 3000 stays in memory, (not counting the larger screen (68Kb)). >The autoswitch feature is about 32 versions old and running very stable. I >ported this feature to some other software, now we have the autoswitch >SM-124 emulator for TT-High and and autoswitch driver for the Reflex 1024 >card. How do you tell accs and the AES about the new screen size, I know that you have a reputation for making some really awsome hooks into TOS/GEM. But you can't tell accs that the screen size have changed - can you? >>Then why don't I release my version? >>- Overscan is Commercial now so I don't know if it's legal. Also my version >>have been hacked so much that it probaly have even more errors. It have been running stable for some time though, and a lot have been fixed! >>How can we fix this problem - I guess that Karsten will tell us that he have >>a fix (called autoswitch Overscan). >You are right :-) But it was a good way to say 'what is wrong', so everybody >interested can change it in the source... But not everybody can! If I send my version to atari.archive, (driver bin and source only) would you care? Should I release it as a Patch like KAOS, so that everybody that allready have overscan can patch it?? (sick) >>Klaus, micro@imada.ou.dk >Karsten, ki@opal.cs.tu-berlin.de Klaus, micro@imada.ou.dk