PDA

View Full Version : beige G3, problem child



jaabo
05-20-2001, 01:30 AM
I adopted a fussy beige G3 (sweet freebee, yet, there had to be a rub).

I replaced the 4G IDE internal hard drive w/ a 60G IDE.

She's somewhat faster than my 604 clone and I'd love to work with her but she has a few problems:

1. when copying a large set of files she sometimes hangs up, may stutter and continue to copy the files or may just hang.

2. downloaded files tend to suffer from bad resource and/or data forks rendering them useless.

3. Static-type sound on MP3 playback (they play fine on the 604).

Under disk first aid the drive appears to be fine, but the above problems still occur.

L'il he'p,

John

magician
05-21-2001, 04:33 AM
is your bG3 a rev A or otherwise?

what drive utility did you use to initialize the drive?

how did you set the drive? As a master or slave?

which IDE bus are you using for the drive? The bG3 has two buses (http://www.macgurus.com/beta/mbppcg3desk.html).

Louie
05-21-2001, 10:43 PM
We need the answers to Mag's questions. There are several possibilities. One could be disk corruption from timing issues between the beige's ATA controller and a UltraDMA 66/100 drive.

jaabo
06-01-2001, 03:22 AM
regarding the beige G3 problems:

Q: is your bG3 a rev A or otherwise?
A: (from System profiler)
Production information
ROM revision: $77D.40F2

Hardware overview
Machine ID: 510
Model name: Power Macintosh G3 series
Keyboard type: Apple Extended Keyboard
Attributes: Audio card
Processor info: PowerPC G3
Machine speed: 300 MHz
Nanokernel version: 2.21
Nanokernel pool extends: 0
Nanokernel scheduled CPUs:1

Q: what drive utility did you use to initialize the drive?
A: (Apple) Drive Setup

Q: how did I set drive master or slave?:
A: There's only one internal drive (answer: master?)

Q: which IDE bus are you using for the drive? The bG3 has two buses.
A: As far as I can tell, the ribbon cable for the drive runs from one IDE slot to the drive and returns to the other IDE slot(?!?!)


thanks, John

magician
06-01-2001, 05:06 AM
disconnect that IDE cable and make sure that it runs from the logic board to the drive and stops right there.

pull your drive, and ensure that it is the only device on that cable.

make certain it is configured as a master.

if you have that cable running from logic board connector thru the drive to the other logic board connector, I'm going to suspect the case will be solved.