A question on going from ME to XP

[Mike M]

> I just extracted all those files and went to the Windows Setup tab
> and to my surprise the list view was no longer empty!

A problem you had not previously mentioned, or at least not that I recall
in this thread, and yes, restoring the INF files would re-populate
Add/Remove Programs | Windows Setup. In addition you should now find that
you are able to create a Win Me boot floppy using Add/Remove Programs |
Startup Disk now that you have restored BASE2.CAB.

> the only concern I
> would have is burner for it was only for ME and Win2k. Although, is
> it true that most Win2k drivers work on XP?

I have to assume here that you mean your CD burning SOFTWARE was for Win
Me/W2K. Moving to XP would probably mean your upgrading a fair bit of
software including anti-virus, CD burning and firewall
applications/software in addition to locating and installing XP drivers
for your audio and network card(s) due to changes in how these work in XP.
In fact before making any attempt to install XP I would want to track down
and save XP compatible drivers for all my hardware.

Best of luck.
--
Mike Maltby
mike.maltby@gmail.com



SSJ04 Mewtwo <ssj04mewtwo@yahoo.com> wrote:

> Mike M <No_Spam@Corned_Beef.Only> wrote:
>
> An "out of the box" clean install of Win Me here shows 488 INF files
> dated 8 June 2000 in the Windows\Inf folder. PRECOPY1.CAB contains
> 370 INF files, BASE2.CAB contains 2 INF files and WIN_18.CAB a
> further 166, a
> total of 538. I don't think that any harm is likely to result from
> extracting all of these and placing them in the Windows\Inf folder.
>
> I just extracted all those files and went to the Windows Setup tab
> and to my surprise the list view was no longer empty!
>
> I re-installed the games since internet checkers went missing a while
> back. Hm, this machine was built back in '01, the only concern I
> would have is burner for it was only for ME and Win2k. Although, is
> it true that most Win2k drivers work on XP?

 

[SSJ04 Mewtwo]

Mike M <No_Spam@Corned_Beef.Only> wrote:


A problem you had not previously mentioned, or at least not that I recall
in this thread, and yes, restoring the INF files would re-populate
Add/Remove Programs | Windows Setup. In addition you should now find that
you are able to create a Win Me boot floppy using Add/Remove Programs |
Startup Disk now that you have restored BASE2.CAB.
I think I'd mentioned it in a thread way...,way back but never found a
solution. And yes, I've made a WinME boot floppy disk. I've got it safely
tucked away with my JAWS authorization floppy.

 

[George Gee]

SSJ04 Mewtwo

Anyone trying to follow this thread will probably find it hard work, as you
seem to be removing the indents that OE adds to differentiate between
posters!

George Gee


"SSJ04 Mewtwo" <ssj04mewtwo@yahoo.com> wrote in message
news:fj9c62$mv1$1@news.datemas.de...
> Mike M <No_Spam@Corned_Beef.Only> wrote:
>
>
> A problem you had not previously mentioned, or at least not that I recall
> in this thread, and yes, restoring the INF files would re-populate
> Add/Remove Programs | Windows Setup. In addition you should now find that
> you are able to create a Win Me boot floppy using Add/Remove Programs |
> Startup Disk now that you have restored BASE2.CAB.
> I think I'd mentioned it in a thread way...,way back but never found a
> solution. And yes, I've made a WinME boot floppy disk. I've got it
> safely
> tucked away with my JAWS authorization floppy.
>
>

 

[Mike M]

> I think I'd mentioned it in a thread way...,way back

Not in this thread, that information could perhaps have led me to the
cause of your problems somewhat quicker than I did. You might also want
to try and establish who deleted all the INF files and why since I am
pretty confident that nothing from Cox would have done so. The reason I
ask is that unless you know who and why there is a pretty good chance the
same might happen again.
--
Mike Maltby
mike.maltby@gmail.com


SSJ04 Mewtwo <ssj04mewtwo@yahoo.com> wrote:

