Its oficial I am a pillock!!

I need help sorting my sam440ep out again. I booted her up for the first in months and for some reason would not boot into os4.1
As being a typicall numpty PC USER (urgh I know) I shamely thought of reinstalling os4.1 it was not untill after reinstalling os4.1 I relised the horror.

I brought a new router recently and forgot to change the IP address which stoped os4 from booting ARRGGGH!!! So now i am starting from scracth. BOOO HOOO!!!

@magic

I've been in the same situation too... I think it is a serious bug in OS4.x...

@magic

AOS4 stop booting with no router powered ON during maybe 1-2 minuts and finally continue to boot fine.

AOS4 just check if the router is powered ON during the boot (not check if good IP or not). If the router is powered ON simply, AOS4 should boot fine with no delay.

If It's not like that, the first time AOS4 using, impossible to set the internet conenction on AOS4.1 the first time.

When first internet connection setting made, roadshow found itself the value on the router and use them.


Hum, maybe I'm not understand all well. Changing a router or modem router to another one and use the old internet conenction setting stop AOS4 to boot forever ???

@Alpyre
I think it's a serious "bug" too. And the sad thing is that the fix is soooo simple, yet due to an extreme minority of users it might concievably cause problems for (and even those are fixable IMHO), they don't fix it.

@Mrodfr

No eth0 waits for IP address before it continues.

if eth0 fails AmigaOS will boot too, but takes along time before eth0 gives up .

If you change

C:AddNetInterface QUIET DEVS:NetInterfaces/~(#?.info)

to

run >nil: C:AddNetInterface QUIET DEVS:NetInterfaces/~(#?.info)

then s:startup-sequence will not wait for C:addnetinterface, but network might not be up at time AmigaOS has booted.

the "run >nil:" part enable startup-sequence to continue, and not what for eth0 device to come alive

@LiveForIt
Yes, that's it...

@ChrisH
But they should... ;)

I had the same problem myself.

I wouldn't call it a bug but i agree that the timeout is too long.

@magic
Yeh..............................been there too.

ace