Annoyances.org
Home » Windows Me Discussion Forum » Message 1193750210 » Entire Thread Search | Help | Home
  
WinME boot sequence problem?
Showing all messages in thread #1193750210
Windows Me Annoyances Discussion Forum


The following are all of the messages in this thread (6 in all), shown in chronological order. Click any message subject to view that message by itself or to view the thread hierarchy.
WinME boot sequence problem?
Tuesday, October 30, 2007 at 6:16 am
Posted by Ed (582 messages posted)

As annoyances go, this one is not very major, but it has always bothered me. I only noticed it because I use both Win98 and WinME, and can compare them side-by-side.

When I boot up my Windows 98 computer (running Win98 Second Edition) it starts up straight away, and displays the Desktop. But when I boot my Windows ME computer, when it reaches that stage it then thrashes the hard disk for about 5 seconds.

I recently investigated this, by generating a boot log (C:\BOOTLOG.TXT) for the WinME machine. And I discovered to my surprise that, whereas the Win98 machine ends all boot up activity once it has loaded Win98, the WinME machine then goes into a mad disk thrash while it UNLOADS a bunch of stuff that it had loaded earlier in the boot up process.

Does anyone know why WinME is doing this? Is there anything I should be doing to prevent it loading the items which it then unloads?

To be a bit technical for a moment, WinME reaches a state at which it records these two lines in the boot log -

EndTerminate = Win32
EndTerminate = KERNEL

I see from a Win98SE boot log that when this occurs in Win98 the boot sequence is complete, and the bootlog ends. But in WinME the boot sequence then does the mad disk thrashing and the unloading, starting with these lines -

[00155915] Removing Unknown (HTREE\RESERVED\0)
[00155916] Removed Unknown (HTREE\RESERVED\0)
[00155916] Removing Processor support (ROOT\PROCESSOR_UPDATE\0000)
[00155916] Removed Processor support (ROOT\PROCESSOR_UPDATE\0000)

It then removes -

The Microsoft Kernel System Audio Renderer
The Microsoft Kernel Audio Mixer
The Plug and Play Software Device Enumerator (ROOT\SWENUM\0000)
The Composite Power Source (ACPI\COMPBATT\ROOT&*PNP0C08&0000)
The ACPI System Button (ACPI\BUTTON\ROOT&*PNP0C08&0000)
The ACPI Power Button (ACPI\*PNP0C0C\0)
The Intel(r) 82815 Processor to I/O Controller - 1130
The LG L1752S [the Monitor is model L1752S]
The SpeedTouch 330 ADSL Modem (USB\VID_06B9&PID_4061\000E50FB9A96)
The Psion WaveFinder [a USB DAB radio]
Two USB Root Hubs
The USB 2.0 Root Hub Device
The ACPI Sleep Button (ACPI\*PNP0C0E\0)
The System board (ROOT\*PNP0C01\0000)
The Lexmark Z12 Series ColorFine (ROOT\PRINTER\0000) [USB printer]
The Alcatel Class Registry Bus (ROOT\ALCACR\0000)
The Client for Microsoft Networks (NETWORK\VREDIR\0001)
The TCP/IP (NETWORK\MSTCP\0000)
The Dial-Up Adapter (ROOT\NET\0000)

I don't believe it is genuinely unloading these items, because the computer works perfectly okay, and the devices said to be unloaded (e.g. the printer, the USB 2.0 ports, etc) all function normally.

Anyone care to cast any light on what this unloading process is all about?

I have checked in Device Manager, and there are no "ghost" entries showing, and there are no faulty devices indicated. So this is not some response to a device conflict or a faulty installation! And I am experiencing no problems of any description with the computer.

I can offer only one further clue: each removal is accomplished by two lines in the boot log, the first of which says "Removing [device description]", and the second line says "Removed [device description]".

The final two lines of the boot log are -

[00155917] Removing Dial-Up Adapter (ROOT\NET\0000)
[00155917] Removed Dial-Up Adapter (ROOT\NET\0000)

In point of fact, I admit to using broadband, not dial-up. But nevertheless the PC still requires the TCP/IP protocols to be installed, as I found out by accident one time, when I was uninstalling my old PCI modem card during the broadband installation.

As I say, not the biggest annoyance I've ever found in WinME, but puzzling nonetheless. What am I overlooking? Why is it unloading all these items?

Ed

[Reply or follow-up to this message]

re: WinME boot sequence problem?
Tuesday, October 30, 2007 at 1:19 pm
Posted by C K (5976 messages posted)

Is system restore active?






