Setpatch... why isn't it setting any patches.

[pheald]

Hello all...

I just don't get what I'm doing wrong... I have AmigaOS3.9 installed in an A1200 with an accelerator card, and 32MB of extended ram.

For a while now I have been using ASIM_atapi.device to control my CD drive which works well, but I have recently discovered that running that device kills my network card connection (this took me three weeks and three network cards to figure out... as soon as I mount the CD, the network connection drops and won't come back. I tried a new file handler but to avail.

So, what I want to do is use the nice scsi.device to control my cd drive and hopefully have BOTH CD and TCP going at the same time...

I know that to do this, the scsi.device that's built into my Amiga simply won't do the job, however I also know that the lovely "setpatch" is supposed to reroute ROM calls to a patched file which will allow me to then access the cd drive (let me know if any of this understanding is wrong).

So here's the deal. If I boot my machine and type:

version scsi.device

I get version 40.12 (I presume that's what's built into KS3.1)

Then I type setpatch... junk goes flying past my eyes, of which the last line is "no updates applied". If I re-execute the version, I get the same version number...

What am I doing wrong? I'm not typing any exclusions or anything. It should update me to something in the 44s, right?

Any ideas? I don't mind how I sort this one out... either by getting setpatch to work or by getting ASIMCD to co-exist with my network driver (I can't find anything about those two programs conflicting anywhere on any of the Amiga help forums... maybe it's just me)

As always, all help appreciated.

Paul.

[amigagr]

at first check in Devs: if there is the file Amigaos rom update. if you have not install so far the updates of os3.9 called boingbags install them on the workbench3.9 you already have and retry. 3.9 bb1&2

i use cachecdfs and scsi.device for cd drive for years and it works ok.

[pheald]

Yup, I have that file in my DEVS: Maybe my copy of it has corrupted. It's 129,956 bytes long, and it has "-" before and after the filename... is that right? (I just renamed it without them and it didn't seem to make a difference).

[amigagr]

it is the original rom update from os3.9 cd.
download the boingbag1 & 2 and install them both.

[Boot_WB]

Since you're running OS3.9 setpatch should already be at the top of your startup sequence - I've just checked the version of scsi.device on mine, and it's coming up as 119.16, but then I use the "SKIPROMUPDATES scsi.device" option with setpatch.

40.12 is probably the version from setpatch - since it has already run once (at startup), running it again from the command line will not install any additional patches.

If you want to see what setpatch is patching at startup remove the QUIET switch from after setpatch in the startup sequence - the resulting output is slow enough (even on 060) that you will see the summary of what has been patched at the end of the spiel.

btw - I assume it is a pcmcia lan card?

[amigagr]

@Boot_WB: i think that yours scsi version is the one of idefix and this has nothing to do with the standard rom updates of 3.9. i use too a pcmcia netcard and the latest scsi.device and  subway usb and blizard scsikit and don't have any problems with any of the hardware.

[Boot_WB]

@amije

Yes, it is the idefix one, that's why I need to use the SKIPPROMUPDATES option with setpatch.  

[pheald]

Got it... Finally... Installed BB2 which did a bit of a botched install, but I managed to get the files I needed and now the setpatch installs and reboots, after that, it all works perfectly. I can surf and use CDs... It's everything I ever dreamed of...  ;-)

Thanks for your help guys (and gals?)