What is wrong with WinME?

Yes, well with the backup regime you're pretty well safe and everyone should
back up religiously regardless of which OS they use anyway. I just want to
make the point that *I* used to think XP had this boot file corruption
problem that would require a reinstallation from time to time - but while it
was a fairly regular occurance in the beginning, I haven't seen it for
several years - except where it has been this easily correctable boot.ini
issue. Possibly it always was this boot.ini thing (which is probably much
more rare if you only have one partition - though backing up is that much
more troublesome, so less likely to be done, which is why one big C: will
always be birdbrained!).

Certainly I once thought XP was far from as trouble-free as they were making
out; now I think it really takes an effort to break it! It *is* the best OS
MS have made. Though they still haven't fixed their Activation procedure.

P.S.

I forgot what I was going to say.


Mart wrote:
> Thanks S - I appreciate your suggestion which sounds like a d**m good
> idea. (Although in my case it was a failed HDD rather than just a
> missing file) But I suppose I've veered a bit OT and we are in danger
> of highjacking LM's thread.
>
> Mart
>
>
> "Pogle S. Wood" <wood.pogle.DeleteThis@googlemail.com> wrote in message
> news:%239tlc4RBJHA.4368@TK2MSFTNGP06.phx.gbl...
>>> My own experience of an XP box (catastrophically) failing to boot
>>> was when the HDD died - so can't really blame it on XP. But have to
>>> admit that trying to recover data from an NTFS HDD was "difficult"
>>> - Soon learnt to use a backup regime after that!
>>>
>>
>>
>> The one most people run into like into a brick wall is the failing
>> to boot due to the HCL or autochk or NTDETECT or similar not being
>> found and, usually, in my experience, that is due to an incorrect
>> boot.ini. And apart from the fact you can correct that via booting
>> with a BartPE disc - though that is quite a lot of effort to make in
>> the first place - you can edit boot.ini via BootItNG (unregistered).
>> Burn one to cd (especially since odds are you won't have a floppy
>> drive anymore!) and there is no need to update it. With SATA and
>> RAID (and NT6.x as well as NT5.x) I still use a BING cd from 2006,
>> and it can be a godsend. Of course, if you make a copy of boot.ini
>> and leave it in the root you don't even need to edit, just rename.
>>
>>
>> P.

"Pogle S. Wood" wrote:

> Yes, well with the backup regime you're pretty well safe and everyone should
> back up religiously regardless of which OS they use anyway. I just want to
> make the point that *I* used to think XP had this boot file corruption
> problem that would require a reinstallation from time to time - but while it
> was a fairly regular occurance in the beginning, I haven't seen it for
> several years - except where it has been this easily correctable boot.ini
> issue. Possibly it always was this boot.ini thing (which is probably much
> more rare if you only have one partition - though backing up is that much
> more troublesome, so less likely to be done, which is why one big C: will
> always be birdbrained!).
>
> Certainly I once thought XP was far from as trouble-free as they were making
> out; now I think it really takes an effort to break it! It *is* the best OS
> MS have made. Though they still haven't fixed their Activation procedure.
>
> P.S.
>
> I forgot what I was going to say.
>
>
> Mart wrote:
> > Thanks S - I appreciate your suggestion which sounds like a d**m good
> > idea. (Although in my case it was a failed HDD rather than just a
> > missing file) But I suppose I've veered a bit OT and we are in danger
> > of highjacking LM's thread.
> >
> > Mart
> >
> >
> > "Pogle S. Wood" <wood.pogle DeleteThis @googlemail.com> wrote in message
> > news:%239tlc4RBJHA.4368@TK2MSFTNGP06.phx.gbl...
> >>> My own experience of an XP box (catastrophically) failing to boot
> >>> was when the HDD died - so can't really blame it on XP. But have to
> >>> admit that trying to recover data from an NTFS HDD was "difficult"
> >>> - Soon learnt to use a backup regime after that!
> >>>
> >>
> >>
> >> The one most people run into like into a brick wall is the failing
> >> to boot due to the HCL or autochk or NTDETECT or similar not being
> >> found and, usually, in my experience, that is due to an incorrect
> >> boot.ini. And apart from the fact you can correct that via booting
> >> with a BartPE disc - though that is quite a lot of effort to make in
> >> the first place - you can edit boot.ini via BootItNG (unregistered).
> >> Burn one to cd (especially since odds are you won't have a floppy
> >> drive anymore!) and there is no need to update it. With SATA and
> >> RAID (and NT6.x as well as NT5.x) I still use a BING cd from 2006,
> >> and it can be a godsend. Of course, if you make a copy of boot.ini
> >> and leave it in the root you don't even need to edit, just rename.
> >>
> >>
> >> P.
>
>
>