The problem doesn't stop with the intern DVD/CD Burner... since i use an extern USB2 burner i could read DVD's and CD's at least on this way. But now for chrismas i wanted to burn some CD's with a Special Ed Program i've made for some presents and what happens? Apple seems to block also to burn CD's on extern machines.
It's not true, that Apple Computer handles CD/DVD Drives as any other systems. Richard Drummond, the famous writer of the C-Compiler DICE and programmer of uae for mac described Apple-Computer behaviour as a "real pig"!, as everyone can read in his manual for compiling the emulator on Mac OS X under the doc/scsi, section, right after he described how to easy configure the devices under linux, BSD-Unixes, and other systems. But read for your own:
-----
Now we get to the real problems. SCSI emulation with E-UAE on OS X is
currently a real pig, due to some features and limitations of OS X. The big
problem is that you need a writable device - a CD or DVD burner - for SCSI
emulation to work at all. This is because the OS X kernel will only let you
send SCSI commands to a writable device (for this problem to be solved, UAE
would need to support a real SCSI emulation - the current implementation is
simply a wrapper around a host SCSI device).
The second problem is that the Finder does not like sharing a removable
media device with any other application. For SCSI emulation to work, you
must start UAE without a disc inserted in your CD or DVD writer. Otherwise,
Finder will auto-mount the disc and not let UAE access the device. A
different (more drastic) solution is to kill OS X's auto-mount daemon, but the
procedure for doing this differs depending on which version of OS X you
have. Somebody remind me to look this up and fill in the details here.
The third problem is getting UAE to locate your CD or DVD writer. libscg on
OS X (the SCSI transport layer which UAE uses) doesn't support bus-scanning
on OS X. Only one device can currently be used with UAE, and you have to
name it explicitly with the 'scsi_device=' option in your config file.
For the first CD writer, this will be:
scsi_device=IOCompactDiscServices/0
For the first DVD writer, this will be
scsi_device=IODVDServices/0
Also remember to add the 'scsi=true' option to your config.
If set up correctly, UAE will output something similar to the following when
starting up:
scsibus:0
0,0,0 0 'YAMAHA ' 'CRW842S ' '1.0f' CD-ROM
0,1,0 0 'YAMAHA ' 'CRW842S ' '1.0f' CD-ROM
0,2,0 0 'YAMAHA ' 'CRW842S ' '1.0f' CD-ROM
0,3,0 0 'YAMAHA ' 'CRW842S ' '1.0f' CD-ROM
0,4,0 0 'YAMAHA ' 'CRW842S ' '1.0f' CD-ROM
0,5,0 0 'YAMAHA ' 'CRW842S ' '1.0f' CD-ROM
0,6,0 0 'YAMAHA ' 'CRW842S ' '1.0f' CD-ROM
0,7,0 0 'YAMAHA ' 'CRW842S ' '1.0f' CD-ROM
0,8,0 0 'YAMAHA ' 'CRW842S ' '1.0f' CD-ROM
0,9,0 0 'YAMAHA ' 'CRW842S ' '1.0f' CD-ROM
0,10,0 0 'YAMAHA ' 'CRW842S ' '1.0f' CD-ROM
0,11,0 0 'YAMAHA ' 'CRW842S ' '1.0f' CD-ROM
0,12,0 0 'YAMAHA ' 'CRW842S ' '1.0f' CD-ROM
0,13,0 0 'YAMAHA ' 'CRW842S ' '1.0f' CD-ROM
0,14,0 0 'YAMAHA ' 'CRW842S ' '1.0f' CD-ROM
0,15,0 0 'YAMAHA ' 'CRW842S ' '1.0f' CD-ROM
SCSIDEV: 16 devices found
support_scsi = 1 support_ioctl = 0
and then it'll complain a bit about being unable to get exclusive access and
then it'll say
(0,0,0) = uaescsi.device:0
Okay. Don't look so worried. What's happening here is that UAE is trying to
scan for SCSI devices, can't, and ends up finding the same device 16 times.
Not very elegant, I know, but it works. I will tidy this up eventually. If
Finder has an exclusive lock on your device because it has mounted a disc,
UAE will just say 'Unable to get exclusive access to device' once and say:
SCSIDEV: 0 devices found
---
So, at least three important behaviours are not normal/standard. And I'm still sure that Apple messed around with some firmware or driver specific parts in Mac OS X 10.6 that also from this installation influences the failout of the Devices under Mac OS X 10.4!
Thats really the last Mac i bought. The only thing that kept me to stay with Apple over the last years was, when i watched funny messages and behaviours of Windows-Machines. But now whats enough is enough:
APPLE JUST WORKS?
NO IT DOESN'T!
Cheers and happy chrismas,
tazman
Message was edited by: Tazmandevil