Remapollo for A4060

[Marmes]

Quickrom maybe

[PanterHZ]

Another probably dumb/obvious question, but if the RemApollo tool "breaks" when using anything newer than BB2, why not just get rid of it and use another tool out there to load Kickstart into RAM?

Well, the thing is that all softkickers out there have this problem with OS3.9 and BB2 update, where SetPatch does something that makes the softkicker belive that KS ROM haven't been copied to RAM, so it does this again and reboots. Next up, SetPatch belives that the BB2 update haven't been loaded, so it does this again and reboots.

And this goes on and on in a never ending loop.

I bypass this problem on my KS2.05 Amiga 600. Here I use a tool for checking the KS version, and if it's lower than 40, then ACAtune is used for softkicking a KS3.1 ROM file. Otherwise, no softkicking is attempted.

[PanterHZ]

No, you still do not understand. If a module is in ROM, LoadModule will replace it. Only then. If you leave a module out, LoadModule will not touch it, and "ramlib" will pick it up. Exactly from the same place. This is *intentional* so you can replace the ROM with any other version, and you do not need to move the modules around.

It is really a bad idea to keep the modules in a separate place because them Ramlib will not be able to find them.

Maybe it could be an idea to make some kind of ListModule tool to go with LoadModule? This tool could then be used for scanning through the boot partition, where it displays all modules that LoadModule will find and prefer to use.

This would give the user a better overview of what LoadModule actually does.

[PanterHZ]

Well all I wanted to know was how to rekick with remapollo or if there is a good alternative for rekicking ROM.

You already have the most suitable tool installed. I promise you that it won't get any easier with another one

The main problem is that you have way too much (non standard) stuff going on in your Startup-Sequence, so it's not easy to pinpoint the exact reason for all the issues. I have tried to explain what you can do, but I realize that it may all sound a bit confusing.

So below is hopefully a more simpler explenation of what you can try, which sticks to the most basics of OS3.9 with Boing Bag 2 only (nothing more, nothing less) :


1. Do as I mentioned in another post regarding workbench.library and icon.library. In other words, copy them to the LIBS:OS3.9 dir, and rename or delete the ones in LIBS:


2. Make sure that the C:RemAPollo line looks exactly like this (everything on ONE line):

C:RemAPollo QUIET MAC Modules LIBS:OS3.9/OS_Module1 OS_Module2 OS_Module3 OS_Module4 OS_Module5 OS_Module6 OS_Module7 OS_Module8 OS_Module9  workbench.library  icon.library


3. Disable the C:LoadResident and C:LoadModule lines for now by inserting a semi-colon at the beginning of the line (you can deal with these later). The lines should then look like this:

;C:LoadResident >NIL: DEVS:trackdisk.device

;C:LoadModule >NIL: DEVS:battmem.resource DEVS:console.device DEVS:FileSystem.resource DEVS:misc.resource DEVSotgo.resource L:FastFileSystem L:Ram-Handler L:Shell-Seg LIBS:dos.library LIBS:layers.library REVERSE NOREBOOT


4. There is no need for SetPatch to have anything to do with the BB2 ROM updates, since this is already taken care of by RemAPollo. So change this line from:

C:SetPatch SKIPROMUPDATES console.device,dos,filesystem,FileSystem.resource, ram-handler,shell QUIET

to:

C:SetPatch NOROMUPDATE QUIET


5. Save the Startup-Sequence and turn off the Amiga. After a couple of seconds, turn it on again, and now the Amiga should hopefully boot into Workbench.



If the above doesn't work, it may be the result of issues with your 68060.library.

[Marmes]

What version of remapollo you use?
In my A4000D I have 2 behaviours.
On version 1.7
if I use the
If WARN
RemAPollo ....
EndIf
...
It doesn't work, Computer freezes.
On version 1.8 I have to use If WARN.... Or it won't softkick.
In either  versions I cannot use DRAP.
According to instructions we have to apply a ptch to 68060.library (60.10), wich I did. (I followed the instructions).
If I use skipromupdate ... it works.
If I use NOROMUPDATE quiet, it doesn't softKick.
Everything works, I understand what you say, I tried it, but maybe I'm still missing something.
From what I see now, only a few parts are rekicked, so, the best solution is to :
a) Make a rom and rekick it by software with your favourite requicker. (but that will still bring you trouble with scsi.device in apollo.
b) Burn ROMs the way you want and simplify S-S by removing manythings.

You already have the most suitable tool installed. I promise you that it won't get any easier with another one

The main problem is that you have way too much (non standard) stuff going on in your Startup-Sequence, so it's not easy to pinpoint the exact reason for all the issues. I have tried to explain what you can do, but I realize that it may all sound a bit confusing.

So below is hopefully a more simpler explenation of what you can try, which sticks to the most basics of OS3.9 with Boing Bag 2 only (nothing more, nothing less) :


