Welcome, Guest. Please login or register.

Author Topic: 3.1 Roms, Blizkick and boot time (for A4000)  (Read 2624 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline Brian

  • Hero Member
  • *****
  • Join Date: Mar 2003
  • Posts: 1604
    • Show all replies
    • http://www.syntaxsociety.se
Re: Need 3.1 Roms for A4000
« on: December 03, 2004, 03:07:10 PM »

Offline Brian

  • Hero Member
  • *****
  • Join Date: Mar 2003
  • Posts: 1604
    • Show all replies
    • http://www.syntaxsociety.se
Re: Need 3.1 Roms for A4000
« Reply #1 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. :)

Offline Brian

  • Hero Member
  • *****
  • Join Date: Mar 2003
  • Posts: 1604
    • Show all replies
    • http://www.syntaxsociety.se
Re: Need 3.1 Roms for A4000
« Reply #2 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.