Background: Upgrading Visual Studio Enterprise Architect from 2002 to 2003;
SQL Server 2000 Developer Edition Installed; Previous Framework Install for
1.0 created MSDE instance \NetSDK.  Visual Studio Enterprise Architect 2003
is now installed and working.

To run the framework 1.1 samples requires a named instance of Microsoft SQL
Server 2000 Desktop Engine (MSDE).  I downloaded SQL2kDeskSP3.exe from
Microsoft.  When I ran the install it gave an error message about an invalid
instance name; I assume for the default install name of \NetSDK

I uninstalled both the SQLSERVER and the FRAMEWORK and then reinstalled
them.  Then I re-ran the SQL2KDeskSP3 install.  Again I got the same invalid
instance name.  In the program files for SQL Server there are directories
for each of the instances I have tried but the SQL Server Services Manager
doesn't recognize any of them.

My goal is to get the Framework 1.1 Samples working with a SQL SERVER
database.  I see four options:

1) install the new data load scripts into my base SQL Server and somehow
point the .NET Framework samples to use this instead of the \NetSDK
instance.  I think I have seen documentation for installing the files but I
don't know how to point the .Net framework samples to look for something
other than \NetSDK.

2) sucessfully create the \NetSDK instance by eliminating the cause of the
invalid instance name error; perhaps there are registry entries and
directories that need to be deleted

3) install a different instance name and rename it to the invalid instance
name \NetSDK; I don't know how to do this.

4) completely remove every reference to SQL Server and the .Net Framework
and start over; when all traces of SQL SERVER are gone from my machine,
should I install the MSDE first, and then SQL SERVER, or the SQL SERVER
first followed by the MSDE?

I also wonder if there is some kind of security catch-22 involved.  I know
Microsoft has increased security over the last few years.  I'm installing
the MSDE as the administrator of the machine but maybe the administrator is
not as powerful as he used to be without increasing his power.  I don't
know.

I also see a reference to the NetSDK on my other machine from the SQLSERVER
Services Manager but I no longer seem to be able to get rid of the
reference. I thought having a DIFFERENTMACHINE/NetSDK might be confusing the
install. I thought if I registered the SQL Server \NetSDK on the other
machine in Enterprise Manager  that when I unregistered it, it might remove
all references to it. But I don't seem to be able to do this anymore because
the SQL SERVER is not a "Trusted Connection" or something like that.

I have installed the MSDE several times over the past two years and it was
always a straight forward process. I don't know what is different now.

Thank you for your help.

Brian