Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Visual Studio.NET / Setup / March 2005

Tip: Looking for answers? Try searching our database.

Problem Installing VS .Net 2003 Trial on XP SP2

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
jkotuby - 18 Sep 2004 21:16 GMT
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.

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.