Printable View
Hi all,
as i own the original A4000 3.1 rom and an original os3.9 CD, i am after someone to make me a custom A4000 3.9 rom.
I understand if this a breaking rules on copyright and the thread sure be removed, but i don't think there is anything wrong with this request as i own the originals?
cheers, JuvUK
@Juv
There is no harm talking about it =)
so my friend you need help in building a custom Kickstart set for your A4000, well for one I know for fact that you have legitimate Kickstart 3.1 ROM's (since I put them there).
Now, the A4000, unlike the A1200 is limited to only 512KB of ROM space (more if you get an EFlash
http://amiga.resource.cx/photos/photos/eflash4000.jpg
or
DENEB USB
http://amiga.resource.cx/photos/photos/deneb.jpg
Both of these can give you up to 2MB of Kick ROM to be used on power-on.
Now, other than programming them, the big problem is the word "Custom"... as a the word suggests these 3.9 ROM's are made for a specific specification or build. While there are some obvious updates like FFS and SCSI.device in the ROM, there is a lot more that can be put-in and some crap taken out.
so, list your hardware here, and tell us your wants. I am sure we can help you figure out whats the optimum for your system build.
lol sweet:thumbsup:
all i want to achieve is a reduction in boot time, so the os3.9 rom update needs to be added, of course newer scsi.device etc would be nice as would the newest NSD but all that would just be gravy, it's the boot time that is most important:D
i'm also pretty sure you all know my specs!
A4000
buster 11
prometheus
voodoo3
network card
A4091
040@25mhz (for now)
okay my friend, I am just catching up with some threads I shall be back shortly to list what you need in the ROM =)
Fitzsteve takes a seat and watches the thread closely :)
/already has 3.9 ROM's so ner ner! lol
I could easily make a custom 3.9 eprom for A4000 but didn't knew about the 512kb ROM restriction the A4000 has! damn that sux :)
It's not that hard if we remove some unwanted modules, hmmm need to research a bit :)
You need to gief some info about the hardware and the BoingBags you use though. For example, do you use at all the internal IDE header (scsi.device) or not?
@mfilos
My friend, Juv uses an A4091, this is a scsi.device that setup under 2nd.scsi.device. it is NSD and RDB complaint, so as long as the scsi.device is updated it will work as it does with the reboots.
Aha I see.
If you include all the modules of original A4000's 3.1 Kickstart (40.68) plus the ones from BB2 ROM Update, you need about 27kb more in the Eprom space.
(And that is if you include the patched input.device, and don't include BB2's bootmenu that's 14kb more than the original 3.1).
IIRC, either Workbench.library or Intuition.library can be left out of the real kickstart since they can reside on the LIBS: directory when workbench boots so everything will be just fine (I'm not sure on that).
I made a custom kickstart that works just fine under WinUAE under A4000 emulation and it's 512kb but... it lacks intuition.library but has the Workbench.library inside (and 87kb free. Intuition.library is 114kb)
if it makes any difference i have BB1,2 and 3 installed, wow this does seem to be complicated.
i also have a blank CF card and DVD drive connected to the onboard IDE (again to speed up the boot time)
i do appreciate all your help guys:thumbsup:
I now have a 1260 on my 1200 which is working beautifully... And I still have KS3.0.
I'm thinking that I should really build my own extra special sekrit sauce receipe rom for it and use remapollo... But that only allows 512kb images.
I think I've got some reading up to do :D , but I'll be watching this with huge interest!
@mfilos
My friend, both workbench.library and intuition.library can be left out of the kickrom, as you have pointed out both of these are in libs: on the boot-drive or would be under any normal or classic-workbench installation.
hope that helps.
@Zetr0
That indeed helps and I'm glad I remembered seeing this over some thread @ some point.
The custom Kickstart ROM I made has 87kb space left for extra modules and that with the Workbench.library that is included.
Leaving out the Workbench.library, I can get inside stuff from BB3/BB4 like Cosmos's Graphics.library, icon.library, Cosmos new scsi.device plus any BlizKick modules that you'd feel comfortable with. (like BBlank,SpeedyIDE etc, but dunno which will be nice for his setup).
Feel free to suggest to make one for testing :)
@Zeets
Don't forget KickFlash :thumbsup:
My 4000D boots up within 15 seconds or less with OS3.9 + BB1 + BB2 and a few other updates.
Dave G :cool:
I shall indeed have a lookie my friend, I appreciate the help! (and I am sure Juvie does too)
BBlank / graphics.library wont be needed as its a RTG system, however scsi.device and speedyIDE sound like a plan - I shall delve a bit more in a bit, just cooking dinner for my girls =)
@Davideo
thats a good point I could of swore there was such a thing as KickFlash but couldn't find it on amiga.resource.cx
I got mine from here :thumbsup: One of the more useful things I've bought :)Quote:
Originally Posted by Zetr0
It certainly speeds up the boot process - removes the agonising double boot for a start.
Dave G :cool:
this thing?
http://amiga.resource.cx/exp/kickflash
That be it matey :thumbsup:Quote:
Originally Posted by JuvUK
Dave G :cool:
maybe you could tell us what's on your 3.9 rom instead of gloating? :pQuote:
Originally Posted by blankstare
Gloating is much more fun ... mine are for the A1200 lolQuote:
Originally Posted by JuvUKmaybe you could tell us what's on your 3.9 rom instead of gloating? :pQuote:
Originally Posted by blankstare
Making a custom 3.9 ROM is easy. Especially with Remus and Romsplit.
Now that I'm 100% that you can put Workbench.library plus Intuition.library off the ROM... You can put whatever u want :D
Sadly I'm not so familiar with all BlizKick modules to propose some, but Zetr0 and other peepz can contribute to that.
Btw... do you guys know what's the difference between Bootmenu of the 3.1 Kickstart and the Bootmenu of the 3.9 ROM Update?
The only visual thing I noticed is the lack of "Expansion Board Diagnostics" button.
For example my own Custom 3.9 Kickstart for my beloved A600 has the following:
- Exec 45.20 (instead of 40.10) --> OS3.9 BB2
- BootMenu 44.7 (instead of 40.5) --> OS3.9 BB2
- Console.device 44.10 (instead of 40.2) --> OS3.9 BB3
- Datatypes.library 44.48 (instead of 44.47) --> OS3.9 BB4
- Filesystem.resource 45.10 (instead of 40.1) --> OS3.9 BB2
- FastFilesystem 45.16 (instead of 40.1) --> OS3.9 BB4
- Graphics.library 42.8b11 (instead of 40.24) --> Cosmos
- Icon.library 46.4.181 (instead of 40.1) --> OS3.9 BB4
- RAM Handler 44.24 (instead of 39.4) --> OS3.9 BB3
- SCSI.device 43.46b3 (instead of 40.5) --> Cosmos
- Shell 45.27 (instead of 40.2) --> OS3.9 BB3
- Workbench.library 45.131 (instead of 40.5) --> OS3.9 BB3
- ROMUpdate 44.57 --> OS3.9 BB2
- BBlank --> BlizKick (For Blank Borders)
- SpeedyIDE --> BlizKick (For quicker IDE speed)
- HRTModule --> Action Replay clone using ACA's NMI header
Oh, hello. What's this? Please, tell me more!Quote:
Originally Posted by mfilos
Thanks for shareing mfilos :D, must try this stuff when I get Deneb working
This is the HRTMon application compiled from Toni's work and it's now a module :)Quote:
Originally Posted by AndyLandy
More info on this thread: http://eab.abime.net/showthread.php?t=57472
I just got the module, inserted in a Custom Kickstart and now... with a switch mounted into ACA630's NMI header, you can enter HRTMon's screen for Action Replay nukage :D
Since it's ROMable... It works even in Early Startup Menu :)
Really awesome stuff. I'm putting a switch to my A600 for that fella :)
@mfilos
- ROMUpdate 44.57 --> OS3.9 BB2
- Exec 45.20 (instead of 40.10) --> OS3.9 BB2
- BootMenu 44.7 (instead of 40.5) --> OS3.9 BB2
- Console.device 44.10 (instead of 40.2) --> OS3.9 BB3
- Datatypes.library 44.48 (instead of 44.47) --> OS3.9 BB4
- Filesystem.resource 45.10 (instead of 40.1) --> OS3.9 BB2
- FastFilesystem 45.16 (instead of 40.1) --> OS3.9 BB4
- RAM Handler 44.24 (instead of 39.4) --> OS3.9 BB3
and if there is room =)
- SCSI.device 43.46b3 (instead of 40.5) --> Cosmos
- SpeedyIDE --> BlizKick (For quicker IDE speed)
there that should do Juvie's Rig =)
ooo oooo oooo Mr Peevely, Mr Peevely!!
very exciting times ahead :)
@mfilos
The read/write function in the 43.46b1+ are completly rewritten : do not add SpeedIDE anymore !
Check EAB, the exec.library v45.24 will be released soon !
@Cosmos, where can we find your patches? :thumbsup:
I have a .net, but don't know how to create a site for some download files...
Archive the patches and then upload to http://www.filehosting.org/
Then just share the URL and everyone is a happy camper :)
or drop me a PM and I can set up an FTP account for you on binarydevotion...
Cosmos my friend thanks a lot for the advice!
New exec would definitely be an AWESOME update! Yey! No more 1MB_ROM module for our kickstarts :)
I can't wait!
Cosmos released his new Exec as he said yesterday. Check his thread over EAB: http://eab.abime.net/showthread.php?t=57950
With all his new awesome modules, the current custom kick I made has the following:
- Exec 45.24 (instead of 40.10) --> Cosmos
- BootMenu 44.7 68020 (instead of 40.5) --> OS3.9 BB2
- Card.resource 40.5 (instead of 40.4) --> Cosmos
- Console.device 44.10 (instead of 40.2) --> OS3.9 BB3
- Datatypes.library 44.48 (instead of 44.47) --> OS3.9 BB4
- Filesystem.resource 45.10 (instead of 40.1) --> OS3.9 BB2
- FastFilesystem 45.16 (instead of 40.1) --> OS3.9 BB4
- Graphics.library 42.8b11 (instead of 40.24) --> Cosmos
- Icon.library 46.4.181 (instead of 40.1) --> OS3.9 BB4
- Misc.resource 37.2 (instead of 37.1) --> Cosmos
- RAM Handler 44.24 (instead of 39.4) --> OS3.9 BB3
- Ramlib 40.3 (instead of 40.2) --> Cosmos
- Romheader 45.21 (instead of BlizKick module) --> Cosmos
- SCSI.device 43.46b3 (instead of 40.5) --> Cosmos
- Shell 45.27 (instead of 40.2) --> OS3.9 BB3
- Trackdisk.device 40.2 (instead of 40.1) --> Cosmos
- Workbench.library 45.131 (instead of 40.5) --> OS3.9 BB3
- ROMUpdate 44.57 --> OS3.9 BB2
- BBlank --> BlizKick (For Blank Borders)
- HRTModule --> Toni Willen, compile from 'Amigoun' (Action Replay clone using ACA's NMI header)
All the other (not yet upgraded) files not mentioned, are from the original Kick 3.1 ROM
Test proved that it works like a charm (at least in my test office WinUAE clone of A600 environment).
Cosmos my friend you are so full of WIN! Next time I'll donate more for your hard work :)
very cool stuff, is this A600 only?
Atm yes but I will stick almost all of these to your Kickstart as well...
(except some A600/A1200 specific modules and Intuition/Workbench libraries that will reside on Hard Disk)
sweeeeeet, thankyou!!
@mfilos,
since the target machine is an A4000, is there a need for card.device?
I am assuming that this is pcmcia-card related.
Ofc not Zetr0 my friend.Quote:
Originally Posted by Zetr0
For Juv's the following need to be changed:
Add:
- bonus (it exists in A4000 Kickstart)
Remove:
- card.resource (it doesn't exists in A4000 Kickstart)
- carddisk.resource (it doesn't exists in A4000 Kickstart)
Also Cosmos scsi.device 43.46b3 will be replaced by the internal scsi.device since it works for internal IDE of A600/A1200 (dunno if it works on A4000 but I doubt it).
Unless Juv has the scsi.device 44.2 patched already (in a file that can send me) since he installed BB3.
Somebody should do a complete step-by-step giude on creating custom ROM's for the various miggy's - I suspect lots of people might want to follow suit and make their own
it's been dropped;)
Already done some time ago...Quote:
Originally Posted by blankstare
http://www.amibay.com/showthread.php?t=11935
It's for A1200 but the same procedure (even easier) can be used for all other miggies.
What I propose, is for peepz that wanna start messing with custom kicks, to make a backup thofeir system under WinUAE and install Remus and the patches available and start tinkering their kickstart :)
When you make it, just try it over WinUAE and see if your system boots. Next step is to check version of the modules you installed and if everything done correctly and works... Burning is the easiest part and you don't even need to do it yourself :thumbsup:
@JuvUK
Got it and it's the correct :)
Will include it also.
Ahh :)Quote:
Originally Posted by mfilos
brilliant! let me know when it's done and i'll start testing:thumbsup:
Quote:
Originally Posted by mfilosAlready done some time ago...Quote:
Originally Posted by blankstare
http://www.amibay.com/showthread.php?t=11935
It's for A1200 but the same procedure (even easier) can be used for all other miggies.
What I propose, is for peepz that wanna start messing with custom kicks, to make a backup thofeir system under WinUAE and install Remus and the patches available and start tinkering their kickstart :)
When you make it, just try it over WinUAE and see if your system boots. Next step is to check version of the modules you installed and if everything done correctly and works... Burning is the easiest part and you don't even need to do it yourself :thumbsup:
@JuvUK
Got it and it's the correct :)
Will include it also.
Trying not to clutter the thread but which one of these is arguably better and why?Quote:
Originally Posted by Zetr0
Thanks!
>- Datatypes.library 44.48 (instead of 44.47) --> OS3.9 BB4
This one is really romable ???
You know, I would really like to try out a custom rom, and I looked at the directions, but my problem is finding all of the library files. I saw that Cosmos has updated many different library files, and I would love to try them in a custom rom, but I am having trouble finding them all. Is there a central repository for his updated files?
Cosmos my friend I wasn't sure about it but that's what I'm getting...Quote:
Originally Posted by Cosmos
Libs:datatypes.library (version 44.48 opening the file in hex) but version reports 44.47.
If I don't put in ROM
- 1>version datatypes.library = 44.47
- 1>version libs:datatypes.library = 44.47
If I put in ROM
- 1>version datatypes.library = 44.48
- 1>version libs:datatypes.library = 44.47
Dunno what's wrong with this, but as long as it's on the ROM... it reports the correct version :S
EDIT: I think I got it!!! If you remove datatypes.library from LIBS: (and you put it in ROM) system starts just fine and version responds the correct version (=it's romable).
Version libs:datatypes.library still responds 44.47 despite library NOT being there LOL. Why the assignment pseudo exists there dunno though :)
---------- Post added at 07:23 ---------- Previous post was at 06:59 ----------
One more thing I noticed...
Is that if you remove Intuition.library from the ROM (and put it in the Hard Disk) the Kickstart screen loads just fine, but booting the Hard Disk loops restarting in black screen.
Are people sure you can put off Intuition.library to save space?
(workbench.library and icon.library can be left out just fine if you leave them on Hard Disk)
@Slayer
I would say the DENEB is the better product - not only do you get 2MB of FlashROM capability, but you also get (in an A3000/A4000) DMA based USB2.0 support.
The DENEB can even have the USB stack up and operational on boot - so you can Boot from USB MEDIA such as attached harddisks. since its also USB it also supports USB Networking, Sound Cards as well as mass storage and HID compliant interfaces.
Arguably DMA based USB2.0 hooked up to a hard-disk should be considerably faster in operation and transfer than that of the Fast SCSI 2 10MB controllers found on a bounty of adapters (i.e. FastLane/CyberSCSI 1&2) when set to sync transfer.
Deneb is an wonderful product.
Theoretically you can include in a custom ROM the following Poseidon files:
- subwayusb.device
- hub.class
- massstorage.class
- poseidon.library
- psdstackloader
- fat95 (optional)
... and you can use subway to boot from USB sticks as well. OFC the speed will be really lower than Deneb's but it may be fun.
I haven't tried it yet, but I will in the future just for the test.
I only don't know if that can be disabled by the command "C:AddUSBHardware REMOVE ALL" (since it's on the ROM) cause if it can't WHDLoad will have issues.
yo all,
i am for some reason just getting a black screen with power cycling if a hd is connected, is it me or the rom?
cheers, JuvUK