Amiga.org
Amiga computer related discussion => Amiga Hardware Issues and discussion => Topic started by: guest1255 on March 12, 2004, 04:50:42 PM
-
Can an Amiga 500 1.3 rom updated to 2.04? In a legall way?
Thanks.
Apache2k :-?
-
Sure, just buy a Kick2.05-ROM (a bit better than the 2.04).
Should work like a treat when the A500 isn't one of the very
first (those may need a bit solderings).
-
Does it mean that i have to remove the old rom or is it a software issue? Sorry for the dum question i dint find a similar topic here.
Apache2k
-
Yes you have to remove the old ROM, to find place for the new one :-o
If you still want to play all the old 1.x-only games, you might
want to purchase a Kickswitch too. That would allow you to have
2 (sometimes even 3) ROMs inside of the A500.
-
Thank you.
Apache2k
-
You could use a rom chip out of an amiga 600 as they are cheap to buy. :-)
-
On a side note,
since upgrading from 2.04 to 2.05 my OS 2.1 - Setup won't boot, any idea why??
It stops showing a clock on the Workbench.
Have fun,
McTrinsic
-
And on another side note, I have an A600HD in which I have tried to put a larger HD - I'm having troubles getting the thing to boot - and I heard that the 2.04 ROM doesn't support HDs over 40MB...Can anyone confirm this? And does anyone know where to get the 2.05 ROM from if this is the case?
Ta
-
@Cyberus
AFAIK there is absolutly NO HD-support build into 2.04-ROMs,
atleast not in the 16-bit-wide one, and a 32-bit one would
only support the A3000's SCSI-controller, not the IDE of the
A600.
-
@McTrinsic
C= had to make space for the SCSI.device (for IDE), the PCMCIA.device,
and therefore threw out some misc libs which now have to be
loaded from disk. Same happened later with the 3.1-ROMs for
the A4000T which had both SCSI and IDE (and both needed ROM-
space).
It might be that the 2.1-installer detected a 2.04-ROM and
therefore didn't install these. Try running the installer
again, or search for libs found on the WB2.1-floppy which
are missing on your HD. Another possibilty would be SnoopDos
(not sure wether that will work on 2.x), and a boot without
startup-sequence.
-
Oh, and you may try renaming the WBStartup-drawer.