CD ROM Drivers With OS3.9

roberthazelby · 29 September 2005, 22:05

Evening all,

After encountering problems with another drive I last night plonked a new one in my machine.

I loaded up the HDToolbox package that comes with the A4000 (I have an A1200, but a friend did me a copy), partitioned my drive, and installed WB3.0.

With 3.0 installed I then installed EIDE'99 and Alleogro CDFS. With the CDROM drivers installed, I then installed OS3.9 from CD.

Anyway, the problem is that even though I chose NOT to install the CDROM drivers from 3.9 they've messed up the drivers I already had up and running on there. Re-installing the drivers doesn't help.

I remember a year or so back I had to manually delete files, and possibly edit some scripts before re-installing the drivers, to get my CDROM working again. However, I can't for the life of me remember what I did.

Can anyone either let me know what I need to do to get the CDROM drive up and running again, or point me in the direction of some instructions.

Many thanks!

Rob

thomas · 30 September 2005, 09:34

Check Elbox' homepage to see if your drivers are recent. Register with Elbox to get the latest versions.

Check that 4xEIDE.driver is present in the C directory of your boot partition. Then edit s:startup-sequence and check if 4xEIDE.driver is called. If not, insert it immediately after SetPatch.

Now check that a DosDriver for your CD-ROM is in Devs:DosDrivers. It's usually called CD0 or CD1 or EMERGENCY_CD. If there are two of them, move the one which OS3.9 has added to Storage/DosDrivers.

Now load the remaining DosDriver into a text editor. Check the lines FileSystem=, Device= and Unit= to match your configuration. Filesystem should point to L:AlegroCDFS, device should be scsi.device. Unit depends on where the CD-ROM is connected to and what its jumper settings are: primary master: unit=0; primary slave: unit=1; secondary master: unit=2; secondary slave: unit=3.

Now check if AllegroCDFS is in the L directory.

If all is checked, reboot to see if it works now. If it still does not work (probably because you didn't need to change anything), change the SetPatch line in S:Startup-Sequence to read

SetPatch QUIET SKIPROMUPDATES "scsi.device"

After this change you have to switch off the Amiga because reset-proof resident modules are only changed on a cold start.

29 September 2005, 22:05	#1
roberthazelby Amiga user since 1990 Join Date: Sep 2005 Location: Bristol, England Age: 48 Posts: 364	OS3.9 Causing CD ROM Driver Probs Evening all, After encountering problems with another drive I last night plonked a new one in my machine. I loaded up the HDToolbox package that comes with the A4000 (I have an A1200, but a friend did me a copy), partitioned my drive, and installed WB3.0. With 3.0 installed I then installed EIDE'99 and Alleogro CDFS. With the CDROM drivers installed, I then installed OS3.9 from CD. Anyway, the problem is that even though I chose NOT to install the CDROM drivers from 3.9 they've messed up the drivers I already had up and running on there. Re-installing the drivers doesn't help. I remember a year or so back I had to manually delete files, and possibly edit some scripts before re-installing the drivers, to get my CDROM working again. However, I can't for the life of me remember what I did. Can anyone either let me know what I need to do to get the CDROM drive up and running again, or point me in the direction of some instructions. Many thanks! Rob Last edited by roberthazelby; 29 September 2005 at 22:57. Reason: New title gives better description of problem.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
OS3.9 & 3.1 Rom	blade002	MarketPlace	17	12 January 2018 22:38
Non Working CD ROM Drivers in OS3.9	roberthazelby	support.Hardware	8	08 October 2010 00:51
A1200 PCMCIA to SCSI CD ROM drivers needed	Amiga-Boy	Amiga scene	2	22 July 2010 12:40
A4000 CD Rom drivers	vertigo	support.Hardware	5	27 October 2008 07:09
CD-ROM Drivers For A600?	Fingerlickin_B	support.Hardware	2	19 March 2007 09:36

30 September 2005, 09:34	#2
thomas Registered User Join Date: Jan 2002 Location: Germany Posts: 6,985	Check Elbox' homepage to see if your drivers are recent. Register with Elbox to get the latest versions. Check that 4xEIDE.driver is present in the C directory of your boot partition. Then edit s:startup-sequence and check if 4xEIDE.driver is called. If not, insert it immediately after SetPatch. Now check that a DosDriver for your CD-ROM is in Devs:DosDrivers. It's usually called CD0 or CD1 or EMERGENCY_CD. If there are two of them, move the one which OS3.9 has added to Storage/DosDrivers. Now load the remaining DosDriver into a text editor. Check the lines FileSystem=, Device= and Unit= to match your configuration. Filesystem should point to L:AlegroCDFS, device should be scsi.device. Unit depends on where the CD-ROM is connected to and what its jumper settings are: primary master: unit=0; primary slave: unit=1; secondary master: unit=2; secondary slave: unit=3. Now check if AllegroCDFS is in the L directory. If all is checked, reboot to see if it works now. If it still does not work (probably because you didn't need to change anything), change the SetPatch line in S:Startup-Sequence to read SetPatch QUIET SKIPROMUPDATES "scsi.device" After this change you have to switch off the Amiga because reset-proof resident modules are only changed on a cold start.

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)