Desperate for help!

[Neil79]

Not sure if any of you have followed my issues with getting this CF card working in my Amiga 600, but here's the gist of it from FB

1)

Put in the new CF that was fully configured by a friend from here, didn't work, gave me that bloody HD0 error. ( not blaming friend ) So people said it was probably the fact that I was using a Kickstart that was not compatible with BIG hard drives. So I purchased a 3.1 Kickstart, and still no go.

2)

Followed both guides to install a CF using the correct file system, and finally I got it working and straight to the OS via the Amiga 600... However NOW I can't get any directory to open via WinUAE : In Dopus the drives are not seen unless I actually type DH1 - DH2: , then I can copy the files over fine. But after loading any of the directories I get this below

Device DH1 - or DH3 : ALERT : Wrong Block ID

- Restarting the Amiga, and all the files are gone! CAN SOMEONE PLEASE DO AN 8GB IMAGE for AN AMIGA 600 unaccelerated! - Thank you

[supaduper]

Run PFS doctor on the drive, that should correct that PFS3 filesystem error

[Neil79]

Originally Posted by supaduper

Run PFS doctor on the drive, that should correct that PFS3 filesystem error

Where is the PFS Doctor?

[Daedalus]

Oh dear Yeah, the 37.300 ROM will give you problems, but even the 3.1 ROM needs help over 4GB. What version of scsi.device are you using? Without updating that, accessing anything over 4GB wraps around and causes block errors, and writing to those blocks will overwrite the blocks at the start of your first partition instead. Normally you need to load the new scsi.device using the Loadmodule command, then reboot and all partitions will be fine.

[supaduper]

I am sure PFS3 aio is good for 8gb with no probs with standard scsi.device.
here is PFS doctor: http://aminet.net/search?query=pfs3+53

[Neil79]

Originally Posted by Daedalus

Oh dear Yeah, the 37.300 ROM will give you problems, but even the 3.1 ROM needs help over 4GB. What version of scsi.device are you using? Without updating that, accessing anything over 4GB wraps around and causes block errors, and writing to those blocks will overwrite the blocks at the start of your first partition instead. Normally you need to load the new scsi.device using the Loadmodule command, then reboot and all partitions will be fine.

Even if the partitions are set to about 3.2GB each?

[Zetr0]

@Neil79

Check your startup-sequence - ensure that "setpatch" is updating the ROM module(s) it should read something like

C:setpatch QUIET

[Daedalus]

Yes. The partition size is a matter for the filesystem (and PFS handles any size just fine), but low-level block access is a matter for the device driver, as it's at a lower level than the partitions. So for example, if PFS tries to read a block in your second partition at 4GB+10, the scsi.device driver will respond that that's ok, but will actually access block 0+10, which is in your first partition without any warning.

As supadupa says, if the filesystem supports "direct-scsi" mode, it can access up to nearly 8GB. But the problem still happens if you go above that limit, as can happen with 8GB cards, since the direct-scsi limit is actually ~7.87GB. So you need to leave the last ~250MB of an 8GB card unpartitioned just to be safe to use this method.

[Zetr0]

Originally Posted by Neil79

Even if the partitions are set to about 3.2GB each?

indeed - standard scsi.device is very limited - there is what I would describe as a hack that will give you 8GB support - but you are best to install PFS3 AIO and update your scsi.device - here is a great tutorial by our resident Fitzsteve!

[ Show youtube player ]

[Neil79]

Originally Posted by Zetr0

indeed - standard scsi.device is very limited - there is what I would describe as a hack that will give you 8GB support - but you are best to install PFS3 AIO and update your scsi.device - here is a great tutorial by our resident Fitzsteve!

[ Show youtube player ]

As you can see here, they are already PFS3

[Total Eclipse]

A 3.2GB Workbench partition????

I think I have mine at 30MB

[supaduper]

Like I said just run PFS Doctor

[Daedalus]

Also, bear in mind there are different versions of PFS3. To use 7.87GB, you need to use the PFS AIO version (AIO = all-in-one). That version supports 7.8GB without patching scsi.device, as does the Direct SCSI (DS) version of PFS. But the standard old version of PFS does not...

[Neil79]

Originally Posted by Total Eclipse

A 3.2GB Workbench partition????

I think I have mine at 30MB

Ignore that fella, I was testing out hard drive files for renames

Originally Posted by supaduper

Like I said just run PFS Doctor

Will try that later now - Ta

[Jope]

Originally Posted by Total Eclipse

A 3.2GB Workbench partition????

I think I have mine at 30MB

I have mine as large as the drive/compact flash card. Why fragment your free space by splitting your drives into many partitions..

[idrougge]

It's easier to backup your system partition if it isn't filled with games and utilities you tried out once.

[Neil79]

Still giving me grief, it might be the CF card. So I'm going to leave it now until late weekend, it's just stressing me out


Is there NO chance of someone uploading an 8GB image that I can just copy over to my CF and test? ( The EAB FTP? )

[fgh]

So your card now works as it should on the A600, but not in WinUAE?
If this is the case try to reconfigure WinUAE to match your real HW (A600, 68000, KS3.1)
I've seen this happen once with a non matching WinUAE config. (Cannot explain it though)

The first fault looks like what you get if using SFS on a 68000, could that have been the case?

As others have said you do not need to update scsi.device for 8GB cards with PFS3AiO (direct scsi).
The limit is 7,87GiB or 8.45GB, and I've never seen 8GB cards being even close to 8.45GB.

Kickstart 37.300 works well with large drives. I ran two of those with large SD cards before. (37.299 does not though)

[ReadOnlyCat]

Originally Posted by fgh

So your card now works as it should on the A600, but not in WinUAE?
If this is the case try to reconfigure WinUAE to match your real HW (A600, 68000, KS3.1)
I've seen this happen once with a non matching WinUAE config. (Cannot explain it though)

The first fault looks like what you get if using SFS on a 68000, could that have been the case?

As others have said you do not need to update scsi.device for 8GB cards with PFS3AiO (direct scsi).
The limit is 7,87GiB or 8.45GB, and I've never seen 8GB cards being even close to 8.45GB.

Kickstart 37.300 works well with large drives. I ran two of those with large SD cards before. (37.299 does not though)

This is why we need package managers.

To have to take care of all these steps manually would be terrifying for everyone except the most motivated of kittens.

(I am not volunteering, need to work on my own projects first.)

[Daedalus]

Originally Posted by fgh

Kickstart 37.300 works well with large drives. I ran two of those with large SD cards before. (37.299 does not though)

It was intended to work with large hard drives, and *should* work with them, but there are many reports of it being buggy with anything over 40MB. It works fine for many people, but others report issues. My A600 has 37.350 so I can't test it myself.