bootlog - how to fix problems

[enrico.caporossi@gmail.com]

Here <http://digilander.libero.it/katalog/bla.jpg> is my bootlog.

Someone can tell me how can i fix the delays?

Thanks.
qcnc

 

[98 Guy]

Re: bootlog - how to fix problems

enrico.caporossi@gmail.com wrote:

> Here <http://digilander.libero.it/katalog/bla.jpg> is my bootlog.
>
> Someone can tell me how can i fix the delays?

Do you have any SCSI drives? Is your hard drive being controlled by a
RAID controller?

If not, then disable the SCSI controller.

Do you connect to the internet via 56k modem? If not, then change
your TCP/IP from dynamic IP to static. You probably have it set for
DHCP. It will be faster if you assign a fixed IP to your computer
(assuming it's on a NAT'd network).

What's "FlyTV" ?

 

[enrico.caporossi@gmail.com]

Re: bootlog - how to fix problems

On 9 Dic, 00:05, 98 Guy <9...@Guy.com> wrote:

> Do you have any SCSI drives?
No I haven't

> Is your hard drive being controlled by a
> RAID controller?
I don't know. I think not

> If not, then disable the SCSI controller.
How can I?

> Do you connect to the internet via 56k modem?
Yes

> What's "FlyTV" ?
Is my card for watchin tv...

Sorry for my English

Thanks
Enrico

 

[98 Guy]

Re: bootlog - how to fix problems

enrico.caporossi@gmail.com wrote:

> > Do you have any SCSI drives?
> No I haven't
>
> > Is your hard drive being controlled by a
> > RAID controller?
> I don't know. I think not
>
> > If not, then disable the SCSI controller.
> How can I?

Right-click on "My Computer". Select Device Manager.

Select "View devices by type" (usually default).

You should see a list of devices. One should say SCSI. Click on it,
then hit the "properties" button. A new window will open. There
should be a check-box at the bottom saying "disable in this hardware
profile". Put check in that box.

> > Do you connect to the internet via 56k modem?
> Yes
>
> > What's "FlyTV" ?
> Is my card for watchin tv...
>
> Sorry for my English

Your english is fine.

Your system might start a little faster without the SCSI adapter.

Your AV software (AVG) is probably responsible for more delays.

You should also run msconfig to see what is being loaded in your
system tray.

After windows is fully loaded, click on Start, Run, then type
"msconfig" and hit enter.

Select the Startup tab. You will see a list of items - some with
checkmarks.

You will see:

- ScanRegistry
- System Tray
- LoadPowerProfile (maybe twice)

Ignore those. If you have others (with checkmarks) then post them
here.

 

[glee]

Re: bootlog - how to fix problems

Enrico,

The VAX347S SCSI Controller appears to be the controller installed by the software
"Alcohol 120%" and possibly also by the software "Daemon Tools", both of which are
programs that create virtual optical drives on your computer.

If you have one of those programs installed, and you do not use the 'virtual CD
drive" feature, you may be able to disable the use of virtual drives and stop
loading the driver for them.

If you do not use the programs at all, uninstall them and the SCSI Controller should
disappear. If it does not, follow the procedure described here:
http://club.cdfreaks.com/f64/problem-uninstalling-alcohol-76501/

That is causing the biggest delay in your log.

The second-biggest delay, Starting TCP/IP, may be caused by having a network adapter
(either a network card or an onboard Ethernet adapter) in your system that is not
used, and is set to automatically obtain an IP address. At startup, it will wait up
to 2 minutes while trying to obtain an IP address. If you are not on a network AND
do not use your network (Ethernet) card for connecting to the Internet (via cable
modem or DSL), then you can assign the NIC a static IP address so that it does not
try to contact a DHCP server at startup:
192.168.0.1 (or actually 192.168.0.2 may be better), subnet mask 255.255.255.0

So, if you are NOT connected to any network, do this:
Click Start> Settings> Control Panel> Network> Configuration tab.
Click to select TCP/IP bound to the Ethernet/Network adapter, in the list of
components.
Click the Properties button.
Click the IP Address tab> Specify
Assign an IP address of: 192.168.0.2
and a subnet mask of: 255.255.255.0
Click OK all the way out, and reboot when prompted.

