Amiga.org
Amiga computer related discussion => Amiga Hardware Issues and discussion => Topic started by: koshman on February 07, 2010, 06:44:12 PM
-
Hi,
I have a problem with CDROM drive in my A4000D. I know this has been discussed to death, but I really don't know what to do.
When I bought the Amiga it had 3.9 installed on a 15GB IDE drive and a working CDROM drive. A few weeks later (during my experimenting :) ) the system crashed and 3 of the 4 partitions were not recognised any longer (including the system partition). I was going to scrap the old harddrive eventually anyway so decided to utilize a spare 4GB Microdrive and install the OS on it.
Since that incident my CDROM drive does not work - HDToolbox doesn't see it - I tried 3.9, stock 3.1 floppy and Bloodwych's ClassicWB 3.1. I thought the problem was the CF adapter so I connected the old harddrive and reinstalled OS 3.9, but nothing changed. I ordered a new IDE cable from Amigakit, but still nothing. I have 3 similar Teac CDROM drives like the one that was there - tried all of them - they all work in a PC, but not in the Amiga. I tried different molexes, jumpers (master, slave, cable select), with or without a harddrive or floppy, but I got nothing. I though about the onboard IDE controller malfunctioning, but both the HDD and CF adapter work without a hitch. I'm really at my wits' end.
Do you have any suggestions about what might be the problem.
Thanks in advance.
PS: I don't actually need the CDROM drive that much, but without it I can't update 3.9 with Boing bags and I just want to know what's happening...
-
Have you installed any CD software, and if yes, which? What do you have in Devs : Dosdrivers?
-
Among others I have CD0 and CD1 in Devs:Dosdrivers/. In 3.9 I'm using the default CacheCDFS, in my 3.1 boot floppy AmiCDFS and whatever Bloodwych uses as CDROM driver in his 3.1.
But if I understand it correctly none of this matters if the HDToolbox can't even SEE the drive, right? I don't think it's a software issue, or at least it doesn't seem like it.
-
Among others I have CD0 and CD1 in Devs:Dosdrivers/. In 3.9 I'm using the default CacheCDFS, in my 3.1 boot floppy AmiCDFS and whatever Bloodwych uses as CDROM driver in his 3.1.
You need to have the device driver the mount files points to in Devs as well. The build in controller can't handle CD drives without a proper device driver.
But if I understand it correctly none of this matters if the HDToolbox can't even SEE the drive, right?
No, as HDToolbox doesn't see CD drives, depending on which version of HDToolbox you are using. As the name points out it is for HDs, not CDs.
-
scsi.device in the 3.1 ROM doesn't handle ATAPI devices. I *think* the one from 3.9 does, so your CD0 should be looking for the CD drive as scsi.device, unit 1 (assuming your HD is set to master and the CD drive is slave). If the 3.9 ROM update isn't kicking in, or you're skipping the scsi.device update in the startup-sequence, this is a moot point since you'll then automatically fall back to the useless 3.1 version.
So then you'd need atapi.device from IDEFix, or asim_atapi.device from AsimCDFS.
EDIT: Can you post the output from version scsi.device?
-
Or you could just install idefix97. That's how Ive got mine configured - IDE HD master and DVD-rom as slave on the IDE port on my A4000D.
Weed
-
As Matt says, IDEfix97 could be your friend here. I would try to use FindDevice to locate your CDrom. Once you have the device type and unit number, you can set about making the right driver. I already had this screenshot uploaded, so just brought it here in case it was of help to you. FindDevice found the IDE Zip drive as scsi.device unit 3, so I was then able to edit the driver accordingly to get an icon for the drive.
(http://i120.photobucket.com/albums/o164/Cyberstorm604e/Zip-Help.jpg)
But In your case you will probably be editing an icon called CD0
.
-
Thank you all. I'll try FindDevice first to see it everything's in order hardware-wise.
-
A really noob question - where can I fnd that Finddevice tool? Is it part of CacheCDFS or IDEfix? Thanks :)
-
IDEfix :)
-
Just to add that FindDevice won't find devices that need IDEfix97 to be running for them to be seen. You can check that IDEfix97 is installed by looking in the C drawer of your Workbench and checking that a file which is actually called IDEfix is in there. And the top of your Startup-Sequence will probably look something like this:-
; $ver: Startup-Sequence_HardDrive 45.1 (25.11.00)
; Startup-Sequence for hard drive systems
If Exists C:IDEFix
C:IDEFix
EndIf
C:setpatch QUIET
C:Version >Nil
C:AddBuffers >Nil DF0: 15
Good luck! :)
.
-
Ha, FindDevice doesn't detect any device other than the Microdrive :( I'm testing other combinations and settings now. I want to test it with a true IDE boot drive thoroughly, because I still suspect the CF adapter might be the culprit.