Tim Seufert wrote:
> At 2:49 AM +0200 8/17/99, Sidney Ho wrote:
Depending on where the DuoList server is (USA Pacific, I presume), I wrote
it at the much more reasonable Central European (Swiss) Time of 11:49 AM :)
>>Absurd it may be, but, as you can see, I'm speculating openly and inviting
>>opinions/explanations to better understand the problem. The fact is the
>>problem hard drive would boot both a G3-3400 directly and a G3-300 tower (in
>>SCSI mode) but not the 2400 (either directly installed or in SCSI mode).
>>That is absurd and defies logic. Apple recommends clean installs whenever
>>possible, and with OS 8.6 updater this is not possible. Any good
>>ideas/explanations why a directory will boot on certain computers and not
>>others?
> It's possible that a piece of program code used only on the 2400 got
> corrupted. However, given how similar the 2400 is to the 3400 and G3-3400
> (the major differences are that the G3-3400 has a PPC 750 and a C&T 65554
> video chip instead of a 603e and C&T 65550), the G3-3400 should have
> crashed too.
That's exactly what I thought, too. Thoroughly puzzling or I would NEVER
have reinstalled the HD into my 2400 with such confidence and finality.
> Now, if you had done a file backup of that disk, reformatted it, restored
> the files, and had the problem disappear, I'd accept that as much better
> evidence that it was actually directory damage which caused the problem.
> As it is you can't rule out corruption of file *contents*.
I use Apple drivers 173. DFA 852, NDD 404, NDD 5beta and TT211 all failed to
resolve the problem or even detect directory damage. Only Disk Warrior saved
the day--beautifully!!! It only rewrites fresh directories. I wanted to try
anything to avoid a full blown reformat and tweaking of everything anew.
Jay <[EMAIL PROTECTED]> asked:
> Did you have the master/slave/solo options configured properly?
Yes, went further than that....Tried via direct HD internal install (solo in
both 3400 and 2400), master, SCSI mode to G3-3400 and G-3 tower, 3400 in
SCSI mode to 2400, external HD hooked to 3400 and 2400, PC card drive to
lead bootup, and floppy, oh, and removeable VST HD inside 3400.
This was really the most illogical, confusing and aggravating piece of
computer sleuthing I've ever endured. Sometimes I'm stubborn and this was a
challenge. Usually a black or gray screen, no chime etc., inability to
connect external devices, unsuccessful multiple PRAM resets are grounds to
send out the 2400 for repair. Based on the shared experiences of this list,
I think there are some subjective grounds to conclude that the 2400 is more
sensitive (somehow, however inexplicable and absurd) to deep PRAM and
directory damage. This is just an idiosyncratic story of bringing one 2400
back from the dead. I was close to giving up at least 3 times. YMMV but be
persistent!
---
Sidney Ho
[EMAIL PROTECTED]
----------
Duo/2400 List, The friendliest place on the Net!
A listserv for users and fans of Mac subportables.
FAQ at <http://www.themacintoshguy.com/lists/DuoListFAQ.shtml>
Be sure to visit Mac2400! <http://www.sineware.com/mac2400>
Dr. Bott LLC | Get a LapBottom with new �GRIPPIER� gripper pads!
| http://www.drbott.com/prod/lapbot.html $23.00
Midwest Mac Parts <http://www.midwestmac.com> | After-market parts
for Macs. Fix your ticking dock for $59 w/ trade-in of PS. 888-356-1104
PowerBook Guy is | Click here!
Everything PowerBook! | http://www.powerbookguy.com
