ACA500 tested

[BarryB]

Originally Posted by fitzsteve

recoverable alert might be BB2's scsi.device conflicting with the ACA's, try the setpatch command:

C:SetPatch SKIPROMUPDATES "scsi.device" QUIET

Nope, still does it: Error: 0100 0003 Task: 080253E8

Originally Posted by meckert

One straight question : what will happen if I connect ACA 500 to A1000 ?

Probably then then

[crasbe]

Originally Posted by meckert

One straight question : what will happen if I connect ACA 500 to A1000 ?

http://eab.abime.net/showthread.php?p=924610#post924610

There are also some posts about the ACA500 on an A1000 spread over this thread.

One straight answer: It will do, what it's supposed to do.

[meckert]

Originally Posted by crasbe

http://eab.abime.net/showthread.php?p=924610#post924610

There are also some posts about the ACA500 on an A1000 spread over this thread.

One straight answer: It will do, what it's supposed to do.

yeah but I wonder what Jens means by "it's not recommended". If it works well with A1000 I think I'll buy one. My old miggy still has the warranty seal sticker untouched and has never been opened. I'd like to keep it that way... so I prefer Aca500 over the A1000 card.... if it works without problems of course.

[BarryB]

Originally Posted by meckert

My old miggy still has the warranty seal sticker untouched and has never been opened. I'd like to keep it that way...

Do you think your warranty is still valid with that sticker intact then

[crasbe]

Originally Posted by meckert

yeah but I wonder what Jens means by "it's not recommended". If it works well with A1000 I think I'll buy one. My old miggy still has the warranty seal sticker untouched and has never been opened. I'd like to keep it that way... so I prefer Aca500 over the A1000 card.... if it works without problems of course.

It's not recommended, because it's not meant to be used with an A1000.

AFAIK there can be problems with the A1000, but if it works, it will work stable.

[joeksterz]

I had mixed luck with a1000's. One machine was perfect, the other seemed dead. Luck of the draw I guess?

http://www.amibay.com/showpost.php?p...0&postcount=45

[Toni Wilen]

Originally Posted by BarryB

So I also flashed v0.81 and now it's getting bizarre!! If I boot from cold into OS3.9 I get 512kb chip, if I CTRL-A-A and reboot back into OS3.9 I get 1mb chip on each and every subsequent reboot, just not the initial boot? So I now have to power on my Amiga, wait for OS3.9 to load then reboot to get 1mb chip?

Boot each time (before setpatch is run and after setpatch resets it) without startup-sequence and run tools/showconfig to 100% confirm memory setup. Do not trust any other program

[meckert]

Originally Posted by joeksterz

I had mixed luck with a1000's. One machine was perfect, the other seemed dead. Luck of the draw I guess?

http://www.amibay.com/showpost.php?p...0&postcount=45

Could you tell me which mobo revision worked with ACA and which one didn't ?

Also does anyone know if there is a way to check A1000 mobo revision without opening the case ?

[BarryB]

Originally Posted by Toni Wilen

Boot each time (before setpatch is run and after setpatch resets it) without startup-sequence and run tools/showconfig to 100% confirm memory setup. Do not trust any other program

Thanks Toni, I'll try that tonight. One thing though, I don't seem to be able to use CTRL-D when booting from the boot card to break to CLI, I can if I boot from WB disk? Looks like renaming the startup-sequence and booting.

EDIT: Toni, as you probably suspected it's setpatch that's the culprit! Booted with no s-s and showconfig reports 1.0mb chip, run setpatch and after rebooting again with no s-s I have 0.5mb chip! There's also an error when running setpatch: Checksum failure! exec.library, exec 45.20 (6.1.2002). Happens on the second run of setpatch and is reported 3 times, piped the output to a file to capture it. Do I try to uninstall Boing Bag 2?

[joeksterz]

both a1000's were rev a. I don't thinks its the mobo rev that matters:
(from memory)
No real difference between rev a and rev 6. they just switched from copper to alumininum traces.
at some point they switched to cheap (ie slow and noisy) pal chips. i think this is what the aca500 doesnt like.

i know of no way of telling the rev and pal chips other than opening up

[Toni Wilen]

Originally Posted by BarryB

Thanks Toni, I'll try that tonight. One thing though, I don't seem to be able to use CTRL-D when booting from the boot card to break to CLI, I can if I boot from WB disk? Looks like renaming the startup-sequence and booting.

CTRL-D only works if CLI window is open. (=boot disk has 1.x bootblock, 2.x bootblock or HD boot does not open it until something is printed to shell from startup-sequence)

EDIT: Toni, as you probably suspected it's setpatch that's the culprit! Booted with no s-s and showconfig reports 1.0mb chip, run setpatch and after rebooting again with no s-s I have 0.5mb chip! There's also an error when running setpatch: Checksum failure! exec.library, exec 45.20 (6.1.2002). Happens on the second run of setpatch and is reported 3 times, piped the output to a file to capture it. Do I try to uninstall Boing Bag 2?

I guess setpatch loaded exec patches can cause problems.

Perhaps 1M custom ROM image works better than setpatch loaded updates. If ACA12xx is connected, ACA12xx 1M ROM maprom is automatically supported. (if 0.80 or newer flash)

You can use "acamaprom <rom image file>" to load rom images (note that there is no physical file called "acamaprom", it is flash resident executable)

[fatbob_gb]

My ACA1230/56 reports 64MB fastmem with the original menu - when I updated to the 081 menu all I ever get is 1MB fastmem.

[lukassid]

Was there even 060 accelerator for a500?

[BarryB]

Originally Posted by lukassid

Was there even 060 accelerator for a500?

ACA500 + Blizzard 060, seems to work for some

[joeksterz]

Originally Posted by lukassid

Was there even 060 accelerator for a500?

There was a tower kit for the a500 that had an a2k cpu slot, add in an 060, and you got an a500/060...

now the aca500 + bliz 1260 seems solid.

[corpsicle]

fatbob_gb : im gonna see if i have time to test 81 tonight and report here how it works for me.

[zipper]

Originally Posted by joeksterz

There was a tower kit for the a500 that had an a2k cpu slot, add in an 060, and you got an a500/060....

And then put PPC developer card into Blizzard 2060 to get an A 500 PPC - well, at least has been done in an A2000.

[corpsicle]

fatbob_gb / jens : im getting the same result with my aca1230/56. 1mb chip, 1mb ram.
Also the AUX CF slot doesnt seem to work ? It worked during flash ( obviously ) but now i cant read the same card, or another card that is FFS formatted.

[fatbob_gb]

@corpsicle
I was getting worried that I was the only one seeing this - sadly I wont be able to investigate much more - I am going away for a fortnight tomorrow.

[BarryB]

Originally Posted by Toni Wilen

CTRL-D only works if CLI window is open. (=boot disk has 1.x bootblock, 2.x bootblock or HD boot does not open it until something is printed to shell from startup-sequence)



I guess setpatch loaded exec patches can cause problems.

Perhaps 1M custom ROM image works better than setpatch loaded updates. If ACA12xx is connected, ACA12xx 1M ROM maprom is automatically supported. (if 0.80 or newer flash)

You can use "acamaprom <rom image file>" to load rom images (note that there is no physical file called "acamaprom", it is flash resident executable)

Excluded exec.library from setpatch and then got checksum error on bootmenu so used NOROMUPDATE and skipped the lot! Now boots to WB with no alerts and 1mb Chip!