Windows 2000 Thinkpad cold boot problem

  • Thread starter Thread starter Roger Fink
  • Start date Start date
R

Roger Fink

I have two nearly identical W2k ThinkPad laptops, which display the same
problem. During a cold boot GoBack is unable to initialize (if that is the
correct term for this), and when that happens the boot just hangs. Instead
of proceeding from "Preparing Network Connections" to "Applying Security
Policy", and then to the logon screen, instead it proceeds from "Preparing
Network Connections" to "Applying Computer Settings", and from there into
limbo. I'm sure GoBack is the problem because in a successful boot, by
design the GoBack logo will momentarily flash on the screen once it's
initialized. After this failure, if you immediately reboot from shutdown,
the next boot will be successful, as will a reboot from within Windows.

My desktop does not exhibit this problem.

In general I try to minimize what's included in start-up through MS-config,
but there are some proprietary IBM functions that I don't tamper with. I
very much want to keep GoBack on these machines, so I'm wondering if there
is anything I can do to correct this situation.
 
The issue should be covered in one of the listings here.
http://searchg.symantec.com/search?...site=symc_en_US&output=xml_no_dtd&context=gbh

Roger Fink wrote:
> I have two nearly identical W2k ThinkPad laptops, which display the same
> problem. During a cold boot GoBack is unable to initialize (if that is the
> correct term for this), and when that happens the boot just hangs. Instead
> of proceeding from "Preparing Network Connections" to "Applying Security
> Policy", and then to the logon screen, instead it proceeds from "Preparing
> Network Connections" to "Applying Computer Settings", and from there into
> limbo. I'm sure GoBack is the problem because in a successful boot, by
> design the GoBack logo will momentarily flash on the screen once it's
> initialized. After this failure, if you immediately reboot from shutdown,
> the next boot will be successful, as will a reboot from within Windows.
>
> My desktop does not exhibit this problem.
>
> In general I try to minimize what's included in start-up through MS-config,
> but there are some proprietary IBM functions that I don't tamper with. I
> very much want to keep GoBack on these machines, so I'm wondering if there
> is anything I can do to correct this situation.
>
>
 
As you say the Problem is with GoBack, which also causes problems in WinXp,
perhaps check symantec or Roxio for any FAQ's

"Roger Fink" <fink@manana.org> wrote in message
news:uagaLLFhIHA.4880@TK2MSFTNGP03.phx.gbl...
>I have two nearly identical W2k ThinkPad laptops, which display the same
> problem. During a cold boot GoBack is unable to initialize (if that is the
> correct term for this), and when that happens the boot just hangs. Instead
> of proceeding from "Preparing Network Connections" to "Applying Security
> Policy", and then to the logon screen, instead it proceeds from "Preparing
> Network Connections" to "Applying Computer Settings", and from there into
> limbo. I'm sure GoBack is the problem because in a successful boot, by
> design the GoBack logo will momentarily flash on the screen once it's
> initialized. After this failure, if you immediately reboot from shutdown,
> the next boot will be successful, as will a reboot from within Windows.
>
> My desktop does not exhibit this problem.
>
> In general I try to minimize what's included in start-up through
> MS-config,
> but there are some proprietary IBM functions that I don't tamper with. I
> very much want to keep GoBack on these machines, so I'm wondering if there
> is anything I can do to correct this situation.
>
>
 
Unfortunately (or perhaps fortunately, in the eyes of more than a few) I
have the earlier Roxio Deluxe 3.0 version, and the response to the relevant
question on the Symantec site appears to be integrated with the Norton
version. I did check my 50 page Roxio faqs and there are a few leads there -
not too promising, but I'll follow up.

The reason I thought it might be solvable outside of manipulating GoBack is
the predictable manner in which it fails to load. It always loads on reboot.
It always loads on cold boot if that cold boot immediately follows a
shutdown. It never loads on cold boot if some period of time elapses, say
twenty minutes. One wonders for instance if temperature affects boot time or
boot activity and could be a factor. What I was thinking was that maybe
there was a way to increase boot time, or intervals between certain process
loadings, or to change the order of process loadings.

Bob I wrote:
> The issue should be covered in one of the listings here.
>
http://searchg.symantec.com/search?...site=symc_en_US&output=xml_no_dtd&context=gbh
>
> Roger Fink wrote:
>> I have two nearly identical W2k ThinkPad laptops, which display the
>> same
>> problem. During a cold boot GoBack is unable to initialize (if that
>> is the
>> correct term for this), and when that happens the boot just hangs.
>> Instead
>> of proceeding from "Preparing Network Connections" to "Applying
>> Security
>> Policy", and then to the logon screen, instead it proceeds from
>> "Preparing
>> Network Connections" to "Applying Computer Settings", and from there
>> into
>> limbo. I'm sure GoBack is the problem because in a successful boot,
>> by
>> design the GoBack logo will momentarily flash on the screen once it's
>> initialized. After this failure, if you immediately reboot from
>> shutdown,
>> the next boot will be successful, as will a reboot from within
>> Windows.
>>
>> My desktop does not exhibit this problem.
>>
>> In general I try to minimize what's included in start-up through
>> MS-config,
>> but there are some proprietary IBM functions that I don't tamper
>> with. I
>> very much want to keep GoBack on these machines, so I'm wondering if
>> there
>> is anything I can do to correct this situation.
 
