Setting up SFS on a real hd with winuae??

[dougal]

Thanks Thomas. Sorry for not describing the problem enough. I'll have another attempt at this when i get home.

I did unpack the files you said in your guide to download using WinRAR on the PC so maybe like you said the integrity might have become damaged although i never had problems before unpacking using the PC as PC is much much faster.

Will try again and post the results.

Cheers and honestly i really do appreciate your help

[dougal]

Ok tried again. I managed to have the boot disk (HD0) and HD1 and HD2 as SFS. The rest would not be seen on WB so i set them as FFS and they work.

All good so far. Just one slight problem.

Tried copying some WhdLoad ready games to the 3rd SFS partition but when i click them rather then loading they get stuck on the WhdLoad screen where it says the credits of the WHDinstaller etc..     Tried copying games to an FFS partition and they work fine.

The 3rd SFS partition in questions is less than 1.5GB

Edit: Instead of a Format i gave it a Quick Format as the initial format. Is that bad? I am now trying a full format.

[dougal]

SFS is all a mess i think... Even now stuff in the system partion is saying HD0 has a blockid error in block xxxxx expected blockid 0x424e4443, but the block says it is blockid 0x6a727778,

[dougal]

I gave up... Deleted all the partitions and created them again with FFS

[mechy]

SFS is all a mess i think... Even now stuff in the system partion is saying HD0 has a blockid error in block xxxxx expected blockid 0x424e4443, but the block says it is blockid 0x6a727778,

SFS works fine and i've been using it for over 10 years. People that say stuff like this usually don't bother to read or understand the docs or set it up right.

It sounds more like you made the mess of your sfs install

theres some good benefits to SFS, like speed,long filenames,tolerance for large drives etc.

mech

[Thomas]

The rest would not be seen on WB so i set them as FFS and they work.

No, they definitely do not work correctly, although it seems so. FFS cannot access outside of the first 4GB of the harddrive. But it does not care, it simply ignores the overflow which happens when calculating the byte offset to the place where to access. This means instead of accessing the area which you reserved for the FFS partitions, it writes to an area inside the first 4GB of the harddrive which belongs to a completely different partition.

Edit: Instead of a Format i gave it a Quick Format as the initial format. Is that bad? I am now trying a full format.

Quick format is the only working way to correctly format a partition outside of the first 4GB. The Format program has the same problem as FFS. If you fully format a partition outside the first 4GB of the harddrive, it will destroy another partition inside the first 4GB.

SFS is all a mess i think... Even now stuff in the system partion is saying HD0 has a blockid error in block xxxxx expected blockid 0x424e4443, but the block says it is blockid 0x6a727778,

That's what happens when you put a FFS partition outside the first 4GB: it overwrites data of another partition. This is not a SFS problem, this problem is caused by your improper use of FFS.

[Piru]

SFS is all a mess i think... Even now stuff in the system partion is saying HD0 has a blockid error in block xxxxx expected blockid 0x424e4443, but the block says it is blockid 0x6a727778,

I warned you about this. FFS only appears to work but happily trashes innocent data.

[dougal]

I warned you about this. FFS only appears to work but happily trashes innocent data.

Thanks for the help. Same to Thomas.

I just couldnt get it, so i am now using FFS without problems. Shame is that i can only get 4GB (out of a 20GB hard drive) but 4GB is more than enough i guess.

[mfilos]

Shame is that i can only get 4GB (out of a 20GB hard drive) but 4GB is more than enough i guess.

You can get just fine the rest of the drive if you use LoadModule (http://aminet.net/package/util/boot/LoadModule) with a newer scsi.device.

So if you put LoadModule in C: and the new scsi.device for example in folder Devs:
...you only need to put as first line of your Startup-Sequence the command:

Code: [Select]

C:LoadModule Devs:scsi.device
(LoadModule command will load the new scsi.device on power up and then reboot! After that and once your system completes it's boot proccess you can enjoy your full HD capacity. Just make sure that the first partition is always under the 4GB barrier.)

Bloodwych's awesome ClassicWB packs (http://classicwb.abime.net/) once installed have some new scsi.device version under "DH0:MyFiles/LargeHD/128GB_Support/" on folders "SCSI_IDE_43.23" or "SCSI_IDE_43.24".

[Thomas]

Why didn't you stay with SFS for all partitions? Those partitions which are shown by SFS are safe to use and those which cross the 4GB boundary are not shown. With FFS you never know.

And why didn't you take PFS3 into account at all? Now that it's free, PFS3 is the best choice for 68k Amigas. It has similar features like SFS and is even faster. And with the PFS3ds version you can increase your space limit to 8GB (all that HDToolbox shows without a new scsi.device).

[zipper]

Gosh I'm happy having used Idefix for years to avoid all this crap...