X64 locks up at SHUTDOWN sometimes - after running for a few days

That seems to be the key...

MSI RS480M2-IL mobo with Athlon 64 - 3000+ and 2 x 512 DDR400 ram.

Has a Seagate 160 Gb SATA drive as well as 2 EIDE 40 Gb drives... the Seaget
is partiitoned into 2 X 20 Gb partitions with E holding a WXP Pro SP1 and F
having the WXP Pro X64 machine... Somehow thru the X64 install the install
process wrote the system files (ntldr et al) on the C drive...

However, this is only a X64 problem.

There seem to be no other problems...

Anyone?

TIA.

Gary D

The system files are always written to your %root% drive. Your boot
sequence in your BIOS determines this. If you change boot sequence you will
have to make copies of your system files to the new root drive and adjust
your boot.ini accordingly. The shutdown problem has been reported here a
couple of times as having to do with installing Avast AV, but most people
here using it seem not to be having a problem, so it must be a conflict with
other drivers or software.


"Gary J. Dikkema" <gary_d_no_spam_@cdir.ca> wrote in message
news:...
> That seems to be the key...
>
> MSI RS480M2-IL mobo with Athlon 64 - 3000+ and 2 x 512 DDR400 ram.
>
> Has a Seagate 160 Gb SATA drive as well as 2 EIDE 40 Gb drives... the
> Seaget is partiitoned into 2 X 20 Gb partitions with E holding a WXP Pro
> SP1 and F having the WXP Pro X64 machine... Somehow thru the X64 install
> the install process wrote the system files (ntldr et al) on the C drive...
>
> However, this is only a X64 problem.
>
> There seem to be no other problems...
>
> Anyone?
>
> TIA.
>
> Gary D
>
>

Yes, I had Avast on my x64 Edition desktop, and it would sometimes lock.
Switched to eTrust, no problem since. As John said, however, the problem
can be more complex than just that.

"Gary J. Dikkema" <gary_d_no_spam_@cdir.ca> wrote in message
news:...
> That seems to be the key...
>
> MSI RS480M2-IL mobo with Athlon 64 - 3000+ and 2 x 512 DDR400 ram.
>
> Has a Seagate 160 Gb SATA drive as well as 2 EIDE 40 Gb drives... the
> Seaget is partiitoned into 2 X 20 Gb partitions with E holding a WXP Pro
> SP1 and F having the WXP Pro X64 machine... Somehow thru the X64 install
> the install process wrote the system files (ntldr et al) on the C drive...
>
> However, this is only a X64 problem.
>
> There seem to be no other problems...
>
> Anyone?
>
> TIA.
>
> Gary D
>
>

I will uninstall Avast... should have mentioned that I had it installed.

We'll see if that makes any difference though...


"M. Murcek" <> wrote in message
news:...
> Yes, I had Avast on my x64 Edition desktop, and it would sometimes lock.
> Switched to eTrust, no problem since. As John said, however, the problem
> can be more complex than just that.
>
> "Gary J. Dikkema" <gary_d_no_spam_@cdir.ca> wrote in message
> news:...
>> That seems to be the key...
>>
>> MSI RS480M2-IL mobo with Athlon 64 - 3000+ and 2 x 512 DDR400 ram.
>>
>> Has a Seagate 160 Gb SATA drive as well as 2 EIDE 40 Gb drives... the
>> Seaget is partiitoned into 2 X 20 Gb partitions with E holding a WXP Pro
>> SP1 and F having the WXP Pro X64 machine... Somehow thru the X64 install
>> the install process wrote the system files (ntldr et al) on the C
>> drive...
>>
>> However, this is only a X64 problem.
>>
>> There seem to be no other problems...
>>
>> Anyone?
>>
>> TIA.
>>
>> Gary D
>>
>>
>
>

It will only boot to the X64 machine if I tell it to boot from C...
(sequence in Bios).

However, not sure if that is causing shutdown problems or not.

Regards.


"John Barnes" <> wrote in message
news:Oz$...
> The system files are always written to your %root% drive. Your boot
> sequence in your BIOS determines this. If you change boot sequence you
> will have to make copies of your system files to the new root drive and
> adjust your boot.ini accordingly. The shutdown problem has been reported
> here a couple of times as having to do with installing Avast AV, but most
> people here using it seem not to be having a problem, so it must be a
> conflict with other drivers or software.
>
>
> "Gary J. Dikkema" <gary_d_no_spam_@cdir.ca> wrote in message
> news:...
>> That seems to be the key...
>>
>> MSI RS480M2-IL mobo with Athlon 64 - 3000+ and 2 x 512 DDR400 ram.
>>
>> Has a Seagate 160 Gb SATA drive as well as 2 EIDE 40 Gb drives... the
>> Seaget is partiitoned into 2 X 20 Gb partitions with E holding a WXP Pro
>> SP1 and F having the WXP Pro X64 machine... Somehow thru the X64 install
>> the install process wrote the system files (ntldr et al) on the C
>> drive...
>>
>> However, this is only a X64 problem.
>>
>> There seem to be no other problems...
>>
>> Anyone?
>>
>> TIA.
>>
>> Gary D
>>
>>
>
>