Umm, some BIOS's have an IDE delay time that is adjustable. You could
check that.

Roger Fink wrote:
> Unfortunately (or perhaps fortunately, in the eyes of more than a few) I
> have the earlier Roxio Deluxe 3.0 version, and the response to the relevant
> question on the Symantec site appears to be integrated with the Norton
> version. I did check my 50 page Roxio faqs and there are a few leads there -
> not too promising, but I'll follow up.
>
> The reason I thought it might be solvable outside of manipulating GoBack is
> the predictable manner in which it fails to load. It always loads on reboot.
> It always loads on cold boot if that cold boot immediately follows a
> shutdown. It never loads on cold boot if some period of time elapses, say
> twenty minutes. One wonders for instance if temperature affects boot time or
> boot activity and could be a factor. What I was thinking was that maybe
> there was a way to increase boot time, or intervals between certain process
> loadings, or to change the order of process loadings.
>
> Bob I wrote:
>
>>The issue should be covered in one of the listings here.
>>
>
> http://searchg.symantec.com/search?...site=symc_en_US&output=xml_no_dtd&context=gbh
>
>>Roger Fink wrote:
>>
>>>I have two nearly identical W2k ThinkPad laptops, which display the
>>>same
>>>problem. During a cold boot GoBack is unable to initialize (if that
>>>is the
>>>correct term for this), and when that happens the boot just hangs.
>>>Instead
>>>of proceeding from "Preparing Network Connections" to "Applying
>>>Security
>>>Policy", and then to the logon screen, instead it proceeds from
>>>"Preparing
>>>Network Connections" to "Applying Computer Settings", and from there
>>>into
>>>limbo. I'm sure GoBack is the problem because in a successful boot,
>>>by
>>>design the GoBack logo will momentarily flash on the screen once it's
>>>initialized. After this failure, if you immediately reboot from
>>>shutdown,
>>>the next boot will be successful, as will a reboot from within
>>>Windows.
>>>
>>>My desktop does not exhibit this problem.
>>>
>>>In general I try to minimize what's included in start-up through
>>>MS-config,
>>>but there are some proprietary IBM functions that I don't tamper
>>>with. I
>>>very much want to keep GoBack on these machines, so I'm wondering if
>>>there
>>>is anything I can do to correct this situation.
>
>
>
 
You cannot change the order of Proccesses / startups loading without the use
of a third party tool, or batch file
Perhaps for your first cold boot, use Safe Mode>Boot logging then examine
the log & see if it gives any other clues

"Roger Fink" <fink@manana.org> wrote in message
news:O70emQHhIHA.4164@TK2MSFTNGP05.phx.gbl...
> Unfortunately (or perhaps fortunately, in the eyes of more than a few) I
> have the earlier Roxio Deluxe 3.0 version, and the response to the
> relevant
> question on the Symantec site appears to be integrated with the Norton
> version. I did check my 50 page Roxio faqs and there are a few leads
> there -
> not too promising, but I'll follow up.
>
> The reason I thought it might be solvable outside of manipulating GoBack
> is
> the predictable manner in which it fails to load. It always loads on
> reboot.
> It always loads on cold boot if that cold boot immediately follows a
> shutdown. It never loads on cold boot if some period of time elapses, say
> twenty minutes. One wonders for instance if temperature affects boot time
> or
> boot activity and could be a factor. What I was thinking was that maybe
> there was a way to increase boot time, or intervals between certain
> process
> loadings, or to change the order of process loadings.
>
> Bob I wrote:
>> The issue should be covered in one of the listings here.
>>
> http://searchg.symantec.com/search?...site=symc_en_US&output=xml_no_dtd&context=gbh
>>
>> Roger Fink wrote:
>>> I have two nearly identical W2k ThinkPad laptops, which display the
>>> same
>>> problem. During a cold boot GoBack is unable to initialize (if that
>>> is the
>>> correct term for this), and when that happens the boot just hangs.
>>> Instead
>>> of proceeding from "Preparing Network Connections" to "Applying
>>> Security
>>> Policy", and then to the logon screen, instead it proceeds from
>>> "Preparing
>>> Network Connections" to "Applying Computer Settings", and from there
>>> into
>>> limbo. I'm sure GoBack is the problem because in a successful boot,
>>> by
>>> design the GoBack logo will momentarily flash on the screen once it's
>>> initialized. After this failure, if you immediately reboot from
>>> shutdown,
>>> the next boot will be successful, as will a reboot from within
>>> Windows.
>>>
>>> My desktop does not exhibit this problem.
>>>
>>> In general I try to minimize what's included in start-up through
>>> MS-config,
>>> but there are some proprietary IBM functions that I don't tamper
>>> with. I
>>> very much want to keep GoBack on these machines, so I'm wondering if
>>> there
>>> is anything I can do to correct this situation.
>
>
 
Back
Top