Amiga HDD Partition just became NDOS

[Colani1200]

taunusand wrote:
Maybe I don't read this right, but..

Install SFS in the RDB of the drive??

I think I have missed something!! :-?

http://en.wikipedia.org/wiki/Amiga_Rigid_Disk_Block

HDtoolbox has an option to install a filesystem in the RDB. Just read the guide that comes with SFS package.

[Colani1200]

I also have a question regarding this procedure. ;-)
When using IDEfix, do I also have to use the CD filesystem that is included in the package or can I choose a different one (such as AmiCDFS)?

[taunusand]

I thought HDToolbox always did this.
SFS = Standard File System ??

[motorollin]

Colani1200 wrote:
I also have a question regarding this procedure. ;-)
When using IDEfix, do I also have to use the CD filesystem that is included in the package or can I choose a different one (such as AmiCDFS)?

You can use any CDFS you want. The IDEfix patch will still apply to scsi.device and fix >4GB support.

--
moto

[motorollin]

taunusand wrote:
I thought HDToolbox always did this.
SFS = Standard File System ??

No, SFS = SmartFileSystem. It's not installed as standard. If you don't install it in the RDB then the Amiga won't be able to see the SFS partitions.

--
moto

[Everblue]

I have done exactly as stated below.

I have created an 8gig partition using HDInstTools, and check4gb  reports its size correctly. Theproblem is that when I double click the partition's icon in Workbench itstates that there are 3134 megs free, when there should be 8g. What am I missing?

Thanks

E;Blue

Thomas wrote:

Still one important step is missing:

0. Install SFS in the RDB of the drive
1. I create a small SFS partition for Workbench 3.1 (100megs)
2. Install Workbench 3.1
3. Install IDEFIX
3a. edit s:startup-sequence and replace c:idefix by c:loadide reset
4. Create SFS partitions of any size, including >4gib
5. Run check4gb to ensure everything is ok
6. Fill them with goodies

If you leave out step 3a, IDEfix does nothing for you.

Note that IDEfix is shareware which nags with registration requesters. There is a free solution, too, but it is more complicated to install. The files needed are:

http://os.amigaworld.de/index.php?lang=en&page=37
http://aminet.net/package/util/sys/patchstrip
http://aminet.net/package/disk/misc/FFS43.19_patch
http://aminet.net/package/util/boot/LoadModule

Bye,
Thomas

[taunusand]

Oh, I think I have made a big mistake then :roll:
Thanks for the info!

[Piru]

@Everblue

Theproblem is that when I double click the partition's icon in Workbench itstates that there are 3134 megs free, when there should be 8g. What am I missing?

Workbench 3.1 doesn't understand partitions larger than 4GB. Basically when the math overflows 32bit it gets total size and free size wrong. In workbench use this is no problem, other than that the free storage figures are "off".

Sometimes some "smart" applications (often game HDD installers) perform storage availability checks and refuse to write files to disk if they think the disk is full. This happens when the free storage gets close to x * 4GB + small_amount. If this happens, just write some dummy file to the disk so that the free size (as reported by workbench 3.1 for example) wraps to <4GB again. Once the installer has completed you can delete the dummy file.

[Everblue]

So, if I try to copy copy filies in the HDD, once it goes over the 3gigs, will it give me an error that the HDD is full, or it will copy everything regardless?

Thanks!

[Piru]

@Everblue

So, if I try to copy copy filies in the HDD, once it goes over the 3gigs, will it give me an error that the HDD is full, or it will copy everything regardless?

It depends on the application. Most (including Workbench and Copy CLI-command) do not perform any "is the disk becoming full?" -checks but rather trust the filesystem to report an error once full. As such they will work just fine with any filesystem size (even though Workbench reports the filesystem total and free capacity wrong).

If the application does perform these checks, it usually depends on the age: Older apps mostly fail in this fashion (back then no one expected HDDs sizes to grow over 4GB...). New applications should not have this problem.

Anyhow, if you do get the problem you can use Workbench or Copy command to "workaround" the issue as described in the earlier post.