AND ONE MORE THING TO CONSIDER.
I HAVE A WORKING INSTALL ON MY DESKTOP OF VS.NET 2003
I SCANNED THE REGISTRY FOR {D825F1C6-87AB-11D5-A54F-0090278A1BB8}
AND IT DOES NOT EXIST IN MY "WORKING" COPY OF VS.NET 2003. SO
I DON'T KNOW WHY OR WHERE THIS CLSID IS COMING FROM.

I AM WONDERING IF MICROSOFT IS BEGINNING TO LOSE
CONTROL OF THEIR SOFTWARE QUALITY CONTROL.

Microsoft.mshtml,Version="7.0.3300.0",PublicKeyToken="b03f5f7f11d50a3a",Cult
ure="neutral",FileVersion="7.0.3300.0"

OK, Mark, no need to SHOUT.
Have you tried doing a default install (all components)?
There appears to be quite a lot of information available on the web about
Error 1935, have you tried any of the reported workarounds, such as (and I'm
quoting here from articles retrieved by searching groups.google.com)

"This error also indicates file corruption during the file transfer from the
CD to the hard drive.
Try contacting your CD-ROM drive manufacturer for a Firmware update for your
specific CD-ROM and then
execute the install.

Tim Macaulay, Microsoft Visual Studio Setup & Install""I've received some
emails asking about how to fix this problem.  Since
I ended up successfully installing the software, I figured that I
should let people know how I got it working so hopefully others can do
the same.

The version I was attempting to install had been downloaded directly
from Microsoft's MSDN page.  When this install didn't work (several
times), I ended up trying to load it from the actual discs that were
mailed to us (we had misplaced them for a few days, which was why I
initially had to download it).  The installation off of the CDs went
perfectly.  I can only conclude that there must have been some problem
on the download that we hadn't been notified of.

If you're trying to install it from CD, maybe try downloading it
instead.  If you're trying to install the downloaded version, try to
get the CDs.  I don't know why the CD and downloaded versions would be
different, but switching mediums worked for me...""It may caused by the
version conflict of .NET Framework. To work around it,
you may try the following steps:

1. Remove the Framework via Add/Remove Programs in the Control Panel.
Please make sure
2. Install the Framework from the dotNetFramework folder on the CD labeled
"Windows Component Update". If you are installing from a network or local
share, the folder dotNetFramework is located in the folder named "wcu".
3. Install VS.NET again

Two points to notice when remove the .NET Framework:

1. Make sure there is not such a registry key in your registry:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NET Framework\Policy\v1.0

2. Rename the old version of mscoree.dll in %SystemRoot%\System32 if it
exists. You may have to log-off and log-on again to make explorer.exe
release its hold (or just kill and restart explorer.exe)

I hope this helps you.

Best regards,

Lion Shi [MS}
MCSE, MCSD
Microsoft Support Engineer

This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.  2001 Microsoft Corporation. All rights
reserved."It appears that different things work in different circumstances.
There are reports of numerous other successful solutions that I won't quote
here.Hope this helps get you started.

-- Peter [MVP Academic]