SLOW Boot-msconfig

D

dwayne001

Limp Gawd
Joined
Aug 9, 2003
Messages
468
OK, so about 3 days ago, I told msconfig to load up windows without using the win.ini (XP, SP2, All critical updates on a p4 2.6 HT w/ 1gb ram)

So i turned the machine off, turned it on, and it booted up, but SLOWLY. It was fine until it got to the "Windows XP" with the scrolling purple bar at the bottom. There it scrolled, on and on for about 5 minuteds before getting into windows.

So once i was in, the msconfig window popped up and i told it to re-instate win.ini during the boot-up sequence.

The slow boot up still occurrs though. I've set MSConfig to run seletive start-ups with minimal drivers, and still I get a slow boot-up. I've set it up for NORMAL/default start-up and still I get a slow bootup. I've tried system-restoring back to days before I made the changes, and still I get a slow boot-up. I've gone so far as to just having complete a full repair install, and still, the boot-up is slow, leading me to think that the repair changed none of the start-up configuration perameters in an effort to keep my settings in tact.

What can i do (besides re-formatting) to get a normal boot-up speed back?

Thanks
Dwayne001
 
Bootvis supoplied me with a 0kb file which the program, upon reboot, rejected. I've tried it a couple time, same result. Any reason why that could be?
 
Not sure what you mean by it "supplied you with a 0KB file" but here's how you use it.

Install Bootvis, then run it. Choose Trace - Optimize system. Click Reboot now and let it reboot.

Here's the overwhelmingly immensely galactically important step:

LEAVE THE PC ALONE UNTIL BOOTVIS IS DONE.

When the PC reboots, you may not notice anything different, and realistically you shouldn't. But, Bootvis is running in the background from the POST handoff. It's tracing and monitoring everything that's going on during the boot process:

- it measures how much time it takes to load specific files
- it measures how much time it takes to load specific drivers
- it measures how much time it takes to initialize the network
- it measures disk activity
- it measures CPU usage

and a whole slew of other details. The point being just because your computer rebooted doesn't mean you mess with it because Bootvis has to do all this and then it will pop up a box after you see the Desktop telling you not to touch the PC because it's still working.

It will continue to monitor the boot to the Desktop, watching all the apps that load in the background, any System Tray apps that load, etc. It continues monitoring everything until it's done - you'll know when it's done because another box will pop up onscreen showing you that Bootvis is now optimizing the files on the hard drive, which is a two stage procedure, so again, leave it alone and let it do it's thing.

Once Bootvis is absolutely and totally done with everything, that final dialogue box about optimizing the file layout will disappear and then Bootvis is done optimizing your PC for faster booting.

*phew*

The proper methodology for Bootvis usage is to first test/trace your current setup to see how fast it's booting; then run Bootvis to optimize the booting; then retest/retrace the setup to see the improvement:

Step 1) Run Bootvis - choose Trace - Next Boot + Driver Delays - Click OK then Reboot as required. Let Bootvis finish it's task, look at the graphs to locate how fast your PC boots (that'll be the tall vertical line topped with a white square box, put the cursor on the box for a second or two and a tiny popup will appear stating the boot to Desktop time), record that info.

Step 2) Do the Trace - Optimize system and let it do it's magic. When the optimization is done, redo Step 1 and compare the results.

Good luck,
bb
 
Appologies broadband, I should've taken the time broadband did to explain how to use the utility, but - I couldn't have said it any better, thanks a ton broadband :)
 
br0adband said:
Not sure what you mean by it "supplied you with a 0KB file" but here's how you use it.

Install Bootvis, then run it. Choose Trace - Optimize system. Click Reboot now and let it reboot.

Here's the overwhelmingly immensely galactically important step:

LEAVE THE PC ALONE UNTIL BOOTVIS IS DONE.

When the PC reboots, you may not notice anything different, and realistically you shouldn't. But, Bootvis is running in the background from the POST handoff. It's tracing and monitoring everything that's going on during the boot process:

- it measures how much time it takes to load specific files
- it measures how much time it takes to load specific drivers
- it measures how much time it takes to initialize the network
- it measures disk activity
- it measures CPU usage

and a whole slew of other details. The point being just because your computer rebooted doesn't mean you mess with it because Bootvis has to do all this and then it will pop up a box after you see the Desktop telling you not to touch the PC because it's still working.

It will continue to monitor the boot to the Desktop, watching all the apps that load in the background, any System Tray apps that load, etc. It continues monitoring everything until it's done - you'll know when it's done because another box will pop up onscreen showing you that Bootvis is now optimizing the files on the hard drive, which is a two stage procedure, so again, leave it alone and let it do it's thing.

Once Bootvis is absolutely and totally done with everything, that final dialogue box about optimizing the file layout will disappear and then Bootvis is done optimizing your PC for faster booting.

*phew*

The proper methodology for Bootvis usage is to first test/trace your current setup to see how fast it's booting; then run Bootvis to optimize the booting; then retest/retrace the setup to see the improvement:

