| From: | Colin Wenzel |
| Date: | 28 Jan 2000 at 02:06:33 |
| Subject: | Re: A4000T SCSI-IDE trouble under WB3.5 |
From: Colin Wenzel <colstv@hotkey.net.au>
I have a unique problem that I hope someone here can help me with.
I have an A4000T, CyberStorm-III-060/50 128Mb RAM.
Very stable, with WB3.5 & BB1, no nasty patches or junk,
just ToolsDaemon & WB2Fast
There are 4 drives attached.
1x 2Gig U/W SCSI on the Cyberstorm, (DH0: + others)
2x 1Gig Normal SCSI on the internal SCSI bus. (Addr 0&1)
Plus a 4 speed SCSI CD Rom (Addr 2).
1x IDE Drive on internal IDE bus. (to a removable drive bay)
( The cyberstorm drive is always fine. )
Now here is the clencher.....
When under v3.1, I used the LoadV43Module() patches.
I had them setup as:
* LoadV43Module whatever.ide.strip*
* LoadV43Module whatever.scsi.strip REBOOT*
* Setpatch........ etc*
Everything worked fine...... Until I reversed the order of
the patches like this:
* LoadV43Module whatever.scsi.strip*
* LoadV43Module whatever.ide.strip REBOOT*
* Setpatch........ etc*
On HDToolbox, the internal SCSI drives showed
up as being on the 2nd.scsi.device, instead of the scsi.device,
The IDE drive became the scsi.device.
This only occured *if* I had an IDE drive attached to the IDE bus.
If there was no drive on it, the internal SCSI used the scsi.device.
By reversing the order of the LoadV43Modules, the problem was fixed.
Then, no matter if an IDE drive was connected or not, it always
became the 2nd.scsi.device, the internal SCSI drives always
used the scsi.device.
I can live with that, but since I went over to WB3.5 & removed
the LoadV43Module stuff, the problem has re-surfaced,
IDE drives become the scsi.device & the SCSI drives are on
the 2nd.scsi.device.
There appears to be no way of reversing the patch order in
SetPatch, so i'm stuck.
If I have an IDE drive connected now, my CD0: comes up & says:
"*Cannot find scsi.device, unit 2*" (it's mounted in WBStartup)
Because it's now on: 2nd.scsi.device u2.
The mount file obviously specified: scsi.device u2.
As I use the IDE bus for backing up to a 13 gig drive, I cannot
guarantee that there is always a drive on the bus, plus,
having anything on the IDE extends the boot time, so I
generally don't have anything connected to it normally.
I have tried disabling the NSD patch, but that is of no use,
it still gets the devices arse-about...
Infact, the NSD part seems to play no part in this problem at all.
Is there a work around to keep the SCSI drives on the scsi.device ?
Can the SetPatch be modified to reverse the order of the patches ?
Can anyone suggest another fix or a workaround for 3.5 ?
H&P, are you listening........??
-------------------------------------
Colin Wenzel. Australia.
EMAIL: mailto:colstv@hotkey.net.au
URL: http://www.hotkey.net.au/~colstv/
ICQ: 17608330
MADE WITH 'AMIGA' 4000T With O.S 3.1
---------------------------------------
--------------------------- ONElist Sponsor ----------------------------
GET A NEXTCARD VISA, in 30 seconds. Get rates as low as 0.0 percent
Intro APR and no hidden fees. Apply NOW.
<a href=" http://clickme.onelist.com/ad/NextcardCreativeCL ">Click Here</a>
------------------------------------------------------------------------