In a fit of foolish enthusiasm, I offered to replace a HD in a friend's
StrongARM RiscPC. It runs RISC OS 3.7, has 38MB RAM (32+4+2MBVRAM), a
10-base-2-and-T network adaptor and a CD-ROM drive.
My plan was to de-configure the CD-ROM drive, connect the new drive as a
slave in its place and transfer all the files over. Then I'd swap the
drives and reconfigure the CD-ROM. Easy.
So I unconfigured the CD-ROM drive, switched the machine off,
disconnected the drive physically, and then switched the machine back on
"just in case".
From that moment on, I get "Abort on Instruction Fetch" errors as soon
as I turn the machine on, and special mention of "Error number
&80000002" each time. Holding down delete /may/ get it as far as the
desktop, but not always.
The fact that it quotes an error number makes me wonder if it is some
sort of POST failure. Anyone know this error code? An IDE problem? A RAM
test problem?
The owner says that this machine probably hasn't been hard-reset for at
least a year, so part of me wonders whether it's a CMOS or battery fault.
Many thanks in advance for advice! I think the owner is beginning to go
spare from spending more than three hours "non-digitally"!
In article <451fbb28$0$8724$ed2619ec@ptn-nntp-reader02.plus.net>,
Kris Adcock <news@danceswithferrets.ork> wrote:
Quote:
My plan was to de-configure the CD-ROM drive, connect the new drive as a slave in its place and transfer all the files over. Then I'd swap the drives and reconfigure the CD-ROM. Easy.
So I unconfigured the CD-ROM drive, switched the machine off, disconnected the drive physically, and then switched the machine back on "just in case".
From that moment on, I get "Abort on Instruction Fetch" errors as soon as I turn the machine on, and special mention of "Error number &80000002" each time. Holding down delete /may/ get it as far as the desktop, but not always.
Get to the desktop and in a task window check *unplug and see if
CDFSSoftATAPI is unplugged. If not do so. It seems to cause all sorts of
problems if it can't find a CD drive.
--
*Is it true that cannibals don't eat clowns because they taste funny?
In article <451fbb28$0$8724$ed2619ec@ptn-nntp-reader02.plus.net>, Kris Adcock <news@danceswithferrets.ork> wrote:
Quote:
My plan was to de-configure the CD-ROM drive, connect the new drive as a slave in its place and transfer all the files over. Then I'd swap the drives and reconfigure the CD-ROM. Easy. So I unconfigured the CD-ROM drive, switched the machine off, disconnected the drive physically, and then switched the machine back on "just in case". From that moment on, I get "Abort on Instruction Fetch" errors as soon as I turn the machine on, and special mention of "Error number &80000002" each time. Holding down delete /may/ get it as far as the desktop, but not always.
Get to the desktop and in a task window check *unplug and see if CDFSSoftATAPI is unplugged. If not do so. It seems to cause all sorts of problems if it can't find a CD drive.
Hi Dave,
Thanks for your reply! Unfortunately, it makes no difference even if I
connect things back up as they were (including putting the CD-ROM drive
back).
Interestingly: pressing ctrl+break just generates another exception - it
doesn't reset! Seems quite serious ...
In article <451fe050$0$24498$ed2e19e4@ptn-nntp-reader04.plus.net>, Kris
Adcock <news@danceswithferrets.ork> wrote:
Quote:
Dave Plowman (News) wrote:
Quote:
In article <451fbb28$0$8724$ed2619ec@ptn-nntp-reader02.plus.net>, Kris Adcock <news@danceswithferrets.ork> wrote:
Quote:
From that moment on, I get "Abort on Instruction Fetch" errors as soon as I turn the machine on, and special mention of "Error number &80000002" each time. Holding down delete /may/ get it as far as the desktop, but not always.
Get to the desktop and in a task window check *unplug and see if CDFSSoftATAPI is unplugged. If not do so. It seems to cause all sorts of problems if it can't find a CD drive.
Thanks for your reply! Unfortunately, it makes no difference even if I connect things back up as they were (including putting the CD-ROM drive back).
Interestingly: pressing ctrl+break just generates another exception - it doesn't reset! Seems quite serious ...
What happens if you completely remove all drives? There is a possibility
that the OS may be the problem. See http://www.iconbar.com/forums/viewt...p?threadid=7421 "The Icon Bar
forums: Installing RISC OS 3.7 - Woes"
On 1 Oct 2006 Kris Adcock <news@danceswithferrets.ork> wrote:
Quote:
From that moment on, I get "Abort on Instruction Fetch" errors as soon as I turn the machine on, and special mention of "Error number &80000002" each time. Holding down delete /may/ get it as far as the desktop, but not always.
This is invariably a hardware error caused by a bus error. Strip down the
entire machine, removing all cables, podule and network cards, RAM, VRAM and
the processor. Then put back together. Often this just remakes all the bus
connections properly and cures the problems, sometimes it may occur again a
few months later, so rinse and repeat.
In article <451fbb28$0$8724$ed2619ec@ptn-nntp-reader02.plus.net>, Kris Adcock
<URL:mailto:news@danceswithferrets.ork> wrote:
Quote:
Afternoon all, In a fit of foolish enthusiasm, I offered to replace a HD in a friend's StrongARM RiscPC. It runs RISC OS 3.7, has 38MB RAM (32+4+2MBVRAM), a 10-base-2-and-T network adaptor and a CD-ROM drive. My plan was to de-configure the CD-ROM drive, connect the new drive as a slave in its place and transfer all the files over. Then I'd swap the drives and reconfigure the CD-ROM. Easy. So I unconfigured the CD-ROM drive, switched the machine off, disconnected the drive physically, and then switched the machine back on "just in case". From that moment on, I get "Abort on Instruction Fetch" errors as soon as I turn the machine on, and special mention of "Error number &80000002" each time. Holding down delete /may/ get it as far as the desktop, but not always.
And did you also make sure the remaining HD is master only (jumpers)?
Gr. HH
-- jheinsbroek@tip.nl Sent from a Risc PC near me. (RISC OS 4.02)
In article <671b276f4e.druck@druck.freeuk.net>,
druck <news@druck.freeuk.com> wrote:
Quote:
On 1 Oct 2006 Kris Adcock <news@danceswithferrets.ork> wrote:
Quote:
From that moment on, I get "Abort on Instruction Fetch" errors as soon as I turn the machine on, and special mention of "Error number &80000002" each time. Holding down delete /may/ get it as far as the desktop, but not always.
This is invariably a hardware error caused by a bus error. Strip down the entire machine, removing all cables, podule and network cards, RAM, VRAM and the processor. Then put back together. Often this just remakes all the bus connections properly and cures the problems, sometimes it may occur again a few months later, so rinse and repeat.
Whilst you've got it stripped down it's a good idea to carefully hoover
out the the dust, hairs, mouse droppings etc that have accumulated inside
and clean the fan. Cleaning the connectors with electolube also helps.
The MyLounge.com forum is intended for informational use only and should not
be relied upon and is not a substitute for any advice. The information contained
on MyLounge.com are opinions and suggestions of members and is not a representation
of the opinions of MyLounge.com. MyLounge.com does not warrant or vouch for
the accuracy, completeness or usefulness of any postings or the qualifications
of any person responding. Please consult a expert or seek the services of an
attorney in your area for more accuracy on your specific situation. Please note
that our forums also serve as mirrors to Usenet newsgroups. Many posts you see
on our forums are made by newsgroup users who may not be members of MyLounge.com
Term of Service
Error number &80000002
Linear Mode
