Parttions not recognized/displayed in ClassicWB?

[koshman]

Hi,
i'm not sure this is a software problem, but most probably yes.

I recently bought the Yamaha SCSi=>IDE converter on Amibay for use on my A3000. The installation couldn't be simpler - I just connected it to the scsi cable from mobo then plugged into it a 20GB Seagate IDE drive and it was instantly recognized.

I prepared the drive under WinUAE - first I was just using FFS, but it was very problematic - data corruption, partitions turning to NDOS etc. Probably a problem with maxtransfer value or something (I used the defaullt value).

So in the end I did it properly - I partitioned the drive using SFS with help from a tutorial, set mask to 0x7ffffffe and maxtransfer to 0x1fe00. The partitions are - 3 x 250MB and the rest is divided into ~4GB chunks. One of the system partitions has ClassicWB ADVSP installed, another has OS 3.9 (the third one is a backup of ClassicWB).

The problem - in CWB only the 250MB system partitions mount, the rest is not recognized. In OS 3.9 everything works just fine. If I first boot to OS 3.9 and then reboot to CWB all partitions are normally accessible, but not when I cold boot to CWB.
I thought probably the rom update that loads with OS3.9 has something to do with it, but when I run "version scsi.device" from shell I get the same version in both OSs - 43.43, I think.
Any ideas? Thanks for your help in advance!

EDIT: I checked again and the CWB only shows scsi.device version 40.12 (I probably had the ROM update already loaded before). So I suppose this might be the reason. How do I update the scsi.device? Is it enough to update the file on the HDD? Thanks.

[Darrin]

What version of ClassicWB are you using?  As you have OS3.9 already, you'll want to use the ClassicWB 3.x for OS3.9:
http://classicwb.abime.net/classicweb/os3x.htm

Make sure you have your boing bags installed on the OS3.9 drive that you use to activate your ClassicWB installation.

You might want to consider PFS3 DS rather than SFS too.

[koshman]

Thanks for the suggestion, Darrin.

The thing is I want to stick with 3.1 because of speed - the A3000 has the stock 030/25MHz in it at the moment and that's not exactly fast (at least not for a system running in 1280x1024 through CV64/3D). I'm using the 3.9 on my 060 A1200.

Is there any way to use the rom update from 3.9 for CWB 3.1? Like start booting into 3.9, but after the initial restart switch to 3.1, that would be great

If there's no way I'll just use 3.9, I'll probably upgrade the A3000 eventually anyway - waiting for something like Warp Engine 3040 to appear on Amibay...

[Thomas]

Download these:

http://aminet.net/package/util/boot/BlizKick
http://aminet.net/package/util/boot/LoadModule

and unpack them to RAM.

Use romupdatesplit to extract the scsi.device for your Amiga model from the AmigaOS ROM Update file of OS 3.9. Read the readme file to find out which one you need to use. Do not use the wrong one or your Amiga won't boot any more.

Copy scsi.device to Devs and LoadModule to C of your 3.1 partition. Add this as the very first line to s/startup-sequence:

loadmodule devs:scsi.device

[koshman]

Thank you very much, Thomas! Worked like a charm