WHDLoad suddenly broken

[lauri.lotvonen]

Did you have your Deneb USB installed when the WHDLoad was working?
Poseidon crashes almost every WHDLoad game that I know of.
Try turning Poseidon USB stack off.

[jj]

No FFS can only handle partition sizes of just under 4GB with FASTATA. You need a file system like SmartFileSystem (the one I use), with SmartFilesystem I have varous sized partitons on my 2 500GB HDs and FASTATA, the biggest of which is 250GB, but there is no real limit on partition sizes using SFS and I have never lost even one bit of data in the years that I have been using it.

Ummmmm no.  I have only ever used the standard Amiga file system with FASTATA.   It has no problems with partitions this size.  especailly under os3.9.
 
There is a limit to filesizes of a couple of gig, cant remember the exact size.  but your 80GB partition/drive should be fine.
 
You dont need SFS.  Though it is a better file system

[Cass]

I agree with amiga1260 & lauri.lotvonen : I have a script running before any WHDLoad launch that disables TCP/IP stack & USB stack.

The quote is from the WHDLoad Support page, you may try this but at the end you should disable any running tasks that create interrupts ;-)

check the Tooltypes (or the options if started from the CLI/Shell), many things can be adjusted setting Tooltypes, there is hardware which requires that you set the correct Tooltypes, maybe your system is to fast - so set NoCache, some games are working only under PAL or NTSC - so try the Tooltypes PAL and NTSC, some extra hardware creates at random interrupts which confuses the installed games/demo - so try Tooltype NoAutoVec, sometimes also the Tooltypes NoVBRMove and NoMMU may help

[Franko]

Ummmmm no.  I have only ever used the standard Amiga file system with FASTATA.   It has no problems with partitions this size.  especailly under os3.9.
 
There is a limit to filesizes of a couple of gig, cant remember the exact size.  but your 80GB partition/drive should be fine.
 
You dont need SFS.  Though it is a better file system

Hi JJ, can't say for certain whether your right or I'm right on this one. I can only go by my own experience of trying to use 2 500GB HDs on my various amigas, never managed to get them formated or partitioned properly under OS3.9 & FFS, thats why I went with SFS and also for the reason that I have lots of files larger than 4GB and the filesize limit of just under 2GB on FFS was no use to me.

[Matt_H]

@ Franko

You were probably hitting the the LBA barrier at 128GB; the default 3.9 FFS will choke with anything that large or larger. There's a patch on Aminet to get around it though, so you could theoretically use your 500GB drives with FFS.

[TheRogue]

I've installed SFS, but that doesn't seem to be the problem. The problem seems to be that no matter how many times I change the driver type to nosplit in the FastATA prefs, the system always defaults back to split and doesn't detect that I have installed and partitioned the drive as a nosplit drive. What am I doing wrong?

[Franko]

I've installed SFS, but that doesn't seem to be the problem. The problem seems to be that no matter how many times I change the driver type to nosplit in the FastATA prefs, the system always defaults back to split and doesn't detect that I have installed and partitioned the drive as a nosplit drive. What am I doing wrong?

Its a fault in the actual ATA3.driver itself (all versions) if you have one partion set to split then another set to nosplit on the same port, the ruddy driver sets everything to split (no matter what you select in the prefs prog).

The only way I solved this problem was to disassemble the driver and rewrite it to allow you to have both split and nosplit and no more of the annoying default back to split.

Wrote to Elbox once showing them how to fix this bug/problem but never heard a thing from them.

[TheRogue]

Here's the thing though, I don't have anything set to split. There is just one drive on the Primary port and that's what I'm trying to set to nosplit. I'm using the driver versions from their webpage though because I bought the controller second hand and don't have access to the latest drivers. Could the problem be that I'm using old drivers? Otherwise, how can I fix this?

[Franko]

Here's the thing though, I don't have anything set to split. There is just one drive on the Primary port and that's what I'm trying to set to nosplit. I'm using the driver versions from their webpage though because I bought the controller second hand and don't have access to the latest drivers. Could the problem be that I'm using old drivers? Otherwise, how can I fix this?

Dunno about everyone else, I can only say what works on my set ups. For example. The FASTATA MKII manual states that the boot partition must be in the first 4GB space of a hard disk for the OS to be able to recognise it as bootable.

An example of the way one of my 500Gb HDs is partitioned is...

DH0: 1GB partition (used for booting in OS3.0 to 3.9) FFS (ie: contains Workbench for booting up in whichever version you use)
DH1: 1GB partition (used for temp storage) FFS
DH2: 2GB partition (used for booting in OS 4.0) FFS
DHA: to DHW: various partitions used for data etc... (rough total about 80GB) FSS
HD0: 200GB partition (used for data, large files etc...) SFS2
HD1: 200GB partition (used for data, large files etc...) SFS2

Not sure how clear this is to you, but sticking with this type of set up for me causes no problems.

[TheRogue]

I suppose it may have to do with the fact that I'm using earlier drivers. Have any idea where I can get the latest ones? I'm using like 2.5 I believe and I've seen people talking about version 7.x. Where can I get this later version?

[Franko]

If your talking about the FastATA drivers I use V8.8

[TheRogue]

Yes, that's exactly what I'm talking about. Where can I get that version?

[Franko]

Don't go away yet, Im going to PM you.

[TheRogue]

Great, thanks so much.

[Bamiga2002]

Why bother, the latest drivers are available at Elbox website.

[Franko]

Why bother, the latest drivers are available at Elbox website.

Hi Bamiga2002, TheRougue had heard that there was a version 7.x of the A4000 drivers, he already had the ones from the Elbox site, I've been scouring the internet but can't find any drivers beyond version 2.5

Anyone else able to help out TheRogue here...