Damaged Hard Drive
John Meyer/Symantec Volunteer
> Configuration Information:
> Version: 3.5.2
> Operating system: System 8.1
> Formatting: --Other--
>
> When running norton utilities on a desktop G3 w/ OS 8.1, the hard
> drive would not boot afterwards. Is there an update or a correction?
> All of my data was lost and I had to comlpetely install all of my
> software.
>
> Steve Gern
Hi Steve:
Are you sure you were running was NUM 3.5.2 or was it either 3.5.1 or
3.5? The G3 may have had the hard drive formatted in HFS+ and, if
so, neither of these versions is compatible with that hard drive
format. Only NUm 3.5.2, the later version released for OS8.1
contains the lock-out to prevent NUM damage to HFS+ driectory
structures. You should cease using NUM until you verify the version
you are using. if you drive is HFS Standard, NUM 3.5.2 is the
correct version to be using with OS8.1. If your drive is HFS+, NUM
will refuse to work on the drive to prevent damage.
Other than that, if you drive was formatted HFS and you had a
problem, what error messages did NUM give you? What errors did it
fix? All of these will be in the test run report. If you could post
them it will make it easier to figure out what happened.
Bob Feldman
I have also had similar problems with norton disk doctor on a G3. It
has trouble rebooting and cannot fix the identified problems. The
problem that keeps repating itself and cannot be dealt with seems to
be :
An error was found in an alias record in the catalog b-tree. An
alias record was found without a corresponding file record. (5,9,11)
Node #1285, Record Offset 1
The leaf alias record was fixed.
Although it is reported fixed, Disk Doctor seems to go into a
do-loop, repeating fixed and reporting the same error as many times
as I care to click the fix button. After 100 or so repetitions, I am
forced to surrender and stop the test. What is going on here? Apple
disk tools reports a problem, but cannot fix it either.
I am running 3.5.2, by the way, and the system will not boot from the
Norton utilities CD, saying it is not for this version of mac! But
your messages in this forum indicate that it should... right?
I have erased and reinitialized this disk twice, but the same
problems re occur. Please help!!!!
John Meyer/Symantec Volunteer
hi Bob:
you are probably running Norton Anti-Virus 5.0 and have not yet
downloaded the patch to NAVM 5.0.2. Here is a link to the patch:
http://www.symantec.com/techsupp/files/navm/norton_antivirus_for_macintosh.html
Install the patch on your installed version of NAVM5.0.
The reason you cannot boot from the CD ROM is that Apple changed
their boot ROMs in later production G3 machines so that older system
enablers no longer work.
COpy NUM 3.5.2 to a floppy disk and then boot from your Apple OS CD
ROM and run Disk Doctor from the floppy as follows:
Here is what the alias records is all about, NAVM 5.0 has an
automatic virus checker called Safezones that scans all new files
created on your machine. Before the patch, if you created a file and
Safezones scanned it and the file was later deleted an artifact was
left on your disk - the "alias record". The patch stops the creation
of new artifacts, but you have a bunch of files that were created
BEFORE you installed the patch that will leave artifacts when they
are deleted. You may not think that there are that many files, but
your browser creates one file for each page you read in the cache.
It also creates one file for each gra[hic on each page, your e-mail
is a file for each message...and so forth.
To clean this up, do this. Open your browser and clear the caceh.
Next, boot from your NUM CD ROM or Apple OS CD ROM. Start up Disk
Doctor from your floppy disk copy of the updated version. Go to
"EDIT:PREFERENCES" and set Disk Doctor to "fix automatically". Run
Disk Doctor on your hard drive. This will clear out all of the alias
records.
Remember: the patch has stopped the creation of new artifacts, but
you may still have some files on your machine from BEFORE you
installed the patch. These may be deleted at a later time and you
may see a few alias records reported because of it. Simply run Disk
Doctor as above and they will be removed.
Hope this helps.