Scott Hanselman's ComputerZen.com

Apparently I blinked and missed it...when did MSDN totally change their search results page?  I haven't been able to give it the full run around, so we'll see if it stands up to the Google Test.

Just a placeholder for a deleted post, nothing here now.

I'll be in Vegas on Monday for an up-and-back-in-one-day trip to CAWorld for a Web Services Panel - ostensibly acting in Prashant's stead, no doubt everyone is down at the Microsoft Global Briefing in Hotleans.  But alas, for me, next stop is the Mandalay Bay to talk about challenges in making Web Services happen.

Just saw LxG.  Pretty awesome if you dig that (give or take 40 years) period in literary history.  They created a pretty amazing fantasy world with advanced (re: 1930s) technology blowing away the people of 1899.  The well-read will dig it, but it's got enough action for kids who haven't read The Picture of Dorian Gray.

One interesting linguistic note: In the final scene in Kenya, the Witch Doctor is actually chanting in Zulu (That's SOUTH AFRICA, not Kenyan kiSwahili, and don't get me started on how F'ed up Hollywood treats of little details like this...) and he's saying vuka (voo-ga) which means "Wake up!"

From Patrick Hynds (repro in link above):

If you try to allocate an array with a size range between 0x027fefbd and 0x027fffec, the framework throws exceptions. This range corresponds to memory block of little under 40MB. But if allocate a buffer smaller than or larger than this range, then every thing is fine. So the following call will fail.

Byte[] test = new Byte[0x027ffc22];

It looks like there are different algorithms for big memory block allocation. Is there something special about this range?  Anyone?  Note: I'm running this on a box with 512megs.  Does this behave different on a box with more or less?

UPDATE: Until someone gives an good explaination, Dejan has added this to the .NET Bugs Registry...