571
Hardware / Re: Slow boot process
« on: 2008.03.04, 15:03:28 »
Hi,
thanks! ...yeah, ok. The relevant part is
That again means that it (the DHCP client) continues to get an IP in the background and it should not cause any kind of wait/break during bootup.
But I wonder... isn't there any kind of "press Enter to continue"-message during the bootup?
Just for the fun of it... how about editing your setup.cmd and
- put a REM in front of the "dhcpstrt..."-line (meaning it should read "REM dhcpstrt..." afterwards)
- add a new line that reads "ifconfig lan0 169.254.0.1 netmask 255.255.255.0" (without quotes)
save the file and (re-)boot the machine?
This assigns a static IP to your lan0 interface and will tell us if there is any problem with DHCP (because now, DHCP wouldn't be used any more)... To revert, simply re-edit the setup.cmd, delete the added "ifconfig"-line and remove the "REM" in front of the dhcpstrt -line.
Alternatively, you could also change the "-d 0" part in the above line to "-d 10" for example.
This would enable 10 seconds of delay for the DHCP client to get an IP from the DHCP server (if there's any) and will show you a "countdown"-style message with a "press Enter to continue" afterwards if the client didn't get an IP assigned. If there's no "press enter..." message shown, it means that the DHCP request would have been successful and that DHCP is not an issue but the lockup happens later.
I am sorry if that is all in vain and EPW.EXE really turns out to be the culprit... but let's see. ;-)
One more question:
Is the genmac wrapper helper driver the first line in your config.sys?
(IIRC it's something with "helperw.sys" or similar, sorry, don't have eCS machine at hand...)
While we're at it - why not simply post your entire config.sys?
regards,
Thomas
I've attached the file \mptn\bin\setup.cmd
thanks! ...yeah, ok. The relevant part is
Code: [Select]
dhcpstrt -i lan0 -d 0which means interface lan0 is set up for DHCP and the DHCP client waits for 0 seconds to get an IP.That again means that it (the DHCP client) continues to get an IP in the background and it should not cause any kind of wait/break during bootup.
But I wonder... isn't there any kind of "press Enter to continue"-message during the bootup?
Just for the fun of it... how about editing your setup.cmd and
- put a REM in front of the "dhcpstrt..."-line (meaning it should read "REM dhcpstrt..." afterwards)
- add a new line that reads "ifconfig lan0 169.254.0.1 netmask 255.255.255.0" (without quotes)
save the file and (re-)boot the machine?
This assigns a static IP to your lan0 interface and will tell us if there is any problem with DHCP (because now, DHCP wouldn't be used any more)... To revert, simply re-edit the setup.cmd, delete the added "ifconfig"-line and remove the "REM" in front of the dhcpstrt -line.
Alternatively, you could also change the "-d 0" part in the above line to "-d 10" for example.
This would enable 10 seconds of delay for the DHCP client to get an IP from the DHCP server (if there's any) and will show you a "countdown"-style message with a "press Enter to continue" afterwards if the client didn't get an IP assigned. If there's no "press enter..." message shown, it means that the DHCP request would have been successful and that DHCP is not an issue but the lockup happens later.
I am sorry if that is all in vain and EPW.EXE really turns out to be the culprit... but let's see. ;-)
One more question:
Is the genmac wrapper helper driver the first line in your config.sys?
(IIRC it's something with "helperw.sys" or similar, sorry, don't have eCS machine at hand...)
While we're at it - why not simply post your entire config.sys?
regards,
Thomas
Are those better releases ? And where exactly am I supposed to have access ? 
of that virtualization software to be able to remove OS/2 guest support?... )
did the trick.