Looking for a patched scsi.device for large IDE drives

[adrian82]

Hi,

I have equipped my Amiga 1200 with a 160GB IDE drive which I primarily intent to use with Linux but also AmigaOS 3.9. I am using AmigaOS 3.9 with BB2. For using the full capacity of the hard disk, I'd still need to patch my scsi.device with this bug fix [1]. I have tried to do that myself, but I found it too much of a hassle.

Could anyone possibly email me an appropriately patched scsi.device which I could use on my A1200?

Cheers,

Adrian

> [1] http://de4.aminet.net/driver/media/SCSI4345p.readme

[Lurch]

http://lilliput.amiga-projects.net/start.htm has boing bag 3 and 4 can get it from there. :-)

[LaserBack]

Hi,

I have equipped my Amiga 1200 with a 160GB IDE drive which I primarily intent to use with Linux but also AmigaOS 3.9. I am using AmigaOS 3.9 with BB2. For using the full capacity of the hard disk, I'd still need to patch my scsi.device with this bug fix [1]. I have tried to do that myself, but I found it too much of a hassle.

Could anyone possibly email me an appropriately patched scsi.device which I could use on my A1200?

Cheers,

Adrian

> [1] http://de4.aminet.net/driver/media/SCSI4345p.readme

for larger hardrives you don't need any patched scsi.device if you use PFS3 direct scsi version (pfs3ds)
you can get PFS3 free on aminet
I have a 80gb hardisk connected on my A1200 using the normal scsi device in rom ( no patch no reboot)
however the first partition must be minor than 2gb...otherwise the hardisk will not boot
in my case I have 2 partitions workbench 2gb and work 76 gb

[mfilos]

I was under the impression that PFS3ds supports at best 8GB HD up to Kickstart 3.1.
If it works for you then what can I say Gz \o/

[Lurch]

PFS3AIO works great, although I had to switch back to SFS with my FastATA to get the drive to talk to the FastATA controller at full speed.

[LaserBack]

I was under the impression that PFS3ds supports at best 8GB HD up to Kickstart 3.1.
If it works for you then what can I say Gz \o/

it works up to 8gb if you don't have installed NSD patch...who  patch scsi.device on the fly
NSD patch is needed to the 2nd partition to be mounted correctly out of 8gb area
in wb 3.1 or wb3.0 you need to install it adding NSDpatch in the startup-sequence....
in OS3.9 NSDpatch  is included is loaded automatically via setpatch
I like this because there is no need to install any new scsi.device who forces the computer to reboot

[mfilos]

True... but if you burn a custom ROM then no reboot is needed and you also put some nice and newest modules

[Thomas]

Oh dear, where does all the mud come from you are trying to publish here?

Fact is:

- the unpatched scsi.device uses CHS addressing scheme on the hardware side
- through HD_SCSICMD (Direct-SCSI) it allows to access the entire size as reported by the drive through CHS.
- the official limit for CHS is 16384 cylinders, 16 heads and 63 sectors which results in a capacity of 7.8 GiB
- only some (cheap) CF cards reports their true size in CHS and thus allow more than 7.8 GiB to be accessed.

So no matter how large the drive is, if it follows ATA specs, with unpatched scsi.device you only get 7.8 GiB.

To go above 128 GiB you need not only LBA addressing but even 48bit LBA addressing. This is not available without a patch.

Talking about NSDPatch, this does not give you any benefit in any case. If you don't patch scsi.device, it gives you access to 7.8 GiB which can be achieved easier with a proper file system. And if you do patch scsi.device, it is already NSD-compliant and you don't need NSDPatch at all.

[mfilos]

Although I was rather certain... I can never learn enough from Thomas

[LaserBack]

btw,

 I was wrong about what I said that pfs3ds needs NSD patch...it doesn't need it...just tested it removing the NSD patch config file in devs
PFS3ds  works perfect without NSD patch and support big partitions...tested up to 76 gb with the standart scsi.device v39 in rom
who needs NSD patch to work with big partitions is fastfilesystem v45

however seems the NSD patch is needed to make HDtoolbox works correctly...otherwise HDtoolbox can'tt recognize the drive correctly or you can't set the correct drive parametrs when the drive is virgin or unformatted
I remember I installed NSDpatch + and scsi.device v43 when I purchase the 80gb hardisk
after you set the drive and you did the PFS3 partitions in hdtoolbox...you can remove those patches safety...there are not needed anymore

[LaserBack]

PFS3AIO works great, although I had to switch back to SFS with my FastATA to get the drive to talk to the FastATA controller at full speed.

