SUWIN/WINSETUP errors

I installed a new floppy drive. The first drive was not recognized. I installed a second floppy drive. Scandisk said two copies of FAT were mismatched. I could not get out of this error message. After reformatting my c: drive and booting up with a startup disk, Windows 95 will not install. During the initial installation of temporary files for setup, I get this:

SUWIN caused a Segment Load Failure in module 0006:0E0C.
WINSETUP caused a Segment Load Failure in module WINSETUP.BIN at 0001:2619
WINSETUP caused a General Protection Fault in module USER.EXE at 0001:40B6

In the dos window, I get:

Standard Mode: invalid DPMI return from 06DF:01B2

What does all this mean and what do I have to do to fix it?

Thank you for all of your help.

Smorg
smorgAsked:
Who is Participating?
 
crobinConnect With a Mentor Commented:
SUWIN errors, especially in user.exe at the point where setup launches windows (the blue and black screen with peripherals on it) are almost always (in my experience: over 90% of the time) caused by faulty RAM or motherboard settings that are incorrect for the RAM being used.

Bad fault in MS_DOS extender is also almost exclusively caused by bad RAM.

On top of that, mismatched FATs on a drive that has previously functioned well can easily be caused by faulty RAM.

Since you describe the problem starting with the replacement of a floppy drive, it is possible that the BIOS got a bit of static or there was a faulty connection to the hard drive when you booted up the first time. Either of these will start the domino effect you described.

Remember that the setup process of Windows is FAR more taxing to a system than almost any other operations you will use the computer for. If a system has a hardware fault or misconfiguration it is likely to show up under setup but might otherwise go undetected.

In your circumstance, I would: 1) Triple check all jumper and soft-settings on the motherboard. 2) Replace the RAM. 3) Re-flash the BIOS. All of these things should be done ONLY if you are comfortable doing them.

Good luck.

0
 
smorgAuthor Commented:
The computer is a Cyrix 6x86 120 with 32MB. The primary drive is a Maxtor 6.4. I'm installing from a slave WD 1.2. The floppy drives were all Mitsumi's. It has a ProComm Aceex 33.6K internal modem, ATI Xpert@work 4MB video card. If you need any more information to answer the question, don't hesitate to let me know :)
0
 
MrbreezeCommented:
You boot up with a startup disk. Where did you get the disk, did you make it with the version of Win you have. Most of the error you are getting I have only seen when you try to install DOS 5.0 after you have installed 6.x or with Win 3.1. You said you are trying to install from a hard drive. Do you have Win95 on a CD or floppies, can you access your CD player. Did you FDISK the drive before the format or just fprmat the drive
                         Mrbreeze
0
Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
smorgAuthor Commented:
The startup disk I made with Win95 didn't work, even though a directory listing showed system files on the boot disk. The config.sys file showed 0 bytes. A neighbor gave me their Win98 SE boot disk. I did NOT copy the system files to the hard drive, but it allowed me to get as far as the Windows setup screen before I started getting the error messages as stated.

I didn't use FDISK; the first time, I used format c: /s. After the trouble started, when I used the Win98 boot disk, I formatted again with format c:

The neighbor builds computers for fun, but they're currently in another state and we were trying to walk me through this on the phone. Obviously, they were very limited in what they could tell me! We tried to start with and without CD drivers; with CD drivers didn't work (Windows didn't recognize the drivers used) and without drivers. Without the CD loaded, I had no choice but to go to the CAB files on my secondary drive. Could I have a boot memory virus or just bad memory? It is a generic computer bought in 1996. I've added to it since then, hence, the name hard drives and video card.

Actually, I started having some serious problems after I uninstalled IE5.
0
 
hewittgCommented:
This will explain what a segment load failure is.
http://support.microsoft.com/support/kb/articles/Q102/6/40.asp?LNG=ENG&SA=ALLKB
This will address the DMPI:

Standard Mode Messages
If you get any of the following error messages, remove
any memory managers (such as EMM386.exe, QEMM, or 386Max)
from your Config.sys file, and then run Setup again.

      Standard Mode: Invalid DPMI return.
      Standard Mode: Fault in MS-DOS Extender.
      Standard Mode: Bad Fault in MS-DOS Extender.
      Standard Mode: Unknown stack in fault dispatcher.
      Standard Mode: Stack Overflow.

NOTE: If you still have problems, add EMM386.EXE back
into your Config.sys file and exclude all ranges. For
example,

      device=c:\windows\emm386.exe x=A000-FFFF

If you encounter these messages or if your computer stops
responding during Setup, turn on double-buffering in
SmartDrive. Several SCSI hard drives and some ESDI drives
require double-buffering.

To turn on double buffering, add the following line to
the beginning of your Config.sys file:

      device=c:\windows\smartdrv.exe /double_buffer+

where "c:\windows" is the path to your Windows directory.




0
 
smorgAuthor Commented:
I've never used this site before, but I want to thank everyone who tried to answer my question. I went to a Canadian tech site (ask-a-tech.org) and they had a very short list of FAQ's. One of them provided a zip file with all of the system files you needed to boot up. It worked. I just finished reinstalling Win95.

I would still like to know what went wrong. I keep checking back here and searching.

Smorg
0
 
Adam LeinssCommented:
Not sure what happened, by the sound of the error messages it really sounded like a hardware problem to me.  My guess is you had something in either the AUTOEXEC.BAT or CONFIG.SYS that didn't agree with SETUP.EXE and thus the fault.  What exactly that would be, however, I wouldn't know.  The only way to know would be to copy back your startup files and REM each line and try to re-run setup til the errors ceased.
0
 
smorgAuthor Commented:
I've been working with my brother (an IT manager) and he's not sure what is wrong either. The reinstallation of Win95 failed and it took me two days to get the right set of startup files in order to reformat. I had to do it without the /s switch. I agree that it's probably a hardware message, and will take it in to the shop for memory testing, since scandisk keeps returning a clean scan. It's a mini tower, so space is really tight with all of the cables and ribbons; I'd rather not swap out the memory myself (at least until I know what I'm doing!), and will have the techs reinstall Win95 for me. I'll seriously look at Linux in the future :)

Thanks for your suggestions and help!
0
 
smorgAuthor Commented:
Thanks, Crobin!

I thought it might be faulty RAM, but I was finally able to get a startup disk and install Win95 on my secondary drive. When I got Windows going, I did a thorough scandisk of my C: drive and now I have 20 removable drives (F-Z)! Obviously, something's going on with the hardware. I will go into the case and get the connections again. I do feel comfortable going into the system, but only when I have clear instructions on what I am doing. That's why not getting a specific answer to my error messages was driving me crazy :)

This is a great site. I've been all over the 'net looking for answers and it really has the most thorough archive to research I've seen; even better than MS knowledge base.

Keep up the good work here.
0
All Courses

From novice to tech pro — start learning today.