romfixes

[maxx11111]

Hi I've been playing around with creating my own custom 3.9 rom and it works well but looking at adding updated stuff ect an was looking at romfixes from blizkick but don't seem to be able to find out what it "fixes" does anyone know?

Thanks

[slaapliedje]

I was thinking of doing the same thing, which is why I ordered one of the 'ROMY' (which allows 1MB kickstart roms) chips, though I need to get an EEPROM burner to put it into the real Amiga after I test it in WinUAE.

I was thinking of trying to put in the 68060.library or something, I do know probably the easiest way to see what needs to be put in a custom rom is to see what startup-sequence has in the patches file, also probably to include the rom update from 3.9 BB2.  That would at least save the reset.

slaapliedje

[utri007]

Are you using this guide http://www.mfilos.com/2010/12/guide-create-and-burn-custom-kickstart.html

There is a small error, DummyCDStrap is needed if your CPU has a MMU, not just if you have BlizzardPPC. MMU blocks memory area used By extended part of rom, it will work but it is bog slow.

Did you managed to get this working, it is best possible scsi.device around http://aminet.net/package/driver/media/SCSI4345p

There is also a problem, needed exctractmodule command is not availlable where guide says, you can get it here http://aminet.net/package/util/boot/PatchRAM

Peterk's icon.library is also very usefull/excellent

Blizkick guide tells very well what those romfixes does?

Best thing with custom 1mb rom with newer scsi.device and filesystems is that it removes all the hasle with hard drives, prety much every hard drive works.

[slaapliedje]

I believe in my particular case, I'd want to use the scsi.device that is installed when the system boots up with the Fast ATA MK-VIII, correct?

slaapliedje

[utri007]

I don't know? Does it have it own scsi.device? My rom works just fine with ide-fix express, wich is similar product.

[matthey]

Hi I've been playing around with creating my own custom 3.9 rom and it works well but looking at adding updated stuff ect an was looking at romfixes from blizkick but don't seem to be able to find out what it "fixes" does anyone know?

I don't use any of the Blizkick patches for an AmigaOS 3.9 kickstart which includes many fixes already. I do use the Remus patches called Patchmath020_All and NoClick in the BK_Mods directory of Remus but they are not necessary. These modules can be added at the bottom of the ROM contents in Remus.

For a 512kB kickstart, split the AmigaOS 3.9 BB2 update (no more double reboot is necessary with these) which will give:

bootmenu 44.7
console.device 44.8
exec 45.20
FileSystem.resource 45.10
(Fast)FileSystem 45.13
scsi.device 43.43
ram-handler 44.23
shell 45.7

Then replace with newer versions from the unofficial AmigaOS 3.9 Boing Bag updates:

console.device 44.10
FastFileSystem 45.16
layers.library 45.24
mathieeesingbas.library 40.4 (or hsmathlibs)
ram-handler 44.24
scsi.device 43.45 (or higher as there are several patched versions)
shell 45.27
icon.library 46.4.411 (Peter K)

Optional if using USB and requiring splitting the input.device from the gameport.device and keyboard.device:

input.device 50.26 (Ralph S from the Poseiden package)

This input.device allows USB devices from the boot menu. It will be slow on some hardware as it uses address 4 to get the exec base rather than caching it and it suffers from optimization issues. I have an incomplete input.device which fixes most of these problems but needs more work and testing.

Some hardware specific drivers can also go in the kickstart. The new workbench.library will no longer fit and should be left out (like with the 4000T).

I was thinking of doing the same thing, which is why I ordered one of the 'ROMY' (which allows 1MB kickstart roms) chips, though I need to get an EEPROM burner to put it into the real Amiga after I test it in WinUAE.

Most accelerators only support a 512kB kickstart for MAPROM. Hardware which supports a 1MB kickstart includes some ACA accelerators, Deneb, eFlash, and maybe some new FPGA accelerators and Amigas.

I was thinking of trying to put in the 68060.library or something, I do know probably the easiest way to see what needs to be put in a custom rom is to see what startup-sequence has in the patches file, also probably to include the rom update from 3.9 BB2.  That would at least save the reset.

ThoR's 68060.library will not work in kickstart which has further requirements than a normal library. Another 68060.library may work from kickstart but would not be activated until SetPatch so there isn't much advantage. It would be possible to activate a 68060.library earlier in kickstart but it would require modification of the 68060.library or adding another program in kickstart to activate it.

[Tenacious]

Forgive my ignorance on this topic.    How tough would it be to make a ROM that would allow an Amiga boot from an attached CDrom drive (like all the other platforms can do).  Only CDTV, A570, and CD32? can do this currently.

[utri007]

Most accelerators only support a 512kB kickstart for MAPROM. Hardware which supports a 1MB kickstart includes some ACA accelerators, Deneb, eFlash, and maybe some new FPGA accelerators and Amigas.

A4000 reguires additional tinkering to get it work with 1mb rom, but it is easy for A1200/A600. Even if accelerator doesn't support 1mb rom with maprom, it is still possible to get ROM to fast, easiest one is CPU FASTROM >NIL:

Blizkick doesn't support 1mb rom, but RemApollo 1.8 does http://www.ppa.pl/programy/remapollo-1.8.html

There is some disadvantages if workbench.library is left out, it can make life little harder certain problem situtations.

