June 19, 2008
It’s officially unofficial…

My primary focus is shifting to Essential Business Server.
Well, not that SBS was ever really a focus for me. Still don’t know how that happened.
But it doesn’t take a badge to push information that matters, right?
First up…
Virtualizing Essential Business Server (posts tomorrow)
|| posted by chris under beta, biz, hardware, it pro, migration, mobility, rx, virtualization || comments (0) ||
||
June 18, 2008
For all you troubleshooters out there…

First one to post up the right answer might get a prize from the infamous Funcave prize stash.
Unless your last name is Stanfill. Or you have a pink blog.
|| posted by chris under clueless, hardware, it pro, rx, timekiller, virtualization || comments (3) ||
||
June 10, 2008
Trust me on this one.
NEVER make this setting change on a virtual machine…

Unless you really don’t care how it runs, or if it runs at all.
Or if you just want to see what it would be like to run Small Business Server with the processing equivalent of a Sinclair ZX Spectrum…

Kicking it old school. Word.
|| posted by chris under clueless, hardware, it pro, nostalgia, rx, virtualization || comments (0) ||
||
May 29, 2008

Weird weird issue on the normally kickass server here at the Funcave, which just so happens to be named Charlene. As in…
The name of this server is CHARLENE, SIR!
Tried to copy a 45GB VHD file to our girl…
A file which came courtesy of someone who just so happens to have a pink blog…
No matter how many different ways I tried to copy the file, Charlene eventually got into a totally frozen state. No matter if I tried to copy directly from USB HDD, via network client, or copying from another share, eventually Charlene would become totally unresponsive at the console, sever all network connects, etc.
Now Charlene’s a badass in her own right…
- HP ML350
- 2Ghz single quad-core Xeon
- 19 GB RAM
- 80 GB OS volume
- 250 GB Data volume
Charlene’s running…
- Windows Server Standard 2008 x64
- Hyper-V RC1
Seeing all kinds of weirdness trying to copy files to/from her.
All the mayhem starts when Free Physical Memory drops to sickeningly low levels.
Anyone with any serious knowledge of what’s going on wanna ping me? I’m talking Windows Server team, etc. Or anyone with the last name of Russinovich.
|| posted by chris under beta, clueless, hardware, kma, thumbs down, timekiller, virtualization || comments (4) ||
||
May 1, 2008

If you’re interested in getting familiar with Windows Mobile without having to shell out any of your hard earned cash nor becoming a total vendor whore to score some free hardware, then Device Emulator could be the answer to your prayers.
I could go on and on about the many many ways you can use Device Emulator for fun & profit. Here are just a few I’ve run across since writing my very first Device Emulator guide in 2005:
- Application development
- Remote support
- Troubleshooting
- Training
- Mobile web design
- Free platform to run GPS software on custom-modded PCs mounted in cars (what up Hungary!)
But enough of that, let’s get to installing this bad mamma-jamma. I’ll fully detail the installation process, including screen shots, for the less bravely-endowed in an upcoming section, Installing Device Emulator and Images. Since all of the installs are pretty much simple click-throughs, those of you capable enough to brave it on your own can use this Getting Started section as a Quick Install.
One thing to keep in mind: If you get prompted to reboot after any item is done installing, reboot before proceeding to the next item.
Here’s the bare minimum you’ll need to get started with the standalone version of Device Emulator:
- Virtual PC 2007 (only needed if you want network connectivity, free download here)
- Device Emulator 3.0 (latest and greatest version, free download here)
- At least one Windows Mobile Emulator Image file (there are separate download files for Standard/Smartphone and Professional/PocketPC images)
Here’s the order to install everything:
- Install Virtual PC 2007.
- Install Device Emulator.
- Install the Windows Mobile Emulator image(s) last. You can install as few or as many images as you want.
After your desired image installations are complete, you can test your installation by launching one image for each of the WM versions you installed. You’ll find the images at the following locations:
Windows Mobile 5 (I recommend using “PocketPC – Coldboot”)

Windows Mobile 6 and 6.1 (I recommend using “Professional”)

Once all three versions are running side-by-side, then you know you’ve got a solid installation.



On Windows Vista, after installing the Windows Mobile 6.x images you may not see any images listed under the Windows Mobile 6 SDK folder in the Program menu.

If this occurs, then open the Programs Control Panel and execute a “repair” on each of the Windows Mobile 6.x standalone image files.

Once each finishes the repair, the respective images will appear under the Windows Mobile 6 SDK folder and you launch them as outlined above.
So if you want to get your grubby little mitts on the hot-n-sexxay new interface for Standard devices in Windows Mobile 6.1 without paying an arm and a leg for a new device…

Device Emulator could be your best and only chance!
|| posted by chris under freebie, it pro, mobility, utility belt, virtualization || comments (0) ||
||