Long boot time OS4 Final

I know I'm a bit late, but I just install OS4 Final on a blank partition and found a long delay before Workbench actually appears.
I checked the battery recently and I have verified that the network is correctly set (I post with OS4 Final).

Any tips how to skrink boot time to something decent?

Bye,
TMTisFree

@TMTisFree

I hope You are really this good looking Ms. TitsFree

What about the July-update? Some details and sorry I'm caged...

Maybe the net hangs or something else. Mine just got a bit more faster.

Edit: Search loads of tips from Amigaworld.net too to get the boot time fast.

Edit2: UBoot settings has a "timeout" put one to zero if not needed to dualboot and the other to one second.

Really this is all discussed before so look the older AW discussions or here.

Hi @TMTisFree

Any tips how to skrink boot time to something decent?

Edit Kickstart modules? The new kernel contains extras that don't apply to you particular hardware...

@TMTisFree

Put a :
run >nil:
Right before c:addnetinterface in your Startup-Sequence.

Don't forget to format your boot partition for SFS.

Good luck!

@TMTisFree

Have you tried the standard trick of starting the TCP/IP stack synchronously with the rest of Startup-Sequence?

"Run >NIL: C:AddNetInterface >T:interface.log DEVS:NetInterfaces/~(#?.info)"

Leave out the ">T:Interface.log" if you wish (replace it with "Quiet"). I like a log of what happened.

@TMTisFree
there is an article on IntuitionBase.com giving several tips to reduce the booting time of OS4. This article was writen for the Pre-release version but I think most of the info still applies.

@TMTisFree

Maybe it's the network connection taking time? A run >NIIL: in the startup-sequence will do the trick then (as described in many forums).

@All

Of course, I already read what's on the subject before posting. I already have the Run <>NIL: in front of AddNetInterface and some others.

What I mean is that between the 'Loading done, now launching...' and the actual Workbench to appear, there is 50-55 seconds.

Edit: grammar

Bye,
TMTisFree

@TMTisFree

Strangely, the early startup menu takes also about 50 seconds to appear and when I click on Boot (so with S-s) it alos takes almost 50 sec. for the Workbench to appear.
Will fiddle with UBoot first.

Edit: forgot time

Bye,
TMTisFree

@TMTisFree

1. Go to UBoot Prefs and disable, IDE channels you don?t use
(If enabled or on auto it will take more time to detect devices)

2. Edit sys:kickstart/layout removed drivers you don?t need
(Simply put a ?;? symbol in front of the line)

3. Set all boot delays in UBOOT to 1

4. Edit S:Startup-sequence, add Run >nil: in front of addinterface line.

5. Remove DOS drivers you don?t need from Devs:dosdrivers

6. Check your user-startup

7. Check WBStartup

@LiveForIt

1. Done.

2. Will check.

3. Done

4. Done

5. Done

6. Empty

7. Empty

Thanks.
TMTisFree

@TMTisFree

Humm, still no joy.
Will try the july update then.

Bye,
TMTisFree

@TMTisFree

52 seconds with july update, I'm stuck.
What else?

Bye,
TMTisFree

Hi @TMTisFree

What else?

Why don't give us some data to work with? You're totally vague.

What's in WBstartup?

@TMTisFree

Quote:Unless you are using an USB keyboard or mouse try if disabling the USB kickstart modules in the kicklayout and "C:USBCtrl START" in the startup-sequence helps.

@joerg

Ok, USB disabled in both software and hardware, and still more than 50 sec. between 'Loading done...' and Workbench.
I tried to revert back memory to 512MB, still about 50 sec.
Will try with removing the sound card.

Bye,
TMTisFree

@Snuffy

What is vague?
It's a fresh OS4Final/JulyUpdate install.
S-s is standard with just some Run <>NIL: added.
Nothing in WBStartup, in User-Startup.
Kickstart reduced to the bare minimum.
Serial/parallel/IDE/USB deactivated.

Bye,
TMTisFree

@TMTisFree

Quote:Sound cards are only accessed when a driver is loaded, not before the boot menu.
Set the IDE driver config to the correct settings for each unit (HD, CD/DVD drive or nothing) instead of "auto". And remove all CDs/DVDs from the drives in case there is one in a drive, especially an unreadable CD/DVD (empty CD-R or DVD+-R for example) could cause a long delay.

@TMTisFree

Same without the sound card.
Hmm.
50 sec. before Early-Startup means that the pb is probably in UBoot config. Will double-check all entries in Prefs now.

Bye,
TMTisFree

@TMTisFree

Yessss, 12 sec.: all IDE timeouts was set at 10 sec. in UBoot Prefs without my consent and I don't know when. It's strange because all IDE settings are deactivated except the 3112 card 'for booting) and nevertheless timeouts are taking in account by UBoot. Bug?

Now all of them at 1 sec.

Thanks you all for your suggestions. Really appreciated.

Bye
TMTisFree