Should have nothing to do with your shutdown. If you want to change your
boot sequence make sure you have the proper ntldr and ntdetect.com and
modified boot.ini file on the %root% of each drive you want to have as the
1st hard drive in your boot sequence in the BIOS. Must be the ones from x64
as they seem not to be backward compatible.


"Gary J. Dikkema" <gary_d_no_spam_@cdir.ca> wrote in message
news:...
> It will only boot to the X64 machine if I tell it to boot from C...
> (sequence in Bios).
>
> However, not sure if that is causing shutdown problems or not.
>
> Regards.
>
>
> "John Barnes" <> wrote in message
> news:Oz$...
>> The system files are always written to your %root% drive. Your boot
>> sequence in your BIOS determines this. If you change boot sequence you
>> will have to make copies of your system files to the new root drive and
>> adjust your boot.ini accordingly. The shutdown problem has been reported
>> here a couple of times as having to do with installing Avast AV, but most
>> people here using it seem not to be having a problem, so it must be a
>> conflict with other drivers or software.
>>
>>
>> "Gary J. Dikkema" <gary_d_no_spam_@cdir.ca> wrote in message
>> news:...
>>> That seems to be the key...
>>>
>>> MSI RS480M2-IL mobo with Athlon 64 - 3000+ and 2 x 512 DDR400 ram.
>>>
>>> Has a Seagate 160 Gb SATA drive as well as 2 EIDE 40 Gb drives... the
>>> Seaget is partiitoned into 2 X 20 Gb partitions with E holding a WXP Pro
>>> SP1 and F having the WXP Pro X64 machine... Somehow thru the X64 install
>>> the install process wrote the system files (ntldr et al) on the C
>>> drive...
>>>
>>> However, this is only a X64 problem.
>>>
>>> There seem to be no other problems...
>>>
>>> Anyone?
>>>
>>> TIA.
>>>
>>> Gary D
>>>
>>>
>>
>>
>
>

Thanks John... much like the WXP and the WS2003 boot files... and backward
compatibility.


"John Barnes" <> wrote in message
news:%...
> Should have nothing to do with your shutdown. If you want to change your
> boot sequence make sure you have the proper ntldr and ntdetect.com and
> modified boot.ini file on the %root% of each drive you want to have as the
> 1st hard drive in your boot sequence in the BIOS. Must be the ones from
> x64 as they seem not to be backward compatible.
>
>
> "Gary J. Dikkema" <gary_d_no_spam_@cdir.ca> wrote in message
> news:...
>> It will only boot to the X64 machine if I tell it to boot from C...
>> (sequence in Bios).
>>
>> However, not sure if that is causing shutdown problems or not.
>>
>> Regards.
>>
>>
>> "John Barnes" <> wrote in message
>> news:Oz$...
>>> The system files are always written to your %root% drive. Your boot
>>> sequence in your BIOS determines this. If you change boot sequence you
>>> will have to make copies of your system files to the new root drive and
>>> adjust your boot.ini accordingly. The shutdown problem has been
>>> reported here a couple of times as having to do with installing Avast
>>> AV, but most people here using it seem not to be having a problem, so it
>>> must be a conflict with other drivers or software.
>>>
>>>
>>> "Gary J. Dikkema" <gary_d_no_spam_@cdir.ca> wrote in message
>>> news:...
>>>> That seems to be the key...
>>>>
>>>> MSI RS480M2-IL mobo with Athlon 64 - 3000+ and 2 x 512 DDR400 ram.
>>>>
>>>> Has a Seagate 160 Gb SATA drive as well as 2 EIDE 40 Gb drives... the
>>>> Seaget is partiitoned into 2 X 20 Gb partitions with E holding a WXP
>>>> Pro SP1 and F having the WXP Pro X64 machine... Somehow thru the X64
>>>> install the install process wrote the system files (ntldr et al) on the
>>>> C drive...
>>>>
>>>> However, this is only a X64 problem.
>>>>
>>>> There seem to be no other problems...
>>>>
>>>> Anyone?
>>>>
>>>> TIA.
>>>>
>>>> Gary D
>>>>
>>>>
>>>
>>>
>>
>>
>
>

Switched to eTrust and so far so good... SHUTDOWN lockupwise...

However, why does MS think my system is insecure? With Avast I didn't have
this issue.