Step 1) Run Bootvis - choose Trace - Next Boot + Driver Delays - Click OK then Reboot as required. Let Bootvis finish it's task, look at the graphs to locate how fast your PC boots (that'll be the tall vertical line topped with a white square box, put the cursor on the box for a second or two and a tiny popup will appear stating the boot to Desktop time), record that info.

Step 2) Do the Trace - Optimize system and let it do it's magic. When the optimization is done, redo Step 1 and compare the results.

Good luck,
bb
Click to expand...

Thanks for the lesson. Sincerely.
I'll let you know how it goes.
 
It didn't go so well. The first time I rean the trace "Next Boot + Driver Delays" I got a message that read "Number of Physical Drives in Trace File is 0. Trace File has invalid system configuration information."

I'm running the physical drive with the system and apps off of a raid 1 array which is part of the intel chipset ICHR yadda yadda that comes with this IC7-Max 3. Could that be why it's not detecting any drives? There are two opti drives on IDE 1 and 2 hard drives on IDE 0, so I don't get it.

I ran it again and got a message that read "File is not in a recognizeable format. Please Check the file again."

I ran it again and now I continually get a mandatory close (the kind that asks if you want to send it to MS or not) error that reads"PerfVis NT Performance Tool has encountered a problem and needs to close. We are sorry for the inconvenience."

I uninstalled it then reinstalled it. The last message kept on appearing. This is after it reboots after the trace.

Any suggestions?
 
I had a similar problem as recently as yesterday but with Win2k. I was fiddling around in msconfig because of a display driver issue. Turns out I accidently unchecked my plug and play in the start up tab. Try that.

Good luck
 
killdroidxx said:
I had a similar problem as recently as yesterday but with Win2k. I was fiddling around in msconfig because of a display driver issue. Turns out I accidently unchecked my plug and play in the start up tab. Try that.

Good luck
Click to expand...


Every single thing that can be checked in the start-up tab is checked. I'm at my wits end. The thing does very well once it's up and running-- it just takes forever to get there. I've fiddled around here and now with it since Bootvis failed me. I think I'm going to reformat tomorrow.....

I tried a repair install and it accomplished nothing.
 
dwayne001 said:
Every single thing that can be checked in the start-up tab is checked. I'm at my wits end. The thing does very well once it's up and running-- it just takes forever to get there. I've fiddled around here and now with it since Bootvis failed me. I think I'm going to reformat tomorrow.....

I tried a repair install and it accomplished nothing.
Click to expand...

I'm real sorry to hear bootvis didn't work out, I've never had a friend (or myself) have any of those (or any at all, really) errors from bootvis, I'm at a complete loss of what to suggest other than a reformat (but try bootvis out once you get a clean install!).i know the feeling about quirky shit. I used to retain an AOL account just for shits and giggles to mess with people when I got bored (like, searching for peopel who were harry potter fans to tell them snape killed dumbledore the night the book came out, before most of them had a chance to get it, much less read it), and AOL puts this god forsaken icon on your desktop that you cannot delete, I never found a way. Well, uninstall didn't remove it for some reason, and - with that icon on my desktop, you couldn't open images on the desktop, it would instantly kill windows picture/fax viewer the second it opened, it would just be a white flash on the screen, well - it took a reformat to fix it the first time (before I knew it was the AOL icon), i couldn't find anything about the problem online, well - almost a year later, on a completely different computer, the same thing happened, and i was determined not to reformat (I had loaned out one of my drives and had all 7,200 of my mp3s on my main drive, didn't want to fool with reinstalling without reformatting) and so i tried for days to figure it out, and it ended up being that damn icon (the best part is, to get rid of it, i had to fully install about 3 different versions of AOL, until i got lucky and one of the installs took the icon with it. I think I just felt like talking just now, sorry for a semi-hijack of your thread.
 
Bootvis didn't work? :confused:

Have you ran some spywares scan? Adwares albeit you did selective start up in msconfig?

I never had any problem with Bootvis as well. Sorry I can't provide any insight on yours :(
 
Thanks for that insight about the AOL icon :) Perhaps in a year or two i'll run into a simmilar prob on a different system and figure it all out.

As for spyware and malware, that's how I got into this whole mess to begin with. I was using Spybot search adn destroy and it kept on complaining about win.ini

I looked online and read that the win.ini settings file isn't really necessary under XP SP 2 so I disabled it.....
super slow boot-ups ensued. So I re-enabled it....yet super slow boot-ups still ensue. No amount of web searching has yielded a solution, so yuck on me. Now I'll never mess with another INI file so long as I use Windows.

When it comes to reformatting, I'll be fine. I keep the Windows file on a 10gb C:\ partition with all the heavy proggies and the games isolated on a D:\ partition. Sure I'll have to reinstall a whole bunch of proggies but installing them into their D:\ directories has proven to be effective in maintaining their individual settings. I should be up and running in the time it takes to reformat 10gb, and install win, so like 1.4 hours. It's just a pain is all-- especially when the installation is so smooht/stable once I get in.

Thanks again people.
 
Not sure how it happened but it seems the problem has corrected itself....it just boot up fine one morning when i was about to do some backing up in prep for a reformat of C. Thanks guys...silly computer!
 
You must log in or register to reply here.
Back
Top