Solved

General Error during setup "Process Error"

Posted on 1998-04-09
5
163 Views
Last Modified: 2013-12-16
While re-installing Win95 on a Compaq Notebook, I got the following message:
General Install Error
SU99405
updatelnis=processing error
0x195

Have tried installing windows in new directory and in old, and still get this error.  Unit had cross links and invalid directories cleaned recently.  

Any Ideas?  I've only seen this error once before, and it
seemed to correct itself.  Never found the actual cause of
error.

Re-installing Version B.
0
Comment
Question by:rclevlnd
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
5 Comments
 
LVL 1

Accepted Solution

by:
aquar earned 100 total points
ID: 1755436
I think this is the same problem of mine.
I install a win95 system in different FONTS like the original
preinstall win95 system is not the same FONTS which you want to install.
So if you want reinstall the win95 system. There are some method.
First method, use clean dos disk to restart dos system and check virus to sure the HDD is unvirus( the dos check virus is shareware in the www.trend.com web site),then reinstall the win95 system(Always virus will occur the install system to dead).

Second method,with clean dos system start the DOS system and hard start(not soft start(CTRL-ALT-DEL)).Format the HDD and after
it, Use fdisk /mbr to check he MBR with no virus . Reinstall the win95 system.

This two method always can help you to reinstall the system. If not, There are another two hardware problem.
First problem, memory chip bad.(this oftenoccur to the unjapan memory)Or with different memory chip match (Try to slow the memory speed down in the CMOS config).
Second problem, Hardisk bad cluster, The format will find it or use advanced harddisk manger like seagate's DISCWIZARD.

0
 

Author Comment

by:rclevlnd
ID: 1755437
Well, I have already solved the problem, but you get the points for a good diagnosis of
some of the problems.  The best points of which I would like to point out for other who may read this:  1) Bad memory - Not in this case, but very likely.
                       2) Bad Cluster - There was a bad cluster.  I found this by backing up
                           the system and then running Western Digitals WDDIAG on the
                           drive.  Although this was the cause, it was not the solution.
                       3) Memory Speed - Can Cause errors as if there were bad memory. Make                            sure your speed matches the chip speed. (Good one).
                       4) Virus - Relly should be the first thing to check for, but none was found                             in this case.
 
I actually found the solution to the problem on Toshiba's website.  Turns out a few of the .INI files were damaged (corrupt).  I renamed the .INI files to *.INX and re-installed, and everything worked great.  Granted they have to re-install a few applications, but it's better then losing everything.  Alot of the applications worked without a peep.

Toshiba's site said that the cause was a lingering Load= in the win.ini file.  I had none.




0
 
LVL 1

Expert Comment

by:aquar
ID: 1755438
Thanks of your points .
I think a good and a stable system is very imprtant.
I bought 2 hdds in my computer and add memory to 80MB but only with the 133 cpu.
If some question happen to my system , i will try to find out where going wrong. I don't want to die with unreason.
So i think i will reinstall it rather than it will happen someday.
So if it happen to me. I will format it  because i have all driver in the second  hdd.
Thanks again.
0
 
LVL 1

Expert Comment

by:aquar
ID: 1755439
I still have something don't understand.
The .ini files almost are in the c:\windows and
c:\windows\system .
Don't you say you ever reinstall it in another directory rather than c:\windows ?
Why does it happen again?


0
 

Author Comment

by:rclevlnd
ID: 1755440
I backed windows up into a WINBAK directory and erased the windows directory.  For some reason, it was still trying to use the .ini files in the winbak even though I was telling it to install in the C:\WINDOWS folder.

I'm not sure why it was trying to do that.  Renaming the .INI files corrected the problem all the same.

You are welcome for the points.
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Determining the an SCCM package name from the Package ID
This article is a collection of issues that people face from time to time and possible solutions to those issues. I hope you enjoy reading it.
Windows 8 came with a dramatically different user interface known as Metro. Notably missing from that interface was a Start button and Start Menu. Microsoft responded to negative user feedback of the Metro interface, bringing back the Start button a…
The Task Scheduler is a powerful tool that is built into Windows. It allows you to schedule tasks (actions) on a recurring basis, such as hourly, daily, weekly, monthly, at log on, at startup, on idle, etc. This video Micro Tutorial is a brief intro…

734 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question