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........
[quoted text, click to view] "jkotuby" <jkotuby@snet.net> wrote in message
news:%239OgexbnEHA.324@TK2MSFTNGP11.phx.gbl...
>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.......................
>