0000000F, 00000003 error
T. Kelley Boylan
on a drive that, without warning, came up with a sad Mac and
0000000F
00000003
What be this thing, and if you know what it is, how do I circumvent it?
Many thanks.
-Kelley-
Robert Altizer
finish for over a minute while the internal (startup) disk
thrashes, as if rebuilding a directory, doing a virus scan,
or some such activity.
System: Mac IIsi w/ DayStar Turbo 040i accellerator board, 170MB Quantum
internal drive, 17MB RAM, MacOS 7.5.1; virtually the same set of
INITs as I use on another machine that does NOT exhibit the
disk thrashing problem. SAM installed, but no startup scan
enabled.
Solicitation: Anybody have any [analytical] ideas? Suggestions that I
try all possible permutations of my INIT set will be accepted
with forbearance, but I'd really like to hear some insightful
comments. Thanks in advance.
Regards,
Bob
--
#-------------------------------------------------------------------------#
# Robert Altizer - Chief Software Engineer alt...@fasolt.sps.mot.com #
# Motorola LATG Advanced Technologies Robert_Altizer-R10908@email #
# 2100 East Elliot Road M/S EL600 RAJR90Q@email (QuickMail) #
# Tempe, AZ USA 85284 (602) 413-4158(v)/413-5543(f) #
#-------------------------------------------------------------------------#
# Dry grass dying makes the sound of rain. -- W. S. Merwin #
#-------------------------------------------------------------------------#
Nicholas E Tyler
: Thank goodness for having a backup system, but there's still a lot of data
: 0000000F
: 00000003
I believe the error code 000F is typically associated with software
problems or hardware that has been modified. Here's what MacCheck says:
xxxx000F Illegal instruction error
00000003
Try restarting the Macintosh with Option and Command keys held down to
rebuild the desktop file (or better yet use TechTool from MicroMat, it's
more thorough). If you still have the problem after doing this it may be
time to do a clean install.
You might want to get some diagnostic software for your Mac.
MicorMat's TechTool is very good (and free for personal use). I believe it
is available on both eWorld and AOL --any web sites anyone?-- Also,
MacCheck can be had free of charge. There are other more expensive
diagnostic software packages (NOW, Norton, MacTools, etc. etc.) Depending
on how much you like to fuss with your Mac, and how much ready cash you
have to spend, anyone of these might not be bad investments.
---Nic
=/|\=/|\=/|\=/|\=/|\=/|\=/|\=/|\=/|\=/|\=/|\=/|\=/|\=/|\=/|\=/|\=/|\=/|\=/|\=
For the unpeaceful how can there be happiness?
Dostoevski
=\|/=\|/=\|/=\|/=\|/=\|/=\|/=\|/=\|/=\|/=\|/=\|/=\|/=\|/=\|/=\|/=\|/=\|/=\|/=
Lee Hoffner
>
> Solicitation: Anybody have any [analytical] ideas? Suggestions that I
> try all possible permutations of my INIT set will be accepted
> with forbearance, but I'd really like to hear some insightful
> comments. Thanks in advance.
>
> Regards,
My best suggestion: buy Conflict Catcher 3 from Cassady & Greene. It is
worth every penny: it's helped me find several extension conflicts and
enabled me to create *useful* (i.e. tested, not merely guessed at)
extension sets so I can get the use out of those apps I bought without
suffering through their incompatibilities.
--
Lee Hoffner.
lhof...@interaccess.com
T. Kelley Boylan
(Nicholas E Tyler) wrote:
> T. Kelley Boylan (kel...@tezcat.com) wrote:
> : Thank goodness for having a backup system, but there's still a lot of data
> : on a drive that, without warning, came up with a sad Mac and
>
> : 0000000F
> : 00000003
Replying to my own post here -- something about the way the machine booted
made me think it was a low-level driver (not drive) failure. To those of
you who posted fixes, thanks, but you were a wee bit off the mark. ;-)
The same thing happened to my SE/30 about five years ago, so I tried
fixing it the same way and it worked. Just in case it happens to you,
here's the procedure:
1) Open up the machine and ground yourself (to keep from frying anything)
2) Unplug the internal SCSI bus
3) Boot from an external drive
4) Start FWB Toolkit or Silverlining
5) While it's running, plug the internal SCSI bus back in; this
is risky -- you could fry the motherboard
6) Have the utility scan the bus for drives, and mount the dead drive
7) Install or update the driver
Reboot to be sure everything works, and you're back in business without a
single bit of lost data. This is *not* a procedure for the weak at heart
or anyone who's unfamiliar with the innards of a computer. To say you
could toast the whole thing is an understatement, but that's the fix.
-Kelley-
Thomas Kelley Boylan
-Author, Que Publishing -Reviewer, MacWeek
Upgrading and Repairing Macs -Technical writer, contract
Microsoft Office 4.2 -System Administrator, contract
Internet and the Macintosh -Fan, The Simpsons
T. Kelley Boylan
Author, Que Publishing
Reviewer, Ziff-Davis
Resident, Chicago
Sitting, comfy chair
Joakim Magnus Taraldsen
Kelley Boylan) wrote:
> Thank goodness for having a backup system, but there's still a lot of data
> on a drive that, without warning, came up with a sad Mac and
>
> 0000000F
> 00000003
This might be a HD driver related problem. Try booting from a floppy and
update your driver. If the machine fails with the same sad mac code even
when fed a bootable floppy you might try this:
Remove the cover and disconnect the power plug from the disk.
Boot from a floppy and reconnect the power plug to make the
drive spin up so that your program can find it (HD SC Setup or
whatever was used to format it).
Best of luck
-Magnus
--
___________________________________________________________________
Joakim Magnus Taraldsen DoD #00101010
University of Oslo KotB 87 VFR 750F
Center for Information Technology Services "Blue Baby" =o%o
J.M.Ta...@usit.uio.no, http://www.uio.no/~joakimt
A)bort, R)etry, I)gnore, V)alium?
___________________________________________________________________
Ian R. Campbell
>Thank goodness for having a backup system, but there's still a lot of data
>on a drive that, without warning, came up with a sad Mac and
>0000000F
>00000003
>What be this thing, and if you know what it is, how do I circumvent it?
>Many thanks.
You either have a hard disk problem or your SCSI controller got screwed up
--
Ian R. Campbell i...@penrij.UUCP
Vince Salupo
>Symptoms: After the last INIT registers on the screen, startup doesn't
> finish for over a minute while the internal (startup) disk
> thrashes, as if rebuilding a directory, doing a virus scan,
> or some such activity.
>
You haven't mentioned if you see the problem with all extensions off. If
the problem goes away and really is an INIT problem, I can only recommend
Conflict Catcher II or 3. Either will do the trick for your machine. Can
you list your INITS?
If the problem does not go away without the INITs loaded, try any of the
following. They are IMO listed in order of difficulty.
1) Rebuild desktop
2) Defragment your harddrive (Shareware:FastUnfrag )
(Commercial: Norton Util or Mactools Pro)
3) Reload System software
4) Update Hard disk driver to current version (Free if Apple, $$ if not)
Good luck
Vincent P Salupo
Eli Lilly and Company
v.sa...@lilly.com
As usual: All opinions are mine and do not reflect the views of my
Company, Managers, co-workers, spouse, children, dog
etc....
Mike Rosenberg
alt...@chdasic.sps.mot.com (Robert Altizer) wrote:
> Symptoms: After the last INIT registers on the screen, startup doesn't
> finish for over a minute while the internal (startup) disk
> thrashes, as if rebuilding a directory, doing a virus scan,
> or some such activity.
If you haven't tried booting with all extensions disabled, do that and see
if the problem occurs. If it occurs even without extensions, try
rebuilding your desktop files, preferably using one of the methods that
delete the old ones. I'd recommend using TechTool, available from
Info-Mac. If that doesn't work, my next step would be to see how
fragmented your drive is and optimize if necessary.
If the problem _doesn't_ occur with extensions disabled, then it's possible
one of your extensions (or an associated preferences file) has become
corrupted, and a search for the culprit is in order. If that's the case,
I'd recommend buying Conflict Catcher.
-------
Mike Rosenberg
Macintosh Consultant/Instructor
<http://www.macconsult.com/mikerose>
"If you ever get annoyed, look at me, I'm self employed..."
Laurent Paumier
: 2) Unplug the internal SCSI bus
: 3) Boot from an external drive
: 4) Start FWB Toolkit or Silverlining
: 5) While it's running, plug the internal SCSI bus back in; this is risky -- you could fry the motherboard
: 6) Have the utility scan the bus for drives, and mount the dead drive
: 7) Install or update the driver
Alternatively, you could hold <Command><Option><Shift><Backspace> while
booting from a floppy disk... It will prevent the SCSI drives from being
mounted.
--
Paumier Laurent. <Pau...@ENSERB.U-Bordeaux.FR>
Brian A. Carb
>Thank goodness for having a backup system, but there's still a lot of data
>on a drive that, without warning, came up with a sad Mac and
>0000000F
>00000003
>What be this thing, and if you know what it is, how do I circumvent it?
This code indicates a SCSI device driver error on the bootable drive. If your
device driver is one of Apple's, you can boot from a floppy and then run
Apple's hard disk Setup program to replace the driver. We were able to fix
this error by running On Track's Disk Manager Mac program to install a new
SCSI device driver.
Brian A. Carb
bc...@tr.unisys.com
Dan Allison
happens no matter what you set in the control panel. This is mostly a long
pause, not too much disk access. Apple Menu Options builds a database of
your Apple Menu folders and "recent" items at startup, and this may take a
long while in some situations. Try turning SAM off, and temporarily taking
AMO out of control panels, to see if your trashing goes away. Try AMO with
and without "recent."
In article <449tkq$h...@newsgate.sps.mot.com>, alt...@chdasic.sps.mot.com wrote:
> Symptoms: After the last INIT registers on the screen, startup
> doesn't finish for over a minute while the internal (startup) disk
> thrashes
> # Robert Altizer - Chief Software Engineer
> alt...@fasolt.sps.mot.com
Dan Allison Computer Support / Desktop Publishing / Env Ed
dal...@cello.gina.calstate.edu 916-894-7611 Chico, CA
~~~~~~~~^^^^^^^^~~~~~~~~^^^^^^^^~~~~~~~~^^^^^^^^~~~~~~~~^^^^^^^^~~~~
Vince Salupo
ric...@interaccess.com wrote:
>> 2) Defragment your harddrive (Shareware:FastUnfrag )
>> (Commercial: Norton Util or Mactools Pro)
>> 3) Reload System software
>> 4) Update Hard disk driver to current version (Free if Apple, $$ if not)
>
>
>What is the Hard Disk driver? Where do I get the update? I've never seen
>the driver in my system folder (Apple 7500/1gig.)
>
>Thanks!!
On your installer CD or Disks you will find a copy of "Apple SC HD setup".
This allows you to setup your hard drive driver. This is not a file you
can access. At least I have never accidentally bumped into it. Check the
version of the above application. The most recent I believe is v7.3.5. It
will update your driver software for your hard drive. Since you have such
a new machine, you may have the most up to date driver and this will get
you nowhere. When you launch SC HD setup you will see a button to update
the driver. Press it and it will be done in a few seconds. Quit, Reboot
and see if you notice any difference.
Don't know the technical details, so I don't know what this would fix but
it has helped other people posting in the past. If you use a third party
disk formatter like Silverlining or FWB harddisk toolkit, you might have
to pay for the upgrade that fixes bugs related to your particular CPU.
Robin D.H. Walker
Robert Altizer <alt...@chdasic.sps.mot.com> wrote:
>Symptoms: After the last INIT registers on the screen, startup doesn't
> finish for over a minute while the internal (startup) disk
> or some such activity.
If you are running Macintosh Easy Open and Dataviz MacLink+,
try turning these two off. Does the delay go away?
--
Robin Walker (Network Admin), Queens' College, Cambridge, CB3 9ET, GB
rd...@cam.ac.uk IBMmail:i1006437 Tel:+44 1223 335528 Fax:+44 1223 335566
Frank R. Rezny
>In article <kelleyb-2609...@1.1.1.1>, kel...@tezcat.com (T.
>Kelley Boylan) wrote:
>
>> 1) Open up the machine and ground yourself (to keep from frying anything)
>> 2) Unplug the internal SCSI bus
>> 3) Boot from an external drive
>> 4) Start FWB Toolkit or Silverlining
>> 5) While it's running, plug the internal SCSI bus back in; this
>> is risky -- you could fry the motherboard
>
>anything.
>
>-Magnus
>
This error message is also a possible indication that the SCSI drive is set up for blind transfers.
Most newer SCSI drives can do blind transfers (Fujitsu, IBM, Conner and others). The Mac (especially if it has an accelerator card i=
n it from Daystar (maybe others) is not capable of handling this. If your SCSI driver software has the ability to turn off blind tra=
nsfers,, great.. If not, you may have to change some jumper settings.
Frank R. Rezny
HyperSoft MedWorks Inc.
http:infoweb.magi.com/~hypersft
Authorised MacMedical Dealer - Please Note MacMedical is for Ontario Only
Truly Elegant, Billing, Billing and Accounting,
Medical Records and Letters Software
Authorised Apple VAR
The only computer line with a great OOBE (out of box experience.)
MedWorks BBS (613)592-7903
Log in as GUEST and download the hi-BBS software Mac or Windows
Over 1 gig of compressed files primarily for Mac
Randy Patton
> Symptoms: After the last INIT registers on the screen, startup doesn't
> finish for over a minute while the internal (startup) disk
> thrashes,
You don't have File Sharing turned on, do you?
Mark D. Huppert
In article <449tkq$h...@newsgate.sps.mot.com>,
alt...@chdasic.sps.mot.com (Robert Altizer) wrote:
> Symptoms: After the last INIT registers on the screen, startup doesn't
> finish for over a minute while the internal (startup) disk
> or some such activity.
That same "problem" happened for me as well. The "solution" was edvident
after I installed Conflict Catcher 3. It seems that most of my installed
INITs and extentions do so without displaying an icon at start up.
Actually, CC3 showed that it was not just 4 INITs being installed at start
up, but, over 20!
--
Mark D. Huppert
Mason City.IA
Ken Landa
mhup...@netins.net (Mark D. Huppert) wrote:
> In article <449tkq$h...@newsgate.sps.mot.com>,
> alt...@chdasic.sps.mot.com (Robert Altizer) wrote:
>
> > Symptoms: After the last INIT registers on the screen, startup doesn't
> > finish for over a minute while the internal (startup) disk
> > thrashes, as if rebuilding a directory, doing a virus scan,
> > or some such activity.
>
This could be Apple files sharing starting up. If you have it on, and
don't need it, turn it off... This will cut down on startup times
dramatically.
--
Ken Landa
bh...@musicb.mcgill.ca
"I don't care! I _never_ cared!
And at this point I don't care twice as much as I never did before!"
David Bettany
> In article <44a0mj$c...@nic.umass.edu>, nty...@wilde.oit.umass.edu
> (Nicholas E Tyler) wrote:
>
> > T. Kelley Boylan (kel...@tezcat.com) wrote:
> > : Thank goodness for having a backup system, but there's still a lot of data
> > : on a drive that, without warning, came up with a sad Mac and
> >
> > : 0000000F
> > : 00000003
>
>
> Replying to my own post here -- something about the way the machine booted
> made me think it was a low-level driver (not drive) failure. To those of
> you who posted fixes, thanks, but you were a wee bit off the mark. ;-)
> The same thing happened to my SE/30 about five years ago, so I tried
> fixing it the same way and it worked. Just in case it happens to you,
> here's the procedure:
>
> 1) Open up the machine and ground yourself (to keep from frying anything)
> 2) Unplug the internal SCSI bus
> 3) Boot from an external drive
> 4) Start FWB Toolkit or Silverlining
> 5) While it's running, plug the internal SCSI bus back in; this
> is risky -- you could fry the motherboard
> 6) Have the utility scan the bus for drives, and mount the dead drive
> 7) Install or update the driver
>
> Reboot to be sure everything works, and you're back in business without a
> single bit of lost data. This is *not* a procedure for the weak at heart
> or anyone who's unfamiliar with the innards of a computer. To say you
> could toast the whole thing is an understatement, but that's the fix.
Kelley,
The idea in theory is fine, just don't think pluging the SCSI data cable
in while the rest of the system is live is at all safe. Perhaps a better
way is to leave the data cable in and remove the power cable, then plug it
back in and continue as you suggest.
Cheers
David Bettany
Wellington
New Zealand
Robert Altizer
>In article <449tkq$h...@newsgate.sps.mot.com>, alt...@chdasic.sps.mot.com wrote:
>
>> Symptoms: After the last INIT registers on the screen, startup doesn't
>> finish for over a minute while the internal (startup) disk
>> thrashes,
>
No, but it *is* on my machine at work which doesn't take nearly as long.
I will be checking the following:
-- Removing SAM (not on machine at work)
-- Reducing number of fonts (tough on someone who thinks "he who dies with
the most fonts, wins!")
-- Checking the Apple Menus Options settings
Thanks for the suggestions, folks! I didn't get to applying fixes last
weekend due to the decision to spend it on non-computer activities.
twir...@gmail.com
> Thank goodness for having a backup system, but there's still a lot of data
> on a drive that, without warning, came up with a sad Mac and
>
> 0000000F
> 00000003
>
>
>
> -Kelley-
0000000F
00000003 means that you presses the interrupt key while the Macintosh was starting up. To fix it: just restart the pc, and it will go away.
Jolly Roger
--
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.
JR
eval...@gmail.com
> Thank goodness for having a backup system, but there's still a lot of data
> on a drive that, without warning, came up with a sad Mac and
>
> 0000000F
> 00000003
>
> What be this thing, and if you know what it is, how do I circumvent it?
>
> Many thanks.
>
> -Kelley-
Auric__
it had been posted closer to the original post... over ***21 YEARS AGO!***
Except, in 1995, Kelley was using either a 68k machine or a PowerPC, where
the error codes may very well have been completely different.
Fucking Google Groupies.
--
There's a big difference between a BUTTER KNIFE and a BUTTERFLY KNIFE.
David Lanahan
Wolffan
(in article<dca5b80f-9a34-4702...@googlegroups.com>):
from _1995_.
What is it about Google Groups users that they can’t bloody look at the
posting dates? 1995. Zombified in 2017, twice. Zombified _again_... and using
an empty post. All three zombi attempts made by Google Groups users.
Auric__
> What is it about Google Groups users that they can't bloody look at the
> posting dates? 1995. Zombified in 2017, twice. Zombified _again_... and
> using an empty post. All three zombi attempts made by Google Groups users.
--
Between two evils, I choose the competent one.