I successfully installed the VS .NET 2003 Pro Trial from the Action Pak CD
on an XP machine at work that had SP1 installed. Trying the same install at
home so I could learn in my "spare time" results in problems.
The machine at home is a clean install of Win XP with SP2, IIS with
Frontpage Extensions and .NET Framework 1.1. Upon starting setup I get a
message that the "wrong versions" of prerequisites are installed. I believe
I am running MDAC 2.8. (FullInstallVer in the Registry says 2.81). My guess
is that all the prerequisite versions are actually newer than what setup
expects to find.
When I try to run the Step 1 to install prerequisites I get an InstallShield
error screen that begins with:
Common Command Line Parameters
/L Lanquage ID
/S Hide initialization dialog...etc.
When I click OK, the setup stops completely.
None of this happened on the SP1 machine at work.
Any ideas?
Thanks.......................
jkotuby - 19 Sep 2004 16:24 GMT
I looked further into the documentation and there was no mention of the
InstallShield parameter prompt. So I ran each of the PreRequisite programs
separately as suggested.
I tried starting the main setup.exe and it was at Step 2 (indicating that my
machine had passed the PreReq test). However clicking on the Step 2 link
again produced the same InstallShield parameter prompt.
I then ran the setup from the command line as suggested: n:\setup\Setup.exe
/NO_BSLN_CHECK
and the setup ran to completion. I am still curious about the InstallShield
parameter prompt and wonder if that will affect the operation of VS .NET.
If anyone has an answer for that mysterious prompt, please reply.
Thanks........
>I successfully installed the VS .NET 2003 Pro Trial from the Action Pak CD
>on an XP machine at work that had SP1 installed. Trying the same install at
[quoted text clipped - 19 lines]
> Any ideas?
> Thanks.......................
David McFarren - 24 Mar 2005 16:50 GMT
I'm having this exact problem installing VS .NET 2003 on my XP Pro SP2
machine. I installed it from the MSDN DVD without problem on my machine at
work (also XP Pro SP2) but when I try to install it here at home I get the
InstallShield Command Line Parameters message as soon as I start the Visual
Studio .NET Prerequisites. Did you figure out why this happens? Did you
figure out how to get around it? Please help.
Thanks,
Dave McFarren
David McFarren - 24 Mar 2005 18:20 GMT
I've now run all the prequisite programs manually (without incident) but I
still get the Command Line Parameters error when I try to install VS. I
tried using the /NO_BSLN_CHECK switch from the command prompt but I still
get the error. HELP! Could this be a permissions thing? I've run into
problems before where XP doesn't properly apply registry permissions to the
Administrators group, only to the Administrator login.