Ok, heres a windows 3.11 problem that I hope someone can fix...... I have TCP/IP installed incase in matters.. If I turn on my computer when it is plugged into a network, it will start up successfully.. But, if I am away (it's a laptop) and turn on the computer, I will see the windows logo, which is longer than usual (i'm asuming it's because it can't find dhcp) and i will see my desktop and here the chime sound, but thats all it gets, the hd turn off. it frezzes. Why do i need to turn on the computer connected to a network? Because once its started on a network, i can unplug it and walk away, but thats a pain...

couple things...i assume by network you mean high speed internet access- if its a local network my advice might not work... make sure youve turned off or disabled printer sharing if you dont use it (unlikely if your using it for the internet). this has caused my box to freeze too when the cable was out... also sometimes rem'ing out the 'net start ' command in the boot files (cant remember if it was autoexec.bat or config.sys anymore)might help- its not needed for internet access- As far as dhcp is concerned, if it doesn't see a connection , usually you'll get a blue screen telling you that it was unable to find a dhcp server ,or something to that effect, and if you would like to see more messages... However, this is with windows for workgroups' Tcp-Ip 32, which is nt -derived, and if your using tcp-ip 16 it may or may not give those messages. HTH

I'm using the 32bit version of TCP/IP and us the worgroup version. I actually just found a workaround, I start windows at dos with WIN/N. I ment the LAN and cable modem, because the internet on win 3.11 sitnks for me, i download all the big stuff and send it to win 3.11 on the lan..