Page 1 of 1

Can't boot from Lite-On CDRW burner, with G3

PostPosted: Fri Mar 07, 2003 12:06 pm
by CyberMac
I just installed Lite-On LTR-52246S 52/24/52 CD-RW in an Apple Mac G3 BW/400mhz, 512mb Ram, running OSX10.2.4, (Jumper pin set at master, also tried slave) it is recognised by the computer, reads & burns disks no problems, BUT it will not operate as a boot drive using my System Disk, or any other Utility boot disk.
Also, can any one tell me what the 2nd set of Jumper pins are on the LHS ? (when facing the rear) I have searched every where on the liteon website, downloaded the manual, but they are not explained. I know Apple used Lite-On drives in their G4 computers, could this set be for that purpose? :-?

PostPosted: Fri Mar 07, 2003 12:46 pm
by cfitz
I'm not a Mac user, but I find it hard to imagine that you need to set something on the CD-RW drive to be able to boot from it. After all, it just responds to read and write commands, and doesn't care how the associated data is used. Instead, I think you should be concentrating your efforts on configuring the software and hardware of your Mac.

cfitz

PostPosted: Fri Mar 07, 2003 1:02 pm
by cfitz
According to this, OS X 10.2.3 and above have native support for the LTR-52246S:

http://forums.xlr8yourmac.com/action.la ... 62&-search

That site looks like it would be a good resource for you. You will find a database of user reports on their experiences with various drives in Mac computers there:

http://forums.xlr8yourmac.com/drivedb/s ... vedb.lasso

Click here for their list of LiteOn CD-RW reports. Some users have reported they can boot from CD with the LTR-52246S, others report they can not. Good luck.

cfitz

PostPosted: Fri Mar 07, 2003 1:15 pm
by CyberMac
All the Mac OSX10.2.4 software/hardware is configured correctly, the cd drive I just took out of there worked fine, ie: it would boot up on a systems disk no prob at all, on another occasion I have had a Cyberdrive burner in there and it too would act as a boot drive, this one has me stumpted! :roll: Could it be a faulty drive? :(