109 reputation
4
bio website
location Ottawa, Canada
age 40
visits member for 3 years, 7 months
seen Apr 1 '13 at 14:56

Nov
16
awarded  Popular Question
Mar
1
comment Troubleshooting endless provisioning in Azure after custom image deployment
I'm having the same issue with a custom VM template. Mine's still not working despite the recommendation to remove all snapshots related to the vhd. Just saying in case that may be your problem ... don't know.
Jan
4
awarded  Scholar
Jan
4
accepted dir /X - 8:3 path name is not working on one drive
Jan
4
awarded  Student
Jan
4
comment dir /X - 8:3 path name is not working on one drive
@RyanRies So, I guess SpaceSniffer must have changed that registry key. I put it back to the default of 0, and now creating a test dir, works again. However, all the files/folders I have pulled down from source control have to be recreated. Thanks, put your comment as an answer and you get the points. :)
Jan
4
comment dir /X - 8:3 path name is not working on one drive
Yes, because some build scripts don't know how to handle spaces in path names, 8:3 support is required. It was working earlier today. So something changed ... NtfsDisable8dot3NameCreation is set to 2. How can that be for one drive and not the other? :S
Jan
4
asked dir /X - 8:3 path name is not working on one drive
Mar
7
awarded  Supporter