Setup.ini for VS.NET Architect

Hi. Very late last night, I was messing around with the setup.ini trying to get the install to work with win server 03. Having decided to revert back to Win2k, I can't get it installed. Now, when I run setup, I get sent to the pre-requisites link. When I click that, the entire installation stops. Here's the line I edited from setup.ini


This is a copy from work that they no longer seem to have (the files are on my HD) , so I'm unable to look at the orginal file. Here's the complete top part plus a few of the key values:

Name=Visual Studio .NET
ProdName=Visual Studio .NET Enterprise Architect - English



Param=/mode=client /locale=1033 /vsui=1





Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

You are trying to install VS .NET on Windows Server 2003? Try inserting the Prerequisite cd, browse it and install the required components individually and then run the setup. BTW: What is the function of this ini file?

Best, Nauman.
dprasadAuthor Commented:
well no, now I'm trying to install it onto windows 2000. I dont have access to the CDs right now..I've tried to install the pre-reqs, but it still takes me to that screen. I think this file just sets the base directory for the installation, it was working fine before i changed that filname value under [baseline].

I can bypass the pre-reqs completely by running setup on the command line using the /NO_BSLN_CHECK switch as explained here:

in which case the installation stops with no message of any kind, making me think it has to be a problem with the value i put in the setup.ini..since this never happened before
hmmm....See if you have any of the Visual Studio .NET 2003 folder in program files. If so, delete them and try running the setup. If no luck here, make a new windows user with admin priviliges and try running the setup by logging in using that user account.

Best, Nauman.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
dprasadAuthor Commented:
I got it going, thanks.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.