Digiwar - the Yeep-blog

Right now I’m on a Windows Server 2003 training and we just covered creating shares (the technical detail of the training is pretty depressing…). During an example the trainer gave about creating shares from the command line, we ran into an interesting Windows bug.
Let’s say you have a folder on your C: drive called “video”. Now if you want to share it from the command line you exectute: “net share video=c:\video”. This will create a share called “video”, which shares the “c:\video” folder. If you browse to the C:\ folder in Windows Explorer, you’ll see the folder with the hand icon overlay and if you right-click it and then click “Sharing and Security”, you’ll see the share properties.
Now remove that share and execute: “net share video=c:/video” (forward slash in the pathname). The share will be created and is accesible through the network, but if you browse to the C:\ folder in Windows Explorer there is no hand icon overlay. And the sharing properties tell you the folder is not shared. Interesting Windows Explorer bug.

[Last played: - Watsgeburt]

So last week I finally got Visual Studio 2005 Team Services beta 2 installed on a Virtual PC image. It took some time because I never configured a PDC, which is required for TFS (Team Foundation Services) even though I still think it’s just lazyness on part of Microsoft who use the domain authentication stuff for TFS, while they could also offer a simple (domain-less) server setup. But anyways, I got a PDC up-and-running, installed all the required parts, installed TFS and got connected from my workstation. But! My workstation is not in a domain, so even though I could connect, I could not create a project Some Googling taught me this is indeed a limit in the current beta. Cross-domain authentication is not supported for some reason. Well, so much for using TFS with the Go-Live license. Now I can only just check it out, because I need to create a VPC image with VS2005 beta 2 and add it to the domain to use it. And I will not start using that for the real development work, I have a beautiful dual processor machine for that, thank you very much! I’m really hoping for a beta refresh, of a RC1 that will allow cross-domain authentication.

[Last played: - Watsgeburt]

So I’ve been using Visual Studio 2005 Beta 2 for a while now. And I’ve confirmed a bug and even made a feature request on their excellent feedback site. The best part is that I can add bugs or feature requests to my MSN Alerts. Which, theoretically, means that I get a notice in MSN Messenger when they get updated (never seen it happen though). The downside of this is that I need to turn on tabs in my MSN Messenger. And because of the 2 tabs I use (Messenger and Alerts), I also get the other 10 I don’t use (or even want). Like the McDonalds tab or the Banking Buddy tab.

I’d like an option that allows me to choose which tabs I want to see and which tabs I don’t want to see. It would make my Messenger look less crowded. But when I try the “Send feeback” option from the Help menu, I get: This Service is Currently Not Available.

This sucks.

[Last played: Shadows Fall - Ghost Of Past Fai…]

I wanted to give some feedback on the horrible performance by VS 2005 Beta 2 and turns out more people are plagued by it. The solutions is to delete your preferences. I did it and it works like a charm now. So now I’m slowly but surely changing the preferences to my liking, waiting for the thing to slow down to a crawl again But if it does, I’ll probably have figured out what setting causes it. Which I can then report. Which they can then fix (I hope).

[Now playing: Cradle Of Filth - Ebony Dressed For…]