exxos's Atari, Amiga & retro forum

rubber_jonnie wrote: 14 Feb 2025 14:51 After some fun and games I finally got the BooBips working with KS 2.04 and can boot to WB2.

Not sure why but whatever ROM I programmed in it wouldn't work, even byte swapped, but now it's OK. Need to try a higher version next.

Could it be down to size? KS1.3 & KS2.04 fit in 256KB (27C200) but KS3.1 is 512KB (27C400).

Did you switch to 27C400 in the BooBips settings?

https://www.boobip.com/hardware/27C400_ ... uick-start

Perhaps your motherboard version doesn't support 512KB ROMs without a modification for the upper address line? I've seen ROMs with wires fitted from the GARY before (but I thought that was for 1MB?).

alexh wrote: 14 Feb 2025 14:57

rubber_jonnie wrote: 14 Feb 2025 14:51 After some fun and games I finally got the BooBips working with KS 2.04 and can boot to WB2.

Not sure why but whatever ROM I programmed in it wouldn't work, even byte swapped, but now it's OK. Need to try a higher version next.

Could it be down to size? KS1.3 & KS2.04 fit in 256KB (27C200) but KS3.1 is 512KB (27C400).

Did you switch to 27C400 in the BooBips settings?

https://www.boobip.com/hardware/27C400_ ... uick-start

Perhaps your motherboard version doesn't support 512KB ROMs without a modification for the upper address line? I've seen ROMs with wires fitted from the GARY before (but I thought that was for 1MB?).

I followed the guide over at BooBip to the letter and it's been set to 27C400 all along. What was odd is that I erased the version I have of KS1.3 then afterwards the only thing I could make work is DiagROM.

Mine is a V6. The current 2.04 ROM file is 512K from Amiga Forever. Works fine.

rubber_jonnie wrote: 14 Feb 2025 16:22 The current 2.04 ROM file is 512K.

My bad. So no reason why 3.1 wouldn't work (unless it was Amiga Forever encrypted version). If you wanted to try to dump it from inside WinUAE using transROM or whatever that would remove said encryption

alexh wrote: 14 Feb 2025 16:48

rubber_jonnie wrote: 14 Feb 2025 16:22 The current 2.04 ROM file is 512K.

My bad. So no reason why 3.1 wouldn't work (unless it was Amiga Forever encrypted version). If you wanted to try to dump it from inside WinUAE using transROM or whatever that would remove said encryption

No worries, and I did try byteswapping as well, but no joy.

I'll see what I can do about dumping 3.1, good idea.

alexh wrote: 14 Feb 2025 14:57 Your motherboard version doesn't support 512KB ROMs without a modification for the upper address line? I've seen ROMs with wires fitted from the GARY before (but I thought that was for 1MB?).

The rev 6a board has a fix for this, only older revisions need a wire.

Good news that you got it sorted! :D
And those Agnus sockets have a tendency to die, so a new and fresh one is certainly an improvement!!

Did you do the chip mod already?

I would use the newest kickstart available (3.2.2) (rom and install) to get the newest HDToolbox.

Maximilian wrote: 14 Feb 2025 17:14

alexh wrote: 14 Feb 2025 14:57 Your motherboard version doesn't support 512KB ROMs without a modification for the upper address line? I've seen ROMs with wires fitted from the GARY before (but I thought that was for 1MB?).

The rev 6a board has a fix for this, only older revisions need a wire.

Good news that you got it sorted! :D
And those Agnus sockets have a tendency to die, so a new and fresh one is certainly an improvement!!

Did you do the chip mod already?

No I didn't do the chip mod as the trapdoor RAM is now working.

It's prepared if I decide to do it later.

Maximilian wrote: 14 Feb 2025 17:17 I would use the newest kickstart available (3.2.2) (rom and install) to get the newest HDToolbox.

I now have 3.1 working:


It turns out that with the upgrade I have, it behaves a bit oddly in that I get a black screen during boot, and the CPU takes a bit longer to start than the standard CPU.

Eventually it boots to Workbench just fine. I guess I'm just too impatient...

So just waiting for the CF-IDE adapter to arrive before I can give installing WB onto the A500 hard drive.

In the meantime I've been looking at the keyboard as these keys are bad:


It's not the end of the world as I probably won't use the keypad much, if at all, but I do like to have things fully functional. Annoyingly my carbon paint pen is either dried up or empty so I can't refresh the pads.

Also I can't find a keyboard matrix as I want to look for commonalities in the bad keys so I can trace it as it may be simply a corroded trace, but I want to work out where best to look. Back to the internet!

CF adapter just arrived, so I think I'll reassemble the keyboard and get on with installing WB ti the HDD.

It looks like I need a new membrane anyway, after tracing some of the tracks around the keys that don't work I do have bad connectivity. Maybe I'll get another carbon pen to try first.