The remainder of your delays do not look too bad, if you can eliminate these top
two, or at least the TCP/IP delay, which is where I would start.
--
Glen Ventura, MS MVP Shell/User, A+


<enrico.caporossi@gmail.com> wrote in message
news:eec083de-9b65-4dcd-b492-d47a5e9ab8ef@e23g2000prf.googlegroups.com...
> On 9 Dic, 00:05, 98 Guy <9...@Guy.com> wrote:
>
>> Do you have any SCSI drives?
> No I haven't
>
>> Is your hard drive being controlled by a
>> RAID controller?
> I don't know. I think not
>
>> If not, then disable the SCSI controller.
> How can I?
>
>> Do you connect to the internet via 56k modem?
> Yes
>
>> What's "FlyTV" ?
> Is my card for watchin tv...
>
> Sorry for my English
>
> Thanks
> Enrico

 

[enrico.caporossi@gmail.com]

Re: bootlog - how to fix problems

Thank you "98 guy" and "glee".

I did the changes, and i think it work's fine.

Now here: <http://digilander.libero.it/katalog/2nd.bla.jpg> is my new
boot log with the delays.
(The previous was here <http://digilander.libero.it/katalog/bla.jpg>).

Can I do something more for fix the delays of the floppy and of the
keyboard?

Thank you again
Enrico

 

[Franc Zabkar]

Re: bootlog - how to fix problems

On Sun, 9 Dec 2007 10:25:26 -0800 (PST), enrico.caporossi@gmail.com
put finger to keyboard and composed:

>Thank you "98 guy" and "glee".
>
>I did the changes, and i think it work's fine.
>
>Now here: <http://digilander.libero.it/katalog/2nd.bla.jpg> is my new
>boot log with the delays.
>(The previous was here <http://digilander.libero.it/katalog/bla.jpg>).
>
>Can I do something more for fix the delays of the floppy and of the
>keyboard?
>
>Thank you again
>Enrico

I have no experience with international versions of Windows, but I'm
wondering whether you really need to load KEYB.COM in those cases
where you are booting directly into the GUI. If not, run Sysedit and
disable it by adding "REM" to the beginning of that line in your
autoexec.bat file, ie ...

rem KEYB.COM ...

I don't know if it makes any difference, but is your keyboard a USB or
PS2 type?

FWIW, it seems to me that many of your delays are related to device
enumeration by the ACPI BIOS. AFAIK, early ACPI implementations were
incomplete or buggy. You might like to probe your CMOS/BIOS setup for
ACPI related settings, or experiment with System Devices in Device
Manager.

- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.

 

[98 Guy]

Re: bootlog - how to fix problems

enrico.caporossi@gmail.com wrote:

> Thank you "98 guy" and "glee".
>
> I did the changes, and i think it work's fine.
>
> Can I do something more for fix the delays of the floppy and of
> the keyboard?

Do you have a European (non-US) keyboard?

You probably don't need keyb.com (look in your config.sys for it, and
remove it).

In Windows, set your keyboard type via control panel.

It's not clear why your floppy controller is taking 16 seconds to
initialize.

Do you use your floppy drive very much? Many systems don't even come
with floppy drives any more. You can disable the floppy controller
the same way as the scsi controller.

 

[enrico.caporossi@gmail.com]

Re: bootlog - how to fix problems

On 9 Dic, 22:27, 98 Guy <9...@Guy.com> wrote:
> Do you have a European (non-US) keyboard?

Yes, an Italian keyboard (PS2 type)

> You probably don't need keyb.com (look in your config.sys for it, and
> remove it).

Ok, I did. Thanks for the help, it works.

> It's not clear why your floppy controller is taking 16 seconds to
> initialize.
>
> Do you use your floppy drive very much? Many systems don't even come
> with floppy drives any more. You can disable the floppy controller
> the same way as the scsi controller.

No, I can't do this. I didn't find a check-box at the bottom saying
"disable in this hardware
profile". I think also is useful to mantain the floppy drive in case
of crash of the system also if I don't use it everyday.

Here is my new bootlog <http://digilander.libero.it/katalog/
3rd.bla.jpg>

