Re: Corrupt Files

Yep, that is why I am a non-expert (and getting too old at that)....LOL

To test drive:
My computer, rt click on drive, select properties, tools, error checking,
then click button "check now"
(or can probably be run from the "Run" command, but I usually don't)

regards,

Roy

"Colin Barnhorst" <colinbarharst(remove)@msn.com> wrote in message
news:OcdZ7q5$...
>A minor matter, but in #2. read 'chkdsk' rather than 'scandisk' (a
>Win9x/ME) program.
>
> --
> Colin Barnhorst [MVP Windows - Virtual Machine]
> (Reply to the group only unless otherwise requested)
> "renoch" <> wrote in message
> news:uhjEIe5$...
>> What you are describing sounds more like a hardware issue rather than a
>> X64 issue.
>>
>> Suggestions from a non-expert:
>> 1. Turn off any overclocking of your system bus or RAM memory
>> 2. Run Scandisk on your hard drives
>> 3. Run Memtest86 on your RAM memory
>> 4. Check the temperature of your system (your bios probably has
>> provisions to do this), this actually sounds like a system overheating
>> issue... verify all your case fans are functioning.
>> 5. This could also be from an inadequate (underpowdered) power supply.
>> Check your bus voltages, if you can, in your bios or with a voltmeter.
>>
>> good luck,
>>
>> Roy
>>
>>
>> "Paul Ferrill" <> wrote in message
>> news:%23IJHpK5$...
>>> Anyone else have the problem of corrupt files in XP64?
>>>
>>> I can't seem to get a good download off the MSDN subscriptions site to
>>> save my life. And today I copied a Ghost image file of another machine
>>> and when I copied it to a USB drive for restore Ghost says its
>>> corrupted.
>>>
>>> Help...
>>>
>>
>>
>
>

Advertisements

Right. If run from Start>Run and type command. At the prompt the command
is 'chkdsk /f' to both check and repair. Without the /f one only gets the
chkdsk report but no corrective actions take place. It results in the same
thing that you describe.

--
Colin Barnhorst [MVP Windows - Virtual Machine]
(Reply to the group only unless otherwise requested)
"renoch" <> wrote in message
news:OcoPM45$...
> Yep, that is why I am a non-expert (and getting too old at that)....LOL
>
> To test drive:
> My computer, rt click on drive, select properties, tools, error checking,
> then click button "check now"
> (or can probably be run from the "Run" command, but I usually don't)
>
> regards,
>
> Roy
>
>
> "Colin Barnhorst" <colinbarharst(remove)@msn.com> wrote in message
> news:OcdZ7q5$...
>>A minor matter, but in #2. read 'chkdsk' rather than 'scandisk' (a
>>Win9x/ME) program.
>>
>> --
>> Colin Barnhorst [MVP Windows - Virtual Machine]
>> (Reply to the group only unless otherwise requested)
>> "renoch" <> wrote in message
>> news:uhjEIe5$...
>>> What you are describing sounds more like a hardware issue rather than a
>>> X64 issue.
>>>
>>> Suggestions from a non-expert:
>>> 1. Turn off any overclocking of your system bus or RAM memory
>>> 2. Run Scandisk on your hard drives
>>> 3. Run Memtest86 on your RAM memory
>>> 4. Check the temperature of your system (your bios probably has
>>> provisions to do this), this actually sounds like a system overheating
>>> issue... verify all your case fans are functioning.
>>> 5. This could also be from an inadequate (underpowdered) power supply.
>>> Check your bus voltages, if you can, in your bios or with a voltmeter.
>>>
>>> good luck,
>>>
>>> Roy
>>>
>>>
>>> "Paul Ferrill" <> wrote in message
>>> news:%23IJHpK5$...
>>>> Anyone else have the problem of corrupt files in XP64?
>>>>
>>>> I can't seem to get a good download off the MSDN subscriptions site to
>>>> save my life. And today I copied a Ghost image file of another machine
>>>> and when I copied it to a USB drive for restore Ghost says its
>>>> corrupted.
>>>>
>>>> Help...
>>>>
>>>
>>>
>>
>>
>
>

Advertisements

The first sentence should read, "Right. If you run chkdsk from Start>Run,
type 'command' to open the command window."

