Dotnetnuke on the local machine cannot be used. It is a disaster caused by wildcards.

Some days ago, I couldn't use dotnetnuke correctly in Windows 2003. When I typed in IE localhost/dnn as normal way, it ran longer time and a error shows
The message of 'the resource cannot be found '.
Then I tried localhost/dnn/default. aspx again, this time ie displayed me dotnetnuke (2.1.2) without images and CSS effect. Even that linkages didn't work at all after I loginned.

I posted the question on cnblogs.com but no replies, the way of re-installation of IIS is on consideration even that will cause your virtual directories will be losted. in my deep mind, I remind me that why not try deletion of wildcard (wildcard) from the property of default website in IIS. the usage of wildcard is for setup of Dudu's cnblogs source code on my local machine at the beginning of this month, but I want say that the dnn's error isn't the duty of Dudu ^ _*.

Now, you all know this time I can use dotnetnuke in right way again.