I recently added a 2nd HD (8GB) which now contains two copies of WIN95 partition 0-0 and 0-3. The old C: drive is now D: and contains another copy of WIN95 in its single partition 1-0. Three Win 95's in total. I used Partition Commander which incorporates System Commander (personal Edition). I got mixed up in System Commander. It only detailed 2 WIN95 OS's and I booted from what I thought was the original OS on the 0-0 partition, but it later turned out that I booted from the D: (HD 1) partition. After this happened I got some strange errors and it now seems I ahve some for of corruption in some files, particularly Outlook Express data. It has somehow propagated so that whenever I try to compact OE folders in ANY of my three WIN95 environments I get an uncommanded reboot of the system or a system lockup. Any ideas? Is this coincidental and actually a HD problem I wonder? Could booting WIN95 from the second HD have somehow corrupted data on the first HD? I also wonder why in System Commander the 0-0 partition OEM is listed as MSDOS5.0 and not WIN '95. I had a very "bastardized" upgraded version of a VERY early version of WIN 95. It was not OSR2. Is it normal for System Commander to misreport the OEM as MSDOS5.0? In their documentation they reckon this would be the case if the true OS was MS-DOS or Windows NT (Dual Boot). I would very much appreciate a strategy for untangling the mess, and also if anyone has any information about "repairing" a damaged set of Outlook Express 5 files. Thanks very much! Mike

The auto-shutdown may be caused by clash of versions of win95. The file VMM32.vxd would cause thesame symptom. So you have to get the correct version of win95 cd.

This exercise was as a prelude to installing Win 98. I wonder if that would be a cure-all or partial cure-all? Or if this problem might persist? Particulsrly if I attempt an upgrade 95-98 versus a clean install.?

It may be significant that my Win 95 version is: 4.01.0.971a Is this familiar to anyone??? Mike