hi everyone,
thanks for your replies :-)
yes, I've already done a couple of things:
- M1230XA disk installed, setup utility, etc.
- reseated and tested five different RAM SIMMs
- replaced all capacitors on the board with new ones
- replaced battery with a new one
- tested in both kickstart 3.0 and 3.1 Amiga 1200s
my M1230XA has a 68RC030@50mhz, no FPU, no RAM
SetXA utility is set to these specs/values.
this is the situation:
- clock works (with a new battery)
- SetXA works: board recognized, "test" jumper recognized
- SetXA says: Hardware version: 0
- eeprom works: SetXA settings remembered
- processor (w. MMU) recognized by "showconfig" and SysInfo
- SysInfo shows 68030, MMU. speed results: ~1.5 times speed of a stock A1200 (~1800 dhrystones)
- board not listed under "Boards" in Early Startup, and not listed by "showconfig"
- so far: same situation on both ks3.0 and ks3.1
now when i install some RAM:
- under ks3.0 "AddXAMem" (or SetXA "Add memory") crashes the machine. new memory shows up for a second in WB title bar, then both chip- and fast-mem go to zero, then machine becomes unusably slow and has some screen corruption.
- under ks3.1 machine does not boot (power-led, keyboard led blinks, no floppy click, black screen)
the speed increase when installing the board is very little (see above).
(note the results at
http://amiga.resource.cx/perf/aibb.html : m1230xa without RAM listed with about 4-5 times the speed of a stock A1200)
but I've tested with a (proved working) Blizzard1230 (FPU, no RAM, no maprom), and the results are about the same (~1.5 times A1200 speed), so the missing RAM might slow down the m1230xa (drastically).
currently, I'm drawing this conclusion:
the board works fine, except for anything RAM-related.
still I'd like to see some screenshots from a working M1230XA without RAM installed:
- does it show up in early startup menu -> boards? (kickstart 3.1 only?)
- does it show up in showconfig?
- is SetXA's "Hardware version: 0" info correct?
- what are SysInfos speed results?
...just to confirm what I see with my board.
I dont know how AutoConfigging works, if it's the same process that gets triggered by "AddXAMem" (or "SetXA add memory"), if the board MUST show up regardless of some AutoConfig function is has or hasn't, etc. - but we'll find out when we get there... ;-)