Very weird Problem

[cheyenne1212]

Listen to this weird little probelm that just happned to me

I have a computer 2.8ghz P4 XP pro and 1.5gb of ram. I turned on the PC and it startes up Windows XP and once it got ot the welcome screen it wouldn't go any farther. I could hear the computer still loading up but my screen just stayed at the Welcom screen. So after a couple restarts and going into safe mode once, I fired up another PC on my network to post the problem here. So while I turned that one on, I turned the PC that had been causing problems on, and sure enough it went all the way to the desktop.

A person that uses this computer of mine told me that he had the same problem last week. The computer wouldn't go past the welcome screen untill the other computer on the network was turned on.

Also when I booted into safe mode I couldn't get the internet connection to work. I couldn't even connect to my router through my browser.

This is a very strange problem to mel. Maybe somebody here has had a similiar problem.

btw: I'm using a Nvidia Gforce 4 TI420 8x graphics card.

[sumdumguy]

well.. in safe mode.. you won't have access to a lot of things so forget that as being a problem.

why don't you boot up creating a bootlog.txt file and look at the file to see what errors you get.

or in safe mode.. disable most of your startup items.. I don't use xp but doesn't xp have an msconfig utility ?

edit: here..
http://pages.zdnet.com/hampsi/Articles/startup.htm

edit #2 : being as it seems to be dependant on the other pc booting up.. it could be that if you're running NAT and the other pc is the primary one.. then your first one is simply "looking for" that pc.. hmmm.. i didn't word that too well.. maybe someone can rescue me and state it a little clearer

[cheyenne1212]

yeah going to start then run and typing in msconfig will brink you a utlility to edit what starts up.

To create a bootlog.txt file do I just press f8 at startup and choose something there that will log the boot process?

[sumdumguy]

To create a bootlog.txt file do I just press f8 at startup and choose something there that will log the boot process?

Yes.. there is such a selection

[cheyenne1212]

Thanks for the help.

I do have a router that uses NAT so maybe thats part of the problem. I'll check that out and that link. Thanks for the help

[Showtime8000]

http://support.microsoft.com/default...NoWebContent=1
Windows XP Stops Responding at the Welcome Screen

It might apply to you; the microsoft article tends to blame a corrupted "memory snapshot." However, the problem did involve the use of the hibernating feature, which may or may not be relevant to your case.

Good luck

[Zonewalker]

cheyenne .... can I point out that by default XP starts up in safe mode without network support... but if you press F8 at boot up there should be an option to start with network support. Has nothing to do with NAT or the router...

Z

[edit] as for the remainder of the problem... i think sumdumguy is on the right track but if you got a router already on this shouldn't really be a problem since the router will be the primary gateway - by the way is the router a linux box or something like a linksys??

[cheyenne1212]

The routers a linksys befsx41 firwall router.


I should of known to boot in safe mode with networking support, but didn't do it.
I think sumdumguy might be right about the one computer being the primary computer. Before all this I had a linksys BEFSR41 and the computer that I used was the always the primary computer, but I never had that problem.

Thanks for the help though.

[phishphreek]

Are you by any chance sharing any resources from the second computer?

I've had this problem before when windows (XP Pro) was trying to reconnect network drives and network printers when they wern't turned on.

It took a really really long time to find out that the second computer and the printer wern't turned on. I guess this was because I had about 8 mapped drives to my server.... and the 2 network printers.

As soon as I turned on the server, it came up right away. Or, I can unmap the drives and that also works fine. I created a logon script to connect/disconnect me from mapped drives to resolve the problem. I didn't really look into it much more than the workaround...

[cheyenne1212]

I do have some mapped drives to that computer. They're not working properly though as I am having some trouble where computer 1 can ping computer 2, but computer 2 can't ping computer 1.

Maybe the problem is in that area somewhere. I'll delet those mapped drives though and see if that solves it.