1. Do as I mentioned in another post regarding workbench.library and icon.library. In other words, copy them to the LIBS:OS3.9 dir, and rename or delete the ones in LIBS:


2. Make sure that the C:RemAPollo line looks exactly like this (everything on ONE line):

C:RemAPollo QUIET MAC Modules LIBS:OS3.9/OS_Module1 OS_Module2 OS_Module3 OS_Module4 OS_Module5 OS_Module6 OS_Module7 OS_Module8 OS_Module9  workbench.library  icon.library


3. Disable the C:LoadResident and C:LoadModule lines for now by inserting a semi-colon at the beginning of the line (you can deal with these later). The lines should then look like this:

;C:LoadResident >NIL: DEVS:trackdisk.device

;C:LoadModule >NIL: DEVS:battmem.resource DEVS:console.device DEVS:FileSystem.resource DEVS:misc.resource DEVSotgo.resource L:FastFileSystem L:Ram-Handler L:Shell-Seg LIBS:dos.library LIBS:layers.library REVERSE NOREBOOT


4. There is no need for SetPatch to have anything to do with the BB2 ROM updates, since this is already taken care of by RemAPollo. So change this line from:

C:SetPatch SKIPROMUPDATES console.device,dos,filesystem,FileSystem.resource, ram-handler,shell QUIET

to:

C:SetPatch NOROMUPDATE QUIET


5. Save the Startup-Sequence and turn off the Amiga. After a couple of seconds, turn it on again, and now the Amiga should hopefully boot into Workbench.



If the above doesn't work, it may be the result of issues with your 68060.library.

[PanterHZ]

What version of remapollo you use?
In my A4000D I have 2 behaviours.
On version 1.7
if I use the
If WARN
RemAPollo ....
EndIf
...
It doesn't work, Computer freezes.
On version 1.8 I have to use If WARN.... Or it won't softkick.
In either  versions I cannot use DRAP.
According to instructions we have to apply a ptch to 68060.library (60.10), wich I did. (I followed the instructions).
If I use skipromupdate ... it works.
If I use NOROMUPDATE quiet, it doesn't softKick.
Everything works, I understand what you say, I tried it, but maybe I'm still missing something.
From what I see now, only a few parts are rekicked, so, the best solution is to :
a) Make a rom and rekick it by software with your favourite requicker. (but that will still bring you trouble with scsi.device in apollo.
b) Burn ROMs the way you want and simplify S-S by removing manythings.

I'm using RemAPollo 1.7 on my Amiga 1200 with Apollo 1240 card, and I use a patched version of the standard 68040.library. I haven't tried RemAPollo 1.8 yet, since I wasn't aware of this version.

If you have the lines like this in your Startup-Sequence:

;C:DRAP
If WARN
RemAPollo ....
EndIf

Then whatever is between the "IF WARN" and "EndIf" lines will be skipped since there's nothing above them that may give a return code of 5 (WARN) or more. This has nothing to do with DRAP or RemAPollo, or anything else really, it's just how the Amiga works :-)
In other words, without any DRAP, no remapping will even be attempted.

But just to rule things out: When you used the RUX tool for extracting modules from the ROM Update, did you remember to use the correct argument? This can either be A600, A1200, A3000, A4000I or A4000S, but in your case it should be one of the last two (A4000I for IDE controller, and A4000S for SCSI controller).

What kind of zorro cards do you have installed in your Amiga (if any)? RemAPollo.doc mentions that there might be issues with certain cards.

[Marmes]

I did exactly like it says on remapollo.doc.
rux  AmigaOS ROM Update A4000i
It gave me 9 OS_Module1-9, wich I put on the recommended drawer. DRAP just hangs.
Don't know why.
Anyway I found an easy way, maybe not the best. I just use SKIPROMUPDATE . It's important to skipromupdate scsi.device, that's what causes the problems. Then I use Quickrom. It works fine. KSRemap from GVP also works fine.

[PanterHZ]

I did exactly like it says on remapollo.doc.
rux  AmigaOS ROM Update A4000i
It gave me 9 OS_Module1-9, wich I put on the recommended drawer. DRAP just hangs.
Don't know why.
Anyway I found an easy way, maybe not the best. I just use SKIPROMUPDATE . It's important to skipromupdate scsi.device, that's what causes the problems. Then I use Quickrom. It works fine. KSRemap from GVP also works fine.

But if it's just scsi.device that causes problems, it should be really easy to fix. Just remove OS_Module6 (scsi.device) from the RemAPollo line, so it looks like this:

C:RemAPollo QUIET MAC Modules LIBS:OS3.9/OS_Module1 OS_Module2 OS_Module3 OS_Module4 OS_Module5 OS_Module7 OS_Module8 OS_Module9 workbench.library icon.library

I had to do this myself, since I use IDEfix which requires original scsi.device.