FAT95 word of warning...

[Echo]

Now unless I've set up the mountlist completely wrong - which I would assume either works or doesn't, there is a serious bug in FAT95.

For those who don't know, FAT95 is a filesystem for Amiga, compatible with Windows - and provides long filename / mixed case support. Most useful for zip disks and other magneto optical media.

I recently changed to FAT95 instead of Ami File Safe, and started doing my Work/Workbench backups to FAT95 formatted zip disks. This had the benefit of being able to pop them into my PC's IDE zip drive and copy over my whole configuration for use with WinUAE.

All was great until the time came when I needed to restore due to losing the hd contents. Smaller (about 100K or less) files were fine, but it corrupted almost every large file I had. Executables would no longer run, pictures and animations were garbled - total nightmare.

So by all means use it as a transfer method from PC to Amiga, but don't use it for critical backups

[thomas]

Originally posted by Echo
Smaller (about 100K or less) files were fine, but it corrupted almost every large file I had.

Change MaxTransfer to 64k (0x10000) or less.

[Echo]

Hmm, that's the cause?

This is my current mountlist:

/* ZIP Drive 0 mount file for FAT95 */

Device         = squirrelscsi.device
Unit           = 5
LowCyl         = 0
HighCyl        = 24575
Surfaces       = 1
Flags          = 0
Interleave     = 0
Reserved       = 2
StackSize      = 8192
BlocksPerTrack = 8
MaxTransfer    = 0x1ffff
Mask           = 0xffffffe
GlobVec        = -1
Buffers        = 200
FileSystem  = L:fat95
DosType     = 0x41465301
#

I'll give it a try on some test files, thanks

[Echo]

Nope, 0x10000 doesn't cure it I'm afraid. Frontier for example gives a "bad loadfile hunk" when copied to and restored from a FAT95 zip disk.

Could mask or dostype be the cause perhaps?

[Severin]

Originally posted by Echo
Nope, 0x10000 doesn't cure it I'm afraid. Frontier for example gives a "bad loadfile hunk" when copied to and restored from a FAT95 zip disk.

Could mask or dostype be the cause perhaps?

Yep, it's your dos type, it's AFS1 (read it as a hex code).