Dual Boot Problems Again.

Followuing on from an earlier post and a successful answer I am having issues
again. I recently did a rebuild of the boot record on my machine as it didnt
detect the two OS's. Windows 2000 on drive C: , Windows XP 64 bit on drive
D:, The rebuild of the mbr seems to have cured it for the time being however
on Christmas day of all days i turned the machine on and and get a message
similar to the following.
"Windows 2000 could not start because of a computer disk hardware
configuration problem.
Could not read from the selected boot disk. Check boot path and disk hardware.
Please check the Windows 2000(TM) documentation about hardware disk
configuration and your hardware reference manuals for additional information.
"

The drive that the 2000 OS is on is brand new and although I cannot rule out
it being faulty but was looking for other answers before formatting the drive
again.
I have the windows 2000 boot disk can I rebuild using these.
(PS I have checked the connections they are all okay, also when bootied into
Win 64 i can access and read/write to the C: Drive with win 2000's

Many Thanks
Martin

TedF
Thu Dec 29 00:47:18 CST 2005

Can you run CHKDSK ?

"MGbassace" <MGbassace@discussions.microsoft.com> wrote in message
news:48E4A265-DC38-4033-BA9B-46D2B2C99C7E@microsoft.com...
> Followuing on from an earlier post and a successful answer I am having
> issues
> again. I recently did a rebuild of the boot record on my machine as it
> didnt
> detect the two OS's. Windows 2000 on drive C: , Windows XP 64 bit on drive
> D:, The rebuild of the mbr seems to have cured it for the time being
> however
> on Christmas day of all days i turned the machine on and and get a
> message
> similar to the following.
> "Windows 2000 could not start because of a computer disk hardware
> configuration problem.
> Could not read from the selected boot disk. Check boot path and disk
> hardware.
> Please check the Windows 2000(TM) documentation about hardware disk
> configuration and your hardware reference manuals for additional
> information.
> "
>
> The drive that the 2000 OS is on is brand new and although I cannot rule
> out
> it being faulty but was looking for other answers before formatting the
> drive
> again.
> I have the windows 2000 boot disk can I rebuild using these.
> (PS I have checked the connections they are all okay, also when bootied
> into
> Win 64 i can access and read/write to the C: Drive with win 2000's
>
> Many Thanks
> Martin
>

MGbassace
Thu Dec 29 02:50:02 CST 2005

TedF, Thanks for the advise, I cannot get it to do anything, I resorted to
installing a fresh copy on this drive from the boot disc's, The only problem
being now is that maybe i should have disconnected the other drive with win
64 on as now it wont boot into that, usual cannot locate file. not sure how
to resolve this without re-installing win 64.
BTW on a lighter note does anyone know how to extact the keycode from win
2003 server, I have a genuine copy but unfortunatley when server went down
and was beyond repair skipped it along with the COA and keycode, DOH

"TedF" wrote:

> Can you run CHKDSK ?
>
> "MGbassace" <MGbassace@discussions.microsoft.com> wrote in message
> news:48E4A265-DC38-4033-BA9B-46D2B2C99C7E@microsoft.com...
> > Followuing on from an earlier post and a successful answer I am having
> > issues
> > again. I recently did a rebuild of the boot record on my machine as it
> > didnt
> > detect the two OS's. Windows 2000 on drive C: , Windows XP 64 bit on drive
> > D:, The rebuild of the mbr seems to have cured it for the time being
> > however
> > on Christmas day of all days i turned the machine on and and get a
> > message
> > similar to the following.
> > "Windows 2000 could not start because of a computer disk hardware
> > configuration problem.
> > Could not read from the selected boot disk. Check boot path and disk
> > hardware.
> > Please check the Windows 2000(TM) documentation about hardware disk
> > configuration and your hardware reference manuals for additional
> > information.
> > "
> >
> > The drive that the 2000 OS is on is brand new and although I cannot rule
> > out
> > it being faulty but was looking for other answers before formatting the
> > drive
> > again.
> > I have the windows 2000 boot disk can I rebuild using these.
> > (PS I have checked the connections they are all okay, also when bootied
> > into
> > Win 64 i can access and read/write to the C: Drive with win 2000's
> >
> > Many Thanks
> > Martin
> >
>
>
>

Tony
Thu Dec 29 03:06:54 CST 2005

Try and check the Data, as well as the Power cables, that is attached to
that disk, make sure that they have good contact. Ideally you might even try
and find an exchange for them, or - since you have two disks, try and swap
them. I read that earlier post, am of the opinion that this is unusual to
happen in such rapid succesion. Are you overclocking? Good temps in that
box? Flakey power? - did you install anything, just prior to this happening?
Also, do note that most Hard Drive manufacturers recommend that you attach
each HD using all four screws, to secure good and stable 'ground'.

Good luck! - Tony. . .


"MGbassace" <MGbassace@discussions.microsoft.com> wrote in message
news:48E4A265-DC38-4033-BA9B-46D2B2C99C7E@microsoft.com...
> Followuing on from an earlier post and a successful answer I am having
> issues
> again. I recently did a rebuild of the boot record on my machine as it
> didnt
> detect the two OS's. Windows 2000 on drive C: , Windows XP 64 bit on drive
> D:, The rebuild of the mbr seems to have cured it for the time being
> however
> on Christmas day of all days i turned the machine on and and get a
> message
> similar to the following.
> "Windows 2000 could not start because of a computer disk hardware
> configuration problem.
> Could not read from the selected boot disk. Check boot path and disk
> hardware.
> Please check the Windows 2000(TM) documentation about hardware disk
> configuration and your hardware reference manuals for additional
> information.
> "
>
> The drive that the 2000 OS is on is brand new and although I cannot rule
> out
> it being faulty but was looking for other answers before formatting the
> drive
> again.
> I have the windows 2000 boot disk can I rebuild using these.
> (PS I have checked the connections they are all okay, also when bootied
> into
> Win 64 i can access and read/write to the C: Drive with win 2000's
>
> Many Thanks
> Martin
>

Tony
Thu Dec 29 03:11:51 CST 2005

Shouldn't you just follow John's recipy for the earlier problem, again?


Tony. . .


"MGbassace" <MGbassace@discussions.microsoft.com> wrote in message
news:1E817A45-940A-4B35-BD83-5950D30167D1@microsoft.com...
> TedF, Thanks for the advise, I cannot get it to do anything, I resorted to
> installing a fresh copy on this drive from the boot disc's, The only
> problem
> being now is that maybe i should have disconnected the other drive with
> win
> 64 on as now it wont boot into that, usual cannot locate file. not sure
> how
> to resolve this without re-installing win 64.
> BTW on a lighter note does anyone know how to extact the keycode from win
> 2003 server, I have a genuine copy but unfortunatley when server went down
> and was beyond repair skipped it along with the COA and keycode, DOH
>
> "TedF" wrote:
>
>> Can you run CHKDSK ?
>>
>> "MGbassace" <MGbassace@discussions.microsoft.com> wrote in message
>> news:48E4A265-DC38-4033-BA9B-46D2B2C99C7E@microsoft.com...
>> > Followuing on from an earlier post and a successful answer I am having
>> > issues
>> > again. I recently did a rebuild of the boot record on my machine as it
>> > didnt
>> > detect the two OS's. Windows 2000 on drive C: , Windows XP 64 bit on
>> > drive
>> > D:, The rebuild of the mbr seems to have cured it for the time being
>> > however
>> > on Christmas day of all days i turned the machine on and and get a
>> > message
>> > similar to the following.
>> > "Windows 2000 could not start because of a computer disk hardware
>> > configuration problem.
>> > Could not read from the selected boot disk. Check boot path and disk
>> > hardware.
>> > Please check the Windows 2000(TM) documentation about hardware disk
>> > configuration and your hardware reference manuals for additional
>> > information.
>> > "
>> >
>> > The drive that the 2000 OS is on is brand new and although I cannot
>> > rule
>> > out
>> > it being faulty but was looking for other answers before formatting the
>> > drive
>> > again.
>> > I have the windows 2000 boot disk can I rebuild using these.
>> > (PS I have checked the connections they are all okay, also when bootied
>> > into
>> > Win 64 i can access and read/write to the C: Drive with win 2000's
>> >
>> > Many Thanks
>> > Martin
>> >
>>
>>
>>

MGbassace
Thu Dec 29 03:35:03 CST 2005

Temp, Power supply etc all okay, Installed in server unit, air flow couldnt
be better, the only thing that you may have a point with is the mounting of
the drive. I will see how it goes, I did install anything just before it went
down, Last thing i did was burn a DVD of my band. But no worries guys, looks
like I am heading in the right direction on getting it running again, I guess
i was looking for an easy fix.

"Tony Sperling" wrote:

> Try and check the Data, as well as the Power cables, that is attached to
> that disk, make sure that they have good contact. Ideally you might even try
> and find an exchange for them, or - since you have two disks, try and swap
> them. I read that earlier post, am of the opinion that this is unusual to
> happen in such rapid succesion. Are you overclocking? Good temps in that
> box? Flakey power? - did you install anything, just prior to this happening?
> Also, do note that most Hard Drive manufacturers recommend that you attach
> each HD using all four screws, to secure good and stable 'ground'.
>
> Good luck! - Tony. . .
>
>
> "MGbassace" <MGbassace@discussions.microsoft.com> wrote in message
> news:48E4A265-DC38-4033-BA9B-46D2B2C99C7E@microsoft.com...
> > Followuing on from an earlier post and a successful answer I am having
> > issues
> > again. I recently did a rebuild of the boot record on my machine as it
> > didnt
> > detect the two OS's. Windows 2000 on drive C: , Windows XP 64 bit on drive
> > D:, The rebuild of the mbr seems to have cured it for the time being
> > however
> > on Christmas day of all days i turned the machine on and and get a
> > message
> > similar to the following.
> > "Windows 2000 could not start because of a computer disk hardware
> > configuration problem.
> > Could not read from the selected boot disk. Check boot path and disk
> > hardware.
> > Please check the Windows 2000(TM) documentation about hardware disk
> > configuration and your hardware reference manuals for additional
> > information.
> > "
> >
> > The drive that the 2000 OS is on is brand new and although I cannot rule
> > out
> > it being faulty but was looking for other answers before formatting the
> > drive
> > again.
> > I have the windows 2000 boot disk can I rebuild using these.
> > (PS I have checked the connections they are all okay, also when bootied
> > into
> > Win 64 i can access and read/write to the C: Drive with win 2000's
> >
> > Many Thanks
> > Martin
> >
>
>
>

me
Thu Dec 29 14:55:19 CST 2005

On Thu, 29 Dec 2005 00:50:02 -0800, MGbassace
<MGbassace@discussions.microsoft.com> wrote:

>TedF, Thanks for the advise, I cannot get it to do anything, I resorted to
>installing a fresh copy on this drive from the boot disc's, The only problem
>being now is that maybe i should have disconnected the other drive with win
>64 on as now it wont boot into that, usual cannot locate file. not sure how
>to resolve this without re-installing win 64.
>BTW on a lighter note does anyone know how to extact the keycode from win
>2003 server, I have a genuine copy but unfortunatley when server went down
>and was beyond repair skipped it along with the COA and keycode, DOH
>
>"TedF" wrote:
>
>> Can you run CHKDSK ?
>>
>> "MGbassace" <MGbassace@discussions.microsoft.com> wrote in message
>> news:48E4A265-DC38-4033-BA9B-46D2B2C99C7E@microsoft.com...
>> > Followuing on from an earlier post and a successful answer I am having
>> > issues
>> > again. I recently did a rebuild of the boot record on my machine as it
>> > didnt
>> > detect the two OS's. Windows 2000 on drive C: , Windows XP 64 bit on drive
>> > D:, The rebuild of the mbr seems to have cured it for the time being
>> > however
>> > on Christmas day of all days i turned the machine on and and get a
>> > message
>> > similar to the following.
>> > "Windows 2000 could not start because of a computer disk hardware
>> > configuration problem.
>> > Could not read from the selected boot disk. Check boot path and disk
>> > hardware.
>> > Please check the Windows 2000(TM) documentation about hardware disk
>> > configuration and your hardware reference manuals for additional
>> > information.
>> > "
>> >
>> > The drive that the 2000 OS is on is brand new and although I cannot rule
>> > out
>> > it being faulty but was looking for other answers before formatting the
>> > drive
>> > again.
>> > I have the windows 2000 boot disk can I rebuild using these.
>> > (PS I have checked the connections they are all okay, also when bootied
>> > into
>> > Win 64 i can access and read/write to the C: Drive with win 2000's
>> >
>> > Many Thanks
>> > Martin
>> >
>>
>>
>>
This is for NT, but the same holds true for 2000.
http://support.microsoft.com/default.aspx?scid=kb;en-us;315233

TedF
Thu Dec 29 21:20:58 CST 2005

I dual boot XP 32 and 64 Bit, but I use mobile rack instead.
Remove XP 32 drive and insert XP 64 drive when I need to use it.
Saves lots of dual boot headache, plus I have a slave
drive that I use to share files between the two OCs.


"MGbassace" <MGbassace@discussions.microsoft.com> wrote in message
news:48E4A265-DC38-4033-BA9B-46D2B2C99C7E@microsoft.com...
> Followuing on from an earlier post and a successful answer I am having
> issues
> again. I recently did a rebuild of the boot record on my machine as it
> didnt
> detect the two OS's. Windows 2000 on drive C: , Windows XP 64 bit on drive
> D:, The rebuild of the mbr seems to have cured it for the time being
> however
> on Christmas day of all days i turned the machine on and and get a
> message
> similar to the following.
> "Windows 2000 could not start because of a computer disk hardware
> configuration problem.
> Could not read from the selected boot disk. Check boot path and disk
> hardware.
> Please check the Windows 2000(TM) documentation about hardware disk
> configuration and your hardware reference manuals for additional
> information.
> "
>
> The drive that the 2000 OS is on is brand new and although I cannot rule
> out
> it being faulty but was looking for other answers before formatting the
> drive
> again.
> I have the windows 2000 boot disk can I rebuild using these.
> (PS I have checked the connections they are all okay, also when bootied
> into
> Win 64 i can access and read/write to the C: Drive with win 2000's
>
> Many Thanks
> Martin
>

MGbassace
Fri Dec 30 03:46:02 CST 2005

I was looking at Ebay yesterday for hard drive caddies, Think that might be
worth looking into, for the sake of £8.00(gb) might be the best solution,
least then as you suggest I can swop drives. I have the system running again
successfully now, Had to re-install win 64 but it was not a great loss as
nothing much saved on system yet. My main concern really is what caused it in
the first place and how to eleviate the possibilty of a repeat.

"TedF" wrote:

> I dual boot XP 32 and 64 Bit, but I use mobile rack instead.
> Remove XP 32 drive and insert XP 64 drive when I need to use it.
> Saves lots of dual boot headache, plus I have a slave
> drive that I use to share files between the two OCs.
>
>
> "MGbassace" <MGbassace@discussions.microsoft.com> wrote in message
> news:48E4A265-DC38-4033-BA9B-46D2B2C99C7E@microsoft.com...
> > Followuing on from an earlier post and a successful answer I am having
> > issues
> > again. I recently did a rebuild of the boot record on my machine as it
> > didnt
> > detect the two OS's. Windows 2000 on drive C: , Windows XP 64 bit on drive
> > D:, The rebuild of the mbr seems to have cured it for the time being
> > however
> > on Christmas day of all days i turned the machine on and and get a
> > message
> > similar to the following.
> > "Windows 2000 could not start because of a computer disk hardware
> > configuration problem.
> > Could not read from the selected boot disk. Check boot path and disk
> > hardware.
> > Please check the Windows 2000(TM) documentation about hardware disk
> > configuration and your hardware reference manuals for additional
> > information.
> > "
> >
> > The drive that the 2000 OS is on is brand new and although I cannot rule
> > out
> > it being faulty but was looking for other answers before formatting the
> > drive
> > again.
> > I have the windows 2000 boot disk can I rebuild using these.
> > (PS I have checked the connections they are all okay, also when bootied
> > into
> > Win 64 i can access and read/write to the C: Drive with win 2000's
> >
> > Many Thanks
> > Martin
> >
>
>
>

TedF
Fri Dec 30 11:26:38 CST 2005

You don't need to go to eBay, they are pretty cheap new
Use Lian-Li mobile racks
http://www.xpcgear.com/lianlirh10.html

Shop around, there are some with single or dual fans,
stay away from Kingwin.
Never had problems with Lian-Li, did have problems
with IDE Kingwin.



"MGbassace" <MGbassace@discussions.microsoft.com> wrote in message
news:3E25B7AF-12FE-448B-8B42-75EADC17999C@microsoft.com...
>I was looking at Ebay yesterday for hard drive caddies, Think that might be
> worth looking into, for the sake of £8.00(gb) might be the best solution,
> least then as you suggest I can swop drives. I have the system running
> again
> successfully now, Had to re-install win 64 but it was not a great loss as
> nothing much saved on system yet. My main concern really is what caused it
> in
> the first place and how to eleviate the possibilty of a repeat.
>
> "TedF" wrote:
>
>> I dual boot XP 32 and 64 Bit, but I use mobile rack instead.
>> Remove XP 32 drive and insert XP 64 drive when I need to use it.
>> Saves lots of dual boot headache, plus I have a slave
>> drive that I use to share files between the two OCs.
>>
>>
>> "MGbassace" <MGbassace@discussions.microsoft.com> wrote in message
>> news:48E4A265-DC38-4033-BA9B-46D2B2C99C7E@microsoft.com...
>> > Followuing on from an earlier post and a successful answer I am having
>> > issues
>> > again. I recently did a rebuild of the boot record on my machine as it
>> > didnt
>> > detect the two OS's. Windows 2000 on drive C: , Windows XP 64 bit on
>> > drive
>> > D:, The rebuild of the mbr seems to have cured it for the time being
>> > however
>> > on Christmas day of all days i turned the machine on and and get a
>> > message
>> > similar to the following.
>> > "Windows 2000 could not start because of a computer disk hardware
>> > configuration problem.
>> > Could not read from the selected boot disk. Check boot path and disk
>> > hardware.
>> > Please check the Windows 2000(TM) documentation about hardware disk
>> > configuration and your hardware reference manuals for additional
>> > information.
>> > "
>> >
>> > The drive that the 2000 OS is on is brand new and although I cannot
>> > rule
>> > out
>> > it being faulty but was looking for other answers before formatting the
>> > drive
>> > again.
>> > I have the windows 2000 boot disk can I rebuild using these.
>> > (PS I have checked the connections they are all okay, also when bootied
>> > into
>> > Win 64 i can access and read/write to the C: Drive with win 2000's
>> >
>> > Many Thanks
>> > Martin
>> >
>>
>>
>>

Techead
Fri Dec 30 16:16:03 CST 2005

Tony:

I'm thinking you know the answer to this:

My XP 64-bit is hanging (keyboard / mouse froze) after loading my "start-up
apps"; I think Avast missed one of those infected .wmf files! I tried usig
the CD's re-installation feature, and it too hangs during the "loading
devices" portion. Since I don't have a 2nd drive, nor 2nd partition, would it
be "safe" to install a 2nd copy of XP 64-bit in a C:\WINNT folder??? Then I
could install the updated patches from MS and run Avast's upgraded version
(and perhaps do a few online scans from others).

What do you think?

Techead

"Tony Sperling" wrote:

> Shouldn't you just follow John's recipy for the earlier problem, again?
>
>
> Tony. . .
>
>
> "MGbassace" <MGbassace@discussions.microsoft.com> wrote in message
> news:1E817A45-940A-4B35-BD83-5950D30167D1@microsoft.com...
> > TedF, Thanks for the advise, I cannot get it to do anything, I resorted to
> > installing a fresh copy on this drive from the boot disc's, The only
> > problem
> > being now is that maybe i should have disconnected the other drive with
> > win
> > 64 on as now it wont boot into that, usual cannot locate file. not sure
> > how
> > to resolve this without re-installing win 64.
> > BTW on a lighter note does anyone know how to extact the keycode from win
> > 2003 server, I have a genuine copy but unfortunatley when server went down
> > and was beyond repair skipped it along with the COA and keycode, DOH
> >
> > "TedF" wrote:
> >
> >> Can you run CHKDSK ?
> >>
> >> "MGbassace" <MGbassace@discussions.microsoft.com> wrote in message
> >> news:48E4A265-DC38-4033-BA9B-46D2B2C99C7E@microsoft.com...
> >> > Followuing on from an earlier post and a successful answer I am having
> >> > issues
> >> > again. I recently did a rebuild of the boot record on my machine as it
> >> > didnt
> >> > detect the two OS's. Windows 2000 on drive C: , Windows XP 64 bit on
> >> > drive
> >> > D:, The rebuild of the mbr seems to have cured it for the time being
> >> > however
> >> > on Christmas day of all days i turned the machine on and and get a
> >> > message
> >> > similar to the following.
> >> > "Windows 2000 could not start because of a computer disk hardware
> >> > configuration problem.
> >> > Could not read from the selected boot disk. Check boot path and disk
> >> > hardware.
> >> > Please check the Windows 2000(TM) documentation about hardware disk
> >> > configuration and your hardware reference manuals for additional
> >> > information.
> >> > "
> >> >
> >> > The drive that the 2000 OS is on is brand new and although I cannot
> >> > rule
> >> > out
> >> > it being faulty but was looking for other answers before formatting the
> >> > drive
> >> > again.
> >> > I have the windows 2000 boot disk can I rebuild using these.
> >> > (PS I have checked the connections they are all okay, also when bootied
> >> > into
> >> > Win 64 i can access and read/write to the C: Drive with win 2000's
> >> >
> >> > Many Thanks
> >> > Martin
> >> >
> >>
> >>
> >>
>
>
>

Tony
Fri Dec 30 19:11:38 CST 2005

When you say "the CD's re-installation feature", is that the 'Repair
Install'? If that fails, how would you get to do that 'otherly' installation
you mention?

Ahh, I will ask you to hang on for a bit, it's late and I will have to think
it over. There was a time when it would have been alright, but that was
before MS came up with the Registry. Right now, I think you might be in for
some trouble if you do. And, overall - if you are running Avast, I would not
start off thinking about 'infection' - heck, that thing is updating more
often than I change my socks! You can litterally have several updates before
you even hear about an issue in the press. Give it a rest, see what it says
in the morning, and if the disk is IDE, I'd begin by rocking the flat cable
gently, swap it if you have a spare. They are surprisingly tuff, but they
are one of the more frequent sources of contact problems in a box, I would
say. (oh, and take off your wrist-watch!)

Also, check that your BIOS setup is intact, and reset it to it's safe
setting if possible. And try to think of what the last piece of action you
had the machine perform, was.


Tony. . .


"Techead" <Techead@discussions.microsoft.com> wrote in message
news:50D15ED2-EB79-4024-BC60-6C590E6299B0@microsoft.com...
> Tony:
>
> I'm thinking you know the answer to this:
>
> My XP 64-bit is hanging (keyboard / mouse froze) after loading my
> "start-up
> apps"; I think Avast missed one of those infected .wmf files! I tried usig
> the CD's re-installation feature, and it too hangs during the "loading
> devices" portion. Since I don't have a 2nd drive, nor 2nd partition, would
> it
> be "safe" to install a 2nd copy of XP 64-bit in a C:\WINNT folder??? Then
> I
> could install the updated patches from MS and run Avast's upgraded version
> (and perhaps do a few online scans from others).
>
> What do you think?
>
> Techead
>
> "Tony Sperling" wrote:
>
>> Shouldn't you just follow John's recipy for the earlier problem, again?
>>
>>
>> Tony. . .
>>
>>
>> "MGbassace" <MGbassace@discussions.microsoft.com> wrote in message
>> news:1E817A45-940A-4B35-BD83-5950D30167D1@microsoft.com...
>> > TedF, Thanks for the advise, I cannot get it to do anything, I resorted
>> > to
>> > installing a fresh copy on this drive from the boot disc's, The only
>> > problem
>> > being now is that maybe i should have disconnected the other drive with
>> > win
>> > 64 on as now it wont boot into that, usual cannot locate file. not sure
>> > how
>> > to resolve this without re-installing win 64.
>> > BTW on a lighter note does anyone know how to extact the keycode from
>> > win
>> > 2003 server, I have a genuine copy but unfortunatley when server went
>> > down
>> > and was beyond repair skipped it along with the COA and keycode, DOH
>> >
>> > "TedF" wrote:
>> >
>> >> Can you run CHKDSK ?
>> >>
>> >> "MGbassace" <MGbassace@discussions.microsoft.com> wrote in message
>> >> news:48E4A265-DC38-4033-BA9B-46D2B2C99C7E@microsoft.com...
>> >> > Followuing on from an earlier post and a successful answer I am
>> >> > having
>> >> > issues
>> >> > again. I recently did a rebuild of the boot record on my machine as
>> >> > it
>> >> > didnt
>> >> > detect the two OS's. Windows 2000 on drive C: , Windows XP 64 bit on
>> >> > drive
>> >> > D:, The rebuild of the mbr seems to have cured it for the time being
>> >> > however
>> >> > on Christmas day of all days i turned the machine on and and get a
>> >> > message
>> >> > similar to the following.
>> >> > "Windows 2000 could not start because of a computer disk hardware
>> >> > configuration problem.
>> >> > Could not read from the selected boot disk. Check boot path and disk
>> >> > hardware.
>> >> > Please check the Windows 2000(TM) documentation about hardware disk
>> >> > configuration and your hardware reference manuals for additional
>> >> > information.
>> >> > "
>> >> >
>> >> > The drive that the 2000 OS is on is brand new and although I cannot
>> >> > rule
>> >> > out
>> >> > it being faulty but was looking for other answers before formatting
>> >> > the
>> >> > drive
>> >> > again.
>> >> > I have the windows 2000 boot disk can I rebuild using these.
>> >> > (PS I have checked the connections they are all okay, also when
>> >> > bootied
>> >> > into
>> >> > Win 64 i can access and read/write to the C: Drive with win 2000's
>> >> >
>> >> > Many Thanks
>> >> > Martin
>> >> >
>> >>
>> >>
>> >>
>>
>>
>>

Techead
Fri Dec 30 20:45:02 CST 2005

See in-line reply:

"Tony Sperling" wrote:

> When you say "the CD's re-installation feature", is that the 'Repair
> Install'?

Yes; but not the recovery console; Windows detected an installation already
on the drive; Windows can attempt to fix this install...............

If that fails, how would you get to do that 'other' installation
> you mention?

I'm thinking if the first installation has infected files, then when the
re-installation tries to load the drivers that are currently configured in
that install's version, an infected driver can cause the installation to
crash. Whereas a fresh install can load the basic drivers (LAN, Video,
wireless / mouse) from my GigaByte-CD. That's all I need to get the PC
running again.

I'm also downloading "Linux Defender" now (637 Mb) as an ISO. I'll create a
bootable-CD and scan my drive before I try the 2nd install.

>
> Ahh, I will ask you to hang on for a bit, it's late and I will have to think
> it over. There was a time when it would have been alright, but that was
> before MS came up with the Registry. Right now, I think you might be in for
> some trouble if you do. And, overall - if you are running Avast, I would not
> start off thinking about 'infection' - heck, that thing is updating more
> often than I change my socks! You can litterally have several updates before
> you even hear about an issue in the press. Give it a rest, see what it says
> in the morning, and if the disk is IDE, I'd begin by rocking the flat cable
> gently, swap it if you have a spare. They are surprisingly tuff, but they
> are one of the more frequent sources of contact problems in a box, I would
> say. (oh, and take off your wrist-watch!)

My boot-drive is a Maxtor 300 Gb SATA (non-RAID) mode. I haven't opened the
case in a while, so that shouldn't be the cause. I've ran CHKDSK /R a few
times; no affect.

>
> Also, check that your BIOS setup is intact, and reset it to it's safe
> setting if possible.

I did that already; no luck.

And try to think of what the last piece of action you had the machine
perform, was.

If Linux Defender doesn't find a culprit, and replacing my 1 Gb RAM module
on Sat. (12/31/05) doesn't resolve the issue; then Ill be forced to install
that 2nd instance of Win-XP 64-bit in C:\WINNT folder and boot from there.
Perhaps then I can get the system restore from the first instance to resolve
the issue?

Your thoughts?
>
>
> Tony. . .
>
>
> "Techead" <Techead@discussions.microsoft.com> wrote in message
> news:50D15ED2-EB79-4024-BC60-6C590E6299B0@microsoft.com...
> > Tony:
> >
> > I'm thinking you know the answer to this:
> >
> > My XP 64-bit is hanging (keyboard / mouse froze) after loading my
> > "start-up
> > apps"; I think Avast missed one of those infected .wmf files! I tried usig
> > the CD's re-installation feature, and it too hangs during the "loading
> > devices" portion. Since I don't have a 2nd drive, nor 2nd partition, would
> > it
> > be "safe" to install a 2nd copy of XP 64-bit in a C:\WINNT folder??? Then
> > I
> > could install the updated patches from MS and run Avast's upgraded version
> > (and perhaps do a few online scans from others).
> >
> > What do you think?
> >
> > Techead
> >
> > "Tony Sperling" wrote:
> >
> >> Shouldn't you just follow John's recipy for the earlier problem, again?
> >>
> >>
> >> Tony. . .
> >>
> >>
> >> "MGbassace" <MGbassace@discussions.microsoft.com> wrote in message
> >> news:1E817A45-940A-4B35-BD83-5950D30167D1@microsoft.com...
> >> > TedF, Thanks for the advise, I cannot get it to do anything, I resorted
> >> > to
> >> > installing a fresh copy on this drive from the boot disc's, The only
> >> > problem
> >> > being now is that maybe i should have disconnected the other drive with
> >> > win
> >> > 64 on as now it wont boot into that, usual cannot locate file. not sure
> >> > how
> >> > to resolve this without re-installing win 64.
> >> > BTW on a lighter note does anyone know how to extact the keycode from
> >> > win
> >> > 2003 server, I have a genuine copy but unfortunatley when server went
> >> > down
> >> > and was beyond repair skipped it along with the COA and keycode, DOH
> >> >
> >> > "TedF" wrote:
> >> >
> >> >> Can you run CHKDSK ?
> >> >>
> >> >> "MGbassace" <MGbassace@discussions.microsoft.com> wrote in message
> >> >> news:48E4A265-DC38-4033-BA9B-46D2B2C99C7E@microsoft.com...
> >> >> > Followuing on from an earlier post and a successful answer I am
> >> >> > having
> >> >> > issues
> >> >> > again. I recently did a rebuild of the boot record on my machine as
> >> >> > it
> >> >> > didnt
> >> >> > detect the two OS's. Windows 2000 on drive C: , Windows XP 64 bit on
> >> >> > drive
> >> >> > D:, The rebuild of the mbr seems to have cured it for the time being
> >> >> > however
> >> >> > on Christmas day of all days i turned the machine on and and get a
> >> >> > message
> >> >> > similar to the following.
> >> >> > "Windows 2000 could not start because of a computer disk hardware
> >> >> > configuration problem.
> >> >> > Could not read from the selected boot disk. Check boot path and disk
> >> >> > hardware.
> >> >> > Please check the Windows 2000(TM) documentation about hardware disk
> >> >> > configuration and your hardware reference manuals for additional
> >> >> > information.
> >> >> > "
> >> >> >
> >> >> > The drive that the 2000 OS is on is brand new and although I cannot
> >> >> > rule
> >> >> > out
> >> >> > it being faulty but was looking for other answers before formatting
> >> >> > the
> >> >> > drive
> >> >> > again.
> >> >> > I have the windows 2000 boot disk can I rebuild using these.
> >> >> > (PS I have checked the connections they are all okay, also when
> >> >> > bootied
> >> >> > into
> >> >> > Win 64 i can access and read/write to the C: Drive with win 2000's
> >> >> >
> >> >> > Many Thanks
> >> >> > Martin
> >> >> >
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>
>

Tony
Sat Dec 31 04:19:46 CST 2005

Well, last night, I did remember having an exchange with you on 'some'
issue, I've now checked that, and personally I am at least happy with not
having given you any wildy conflicting advise. I still feel that your
problem may be much more 'trivial' than you imagine - it's like, if you are
out driving and your Cadillac suddenly stops, you shouldn't start off by
calling a rescue service and ask them to install a new engine. You
definitely need to look at the 'cheeper' posibillities first, and by
cheeper, I mean: regarding to the use of time and resources, as well as the
prize factor. Such is the philosophy of the search for failures. Think about
the Cadillac analogy, if it's the fuel pump or generator - a new engine
would indeed fix the problem, the Garage would be very happy, and you would
be non-the-wiser.

Having a look inside the box, I regard as being the first-aid-kit of all
computer failure recovery. Not having opened the case for 'a while', is by
no means any indication of nothing being wrong in there, rather the
opposite, perhaps. One of the more frequent causes to problems, is indeed of
an electrical nature, I didn't ask you to check the connections inside for
the faint possibillity that you (or someone else) hadn't been doing it
properly from the begining - the simple fact is that vibration and
temperature related issues can make good contact turn into
not-so-good-contact, and when that happens the contact areas start oxidising
and then it is only a matter of time when you begin to experience wildly
random behavior, typically of the sort that doesn't give you any lead. And
note - that this description is relating to a situation where everything is
'normal' inside that box. But it could be a Hardware failure. There is a
saying that relates to electronics: "If it survives the first year, you will
never get rid of it" - this is because, maybe 90% of all Hardware failures
happen in the first year (this is not the same as saying 90% of all new
computers have a failure in the first year) - most of the rest happen from
misshandling.

The lacking quality of the standard kind of Power Supply you find in a Super
Market kind of machine, is another frequent contributor to this kind of
behavior. Using the 'Wattage Rating' as a quality measure, is pure
ignorance, and many 'HomeBuilders' too are eager to save a 'buck' and follow
the standard rating as guideline. So, in order for anybody to be of any
assistance to you, you really should try and help us gather some usefull
information.

The Linux disk, I think, is a great idea. While you are at it, I would
suggest you use that to salvage any data you love on that disk before
following that 'other' idea. Yes, try it if you are desperate! And if you
have to start all over, use that opportunity to set up a dual-boot system.
Regarding the Repair Install - if you boot the CD and ask it to make an
installation, it will detect the presence of another Windows installation,
and you will then be presented with an option to make a Repair Installation
on that partition, this is not the same as Recovery Console, this is just
after the actual installation begins.

Tony. . .

(And a happy NewYear, to you! (Barry, was it?))


"Techead" <Techead@discussions.microsoft.com> wrote in message
news:2BD17F80-70A8-4E07-B179-577CB0731605@microsoft.com...
> See in-line reply:
>
> "Tony Sperling" wrote:
>
>> When you say "the CD's re-installation feature", is that the 'Repair
>> Install'?
>
> Yes; but not the recovery console; Windows detected an installation
> already
> on the drive; Windows can attempt to fix this install...............
>
> If that fails, how would you get to do that 'other' installation
>> you mention?
>
> I'm thinking if the first installation has infected files, then when the
> re-installation tries to load the drivers that are currently configured in
> that install's version, an infected driver can cause the installation to
> crash. Whereas a fresh install can load the basic drivers (LAN, Video,
> wireless / mouse) from my GigaByte-CD. That's all I need to get the PC
> running again.
>
> I'm also downloading "Linux Defender" now (637 Mb) as an ISO. I'll create
> a
> bootable-CD and scan my drive before I try the 2nd install.
>
>>
>> Ahh, I will ask you to hang on for a bit, it's late and I will have to
>> think
>> it over. There was a time when it would have been alright, but that was
>> before MS came up with the Registry. Right now, I think you might be in
>> for
>> some trouble if you do. And, overall - if you are running Avast, I would
>> not
>> start off thinking about 'infection' - heck, that thing is updating more
>> often than I change my socks! You can litterally have several updates
>> before
>> you even hear about an issue in the press. Give it a rest, see what it
>> says
>> in the morning, and if the disk is IDE, I'd begin by rocking the flat
>> cable
>> gently, swap it if you have a spare. They are surprisingly tuff, but they
>> are one of the more frequent sources of contact problems in a box, I
>> would
>> say. (oh, and take off your wrist-watch!)
>
> My boot-drive is a Maxtor 300 Gb SATA (non-RAID) mode. I haven't opened
> the
> case in a while, so that shouldn't be the cause. I've ran CHKDSK /R a few
> times; no affect.
>
>>
>> Also, check that your BIOS setup is intact, and reset it to it's safe
>> setting if possible.
>
> I did that already; no luck.
>
> And try to think of what the last piece of action you had the machine
> perform, was.
>
> If Linux Defender doesn't find a culprit, and replacing my 1 Gb RAM module
> on Sat. (12/31/05) doesn't resolve the issue; then Ill be forced to
> install
> that 2nd instance of Win-XP 64-bit in C:\WINNT folder and boot from there.
> Perhaps then I can get the system restore from the first instance to
> resolve
> the issue?
>
> Your thoughts?
>>
>>
>> Tony. . .
>>
>>
>> "Techead" <Techead@discussions.microsoft.com> wrote in message
>> news:50D15ED2-EB79-4024-BC60-6C590E6299B0@microsoft.com...
>> > Tony:
>> >
>> > I'm thinking you know the answer to this:
>> >
>> > My XP 64-bit is hanging (keyboard / mouse froze) after loading my
>> > "start-up
>> > apps"; I think Avast missed one of those infected .wmf files! I tried
>> > usig
>> > the CD's re-installation feature, and it too hangs during the "loading
>> > devices" portion. Since I don't have a 2nd drive, nor 2nd partition,
>> > would
>> > it
>> > be "safe" to install a 2nd copy of XP 64-bit in a C:\WINNT folder???
>> > Then
>> > I
>> > could install the updated patches from MS and run Avast's upgraded
>> > version
>> > (and perhaps do a few online scans from others).
>> >
>> > What do you think?
>> >
>> > Techead
>> >
>> > "Tony Sperling" wrote:
>> >
>> >> Shouldn't you just follow John's recipy for the earlier problem,
>> >> again?
>> >>
>> >>
>> >> Tony. . .
>> >>
>> >>
>> >> "MGbassace" <MGbassace@discussions.microsoft.com> wrote in message
>> >> news:1E817A45-940A-4B35-BD83-5950D30167D1@microsoft.com...
>> >> > TedF, Thanks for the advise, I cannot get it to do anything, I
>> >> > resorted
>> >> > to
>> >> > installing a fresh copy on this drive from the boot disc's, The only
>> >> > problem
>> >> > being now is that maybe i should have disconnected the other drive
>> >> > with
>> >> > win
>> >> > 64 on as now it wont boot into that, usual cannot locate file. not
>> >> > sure
>> >> > how
>> >> > to resolve this without re-installing win 64.
>> >> > BTW on a lighter note does anyone know how to extact the keycode
>> >> > from
>> >> > win
>> >> > 2003 server, I have a genuine copy but unfortunatley when server
>> >> > went
>> >> > down
>> >> > and was beyond repair skipped it along with the COA and keycode, DOH
>> >> >
>> >> > "TedF" wrote:
>> >> >
>> >> >> Can you run CHKDSK ?
>> >> >>
>> >> >> "MGbassace" <MGbassace@discussions.microsoft.com> wrote in message
>> >> >> news:48E4A265-DC38-4033-BA9B-46D2B2C99C7E@microsoft.com...
>> >> >> > Followuing on from an earlier post and a successful answer I am
>> >> >> > having
>> >> >> > issues
>> >> >> > again. I recently did a rebuild of the boot record on my machine
>> >> >> > as
>> >> >> > it
>> >> >> > didnt
>> >> >> > detect the two OS's. Windows 2000 on drive C: , Windows XP 64 bit
>> >> >> > on
>> >> >> > drive
>> >> >> > D:, The rebuild of the mbr seems to have cured it for the time
>> >> >> > being
>> >> >> > however
>> >> >> > on Christmas day of all days i turned the machine on and and get
>> >> >> > a
>> >> >> > message
>> >> >> > similar to the following.
>> >> >> > "Windows 2000 could not start because of a computer disk hardware
>> >> >> > configuration problem.
>> >> >> > Could not read from the selected boot disk. Check boot path and
>> >> >> > disk
>> >> >> > hardware.
>> >> >> > Please check the Windows 2000(TM) documentation about hardware
>> >> >> > disk
>> >> >> > configuration and your hardware reference manuals for additional
>> >> >> > information.
>> >> >> > "
>> >> >> >
>> >> >> > The drive that the 2000 OS is on is brand new and although I
>> >> >> > cannot
>> >> >> > rule
>> >> >> > out
>> >> >> > it being faulty but was looking for other answers before
>> >> >> > formatting
>> >> >> > the
>> >> >> > drive
>> >> >> > again.
>> >> >> > I have the windows 2000 boot disk can I rebuild using these.
>> >> >> > (PS I have checked the connections they are all okay, also when
>> >> >> > bootied
>> >> >> > into
>> >> >> > Win 64 i can access and read/write to the C: Drive with win
>> >> >> > 2000's
>> >> >> >
>> >> >> > Many Thanks
>> >> >> > Martin
>> >> >> >
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>
>>
>>

John
Sat Dec 31 08:50:37 CST 2005

When is the last time you worked on a car, my friend. Last time there was a
generator on a car was the 1960's. However even a turnkey engine rarely if
ever comes with an alternator. :-)


"Tony Sperling" <tony.sperling@dbREMOVEmail.dk> wrote in message
news:%23pa2JPfDGHA.2664@TK2MSFTNGP15.phx.gbl...
> Well, last night, I did remember having an exchange with you on 'some'
> issue, I've now checked that, and personally I am at least happy with not
> having given you any wildy conflicting advise. I still feel that your
> problem may be much more 'trivial' than you imagine - it's like, if you
> are out driving and your Cadillac suddenly stops, you shouldn't start off
> by calling a rescue service and ask them to install a new engine. You
> definitely need to look at the 'cheeper' posibillities first, and by
> cheeper, I mean: regarding to the use of time and resources, as well as
> the prize factor. Such is the philosophy of the search for failures. Think
> about the Cadillac analogy, if it's the fuel pump or generator - a new
> engine would indeed fix the problem, the Garage would be very happy, and
> you would be non-the-wiser.
>
> Having a look inside the box, I regard as being the first-aid-kit of all
> computer failure recovery. Not having opened the case for 'a while', is by
> no means any indication of nothing being wrong in there, rather the
> opposite, perhaps. One of the more frequent causes to problems, is indeed
> of an electrical nature, I didn't ask you to check the connections inside
> for the faint possibillity that you (or someone else) hadn't been doing it
> properly from the begining - the simple fact is that vibration and
> temperature related issues can make good contact turn into
> not-so-good-contact, and when that happens the contact areas start
> oxidising and then it is only a matter of time when you begin to
> experience wildly random behavior, typically of the sort that doesn't give
> you any lead. And note - that this description is relating to a situation
> where everything is 'normal' inside that box. But it could be a Hardware
> failure. There is a saying that relates to electronics: "If it survives
> the first year, you will never get rid of it" - this is because, maybe 90%
> of all Hardware failures happen in the first year (this is not the same as
> saying 90% of all new computers have a failure in the first year) - most
> of the rest happen from misshandling.
>
> The lacking quality of the standard kind of Power Supply you find in a
> Super Market kind of machine, is another frequent contributor to this kind
> of behavior. Using the 'Wattage Rating' as a quality measure, is pure
> ignorance, and many 'HomeBuilders' too are eager to save a 'buck' and
> follow the standard rating as guideline. So, in order for anybody to be of
> any assistance to you, you really should try and help us gather some
> usefull information.
>
> The Linux disk, I think, is a great idea. While you are at it, I would
> suggest you use that to salvage any data you love on that disk before
> following that 'other' idea. Yes, try it if you are desperate! And if you
> have to start all over, use that opportunity to set up a dual-boot system.
> Regarding the Repair Install - if you boot the CD and ask it to make an
> installation, it will detect the presence of another Windows installation,
> and you will then be presented with an option to make a Repair
> Installation on that partition, this is not the same as Recovery Console,
> this is just after the actual installation begins.
>
> Tony. . .
>
> (And a happy NewYear, to you! (Barry, was it?))
>
>
> "Techead" <Techead@discussions.microsoft.com> wrote in message
> news:2BD17F80-70A8-4E07-B179-577CB0731605@microsoft.com...
>> See in-line reply:
>>
>> "Tony Sperling" wrote:
>>
>>> When you say "the CD's re-installation feature", is that the 'Repair
>>> Install'?
>>
>> Yes; but not the recovery console; Windows detected an installation
>> already
>> on the drive; Windows can attempt to fix this install...............
>>
>> If that fails, how would you get to do that 'other' installation
>>> you mention?
>>
>> I'm thinking if the first installation has infected files, then when the
>> re-installation tries to load the drivers that are currently configured
>> in
>> that install's version, an infected driver can cause the installation to
>> crash. Whereas a fresh install can load the basic drivers (LAN, Video,
>> wireless / mouse) from my GigaByte-CD. That's all I need to get the PC
>> running again.
>>
>> I'm also downloading "Linux Defender" now (637 Mb) as an ISO. I'll create
>> a
>> bootable-CD and scan my drive before I try the 2nd install.
>>
>>>
>>> Ahh, I will ask you to hang on for a bit, it's late and I will have to
>>> think
>>> it over. There was a time when it would have been alright, but that was
>>> before MS came up with the Registry. Right now, I think you might be in
>>> for
>>> some trouble if you do. And, overall - if you are running Avast, I would
>>> not
>>> start off thinking about 'infection' - heck, that thing is updating more
>>> often than I change my socks! You can litterally have several updates
>>> before
>>> you even hear about an issue in the press. Give it a rest, see what it
>>> says
>>> in the morning, and if the disk is IDE, I'd begin by rocking the flat
>>> cable
>>> gently, swap it if you have a spare. They are surprisingly tuff, but
>>> they
>>> are one of the more frequent sources of contact problems in a box, I
>>> would
>>> say. (oh, and take off your wrist-watch!)
>>
>> My boot-drive is a Maxtor 300 Gb SATA (non-RAID) mode. I haven't opened
>> the
>> case in a while, so that shouldn't be the cause. I've ran CHKDSK /R a few
>> times; no affect.
>>
>>>
>>> Also, check that your BIOS setup is intact, and reset it to it's safe
>>> setting if possible.
>>
>> I did that already; no luck.
>>
>> And try to think of what the last piece of action you had the machine
>> perform, was.
>>
>> If Linux Defender doesn't find a culprit, and replacing my 1 Gb RAM
>> module
>> on Sat. (12/31/05) doesn't resolve the issue; then Ill be forced to
>> install
>> that 2nd instance of Win-XP 64-bit in C:\WINNT folder and boot from
>> there.
>> Perhaps then I can get the system restore from the first instance to
>> resolve
>> the issue?
>>
>> Your thoughts?
>>>
>>>
>>> Tony. . .
>>>
>>>
>>> "Techead" <Techead@discussions.microsoft.com> wrote in message
>>> news:50D15ED2-EB79-4024-BC60-6C590E6299B0@microsoft.com...
>>> > Tony:
>>> >
>>> > I'm thinking you know the answer to this:
>>> >
>>> > My XP 64-bit is hanging (keyboard / mouse froze) after loading my
>>> > "start-up
>>> > apps"; I think Avast missed one of those infected .wmf files! I tried
>>> > usig
>>> > the CD's re-installation feature, and it too hangs during the "loading
>>> > devices" portion. Since I don't have a 2nd drive, nor 2nd partition,
>>> > would
>>> > it
>>> > be "safe" to install a 2nd copy of XP 64-bit in a C:\WINNT folder???
>>> > Then
>>> > I
>>> > could install the updated patches from MS and run Avast's upgraded
>>> > version
>>> > (and perhaps do a few online scans from others).
>>> >
>>> > What do you think?
>>> >
>>> > Techead
>>> >
>>> > "Tony Sperling" wrote:
>>> >
>>> >> Shouldn't you just follow John's recipy for the earlier problem,
>>> >> again?
>>> >>
>>> >>
>>> >> Tony. . .
>>> >>
>>> >>
>>> >> "MGbassace" <MGbassace@discussions.microsoft.com> wrote in message
>>> >> news:1E817A45-940A-4B35-BD83-5950D30167D1@microsoft.com...
>>> >> > TedF, Thanks for the advise, I cannot get it to do anything, I
>>> >> > resorted
>>> >> > to
>>> >> > installing a fresh copy on this drive from the boot disc's, The
>>> >> > only
>>> >> > problem
>>> >> > being now is that maybe i should have disconnected the other drive
>>> >> > with
>>> >> > win
>>> >> > 64 on as now it wont boot into that, usual cannot locate file. not
>>> >> > sure
>>> >> > how
>>> >> > to resolve this without re-installing win 64.
>>> >> > BTW on a lighter note does anyone know how to extact the keycode
>>> >> > from
>>> >> > win
>>> >> > 2003 server, I have a genuine copy but unfortunatley when server
>>> >> > went
>>> >> > down
>>> >> > and was beyond repair skipped it along with the COA and keycode,
>>> >> > DOH
>>> >> >
>>> >> > "TedF" wrote:
>>> >> >
>>> >> >> Can you run CHKDSK ?
>>> >> >>
>>> >> >> "MGbassace" <MGbassace@discussions.microsoft.com> wrote in message
>>> >> >> news:48E4A265-DC38-4033-BA9B-46D2B2C99C7E@microsoft.com...
>>> >> >> > Followuing on from an earlier post and a successful answer I am
>>> >> >> > having
>>> >> >> > issues
>>> >> >> > again. I recently did a rebuild of the boot record on my machine
>>> >> >> > as
>>> >> >> > it
>>> >> >> > didnt
>>> >> >> > detect the two OS's. Windows 2000 on drive C: , Windows XP 64
>>> >> >> > bit on
>>> >> >> > drive
>>> >> >> > D:, The rebuild of the mbr seems to have cured it for the time
>>> >> >> > being
>>> >> >> > however
>>> >> >> > on Christmas day of all days i turned the machine on and and
>>> >> >> > get a
>>> >> >> > message
>>> >> >> > similar to the following.
>>> >> >> > "Windows 2000 could not start because of a computer disk
>>> >> >> > hardware
>>> >> >> > configuration problem.
>>> >> >> > Could not read from the selected boot disk. Check boot path and
>>> >> >> > disk
>>> >> >> > hardware.
>>> >> >> > Please check the Windows 2000(TM) documentation about hardware
>>> >> >> > disk
>>> >> >> > configuration and your hardware reference manuals for additional
>>> >> >> > information.
>>> >> >> > "
>>> >> >> >
>>> >> >> > The drive that the 2000 OS is on is brand new and although I
>>> >> >> > cannot
>>> >> >> > rule
>>> >> >> > out
>>> >> >> > it being faulty but was looking for other answers before
>>> >> >> > formatting
>>> >> >> > the
>>> >> >> > drive
>>> >> >> > again.
>>> >> >> > I have the windows 2000 boot disk can I rebuild using these.
>>> >> >> > (PS I have checked the connections they are all okay, also when
>>> >> >> > bootied
>>> >> >> > into
>>> >> >> > Win 64 i can access and read/write to the C: Drive with win
>>> >> >> > 2000's
>>> >> >> >
>>> >> >> > Many Thanks
>>> >> >> > Martin
>>> >> >> >
>>> >> >>
>>> >> >>
>>> >> >>
>>> >>
>>> >>
>>> >>
>>>
>>>
>>>
>
>

Tony
Sat Dec 31 10:08:28 CST 2005

Yes, I did use a bit of 'poetic license' there, i admit - although, here in
Denmark, both types are defined as 'generators', please label that as: 'one
of those things'. And - as for cars - I am considerably more interested in
the veterans. The 50's & the 60's - the golden years of car building - after
that, only junk. Before, examples of brilliant and unparalleled workmanship
in combination with an unfinished technology.

(grunt - I hate those instances, when more terms are valid, yet mutually
exclusive across languages!)


Tony. . .


"John Barnes" <jbfoofy@email.net> wrote in message
news:%23lAPSmhDGHA.2320@TK2MSFTNGP11.phx.gbl...
> When is the last time you worked on a car, my friend. Last time there was
> a generator on a car was the 1960's. However even a turnkey engine rarely
> if ever comes with an alternator. :-)
>
>
> "Tony Sperling" <tony.sperling@dbREMOVEmail.dk> wrote in message
> news:%23pa2JPfDGHA.2664@TK2MSFTNGP15.phx.gbl...
>> Well, last night, I did remember having an exchange with you on 'some'
>> issue, I've now checked that, and personally I am at least happy with not
>> having given you any wildy conflicting advise. I still feel that your
>> problem may be much more 'trivial' than you imagine - it's like, if you
>> are out driving and your Cadillac suddenly stops, you shouldn't start off
>> by calling a rescue service and ask them to install a new engine. You
>> definitely need to look at the 'cheeper' posibillities first, and by
>> cheeper, I mean: regarding to the use of time and resources, as well as
>> the prize factor. Such is the philosophy of the search for failures.
>> Think about the Cadillac analogy, if it's the fuel pump or generator - a
>> new engine would indeed fix the problem, the Garage would be very happy,
>> and you would be non-the-wiser.
>>
>> Having a look inside the box, I regard as being the first-aid-kit of all
>> computer failure recovery. Not having opened the case for 'a while', is
>> by no means any indication of nothing being wrong in there, rather the
>> opposite, perhaps. One of the more frequent causes to problems, is indeed
>> of an electrical nature, I didn't ask you to check the connections inside
>> for the faint possibillity that you (or someone else) hadn't been doing
>> it properly from the begining - the simple fact is that vibration and
>> temperature related issues can make good contact turn into
>> not-so-good-contact, and when that happens the contact areas start
>> oxidising and then it is only a matter of time when you begin to
>> experience wildly random behavior, typically of the sort that doesn't
>> give you any lead. And note - that this description is relating to a
>> situation where everything is 'normal' inside that box. But it could be a
>> Hardware failure. There is a saying that relates to electronics: "If it
>> survives the first year, you will never get rid of it" - this is because,
>> maybe 90% of all Hardware failures happen in the first year (this is not
>> the same as saying 90% of all new computers have a failure in the first
>> year) - most of the rest happen from misshandling.
>>
>> The lacking quality of the standard kind of Power Supply you find in a
>> Super Market kind of machine, is another frequent contributor to this
>> kind of behavior. Using the 'Wattage Rating' as a quality measure, is
>> pure ignorance, and many 'HomeBuilders' too are eager to save a 'buck'
>> and follow the standard rating as guideline. So, in order for anybody to
>> be of any assistance to you, you really should try and help us gather
>> some usefull information.
>>
>> The Linux disk, I think, is a great idea. While you are at it, I would
>> suggest you use that to salvage any data you love on that disk before
>> following that 'other' idea. Yes, try it if you are desperate! And if you
>> have to start all over, use that opportunity to set up a dual-boot
>> system. Regarding the Repair Install - if you boot the CD and ask it to
>> make an installation, it will detect the presence of another Windows
>> installation, and you will then be presented with an option to make a
>> Repair Installation on that partition, this is not the same as Recovery
>> Console, this is just after the actual installation begins.
>>
>> Tony. . .
>>
>> (And a happy NewYear, to you! (Barry, was it?))
>>
>>
>> "Techead" <Techead@discussions.microsoft.com> wrote in message
>> news:2BD17F80-70A8-4E07-B179-577CB0731605@microsoft.com...
>>> See in-line reply:
>>>
>>> "Tony Sperling" wrote:
>>>
>>>> When you say "the CD's re-installation feature", is that the 'Repair
>>>> Install'?
>>>
>>> Yes; but not the recovery console; Windows detected an installation
>>> already
>>> on the drive; Windows can attempt to fix this install...............
>>>
>>> If that fails, how would you get to do that 'other' installation
>>>> you mention?
>>>
>>> I'm thinking if the first installation has infected files, then when the
>>> re-installation tries to load the drivers that are currently configured
>>> in
>>> that install's version, an infected driver can cause the installation to
>>> crash. Whereas a fresh install can load the basic drivers (LAN, Video,
>>> wireless / mouse) from my GigaByte-CD. That's all I need to get the PC
>>> running again.
>>>
>>> I'm also downloading "Linux Defender" now (637 Mb) as an ISO. I'll
>>> create a
>>> bootable-CD and scan my drive before I try the 2nd install.
>>>
>>>>
>>>> Ahh, I will ask you to hang on for a bit, it's late and I will have to
>>>> think
>>>> it over. There was a time when it would have been alright, but that was
>>>> before MS came up with the Registry. Right now, I think you might be in
>>>> for
>>>> some trouble if you do. And, overall - if you are running Avast, I
>>>> would not
>>>> start off thinking about 'infection' - heck, that thing is updating
>>>> more
>>>> often than I change my socks! You can litterally have several updates
>>>> before
>>>> you even hear about an issue in the press. Give it a rest, see what it
>>>> says
>>>> in the morning, and if the disk is IDE, I'd begin by rocking the flat
>>>> cable
>>>> gently, swap it if you have a spare. They are surprisingly tuff, but
>>>> they
>>>> are one of the more frequent sources of contact problems in a box, I
>>>> would
>>>> say. (oh, and take off your wrist-watch!)
>>>
>>> My boot-drive is a Maxtor 300 Gb SATA (non-RAID) mode. I haven't opened
>>> the
>>> case in a while, so that shouldn't be the cause. I've ran CHKDSK /R a
>>> few
>>> times; no affect.
>>>
>>>>
>>>> Also, check that your BIOS setup is intact, and reset it to it's safe
>>>> setting if possible.
>>>
>>> I did that already; no luck.
>>>
>>> And try to think of what the last piece of action you had the machine
>>> perform, was.
>>>
>>> If Linux Defender doesn't find a culprit, and replacing my 1 Gb RAM
>>> module
>>> on Sat. (12/31/05) doesn't resolve the issue; then Ill be forced to
>>> install
>>> that 2nd instance of Win-XP 64-bit in C:\WINNT folder and boot from
>>> there.
>>> Perhaps then I can get the system restore from the first instance to
>>> resolve
>>> the issue?
>>>
>>> Your thoughts?
>>>>
>>>>
>>>> Tony. . .
>>>>
>>>>
>>>> "Techead" <Techead@discussions.microsoft.com> wrote in message
>>>> news:50D15ED2-EB79-4024-BC60-6C590E6299B0@microsoft.com...
>>>> > Tony:
>>>> >
>>>> > I'm thinking you know the answer to this:
>>>> >
>>>> > My XP 64-bit is hanging (keyboard / mouse froze) after loading my
>>>> > "start-up
>>>> > apps"; I think Avast missed one of those infected .wmf files! I tried
>>>> > usig
>>>> > the CD's re-installation feature, and it too hangs during the
>>>> > "loading
>>>> > devices" portion. Since I don't have a 2nd drive, nor 2nd partition,
>>>> > would
>>>> > it
>>>> > be "safe" to install a 2nd copy of XP 64-bit in a C:\WINNT folder???
>>>> > Then
>>>> > I
>>>> > could install the updated patches from MS and run Avast's upgraded
>>>> > version
>>>> > (and perhaps do a few online scans from others).
>>>> >
>>>> > What do you think?
>>>