On Tuesday, October 30, 2007 at 5:16 am, Ed wrote:
>As annoyances go, this one is not very major, but it has always bothered me. I only
>noticed it because I use both Win98 and WinME, and can compare them side-by-side.
>
>When I boot up my Windows 98 computer (running Win98 Second Edition) it starts up
>straight away, and displays the Desktop. But when I boot my Windows ME computer,
>when it reaches that stage it then thrashes the hard disk for about 5 seconds.
>
>I recently investigated this, by generating a boot log (C:\BOOTLOG.TXT) for the WinME
>machine. And I discovered to my surprise that, whereas the Win98 machine ends all
>boot up activity once it has loaded Win98, the WinME machine then goes into a mad
>disk thrash while it UNLOADS a bunch of stuff that it had loaded earlier in the boot
>up process.
>
>Does anyone know why WinME is doing this? Is there anything I should be doing to
>prevent it loading the items which it then unloads?
>
>To be a bit technical for a moment, WinME reaches a state at which it records these
>two lines in the boot log -
>
>EndTerminate = Win32
>EndTerminate = KERNEL
>
>I see from a Win98SE boot log that when this occurs in Win98 the boot sequence is
>complete, and the bootlog ends. But in WinME the boot sequence then does the mad
>disk thrashing and the unloading, starting with these lines -
>
>[00155915] Removing Unknown (HTREE\RESERVED\0)
>[00155916] Removed Unknown (HTREE\RESERVED\0)
>[00155916] Removing Processor support (ROOT\PROCESSOR_UPDATE\0000)
>[00155916] Removed Processor support (ROOT\PROCESSOR_UPDATE\0000)
>
>It then removes -
>
>The Microsoft Kernel System Audio Renderer
>The Microsoft Kernel Audio Mixer
>The Plug and Play Software Device Enumerator (ROOT\SWENUM\0000)
>The Composite Power Source (ACPI\COMPBATT\ROOT&*PNP0C08&0000)
>The ACPI System Button (ACPI\BUTTON\ROOT&*PNP0C08&0000)
>The ACPI Power Button (ACPI\*PNP0C0C\0)
>The Intel(r) 82815 Processor to I/O Controller - 1130
>The LG L1752S [the Monitor is model L1752S]
>The SpeedTouch 330 ADSL Modem (USB\VID_06B9&PID_4061\000E50FB9A96)
>The Psion WaveFinder [a USB DAB radio]
>Two USB Root Hubs
>The USB 2.0 Root Hub Device
>The ACPI Sleep Button (ACPI\*PNP0C0E\0)
>The System board (ROOT\*PNP0C01\0000)
>The Lexmark Z12 Series ColorFine (ROOT\PRINTER\0000) [USB printer]
>The Alcatel Class Registry Bus (ROOT\ALCACR\0000)
>The Client for Microsoft Networks (NETWORK\VREDIR\0001)
>The TCP/IP (NETWORK\MSTCP\0000)
>The Dial-Up Adapter (ROOT\NET\0000)
>
>I don't believe it is genuinely unloading these items, because the computer works
>perfectly okay, and the devices said to be unloaded (e.g. the printer, the USB 2.0
>ports, etc) all function normally.
>
>Anyone care to cast any light on what this unloading process is all about?
>
>I have checked in Device Manager, and there are no "ghost" entries showing, and there
>are no faulty devices indicated. So this is not some response to a device conflict
>or a faulty installation! And I am experiencing no problems of any description with
>the computer.
>
>I can offer only one further clue: each removal is accomplished by two lines in the
>boot log, the first of which says "Removing [device description]", and the second
>line says "Removed [device description]".
>
>The final two lines of the boot log are -
>
>[00155917] Removing Dial-Up Adapter (ROOT\NET\0000)
>[00155917] Removed Dial-Up Adapter (ROOT\NET\0000)
>
>In point of fact, I admit to using broadband, not dial-up. But nevertheless the PC
>still requires the TCP/IP protocols to be installed, as I found out by accident one
>time, when I was uninstalling my old PCI modem card during the broadband installation.
>
>As I say, not the biggest annoyance I've ever found in WinME, but puzzling nonetheless.
>What am I overlooking? Why is it unloading all these items?
>
>Ed

[Reply or follow-up to this message]

re: WinME boot sequence problem?
Thursday, November 1, 2007 at 11:35 am
Posted by Ed (582 messages posted)

No, System Restore has been switched off.


On Tuesday, October 30, 2007 at 12:19 pm, C K wrote:
>Is system restore active?
>
>
>

[Reply or follow-up to this message]

re: WinME boot sequence problem?
Thursday, November 1, 2007 at 12:06 pm
Posted by C K (5976 messages posted)

They all do it for a short time as the registry and some other files are backed up. 
 Happens in every system for emergancy startup/recovery options.  System restore 
doesn't have anything to do with that function...  Other than that, not sure but 
there could be other software/utilities running and starting up such as AV etc.. 
 It's not like the old DOS days..






On Thursday, November 1, 2007 at 10:35 am, Ed wrote:
>No, System Restore has been switched off.
>
>
>

[Reply or follow-up to this message]

re: WinME boot sequence problem?
Thursday, November 1, 2007 at 12:12 pm
Posted by C K (5976 messages posted)

Also, swap file loading and maintenance.  There are a number of things that go on 
at start up.






On Thursday, November 1, 2007 at 10:35 am, Ed wrote:
>No, System Restore has been switched off.
>
>
>

[Reply or follow-up to this message]

re: WinME boot sequence problem?
Thursday, November 1, 2007 at 8:02 pm
Posted by Ed (582 messages posted)

I really don't think it can be any of the things you mention. The bootlog is *very* specific. Windows is unloading the dozen or so device entries mentioned in my initial post.

In particular, this is not being caused by any software or utilities loading. It's being caused by things being unloaded.

I'm wondering why WinME is unloading, at this final stage in the boot-up process, device entries that were successfully loaded earlier in the boot sequence. Win98SE does not do this, as mentioned in my initial post; so what is the purpose of WinME in doing it?

Ed




On Thursday, November 1, 2007 at 11:06 am, C K wrote:
>They all do it for a short time as the registry and some other files are backed up.
> Happens in every system for emergancy startup/recovery options. System restore
>doesn't have anything to do with that function... Other than that, not sure but
>there could be other software/utilities running and starting up such as AV etc..
> It's not like the old DOS days..
>
>
>

[Reply or follow-up to this message]

Tip: Use one of the [Reply or follow-up to this message] links above to add a message to this thread
Return to the Windows Me Discussion Forum

All content at Annoyances.org is Copyright © 1995-2008 Creative Elementtm All rights reserved.
Please do not plagiarize; redistributing these pages without permission is strictly prohibited.