Amiga.org

Amiga computer related discussion => Amiga Hardware Issues and discussion => Topic started by: Jose on December 03, 2004, 01:31:40 PM

Title: 3.1 Roms, Blizkick and boot time (for A4000)
Post by: Jose on December 03, 2004, 01:31:40 PM
Anyone has some for sale? :-)
Title: Re: Need 3.1 Roms for A4000
Post by: pjhutch on December 03, 2004, 01:44:28 PM
Check out:
http://www.amigadeals.fsnet.co.uk/adaddon.htm
Title: Re: Need 3.1 Roms for A4000
Post by: Jose on December 03, 2004, 02:08:15 PM
Hi. Thanks, but PowerComputing (http://www.powerc.com/cgi-bin/psearch.cgi?code=623-0002&rn=360&aid=&uid=sscrmfibcXkankE&sid=&cid=4&act=gpage)has them cheaper but still I think it's a bit expensive...
I think I'm gonna wait for eBay or some slip system...
Title: Re: Need 3.1 Roms for A4000
Post by: Effy on December 03, 2004, 02:48:17 PM
What turboboard do you have ??? If you have an A3640 then you can use the maprom function to load a kickstart 3.1 file into the memory and even install OS3.1  :-o No need for an expensive kickstart 3.1  :-D
Title: Re: Need 3.1 Roms for A4000
Post by: Brian on December 03, 2004, 03:07:10 PM
Title: Re: Need 3.1 Roms for A4000
Post by: x56h34 on December 03, 2004, 03:11:05 PM
@Brian:

Does Kickflash let you use Blizkick modules? Does this mean that one doesn't need to own a Blizzard/Cyberstorm accelerator anymore, in order to use Blizkick?
Title: 3.1 Roms, Blizkick and boot time (for A4000)
Post by: Jose on December 03, 2004, 03:18:46 PM
@Effy

Silly me :-o I'm expecting a CyberstormPPC to arrive any day now, and that one's got that function too.
Does it slow boottime very much ?

EDIT: just updated the tile, was "Need 3.1 Roms for A4000"
Title: Re: Need 3.1 Roms for A4000
Post by: adolescent on December 03, 2004, 03:22:20 PM
Quote

x56h34 wrote:

Does Kickflash let you use Blizkick modules? Does this mean that one doesn't need to own a Blizzard/Cyberstorm accelerator anymore, in order to use Blizkick?


No, it doesn't directly use BlizKick modules.  
And you still need a BlizKick supported accellerator to use the Kickstart mapping function.


Title: Re: Need 3.1 Roms for A4000
Post by: x56h34 on December 03, 2004, 03:25:41 PM
That's a shame. :-(

One of the better reasons to own a Phase 5 card is the ability to run BlizKick...too bad Kickflash didn't 100% eliminate that.
Title: Re: Need 3.1 Roms for A4000
Post by: Jose on December 03, 2004, 03:27:27 PM
[EDIT] Fixed the tile correctly now... :oops:

Anyways, can anyone say how much it slows boot time?
Title: Re: Need 3.1 Roms for A4000
Post by: nex4060 on December 03, 2004, 04:47:38 PM
dosn't realy slow the boot time, but it will however reboot the amiga when the rom file has been loaded into ram, but that only happens once from a cold boot.
Title: Re: Need 3.1 Roms for A4000
Post by: Brian on December 03, 2004, 04:51:25 PM
Using BlizKick alone will slot it down by some 5-10sec from a coldboot as it will do a reset partually through the startup sequence so the 3.1ROM is put to use. Using KickFlash this reset will come right after poweron (as it'll too have to put the 3.1ROM into use) BUT if you use OS3.9 you can ad it's ROMUpdates to the flashcard and as a result save yourself a reset later in the boot and thus save some time on the boot. :)
Title: Re: Need 3.1 Roms for A4000
Post by: Jose on December 04, 2004, 11:42:04 AM
10 seconds is a lot to me... Hmmm couldn't Blizkick also put the ROMUpdates on ram with a patch if I remember ? This wouldn't take off the cold boot's 5-10 seconds slowdow but it would still speed the bootup from AOS3.9(5).

By the way, isn't the 5-10 second Brian refers to caused by waiting for the IDE port? If so wasn't there a patch to kill it? This would take it off. Not sure if it worked with a cold boot though...
Title: Re: Need 3.1 Roms for A4000
Post by: Brian on December 04, 2004, 11:53:27 AM
No... that's the 30sec IDE wait you're thinking of... I'm saying it takes a 3-4 sec for the machine after I power it on before each reset before the HD kicks in (at least on my maxed out system). Then it takes a few secounds 'till it gets to the part in the startupseq where the ROM part is and it resets. Then it takes another sec or two before the HD kick in again. Adding up I get a reset wait of 1-2sec and a few sec of startupseq reading extra resulting in a 5-10 sec slower start of the machine... from a cold boot that is.

Dunno if BlizKick and ROMUpdate can work together to save yourself a from an extra reset.