--
Colin Barnhorst [MVP Windows - Virtual Machine]
(Reply to the group only unless otherwise requested)
"Colin Barnhorst" <colinbarharst(remove)@msn.com> wrote in message
news:O7Da1O6$...
> Right. If run from Start>Run and type command. At the prompt the command
> is 'chkdsk /f' to both check and repair. Without the /f one only gets the
> chkdsk report but no corrective actions take place. It results in the
> same thing that you describe.
>
> --
> Colin Barnhorst [MVP Windows - Virtual Machine]
> (Reply to the group only unless otherwise requested)
> "renoch" <> wrote in message
> news:OcoPM45$...
>> Yep, that is why I am a non-expert (and getting too old at that)....LOL
>>
>> To test drive:
>> My computer, rt click on drive, select properties, tools, error checking,
>> then click button "check now"
>> (or can probably be run from the "Run" command, but I usually don't)
>>
>> regards,
>>
>> Roy
>>
>>
>> "Colin Barnhorst" <colinbarharst(remove)@msn.com> wrote in message
>> news:OcdZ7q5$...
>>>A minor matter, but in #2. read 'chkdsk' rather than 'scandisk' (a
>>>Win9x/ME) program.
>>>
>>> --
>>> Colin Barnhorst [MVP Windows - Virtual Machine]
>>> (Reply to the group only unless otherwise requested)
>>> "renoch" <> wrote in message
>>> news:uhjEIe5$...
>>>> What you are describing sounds more like a hardware issue rather than a
>>>> X64 issue.
>>>>
>>>> Suggestions from a non-expert:
>>>> 1. Turn off any overclocking of your system bus or RAM memory
>>>> 2. Run Scandisk on your hard drives
>>>> 3. Run Memtest86 on your RAM memory
>>>> 4. Check the temperature of your system (your bios probably has
>>>> provisions to do this), this actually sounds like a system overheating
>>>> issue... verify all your case fans are functioning.
>>>> 5. This could also be from an inadequate (underpowdered) power supply.
>>>> Check your bus voltages, if you can, in your bios or with a voltmeter.
>>>>
>>>> good luck,
>>>>
>>>> Roy
>>>>
>>>>
>>>> "Paul Ferrill" <> wrote in message
>>>> news:%23IJHpK5$...
>>>>> Anyone else have the problem of corrupt files in XP64?
>>>>>
>>>>> I can't seem to get a good download off the MSDN subscriptions site to
>>>>> save my life. And today I copied a Ghost image file of another machine
>>>>> and when I copied it to a USB drive for restore Ghost says its
>>>>> corrupted.
>>>>>
>>>>> Help...
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>

You don't need to open a command window. Just type your command in the Run
window.

"Colin Barnhorst" <colinbarharst(remove)@msn.com> wrote in message
news:eqaoud6$...
> The first sentence should read, "Right. If you run chkdsk from Start>Run,
> type 'command' to open the command window."
>
> --
> Colin Barnhorst [MVP Windows - Virtual Machine]
> (Reply to the group only unless otherwise requested)
> "Colin Barnhorst" <colinbarharst(remove)@msn.com> wrote in message
> news:O7Da1O6$...
>> Right. If run from Start>Run and type command. At the prompt the
>> command is 'chkdsk /f' to both check and repair. Without the /f one only
>> gets the chkdsk report but no corrective actions take place. It results
>> in the same thing that you describe.
>>
>> --
>> Colin Barnhorst [MVP Windows - Virtual Machine]
>> (Reply to the group only unless otherwise requested)
>> "renoch" <> wrote in message
>> news:OcoPM45$...
>>> Yep, that is why I am a non-expert (and getting too old at that)....LOL
>>>
>>> To test drive:
>>> My computer, rt click on drive, select properties, tools, error
>>> checking, then click button "check now"
>>> (or can probably be run from the "Run" command, but I usually don't)
>>>
>>> regards,
>>>
>>> Roy
>>>
>>>
>>> "Colin Barnhorst" <colinbarharst(remove)@msn.com> wrote in message
>>> news:OcdZ7q5$...
>>>>A minor matter, but in #2. read 'chkdsk' rather than 'scandisk' (a
>>>>Win9x/ME) program.
>>>>
>>>> --
>>>> Colin Barnhorst [MVP Windows - Virtual Machine]
>>>> (Reply to the group only unless otherwise requested)
>>>> "renoch" <> wrote in message
>>>> news:uhjEIe5$...
>>>>> What you are describing sounds more like a hardware issue rather than
>>>>> a X64 issue.
>>>>>
>>>>> Suggestions from a non-expert:
>>>>> 1. Turn off any overclocking of your system bus or RAM memory
>>>>> 2. Run Scandisk on your hard drives
>>>>> 3. Run Memtest86 on your RAM memory
>>>>> 4. Check the temperature of your system (your bios probably has
>>>>> provisions to do this), this actually sounds like a system overheating
>>>>> issue... verify all your case fans are functioning.
>>>>> 5. This could also be from an inadequate (underpowdered) power
>>>>> supply. Check your bus voltages, if you can, in your bios or with a
>>>>> voltmeter.
>>>>>
>>>>> good luck,
>>>>>
>>>>> Roy
>>>>>
>>>>>
>>>>> "Paul Ferrill" <> wrote in message
>>>>> news:%23IJHpK5$...
>>>>>> Anyone else have the problem of corrupt files in XP64?
>>>>>>
>>>>>> I can't seem to get a good download off the MSDN subscriptions site
>>>>>> to save my life. And today I copied a Ghost image file of another
>>>>>> machine and when I copied it to a USB drive for restore Ghost says
>>>>>> its corrupted.
>>>>>>
>>>>>> Help...
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>

Share This Page

Welcome to Velocity Reviews!

Welcome to the Velocity Reviews, the place to come for the latest tech news and reviews.

Please join our friendly community by clicking the button below - it only takes a few seconds and is totally free. You'll be able to chat with other enthusiasts and get tech help from other members.
Sign up now!