Re: Repair Windows XP by using the XP installation CD
Franc Zabkar wrote:
> On Sun, 31 Aug 2008 08:10:50 -0300, "John John (MVP)"
> <audetweld@nbnet.nb.ca> put finger to keyboard and composed:
>
>
>>Franc Zabkar wrote:
>>
>>>On Sat, 30 Aug 2008 00:24:23 -0300, "John John (MVP)"
>>><audetweld@nbnet.nb.ca> put finger to keyboard and composed:
>>>
>>>
>>>
>>>>Franc Zabkar wrote:
>>>>
>>>>
>>>>
>>>>>On Fri, 29 Aug 2008 12:05:00 +0100, admin_papa
>>>>><admin_papa.2fd9e5c@news.win98banter.com> put finger to keyboard and
>>>>>composed:
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>Just wanted to share my new experience.
>>>>>>
>>>>>>If your system fails to start due to an error corresponding to missing
>>>>>>HAL.DLL, invalid Boot.ini or any other critical system boot files you
>>>>>>can repair this by using the XP installation CD. Just boot from your XP
>>>>>>Setup CD and enter the Recovery Console. Then run "attrib -H -R -S" on
>>>>>>the C:\Boot.ini file and delete it. Launch "Bootcfg /Rebuild" and then
>>>>>>Fixboot
>>>>>>
>>>>>>Cheers,
>>>>>>Carl
>>>>>
>>>>>
>>>>>Do not run FIXBOOT on a FAT32 partition. You *will* trash it.
>>>>
>>>>That is simply not true, fixboot does not trash FAT32 partitions. That
>>>>you would have experienced a disk problem after using fixboot is more
>>>>coincidence than anything else, your disk probably had other problems or
>>>>corruption and as luck would have it the disk failed when you used
>>>>fixboot. Fixboot is the prescribed method for repairing the NT boot
>>>>sector and returning the boot loader from Io.sys to ntldr, the command
>>>>is safe and it does not trash FAT32 partitions, your disk had other
>>>>problems when you ran the command.
>>>>
>>>>John
>>>
>>>
>>>That's how it's supposed to work. However, FIXBOOT actually turns your
>>>FAT32 partition into a 10MB FAT16 drive, at least under some
>>>circumstances. Many people have experienced exactly the same problem.
>>
>>That is not true! You are spreading misinformation. These kinds of
>>problems usually result when the command is run on improperly cloned
>>drives, the problem is not with fixboot, it is with incorrect drive
>>geometry that results from a bad cloning job. Windows 2000/XP are
>>compatible with FAT32 and they can be installed on FAT32, fixboot does
>>not damage partitions and it does not change FAT32 partitions into FAT16
>>partitions, if you experience such difficulties you have other disk
>>problems and that is not fixboot's fault!
>>
>>John
>
>
> Actually the problem in my case was that Fixboot wrote a FAT12 boot
> sector (used by floppy discs or HDs smaller than 16MB), not FAT16.
That is a *known* symptom that can occur in the somewhat infrequent
situation when *both* the bootsector and the backup bootsector are
corrupted, it is by no means a common occurrence and it also occurs with
NTFS partitions, it is not a basis for proclaiming that fixboot trashes
FAT32 partitions and turns them into FAT12, when this problem occurs the
disk is experiencing other difficulties or corruption problems.
> The history of the problematic HD, AFAICT, is that is was formatted as
> FAT32 by Win9x (the backup boot sector had references to IO.SYS and
> MSDOS.SYS), and then XP was later installed over the top. It had been
> working OK for several years until one day it powered up with a
> "missing NTLDR" error. DISKPART was able to see the full partition
> (38GB), so the partition table and MBR were apparently OK. A
> subsequent Fixboot then trashed the boot sector. This begs the
> question, why did Fixboot create a 10MB FAT12 boot sector when the
> partition table was reporting a size of 38GB? An "NTLDR is missing"
> error message is present in the FAT32 boot sector, so it appears that
> the original boot sector may have been OK. Instead the FATs were
> probably corrupt, as later suggested, and repaired, by Scandisk.
>
> I invite you to search the Internet for "fixboot FAT12" or "fixboot
> FAT16".
I have. In the Google Groups archive a search for fixboot fat16 returns
a grand total of 11 hits, two of which are related to this discussion
http://groups.google.com/groups/search?lr=&safe=off&num=100&q=fixboot+fat16&safe=off&qt_s=Search
And a search for fixboot fat12 returns even fewer hits, a grand total of
4 hits, one of which is related to this discussion.
A Google search for Fixboot+fat12 returns a paltry 2,730 hits, and a
Yahoo! search returns 2,030, by no means can it be said that this is
indicative of a common or frequent problem with fixboot, to the contrary
it indicates that this is a rare or infrequent situation. This problem
is only encountered when other disk corruption is presents and even then
it is a rather rare occurrence.
> Maybe you're right and maybe Fixboot doesn't trash good
> partitions,
It doesn't, you had *one* bad experience and as luck would have it you
had other existing disk problems which caused problems with fixboot,
this is by no means ample evidence and reason to issue a broad and
definitive claim stating that fixboot *trashes* FAT32 partitions or that
it turns them into FAT12 partitions.
> but clearly there are many documented cases where it makes
> an existing problem much, much worse.
Many? Make that a handful of cases. A search on the net that results
in a couple thousands of hits is by no means many, it is but a few.
Give me a problem with millions of hits and documented cases, or at
least hundreds of thousands of hits and then we can start talking about
many cases.
AFAICS, if you're having a file
> system problem, expect Fixboot to hinder you, not help you. I
> certainly will never trust it again.
That is certainly your prerogative. It doesn't mean that others have
had or will have the same bad experience with the command, the command
has been used successfully by others hundreds of thousands or millions
of times.
> BTW, if I can get my hands on an XP CD, I'll try a few experiments to
> see if I can reproduce the FAT12 problem.
You can download the 6 floppy diskette setup set from Microsoft or
download an .iso copy of the Recovery Console on several web sites.
John