soft kicking A500 1.3->2.04
yock...@fuse.net
ago, before I did the 1 meg chip ram hack, I was able to use mkick to
soft kickstart my 500 into 2.04(37.175). Of course I couldn't do
anything with only 200 odd K of memory available, but it let me see
some stuff with 2.04. Then I did the hack and I no longer could soft
boot the same way; ata all actually. I didn't worry too much because I
had ordered 8 MB (Elbox 500/8)of fast ram and would be able to do it
then, or so I thought. Now I have 8 MB's of fast 1 MB of chip and I
still can't soft kick. I have tried mkick, zkick and kickit to no
avail. Mkick actually loads the kickstart and reboots but crashes, I
have tried using different command line options but nothing seems to
help. Zkick always complains that there is an error loading the
kickstart file even though it worked once upon a time with mkick.
Kickit crashes also when rebooting, loading a kickfile name
kick.32e.20. Am I doing something wrong or are all of these kickfiles
hosed up in some way. I know that their origin is somewhat dubious, but
the fact that the 37.175 did work.....I don't understand. The
alternative is that the memory board is somehow the problem, I'm not
sure how that could be though, seems to work fine. Any thoughts, aside
from, "go buy the ROM!". I'm sure I'll end up buying the ROM, it will
get old having to constantly have to load the kickstart then boot the
workbench (all from floppies), but right now this is somewhat
convenient and immediate.
Comcast GigaNews
use SKick for my A2000 again when I get room to put it up for use. Need to
get rid of like 2 PCs and 3 Macs first though.
<yock...@fuse.net> wrote in message
news:1169422790.3...@v45g2000cwv.googlegroups.com...
Thomas Richter
> Maybe this isn't the correct place but here it goes anyway. A few weeks
> ago, before I did the 1 meg chip ram hack, I was able to use mkick to
> soft kickstart my 500 into 2.04(37.175). Of course I couldn't do
> anything with only 200 odd K of memory available, but it let me see
> some stuff with 2.04. Then I did the hack and I no longer could soft
> boot the same way; ata all actually.
That's because the v33 and v34 Roms have a bug that cause all memtags
to be invalidated if more than 512KB chip ram is available. SetPatch v34
patches around it by using ColdReboot, but that vector is also likely
required for the kickstart mappers.
> I didn't worry too much because I
> had ordered 8 MB (Elbox 500/8)of fast ram and would be able to do it
> then, or so I thought. Now I have 8 MB's of fast 1 MB of chip and I
> still can't soft kick.
That 8MB is likely autoconfig memory, and for that purpose useless for
ROM remapping. First of all, it goes away on a reset until it is
re-configured by the expansion library, and then it is too late for
the kickstart remapper to hook in, and second you still figure the
ROM bug of V33 which won't you have any resident programs either without
SetPatch, and neither with SetPatch because the remapper and SetPatch
use the same vector. And a remapper in the KickMemTags won't work either
because the expansion ram will be configured too late, or not available.
> I have tried mkick, zkick and kickit to no
> avail. Mkick actually loads the kickstart and reboots but crashes, I
> have tried using different command line options but nothing seems to
> help. Zkick always complains that there is an error loading the
> kickstart file even though it worked once upon a time with mkick.
> Kickit crashes also when rebooting, loading a kickfile name
> kick.32e.20. Am I doing something wrong or are all of these kickfiles
> hosed up in some way.
First of all, this kind of hack won't work, not stable at least.
Kickstart remapping means that the old ROM has to start, and then the
new one has to replace the old one on the fly, with some parts of the
ROMs already configured. Especially, it is likely that your 8MB
expansion RAM won't work with the kickstart replaced.
> I know that their origin is somewhat dubious, but
> the fact that the 37.175 did work.....I don't understand. The
> alternative is that the memory board is somehow the problem, I'm not
> sure how that could be though, seems to work fine. Any thoughts, aside
> from, "go buy the ROM!".
GO, Buy the d*mn ROM. Is that better? It won't work otherwise...
> I'm sure I'll end up buying the ROM, it will
> get old having to constantly have to load the kickstart then boot the
> workbench (all from floppies), but right now this is somewhat
> convenient and immediate.
So long,
Thomas
Clockmeister
I used Skick to boot my old A2000 to KS3.1 from memory and Mkick to boot my
A1000 to 3.1. The trick was to find the right combination of KS ROM file and
PAT file (where applicable). You must use a KS from an A500/A2000 or it
won't work at all.
Softkicking does cause stability problems and buying the ROM really is the
best option.
user
"Clockmeister" <whow...@andwhy.com> wrote in message news:12r9n5e...@corp.supernews.com...
Would the kickrom for an A600 work? (kick40063.A600) As i`ve got both the .pat & .rtb files that match the rom.
If not, I`ve got a real A600 rom V37.300 spare....any good for the A5?
Clockmeister
"user" <noemail.com> wrote in message
news:45b51f7a$0$21086$afc3...@news.optusnet.com.au...
Should work yes since a real A600 ROM will work in an A500/A2000.
> If not, I`ve got a real A600 rom V37.300 spare....any good for the A5?
>
Yep.
You sure get around Mr user, I see you in just about all the newsgroups I
frequent ;-)
user
"Clockmeister" <whow...@andwhy.com> wrote in message news:12ra9e5...@corp.supernews.com...
Lol...I`m stalkin` ya clocky.
Thanks for the quick replies
user
As far as I can see (not too far :):, MKick should work for you; but use the command> MKick GUI in startup-sequence; then you can
select which way you`d like the rom to be loaded; (and use an earlier `arp.library` v39+...the one from DOpus4 works...but not the
V40 from aminet, as it crashes the emulated A500)
I`ve spent a couple of spare moments experimenting with both the 37175 & 40063 roms on my A600 (and have a couple of pre-prepared
diskimages if you`d like them); and found that both load in chip mem with SKick in the A600 (don`t have the A5).... (need 2.04
rom..I`ve got one...just pay the postage...or go straight to a 3.1 chip)
..Mkick needs a 1.3 rom to load...later, if you reply:)
yock...@fuse.net
user wrote:
>
> As far as I can see (not too far :):, MKick should work for you; but use the command> MKick GUI in startup-sequence; then you can
Seems like I tried this from a shell window and it didn't work....I
thought you had to have 2.0x ROM for GUI mode?
> select which way you`d like the rom to be loaded; (and use an earlier `arp.library` v39+...the one from DOpus4 works...but not the
> V40 from aminet, as it crashes the emulated A500)
>
What version comes with the ARP 1.3 package? That's what I'm using.
> I`ve spent a couple of spare moments experimenting with both the 37175 & 40063 roms on my A600 (and have a couple of pre-prepared
> diskimages if you`d like them); and found that both load in chip mem with SKick in the A600 (don`t have the A5).... (need 2.04
> rom..I`ve got one...just pay the postage...or go straight to a 3.1 chip)
This sounds like a distinct possibilty!
> ..Mkick needs a 1.3 rom to load...later, if you reply:)
Got that. More experimenting tonight; I tried messing with the jumpers
on the Elbox to make it non-autoconfiguring and using the addmem option
of mkick....didn't help.
user
<yock...@fuse.net> wrote in message news:1169558811.4...@s48g2000cws.googlegroups.com...
>
> user wrote:
> >
> > As far as I can see (not too far :):, MKick should work for you; but use the command> MKick GUI in startup-sequence; then you
can
>
> Seems like I tried this from a shell window and it didn't work....I
> thought you had to have 2.0x ROM for GUI mode?
>
No, you don`t...just need the right combination of past experience...and then some:)
Want the disk-images?
user
yock...@fuse.net
user wrote:
>
> No, you don`t...just need the right combination of past experience...and then some:)
>
> Want the disk-images?
>
>
Sure.
user
<yock...@fuse.net> wrote in message news:1169567405.0...@s48g2000cws.googlegroups.com...
You can wite .adf`s y/n?
user
<yock...@fuse.net> wrote in message news:1169567405.0...@s48g2000cws.googlegroups.com...
And then some!....
yock...@fuse.net
.adfs are fine.
user
<yock...@fuse.net> wrote in message news:1169582355.0...@m58g2000cwm.googlegroups.com...
So, where do I send them to....Jupiter2?
yock...@fuse.net
> >
>
>
> So, where do I send them to....Jupiter2?
Well, the domain is fuse.net and the user is yock1960.
Thanks.
user
<yock...@fuse.net> wrote in message news:1169591125.1...@l53g2000cwa.googlegroups.com...
>
> > >
> >
> >
> > So, where do I send them to....Jupiter2?
>
> Well, the domain is fuse.net and the user is yock1960.
>
> Thanks.
>
Too obvious, that`s why I haven`t sent yet...give us half an hour.
user
<yock...@fuse.net> wrote in message news:1169591125.1...@l53g2000cwa.googlegroups.com...
>
> > >
> >
> >
> > So, where do I send them to....Jupiter2?
>
> Well, the domain is fuse.net and the user is yock1960.
>
> Thanks.
>
Emails sent.
And if anyones` got a problem about rom distribution...too `F`in bad.
Here`s Cloanto`s webpage for either/neither/both Amiga Forever and/or Amiga Explorer (an absolute must for ADF<>Disk transfers) :P
user
"user" <noemail.com> wrote in message news:45b6f98c$0$9772$afc3...@news.optusnet.com.au...
http://www.amigaforever.com/ae/
http://download.cloanto.com/download/amigaforever/aesetup.exe (free to download, Buy - $19.95)