Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Pastimes : Computer Learning -- Ignore unavailable to you. Want to Upgrade?

To: Gottfried who wrote (9102)	4/8/2000 3:42:00 PM
From: mr.mark	Read Replies (1) \| Respond to of 110652

imo, the boot routine sequence on your pc is closer to the exception than it is to the rule.

To: Gottfried who wrote (9102)	4/19/2000 12:24:00 PM
From: mr.mark	Respond to of 110652

gottfried and all, since you and i recently exchanged posts on the subject of a:drive emergency boot disks and your subsequent use of windows bootlog, i thought it might be helpful to include this small piece on bootlogs... "Check the Boot Log Still suffering from slow boot times? It could be a problematic hardware or software driver. These can be a bit difficult to diagnose, but there are some tools that can help. The first thing to do is to generate a boot log and see if you can find the problem. You'll need to get to the Windows startup menu, which will give you an option to generate a boot log. Here's how: Windows 98: After the BIOS has completed its power-up testing, hold down the Ctrl key. The boot menu should appear. If the Windows logo appears instead, you probably didn't press the Ctrl key soon enough. Windows 95: After the BIOS has completed its power-up testing, press the F8 key. The boot menu should appear. If the Windows logo appears instead, you probably didn't press the F8 key soon enough. From the boot menu, select a logged startup. Once Windows has finished booting up, the file BOOTLOG.TXT will be in the root of your C drive. You can view this file with Notepad. To make sense of the information in the boot log file, you'll want to get a copy of a free program called Boot Log Analyzer. You can get it at vision4.dial.pipex.com. It's also available through download sites such as download.com . Just run the utility and it will analyze the boot log that you created with the procedure listed above. On a normal system, it's unusual to have any step in the boot process take more than a second or two. Large delays of ten or twenty seconds usually indicate some sort of problems with a driver or its associated hardware. However, note that it's normal to have some items that fail to load, even on a system in perfect shape. For example, most systems fail to load ndis2sup.vxd because that file detects it isn't needed and therefore doesn't need to load." :) mark