From: SourceForge.net <no...@so...> - 2007-12-10 08:21:14
|
Bugs item #1847275, was opened at 2007-12-09 15:15 Message generated for change (Comment added) made by manuelbi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=421861&aid=1847275&group_id=38274 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: General/misc Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Manuel Bilderbeek (manuelbi) Assigned to: Nobody/Anonymous (nobody) Summary: Penguin Adventure doesn't work on some machines Initial Comment: On at least a Philips VG 8020/00, Goldstar FC-200 and Toshiba HX-10, Penguin Adventure crashes in the initialization code. On my real HX-10, it runs fine. Analysis by BiFi: <BiFiMSX> badly interfering interrupt <BiFiMSX> the problem is in the init part: <BiFiMSX> 1. set up blocks (store values in RAM) <BiFiMSX> 2. reset that area <BiFiMSX> 3. init sound (enable interrupts) <BiFiMSX> 4. interrupt occurs <BiFiMSX> in step 1 the hook handler is set up as well <BiFiMSX> so the penguin adventure handler is called <BiFiMSX> the handler switches to the sound part to handle it, and restores the 'old' blocks, which were reset just before the sound init <Quibus> it seems to get in some kind of loop around 0x2766 <Quibus> 0x2762 - 0x2768 is a djnz loop So, there seems to be something going wrong with interrupt timing? ---------------------------------------------------------------------- >Comment By: Manuel Bilderbeek (manuelbi) Date: 2007-12-10 09:21 Message: Logged In: YES user_id=78178 Originator: YES This seems similar to 739150 (Zanac title corrupted), where there is also a badly timed interrupt. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=421861&aid=1847275&group_id=38274 |