WinUAE, Phase 5 Blizzard 1260, BlizKick, and ROM 3.1.4

tygre · 19 July 2019, 05:04

Hi all

I'm posted here although I'm not sure if my problem is related to WinUAE or something else: I created a straighforward WinUAE config. with ROM 3.1, a Blizzard 1260 in the Extensions and its MapROM feature enabled. I installed a fresh version of v3.1.4 in a disk. I added the 68060.library from Phase 5. It boots but, obviously, the ROM is v3.1.

Now, I wanted to use BlizKick to soft-kick the 3.1.4 ROM to mimic my actual Amiga. When I add:

Code:

BlizKick DEVS:Kickstart/Kick.A1200.46.143

and reboot, the Amiga reboots one more time (to install the ROM) and then boots but boots into the boot screen: it doesn't see the hard disk. If I reset again, it boots into the hard disk but the ROM is not kicked...

I must certainly be doing some wrong!!!

Any advice?

Cheers!

Thomas Richter · 20 July 2019, 00:21

Quote:

Originally Posted by tygre

I must certainly be doing some wrong!!!

The fairly obvious answer you probably don't want to hear is "you did not use LoadModule to load it".

The answer "why Blitzkick does this" I cannot give fully because I do not know how it operates. A fairly common problem with these kickstart replacers is that they run into the coldstart function of the Os. That, however, is not sufficient to restart the system properly. If you do just that, anything that sits on the autoconfig will be missed, for example the harddisk.

The reason is that the autoconfig chain requires a reset as otherwise all the devices on the chain consider themselves as "already configured", and thus does not react on expansion trying to configure the device.

Quote:

Originally Posted by tygre

Any advice?

Yup. Use Loadmodule.

tygre · 20 July 2019, 00:28

Hi Thomas and thank you!

So, I should remove the call to BlizKick and use LoadModule... but how should I use LoadModule exactly? I'm completely NOOB when it comes to it...

Cheers!

AMIGASYSTEM · 20 July 2019, 01:18

tygre if you have installed OS 3.1.4 + Modules (ModulesA1200_3.1.4) with KickStart 3.1, you do not need to use BlizKick

In practice, if you have installed "Modules", the new KickStart will be automatically loaded by the system.

If the installation is correct in the Startup-sequence you will need to have this string:

Code:

If Exists C:LoadModule
   C:Version exec.library version 46 >NIL:
   If Warn
      C:LoadModule ROMUPDATE
   EndIf
EndIf

tygre · 20 July 2019, 04:21

Hi AmigaSystem!

Thank you but I'm confused

Where should the KickStart file be copied? Right now, I do have the lines at the beginning of my Startup-Sequence but About... shows:

Code:

Kickstart version 46.65535
Workbench version 45.194

Best

Toni Wilen · 20 July 2019, 07:57

I think there is some confusion. BlizKick is map rom program, it loads the whole image to Blizzard accelerator's map rom and enables it. There is no reset tricks needed. (Blizkick can also load modules but it is not used in OPs command line)

Few possible reasons it isn't working:
- You have Z3 RAM. BlizKick does not handle it well. It expects all RAM to stay in address space during reset. (But usually this causes a crash)
- You don't have any configured accelerator board RAM: Last 512k is used for maprom.
- You don't have Blizzard 1260 ROM properly configured. (Do you see blue flashing lines at boot?)
- Map rom emulation is broken in some situations

AMIGASYSTEM · 20 July 2019, 09:23

Quote:

Originally Posted by tygre

Hi AmigaSystem!

Thank you but I'm confused

Where should the KickStart file be copied?

Is in a library (exec.library), look closely located in the floppy Modules

Thomas Richter · 20 July 2019, 11:40

Quote:

Originally Posted by tygre

Where should the KickStart file be copied?

Not at all. You install from the Install disk, and everything is been taken care of. Including the right startup sequence, and the call to loadmodule, and to place modules to the right places.

Yes, it is really that simple.

Shaytan · 20 July 2019, 12:57

Did a quick test using A1200 quickstart + Blizzard 1260 option.

Boosted accelerator board memory to 64mb under Expansions and ticked MapROM option.

Installed OS 3.1.4 + update, copied MMULib's 68060.library to LIBS and BlizKick to C (both from Aminet), edited startup-sequence, rebooted and everything is working and is recognized as expected.

Screenshot, startup-sequence and WinUAE config attached.

tygre · 21 July 2019, 03:58

Hi all and thank you for your advice!

Just to clarify my unclear post:

Quote:

Originally Posted by Toni Wilen

- You have Z3 RAM. BlizKick does not handle it well. It expects all RAM to stay in address space during reset. (But usually this causes a crash)

I checked, I have set 32 MB of memory in the Expansion part of the Settings. Also, I checked in Hardware info that I only have Z2 memory listed. I'm using "Blizzard 1240/1260 (32k)" as Accelerator board ROM file, is that correct?

Quote:

Originally Posted by Toni Wilen

- You don't have any configured accelerator board RAM: Last 512k is used for maprom.

