you are making this too hard, ke, and you are going to disable his win2000 installation by wiping out the c: drive, since the boot files remain there. Yes, I see the reinstall will restore those, but if he needs help, he will have no computer. Furthermore, depending on how he set it up, there is the possibility his program files folder is still on the C:\drive.
Did u not read my post? :mad: I said, "BACK UP any data that you want saved..." How hard is that? :mad: If you follow this to the "T," the problem will be solved. :mad: You could delete the c:\windows file, but files that reside on the drive will try to make procedural calls to files that existed in the c:\windoze directory, and this would cause more errors.
I don't think that this end user wants more errors, only solutions to this problem. This is how it's done in the real world...this is a real world
solution... :rolleyes:I don't know if this fits into your preconceived MS world, but this is what we do in the real world
. :mad: If you've ever worked in a good IT department
, you'd know this...but then again, what do I know? I'm only a paid professional
that has a degree in computer science. I've only been working with MS crap since NT 3x...What the heck do I know? Oh, btw, if you remove the instance of ME from the boot.ini, you're gonna cause even more problems than the end user needs right now...both installs are on the same drive, residing in a FAT32 partition. If he had his drive partitioned 2 ways, with win2k residing in an NTFS partition, he wouldn't have problems with Win2k, because both installs would exist in different partions
...When he did his install, he did everything by default, which means a FAT32 partition. If he'd installed 2k over ME, ME would no longer exist, because it would've been overwritten...
Edited by ke6ziu, 18 April 2005 - 01:44 PM.