From mint-bounce@lists.fishpool.fi Thu Mar 11 04:09:00 2010 Message-ID: From: "Jo Even Skarstein" To: References: <72454075-6FA5-46CA-A174-A3AE573771A6@gmail.com> <04F5AE6B-D53F-4EE1-BA57-9BA46392BD13@gmail.com> <1B8C9039-CFB4-4675-9E79-5D1CC4F54DAC@gmail.com> <0D259770-D6AF-408E-B721-2BD14DA6E237@gmail.com> <17DDE44C-929C-4003-AB62-2253AC49D883@gmail.com> <11a6f2b11003101720i46a7bd71u295b5d327423218b@mail.gmail.com> <3212BDDA-2FD3-47D3-A3E8-9A4EEDAB06B3@gmail.com> In-Reply-To: Subject: Re: [MiNT] Patch for xaloader.prg Date: Thu, 11 Mar 2010 10:08:30 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_01F0_01CAC102.CC9E9240" X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 14.0.8089.726 X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8089.726 X-EsetScannerBuild: 6731 X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: joska@online.no Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Dette er en melding med flere deler i MIME-format. ------=_NextPart_000_01F0_01CAC102.CC9E9240 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Are you using memory protection? Could it be a problem related to the = MMU after a soft reset? Jo Even From: Miro Kropacek=20 Sent: Thursday, March 11, 2010 8:57 AM To: Peter Persson=20 Cc: Paul Wratt ; mint=20 Subject: Re: [MiNT] Patch for xaloader.prg Actually my previous statement was wrong. It happens sometimes when = switching the CT60 form 060 to 030 mode. Next boot, freemint gets lost = and somehow persists on using the default binary (mint.prg) despite the = presence of a 060 binary (mint060.prg). No big deal, I wouldn't be = surprised if the "feature" originates from some CT60-oddity. When talking about oddities, does anyone observe this (on CT60): I boot = into freemint (might be just pure basic shell, nothing special), then I = do software reset ('reboot' or from xaaes) into TOS and there's 90% = chance I get sooner or later bus error. When I use hardware reset or = reset from that bus error state, TOS is sound and stable. I have no clue = what could cause it, certainly it's something in kernel/ct60tos, not = some external app. --=20 MiKRO / Mystic Bytes http://mikro.atari.org ------=_NextPart_000_01F0_01CAC102.CC9E9240 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Are you using memory protection? Could it be a = problem=20 related to the MMU after a soft reset?
 
Jo Even

Sent: Thursday, March 11, 2010 8:57 AM
Cc: Paul Wratt ; mint=20
Subject: Re: [MiNT] Patch for xaloader.prg

Actually my previous statement was wrong. It happens = sometimes when switching the CT60 form 060 to 030 mode. Next boot, = freemint=20 gets lost and somehow persists on using the default binary (mint.prg) = despite=20 the presence of a 060 binary (mint060.prg). No big deal, I wouldn't be = surprised if the "feature" originates from some = CT60-oddity.
When talking about oddities, does anyone observe this (on CT60): I = boot=20 into freemint (might be just pure basic shell, nothing special), then I = do=20 software reset ('reboot' or from xaaes) into TOS and there's 90% chance = I get=20 sooner or later bus error. When I use hardware reset or reset from that = bus=20 error state, TOS is sound and stable. I have no clue what could cause = it,=20 certainly it's something in kernel/ct60tos, not some external=20 app.

--
MiKRO / Mystic Bytes
http://mikro.atari.org
------=_NextPart_000_01F0_01CAC102.CC9E9240--