aca 1231 on 3.0 rom

[Prosonic]

hay guys i recently aquired a 64mb aca1231 and discovered the 3.0 rom doesnt see the fast rem or detect the card, sysinfo shows its using the cpu on the card

i used aca tune to detect the memory and it was working fine but due to alot of whd games i was running out of chip memory (glowicons) with some more googling i discovered fblit and installed, to go one better i decided to use acatune to map in the 3.1 rom from file and turns out it works rather well and i dont need to run acatune just to detect the memory

long story shot any risk running such a weird setup (remaped software rom into the accelerator reserved memory ) im remapting the rom before blinddrivers and flbit in the startup sequence

i do plan on going 3.1 roms down the track and maybe os 3.9 depending on how it handles old games

[Coltch]

I'm running 3.0 roms with my ACA1231 and haven't really had any problems (ACATune is first line in S-S), I do get some random issues with WHDLoad. As the card seems to run stable on my current set-up I haven't bothered switching the roms out (I have 3.1 roms in my 1D4). Also I'm running a fairly standard WB3.1 on this machine (this will soon change).

[desiv]

Originally Posted by Prosonic

long story shot any risk running such a weird setup (remaped software rom into the accelerator reserved memory ) im remapting the rom before blinddrivers and flbit in the startup sequence

No risk at all..
That's what it's designed to do...
Do that myself.. (with my ACA1230)

One thing, don't just run acatune before those..
Make it the first line in your startup-sequence...
It should be the first command run... Otherwise you can have issues...

Enjoy..

desiv

[Neil79]

In the line below ;Lite3.1 :

C:acatune -maprom devs:ks31.rom >NIL:
C:acatune -cache on -burst on >NIL:
C:acatune -resetpcmcia >NIL:

Is what I use

[fitzsteve]

Should all be on one line, i.e:

C:acatune - maprom -cache on -burst on -resetpcmcia >nil:

[demolition]

It doesn't work on my ACA1232 when they're all on one line. I have to keep maprom on one line and the other options on another line, or they won't be executed. Perhaps it stops all execution of acatune when it sees that the maprom file is already mapped, and thus 'forgets' that it needed to do other things as well.

[fitzsteve]

Works fine here :-)

[demolition]

Here's my proof.

A command line identical to the first one was executed after which the machine rebooted to apply the maprom.
As you can see, it ignores both the '-burst on' as well as the '-vbrmove'.
If I do 'acatune -burst on -vbrmove' on its own, it works as it should.

Edit: Seems weird if it works for you and not me..

[Neil79]

Originally Posted by demolition

It doesn't work on my ACA1232 when they're all on one line. I have to keep maprom on one line and the other options on another line, or they won't be executed. Perhaps it stops all execution of acatune when it sees that the maprom file is already mapped, and thus 'forgets' that it needed to do other things as well.

Doesn't work when it's all on one line here either

It only works for me if I take out the maprom kickstart bit But I won't do that!

Doing it seperate doesn't do any harm

What's -vbrmove anyway?

[Coltch]

Strange, I have everything on the same line with my 1231 and it's fine

[desiv]

Originally Posted by Coltch

Strange, I have everything on the same line with my 1231 and it's fine

Can you post yours?
I wonder if it's an order thing? Or version?

I only do the maprom, so I don't have any other options.. ;-)

desiv

[Sandro]

Originally Posted by Prosonic

hay guys i recently aquired a 64mb aca1231 and discovered the 3.0 rom doesnt see the fast rem or detect the card, sysinfo shows its using the cpu on the card

i used aca tune to detect the memory and it was working fine but due to alot of whd games i was running out of chip memory (glowicons) with some more googling i discovered fblit and installed, to go one better i decided to use acatune to map in the 3.1 rom from file and turns out it works rather well and i dont need to run acatune just to detect the memory

long story shot any risk running such a weird setup (remaped software rom into the accelerator reserved memory ) im remapting the rom before blinddrivers and flbit in the startup sequence

i do plan on going 3.1 roms down the track and maybe os 3.9 depending on how it handles old games

** the exact clock speed is 41.6625 (25 x 3.333/2) MHz.
** Kickstart 3.0 users must add the memory with the ACATune software.