.net – Install .NET Framework 2.0 on Embedded XP (Win XPE)

netqfe

I'm trying to install the .Net framework version 2.0 on embedded Windows XP SP2 (aka XPE).

I'm using the XPE specific version of the installer from Microsoft:

http://www.microsoft.com/downloads/details.aspx?familyid=c4837dad-5719-4b63-8752-cb0a65802329&displaylang=en

When the installation starts it fails with the following error:

QFE Installer — Error
Cannot connect to the database – please check the database

How can I get .Net 2.0 installed on SPE?

Best Answer

Okay, so you're running the installer that is updating your XPE development environment, right? Or are you attempting to run that on a device before you seal it?

You need to run that installer on the workstation that has the XPE dev environment (and database) installed. The installer is looking for a specific database on a specific instance of Sql Server, so if you have (or somebody else has) changed it, you'll need to read up on how to specify the connection string to use with the installer.

In addition, it's probably trying to connect using your windows account credentials. Make sure you are able to log on to Sql Server, open the DB with the component definitions, and add records to it. Alternatively, if you can specify the connection string you can set a Sql login username and password to use.

Profiler is a great tool for troubleshooting the two issues described above.

Once you have the components installed, you'll have to add them to your image, check your dependencies and then build it.

If you're trying to just install .NET 2.0 on a machine directly (before you reseal it), you will need the packages for Windows Installer on the machine first. There might be some other dependencies; I haven't done it in a long time so I can't remember.

The best way to troubleshoot dependencies on an XPE installation is to put ProcessMonitor from Sysinternals on it. As you run the installer, you'll see where it attempts to find stuff and fails. Take that information back to your XPE IDE and search your components for those files. You then have to add the packages containing those files to your image and try again. Its an arduous process sometimes..,.

Related Solutions

R – the .Net Client Profile PREVIEW

It does look like the title is in error, because it says RTM further down on that page.

HOWEVER, a new version of 3.5 SP1 (known as 3.5 SP1 GDR) is about to be released any day now, to fix regressions which were in SP1. You might want to wait for that before a big deployment.

.net – Difference between decimal, float and double in .NET

float and double are floating binary point types. In other words, they represent a number like this:

10001.10010110011

The binary number and the location of the binary point are both encoded within the value.

decimal is a floating decimal point type. In other words, they represent a number like this:

12345.65789

Again, the number and the location of the decimal point are both encoded within the value – that's what makes decimal still a floating point type instead of a fixed point type.

The important thing to note is that humans are used to representing non-integers in a decimal form, and expect exact results in decimal representations; not all decimal numbers are exactly representable in binary floating point – 0.1, for example – so if you use a binary floating point value you'll actually get an approximation to 0.1. You'll still get approximations when using a floating decimal point as well – the result of dividing 1 by 3 can't be exactly represented, for example.

As for what to use when:

For values which are "naturally exact decimals" it's good to use decimal. This is usually suitable for any concepts invented by humans: financial values are the most obvious example, but there are others too. Consider the score given to divers or ice skaters, for example.
For values which are more artefacts of nature which can't really be measured exactly anyway, float/double are more appropriate. For example, scientific data would usually be represented in this form. Here, the original values won't be "decimally accurate" to start with, so it's not important for the expected results to maintain the "decimal accuracy". Floating binary point types are much faster to work with than decimals.

Best Answer

Related Solutions

R – the .Net Client Profile PREVIEW

.net – Difference between decimal, float and double in .NET

Related Topic