Windows

A stock 5.3-RELEASE /amd64 works on my workstation, while Windows 2003 x64 version would not :-)

Because sometimes I use Windows for daily desktop (the company’s IM system can’t run on FreeBSD and that’s the only reason why I can’t use FreeBSD as desktop at company) I have adopted WinCVS as development tool.

Unfortunatelly, when I have started WinCVS, it complained that it can’t find python (the version I have installed is 2.4). After searching the disk I figured out that the file exists in windows/system32/, not python24/dll. Corrected this setting and WinCVS appears to work correctly.

Windows XP SP2 is an important update and have introduced many security improvements. However, after installing Windows XP SP2, some graphical identity systems will be rendered to be useless.

The root cause is that these systems makes use of a special MIME type: x-xbitmap, or so called “XBM”.

XBM is originally developed by the X community. Presently it is uncommon on the web. However, banks like China Merchant Bank utilizies this format for authentication.

It seems that Microsoft is still testing/finalizing the Windows XP SP2 release. Up to today’s check, it is not released here. Interestingly, a Korean edition (Korean is another asian language, which is usually listed with Chinese) has been released much more earlier, even before Japanese and Chinese (both Simplified Chinese and Traditional Chinese) editions.

A Dell Latitude D600 computer with Windows 2003 Server Enterprise Edition is experiencing problem when installing Windows Update from website. By downloading the hotfix, and trying to install it, it fails with “Data Error, 0x8000007d”

ShapReader was introduced to me by junsu@ and I liked it very much. Today, it turns one (The first release was released last year), let bless it :-)

From Microsoft’s KB:

You can configure Microsoft Windows 2000, Microsoft Windows XP, and Microsoft Windows Server 2003 to write debugging information to three different file formats (also known as memory dump files) when your computer stops unexpectedly as a result of a Stop error (also known as a “blue screen”, system crash, or bug check). You can also configure Windows not to write debugging information to a memory dump file. Windows can generate any one of the following three memory dump file types:

1. Complete memory dump
2. Kernel memory dump
3. Small memory dump (64 KB)

junsu and I have discussed about some big hacks to FreeBSD kernel, and the implementation of a minidump is a good idea, I think.

On Windows there’s a minidump mechanism. The minidump will save ‘crashing’ pages only, while full dump will save the whole core memory when the system going to crash.

This is really insteresting one. With an “advertised” shell link, Windows Installer will automatically executed to install on demand.

Well, it’s out of my surprise to see a website called “LonghornBlogs” when I am looking for a Microsoft implementation of blog engine…