Classic Workbench; Problems with aca1233 accelerator.

[paul1981]

Thanks, I will try this. Oddly what seems to be happening is, I activated the maprom feature and I get loads of other mem. But after resetting the amiga, ctrl, A+A, I lose the other mem. Is there a way to save the maprom command rather than having to activate this every time i boot up?

Well I will try your suggestion. Really, that's great. I guess some games require 3.1? Oh and should I enter the command in my acatune software. Its on a floppy. Or from a cli?

You need to add the ACATune command at the beginning of your startup-sequence, so that you don't have to keep typing it every time . The startup-sequence is what boots your Amiga into Workbench. It's literally just a sequence of commands stored in a text file.

Boot up your computer, go to a shell and type in "ed s:startup-sequence".
Or, just select the "Execute Command" from the Workbench menu and type "ed s:startup-sequence".

Your startup-sequence will be listed and you can add the ACATune line in here. Put it at the top, before SetPatch or any other command is run (in most cases). Then go to the menu and select 'Save'.

[doctorq]

And whatever you do, DO NOT buy 3.1 roms. They are a waste of money in your case as you have an ACA card with a maprom feature. You can 'soft kick' 3.1 from your hard drive with the ACATune command.

+1

Kickstart 3.1 offers only minor improvements. If you don't have any specific reason for getting the roms, then don't.

[Oldsmobile_Mike]

+1

Kickstart 3.1 offers only minor improvements. If you don't have any specific reason for getting the roms, then don't.

I feel like a drug pusher. "Upgrade to 3.1, you know you want to, you know it'll make you feel better", LOL. Jeeze, it's less than $20. I'll just put this here:

http://wiki.classicamiga.com/Kickstart_Roms_Explained#Why_upgrade_from_Kickstart_3.0_to_Kickstart_3.1.3F


All the 3.1 haters on here.

[wrath of khan]

You need to add the ACATune command at the beginning of your startup-sequence, so that you don't have to keep typing it every time . The startup-sequence is what boots your Amiga into Workbench. It's literally just a sequence of commands stored in a text file.

Boot up your computer, go to a shell and type in "ed s:startup-sequence".
Or, just select the "Execute Command" from the Workbench menu and type "ed s:startup-sequence".

Your startup-sequence will be listed and you can add the ACATune line in here. Put it at the top, before SetPatch or any other command is run (in most cases). Then go to the menu and select 'Save'.

Ive tried the command a few times but no luck. Perhaps I am entering in the wrong place/order?
Here's a pic attached of the startup sequence and you can see where ive entered the line.
Upon reset of the miggy the other mem diminishes greatly.

[paul1981]

Ive tried the command a few times but no luck. Perhaps I am entering in the wrong place/order?
Here's a pic attached of the startup sequence and you can see where ive entered the line.
Upon reset of the miggy the other mem diminishes greatly.

Open Multiview (in SYS:Utilities) and open the file 'RAM:acaoutput.txt'
Or open a Shell again and type "type ram:acaoutput.txt" instead.

This perhaps will give us some clues as to why it isn't working correctly.

I didn't know you were using ClassicWB, and I don't know what the Maxmem-sequence is, which for all I know could be causing the issue. You can try moving the ACATune line directly above the SetPatch line though.

TBH, there's nothing wrong and the line should stay at the top. Let us know what acaoutput.txt reads...

[giZmo350]

 Why upgrade from Kickstart 3.0 to Kickstart 3.1?

 If you own an A1200 or A4000 with Kickstart 3.0 Roms installed, then  you might wonder what the advantages are, and why it is worth upgrading  to the newer 3.1 roms.   Here are some of the main changes 3.1 offers  over 3.0.
 