"M. Murcek" <> wrote in message
news:...
> Yes, I had Avast on my x64 Edition desktop, and it would sometimes lock.
> Switched to eTrust, no problem since. As John said, however, the problem
> can be more complex than just that.
>
> "Gary J. Dikkema" <gary_d_no_spam_@cdir.ca> wrote in message
> news:...
>> That seems to be the key...
>>
>> MSI RS480M2-IL mobo with Athlon 64 - 3000+ and 2 x 512 DDR400 ram.
>>
>> Has a Seagate 160 Gb SATA drive as well as 2 EIDE 40 Gb drives... the
>> Seaget is partiitoned into 2 X 20 Gb partitions with E holding a WXP Pro
>> SP1 and F having the WXP Pro X64 machine... Somehow thru the X64 install
>> the install process wrote the system files (ntldr et al) on the C
>> drive...
>>
>> However, this is only a X64 problem.
>>
>> There seem to be no other problems...
>>
>> Anyone?
>>
>> TIA.
>>
>> Gary D
>>
>>
>
>

Some av programs don't automatically "introduce" themselves to the Windows
Security Center. In my case, I turned off the Balloon Tips, so I'm not
being annoyed. You can open up Security Center, click the Recommendations
button in the Virus Protection pane, and check teh box that says "I have an
antivirus program that I will monitor myself..." That'll quiet things down.

"Gary J. Dikkema" <gary_d_no_spam_@cdir.ca> wrote in message
news:...
> Switched to eTrust and so far so good... SHUTDOWN lockupwise...
>
> However, why does MS think my system is insecure? With Avast I didn't have
> this issue.
>
>
>
> "M. Murcek" <> wrote in message
> news:...
>> Yes, I had Avast on my x64 Edition desktop, and it would sometimes lock.
>> Switched to eTrust, no problem since. As John said, however, the problem
>> can be more complex than just that.
>>
>> "Gary J. Dikkema" <gary_d_no_spam_@cdir.ca> wrote in message
>> news:...
>>> That seems to be the key...
>>>
>>> MSI RS480M2-IL mobo with Athlon 64 - 3000+ and 2 x 512 DDR400 ram.
>>>
>>> Has a Seagate 160 Gb SATA drive as well as 2 EIDE 40 Gb drives... the
>>> Seaget is partiitoned into 2 X 20 Gb partitions with E holding a WXP Pro
>>> SP1 and F having the WXP Pro X64 machine... Somehow thru the X64 install
>>> the install process wrote the system files (ntldr et al) on the C
>>> drive...
>>>
>>> However, this is only a X64 problem.
>>>
>>> There seem to be no other problems...
>>>
>>> Anyone?
>>>
>>> TIA.
>>>
>>> Gary D
>>>
>>>
>>
>>
>
>

I do find it amusing that a program Microsoft is claimed to be using
themselves never made it to the recognised AV list. Didn't they use it
during the beta?


"M. Murcek" <> wrote in message
news:...
> Some av programs don't automatically "introduce" themselves to the Windows
> Security Center. In my case, I turned off the Balloon Tips, so I'm not
> being annoyed. You can open up Security Center, click the Recommendations
> button in the Virus Protection pane, and check teh box that says "I have
> an antivirus program that I will monitor myself..." That'll quiet things
> down.
>
> "Gary J. Dikkema" <gary_d_no_spam_@cdir.ca> wrote in message
> news:...
>> Switched to eTrust and so far so good... SHUTDOWN lockupwise...
>>
>> However, why does MS think my system is insecure? With Avast I didn't
>> have this issue.
>>
>>
>>
>> "M. Murcek" <> wrote in message
>> news:...
>>> Yes, I had Avast on my x64 Edition desktop, and it would sometimes lock.
>>> Switched to eTrust, no problem since. As John said, however, the
>>> problem can be more complex than just that.
>>>
>>> "Gary J. Dikkema" <gary_d_no_spam_@cdir.ca> wrote in message
>>> news:...
>>>> That seems to be the key...
>>>>
>>>> MSI RS480M2-IL mobo with Athlon 64 - 3000+ and 2 x 512 DDR400 ram.
>>>>
>>>> Has a Seagate 160 Gb SATA drive as well as 2 EIDE 40 Gb drives... the
>>>> Seaget is partiitoned into 2 X 20 Gb partitions with E holding a WXP
>>>> Pro SP1 and F having the WXP Pro X64 machine... Somehow thru the X64
>>>> install the install process wrote the system files (ntldr et al) on the
>>>> C drive...
>>>>
>>>> However, this is only a X64 problem.
>>>>
>>>> There seem to be no other problems...
>>>>
>>>> Anyone?
>>>>
>>>> TIA.
>>>>
>>>> Gary D
>>>>
>>>>
>>>
>>>
>>
>>
>
>