Sorry for not understanding before. I guess I'm just adding to your frustration.
"Setup has encountered an error and needs to close" is about as worthless an error message as not giving one at all. I don't
remember back to VS6 setup to recall whether the 16-bit subsystem should even be relevant. I looked back over the thread, and I
don't see any mention of what operating system you're using.
Your symptoms make me believe that your uninstall wasn't thorough enough and that the setup is somehow in a "limbo" state.
Uh? I found the missing DLL that the linker needed, but the linker
still would not run .....so then......(afterwards) I uninstalled VC ver 6.
Ok so far ?...... then I tried to reinstall VC ver 6 but setup baulks and
had to close. Did I get it clear this time ?
So in the meantime I'm looking around on the MS site for messages
like the one I got in relation to VC ver 6 and I find this.
"Setup does not succeed at the Windows NT Virtual DOS Machine
(NTVDM) level as installation is handed off to Acmsetup. This is
caused by a corrupt 16-bit subsystem. "
Man what a nightmare, I just want to get on with writing my code.
Am I going to have to do a full restore ?
"Scot T Brennecke" <ScotB@Spamhater.MVPs.org> wrote in message
news:OD2LHR0AKHA.5068@TK2MSFTNGP03.phx.gbl...
RB wrote:
Well I tried finding the DLL (which I did ) and put it in all
directories that
are on the setup. The linker still would not run. That was strange.
So then
I uninstalled my entire Visual C Pro Ver. 6.x and then rebooted and
tried
to install it back. At the very start of the install I get a message
stating,
"Setup has encountered an error and needs to close " When asked, I
chose to send the data to Microsoft since I have a legal copy. What the
heck is going on ? I've had this package since 1998 ?
I'm not sure what you mean when you say you "found" the DLL, and put
it into all the directories that are on the setup. You shouldn't have
to muck around with the setup of VC6 at all. If you successfully
uninstalled it, and you have the legal installation for it, you should
be able to reinstall it without having to "find" and copy the DLL into
anywhere. My guess is that you "found" a version of the DLL that
isn't compatible, and put it somewhere it doesn't belong.
If your reasons for staying with VC6 are financial limitations, I
understand and empathize. However, I cannot fathom any other
justification for staying with that product. If you have the means to
upgrade to VS2008 (or VS2010 next year), I strongly recommend it.