Bye.
Enrico

 

[enrico.caporossi@gmail.com]

Re: bootlog - how to fix problems

Here is my new bootlog:
<http://digilander.libero.it/katalog/3rd.bla.jpg>

Bye.
Enrico

 

[Franc Zabkar]

Re: bootlog - how to fix problems

On Sun, 9 Dec 2007 14:02:25 -0800 (PST), enrico.caporossi@gmail.com
put finger to keyboard and composed:

>Here is my new bootlog:
><http://digilander.libero.it/katalog/3rd.bla.jpg>
>
>Bye.
>Enrico

Now instead of keyb.com you have mode.com which takes just as long.


If the MODE command is setting up the keyboard's "typematic rate" (see
below), then REM this line out as well.

MODE CON[:] [RATE=r DELAY=d]

- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.

 

[98 Guy]

Re: bootlog - how to fix problems

enrico.caporossi@gmail.com wrote:

> Here is my new bootlog:
> <http://digilander.libero.it/katalog/3rd.bla.jpg>

I'm seeing this on my system:

Enumerated Standard Floppy Disk Controller (ACPI\*PNP0700\0)

with a duration of 11.222 seconds.

 

[glee]

Re: bootlog - how to fix problems

Try this for the floppy delay:
Right-click "My Computer", click Properties on the menu that appears.
In System properties, click the "Performance" tab> "File System" button> "Floppy
Disk" tab:
Remove the check from the box for "Search for new floppy disk drives each time your
computer starts"

Click OK all the way out, and reboot.
--
Glen Ventura, MS MVP Shell/User, A+


<enrico.caporossi@gmail.com> wrote in message
news:a174e638-268c-4a48-87a9-d84cbb546efa@l16g2000hsf.googlegroups.com...
> Here is my new bootlog:
> <http://digilander.libero.it/katalog/3rd.bla.jpg>
>
> Bye.
> Enrico
>

 

[enrico.caporossi@gmail.com]

Re: bootlog - how to fix problems

On 9 Dic, 23:18, Franc Zabkar wrote:
> Now instead of keyb.com you have mode.com which takes just as long.
>
>
> If the MODE command is setting up the keyboard's "typematic rate" (see
> below), then REM this line out as well.
>
> MODE CON[:] [RATE=r DELAY=d]

Now my autoexec.bat is empty nothing more to do there ;-)

the last canges are:
rem mode con codepage prepare=((850) C:\WINDOWS\COMMAND\ega.cpi)
rem mode con codepage select=850

Here is my 4th bootlog:
<http://digilander.libero.it/katalog/4th.bla.jpg>

The problem with the foppy is disappeared. So it seems.

Something more to do? ;-)

A lot of thanks
Enrico

 

[Franc Zabkar]

Re: bootlog - how to fix problems

On Sun, 9 Dec 2007 18:33:34 -0500, "glee" <glee29@spamindspring.com>
put finger to keyboard and composed:

>Try this for the floppy delay:
>Right-click "My Computer", click Properties on the menu that appears.
>In System properties, click the "Performance" tab> "File System" button> "Floppy
>Disk" tab:
>Remove the check from the box for "Search for new floppy disk drives each time your
>computer starts"
>
>Click OK all the way out, and reboot.

That's interesting. My search check box is ticked, but I still see
only a short enumeration time.

15:29:05 0.17 Enumerating Standard Floppy Disk Controller
(BIOS\*PNP0700\0C)

15:29:06 0.00 Enumerated Standard Floppy Disk Controller
(BIOS\*PNP0700\0C)

The difference appears to be that my old socket 7 motherboard doesn't
support ACPI.

I'm not sure why I see two entries, except that I have the following
two registry keys:

HKEY_LOCAL_MACHINE\Enum\BIOS\*PNP0700\0B
HKEY_LOCAL_MACHINE\Enum\BIOS\*PNP0700\0C

The "0C" device appears twice in the bootlog, but the "0B" device is
absent. They appear identical except that the first is using an
"fdc\0001" driver, and the second is using "fdc\0000". Both have a
DeviceDesc of "Standard Floppy Disk Controller", and a HardwareID of
"BIOS\*PNP0700,*PNP0700". There is only one FDC in Device Manager.

