The question is, do you actually use MSBackup? If not, uninstall it from Add\Remove
Programs Windows Setup tab, then rename the files mentioned. if you do use
MSBackup, you *may* get some sort of error message either upon boot or when starting
backup....I am not sure, as I do not ever use that applet. There are countless
better backup apps and backup strategies than MSBackup. Give the rename a try and
see if anything complains. If it does, you can simply rename the files back to
their original names.
By tape backup, I mean a tape drive.....if you don't know if you have one, you don't
have one. :-)
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm
"George" wrote in message
...
Hello Glen,
Thanks for your reply and help. I switched to the standard
MS mouse driver, and it cut the load time down to 17
secs. - better, but that still seems a long time.
I do have Msbackup (w/.exe, .chm, .ini, .hlp extensions)
installed. I don't really know what a tape drive backup
drive is - don't think I have one as I think of a tape
drive being a magnetic reel tape type for big business
machines. My system is pretty standard and simple - AMD K-
6 Chip, 96 RAM, 4GB HD, 3.5 Floppy and CD drives.
Assuming that I have Msbackup installed but don't have a
tape drive backup, can I disable tape detection per your
list below? All of the .inf and .vxd files are there.
George
-----Original Message-----
Tape Detection, and your Logitech mouse drivers, are
really taking a lot of boot
time.
I don't know if you can use that particular mouse without
those drivers....with many
such mice, the standard MS driver works fine.
Do you have MS Backup or another backup programs
installed? Do you have a tape
drive backup drive? If not, you can disable tape
detection, this way:
Look for any and all of the following files in these
locations:
[C:\windows\inf ]
pnpwfdc.inf
pnpwide.inf
pnpwtape.inf
pnpwppt.inf
[C:\windows\system\iosubsys ]
drvwq117.vxd
drvwppqt.vxd
drvwcdb.vxd
Rename all that you find....you can rename them by simply
changing the file
extension: change the inf to in_, and the vxd to vx_
You must set Folder OptionsView to 'Show all file types'
to find them, as they are
'hidden' files.
I will look at the rest of your list and see if I can add
another reply....hopefully
someone will drop in and add to this thread.
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm
"George" wrote in
message
...
Any help interpreting and correcting failures and delays
appreciated. Failures and delays log posted below:
7:59:03 0.28 Loading Device = C:\WINDOWS\HIMEM.SYS
7:59:04 7.89 LoadSuccess = C:\WINDOWS\IFSHLP.SYS
7:59:12 0.28 Loading Vxd = vnetsup.vxd
7:59:13 0.11 LoadFailed = ndis2sup.vxd
7:59:15 0.78 Loading Vxd = C:\WINDOWS\system\VMM32
\IFSMGR.VXD
7:59:16 0.28 Loading Vxd = C:\WINDOWS\system\VMM32
\IOS.VXD
7:59:21 2.89 LoadSuccess = vnetbios.vxd
7:59:24 4.61 Loading Vxd = C:\PROGRA~1
\SYMANTEC\SYMEVNT.386
7:59:29 29.72 Loading Vxd = LMOUSE.VXD
7:59:59 0.61 Loading Vxd = dfs.vxd
8:00:11 0.06 DEVICEINITFAILED = MTRR
8:00:13 0.50 DEVICEINITSUCCESS = VTD
8:00:13 0.28 DEVICEINIT = NTKERN
8:00:16 0.28 Dynamic load device bios.vxd
8:00:20 0.61 Dynamic load device pci.vxd
8:00:32 0.33 DEVICEINIT = IOS
8:00:34 0.33 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\diskvsd.vxd
8:00:36 4.39 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\acbhlpr.vxd
8:00:44 0.39 Dynamic load device lmul.vxd
8:00:45 31.56 Dynamic load device lmouse.vxd
8:01:17 1.61 Starting TrackMan7 (COM2)
(ROOT\*PNP0F0C\0000)
8:01:19 0.50 Dynamic load device
C:\WINDOWS\system\serial.vxd
8:01:20 2.06 Started TrackMan7 (COM2)
(ROOT\*PNP0F0C\0000)
8:01:23 0.44 DEVICEINIT = NDIS
8:01:28 4.17 Dynamic load device vdhcp.386
8:01:40 0.33 Initing hsflop.pdr
8:01:40 0.44 Initing esdi_506.pdr
8:01:41 0.67 Initing esdi_506.pdr
8:01:42 0.94 Initing drvwq117.vxd
8:01:43 0.78 Init Success drvwq117.vxd
8:01:50 0.11 INITCOMPLETEFAILED = SDVXD
8:01:54 0.39 Enumerating Communications Port (COM1)
(ROOT\*PNP0500\0000)
8:01:55 0.33 Enumerating Printer Port (LPT1)
(BIOS\*PNP0400\0C)
8:01:57 0.61 Initing drvwppqt.vxd
8:02:00 0.28 Dynamic load device dsound.vxd
8:02:00 1.33 Dynamic load success dsound.vxd
8:02:02 0.44 Dynamic load device vjoyd.vxd
8:02:03 7.72 INITCOMPLETE = NAVAP
8:02:11 4.17 Dynamic load device C:\PROGRA~1
\COMMON~1
\SYMANT~1\VIRUSD~1\20030430.004\NAVEX15.VXD
8:02:15 2.83 Dynamic load device C:\PROGRA~1
\COMMON~1
\SYMANT~1\VIRUSD~1\20030430.004\NAVENG.VXD
8:02:18 180.44 Dynamic load success C:\PROGRA~1
\COMMON~1
\SYMANT~1\VIRUSD~1\20030430.004\NAVENG.VXD
8:05:19 0.33 INITCOMPLETESUCCESS = NAVAP
8:05:27 168.44 InitDone = TSRQuery (time estimated)
8:08:15 0.78 Enumerating Standard Floppy Disk
Controller (BIOS\*PNP0700\0B)
8:08:16 4.06 Enumerating TapeDetection
(TAPECONTROLLER\TAPEDETECTION\0000)
8:08:20 260.56 Enumerated TapeDetection
(TAPECONTROLLER\TAPEDETECTION\0000)
8:12:41 0.33 Started Client for Microsoft Networks
(NETWORK\VREDIR\0001)
BOOT FAILURES AND DELAYS LOG ENDS HERE!
-----Original Message-----
Post the failures and delays here, and someone may be
able to help.
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm
"George" wrote in
message
...
I'm trying to determine why my start-up is taking so
long
to bring up the desktop. I've downloaded, installed
and
run Boot Log Analyzer bla.exe and have the list of
load
failures and delays it has produced from my last
boot.
How do I interpret and make corrections to items on
the
list? I see some failures explained in MKB Article
127970,
but it is not comprehensive in covering delays or
corrective action - is there an on-line source that
will
give more complete direction? Any help appreciated.
.
.