I believe I do but not sure... see below...

Quote:

Originally Posted by Toni Wilen

- You don't have Blizzard 1260 ROM properly configured. (Do you see blue flashing lines at boot?)

Actually, I would like a 1240... However, I see some "copper rainbow" on boot.

Quote:

Originally Posted by Toni Wilen

- Map rom emulation is broken in some situations

I think that I'm doing something stupid, not WinUAE

I wanted to add that I realised that I was using a 68060 in the CPU and FPU settings. But, when I change to 68040, instead of booting, WinUAE reports a HALT3...

EDIT1: Ah, what a dummy! I had set the JIT option so there was no MMU, which explains the HALT3!

EDIT2: After reinstalling v3.1.4 from scratch and adding BlizKick, I now have the 46.143 ROM

Yeah! Thanks all!

Best,

AMIGASYSTEM · 21 July 2019, 09:59

Quote:

Originally Posted by tygre

EDIT2: After reinstalling v3.1.4 from scratch and adding BlizKick, I now have the 46.143 ROM

Yeah! Thanks all!

Strange, BlizKick is not necessary if you install the modules

tygre · 21 July 2019, 20:11

Hi AmigaSystem!

Quote:

Originally Posted by AMIGASYSTEM

Strange, BlizKick is not necessary if you install the modules

I don't know: how LoadModules works? Right now, without BlizKick, I don't have the 3.1.4 ROM

Best!

Toni Wilen · 21 July 2019, 20:19

There is still some confusion going on because with blizkick you don't need loadmodules to load updated modules.. It is same as physically replacing ROM chips.

Unless you load older version and then update it with loadmodules

tygre · 21 July 2019, 21:55

Hi Toni!

Quote:

Originally Posted by Toni Wilen

There is still some confusion going on because with blizkick you don't need loadmodules to load updated modules.. It is same as physically replacing ROM chips.

Unless you load older version and then update it with loadmodules

So, I could remove the LoadModules part of my Startup-Sequence?
Still I don't understand how LoadModules works?

Best!

AMIGASYSTEM · 21 July 2019, 22:23

Hello tygre, LoadModules is not necessary if you are using the native Kickstart 3.1.4, but if you need to start the Amiga with the KickStart 3.1 LoadModules is necessary because it is used to load Modules installed.

If you start the Amiga with the Kickstart 3.1.4 LoadModules will no longer serve that purpose, but in the future it may still serve to load other libraries such as the new intuition.library that will allow you to move windows off the screen.

I have a lot of LoadModules on my AfA-OS especially to instal the new icon.library Peter's.

I created a comprehensive video that shows the clean installation of OS 3.1.4 with the KickStart 3.1:

https://drive.google.com/open?id=1Da...-t0sbmDZ5PHPHr

Toni Wilen · 21 July 2019, 22:30

Boot without startup-sequence, use blizkick to load 3.1.4. It should reset and boot normally. If it does not, something is configured wrong.

EDIT: Attach config or winuaelog.txt.

Solution is not LoadModule.

Quote:

Originally Posted by AMIGASYSTEM

Hello tygre, LoadModules is not necessary if you are using the native Kickstart 3.1.4

Which he mentioned in first post. Using Blizkick to load 3.1.4 using Blizzard map rom hardware. Which is totally different than using 3.1 + LoadModules.

tygre · 22 July 2019, 18:31

Hi Toni and all!

Quote:

Originally Posted by Toni Wilen

Boot without startup-sequence, use blizkick to load 3.1.4. It should reset and boot normally. If it does not, something is configured wrong.

EDIT: Attach config or winuaelog.txt.

Solution is not LoadModule.

Thank you! This is exacty what I'm doing now (I mean, using my Startup-Sequence) and it works well: I have the 3.1.4 ROM and Workbench

Could you explain me LoadModules and point me to some explanations? What is it and how does it work?

Best!

Jope · 23 July 2019, 12:39

Quote:

Originally Posted by tygre

Could you explain me LoadModules and point me to some explanations? What is it and how does it work?

You can selectively upgrade parts of your Kickstart ROM with LoadModule. You must have the newer modules on your hard disk and then LoadModule will load them into RAM in a special way so that the Kickstart will find them and initialize them when the machine boots up.

If the RAM based module is a higher version than the one in ROM, it gets initialized instead of the ROM based module.

tygre · 14 December 2019, 21:17

@Jope

Thanks for your explanations! 8-)

MetalliC · 15 December 2019, 22:46

is it possible to run WB 3.1.4 in WinUAE with no new kickstart ?
Workbench install went fine, including A1200 modules disk, but at HDD boot I see just a black screen and then guru meditation.
is it same for everyone or just me ?
is it WB3.1.4 bug or WinUAE's ?

PS: it works fine with 3.1.4 kickstart.

