Pismo DVD drive booting issue

[markyb86]

Hello,

Having a problem getting the Pismo to boot anything other than whats already on the hard drive.

I have several versions of OS9 on CD, OSX 10.2, 10.3 & 10.4 and none will boot this guy. The drive sounds like its doing something but all I can get is a folder with a question mark.

I've heard of others having this issue, but not of their solutions.

Does anyone here have a suggestion?

I even tried taking the apple drive out of the caddy and using a generic dvd-rom from an Acer. Same result.

Mark

 

[theos911]

My Wallstreet will only take CD-R - not CD-RW. DVDs are even more picky.

 

[Macdrone]

I agree with the recordable cd statement. More over you should use a classic Mac to burn so you can check the box for make bootable for making back ups of bootable disks. If you don't they are not "blessed" and therefore won't boot.

 

[markyb86]

Well the one disk was burned on a Luxo Jr. iMac, but the 9.0.4 is a legit copy? and the others were burned with windblows xp on 4x speed. I will try again with a new one burned off the G3. Thanks!

 

[Macdrone]

If legit copy won't work then drive may be dead.

 

[markyb86]

are generic drives compatible with these guys? or is that something I should stop trying?

also is it possible the caddy is just bad?

 

[jruschme]

OEM drive is master, generic is probably slave. Does the CD show up if you hold the Opt key at boot?

 

[markyb86]

In either configuration, no.

Now that you mention master/slave.. Would the CF>IDE adapter throw it off? I'm pretty sure I had it set to slave.

 

[markyb86]

Don't know what I did, but I got it to boot the CD version of tiger, rather than the DVD version. |)

 

[Macdrone]

That's ok I got a PowerBook 667 that I can't get to boot is 9, even in classic. I'm stumped.

 

[beachycove]

I had this problem on a Pismo and could not for the life of me resolve it. And I tried hard. So I got another parts Pismo, swapped logic boards, and it all worked properly afterwards.

I have thought since that the trouble was either a logic board fault, or POSSIBLY an error thrown up by later ATA standards than those in play in 1998-99. The latter would, however, presumably only explain the problem if there were differences between logic board revisions. I suppose I tend to the fault explanation myself.