Tuesday, April 29, 2008

Can't see drivers\etc folder or hosts file in Vista x64?

I've just joined the Windows 64-bit OS club and ran into a frustrating issue, whereby I couldn't edit my hosts file (%systemroot%\system32\drivers\etc) using Altap Salamander. If I used Vista's Explorer, there it was.
Now, what's important to understand is Salamander is a 32-bit Windows application and the Wow64 layer is redirecting 32-bit applications to %systemroot%\SysWOW64. I remembered I 'knew' this, but surely there must be a way for a 32-bit application to see the native system32 folder, for file management operations.
Turns out there is. Create a folder %systemroot%\sysnative, and navigate via this to see the native system32 folder from within 32-bit applications.

Saturday, April 26, 2008

Vista x64 officially supported on Apple hardware

The Vista x64 update for Boot Camp is available here.  Perfect timing, as I'll be getting a new 17" Macbook Pro for 'research' at work in the coming weeks, and was hoping to dual-boot with Vista x64.

SIDPLAY 4.0 for OS X 10.5

For all those old Commodore 64 chip-tune fans out there, take a look at the re-released SIDPLAY for OS X.
In Summary:
  • Rewrite of the UI
  • iTunes look and feel
  • Export to mp3, AAC, AIFF and Apple Lossless
  • Integrated Spotlight search
  • Core Audio support

Friday, April 25, 2008

Get latest code from TFS via command line

I tend to work from the command line for managing builds and source control.  For my day job, we use TFS, so I use the Team Foundation command-line utility tf.exe with the 'get' option.
Be sure to start a Visual Studio 200x command-line prompt, to ensure tf.exe is available in the search path.
image
tf get will recursively grab changes from the current directory, so you can be somewhat selective.
 
If there are any conflicts, the familiar conflict dialog is presented, allowing you to determine the appropriate resolution.

Improve MSBuild performance with multi-processor builds

Using the command line :\>msbuild /m[:max cores] will automatically take advantage of multiple cores if they are available. Without the max cores parameter, msbuild will use all available cores. I've seen some recent posts on this topic, and wanted to point out I have been using this feature for a number of months, and can confirm noticable performance gains on my dual-core laptop. A big issue for laptops is the IO performance, so if you have slower drives, you may not see the same gains. Have not had a chance to try it on my 8-core Mac Pro :-)