So what to do? Just change the Windows Runtime Debugger back to Dr Watson. You can do this by using the command drwtsn32 -i. Just run it in a command prompt and the Windows Runtime Debugger is back to Dr. Watson.

The Installation went well – and everything seams to be running – until I noticed, that the ASP pages could not use the ActiveX object for the ExpandIT Online Connector.

After doing some tests, I found out that the reason was that the Internet Information Services (IIS) was using ASP.NET in a 64bit version and not in 32bit version.

So what to do? You can reconfigure the IIS to use the 32bit version of ASP.NET

This is done in the following steps:

1) Start the command prompt (Start -> Run -> CMD)

2) Then enable the 32-bit mode by using the following command:

cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 1

3) Install the 32 bit version of ASP.NET:

To install ASP.NET 1.1. use the following command:
%SYSTEMROOT%\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exe -i

To install ASP.NET 2.0 use this command:
%SYSTEMROOT%\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i

I would recommend only to install the ASP.NET 2.0 -  ASP.NET 1.1 is not needed

4) Finaly you have to enable the use of ASP, by going to the Web service extension list in Internet Information Services Manager and setting the ASP to allowed.

Now you should be able to use ExpandIT Online Connector on the server

They are wrong! XP is a 32 bit version, which means it supports up till 4 GB. Just do a little calculation and you will see that I am right in my suggestion.

2³² = 4.294.967.296

4.294.967.296 / (1.024 x 1.024) = 4.096

To get XP to recognize the remaining Ram you have to do a little trick. In the boot.ini (hidden file, which is found in the root of c) you have to add some new switches /3GB and /PAE.

Per default the user-mode memory space is limited to 2 GB with the /3GB it will be limited to 3 GB. This switch is a feature from the Windows 2000 / 20003 servers and was introduced to XP, so that device-driver developers could test their drivers without have to install a Windows server.

Note this switch should be used with caution; it can cause applications to have address dependencies related problems. Also it can cause an error with Active Directories (resource starvation). Though, these problems are mostly seen on a Windows 2003 Server.

By using the /PAE switch, it will let your device drivers use the Ram up till the 4 GB.

These changes may not work on all chipsets, cpu’s, motherboards. But after I enabled the switches, I’m able to see 3,5 GB and it seams that XP is using the ram above the 3 GB when I am looking on the usages in the Task Manager

Just start a command prompt:

Start -> Run -> Cmd

and then type:

IPCONFIG /ALL

In case of you want to change you IP (works only when you are running DHCP) – you can do i by using a release in combination with a renew.

IPCONFIG /RELEASE

IPCONFIG /RENEW

Here is how to do it:

1. Start regedit (Start -> Run -> Regedit)
2. Navigate to the Registry key HKEY CURRENT USER\Control Panel\Desktop
3. Double click on the AutoEndTasks entry and replace the 0 with a 1 in the Value data text box
4. Double click on the WaitToKillAppTimeout entry (if the dword value does not exist, then create it) and change the value to 2000
5. Double click on the HungAppTimeout entry (if the dword value does not exist, then create it) and change the value to 1000
6. Reboot

If you still have problems, then make the following changes:

1. Start regedit (Start -> Run -> Regedit)
2. Navigate to the Registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
3. Double click on the WaitToKillServiceTimeout entry and change the value to 2000
4. Reboot

Notice that lowest value XP will accept is 1000 (1 sec).

Be also aware of, that the WaitToKillService tweak can cause problems. If an application is in process of saving data a “kill”can case the loss of data.