Blizkick trouble

steenl · 02 July 2024, 23:40

Hi,

I am trying to use Blizkick on my CyberstormPPC because I would like install the BootMonFix module from Aminet.

But I am having strange problems Blizkick. BootMonFix requires EXTRESBUF but when I specify this on the commandline blizkick says "object is not of the required type" no matter what module I try to install.

e.g this fails

Code:

Blizkick A4000.47.111.rom EXTRESBUF=100000 MODULE Colour

but this works

Code:

Blizkick A4000.47.111.rom MODULE Colour

works fine.

Anyone know what might be going on?

patrik · 03 July 2024, 16:10

BlizKick does unfortunately not support loading modules with kickstarts that are newer than BlizKick. It probably needs some specific information about the kickstart layout to do that.

Jope · 03 July 2024, 18:11

It patches exec.library when setting up the extresbuffer. There are no heuristics, it is hard coded based on detected exec version.

steenl · 03 July 2024, 20:42

So if I try to kick an older version like 3.1 I might have more success, but then my OS probably will not load

steenl · 03 July 2024, 23:11

ok, different approach. I was looking at the source code for BootMonFix and BlizKick and realized that BootMonFix set a flag that make it require EXTRESBUF.

With a little hex editing I removed the flag and now I can map my rom and install the BootMonFix module

patrik · Yesterday, 13:53

Good work!

Another more manual solution would be to press the 'c' key during boot, according to the .doc in:
https://aminet.net/package/driver/ot...dates-26042002

02 July 2024, 23:40	#1
steenl Registered User Join Date: Jan 2020 Location: Herlev/Denmark Posts: 24	Blizkick trouble Hi, I am trying to use Blizkick on my CyberstormPPC because I would like install the BootMonFix module from Aminet. But I am having strange problems Blizkick. BootMonFix requires EXTRESBUF but when I specify this on the commandline blizkick says "object is not of the required type" no matter what module I try to install. e.g this fails Code: Blizkick A4000.47.111.rom EXTRESBUF=100000 MODULE Colour but this works Code: Blizkick A4000.47.111.rom MODULE Colour works fine. Anyone know what might be going on?

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Blizkick Command	blade002	support.Apps	10	13 January 2024 02:46
blizkick	hexaae	support.WinUAE	4	21 March 2013 16:31
BlizKick problem	Diz_57	support.Apps	10	22 January 2011 01:34
BlizKick	NovaCoder	support.Apps	10	31 January 2009 21:48
Compiling BlizKick	Toni Wilen	Coders. General	2	26 December 2007 17:06

03 July 2024, 16:10	#2
patrik Registered User Join Date: Jan 2005 Location: Umeå Age: 44 Posts: 938	BlizKick does unfortunately not support loading modules with kickstarts that are newer than BlizKick. It probably needs some specific information about the kickstart layout to do that.

03 July 2024, 18:11	#3
Jope - Join Date: Jul 2003 Location: Helsinki / Finland Age: 43 Posts: 9,925	It patches exec.library when setting up the extresbuffer. There are no heuristics, it is hard coded based on detected exec version.

03 July 2024, 20:42	#4
steenl Registered User Join Date: Jan 2020 Location: Herlev/Denmark Posts: 24	So if I try to kick an older version like 3.1 I might have more success, but then my OS probably will not load

03 July 2024, 23:11	#5
steenl Registered User Join Date: Jan 2020 Location: Herlev/Denmark Posts: 24	ok, different approach. I was looking at the source code for BootMonFix and BlizKick and realized that BootMonFix set a flag that make it require EXTRESBUF. With a little hex editing I removed the flag and now I can map my rom and install the BootMonFix module

Yesterday, 13:53	#6
patrik Registered User Join Date: Jan 2005 Location: Umeå Age: 44 Posts: 938	Good work! Another more manual solution would be to press the 'c' key during boot, according to the .doc in: https://aminet.net/package/driver/ot...dates-26042002

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)