Interesting result with AKU3.2 and custom Ext ROM

[jorge_culv]

OK, so I finally got curious enough to cook my own ROM then added it to Ell82's AKU3.2 ROM and stumbled across something pretty cool...I followed Faria's instructions (turns out not very well...) and added a cab with spaces (I know, I know, freakin noob...). Anyway, it apparently just skipped over that cab and kept going. Now here's the cool part, the total cabs I added to my ROM was only 2.6 MB so I thought I was OK. Didn't pay close enough attention until later and realized the nk.nbf file was about 10.5 MB. When faria says the Ext Rom shoudl be less than 9.5 MB, is he talking the total of all the cabs, or the nk.nbf file???

Bottom line is even though the nk.nbf file was 10.5 MB it installed and ran fine on AKU3.2 (except for the cab with spaces). I then tried to load this into Molski's 2.26 ROM and the ExtROM wouldn't take. Went back and fixed the cabs with spaces and it still won't take.

This leads me to the initial conclusion that the AKU3.2 ROM allows you to exceed the 9.5MB limit. Can anyone else confirm this?

[shogunmark]

total n00b for sure... :D (not flaming)

when you make an extended rom it defaults to a size of around 10meg, no matter whats in there.. you could have 1 cab@ 10k or 500 cabs@ 10.5meg (just cant go over the 10 meg limit).. so if you have 1 cab then no matter what the size is automatically 10meg.. everything in the rom is addressed my memory locations, everything has a set start and end address

and you can prevent cabs from being installed by removing them from the config.txt

[jorge_culv]

OK, then help a ROM-cooking n00b out. Faria's tutorial mentions the instructions were tested up to the 2.24 ROMs--anything that would cause a problem with his ext-rom-base on a 2.26 ROM? I just can't get it to install. The ExtROM is not corrupt because I can manually install each cab in the ExtROM using total commander, but can't get them to install from hard-reset...

[shogunmark]

OK, then help a ROM-cooking n00b out. Faria's tutorial mentions the instructions were tested up to the 2.24 ROMs--anything that would cause a problem with his ext-rom-base on a 2.26 ROM? I just can't get it to install. The ExtROM is not corrupt because I can manually install each cab in the ExtROM using total commander, but can't get them to install from hard-reset...

well actually the ext rom could be corrupt.. i have had that problem before(actually with my latest UWC beta, which caused almost a week long delay).. all cabs would install manually but the ones listed in the config.txt wouldnt install at all... what cabs are you trying to install that arent? and what does the contents of your config.txt look like?

[jorge_culv]

Thanks for the help ShogunMark--is it possible for an ExtRom to install fine for AKU3.2, then same extact ExtROM (no rebuild, no changes, didn't even look at it funny!) not install on 2.26 (installed it twice on 2.26 in case it might have been corrupt the first time)? That's the situation I'm looking at. Originally the extROM (the one that worked for AKU3.2 but not on 2.26) had a few cabs with spaces in their names. When I started having problems on 2.26 I started looking closer and rebuilt the ExtROM with new file names, but it still wouldn't install on 2.26. Just to make sure I'm not crazy, I'm about to down-grade to AKU2.3 OS version 2.24 to fully comply with the ROM building tutorial that says its tested to at least OS version 2.25. I'll let you know how that goes in a few hours. In the meantime, here's the Config.txt I'm using now that won't go in auto, but allows me to install the cabs by hand in 2.26:

LOCK:Enabled
CAB: \Extended_ROM\cLaunch.arm.CAB
CAB: \Extended_ROM\Molski.Biz_VoiceDial_Button_Customiz er.cab
CAB: \Extended_ROM\Molski.Biz_Customizing_Tweaks.cab
CAB: \Extended_ROM\Molski.Biz_Performance_Registry_Twea ks.cab
CAB: \Extended_ROM\nullkb.ARM4.CAB
CAB: \Extended_ROM\rar360.ppc_arm.cab
CAB: \Extended_ROM\SmartDial+EtenSkinPortretD_v2.cab
CAB: \Extended_ROM\fileaslf.arm.cab
LOCK:Disabled
RST: Reset

[shogunmark]

Thanks for the help ShogunMark--is it possible for an ExtRom to install fine for AKU3.2, then same extact ExtROM (no rebuild, no changes, didn't even look at it funny!) not install on 2.26 (installed it twice on 2.26 in case it might have been corrupt the first time)? That's the situation I'm looking at. Originally the extROM (the one that worked for AKU3.2 but not on 2.26) had a few cabs with spaces in their names. When I started having problems on 2.26 I started looking closer and rebuilt the ExtROM with new file names, but it still wouldn't install on 2.26. Just to make sure I'm not crazy, I'm about to down-grade to AKU2.3 OS version 2.24 to fully comply with the ROM building tutorial that says its tested to at least OS version 2.25. I'll let you know how that goes in a few hours. In the meantime, here's the Config.txt I'm using now that won't go in auto, but allows me to install the cabs by hand in 2.26:

LOCK:Enabled
CAB: \Extended_ROM\cLaunch.arm.CAB
CAB: \Extended_ROM\Molski.Biz_VoiceDial_Button_Customiz er.cab
CAB: \Extended_ROM\Molski.Biz_Customizing_Tweaks.cab
CAB: \Extended_ROM\Molski.Biz_Performance_Registry_Twea ks.cab
CAB: \Extended_ROM\nullkb.ARM4.CAB
CAB: \Extended_ROM\rar360.ppc_arm.cab
CAB: \Extended_ROM\SmartDial+EtenSkinPortretD_v2.cab
CAB: \Extended_ROM\fileaslf.arm.cab
LOCK:Disabled
RST: Reset

the problem is that you are missing the disable security cab, i have attached in case you need it.. I would also bet those spaces arent suppose to be there... you should have this:
LOCK:Enabled
CAB: \Extended_ROM\Default_Signed_DisableSecurity.CAB
CAB: \Extended_ROM\cLaunch.arm.CAB
CAB: \Extended_ROM\Molski.Biz_VoiceDial_Button_Customiz er.cab
CAB: \Extended_ROM\Molski.Biz_Customizing_Tweaks.cab
CAB: \Extended_ROM\Molski.Biz_Performance_Registry_Twea ks.cab
CAB: \Extended_ROM\nullkb.ARM4.CAB
CAB: \Extended_ROM\rar360.ppc_arm.cab
CAB: \Extended_ROM\SmartDial+EtenSkinPortretD_v2.cab
CAB: \Extended_ROM\fileaslf.arm.cab
LOCK:Disabled
RST: Reset

[jorge_culv]

Ahh, so even though one of Molski's cabs does this, I need to disable security first to allow the other cabs to install? I think I get it! Thanks again,

Geo

[shogunmark]

Ahh, so even though one of Molski's cabs does this, I need to disable security first to allow the other cabs to install? I think I get it! Thanks again,

Geo

yes, you need that or the other cabs wont install, most importantly it needs to be first, or else anything else that isnt signed wont install