Re: upgrade problem win ME to win 2000


"Pegasus (MVP)" <I.can@xxxxxxx> wrote in message
news:uequsY%231FHA.3000@xxxxxxxxxxxxxxxxxxxxxxx
| The basic thrust of your reply ("You cannot convert from WinME
| to Win2000") is entirely correct. However, your response contains
several
| explicit claims that are incorrect. See below.
|
|
| "Peter_Julian" <pj@xxxxxxxxxxxxxxxxxx> wrote in message
| news:aoH6f.4$ki7.1446@xxxxxxxxxxxxxxxxxxxxxxxx
| >
| > "Fredrik Er" <FredrikEr@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
| > news:D5440C5E-EE25-4E45-B889-F3DD976189C6@xxxxxxxxxxxxxxxx
| > | HI!
| > |
| > | I cant uppgrade with the win 2000 CD from win ME. I upg.DLL file
that
| > has
| > | something to do with win 95 is missing. How can I uppgrade?
Microsoft
| > | troubleshooting saying you must do it clicking winnt32.exe doesnt
| > work.
| > |
| > | Thanks for help.
| >
| > You can't upgrade from a share-level operating system to Window 2000
( a
| > user-level OS ).
| *** Win98 is what you call a "sharel-level OS". A conversion from
Win98 to
| *** Win2000 is supported by Microsoft.

I'ld disagree. A "conversion" implies a migration of settings /
configurations from one version of a given product to another. Win98 has
little, if anything, in common with W2K. One can argue that an NT4 to
W2K conversion is indeed an upgrade because both implement a security
manager with user-level logins. Hence, there is a distinct type of
conversion when one carries out a migration vs and upgrade.

|
| > Besides, WinME was created after Windows 2000. So
| > basicly Windows 2000 isn't even aware that WinME was ever available
(and
| > therefore knows nothing about it).
| >
| > In most cases where an upgrade path is available, because of the
| > resulting bugs and the need to support those bugs, a clean install
is
| > the preferred way to go. The exception is in a wide corporate
deployment
| > within a controlled environment. In your case, consider the result
of
| > upgrading to a 32 bit, unicode OS when you have 16 bit applications
and
| > tools without unicode support still left on the system. Thats the
| > ultimate nightmare.
| >
| > And please, don't respond that "well, it worked for me!". Its
| > physically impossible to carry out that procedure. The Windows 2000
| > installation will not let you. Never, ever.
| *** Just because you state this myth three times in the strongest
| *** possible terms does not turn it into a fact. I tried to convert
| *** a WinME installation to Win2000 a moment ago. I had no
| *** problem with the conversion and I was able to boot up the
| *** "converted" version of Win2000 to the desktop and test
| *** network connectivity (although I don't expect the result to
| *** be of any use).

Thats impossible. Even the installation clearly states that this is so.
The only option allowed is a clean install. Incidentally, because of the
fact that W2K is not dealing with a known migration path (ie: Win98 to
W2K), the result of the clean install is itself faulty! This was
verified with Sysdiff by yours truly. Compare Win98 and WinME to
understand why. WinME uses a seperate user registry file that Win98
doesn't implement. Therefore, the WinME migration to W2K is an illusion.

|
| > The only option available is
| > a clean installation. Additionally, a Windows 2000 installation is
| > capable of formatting a drive in 4K clusters (the default), a
| > requirement for W2K ntfs compression. Converted file systems do not
| > satisfy that requirement.
| *** Again I converted a 12 GByt FAT32 partition to NTFS.
| *** I then set the compression flag. It worked just fine.

Hmm, indeed, converted files do satisfy the requirement, that statement
was wrong. But...
Those are 8K clusters in a typical 12GB FAT32 drive. Converting it
generates an NTFS drive with 512 byte clusters. That is neatly within
the maximum requirement of 4K specified by the manufacturer. In NTFS,
you'll suffer a hefty performance cost due to the tiny cluster size.
Thats related to the oversized MFT table symptoms.

|
| > Perform a clean installation after verifying hardware and software
| > compatibility requirements (or pay a tech to do it for you).
| *** Indeed, this is the only reasonable way to go. Anything
| *** else would result in a flawed system.
|
|


.

Relevant Pages

  • Re: upgrade problem win ME to win 2000
    ... The basic thrust of your reply ("You cannot convert from WinME ... WinME was created after Windows 2000. ... *** problem with the conversion and I was able to boot up the ... > Perform a clean installation after verifying hardware and software ...
    (microsoft.public.win2000.general)
  • New XP install keeping dual boot
    ... 1- WinMe ... 2- WinXP Home Ed. ... I'd like to do a clean install. ... Can I have some help on that as I don't want to lose the dual boot? ...
    (microsoft.public.windowsxp.general)
  • New XP install keeping dual boot
    ... 1- WinMe ... 2- WinXP Home Ed. ... I'd like to do a clean install. ... Can I have some help on that as I don't want to lose the dual boot? ...
    (microsoft.public.windowsxp.basics)
  • Re: ie 6 wont install
    ... > that (It's unlikely that it will work if the normal update mechanism ... WinME is utter crap and has to be the most useless OS ever released. ... WinMe is famous for its memory leaks. ... I suggest an immediate and clean install of XP Pro. ...
    (microsoft.public.windowsupdate)
  • Re: Installing XP clean
    ... >from WinME to XP Home. ... I might as well make it a clean install. ... or do I have to run Partition Commander or PartitionMagic on ... Clean Install Windows XP ...
    (microsoft.public.windowsxp.help_and_support)