Re: XP General question - wrong ng though?
From: Sharon F (sharonfDEL_at_ETEmvps.org)
Date: 03/13/04
- Next message: KiwiBrian: "Task Bar icon size"
- Previous message: High Sierra: "Re: regedit????"
- In reply to: Pop Rivet: "Re: XP General question - wrong ng though?"
- Next in thread: Sharon F: "Re: XP General question - wrong ng though?"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 13 Mar 2004 08:34:27 -0600
On Sat, 13 Mar 2004 07:39:09 -0500, Pop Rivet wrote:
> Sharon,
>
> Thank you much; never thought about "parallel" installs before, but after
> a little research, it sounds like a good idea to me. I DO want to learn,
> but need to get things running again soon, so I think I"ll try it.
> I also have a spare NIC card - so I can try that too. Makes sense.
>
> Thanks for sticking with me. That's just the kind of "general" advice I was
> looking for and describing things wasn't an easy task. It's hard when one
> can't even figure out which question/s to ask.
>
> One final question if I may:
> The boot delay is so long and pretty obviously waiting for "something" to
> time out, are there any machine logs I can look at to see if there are any
> error or warning messages that might point to what the delay is waiting for?
> I have all the logs except packet monitoring turned on & set to default
> sizes; 512k if I recall, but it's sort of an information overload since I'm
> new to them all except Event Viewer.
>
> By the time you read this I'll have already installed, parallel or not,
> something, but I have archived all the logs I can find for later study and
> analysis. I'd really like to figure out what's up and how to "see" the
> problem as though I knew what to look for!
Check Event Viewer. It logs the startup process and reports on problems.
Another tool, System Information, can give you a report on hardware
configuration and potential conflicts. MSCONFIG can be used to disable
startup programs. Troubleshooting startup problems is very similar to
troubleshooting shutdown problems. The issues are very much the same, just
the "when" is different. The following site is well known for its extensive
coverage of shutdown issues for all versions of Windows, including XP:
http://www.aumha.org/win5/a/shtdwnxp.htm
Packet logging can take time. If your security is in place - firewall,
current antivirus program and regular checks for spyware - it is an
additional load that's not really productive in a home setting.
There is a program called "boot-vis" that was around when XP was first
released. Microsoft has pulled it from their site but it can still be found
if you look around the internet. I think MVP Kelly Theriot has it at her
site still (or at least a link to it): www.kellys-korner-xp.com.
It basically does the same thing that the builtin XP housekeeping does but
it has a feature that *could* be helpful: It creates a tracelog of startup
and shows a graph of how long each component takes to load. By noting the
items that take up huge chunks of time, it can guide you to troublesome
drivers or problem areas in the configuration. There is an Optimize
function - this portion produces the same results as XP's builtin
mechanisms but it happens a little "faster."
IMPORTANT: If you try boot-vis: When analyzing, keep in mind that network
always takes a bit more to initialize at startup. Also, don't forget to
disable the tracelogging before uninstalling it! If you forget, the
tracelog keeps growing and growing and it's a nasty experience working
backwards to get the logging disabled (Yes, I forgot this the first time I
used the program. BTDT). Uninstall bootvis after getting one or two
readouts. Disable logging before uninstalling.
For consideration if you do a new install:
One of the things that I do on my systems, after a clean install and
everything is setup, I change the "started" services to the "Automatic"
startup type. They are only loaded if needed - many load, do their thing
and drop back taking no further system resources. The rest are just needed
so why not get them loaded and move on. I think this is an efficient
approach instead of the system waiting to start a service that is needed
and then proceeding further with the boot.
-- Sharon F MS MVP - Windows XP Shell/User
- Next message: KiwiBrian: "Task Bar icon size"
- Previous message: High Sierra: "Re: regedit????"
- In reply to: Pop Rivet: "Re: XP General question - wrong ng though?"
- Next in thread: Sharon F: "Re: XP General question - wrong ng though?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