> I think I'd mentioned it in a thread way...,way back but never found a
> solution. And yes, I've made a WinME boot floppy disk. I've got it
> safely tucked away with my JAWS authorization floppy.

 

[Mike M]

George Gee <georgegee@nomaps.com> wrote:

> SSJ04 Mewtwo
>
> Anyone trying to follow this thread will probably find it hard work,
> as you seem to be removing the indents that OE adds to differentiate
> between posters!

Indeed! I also wish that I had been more awake and realised earlier in
the thread the cause of the problem was missing INF files.
--
Mike M

 

[SSJ04 Mewtwo]

Mike M <No_Spam@Corned_Beef.Only> wrote:

Not in this thread, that information could perhaps have led me to the
cause of your problems somewhat quicker than I did. You might also want
to try and establish who deleted all the INF files and why since I am
pretty confident that nothing from Cox would have done so. The reason I
ask is that unless you know who and why there is a pretty good chance the
same might happen again.

I apologize for not mentioning that. The rest of my family wanted to see if
would fix this box by going to XP. In my hast I failed to mention it, so
once again I apologize. If this does happen again I'll know where to find
those .inf files.

Hm, come to think of it I'd stupidly installed Norton 2001 way...,way back.
Fortunately I came to my senses and ditched for AVG.

 

[Mike M]

Thanks,

> Hm, come to think of it I'd stupidly installed Norton 2001 way...,way
> back. Fortunately I came to my senses and ditched for AVG.

I think that may have been when you lost or deleted the INF files. Norton
has/had a nasty bug that created very large numbers of OEM*.INF files of
length zero bytes in the Windows\Inf folder which caused any application
or driver using an INF file to install to lock up. It's possible that you
experienced this problem and in error not only removed the zero byte
OEM*.INF files but perhaps also a number that form part of the Win Me
operating system.

If you decide to move to XP I hope that all goes well. I've been using XP
as my main system since before it was publicly launched in 2001 and have
found it to be very stable and reliable, especially so since SP2 was
released in 2004.
--
Mike Maltby
mike.maltby@gmail.com


SSJ04 Mewtwo <ssj04mewtwo@yahoo.com> wrote:

> I apologize for not mentioning that. The rest of my family wanted to
> see if would fix this box by going to XP. In my hast I failed to
> mention it, so once again I apologize. If this does happen again
> I'll know where to find those .inf files.
>
> Hm, come to think of it I'd stupidly installed Norton 2001 way...,way
> back. Fortunately I came to my senses and ditched for AVG.

 

[webster72n]

"Mike M" <No_Spam@Corned_Beef.Only> wrote in message
news:eEtYTMNOIHA.5524@TK2MSFTNGP05.phx.gbl...
> Thanks,
>
> > Hm, come to think of it I'd stupidly installed Norton 2001 way...,way
> > back. Fortunately I came to my senses and ditched for AVG.
>
> I think that may have been when you lost or deleted the INF files. Norton
> has/had a nasty bug that created very large numbers of OEM*.INF files of
> length zero bytes in the Windows\Inf folder which caused any application
> or driver using an INF file to install to lock up. It's possible that you
> experienced this problem and in error not only removed the zero byte
> OEM*.INF files but perhaps also a number that form part of the Win Me
> operating system.
>
> If you decide to move to XP I hope that all goes well. I've been using XP

that's XP Pro, I presume? <H>.

> as my main system since before it was publicly launched in 2001 and have
> found it to be very stable and reliable, especially so since SP2 was
> released in 2004.
> --
> Mike Maltby
> mike.maltby@gmail.com
>
>
> SSJ04 Mewtwo <ssj04mewtwo@yahoo.com> wrote:
>
> > I apologize for not mentioning that. The rest of my family wanted to
> > see if would fix this box by going to XP. In my hast I failed to
> > mention it, so once again I apologize. If this does happen again
> > I'll know where to find those .inf files.
> >
> > Hm, come to think of it I'd stupidly installed Norton 2001 way...,way
> > back. Fortunately I came to my senses and ditched for AVG.
>