BTW, I notice that the OP's system is now showing a load failure for
AVGCORE which makes me wonder whether AVG Antivirus is working
properly.

- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.

 

[Franc Zabkar]

Re: bootlog - how to fix problems

On Sun, 9 Dec 2007 15:43:37 -0800 (PST), enrico.caporossi@gmail.com
put finger to keyboard and composed:

>Here is my 4th bootlog:
><http://digilander.libero.it/katalog/4th.bla.jpg>
>
>The problem with the foppy is disappeared. So it seems.
>
>Something more to do? ;-)

The message, "INITCOMPLETEFAILED = AVGCORE", suggests that your AVG
antivirus may not be initialising properly. Strangely, everything
looked OK in your first screen shot. <shrug>

Also, the fact that IFSHLP.SYS is now taking 13 seconds to load
suggests to me that no matter what you do, there is always going to be
a 12-13 second delay during which something is being set up. It would
appear that neither KEYB.COM nor MODE.COM were responsible for this
delay, and I now suspect that IFSHLP.SYS may not be responsible for
it, either.

- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.

 

[glee]

Re: bootlog - how to fix problems

"Franc Zabkar" <fzabkar@iinternode.on.net> wrote in message
news:ar3pl3djenu87pqbtl1ht1t31gkrpg4lic@4ax.com...
> On Sun, 9 Dec 2007 18:33:34 -0500, "glee" <glee29@spamindspring.com>
> put finger to keyboard and composed:
>
>>Try this for the floppy delay:
>>Right-click "My Computer", click Properties on the menu that appears.
>>In System properties, click the "Performance" tab> "File System" button> "Floppy
>>Disk" tab:
>>Remove the check from the box for "Search for new floppy disk drives each time
>>your
>>computer starts"
>>
>>Click OK all the way out, and reboot.
>
> That's interesting. My search check box is ticked, but I still see
> only a short enumeration time.
>
> 15:29:05 0.17 Enumerating Standard Floppy Disk Controller
> (BIOS\*PNP0700\0C)
>
> 15:29:06 0.00 Enumerated Standard Floppy Disk Controller
> (BIOS\*PNP0700\0C)
>
> The difference appears to be that my old socket 7 motherboard doesn't
> support ACPI.
>
> I'm not sure why I see two entries, except that I have the following
> two registry keys:
>
> HKEY_LOCAL_MACHINE\Enum\BIOS\*PNP0700\0B
> HKEY_LOCAL_MACHINE\Enum\BIOS\*PNP0700\0C
>
> The "0C" device appears twice in the bootlog, but the "0B" device is
> absent. They appear identical except that the first is using an
> "fdc\0001" driver, and the second is using "fdc\0000". Both have a
> DeviceDesc of "Standard Floppy Disk Controller", and a HardwareID of
> "BIOS\*PNP0700,*PNP0700". There is only one FDC in Device Manager.
>
> BTW, I notice that the OP's system is now showing a load failure for
> AVGCORE which makes me wonder whether AVG Antivirus is working
> properly.

Re: AVGCORE....yes, I saw that too, and am wondering why it didn't show up in the
earlier logs' failures, and if it will show up again if another logged boot is done.
If it persists, I would reinstall AVG.

Re: your two FDC entries in the bootlog, does more than one FDC and/or more than one
floppy disk drive appear in SAFE MODE Device Manager? If so, delete them all and
restart.
--
Glen Ventura, MS MVP Shell/User, A+

 

[Franc Zabkar]

Re: bootlog - how to fix problems

On Mon, 10 Dec 2007 12:31:35 -0500, "glee" <glee29@spamindspring.com>
put finger to keyboard and composed:

>"Franc Zabkar" <fzabkar@iinternode.on.net> wrote in message
>news:ar3pl3djenu87pqbtl1ht1t31gkrpg4lic@4ax.com...

