Problem with new ACA1233n

[arti040]

If you're talking about me, i got to sell that ACA card unfortunately. It did not want to work with my Mediator.

[Romanujan]

I'm talking about working ACA1233n MapROM tool...

[DerSheriff]

Originally Posted by Romanujan

I'm talking about working ACA1233n MapROM tool...

I'm also intrested. Tried to contact Jens asking for news, never got an answer.

[bubbob42]

I'm the bottleneck here. As told before, this is hobby work and I already spent lots of time to bring you more than half a dozen tools for the card, as you may have noticed.

If you can't wait - check out the various Maprom tools on Aminet and softkick Roms with or even without the card's MMU. I won't give a date for the release of ACAMapRom, since I have other "obligations" to meet, first.

Another approach would be to check out the documentation on the ICOMP wiki and implement such a tool yourself. All the information is there.

[bubbob42]

There you go, now "feature complete":

http://wiki.icomp.de/wiki/ACA1233n#Download

Please read the documentation and send reports, if something is not working as expected. ACAMapROM supports 512kB & 1MB ROMs. Tool sources & full developer docs are included.

Thanks go to Toni, for his hints & help with the reboot routine.

[DerSheriff]

Originally Posted by bubbob42

There you go, now "feature complete":

http://wiki.icomp.de/wiki/ACA1233n#Download

Please read the documentation and send reports, if something is not working as expected. ACAMapROM supports 512kB & 1MB ROMs. Tool sources & full developer docs are included.

Thanks go to Toni, for his hints & help with the reboot routine.

Thanks mate!

I managed to try it. At least, the MapRom and ACAInfo tools.

Only a question. I added the maprom line in 1st place at startup-sequence. It maps correctly the 3.1 rom (i have physical 3.0). It does one reboot (when it maps the rom file into memory) and then I get the 3.1 ROM purple screen, waiting for a floppy disk. Then if I reboot with CTRL-A-A it boots correctly from the IDE/CF drive. Not a problem of course, it works and found no problems until now! Just to know if it's OK or I done something wrong.

Thank you again!
DerSheriff

[bubbob42]

Hm, that is strange. Both Kick3.1 and ACA1233n bootup delays are especially long to prevent just that. Only tested to kick 3.0 and 3.9 with a physical 3.0 Rom. What kind of drive are you booting from?

I'll try to reproduce the issue once my new A1200 case arrives. It'll host my A1200T Board which still has 3.0 ROMs.

[Vypr]

I've got a strange issue when using KickROM on mine, if it's enabled in startup-sequence I keep getting "intuition is attempting to reset the workbench" on Workbench loadup and it also pops up when I attempt to change the screen settings. Taking it out of startup sorts it.

[Toryglen-boy]

copy ACAMAPROM over to c:

in your startup :


acamaprom i

(you can do a "quiet" command with no screen output)


this will map the internal ROM for you, and that's about all it can do! ACATune does not work with these cards, so for gods sake, dont try.

Originally Posted by DerSheriff

I'm also intrested. Tried to contact Jens asking for news, never got an answer.

[Toryglen-boy]

Originally Posted by Vypr

I've got a strange issue when using KickROM on mine, if it's enabled in startup-sequence I keep getting "intuition is attempting to reset the workbench" on Workbench loadup and it also pops up when I attempt to change the screen settings. Taking it out of startup sorts it.

i had this with timing issues, running an EC1221 on a 2B board, with the 1233n it't not hung once.

[DerSheriff]

Originally Posted by bubbob42

Hm, that is strange. Both Kick3.1 and ACA1233n bootup delays are especially long to prevent just that. Only tested to kick 3.0 and 3.9 with a physical 3.0 Rom. What kind of drive are you booting from?

I'll try to reproduce the issue once my new A1200 case arrives. It'll host my A1200T Board which still has 3.0 ROMs.

I'm booting from a CF card, with cf ide adapter from amigakit (the classic kind of). My CF is a 4gb formatted card with 2 pfs partitions (500 mb the DH0, 3*** the DH1), with WB3.1 (more specifically the ClassicWB Full).
Tomorrow I'll try another CF card, 256MB, and I'll report the results. If you need other infos just ask me. I can make you a video if it could be useful to you for troubleshooting the problem.

Thank you,
DerSheriff

[Nightfox]

When I use the "ACAMapROM I" command in startup-sequence it successfully puts the internal ROM into memory but it no longer detects my hard drive (CF card with IDE adapter from AmigaKit) so all I can do is boot from floppy.

[mike_01]

Hello,
Have you tried adding the quiet (q) option?

"ACAMapROM I q"

Maybe that's the problem.
Regards

[Nightfox]

Originally Posted by mike_01

Hello,
Have you tried adding the quiet (q) option?

"ACAMapROM I q"

Maybe that's the problem.
Regards

Thank you so much! I didn't even bother trying the quiet option because that option seems like the most illogical solution to the problem. Why on earth does being quiet fix the issue?

[Nightfox]

I spoke too soon. It worked once but now it's doing it again...

[DerSheriff]

Originally Posted by Toryglen-boy

copy ACAMAPROM over to c:

in your startup :


acamaprom i

(you can do a "quiet" command with no screen output)


this will map the internal ROM for you, and that's about all it can do! ACATune does not work with these cards, so for gods sake, dont try.

I use "acamaprom" from the ACA1233n lib archive. I don't need to map the internal rom, but instead I need to map a ROM file.
It maps correctly the 3.1 ROM file (i'm on physical 3.0 roms).

BTW, i'll try to move it to C, seems a good idea.

Thank you,
DerSheriff

[Nightfox]

I'm wanting to use it and boot AmigaOS 3.9 and was wondering if SETPATCH affects anything or not? I put ACAMapROM I q to be before any SETPATCH line. I'm using physical 3.1 ROMs

[bubbob42]

@sacredbanana: Do a manual reset after mapping the rom and your HD should show up. I need to add some patching for your config. Will take a while, though.

[DerSheriff]

Copying acamaprom to C does not solve the problem.

All I can see is that powering on my amiga, after the 1st reboot (in which the ACA card maps my 3.1 rom file), I have only DF0 and CC0 in the boot menu. No DH drives. After a soft reboot (CTRL-A-A) my CF hard drive becomes visible in the boot menu, and of course it boots OK.

[Nightfox]

I've had lots of issues with my system so I ended up reinstalling AmigaOS 3.9 from scratch with all the boing bags and for some reason ACAMapROM works fine now. Could be coincidence though