I just tested this version...is a version done by Toni- winuae author
it doesn't support big partitions without a new scsi.device
seems is hack or patch based on the PFS3 common version but no based on the direct scsi version

[LaserBack]

True... but if you burn a custom ROM then no reboot is needed and you also put some nice and newest modules

yep you can do your own romset with new modules..but you need a rom-burner (I haven't one)
anyways there aren't interesting modules for me unless the new ram-handler and the new trackdisk.device
I did a custom rom for winuae replacing only those 2 modules

[mfilos]

I just tested this version...is a version done by Toni- winuae author
it doesn't support big partitions without a new scsi.device
seems is hack or patch based on the PFS3 common version but no based on the direct scsi version

All-In-One means that both versions (PFS3 and PFS3ds) are merged into one version. Also yesterday Toni release a Romable version of his PFS3 handler.
You don't need an EPROM burner if you can make the ROM with Remus and then ask the IC company that provides you with the 27C800 to burn the image into the ROM before sending (They's only ask if you want it burned ByteSwapped or not).

Also... imho, the most valuable modules for making a custom ROM are:
- Icon.library
- SCSI.device
- Workbench.library

Trackdisk.device can be easily replaced just by an AntiClick program that requires no reboot

Also I can't understand how your HD works just fine without a patched scsi.device.
Scsi.device of Kick 3.1 is 40.5 alas your 39 version must be Kick 3.0.
Without a patched scsi.device you shouldn't have had more than 7.8GB as Thomas said whatever FS you'd be using.

As a referece, I'm pasting some info based on Thomas that I found in the past in Bloodwych's post for ClassicWB Big Hard Drive support:

Large drive support (>4GB) under Workbench 2.0/2.1/3.0/3.1 requires some limitations to be overcome in order to work successfully.

The two main problems are the hard drive controller, the “scsi.device”, and the actual native Fast File System (FFS). Both must use the same method to overcome the 4GB barrier; essentially you have to be sure the drive controller and the file system speak the same language or command set.

The three common command sets used in this tutorial are “NSD”, “TD64” and “Direct-SCSI/HD_SCSICMD”. If the hard drive controller and file system both support one or more of these, the 4GB barrier can be breached.

Here is a list of common controllers and file systems (Thomas et. al. 2009):
scsi.device V37/40: NSD -> no, TD64 -> no, SCSI -> yes, but only up to 7.8 GB.
scsi.device V43+: NSD -> yes, TD64 -> no, SCSI -> yes
scsi.device V116+ (IDEfix): NSD -> yes, TD64 -> yes, SCSI -> yes
cybppc.device (and most other Phase5 controllers): NSD -> no, TD64 -> yes, SCSI -> yes
FFS V40 and below: NSD -> no, TD64 -> no, SCSI -> no
FFS V43: NSD -> yes, TD64 -> no, SCSI -> no
FFS V44 (FFSTD64): NSD -> no, TD64 -> yes, SCSI -> yes
FFS V45 (OS 3.5 or 3.9): like V43
PFS: NSD -> no, TD64 -> yes, SCSI -> no
PFSds: NSD -> no, TD64 -> no, SCSI -> yes
SFS V1.84: NSD -> yes, TD64 -> yes, SCSI -> yes
SFS V1.279: NSD -> yes, TD64 -> yes, SCSI -> no

OS 3.5/3.9 overcome this limitation by replacing the “scsi.device” at boot and using a newer version of the Fast File System. The ClassicWB OS35/9 therefore has this support built in.

Other issues can arise from software such as defraggers and disk repair tools (eg Reorg and DiskSalv) not being able to work with partitions above 4GB due to lacking the necessary 64bit support.

This guide is for getting the original ClassicWB packs (and therefore Workbench 2.0/2.1/3.0/3.1) working with partitions beyond 4GB by essentially adding the support OS 3.5/3.9 already has.

[klapdeur]

you'll need a patched scs.device to reqonize the 160gb hdd fully,
normal scsi.device is limited to 128gb. !!!!

classic wb also has the patched scsi.devices for all amiga versions. you only have to copy it to devs: and use loadmodule devs:scsi.device before setpatch
and skip scsi.device from rom update
setpatch SKIPRROMMODULES ,scsi QUIET

[klapdeur]

you'll need a patched scs.device to reqonize the 160gb hdd fully,
normal scsi.device is limited to 128gb. !!!!

classic wb also has the patched scsi.devices for all amiga versions. you only have to copy it to devs: and use loadmodule devs:scsi.device before setpatch
and skip scsi.device from rom update
setpatch SKIPRROMMODULES ,scsi QUIET