You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During the DiagROM startup, before the menu is displayed, the rom checks for both A4000 and A1200 fast memory. There is an option here to abort the tests if you are really good at playing the mouse-button timing game, which makes me think that a freeze is sometimes expected?
However, if such a freeze occurs predictably and regularly, it seems to me that it might just be an issue. I am seeing 100% reproduction of a freeze/lock-up during the A1200 mem check portion in Amiga 4000s.
So far, I have NOT seen this problem on my A4000/030 or A4000EC/030 (both of which using the A3630 cpu card). However, I have seen the problem 100% of the time on A4000s with A3640 cpu cards, on both A4000s and A4000T boards. Playing the mouse button game allows me to get past this, and all other tests come out fine. The machines are a random mix of NTSC and PAL, so I don't think that matters.
The text was updated successfully, but these errors were encountered:
I'm just about to finish populating and testing a NOS A4000T Mainboard. The symptoms you describe could be seen on my board in combination with a A3640, too. However, recapping and upgrading the 3640 to 3.2 seems to have solved the problem. So basically, there seems to be nothing wrong with the DiagROM but with our ancient machines... ;-)
During the DiagROM startup, before the menu is displayed, the rom checks for both A4000 and A1200 fast memory. There is an option here to abort the tests if you are really good at playing the mouse-button timing game, which makes me think that a freeze is sometimes expected?
However, if such a freeze occurs predictably and regularly, it seems to me that it might just be an issue. I am seeing 100% reproduction of a freeze/lock-up during the A1200 mem check portion in Amiga 4000s.
So far, I have NOT seen this problem on my A4000/030 or A4000EC/030 (both of which using the A3630 cpu card). However, I have seen the problem 100% of the time on A4000s with A3640 cpu cards, on both A4000s and A4000T boards. Playing the mouse button game allows me to get past this, and all other tests come out fine. The machines are a random mix of NTSC and PAL, so I don't think that matters.
The text was updated successfully, but these errors were encountered: