Boot Log Analyzer v. Slow Boot-up...

[caddmannq]

I have one Win98se machine that's booting almost twice as slow as other similar machines in the office.

I ran Boot Log Analyzer against the current boot log and found some interesting things.

1. Loadfailed=ndis2sup.vxd

2. Initcompletefailed =SDVXD

3. 4.944 sec. Enumerating tapedetection
(tapecontroller\tapedetection\0000)

4. 29.167 sec. initing ultra.mpd

5. init failure ppa3.mpd


#1 is, I assume, related to Novel Netware Directory Services, but this PC has never been on a Novel network, but has a Netgear NIC and on Win peer-to-peer.

#2 I don't have a clue about.

#3 is failing to detect a tape drive? This PC has never had a tape drive. Nothing on the network has one either. We back up to Zip drive & CD-R.

#4 This is an ASUS A7V machine w/ UDMA 100 HDD. This seems like an abnormal delay, and the cause (I suspect) of most of the slow boot-up.

#5 No clue.


Sooo....What's my next step?

we got the same kinda stuff going on - and I keep trolling ofr an idea - thanks- wiz

[BFlurie]

1. Normal
2. Normal
3. You want to stop this. I think the guilties are in C:\windows\system\iosubsys. Right click each file in there, look at properties & see if you can identify 'em, then move 'em out.
4. Your HD/CD mini-port driver. Usually windows' generic driver would load up much faster, IF you could use it. Sorry, can't offer any more than that. If you must use that driver, try completely removing it & all other HD controllers in Safe mode, reboot again into Safe mode, & reinstall 'em.
5. Sounds like related to 4? Can you look at the properties of the file ppa3.mpd?

[caddmannq]

Thanks Bflurie.

I haven't been able to pry the user off this machine to get back to it. But I did see that the ATA 100 is not detecting properly at bootup. Could be someone else "tweaked" with the BIOS.

More later,
Cadd.

[BFlurie]

That's the problem. Since the ATA100 isn't detected by the BIOS, Windows literally has to do an ad-hoc "Search for new hardware" on each bootup. Might try auto-detecting the drives in the BIOS.

would the same be true for a ata66 that is not picked up in the bios - therfore the drive gets loaded after windows tries to fix things up?

wiz

[BFlurie]

Yup. I noticed this yrs ago w/W95A when I tried the "latest, greatest" Intel IDE driver. Worked fine, but it strangely slowed up my bootup. Sounded like the "Detect new hardware" disk grinding. After looking at Bootlog.txt & later Boot-log analyzer, I decided it was doing just that.

thanks this is starting to make sense - boots have been in the 5 to t10 minute range - and really flaky - sometime I get a vide9o screen f up that you just have to pull the power on and start over -

best regards - wiz

[caddmannq]

OK, guys. I went in & tweaked the BIOS & cleaned out iosubsys (with some trial and error ) and I cut the boot up from 1 min 45 sec down to 45 sec. flat.

Woohoo!

It's nice to feel like you have some control over Windows once in a while.