After getting a licence and re-installing the MAPILap NNTP Outlook plug-in I was kind of frustrated that the plug-in did not work anymore. Basically I found the reason in the registry settings of the tool. There the account was still disabled since I have chosen this option during a test installation before.
Just delete the folder with the deactivated profile name. After the next start of Outlook the plug-in wizard appears again.
Working in the virtual machine sucks sometimes. The Virtual Machine Network Driver is supposed to be a solution at least for some network issues.
The Virtual Machine Network Driver allows the Device emulator’s OS (or even the Virtual PC OS, as the case may be) to emulate its own network connection. Because the physical network interface on the host machine is now “virtualized,” you have a way to get two IP Addresses – one for the host PC, and one for the operating system that is running within the Device Emulator (or Virtual PC). Device Emulator users using the VMNet Driver can connect to the host machine over TCP or UDP as the alternative to the standard “Activesync over DMA” solution.
I remember now one of the issues with w.bloggar: After doing all this setup stuff for the FTP, closing w.bloggar and starting the tool again, all the entries are gone. Well, if I have to rewrite all the settings again after I closed the tool, it looks somehow wrong to me.
Today, I decided to pimp my Tablet PC somehow. The first I pushed the available RAM of the Toshiba M200 to the absolute limit of 2GB. Finally, I decided against a second Samsung M40L2923 module. Instead I use a 1GB DIMM-S0 Infineon module.
Still not satisfied, I wanted to update my BIOS to the current BIOS version 1.7. This sound pretty easy while Toshiba offering a windows-based update utility for those not having any disk or DVD drive available. Anyway some issues appeared:
If you search for a while, you’ll find that the problem is well known and described in this technical support bulletin. All you have to do is downloading the Toshiba Utilities to make the missing DLLs available. Beside the installation of the BIOS some more utilities are available, too.
After starting the update utility again, the system need only a few seconds, until reboot. The after logging into the system the tool is finishing the (un-)installation for a few seconds. After that everything works properly again.
While playing with Indigo, I spend several hours on duplex services and clients finally leading to an annoying issue. I tried two different examples, one from the book Programming “Indigo” and another one from the WinFX SDK documentation. In both cases, I spend hours writing down all the code, especially as the examples in the book do not fit with the current release of WCF anymore. So some fixes have been necessary. Having both examples, I tried to start the clients, but they did not receive any response from the service. If you are patient enough (which means waiting 5 to 10 minutes) the client will result in a ChannelConnectException.
What is wrong? Bindings? Any mistake in the XML config-files? The solution is as simple as it could be: Just right-click the web site in the solution browser and choose Start Options…
Uncheck NTLM Authentication which is checked by default and restart your service and client.
After restarting the service and the client, the client is processing, the service is responding and the Quick Console shows the expected output:
While preparing some demos to show cool stuff at PDC 05 I installed the hot new DirectX SDK Update August 2005. Unfortunately, VS 2005 does not like the update. After starting my already testet applications using DirectInput an Exception occured. A LoaderLock was detected… what the heck?
Actually, you can find something about this issue in the Visual C++ 2005 Library and Runtime Enhancements transcript. Also Tone Engel has found this isue already and posted the solution in his blog.
Just set a new string value mda = “0” under HKEY_LOCAL_MACINESOFTWAREMicrosoft.NETFramework. Looks like it does not solve the problem, but at least the error message disapears.
IIS is not willing to start anymore. At least in the Microsoft Knowledge Base you can find a hint for this problem. So first, I thought it could be all the beta WinFX and Indigo stuff, I have installed on my machine. Finally, I found the reason: Skype grabbed port 80. After closing Skype I was able to restart the IIS.
