No. The 1200, 3000, 4000 all use 2 kickstart roms 16bit config.
Upon startup the roms are combined in a 32bit read.
The A3000 desktop was the only 2 rom machine that could use A2000
single roms by switching a jumper to A2000 compatible rom
mode. In this case you would remove both rom0 and rom1
and place the A2000 rom in the rom0 position.
The jumpers in question are J180 and J181. From the A3000
desktop service manual.
What real purpose other than repair house testing the
reverse compatibillity to 2000 roms would benefit
an end user is anyone's guess as you would loose the
internal A3000 SCSI controller using A2000 roms.
James Vigliotti
No. You're better off getting ReloKick to kick an image of your A500's
1.3 rom in your A1200. You will then only be able to use floppy though.
--
Marcel J. DeVoe - mde...@shore.net - Team *AMIGA*
A4091scsi CV64 96 megs CDRW M1764-17" Catweasel FUSION/Emplant
A4000/060 CyberStorm MKII overclocked 66mhz - see "How to Overclock!"
and "DIY A4000 Tower for $45" @ http://www.shore.net/~mdevoe
>No. You're better off getting ReloKick to kick an image of your A500's
>1.3 rom in your A1200. You will then only be able to use floppy though.
Aminet: util/boot/GetSCSI11.lha
I remember using this together with my MMU kicker, I might up that to
Aminet some day if I find it again. A lot of A500 games are useless
without RAM at $C00000, which is easily fixed with MMU.
Jorma
>>No. You're better off getting ReloKick to kick an image of your A500's
>>1.3 rom in your A1200. You will then only be able to use floppy though.
> Aminet: util/boot/GetSCSI11.lha
Okay, I finally tried that on my A4000 with 3.1 roms. Although there are
surprisingly quite a few differences between 3.0 and 3.1 (I have the
developer docs showing them) I don't thing there's much difference in the
scsi drivers.
OTOH, I made the mistake of using the above file after booting into my
AOS 3.9 Workbench, which creates a file image of the rom then alters
the scsi.driver to the new NSD standard for larger than 4 gig drives.
The resulting file was 15K in length. Realising this, and knowing after a
warm reset the kicked rom survives this, I created a copy of my original
WB 3.1 floppy and copied GetSCSI to it, turned off the computer to flush
out any residual memory and booted with that. Ran the program and then got
a scsi.driver file now only 10K in length.
One of my partitions is only 600 meg and I created a mount file for it
using parameters from HDToolbox, added it to the mount file on a copy of
my old Workbench 1.3 floppy, copied the scsi.device file to the floppy's
DEVS: drawer and then booted Relokick1.3.
No dice. Just the floppy came up.
Then I remembered I was using PFS3. Tried putting the "pfs3" file handler
in L: and made the change in the mount file to use it. But it still
didn't work. Then did a quick look at the PFS3 docs and it said
"Requirements: Workbench 2.0 and up".
Oh well. It was a nice attempt anyways. ;-)
I suspect though that even with FFS, it still wouldn't see my drives as
they were formatted with 3.1 and 1.3 won't recognise that format anyways.
Would be interested to see if anyone else with normal 3.1 FFS could do
this.
> I remember using this together with my MMU kicker, I might up that to
> Aminet some day if I find it again. A lot of A500 games are useless
> without RAM at $C00000, which is easily fixed with MMU.
Hey, the more programs on Aminet the better. ;)
> Jorma
Interesting idea! They are both 256k, 16 bits wide. I wonder how you would
suppress the other 3.0 chip.
Also, is there any point in it when there are softkick solutions available?
Relokick is simple to install and use.
--
--
My domain contains .co, not .com as appears in the header.
Patrick Ford Auckland, Aotearoa (New Zealand)
>tenu@sci*remove_me*.fi wrote:
>> I remember using this together with my MMU kicker, I might up that to
>> Aminet some day if I find it again. A lot of A500 games are useless
>> without RAM at $C00000, which is easily fixed with MMU.
>
>Hey, the more programs on Aminet the better. ;)
I found the program, sadly sources were lost a few years back in a HD
crash. It's a major hack requiring 68030 with MMU, I might now add
68040 support if I have time for that.
Jorma
> Interesting idea! They are both 256k, 16 bits wide. I wonder how you would
> suppress the other 3.0 chip.
dont have a clue is that needed?
>
> Also, is there any point in it when there are softkick solutions available?
> Relokick is simple to install and use.
just thought it would be cool with a switch.
-----------------------------------------------------------------------------
Hen...@gigahertz.se
FHB Gigahertz Västerås
> On 15 Jun 2001, Patrick Ford wrote:
>
> > Interesting idea! They are both 256k, 16 bits wide. I wonder how you would
> > suppress the other 3.0 chip.
> dont have a clue is that needed?
I doubt very much that anyone has ever done what you are trying to do. On
the face of it, your Amiga is going to be taking 32 bit reads where the
first 16 bits come from KS1.3 and the second 16 from KS3.0.
I have a sneaky suspicion it would get confused.
> > Also, is there any point in it when there are softkick solutions available?
> > Relokick is simple to install and use.
> just thought it would be cool with a switch.
Try Relokick. That really is cool to see that ugly old static hand appear
with NO hardware mod. Keep in mind that it is warm boot resistant, and has
no possibility of booting your A1200 HD. One guy panicked thinking it had
over written his physical ROM when it came comimg back after reboot.
>> > Also, is there any point in it when there are softkick solutions available?
>> > Relokick is simple to install and use.
>> just thought it would be cool with a switch.
> Try Relokick. That really is cool to see that ugly old static hand appear
> with NO hardware mod. Keep in mind that it is warm boot resistant, and has
> no possibility of booting your A1200 HD. One guy panicked thinking it had
> over written his physical ROM when it came comimg back after reboot.
I installed "ColdBoot" on a self-booting floppy to activate from it's
startup-sequence for just such occasions. It's the only thing that
breaks out of the loop. It works a little faster than a full power down,
as I have to go through 2 reboots from a power on and slow hard drive
spin ups.
> Patrick Ford <pa...@ihug.com.nz> wrote:
> > Henrik Berglund SdU wrote:
>
> >> > Also, is there any point in it when there are softkick solutions available?
> >> > Relokick is simple to install and use.
>
> >> just thought it would be cool with a switch.
>
> > Try Relokick. That really is cool to see that ugly old static hand appear
> > with NO hardware mod. Keep in mind that it is warm boot resistant, and has
> > no possibility of booting your A1200 HD. One guy panicked thinking it had
> > over written his physical ROM when it came comimg back after reboot.
>
> I installed "ColdBoot" on a self-booting floppy to activate from it's
> startup-sequence for just such occasions. It's the only thing that
> breaks out of the loop. It works a little faster than a full power down,
> as I have to go through 2 reboots from a power on and slow hard drive
> spin ups.
There's a utility called something like CheckLMB which is just ideal for
breaking regular Startup-sequence when the LMB is held down. It can divert
to another S-S to run Relokick.