CD32 custom kickstart?

[Amiga1992]

Can you make a custom CD32 Kickstart using remus?
iI know the CD32 is special and has that extended ROM, so I am not sure you could make your own kickstart, but it'd be useful, for example, to have an updated scsi.device in ROM for those of us that have TF328s.

[emufan]

the cd32 roms are somehow special, there is a good post already,
which results in a tool to automate the build process for the final rom.
but the tool is missing, while all the info is still there.

#1) did anyone grab the REAL_CD32_CONVERTER.ZIP tool, mentioned in the link above ?!

[Amiga1992]

So that means there's no real way to swap the scsi.device in the ROM itself
Oh well, rebooting once it is.
My main reson to want this is that many times after loading a whdload game, the scsi.device module reverts back to the original.

[emufan]

I think you can build the rom (standard + extended) with remus,
but the trouble was to make the final rom for the real hardware, the link gave the solution.

#1) here is a similar situation, which ends with the request for the tool above.

#2) pucci was here today, I write a PM - done

[fgh]

there are some sandisk cf cards that use 'illegal' CHS values (larger than 16383/16/63) and therefore are safe to use with the original scsi.device and a directscsi file system like pfs3aio.

This model was confirmed by Toni wilen and one more guy at the 16 and 32G versions, but you need to test it yourself as they could change the firmware anytime.
http://www.sandisk.com/home/memory-c...a-compactflash

The same is true for the old SDHC only SD-IDE adapters, as mentioned in the FAQ in my signature.

Edit: These cards would fail the 'check4g' and perhaps also 'hddreport' test tools, but pfs3aio does not mount unsafe partitions, so if it mounts you are good.

[Amiga1992]

The problem is also that skick would not work with the CD32 ROM. I need a way to test before even trying to burn to EPROM, and honestly, if I can softkick, I don't care about burning, even though I don't have that much Fast RAM.

[emufan]

Originally Posted by Akira

The problem is also that skick would not work with the CD32 ROM.

if I look in my rom folder, i only see combination of *.rom and *-ext.rom
for the CD32, this way you cannot softkick these.
with the missing tool, or someone who can make something from the pseudo code,
you will get a 1mb rom which you can test with softkicker or emulators(!?)
additionally there is no CD32 PAT/RTB for blitzkick (!?)

I cannot say if the above is all correct, but there seems to be noone with some insight here.

[Amiga1992]

Originally Posted by emufan

with the missing tool, or someone who can make something from the pseudo code, you will get a 1mb rom which you can test with softkicker or emulators(!?)

YEah but there's no PAT/RTB, so no skick.

[emufan]

Originally Posted by Akira

YEah but there's no PAT/RTB, so no skick.

may work on the emulators, dunno yet.
we should open a competition on Coders/System, give them the pseudo code,
and see if one succeeds. but don't tell them :/

[gulliver]

Why dont you use LOADMODULE to test the rom?

It has been already tested on a CD32.

[Amiga1992]

I mentioned before that I am already using loadmodule to have an updated scsi.device.
The problem is that many times on reboot the original gets restored and I have to go through another reset cycle to load it again, so it would be good to have a physical ROM with the updated scsi.device always present.

[gulliver]

Originally Posted by Akira

I mentioned before that I am already using loadmodule to have an updated scsi.device.
The problem is that many times on reboot the original gets restored and I have to go through another reset cycle to load it again, so it would be good to have a physical ROM with the updated scsi.device always present.

Then you could probably solve this in the startup-sequence by adding a version check in an IF statement and reload scsi device when suitable. in this way you can always make sure no matter what happens you get your desired scsi.device version.

[Amiga1992]

gulliver, I already have that.
The problem is, as I explained, that after resetting the unit after loading a WHDLoad game, SOME TIMES the original scsi.device is restored. Dunno why. It's like if I had turned the machine off and on (hard reset).

I'm just trying to save a reboot cycle here. Yes, I am being picky :P

[gulliver]

Originally Posted by Akira

gulliver, I already have that.
The problem is, as I explained, that after resetting the unit after loading a WHDLoad game, SOME TIMES the original scsi.device is restored. Dunno why. It's like if I had turned the machine off and on (hard reset).

I'm just trying to save a reboot cycle here. Yes, I am being picky :P

Maybe play with whdload options, or simply ask its developer, as that should not happen.

It is okay to be picky

[Amiga1992]

Originally Posted by gulliver

Maybe play with whdload options, or simply ask its developer, as that should not happen.

I don't know if it's a WHDLoad problem , maybe the CD32 always does a hard reset when you press the reset button?
I need to figure out if it happens EVERY time or not. More testing needed.

[fgh]

Akira: Did you see my post above?

[kolla]

Originally Posted by fgh

Akira: Did you see my post above?

It's the solution to a question he did not ask - scsi.device was just an example, there are also other things one may want to update in the kickstart.

[fgh]

Originally Posted by Akira

So that means there's no real way to swap the scsi.device in the ROM itself
Oh well, rebooting once it is.
My main reson to want this is that many times after loading a whdload game, the scsi.device module reverts back to the original.

Wonderful

[Amiga1992]

Originally Posted by fgh

Wonderful

I also don't want to change the CF card I am using, if that answers your question. So, good to know, but not an option in my particular case scenario.

Knowing if it is possible to make a custom CD32 ROM was the original question, and also knowing if the CD32 performas a hard reset on pressing the RESET button is also a related question. Because the updated scsi.device should not disappear from RAM on reset, so that's weird.

[solidcore]

Interestingly enough I too would like to modify an a1200 ks rom , anyone got the tools that work? experience doing it?

Edit: all sorted my end made a custom a1200 ks using https://github.com/cnvogelg/amitools...doc/romtool.md

Akira, that tool has support for cd32 rom split down to modules and re-pack with any modules you want