|
Prev: Skybuck presents FastGetBit ( Value, BitPosition ) (latency 3)
Next: Fast way of splitting an image into bit planes ?
From: rio on 4 May 2008 14:45 "Wolfgang Kern" <nowhere(a)never.at> ha scritto > Many old programs weren't aware of 'huge' RAM, VRAM > and speed values, so they in fact often stumble into > DIV overflow, my workaround for DOS-based programs is > a tiny TSR which hooks DIV-exceptions and skips the my "workaround" it is never to do that error (divide overflow error) > faulty instruction with AX = FFFFh DX = 0. > wolfgang (HEX-coder, but w/o magic) > btw: you got a funny/weird name :)
From: Wolfgang Kern on 5 May 2008 05:38
"rio" mentioned: >> Many old programs weren't aware of 'huge' RAM, VRAM >> and speed values, so they in fact often stumble into >> DIV overflow, my workaround for DOS-based programs is >> a tiny TSR which hooks DIV-exceptions and skips the > my "workaround" it is never to do that error (divide overflow error) Fine, do you really rewrite existing good but old tools and games just to make them work on newer PCs ? :) I found it more convenient to waste ~150 bytes RAM in a TSR. >> faulty instruction with AX = FFFFh DX = 0. __ wolfgang |