In this maladroitly titled thread: Video problem with my new Windoews ME system I asked for some advice on a problem with my new Windows ME system. I came to the conclusion that I needed to re-install the OS, so I did, booting from the cd-rom and going to Windows Setup. So what is the problem now?
1 First attempt, the preliminary scandisk found some problems with the FAT, and corrected it. Rest of the install went ok until, after the reboot, the system hung on the installing hardware drivers part
2 Went to setup->install again, this time scandisk found another disk error, the drive reporting more space than it had or some such, again it was corrected, again the install went ok until after reboot, then it hung.
3 on the third and fourth attempts I got this error message during install:
Haven’t got a clue what that means.
4 On the fifth try, the scandisk found an error it couldn’t fix, something to do with some file names being too long.
So…I suspect I have a defective hard disk here. Anyone agree, or disagree? Can I perhaps salvage this disk by reformating it clean. If so, can I do that from a Win Me cd-rom boot-up?
SU-99407
Problem: A SetUp on a freshly formatted HDD hangs right after the ‘copying files’ with the Error Message SU99407
Probable Cause: Make sure that the Hard Disk is formatted with the /S switch which will install the necessary files to boot the machine.
the /s switch in formatting is the ‘System’ switch. It copies the command interpreter, autoexec.bat, config.sys, msdos.sys, io.sys to your C: drive. When installing a new OS you generally don’t want to have the HDD “sys’d” because the new OS (Microsoft products, mostly) assume that there’s already an Operating System installed and has a few kittens. M suggestion in this situation would be to start with an fdisk (type that at the command promt and select ‘Delete Partition’: no. 3) to start over from scratch. Next, I’d get meself a copy of 98SE, 2000, or XP and completely IGNORE Windows ME. It truly is an abortion that made it to store shelves.
Not the cute and cuddly kind of kittens, I assume, but…during the multiple attempts I made to re-install Windows ME, which I related in the OP, the new Microsoft OS I was trying to install did in fact assume that an OS already installed. Assumed it because it was true. The only complication this seemed to produce was that it asked me if I wanted to backup the old OS, I said no, and it went from there.
Whoa!!! We’re traveling at full gallop down the wrong road here, folks!
Until Me, the Windows series had been getting easier to install with each version issued; for whatever reasons, Gates & Co. decided to toss a few kinks into Me that can be confusing and very misleading. I’m no supereducated technogeek, but I have been through a number of Me installations and I’ve seen and solved the problems the OP describes.
First of all, Weird_Al, your hard drive is probably physically OK; difficulties of this sort are software-based about 99.9% of the time, in my experience. However, if I were in your position, I’d thoroughly “clean” the hard drive using a “zero-fill” utility. Performing a “zero-fill” restores your hard drive to the state it was in when it left the factory, completely erasing everything, including your corrupted boot sector. Check with the drive’s manufacturer – many drive makers used to offer a brand-specific utility for free. If your drive’s manufacturer doesn’t offer one, you can get a universal version from http://www.ontrack.com. Look under the “Personal” tab for “DataEraser.”
Once the “zero-fill” is done, boot your system using an Me-specific boot disk, being sure to specify CD-ROM support. Then partition and format the hard drive using the utilities on the Me CD-ROM. And forget trying to format the hard drive as a system disk with the “/s” switch – you’ll find that what’s left of DOS in the Me incarnation doesn’t even support it. Instead, let Me do the system formatting as it installs – it’s completely painless.
I have to note that much of this advice depends on your having a complete version of Me, and not the notoriously shitty “Upgrade” version.
TBone2: So I shouldn’t use the /s switch? Now I’ve gotten conflicting advice. Damn. Will a “zero fill” utility work under a Win ME cd-rom bootup? Can I just type the command from the DOS prompt?
FTR I do have the complete version, not an upgrade.
Depite my prior recommendation for a generic 98/ME install procedure using the /s switch with format I think Tbone is correct. In recalling various ME and 98 installs over the past 6 months the ME boot disk install procedure is slighty different from Win98 and ME will apply the system files to the format disk automatically so the /s switch is no longer required as it would be in a 98 install.
I guess I could have been a bit more specific about a couple things…
A “zero-fill” utility, at least the OnTrack variety, has to be run from its own bootable disk; mine’s on a bootable floppy. The software is downloadable as an .exe file that will run from Windows to create its own bootable floppy. The bootable floppy must be run from a cold boot, and will not run under either Windows or MS-DOS. (OnTrack’s uses Caldera’s DR-DOS, IIRC.) In other words, once you’ve used the download to create a bootable floppy, shut down your computer completely, insert the “zero-fill” disk in the floppy drive, turn on the power, and follow instructions.
Once the “zero-fill” has blanked your hard drive, you can proceed as if you just bought the drive new – partition using Microsoft’s fdisk (found on the bootable floppy that came with Me) and format using the utility you’ll find (I think) in a DOS folder on the Me CD-ROM. You misunderstood about the /s switch. What I meant to say, and what you’ll find to be so, is that you can’t use it any more, since the version of MS-DOS mated with Me doesn’t allow or support it.
I hope this is a little more clear. Again, best of luck!
Ok, I decided to wait until I heard back from tech support before doing anything. They advised me to simply reformat the drive and again re-install, so this is what I tried, and here is what happened:
1 Reformatted the C: drive. Rebooted, did Windows setup from the CD-Rom. Install went ok until the reboot, on reboot got an error message: “msgsrv32 has caused an error in setupx.dll msgsrv will now close”. After this system is hung.
2 On rebooting, got a scandisk because of the improper shutdown almost immediately followed by a Blue Screen of Death error: “File Name VWin32(05)x00000FA error : OE : 0028 : c0299dc”. System is again hung.
3 Tried Re-installing without reformatting, the initial scandisk reported an error in the amount of free space being reported, fixed it. Install again went ok until reboot part, after which I got the same problem as number 1.
4 Reformatted again, re-installed again, when I got to the reboot part, instead of booting from the hard drive, booted to dos with the CD-Rom, did a scandisk, everything clean. Rebooted again from hard drive, setup began the install drivers part, then got this error message: “shell32.dll file is linked to missing export shlwapi.dll:PathQumteSpacesA”. After this system is hung.
TBone2: I didn’t do the “zero fill” thing. That may be my next step, depending on how tech support responds when I email them. I am pessimistic about it though.
BTW, you were right about the “/s” switch, Windows ME does not support it.
Install errors on a more or less bare system of the type you are describing are usually indicative of some fundamental hardware malfunction or conflict. You need to return the unit and get a new one. Your current one has a serious hardware bellyache and replacing it now would be the most efficient thing to do. I don’t think I’d screw around with it any more.
I mentioned before, I think the hard drive is defective. I’m hoping if I have to get something replaced it will just be that. Can you think of anything else it might be?
Perhaps a cmos setup item? You see, they often have all sorts of boot sector protection options in the cmos that you must turn off to put on new OS. I would see if my bios has a default setting or a ‘safe’ setting & use that & see if that works. be sure the HD listed in the cmos is the same you have.