URGENT! Cannot install VS 2003

[TumurS]

Hi all!
I need to make some changes on my old NET 2003 project and tried
to install VS 2003. The Prerequisites starts ATI south bridge driver
install (I have RADEON XPRESS 200 series built-in video) and it fails
with an error # 0x80040705. I cannot continue VS setup.
Any ideas? Is there a way to avoid this driver installation?

[pvdg42]

"TumurS" <sp********@magicnet.mnwrote in message
news:eE*************@TK2MSFTNGP03.phx.gbl...

Hi all!
I need to make some changes on my old NET 2003 project and tried
to install VS 2003. The Prerequisites starts ATI south bridge driver
install (I have RADEON XPRESS 200 series built-in video) and it fails
with an error # 0x80040705. I cannot continue VS setup.
Any ideas? Is there a way to avoid this driver installation?

Try this:

http://support.microsoft.com/default...b;en-us;290301

[TumurS]

Thank you for response. But I cannot imagine
what to do with this CleanUp utility.
There was no VS2003 / NET1.1 installed
on my machine before. What I have to cleanup?
The NET2.0 (but not VS 2005) framework installed
on my WinXP Pro SP2. Some ATI or Realtek tools
require it. Also there're Norton AntiVirus/SysWorks,
IE7, J2SE Runtime 5, OfficeXP, MS SQL2K server and etc.

Yesterday I downloaded and installed the latest ATI drives/ SouthBridge
/Catalyst utility, but the VS 2003 setup still tries (unsuccessfully) to
install the ATI South Bridge driver.
I removed ATI driver and ran setup in plain VGA mode.
No success!!!
"pvdg42" <pv****@newsgroups.nospamwrote in message
news:ut**************@TK2MSFTNGP02.phx.gbl...

>
"TumurS" <sp********@magicnet.mnwrote in message
news:eE*************@TK2MSFTNGP03.phx.gbl...

>Hi all!
I need to make some changes on my old NET 2003 project and tried
to install VS 2003. The Prerequisites starts ATI south bridge driver
install (I have RADEON XPRESS 200 series built-in video) and it fails
with an error # 0x80040705. I cannot continue VS setup.
Any ideas? Is there a way to avoid this driver installation?

Try this:

http://support.microsoft.com/default...b;en-us;290301

[pvdg42]

"TumurS" <sp********@magicnet.mnwrote in message
news:O6**************@TK2MSFTNGP04.phx.gbl...

Thank you for response. But I cannot imagine
what to do with this CleanUp utility.
There was no VS2003 / NET1.1 installed
on my machine before. What I have to cleanup?
The NET2.0 (but not VS 2005) framework installed
on my WinXP Pro SP2. Some ATI or Realtek tools
require it. Also there're Norton AntiVirus/SysWorks,
IE7, J2SE Runtime 5, OfficeXP, MS SQL2K server and etc.

Yesterday I downloaded and installed the latest ATI drives/ SouthBridge
/Catalyst utility, but the VS 2003 setup still tries (unsuccessfully) to
install the ATI South Bridge driver.
I removed ATI driver and ran setup in plain VGA mode.
No success!!!

It cleans up leftover junk related to the Windows installer that typically
results in the types of symptoms you have.
It's not specific to .NET or VS 2003.

[TumurS]

Thank you!
I found another way to install the VS. I ran the Prerequisites
separately and it installed whatever I needed or not. After
I run the VS setup with no-check option and it worked well.
"pvdg42" <pv****@newsgroups.nospamwrote in message
news:eu*************@TK2MSFTNGP05.phx.gbl...

>
"TumurS" <sp********@magicnet.mnwrote in message
news:O6**************@TK2MSFTNGP04.phx.gbl...

>Thank you for response. But I cannot imagine
what to do with this CleanUp utility.
There was no VS2003 / NET1.1 installed
on my machine before. What I have to cleanup?
The NET2.0 (but not VS 2005) framework installed
on my WinXP Pro SP2. Some ATI or Realtek tools
require it. Also there're Norton AntiVirus/SysWorks,
IE7, J2SE Runtime 5, OfficeXP, MS SQL2K server and etc.

Yesterday I downloaded and installed the latest ATI drives/ SouthBridge
/Catalyst utility, but the VS 2003 setup still tries (unsuccessfully) to
install the ATI South Bridge driver.
I removed ATI driver and ran setup in plain VGA mode.
No success!!!

It cleans up leftover junk related to the Windows installer that typically
results in the types of symptoms you have.
It's not specific to .NET or VS 2003.