V 1.72 cd.device for Atapi CD-Drives on A1200

[pheald]

I've recently bought an Amiga 1200 to relive my childhood, and sadly the frustration I'm feeling is pretty accurate!

I've managed to hook it up to a nice new hard disk and use 3.5" cables and so on and so forth, but the only atapi driver I can find that has worked so far has been the Atapi PnP package "V 1.72 cd.device for Atapi CD-Drives on A1200" on Aminet... it gives me a cd.device that I can use to mount my cd and all goes well... IDEFix seemed to do an okay job, but it crashed a number of times, but I'm sure I could work with that...

I'm only using an HDD and a CDROM, so I don't need the fancy 4 port switching facilities of IDEFix...

But here's my problem. If I'm going to pay for IDEFIx I want it to work perfectly (it seems a little expensive for software that can kill my machine from time to time). What I would really like is a registered version of the package I'm using, but I have written to the address in the readme, and strangely enough, his address from 1997 is no longer valid... go figure... does anyone know if this package has now been released into the public domain, and if so, where I can get it? If not, does anyone know of any other package (specifically, some form of .device file) that I can place in my DEVS: folder which will allow me to get my cd drive up and running?

I'm using OS3.9 which I got thinking it had CD funcionality, but alas, unless I'm doing something majorly wrong, it would appear not. (I tried accessing both unit 0 and unit 1 of scsi.device and didn't get very far).

Please help me out if you know what I need to do. This is driving me crazy, and I'm beginning to wish I'd stuck with my happy little PC.

Regards,

Paul

[adolescent]

OS3.9 contains an update for scsi.device.  You need to make sure that IDEFix is uninstalled (mainly no IDEFix file in C:)    otherwise the startup-sequence skips the ROM update.  Other than that it should work as scsi.device, and unit 1.  

[pheald]

What part of the startup sequence updates the Rom?

[adolescent]

It's in SETPATCH.  You'll notice that if IDEFix is found it runs something like SETPATCH SKIPROMUPDATES "scsi.device".

[amigagr]

remove all the parts of idefix from amiga you don't need it with this configuration, all you need is the file CacheCDFS in L directory and the use of the native scsi.device of os3.9
if your cd works somehow insert the os3,9 cd in and run the install, then choose to create a new cdrom driver, but before this i'll say it again:remove all the parts of idefix from amiga.

-edit-
i hope that you have set the hard disk as master and the cdrom as slave.

[pheald]

Okay... Erm... AGH!

So my understanding is this... the scsi.device that's built into my kickstart ROM won't do the job, but OS3.9 runs a command called Setpatch which will patch the device and all should work...

well, if I boot with no startup-sequence and do

>version scsi.device
I get version 40.something

then I run the setpatch and it gives me a long list of things it's checking (including scsi.device) and then it tells me no ROM updates were done. If I then do the version command again,  it gives me the same version number. Am I missing something fundamental here?

Yes, I have the HDD set as master and the CD as slave. If I use atapi.device or cd.device (I think they're both part of IDEfix or the package I mentioned before (the Atapipnp) then I get the device listed, but both with the nag screens that I want to avoid... if I use scsi.device then it can't find the drive. (presumably because the scsi.device that's built into my machine is useless)...

What gives with the setpatch thing?

Thanks for all your help by the way.

[Castellen]

You probably want to check setpatch has actually applied the ROM updates.

To do this, use the version command:
11.System:> version
Kickstart 45.57, Workbench 45.3

11.System:> version scsi.device
scsi.device 43.43

This is with OS3.9+BoingBag2 updates, but OS3.9 kickstart should still be version 45.xx

If Kickstart is showing up as ver 40.xx it suggests the ROM update is not being applied for some reason.
You do have OS3.1 in ROM (40.xx) and not 3.0 (39.xx), right?

Once you have the ROM update being applied correctly, SCSI Inquire is an invaluable tool for fault finding SCSI & IDE device connectivity.  If you can't see the CDROM using SCSI Inquire, then the system isn't going to be able to mount it.

The info used from SCSI Inquire can be used to set up your mountfile Devs:DOSdrivers/CD0
It most likely will be device=scsi.device unit=1


Edit: In fear of stating the obvious, you need the CDROM drive to be working to install OS3.9 to install the patch to make the CDROM work.  A bit chicken & egg....
The IDEfix demo from Aminet will get you that far though.

[pheald]

Yeah, I have the 3.1 roms... I can run the CD drive long enough to install... but when I do the setpatch, the report comes back (after a long list) that no rom updates were installed... I notice that next to scsi.device the version number it is "checking" is 100.something...

I'm clearly totally incompetent... I reinstalled workbench over my installation. As I say, I can get the computer to detect the CD drive through shareware devices (cd.device, atapi.device) but these devices are crippled... My kickstart chips are version 40.68.

I've not applied the boingboing updates... Guess I'll try that. Thanks again.

[adolescent]

What version is the SETPATCH?  Check it compared to the one on the OS3.9 CD to make sure it got copied over during the install.  Normally, just running SETPATCH on a cold booted system should reboot the system.

[pheald]

Setpatch v44.17

Tried to download the boingbag updates but I can't locate them on the amiga.com site... any ideas where they're available?

[adolescent]

http://os.amigaworld.de has them.

[amigagr]

check if in the DEVS directory is the file AmigaOS ROM Update.
all the updates/patches that installed from setpatch they are in this file. in the startup-sequence you must have this: ''C:SetPatch Quiet'' to be capable the setpatch install all the updates. the boingbags is a later option/improvment, you don't need them in the first place to install the os correctly. of course it sould be wised to install them later.

[Castellen]

Yep, shouldn't need the BoingBag updates at this stage, leave them for now.

During the install, you would have been required to create an emergency disk and reboot, thus booting from the emergency disk.

The idea is that when you boot from the emergency disk, it runs OS3.9 setpatch which then applies the ROM update (all from the floppy disk).
You should then see the computer do a soft reset by itself in order to actually run the new ROM code, so now it'll be using the updated scsi.device, etc, which means the CDROM drive will be operational, no IDEfix required.
The system then proceeds to boot WB from the OS3.9 CD once the drive has been mounted.

Not sure why it's not playing ball for you, it's generally not caused many issues on the countless OS3.9 machines I've set up over the last few years.

Try this:
1. Boot from emergency disk
2. Wait until it loads the new ROM image then reboots itself (takes about 20-30 seconds)
3. Hold down both mouse buttons, boot with no startup
4. Providing "version" is on the emergency disk, you'll be able to check the kickstart version is 45.xx
5. Entering "mount CD0:" should immediately mount the CDROM, so you should be able to then browse files, etc, on it using the CLI

If all works fine from the emergency disk, it suggests something wrong with the new OS3.9 install on the hard drive.