• 3.0 cannot run AmigaOS later than 3.1 (it doesn't support loading in modules from AmigaOS updates like 3.1 does)
• 3.1 contains many bug fixes to the libraries both internally and on the disk
• 3.1 is more up-to-date
• 3.1 supports the Akiko chip when used on a CD32
• 3.1 supports the extra CD32 libraries that are built into ROM (namely lowlevel.library and nonvolatile.library)
• 3.1 contains minor improvements to RTG handling
• 3.1 contains the additional datatypes: ANIM and CDXL
• 3.1 introduces a small delay whilst checking for hard drives.  This gets around the old 3.0 bug whereby a hard drive is not always recognized from cold boot.

I know, my reply doesn't really help the problem... thought I would post 3.1 ROM advantages though...

Ok Mike.... I see your "Double Face Palm" and raise you a face palm!

[wrath of khan]

Open Multiview (in SYS:Utilities) and open the file 'RAM:acaoutput.txt'
Or open a Shell again and type "type ram:acaoutput.txt" instead.

This perhaps will give us some clues as to why it isn't working correctly.

I didn't know you were using ClassicWB, and I don't know what the Maxmem-sequence is, which for all I know could be causing the issue. You can try moving the ACATune line directly above the SetPatch line though.

TBH, there's nothing wrong and the line should stay at the top. Let us know what acaoutput.txt reads...

The shell reads: Error: Aca card type unsupported.
It then tells me to get the latest version of acatune from icomp.de. Guess the floppy disk version supplied is not the latest.
Well, I need to buy a cd drive to set up easynet pcmcia wireless, to go online and then download the software...bummer.
I foresee some difficulty setting up easynet too...

I'll get the cd drive soon.

[Oldsmobile_Mike]

Might be a ClassicWB issue. As Paul1981 said, you've got some weird programs installed on there. May be a conflict. If you type 'version acatune' at a command prompt what does it say? Post your version number and maybe someone else can confirm if it's the latest?

I would download the latest version to a CD from your PC and read it back on the Amiga that way (obviously this will require a CD drive on your Amiga). You don't happen to have any PC's sitting around with a floppy drive still, anymore, do you?

There's various methods of transferring files via serial and parallel links, of varying levels of difficulty to setup/configure.

[paul1981]

The shell reads: Error: Aca card type unsupported.
It then tells me to get the latest version of acatune from icomp.de. Guess the floppy disk version supplied is not the latest.
Well, I need to buy a cd drive to set up easynet pcmcia wireless, to go online and then download the software...bummer.
I foresee some difficulty setting up easynet too...

I'll get the cd drive soon.

ACATune should be version 17.

[wrath of khan]

ACATune should be version 17.

Yeah the floppy disk says ver 1.7.
I'm using a cf card preset with lots of software, whdload etc. Its installed internally. I'm not sure about most of whats on there but there is d-paint, hippo player etc. Looks like there's software for adding a large hardrive too etc.

Is classic workbench lite a good thing or bad? I'm rather clueless but i guess its meant to be fast with slow amigas?

[paul1981]

Yeah the floppy disk says ver 1.7.
I'm using a cf card preset with lots of software, whdload etc. Its installed internally. I'm not sure about most of whats on there but there is d-paint, hippo player etc. Looks like there's software for adding a large hardrive too etc.

Is classic workbench lite a good thing or bad? I'm rather clueless but i guess its meant to be fast with slow amigas?

Open a Shell, and type the command "acatune -status"

Let us know what it says.

There's nothing wrong with ClassicWB, it's just a pre-configured Workbench environment. The problem you have though is one of the chicken and the egg... the file transfers that presently are impossible for you. This is why I always keep a pc with a floppy drive around.

[wrath of khan]

Open a Shell, and type the command "acatune -status"

Let us know what it says.

There's nothing wrong with ClassicWB, it's just a pre-configured Workbench environment. The problem you have though is one of the chicken and the egg... the file transfers that presently are impossible for you. This is why I always keep a pc with a floppy drive around.

Again the shell reads: Error: Aca card type unsupported.
It then tells me to get the latest version of acatune from icomp.de

[wrath of khan]

Version 17 is available to download and my disk has ver.1.7? Is that just another way of typing 17 or have there been that many revisions already?

[paul1981]

Again the shell reads: Error: Aca card type unsupported.
It then tells me to get the latest version of acatune from icomp.de

Open a shell and type "version c:acatune full"

And let us know what that says.

Also, please do make sure that you have turned your Amiga off/on at the power brick. A 'cold boot' is a boot from a previously powered off state, and a 'warm boot' is a boot from a previously powered on state (like after a reset with A-A-CTRL). I'm interested to know whether it's working from a cold boot, so please make sure you've cold booted it first. So, see what happens from a cold boot please.

[paul1981]

Version 17 is available to download and my disk has ver.1.7? Is that just another way of typing 17 or have there been that many revisions already?

1.7 = 17 IIRC, so no problem there.

http://wiki.icomp.de/wiki/ACAtune

If there's still no joy, I suggest powering the Amiga off at the brick, power on again whilst holding down both mouse buttons and this will take you to the Amiga Early Startup Control.

From here select the button "Boot with no Startup-Sequence".

When the AmigaDOS prompt appears, type in "c:acatune -status"

And let us know what that says. If it recognises the card then there's something in the ClassicWB startup-sequence which is upsetting it.

[wrath of khan]

Open a shell and type "version c:acatune full"

And let us know what that says.

Also, please do make sure that you have turned your Amiga off/on at the power brick. A 'cold boot' is a boot from a previously powered off state, and a 'warm boot' is a boot from a previously powered on state (like after a reset with A-A-CTRL). I'm interested to know whether it's working from a cold boot, so please make sure you've cold booted it first. So, see what happens from a cold boot please.

The shell said: Could not find version information for C:acatune. I powered on from the brick to begin.