Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: jedcooper on October 28, 2009, 10:47:36 PM
-
hi there!
as topic i got this problem... every feature else runs fine.
is this a known issue? any workarounds?
i'm using SFS 1.277 with IDE drive and 5 partitions just fine, even SFSformat works, as i tried it just minutes ago.
the boot rom is 4.13, even with patch in SYS:Expansion, without or any bootdisks or without startup-sequence doesn't work.
help is urgently needed, as i want to get the fastest outta this drive..
thanks in advance
regards
jc
-
Have you already checked these ?
With these settings it should work:
Mask = 0x7ffffffe
MaxTransfer = 0x1fe00
Blocksize = 512
x303 :D :D :D
-
uhm not yet, where? in HDToolBox?
with FFS it's working with the default... and the manual of the card also says 0xfffffffe
-
uhm not yet, where? in HDToolBox?
Yep, in HDToolBox. For any further information about mask & maxtransfer settings, check the SFS guide.
x303 :D :D :D
-
aaaah great, yes i'll do that, and notice if it works!
-
What happens if you use WB quick format on the SFS partition instead of SFSFormat?
Have you setup the partition with SFS/01 or SFS/02 ? What is the exact software failure (ending 0003 or 0004)?
Thanks.
-
WB quickformat does the same... WB fullformat after initializing the disk...
error codes are:
WB-standardformat:
8000 0003 0704Fxxx
WB-quickformat:
8000 0004 07051280
sfsformat:
8000 0003 07051280
07051280 is my SDH0: (SCSI-partition)
0704F0F8 DF0: :confused::confused:
-
You shouldn't use WB Standard full format.
Does the partitions have the have the filesystem Identifier 0x53465300 or 0x53465302
BTW: Latest SFS is 1.279 - see here:
http://www.strohmayer.org/
-
err sorry, i tried both SFS/00 and SFS/02 of course with the correct mask.
i'm reading through the SFS_OLD.guide at the moment and maybe the mask for accessing RAM is the critical point.
-
Have you already checked these ?
With these settings it should work:
Mask = 0x7ffffffe
MaxTransfer = 0x1fe00
Blocksize = 512
x303 :D :D :D
YEAH MAN!!!! that worked it out!!! :uzi:GURU
don't know why, but i could format the drive and then i fiddled around with mask and maxtransfer... finally i got both set to 0x7FFFFFFF what doesn't make problems (yet)
i even can SFSformat again with my new settings - strange!
now with the mask set to chip/24-bit ram only the drive is really slow and i also got a guru once at unlzx, so i thinmk it can handle the NEW full mask alright.
as wih the maxtransfer i'm not sure, but hostadapter manual says 0x7FFFFFFF. SFS says the same, maxtransfer and mask is for fixing bad devices... so now you fixed it :D
with ExpertPrep from GVP i checked also the automatic settings which are DMA 0xFFFFFFFE and MaxT 0x7FFFFFFF, quite the same i've set it to. SFS.guide says always try hard to reach 0xFFFFFFFF for DMA/Mask
let's see if it runs stable the next few days...
would MaxTransfer give a speed drain if set too low??
alright again thank you all guys! especially the crack from the netherlands!
settings now:
Mask = 0x7FFFFFFF
MaxTransfer = 0x7FFFFFFF
Blocksize = 512
best regards
jc
-
What happens if you use WB quick format on the SFS partition instead of SFSFormat?
Have you setup the partition with SFS/01 or SFS/02 ? What is the exact software failure (ending 0003 or 0004)?
Thanks.
What's the difference between SFS/01 and SFS/02? I have an 80GB hard drive with three partitions. Tehe boot partition is FFS, DH1: is SFS/01 and DH2 is SFS/02. SFSCheck Dh1: completes without error BUT SFSCheck DH2: returns a "Checksum failure".
Thanks.
Weed.
PS: appologies for hijacking thread.
-
appologies for hijacking thread.
You should be ashamed of yourself. :whack:
BUT SFSCheck DH2: returns a "Checksum failure".
Try SFS/0 instead...
x303 :D :D :D
-
You should be ashamed of yourself. :whack:
Try SFS/0 instead...
x303 :D :D :D
Just trying that. SFS/0 seems to work without probelms. Is SFSCheck compatible with SFS/2 and hence is reporting a false error?
Weed
-
@Tumbleweed
As per the changes.txt file; dunno if it is only cornerning OS4.
Added a new format with large file support, to use it select DOSType 'SFS\2' (0x53465302) for the partitions.
WARNING: It's not compatible to the older SFS2 versions, nor to standard SFS partitions (DOSType 'SFS\0', 0x53465300) and therefore tools like SFSCheck, PartitionWizard, etc. don't work on such partitions and you can't use such a partition for booting from U-Boot/SLB!
-
doctorq thanks very much.
So SFSCheck doesn't work with SFS/2. I should have read the .docs more closely. This has been annoying me for ages, I have reinstalled the HD umpteen times to try and get rid of the checksum error. Its all working ok as I type, I'm copying a bunch of cover CD's to the drive to test it and there haven't been any issues so far.
Weed