In Grey Nomad had this to say:
My reply is at the bottom of your sent message:
Galen said:
In Grey Nomad had this to say:
My reply is at the bottom of your sent message:
After hours of "the process of elimination" it has turned out that I
can replicate the problem consistently by disabling my wireless
network (cable network has no effect and disabling any software has
no effect). Either switching off the router, or disabling wireless
networking in my machine will cause boot up to go from 60 seconds to
over two and a half minutes. Does this indicate something and where
do I go from here ? ([be nice!]
The old Grey Nomad
Sort of... If you haven't much to do you can do two things.
The first is, well, disable the wireless networking by default and
then - after booting - enable it if you need it.
The second is to check with any wireless devices - are you getting
signals from something else and then the network searching for the
default? Along with that you can check for (assuming you do use
wireless) device upgrades but I really suspect it is looking for a
second network during boot or you're grabbing another network during
boot and the compute cycles used to pick which is the default may
well have something to do with the login times. That is JUST a guess
(a stab in the dark if you will) but that's where I'd start... If
wireless isn't your primary then (honestly) turn it off and just use
it when you need it.
--
Galen - MS MVP - Windows (Shell/User & IE)
http://dts-l.org/
http://kgiii.info/
"At present I am, as you know, fairly busy, but I propose to devote
my declining years to the composition of a textbook which shall
focus the whole art of detection into one volume." - Sherlock Holmes
Er... the other way round. It boots ok if the wireless network is
available. But if I take my notebook away from the network - then the
boot up is dead slow. PS. I updated the D-Link wireless network
drivers but it changed nothing.
Do you have a networked drive that is mapped maybe? (Why is it that I seem
to find the unusual questions?) I'm stretching with this one though...
It doesn't seem likely that it is a hardware issue. *blindly stabbing in the
dark here*
Without getting too specific? It, the PC, is likely expecting, looking for
something, or loading something from the network and when the network's not
available it spends x-amount of time looking before giving up and completing
the login. It makes no difference what programs you have loading? And
example of where I've seen this happen is where someone has set an
application (such as the antivirus application) to update off a network
drive or to update prior to scanning so it will either look to update over
the internet on boot or it will try to update from a networked share.
So, well, I freely admit the above is the only LOGICAL reason I could think
of that happening - that doesn't mean that is the reason nor is it the only
logical reason - it's just that is the only one that I can think of. I
think, if I were you, and the above isn't the case or doesn't help you to
troubleshoot it then asking in the networking group might be your next step.
A networking MVP I am not.
news://msnews.microsoft.com/microsoft.public.windowsxp.network_web
(It might be easier to use a newsgroup client such as Outlook Express - the
above link should take you right there by default.)
More info:
Access MS Newsgroups:
http://kgiii.info/windows/all/general/msnewsgroups.html
Again, the above is a stab in the dark. I truly don't know and have
exhausted what I can think of or find though I think I'd check with the
networking gurus now that you've established that much.
--
Galen - MS MVP - Windows (Shell/User & IE)
http://dts-l.org/
http://kgiii.info/
"At present I am, as you know, fairly busy, but I propose to devote my
declining years to the composition of a textbook which shall focus the
whole art of detection into one volume." - Sherlock Holmes