19 July 2019, 05:04	#1
tygre Returning fan! Join Date: Jan 2011 Location: Montréal, QC, Canada Posts: 1,434	WinUAE, Phase 5 Blizzard 1260, BlizKick, and ROM 3.1.4 Hi all I'm posted here although I'm not sure if my problem is related to WinUAE or something else: I created a straighforward WinUAE config. with ROM 3.1, a Blizzard 1260 in the Extensions and its MapROM feature enabled. I installed a fresh version of v3.1.4 in a disk. I added the 68060.library from Phase 5. It boots but, obviously, the ROM is v3.1. Now, I wanted to use BlizKick to soft-kick the 3.1.4 ROM to mimic my actual Amiga. When I add: Code: BlizKick DEVS:Kickstart/Kick.A1200.46.143 and reboot, the Amiga reboots one more time (to install the ROM) and then boots but boots into the boot screen: it doesn't see the hard disk. If I reset again, it boots into the hard disk but the ROM is not kicked... I must certainly be doing some wrong!!! Any advice? Cheers!

20 July 2019, 01:18	#4
AMIGASYSTEM Registered User Join Date: Aug 2014 Location: Brindisi (Italy) Age: 70 Posts: 8,248	tygre if you have installed OS 3.1.4 + Modules (ModulesA1200_3.1.4) with KickStart 3.1, you do not need to use BlizKick In practice, if you have installed "Modules", the new KickStart will be automatically loaded by the system. If the installation is correct in the Startup-sequence you will need to have this string: Code: If Exists C:LoadModule C:Version exec.library version 46 >NIL: If Warn C:LoadModule ROMUPDATE EndIf EndIf

20 July 2019, 04:21	#5
tygre Returning fan! Join Date: Jan 2011 Location: Montréal, QC, Canada Posts: 1,434	Hi AmigaSystem! Thank you but I'm confused Where should the KickStart file be copied? Right now, I do have the lines at the beginning of my Startup-Sequence but About... shows: Code: Kickstart version 46.65535 Workbench version 45.194 Best

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
blizzard 1260 and winuae	loth77	New to Emulation or Amiga scene	4	03 May 2019 11:26
FS: Phase 5 Blizzard 1260	Dreamcatcher	MarketPlace	2	24 September 2010 09:07
Blizzard 060 - The SCSI KIT IV - Blizkick problem	ancalimon	support.Apps	3	16 December 2009 12:33
Troubleshoot my Blizzard 1260/50 (Phase 5)	StarEye	support.Hardware	3	31 March 2009 18:26
FS: Phase 5 Blizzard 1260	AMIGAZ	MarketPlace	14	06 April 2005 12:41

20 July 2019, 00:28	#3
tygre Returning fan! Join Date: Jan 2011 Location: Montréal, QC, Canada Posts: 1,434	Hi Thomas and thank you! So, I should remove the call to BlizKick and use LoadModule... but how should I use LoadModule exactly? I'm completely NOOB when it comes to it... Cheers!

20 July 2019, 07:57	#6
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 49 Posts: 26,502	I think there is some confusion. BlizKick is map rom program, it loads the whole image to Blizzard accelerator's map rom and enables it. There is no reset tricks needed. (Blizkick can also load modules but it is not used in OPs command line) Few possible reasons it isn't working: - You have Z3 RAM. BlizKick does not handle it well. It expects all RAM to stay in address space during reset. (But usually this causes a crash) - You don't have any configured accelerator board RAM: Last 512k is used for maprom. - You don't have Blizzard 1260 ROM properly configured. (Do you see blue flashing lines at boot?) - Map rom emulation is broken in some situations

21 July 2019, 20:19	#13
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 49 Posts: 26,502	There is still some confusion going on because with blizkick you don't need loadmodules to load updated modules.. It is same as physically replacing ROM chips. Unless you load older version and then update it with loadmodules

21 July 2019, 22:23	#15
AMIGASYSTEM Registered User Join Date: Aug 2014 Location: Brindisi (Italy) Age: 70 Posts: 8,248	Hello tygre, LoadModules is not necessary if you are using the native Kickstart 3.1.4, but if you need to start the Amiga with the KickStart 3.1 LoadModules is necessary because it is used to load Modules installed. If you start the Amiga with the Kickstart 3.1.4 LoadModules will no longer serve that purpose, but in the future it may still serve to load other libraries such as the new intuition.library that will allow you to move windows off the screen. I have a lot of LoadModules on my AfA-OS especially to instal the new icon.library Peter's. I created a comprehensive video that shows the clean installation of OS 3.1.4 with the KickStart 3.1: https://drive.google.com/open?id=1Da...-t0sbmDZ5PHPHr

14 December 2019, 21:17	#19
tygre Returning fan! Join Date: Jan 2011 Location: Montréal, QC, Canada Posts: 1,434	@Jope Thanks for your explanations! 8-)

15 December 2019, 22:46	#20
MetalliC Registered User Join Date: Aug 2014 Location: UA Posts: 12	is it possible to run WB 3.1.4 in WinUAE with no new kickstart ? Workbench install went fine, including A1200 modules disk, but at HDD boot I see just a black screen and then guru meditation. is it same for everyone or just me ? is it WB3.1.4 bug or WinUAE's ? PS: it works fine with 3.1.4 kickstart.

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