See no kick, hear no kick, do no kick

[Hockmiester]

Morning all. A nice Friday morning I'm sat in the office question for you.

I have a 1200 for CFHDD & ACA1220 all working fine. The 1200 has a 3.0 but I also have a 600 upstairs (not super relevant) with a 3.1 and in a drawer I have a 2.0 physical roms.

Anyway, I configured the HDD from WinUAE including the ACA1220 setup. WinUAE works fine using 1.3 roms as a 500 or 3.0 & 3.1 (40068) as a 1200 or even as a 4000.

I replicated my machine hardware in WinUAE and created the HDD and when it transferred over to the A1200 everything works perfectly.

Except one thing. I have installed all my games from the original disks to the HDD and (for example) BASS works fine. I thought I would give WHDLoad a go to load the games faster.

Now if I run WHDLoad with the CFHDD in the PC then WHDLoad works perfectly. If I transfer the CF to the Amiga then it says invalid rom in devs/kickstarts blah blah and if I move back to the PC it works again.

So from ACATune in the startup-sequence I softkicked the 3.1 rom WinUAE was using into the fastram with no problems (HDD games work) and made sure everything was named correctly in devs/kickstarts but got the same error.

Yes I tried about 5 different 31 kicks and also copied/pasted and renamed the WinUAE version to 40068.a1200. (also the a500, a600 and a4000 do the same error)

Any suggestions?

[Thomas]

Change MaxTransfer of all partitions to 0x1fe00.

[Hockmiester]

Ok, and I can do that from WinUae to the CFHDD by entering a value of 1fe00?

Any reason why that might be causing the problem?

Cheer for the suggestion.

[psxphill]

Ok, and I can do that from WinUae to the CFHDD by entering a value of 1fe00?
 
Any reason why that might be causing the problem?

The ide interface is limited to that, but scsi.device doesn't ignore values above that. It will work fine until a single transfer is larger and then it will fail. So you might not notice until a large file is loaded into ram.

[Thomas]

The ide interface is limited to that, but scsi.device doesn't ignore values above that. It will work fine until a single transfer is larger and then it will fail. So you might not notice until a large file is loaded into ram.

Actually this is not the entire truth. The problem is not a bug in scsi.device. The problem is the age of scsi.device and that the ATA specs have changed since scsi.device was written. Scsi.device relies on a feature which is not present any more in the current ATA specs. It does not have problems with old drives. Only with new drives the MaxTransfer problems occur.

[paul1981]

Ok, and I can do that from WinUae to the CFHDD by entering a value of 1fe00?

You can make the MaxTransfer adjustment on the real Amiga, or the emulated Amiga. HDToolBox for instance.

[Hockmiester]

I'm going to hate myself for asking this question but my wife is watching the voice so its making me insane.

OK, I'm in HDToolBox and can't see how to set the max speed.

Tell me I don't need to reformat @ the correct speed. I've been playing around but can't see how I alter this speed.

Please point me in the right direction.

M

[Oldsmobile_Mike]

It's under the advanced options checkbox, then hit change, I think.  Make sure to press enter after entering the new, correct value, and to change it for each partition.  No, you don't need to reformat to change it.

Edit: these screenshots should help you:  http://home.arcor.de/heider.michael/englisch/image_inst-en.html

[Dr.Bongo]

after entering the maxtransfer value PRESS ENTER, or it will not be kept.

nevermind, oldsmobile_mike already said that

[paul1981]

after entering the maxtransfer value PRESS ENTER, or it will not be kept.

nevermind, oldsmobile_mike already said that

And remember also to go back to the initial screen and press "Save changes to drive" button.