17 March 2015, 00:46 | #1 |
Registered User
Join Date: Oct 2014
Location: Constanta / Romania
Posts: 202
|
BlizKick OS3.9 Custom ROM Troubles
Hi!
I have used the following guide: to cook a custom ROM at v44.57. When I try to kick it from BlizKick, I get a software failure with error number #80000008 followed by a guru error number 78132480. Compared to the tutorial, I have used:
I have tried both byte-swapped and not byte-swapped modes and I always get the some error. My test line that I used to kick the resulting rom is: Code:
BlizKick >NIL: KickFile DEVS:Kickstarts/kick3.9.A1200 Any clue as to what is going on? |
17 March 2015, 01:12 | #2 |
Registered User
Join Date: Oct 2014
Location: Constanta / Romania
Posts: 202
|
Further to this, I have also tried to create just a 512K ROM as per the A4000: I removed 1MB_ROM and added WBFind and copied workbench.library to SYS:Libs/
This time BlizKick does not throw error #80000008, it kicks fine but then I get a guru meditation 780095B0 after the reboot. I have even accessed the menu and selected "Boot without Startup-Sequence" and it still shows that guru and reboots. |
17 March 2015, 01:26 | #3 |
Registered User
Join Date: Oct 2014
Location: Constanta / Romania
Posts: 202
|
Ok, I figured that one out. The scsi.device from the v44.57 was the problem. I now rebaked and used the scsi.device from "that long thread on EAB suggesting a patched scsi.device could support large drives".
Now I get a ramlib error #8000000B. I am enjoying my monologue. I'll figure this out; you watch. |
17 March 2015, 01:47 | #4 |
Registered User
Join Date: Oct 2014
Location: Constanta / Romania
Posts: 202
|
Ok, going further, I copied the SetPatch from AmigaOS 3.9 to C:SetPatch and then modified the line in S:Startup-Sequence to read:
Code:
C:SetPatch NOCACHE QUIET |
17 March 2015, 03:36 | #5 |
Registered User
Join Date: Sep 2007
Location: Melbourne/Australia
Posts: 4,400
|
Hiya,
You don't actually need to create a ROM. BlizKick is clever and can create a custom ROM on the fly for you. Basically you rip your 3.9 updates from your SETPATCH ROM, then mix and match your own updates from the boing bags and load them all up at start-up without needing a reset. It's all in the BlizKick readme BTW This will give you some ideas -> Blizzy Startup Last edited by NovaCoder; 17 March 2015 at 03:45. |
17 March 2015, 04:55 | #6 | |
Registered User
Join Date: Oct 2014
Location: Constanta / Romania
Posts: 202
|
Hi Nova! Thanks for the response. I've been on and off playing with creating ROMs. I'm now more of an expert than I intended to be...
May I ask, in your startup-sequence, what exactly does BlizKick refer to when it says: Quote:
Also, I've been having mixed experiences by using the WB3.1 SetPatch vs the OS3.9 SetPatch (found in BB2). May I ask which SetPatch you are using? I'll just use the BB2 one for now. With the SetPatch found on the OS3.9 CD, my icon borders disappear. Not sure if that's how it's supposed to be... or? Great. Time to dump the ROMs again... I'll check back in a few! Thank you! P.S. Why did you leave out the new workbench.library? Last edited by eva; 17 March 2015 at 05:03. |
|
17 March 2015, 06:15 | #7 |
Registered User
Join Date: Oct 2014
Location: Constanta / Romania
Posts: 202
|
Yeah, still no dice:
I have copied all the files from NovaCoder's startup-sequence to a directory, then changed the BlizKick line like so: Code:
BlizKick >NIL: KickFile DEVS:Kickstarts/kick40068.A1200 EXTRESBUF=150000 MODULE DEVS:kick3.9/exec.library DEVS:kick3.9/bootmenu DEVS:kick3.9/FileSystem.resource DEVS:kick3.9/ram-handler DEVS:kick3.9/scsi.device DEVS:kick3.9/console.device DEVS:kick3.9/shell BBlank NoClick LocalFast MoveVBR SpeedyIDE QUIET EDIT: Ok, I managed to kick it now. :-) Thanks! Last edited by eva; 17 March 2015 at 06:28. |
17 March 2015, 06:41 | #8 | |
Registered User
Join Date: Sep 2007
Location: Melbourne/Australia
Posts: 4,400
|
Quote:
Because I don't need it. The only significant change is that is supports 3.0 (AFAIK). |
|
17 March 2015, 06:53 | #9 | |
Registered User
Join Date: Oct 2014
Location: Constanta / Romania
Posts: 202
|
Quote:
Now I see that DefIcons for OS3.9 does not want to start when I double-click it. Ugh... I also notice that ToolsDaemon has stopped working. Nice. Business as usual... Icons have their borders removed. Great - now I'll have to figure out a way to get them back. |
|
17 March 2015, 08:00 | #11 | |
Registered User
Join Date: Oct 2014
Location: Constanta / Romania
Posts: 202
|
Quote:
I was trying to get SYS:Prefs/Workbench to work from BB. For reference, if anybody stumbles on this thread: do not use KickControl / KickPrefs - it apparently is not able to handle long lines such as the ones needed by BlizKick. It will end-up truncating the line to a "manageable size" which confuses BlizKick and leads to #80000008 software failure again. |
|
17 March 2015, 08:56 | #12 |
Registered User
Join Date: Oct 2014
Location: Constanta / Romania
Posts: 202
|
I wish I could do something like:
Code:
BlizKick MODULE Devs:kick3.9/#? |
17 March 2015, 13:30 | #13 |
Registered User
Join Date: Oct 2009
Location: Germany
Posts: 3,304
|
Have a look into BlizKick.guide (click "Usage" buttion). There you can read how to use MODULES. There exists a default module path ("DEVS:Modules") which can be changed be set a environment variable called BKMODPATH. With this you can shrink you Blizkick command line a lot.
|
17 March 2015, 17:02 | #14 | |
Registered User
Join Date: Oct 2014
Location: Constanta / Romania
Posts: 202
|
Quote:
It still scratches my brain since I am now mixing BlizKick modules with OS stuff like .library and .device. I'm a tidiness freak. Would have loved to have them separated, perhaps something like: Code:
BlizKick * MODULES Devs:kick3.9/#? LIBS:kick3.9/#? NoClick BBlank etc... |
|
17 March 2015, 18:12 | #15 |
Registered User
Join Date: Oct 2009
Location: Germany
Posts: 3,304
|
I guess loading Modules from two or more different places without using full path isn`t supported. There is an option called IGNPATH which load the modules relative to current directory but this may not help.
|
17 March 2015, 18:23 | #16 | |
Banned
Join Date: Jan 2010
Location: Kansas
Posts: 1,284
|
Quote:
My BlizKick line in my S:Startup-Sequence is: Code:
BlizKick Devs:My3000.ROM QUIET Last edited by matthey; 17 March 2015 at 18:42. |
|
17 March 2015, 19:26 | #17 | |
Registered User
Join Date: Oct 2014
Location: Constanta / Romania
Posts: 202
|
Quote:
I have toyed with Remus around but given the 512k constraint, there are a lot of libraries that cannot be replaced (ie: the updated graphics.library, intuition.library, icon.library and scsi.device) since they would go over the 512k. For a soft-kick, it's rather strange that BlizKick does not support 1MB ROMs... It's just a file anyway and does not need to fit on a chip... There are several BlizKick modules that I find necessary: BBlank (to make the margin black), NoClick (to remove the click), ColdResetCard (for the PCMCIA fix), etc... They could be replaced by other tools from the Startup-Sequence but there are some like NoClick that I would like to have regardless whether I am booting from the HDD or from floppies. Last edited by eva; 17 March 2015 at 19:33. |
|
17 March 2015, 22:04 | #18 | ||
Banned
Join Date: Jan 2010
Location: Kansas
Posts: 1,284
|
Quote:
I have enough room in a 512kB Kickstart after leaving out workbench.library. There isn't any easy way to squeeze the new workbench.library in and it's not really a problem leaving it out. Quote:
|
||
01 June 2015, 18:22 | #19 |
Zone Friend
Join Date: Nov 2004
Location: Polsbroek NL
Age: 48
Posts: 74
|
I've been trying to make my own ROM for Blizkick using Remus aswell. So far I haven't been successful getting WinUAE to boot using a custom ROM. I've tried about everything. Put in the exec first, then other modules, and wbfind to point at SYS:workbench.library. I guess I've tried 15 or 20 different combo's in all by now. Not a single go. Then I read something about the order of modules after exec.library also being important. Is that the case? If so, what would be the correct build order? The Mfilos guide only give alphabetical lists, as does ROMSplit. I've even tried creating a custom ROM using a sort command on the datestamps of the ROMSplit directory which did indeed put exec.library on top. But no go again. Even tried the byte-swap for...well dunno actually. Even when trying to rebuild the same ROM, with exactly the same modules using alpha or datestamp order produces a HALT3 in WinUAE.
What the heck am I missing mates, that's so obvious to about everyone else on here? And BTW: what's with this site and Chrome? |
02 June 2015, 00:35 | #20 |
Registered User
Join Date: Oct 2009
Location: Germany
Posts: 3,304
|
Did you test with an unchanged ROM file? If that works just make one change and try again.
|
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
29f800/160 custom ROM | kipper2k | Hardware mods | 90 | 08 April 2017 09:31 |
Chip ram not found with custom kickstart rom [Solved] | Rien | support.FS-UAE | 1 | 01 March 2015 15:23 |
Help making Custom Kickstart rom | Viserion | Hardware mods | 28 | 13 December 2014 05:43 |
Crash with custom ROM on 68000 | UAE | support.WinUAE | 5 | 10 July 2012 09:04 |
ROM troubles + stuck on bootscreen | DashProject | support.WinUAE | 16 | 11 March 2011 18:10 |
|
|