3.9, ACA500, and ACA1233 = recoverable errors

[Motormouth]

I purchased an ACA500 couple months ago and an ACA1233 for it about a month ago.
This has definitely breathed new live in one of my old A500s.  This config runs at over 9K Dhrystones with just blazing fast memory transfers and a very quick CF card (when using the ACA 1233).

This hardware configuration works extremely well with both 1.3 and 3.1 installs, but........

There is just one problem...... OS 3.9.

When I try to use a clean OS 3.9 install (that is OS 3.9 with BB1&2 freshly installed on a CF card)  I get two recoverable errors during boot.  After hitting the right mouse button, the necessary two times, the computer finishes booting and goes to the workbench screen without any other problems.

I am guessing this has to do with the kickstart patches OS 3.9 uses.  Maybe the patches do not like the mapping of the 3.1 rom by either the ACA500 or the ACA1233 or the patches do not like the ACA500 scsi.device (since it is neither an A2091, a590, a built in A3000 SCSI, nor the gayle in the A600, A1200, A4000).  Anyone else have this problem and/or wisdom to solve this?

Or anyone know how to contact individual computers???  Nothing obvious on webpage?

[xboxOwn]

I purchased an ACA500 couple months ago and an ACA1233 for it about a month ago.
This has definitely breathed new live in one of my old A500s.  This config runs at over 9K Dhrystones with just blazing fast memory transfers and a very quick CF card (when using the ACA 1233).

This hardware configuration works extremely well with both 1.3 and 3.1 installs, but........

There is just one problem...... OS 3.9.

When I try to use a clean OS 3.9 install (that is OS 3.9 with BB1&2 freshly installed on a CF card)  I get two recoverable errors during boot.  After hitting the right mouse button, the necessary two times, the computer finishes booting and goes to the workbench screen without any other problems.

I am guessing this has to do with the kickstart patches OS 3.9 uses.  Maybe the patches do not like the mapping of the 3.1 rom by either the ACA500 or the ACA1233 or the patches do not like the ACA500 scsi.device (since it is neither an A2091, a590, a built in A3000 SCSI, nor the gayle in the A600, A1200, A4000).  Anyone else have this problem and/or wisdom to solve this?

Or anyone know how to contact individual computers???  Nothing obvious on webpage?

I went the route of ClassicWB. Don't regret it ever since I enjoy both my ACA500+ACA1233 and my Amiga experience environment.

Just saying. Sure it isn't pweaty like AmigaKit or AmigaSYS but it is functional. I can even listen to MP3 on my A500 thanks to classicWB.

[Lurch]

Running ClassicWB 3.9 with no issues.

http://classicwb.abime.net/classicweb/os39.htm

[danbeaver]

A common issue with OS3.9 causing a bad install, you can: reinstall it (once took twice for me), disable thr Setpatch ROM update, or install BB3 & BB4.  I prefer the reinstall route WITH BB3 and the most recent 4.

[Motormouth]

I went the route of ClassicWB. Don't regret it ever since I enjoy both my ACA500+ACA1233 and my Amiga experience environment.

Just saying. Sure it isn't pweaty like AmigaKit or AmigaSYS but it is functional. I can even listen to MP3 on my A500 thanks to classicWB.

Running ClassicWB 3.9 with no issues.
http://classicwb.abime.net/classicweb/os39.htm

Thanks for all the replies I definitely agree with both of you, ClassicWB rocks.  I tried ClassWB FULL, ADV, and ADVSP with the ACA500+ACA1233 without any issues.  I will try Lurch's I idea of ClassicWB 3.9.  I have clean hardfile image of of this already made on WinUAE.  I will try this.

A common issue with OS3.9 causing a bad install, you can: reinstall it (once took twice for me), disable thr Setpatch ROM update, or install BB3 & BB4.  I prefer the reinstall route WITH BB3 and the most recent 4.

@danbeaver, I oddly have never had an issue installing OS3.9 before.  I will try another clean os3.9 install.  I will see what happens when I put BB1 then BB2 then BB3&4 (as they come together is a single install now).  and see what happens I will disable the Setpatch rom update also.

Thanks for the great ideas!!!!!!