>> My search check box is ticked, but I still see
>> only a short enumeration time.
>>
>> 15:29:05 0.17 Enumerating Standard Floppy Disk Controller
>> (BIOS\*PNP0700\0C)
>>
>> 15:29:06 0.00 Enumerated Standard Floppy Disk Controller
>> (BIOS\*PNP0700\0C)
>>
>> The difference appears to be that my old socket 7 motherboard doesn't
>> support ACPI.
>>
>> I'm not sure why I see two entries, except that I have the following
>> two registry keys:
>>
>> HKEY_LOCAL_MACHINE\Enum\BIOS\*PNP0700\0B
>> HKEY_LOCAL_MACHINE\Enum\BIOS\*PNP0700\0C
>>
>> The "0C" device appears twice in the bootlog, but the "0B" device is
>> absent. They appear identical except that the first is using an
>> "fdc\0001" driver, and the second is using "fdc\0000". Both have a
>> DeviceDesc of "Standard Floppy Disk Controller", and a HardwareID of
>> "BIOS\*PNP0700,*PNP0700". There is only one FDC in Device Manager.
>>
>> BTW, I notice that the OP's system is now showing a load failure for
>> AVGCORE which makes me wonder whether AVG Antivirus is working
>> properly.
>
>Re: AVGCORE....yes, I saw that too, and am wondering why it didn't show up in the
>earlier logs' failures, and if it will show up again if another logged boot is done.
>If it persists, I would reinstall AVG.
>
>Re: your two FDC entries in the bootlog, does more than one FDC and/or more than one
>floppy disk drive appear in SAFE MODE Device Manager? If so, delete them all and
>restart.

Thanks. I'm always hesitant to go into safe mode (because my desktop
settings may be trashed), but after doing so I saw the two FDC
entries, deleted them both, and restarted. I now have only the one
device at HKLM\Enum\BIOS\*PNP0700.

- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.

 

[glee]

Re: bootlog - how to fix problems

"Franc Zabkar" <fzabkar@iinternode.on.net> wrote in message
news:r0ttl3h2t7i1pm4216jpj92hfqvggig4sh@4ax.com...
> On Mon, 10 Dec 2007 12:31:35 -0500, "glee" <glee29@spamindspring.com>
> put finger to keyboard and composed:
>
>>"Franc Zabkar" <fzabkar@iinternode.on.net> wrote in message
>>news:ar3pl3djenu87pqbtl1ht1t31gkrpg4lic@4ax.com...
>
>>> My search check box is ticked, but I still see
>>> only a short enumeration time.
>>>
>>> 15:29:05 0.17 Enumerating Standard Floppy Disk Controller
>>> (BIOS\*PNP0700\0C)
>>>
>>> 15:29:06 0.00 Enumerated Standard Floppy Disk Controller
>>> (BIOS\*PNP0700\0C)
>>>
>>> The difference appears to be that my old socket 7 motherboard doesn't
>>> support ACPI.
>>>
>>> I'm not sure why I see two entries, except that I have the following
>>> two registry keys:
>>>
>>> HKEY_LOCAL_MACHINE\Enum\BIOS\*PNP0700\0B
>>> HKEY_LOCAL_MACHINE\Enum\BIOS\*PNP0700\0C
>>>
>>> The "0C" device appears twice in the bootlog, but the "0B" device is
>>> absent. They appear identical except that the first is using an
>>> "fdc\0001" driver, and the second is using "fdc\0000". Both have a
>>> DeviceDesc of "Standard Floppy Disk Controller", and a HardwareID of
>>> "BIOS\*PNP0700,*PNP0700". There is only one FDC in Device Manager.
>>> snip
>> snip
>>Re: your two FDC entries in the bootlog, does more than one FDC and/or more than
>>one
>>floppy disk drive appear in SAFE MODE Device Manager? If so, delete them all and
>>restart.
>
> Thanks. I'm always hesitant to go into safe mode (because my desktop
> settings may be trashed), but after doing so I saw the two FDC
> entries, deleted them both, and restarted. I now have only the one
> device at HKLM\Enum\BIOS\*PNP0700.

Yep, Safe Mode can make an aesthetic mess, but also changes settings. I always go
to Folder Options' View settings afterwards, to re-set what has been toggled by Safe
Mode, usually things like "show full path in title bar (or address bar)", which I
enable and Safe Mode disables for reasons beyond my comprehension.
--
Glen Ventura, MS MVP Shell/User, A+