workbench3.1 and SFS - incorrect partition sizes

[rvo_nl]

Hi there, its me again!

Made a lot of progress since I started a month ago:

- Found the correct way of installing OS3.9, both Boing Bags, CyberGraphX, PowerUP, WarpOS and Warp3D
- Installed internet and filesharing
- Enjoyed OS3.9 for a while, then decided it was time to repartition and install SFS. I've done this, and the following is the way my drive is now partitioned (using HDToolbox of OS3.9):

HD0/System: 100MB, FFS Workbench 3.1
MAC: 2.5GB, FFS
PC: 1.4GB, MSH\00
------------------------------------4gb barrier
SWAP: 1GB (I wont be using this, its just to be safe)
HD1/OS3.9: 10GB, SFS2, AmigaOS3.9
HD2/OS4: 15GB, SFS2, AmigaOS4.0
HD3/Games: 50GB, SFS2, Games
HD4/Data: 30GB, SFS2, Data
HD5/Spare: ??GB, SFS2, Backup

WB3.1 will be my boot partition. I will write a little script that allows me to select one of the 3 OS's to boot from. But for this to work, all partitions must be correctly mounted under Workbench3.1. And that's where I'm stuck now.

- I have an IDE-Fix express, so c:IDEfix is loaded in startup-sequence. This way scsi.device is patched.
- I'm using SFS for all partitions >4GB, so no reason to patch the filesystem
- I can only make the other (os3.9-formatted) partitions to show up using the diskchange command
- The problem is, hd2 for example shows up as a 3GB drive, while it really is 15GB in size.
- Also, HDToolbox does not display the correct size for the drive (strangely enough: 10GB in total ?)
- Oh, and when I start it, it asks me to save changes to disk (RDB) but Im afraid to lose everything when I do that.
- Check4gb displays all partitions (except those that are not on auto-mount) correctly. scsi.device v119.4, sfs2 v1.279, correct sizes.
- I think I've read all forum threads on this matter but the question remains:

How do I get (all) partitions to show up in the correct sizes under Workbench 3.1?

[rvo_nl]

Someone might have a better suggestion, but...
 
For 3.1 to properly recognize a HD larger than 4gb, you'll need to add an OS3.5/3.9 type patch in your startup-sequence called 'New Style Device' or NSDPatch. Then you have to edit the NSDPatch.config file to reflect your hardware and SCSI or IDE setup. Here's the linky:
 
http://aminet.net/package/disk/misc/NSDPatch43_20

thanks, is this patching the filesystem, scsi.device, or something else?

[rvo_nl]

Complete nonsense. NSDPatch does nothing like this

thanks, thats what I thought.
 

The remainder of 15 / 4 is 3. Normal behaviour of old programs. There is nothing you can do except to use new programs.

I dont understand what you mean by this. Im talking about workbench here. Surely its not safe to write to a partition which size is incorrectly shown?

[rvo_nl]

Hm, I don't understand you went back to wb3.1 in the first place.
Secondly, I don't think SFS2 partitions work under OS3.x. :confused:
 
x303

I didnt go back to 3.1, I just wanted a fast backup partition from which I can load either OS3.9 or OS4.0, which are both located after and sized bigger than 4GB.

[rvo_nl]

okay, so, just to summarize what you've said: mounting the partitions manually with diskchange is expected and normal behaviour, and the incorrect filesize can be ignored when using workbench3.1. I do not need other patches and can safely write files to all partitions. I just shouldnt touch hdtoolbox in wb3.1 and I shouldnt format anything with it either. correct?

[rvo_nl]

Thomas, again I am very thankful for your replies. Like save2600 said, your answers really save me lots of time. But most of all, I'm learning a lot from them. Hope I can return the favor to other people some day.
 
edit: wanted to add one thing, its only the free space count that seems to be incorrect. The '% full' and 'in use' indication of the partition seem to work alright. I tried filling it up with some big files, and after some copies it says:
 
21% full, 4MB free, 2160MB in use
 
when I copied over another 80MB it says:
 
22% full, 96MB free, 2240MB in use
 
I will continue to fill up 2 partitions after the first 4GB and in case my HD0 gets destroyed will report back here

edit 2: no wait, its only the percentage indicator that works.