win95 install

[skut]

i got a client in the other day who wanted to upgrade from win 3.1 to win95. easy nuff eh? not quite. i ran the upgrade--it went w/ a breeze, just a tad slow. so it goes to reboot and i get a msgsrv32 error...

so i turned it off, booted the system back up and bam same problem. i tried this a couple of times but to no avail. i called him up told him we ran into some problems and asked if it was okay to wipe him out and start a new. so he said okay to that. i deltreed c:\windows and ran an install over it...same problem. so i repartitioned him, formated him and ran the install again. same msgsrv32 problem. ive done this 4 times already and im stuck.
frankly ive never seen this problem before (repeatedly that is) and i was looking for any kind of direction. thanks a lot.

[Damned Angel]

I have had some success getting around this error by removing the soundcard from the machine until all other windows components are setup and working properly.

It would be of great help if you post the exact error message, there are a few posts related to this file in the ms knowledge base

hope this helps

[This message has been edited by Damned Angel (edited June 19, 2000).]

[skut]

about the soundcard...all i had in there was the floppy, hdd, cdrom and video card. the install goes fine w/o any problems...its just after the first reboot (after installing the files onto the hdd) that i get this error. >shrug<

[disturbance]

I had this problem before a long time ago. I believe what i did to fix the problem was that I added more RAM to the computer during the windows installation. After the install, I installed all the applications and then took out the extra RAM. This seemed to work for a couple of the computers at my work, don't know about anyone else.

[CyberTech]

It wouldn't be a Cyrix CPU would it?? :-)

I've seen this problem with certain Cyrix 6x86 processors. Sometimes you need to run the install with a different CPU and then swap back to the Cyrix after it's up and running.

Also, it may be a bad CPU all together, or bad memory. Since Windows 95 addresses memory quite differently to Win 3.1 these hardware failures may not become apparent until you try to run Win 95. Try swapping out CPU and/or RAM.

[skut]

ive already tried the cpu swap. we had a intel 486sx2-50 cpu in there and put a 486 dx. its an old packard bell. it had 4mb of on board ram, 420 mb hdd, a daughter-board in which a proprietary sound card/controller and a panasonic CD rom. what we had tried to do was run a newer ide cd rom as slave to the hdd, loading a generic driver for the cd. the "pre install" (copying the files to the hdd") went fine. the hdd worked as did the temporary cd rom. however once rebooted, the install crapped out. however, i will try adding more RAM for the install and ill get back to you this afternoon. if any other fixes arise please let me know. at this point im about to install DOS and put win 3.1 back in there. at the moment i have his old 486sx2-50 back in there...im so lost and frustrated its not even funny...

once again thanks for the help.

[This message has been edited by skut (edited June 21, 2000).]

[bdunn]

http://www.geocities.com/SiliconValley/Lakes/8774/

Visit this site. Packard Bells have unique problems and this is the best PB resource I've seen yet.

[skut]

nevertheless... i figured id start from scratch, just slightly different. i kept the "temporary replacement" cd rom drive run as slave to the hdd, installed DOS, then 3.11, then the 95 u/g and it magically works. i dont know why it woudlnt take the upgrade the first time or why it wouldnt take 4 clean installs of 95, but starting in DOS worked....go figure...

[Big Blue TECHIE]

turn off rom shadowing

[cricket23]

tell the customer to dial 1 800 DELL for Me!!