Forgive my ignorance on this topic. How tough would it be to make a ROM that would allow an Amiga boot from an attached CDrom drive (like all the other platforms can do). Only CDTV, A570, and CD32? can do this currently.

Nobody hasn't succeeded that. I tried to found cd filesystem wich would be rommable, I didin't found one. CDTV/CD32 filesystems doesn't work, I tested them.

[matthey]

Forgive my ignorance on this topic.    How tough would it be to make a ROM that would allow an Amiga boot from an attached CDrom drive (like all the other platforms can do).  Only CDTV, A570, and CD32? can do this currently.

1) A CD-ROM file system is needed which is ROMable. This likely already exists.

2) A ROMTag started program would need to be created and go in kickstart to detect and mount the CD-ROM. This would be difficult supporting all SCSI, IDE and USB CD-ROM drives while supporting a specific known drive at a specific location like the CDTV, A570 or CD32 would still be tricky but much easier. Scanning for drives at different locations would likely substantially slow booting. It may be possible to update the bootmenu or other components in the kickstart to do the mounting.

It should be possible on most Amigas to configure a CD-ROM file system after the cold bootup so that it will survive a reset and boot off the CD-ROM on warm resets without modifying the kickstart. There is a mechanism in AmigaOS for this which has existed for a long time. A smart CD-ROM file system could have this option to survive resets for booting purposes (maybe it already exists). AmigaOS 3.9 installs a smarter warm reset bootmenu than what is in the AmigaOS 3.1 ROM cold reset boot menu which has a better chance of handling a CD-ROM or USB file system. It might be worth experimenting if AmigaOS 3.9 was still being developed or there was a good open source CD-ROM file system which supported all CD formats.

The 68060.library support code would need to be installed before the CD-ROM boots in order to use most CD32 CDs. The 68060 is missing integer 68020 instructions and will crash without the support code installed (usually happens with SetPatch). The 68040 has all integer instructions but needs 68040.library support code if the FPU is used. CD32 and CDTV CDs may need other kickstart modules as well which would likely require a 1MB kickstart.

AmigaOS 68k and CD-ROM file systems are no longer being developed. ThoR doesn't seem interested in making his 68060.library ROMable and it is the last to get updates. Without a combination of changes in these components, it is unlikely we will ever see proper USB, media card or CD-ROM booting support. New specific 68k Amiga hardware wouldn't have to support as many hardware options so an update to support them is possible if they turn out to be popular. AROS has the necessary components for booting off a wide variety of media and may be another option for the 68k.

[utri007]

Rommable cd filesystem could be handy, it would allow mounting cd-rom with any boot disk wich has normal 2.0-3.1 c: drawer. Could be time saving and make OS installation much easier, even if boot from cdrom wouldn't be possible.

When I made my custom rom, I wanted to make life easier. I would say I succeeded prety well. No more problems with hard drives, all poosible filesystems FFS/SFS/PFS, PCMCIA resest fixes and compaqflash.device wich does what  cd-rom couldn't, it mountable with any boot media.

[paul1981]

I believe in my particular case, I'd want to use the scsi.device that is installed when the system boots up with the Fast ATA MK-VIII, correct?

slaapliedje

Yes, the FastATA driver is all you need, any updates to scsi.device isn't relevant under normal use. If you'd like large hard drive support from cold boot (with a custom rom or whatever) then I'd guess you'd still be able to achieve that with an updated scsi.device in rom, but obviously the FastATA driver will still need to be run, or your FastATA card it will just act the same as the onboard IDE (PIO 0 and the one IDE port).

[maxx11111]

Are you using this guide http://www.mfilos.com/2010/12/guide-create-and-burn-custom-kickstart.html

There is a small error, DummyCDStrap is needed if your CPU has a MMU, not just if you have BlizzardPPC. MMU blocks memory area used By extended part of rom, it will work but it is bog slow.

Blizkick guide tells very well what those romfixes does?

cant find a guide that explains what "romfixes" does

with dummycdstrap is this also needed with a 030 with mmu?

[maxx11111]

I don't use any of the Blizkick patches for an AmigaOS 3.9 kickstart which includes many fixes already. I do use the Remus patches called Patchmath020_All and NoClick in the BK_Mods directory of Remus but they are not necessary. These modules can be added at the bottom of the ROM contents in Remus.

For a 512kB kickstart, split the AmigaOS 3.9 BB2 update (no more double reboot is necessary with these) which will give:

bootmenu 44.7
console.device 44.8
exec 45.20
FileSystem.resource 45.10
(Fast)FileSystem 45.13
scsi.device 43.43
ram-handler 44.23
shell 45.7

Then replace with newer versions from the unofficial AmigaOS 3.9 Boing Bag updates:

console.device 44.10
FastFileSystem 45.16
layers.library 45.24
mathieeesingbas.library 40.4 (or hsmathlibs)
ram-handler 44.24
scsi.device 43.45 (or higher as there are several patched versions)
shell 45.27
icon.library 46.4.411 (Peter K)

thanks i will have a look at these

[utri007]

There is no better scsi.device than 43.45 By Hodges, Wilen and Sauer. I tried 43.46 but soon found that version number of it, is just a number.

Info picture taken from EAB

There is a blizkick.guide inside of archive, all modules are descripted there.

[matthey]

There is no better scsi.device than 43.45 By Hodges, Wilen and Sauer. I tried 43.46 but soon found that version number of it, is just a number.

Info picture taken from EAB

Do you have a link to where the pic on EAB came from?