Speeding up the reset

@All
i was getting 20+second resets and remembered the old hack
Run >NIL: C:AddNetInterface >NIL: DEVS:NetInterfaces/~(#?.(info|off))

to speed up the reboot i noticed in new SS on OS4final had this C:AddNetInterface QUIET DEVS:NetInterfaces/~(#?.info)

so i added Run >NIL: to the start of it making this
Run >NIL: C:AddNetInterface QUIET DEVS:NetInterfaces/~(#?.info)

and shed 10 seconds of the reset time

So, in this day of 5 minute reboots 20 seconds wasn't fast enough?!?!?!

Trouble is, the time you save booting up, you lose waiting for the internet to connect after WB shows. Some net apps will crash if you try to start them before you connect.

@ sundown:

IMHO you aren't going to lose that time, because you can start your applications during the addnetinterface waiting for the dynamic IP address. If an application crashes, it's a bug in the application which must be fixed.

Same here and worked a treat. Back fast and stable as ever!

ace

Works here too.

Thanks Rich

@poweramiga
I have a DHCP server that needs more than the default 60 second delay to work properly so I use Run all the time. My Mac also takes a long time to DHCP and it also uses "Run" of course.

Sometimes I even use the C:ConfigureNetInterface command to configure the IP address after the AddNetInterface fails with DHCP. I'm not sure how many people even know the two commands are there and what they do.

@sundown
If some application crashes because the TCP/IP stack isn't up and running it is seriously flawed. With OS4 it is a simple matter of one function call to determine if there is a valid interface available or not so there is no excuse for native OS4 software.

sundown wrote:

Quote:
It?s not that bad, and I don?t like waiting around.

Quote:
What if you have no internet at home, if there are bugs then developer making the programs most fix the bugs, there are no excuses!