XP Pro (New Install) [VS6 Setup Needs to Close]
news.microsoft.com
setup has encountered a problem and needs to close. We are sorry for the
inconvenience.
AppName: vs60wiz.exe AppVer: 6.0.0.8167 ModName: vs60wiz.exe
ModVer: 6.0.0.8167 Offset: 00008871
Ideas, suggestions - or just a plain old good fix, please!
Daniel
Tom Garvin
Windows XP + SP1 on Dell Workstation 450 (dual processors, and sometimes
that's significant)
"news.microsoft.com" <drbo...@existinglight.net> wrote in message
news:OKsJXHyzCHA.2736@TK2MSFTNGP09...
Daniel Bohner
SP1? I did have it installed on an older XP box (when XP first came out)...
haven't tried to install it since...
kum-on M$, wake up - we are dying out here!
Daniel
"Tom Garvin" <tom.g...@verizon.net> wrote in message
news:e3MZ3vyzCHA.2232@TK2MSFTNGP11...
Daniel Bohner
from Tim Macaulay)... got me to the first Installation Wizard screen - then
it goes doa.... again...
AppName: vs60wiz.exe AppVer: 6.0.0.8167 ModName: ntdll.dll
ModVer: 5.1.2600.1106 Offset: 00008cf1
Note, now I get the modname: ntdll.dll error (I get past the VS60wiz.exe
modname)
db
"news.microsoft.com" <drbo...@existinglight.net> wrote in message
news:OKsJXHyzCHA.2736@TK2MSFTNGP09...
Daniel Bohner
gone bad...
Renaming the perf*.dat (s) got me past the first error.
running: d:\SETUP\ACMSETUP.EXE /T D:\SETUP\vS98ENT.STF /S D:\ /n "" /o ""
/k "0000000000" /b1 gets me past the ntdll.dll issue - but, now I get a
setup error that requires me to run the setup wizard.
So, how can I run the installation wizard? And so many folks call it
aohell... any nicknames for this process?
db
"Tom Garvin" <tom.g...@verizon.net> wrote in message
news:e3MZ3vyzCHA.2232@TK2MSFTNGP11...
Daniel Bohner
Thanks to ABBIE...
From: Abbie Fritz (Ab...@nospam.com)
Subject: RE: Install error
View: Complete Thread (11 articles)
Original Format
Newsgroups: microsoft.public.vstudio.setup
Date: 2001-06-19 20:52:23 PST
Yep, I was hoping not to have to go through all of this though :-)
Okay, you can bypass setup.exe completely, but it takes a little work.
Normally acmsetup.exe is used in silent installs, but it can also be used
to bypass setup.exe and the normal handoff to acmsetup.exe which passes
through the 16-bit NTVDM. Please read through the following and let me
know if you have any questions.
Creating the STF
-------------------------
Use Acost.exe from the Enterprise edition of Visual Studio to make product
selection choices and save those choices to VS98Ent.stf. Be aware that if
you are running this from the CD, you will have to save the modified
VS98Ent.stf to your local drive, and put the correct path to it in the
command line later. See Article Q195828 at
http://support.microsoft.com/support/kb/articles/q195/8/28.asp for
instruction on using Acost.
Command Line Switches
-------------------------------------
D:\setup\acmsetup.exe /q# /t <drive letter and folder location of modified
STF file> /s <location of source> /n "" /o "" /k "<CD key, include the
quotes>" /b#
Abbreviated list of flag functions:
/b #, Suppress the dialog box for choosing installation type of
preselecting one of the large buttons:
/b1 represents first button,
/b2 the second . . .
/k "CD Key", enters and validates the 10-digit key (enter the number
without dashes. Quotes are required)
/n ??, Setup will use the Windows registry Copy Disincentive name if it
exists; otherwise, Setup will prompt the user for the name.
/n "name", Specifies the user name: Windows registry Copy Disincentive
name if it exists; otherwise, Setup will use name supplied here (quotes are
required and there is a space between the 'n' and the first quote).
/o ??, Setup will use the Windows registry Copy Disincentive organization
name if it exists; otherwise, Setup will prompt the user for the name.
/o "name", Specifies the organization name: Windows registry Copy
Disincentive organization name if it exists; otherwise, Setup will use
organization name supplied here (quotes are required and there is a space
between the 'o' and the first quote).
/q #, Quiet Mode: performs a batch mode installation with no user
interaction.
If present, option can be 0, 1, or t:
/q or q0 suppresses all dialog boxes except the exit dialog box;
/q1 suppresses all dialog boxes, including the exit,
/qt suppresses all the UI, including the blue background and copy
gauge.
/s srcdir, Specifies location of source files, used by bootstrapper.
Quotes are required if there are spaces in the path. If you are installing
from the CD, this is generally not the case. For example if your CD-ROM is
drive letter D, the switch would be: /s D:\
/t tablefile, Specifies the STF filename: the default is <base>.stf, where
<base> is the filename of the Setup executable (for example., Setup.stf is
the default file for Setup.exe). This also requires the full path, in
quotes if there are spaces. For example: /t "C:\Documents and
Settings\Administrator\Local Settings\Temp\VS98Ent.stf"
The end result might look something like this:
D:\setup\acmsetup.exe /q /t C:\VS98Ent.stf /s D:\ /n "Jyotsna" /o "None" /k
"0123456789" /b1
Installation Wizard Error
-----------------------------------
If installation fails with "You must first run the Installation Wizard
before running this setup." Cut and Paste the following into a registry
import
file. (a registry import file is nothing more than a text file with a .reg
extension) To import the registry changes, double-click the .reg file or
run from a command prompt. This will work for Windows 2000.
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\6.0]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\6.0\Setup]
"VsCommonDir"="C:\\Program Files\\Microsoft Visual Studio\\Common"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\6.0\Setup\Visual Studio
98]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\6.0\Setup\Visual Studio
98\SetupWizard]
"aspo"=dword:38395356
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\6.0\Setup\Visual Studio
98\SetupWizard-1033-ENT]
"heuristics"=hex:00,00,00,00,00,00,00,00
Let me know if this works!
Abbie
Tony Pacheco [MSFT]
Are you still having trouble with VS6 Setup on Windows XP SP1?
Thanks,
Tony Pacheco [MSFT]
Program Manager
Visual Studio Update
Michael Asherman
I'm experiencing the same problem as Daniel described. Attempting to
install Visual Studio 6.0 on a brand new Dell Inspiron 8500 notebook running
Windows XP SP1, it fails immediately with "setup has encountered a problem
and needs to close". The Application Event log indicates module is
vs60wiz.exe, version 6.0.0.8167, fault address 0x00008831, Event ID = 1000.
I think I've exhausted the "easy" remedies, so I hope you can help me. In
particular, perhaps you could shed some light on the patch that Tim Macaulay
mentioned in
http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&th=3af5395ba849538. Do
you have any idea of the likelihood that this patch would relevant, or can
you give us any addition info about it? How should I contact Microsoft
Product Support to obtain it?
People have reported mixed results with
http://support.microsoft.com/support/kb/articles/q192/7/31.asp, so I'm not
eager to embark on that approach if there's an easier, more promising
solution. If the aforementioned patch avoids the need for so many manual
registry edits (under about 20 separate Performance keys), I'd certainly
prefer to have the patch. I will also be immediately upgrading to VS6 SP5,
if that has any bearing.
Daniel seemed to be getting somewhere with a silent installation as
described in http://support.microsoft.com/support/kb/articles/q195/8/28.asp,
but I'm not sure if this applies to my case (I've got VS6 Pro, not
Enterprise), and I just don't know if this would be the best solution.
It seems that quite a few people have run into very similar difficulties
with installing VS6 on XP, usually without any clear resolution of the
thread. That makes it tough to know how best to proceed. I'll do my part
by making sure to post how I ultimately resolve this problem. If you can
help, esp. as to details about the patch, it would be very much appreciated!
TIA
Mike Asherman
m...@ideaxchg.com
"Tony Pacheco [MSFT]" <ton...@microsoft.com> wrote in message
news:Hd$NibjSD...@cpmsftngxa06.phx.gbl...
Michael Asherman
Professional Edition + SP5 under XP SP1, with guidance from Microsoft
Product Support:
After loading the VS6 CD and exiting from the error dialog ("setup has
encountered a problem and needs to close"), I instead ran the following
command line to launch the ACMSETUP directly:
D:\SETUP\ACMSETUP.EXE /T VS98Pro.STF /S D:\ /n "" /o "" /k "PRODUCTKEYHERE"
/b 1
where my CD drive is D:, and I substituted my VS6 CD Key (without hyphen)
for PRODUCTKEYHERE (keeping the surrounding quotes). This launched the
Visual Studio 6 setup, but soon failed with the catch-22: "You must first
run the Installation Wizard before running this setup", so that attempt had
to be aborted.
The remedy for this second problem was to import a Microsoft-provided .REG
file (182 KB), which added a bunch of entries under the registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\6.0. After running this
registry update (i.e. by double-clicking on the .REG file), I was able to
repeat the preceding ACMESETUP command line and successfully perform a full
installation of VS6. There were no further complications when I then
applied the SP5 upgrade.
My understanding is the the MS-provided registry file simply consisted of an
export of this registry branch from another machine on which VS6 had been
successfully installed, and that any system-dependent entries would be
properly overwritten during my own installation. I.e. it just served to
fool the setup logic into believing that the Installation Wizard had been
run. One minor consequence of this trick was that it bypassed the usual
second phase of the setup, which normally offers to install Other Client
Tools, InstallShield, Back Office, etc. I presume that those optional
components could have been installed separately, by explicitly running their
setups from VS6 CD #2, but I didn't actually try this.
Many thanks to Will Buffington at Microsoft, without whose superb assistance
I'd have wasted a lot more time barking up the wrong tree. Will mentioned
that Microsoft's policy is to provide indefinite free support in matters of
installing and uninstalling MS products (call 800 936-5800 for Visual
Studio), and he has also taken steps to update some of the confusing KB
articles related to this particular issue.
I hope this may be helpful to anyone else who runs into similar problems
installing VS6 under XP.
Mike
Michael Asherman <m...@ideaxchg.com> wrote in message
news:#p1xG#0SDHA...@tk2msftngp13.phx.gbl...
Victor
You mentioned that you imported a Microsoft .REG file to fix this
problem - where do you get this .REG file from?
thanks.
Michael Asherman
I received the .REG file via email from MS Product Support. I would have
attached it to my posting, but at 182 KB, this might not be considered good
newsgroup etiquette. You should have no difficulty getting free help by
calling MS Support, or if you have another machine with VS6 successfully
installed, I believe you can simply export the registry branch of interest
from that (i.e. everything under the key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\6.0). It would be nice
if MS were to make this information more freely and easily available, and I
hope we'll eventually see a response from someone at Microsoft about it.
Mike
"Victor" <victori...@hotmail.com> wrote in message
news:474c316f.03072...@posting.google.com...