ClassicWB + FastATA problem

[Amilord]

Hi,
I just Installed ClassicWB and after i installed the FastATA drivers and i experience serious issues with that.
I cant boot anymore I have errors on C:version or FBlit

Here is my modified Startup-sequence:

C:stack 8192
Wait 1
C:TestRMB
IF WARN
C:SetPatch QUIET
SYS:Prefs/ATA3Prefs
...
EndIF

C:TestLMB
IF WARN
C:SetPatch QUIET
SYS:Prefs/ATA3Prefs
...
EndIF

IF EXISTS SYS:WBstartupD
Rename >NIL: SYS:WBStartupD SYS:WBStartup
EndIF

C:SetPatch QUIET <----- tried to remove that but it's the same
C:ATA3.driver QUIET
C:Version >NIL:
FailAt 21
....

My config: WB3.1 Roms 3.0 A1230 / 8Mo FAST + FastATA MKII (not the last revision. It's important for the drivers : FastATA'99v71a34)

Hope you can help me.

[Bloodwych]

I'm out of my depth with FastATA as I've never used it or have any experience with the drivers. The fact that you're getting errors as early as C:Version says to me you have an issue with your hardware, partition settings or FastATA drivers. I doubt it's anything to do with the ClassicWB, as a default install uses exactly the same lines up to that point.

All I can suggest is double check how you install the FastATA, then if you still get problems removing anything non-standard in the startup-sequence and see if that helps. That means doing the following from CLI/shell:

Hold both mouse buttons and boot with no startup-sequence.
At the CLI prompt, type ed s/startup-sequence
Place a ; in front of the following lines to disable them:

IF EXISTS SYS:Expansion/FBlit/FBlit down to the EndIF part.
IF EXISTS S:User-Startup down to the EndIF part.
Change LoadWB to LoadWB.orig

The WBStartupD line won't affect anything, so leave that alone.

Doing the above will start Workbench with exactly the same settings as a default install except the inclusion of your FastATA lines, so if you still get errors it's something to do with your hardware, partition settings or FastATA drivers.

[keropi]

when I used my fastata's , I only put those lines on the beggining of s-s:

C:stack 8192
C: ATA3.driver QUIET

and it never failed me... mind you, I was using OS3.9 though...

[Bloodwych]

Keropi brings up a good point - remember Workbench 3/3.1 has a 2GB partition limit with the standard FFS, 4GB with SFS/PFS.

If your partition is too large, you'll get errors.

[keropi]

oh yeah, the boot partition is ALWAYS under 2GB...

[Amilord]

Originally Posted by Bloodwych

I'm out of my depth with FastATA as I've never used it or have any experience with the drivers. The fact that you're getting errors as early as C:Version says to me you have an issue with your hardware, partition settings or FastATA drivers. I doubt it's anything to do with the ClassicWB, as a default install uses exactly the same lines up to that point.

All I can suggest is double check how you install the FastATA, then if you still get problems removing anything non-standard in the startup-sequence and see if that helps. That means doing the following from CLI/shell:

Hold both mouse buttons and boot with no startup-sequence.
At the CLI prompt, type ed s/startup-sequence
Place a ; in front of the following lines to disable them:

IF EXISTS SYS:Expansion/FBlit/FBlit down to the EndIF part.
IF EXISTS S:User-Startup down to the EndIF part.
Change LoadWB to LoadWB.orig

The WBStartupD line won't affect anything, so leave that alone.

Doing the above will start Workbench with exactly the same settings as a default install except the inclusion of your FastATA lines, so if you still get errors it's something to do with your hardware, partition settings or FastATA drivers.

Ok, I tried that and I got a C:SetPatch failed returncode 20
I have 3 partitions on my CF : Workbench: < 1Go , Work: 1,1Go and Games: 2038Mo ....
So I dont know....without the drivers but with FastATA plugged everything is ok.

[Bloodwych]

mmm, your using a CF card as well - again another area I'm not familiar with.

If you don't get any responses in this thread, do a search on here about using compact flash cards and post in there. I know for a fact there are some big threads kicking around on this subject.

[Calgor]

If it works perfectly without the FastATA driver, but stuffs up with it, maybe you have a problem with how that driver is configured. If your hard disk is not greater than 8GB, then you only need the driver for extra speed, or if it is greater than 4GB you may need it if you had SPLIT mode where all partitions are max 4GB.

There are many settings to choose from. I have the Mk-III version which has some extra features so not sure what yours has got. Make sure you have the latest driver as per Elbox website versions. Also I only briefly used WB3.1 with mine (mostly 3.9), my HD is currently trashed but 3.1 should be back soon so I will let you know how that goes.

Can you select NOSPLIT mode? Should your driver be loaded before or after SetPatch? Is your PIO mode too fast (PIO0 is safer if problems). Interrupt mode selected (disable this as possible bugs). Loading the ATAPrefs program will tell you your settings.

Is the MaxTransfer too large or Mask incorrect?

[Amilord]

it works ! here is what i did and it seems to work (hmm... today it works)
I change the max transfer to 0x1fe000 and the Pio Mode in the ATAPefs to 0
I tested that settings and it was ok but i was not satisfied with the speed so I tried PIO3 Mode and it'is ok and I can achieve 4Mo/s transfert rate...so it's better, and it's seems that PIO4/5 cant't do it so no full speed with my CF for me but it's not related to ClassicWB i think, and by the way 4Mo is 2.5x the original speed of the onboard ide controller of the A1200 ;-)

Thanks guys.

edit: I forgot, i had to put the driver load after the Setpatch QUIET

[Calgor]

Glad to hear you got it working.

If you ever use OS3.9 (and probably OS3.5), you are supposed to put the driver to resident mode and also before setpatch. This is so it stays in memory and uses the correct scsi.device of FastATA instead of the ROM one with that extra reboot in those OSes. It must be okay after setpatch for OS3.1 if it is working for you for your setup - however I would suggest that it may not work for you if you try to write to any partitions over 8GB.

Elbox instructions on this are not the best, and I suggested a rewrite to them to make them clearer.