Entries Tagged as 'Windows'

Microsoft MyPhone

I’ve been using Microsoft MyPhone for several months now; and I switched over to it not because it’s something I felt I really needed, but because Windows 7 doesn’t synchronize with Windows Mobile 6.5 devices using the new Windows Sync Center; it requires that I install the Vista (abomination) Device Center which replaced Active-Sync.

Why do I hate Device Center?  Well, I couldn’t really care whether I use the-man-in-the-moon or what ever to sync my phone, all I care is that I not have to use Outlook!  And you guessed it, Device Center will only synchronize with Outlook, Windows Sync Center allows synchronization with a number of sources (including Outlook if you use that POS).

The options I had were use third party synchronization software (which I was forced to use back when I had a Motorola KRZR — and I really didn’t want software to limit what I could sync), use Google (I really don’t want Google to have more of my personal information than they already have, or try MyPhone (not that I’m wild about Microsoft having my personal information; but I know that they’re a clueless company who wouldn’t know what to do with the information even if they realized they had it).

There are many things that MyPhone won’t do, and we might as well get those listed first:

  • It will not download ring tones
  • It will not synchronize to live contact, calendar, etc
  • It will not allow you to backup on your desktop

Things it will do:

  • It will limit you to 200 MB of storage
  • It will synchronize contacts (including pictures, but it does have some limitation with field sizes; so Garmin GPS points are a little problematic)
  • It will synchronize calendar (but it doesn’t allow notes or reminder, you have to enter those on the phone)
  • It will synchronize task lists (again see the above limitations)
  • It will synchronize text messages
  • It will synchronize browser favorites
  • It will synchronize photos
  • It will synchronize videos
  • It will synchronize music
  • It will synchronize documents
  • It will allow for deleting and archiving.
  • It will support multiple phone
  • It will support social networks (well, Live)
  • It will provide your phone’s last known location (last sync)

If you’re willing to pay for enhanced services:

  • It will ring your phone
  • It will provide your phone’s current location
  • It will lock your phone
  • It will erase your phone

Presumably these last services are targeted at lost phone (so you might wait until you’ve lost your phone to pay for the service, and I guess if it can’t do it you might be able to get a refund).

Currently MyPhone only supports Windows Mobile devices (so you can consider it’s something you get when you purchase a Windows Mobile phone), and most current Mobile 6.1 and 6.5 phones already have it pre-installed (but you can easily download it and install it on any Windows Mobile 6, 6.1, or 6.5).

To effectively use MyPhone you should have an unlimited data plan (or it might end up costing you quite a bit of money to do the synchronizations).

I don’t want to give anyone the impression that I think MyPhone is the best thing since sliced white bread (who came up with that expression — white bread is horrible), but it works, and it works well — and it provides a service for owners of Windows Mobile 6.x that Windows 7 doesn’t (so much for Microsoft’s flagship products, makes you wonder why you have to pay the big bucks for things that don’t work well, and don’t work together).

One of the nice features of MyPhone is that you can use it to sync information to you phone regardless of what desktop operating system you run (I believe synchronizing to Windows Mobile devices still requires a third party [extra cost] product on OS-X; Sync Mate or Missing Sync).

NOTE:  I believe Microsoft considers MyPhone to be part of the Windows Live offerings, but since it doesn’t inter-operate with Windows Live (at least in the current version) I don’t see how anyone can make that claim with a straight face (where do they get these programmers and program managers).

Microsoft MyPhone

GIMP

GIMP is an acronym for GNU Image Manipulation Program. It is a freely distributed program for such tasks as photo retouching, image composition and image authoring.

It has many capabilities. It can be used as a simple paint program, an expert quality photo retouching program, an online batch processing system, a mass production image renderer, an image format converter, etc.

GIMP is expandable and extensible. It is designed to be augmented with plug-ins and extensions to do just about anything. The advanced scripting interface allows everything from the simplest task to the most complex image manipulation procedures to be easily scripted.

That’s what the GIMP site says; but what GIMP is is a free Open Source alternative to programs like Adobe Photoshop and Corel Paint Shop Pro that runs on Linux, OS-X, and Windows.

GIMP is reasonably easy to use, powerful, and rock solid.

If you understand the principles of image/photo editing you’ll be a pro at using GIMP in no time — far easier to use than Photoshop, far more functional than Paint Shop Pro.  And it’s free — totally free — just download it an install it.  There’s lots of plug-ins for it as well (so make sure you take a look at some of those add ins).  Be sure and review the online documentation, tutorials, and FAQ; plus there are a number of well written books on GIMP available for purchase.

GIMP.org

#$%^ Documents and Settings

I wrote this little batch file to make Windows XP and Windows Server 2003 have a user directory structure more similar to Windows Vista, Windows Server 2008, and Windows 7.

You simply need to run it as a user with administrative privileges and it will create the “User” directory in the root of your drive along with all the other more “sane” directory structures that the newer Windows use — don’t worry, it uses links so that you won’t have two copies of the information, and applications that expect the old structure will continue to work.

There is an older BLOG post that describes how it works:  Revise Windows XP “Home” Directory Structure if you’re interested in the details.

MkLinks

Desktop Backgrounds

I use a lot of virtual machines, and I often RDP to my servers to manage them; sometimes I’ll have several windows open at once and it becomes fairly easy to get a little confused as to what window is associated with which machine.

Long long ago (in a galaxy far far away) I started making desktop background images that contained the machine name and installing them on each machine.  That was a fair amount of work, and require configuration on each and every machine.

Then I found BgInfo (from SysInternals, now Microsoft), and that was a great solution — but it did still require a moderate amount of configuration on every machine…

So, I created an “installer” for BgInfo that puts all the files in the right places, and creates the startup link so as to almost completely automate the configuration (OK – you have to run a single command on each machine; but if you map to a share or put this on a thumb drive it’s really simple).

BgInfo (my installer; includes an older version of BgInfo)

BgInfo on Microsoft

Secure what?

We  really haven’t done everything we could to protect our customers. Our products just aren’t engineered for security.

· Brian Valentine – Senior Vice President for Windows Development, Microsoft Corporation

Defragmenting

There are many people out there that say that *nix and Mac file systems don’t fragment — only Windows does.

They’re dead wrong.

[I know I've said this before, but it's worth saying again]

All three file systems (and in Windows we’re talking about NTFS, not FAT) derive from the same basic file system organization, and all three have pretty much the same characteristics (there are differences, but those really have nothing to do with the likelihood of fragmentation).

Fragmentation is just a by-product of the way a file system works.  The file system must make decisions about how to lay files down on the disk, and since it doesn’t have a crystal ball it cannot see the future.  Thus is a file is pinned between two other files and it must grow, the file would either need to be moved (creating an empty spot of a maximum size) or extended in another area (thus being fragmented).

There are various schemes for handling file allocations, but most of them rely on an application that is creating the file giving the operating system (and thus file system) sufficient information on the files maximum size and hints as to whether it is temporary, may grow, etc.

Given that file systems will fragment, the need for fragmentation is real.  Windows recognizes this (mainly because Windows used to use a FAT file system where fragmentation caused severe performance issues).

If you have a *nix or Mac based system, I’m sure you can locate a reasonably good defragmenter (not every one is in denial about the need for periodically defragmenting the system).  If you have  Windows based system you already have a reasonably good defragmenter that came with the systems (a “lite” version of Executive Systems Diskeeper, which now just goes by the name of Diskeeper Corporation).  You can, of course, purchase a number of commerical products, like the full blown Diskeeper, O&O Defrag (my personal favorite), or download a host of free or inexpensive products.

The key to defragmenting your system is knowing when you should invest the time (and wear on your disks).  The most accurate answer would be when system fragmentation reaches a point where it adversely effects performance.  That seems a little vague, but most of the defragmentation tools actually will do an analysis and advise you if they should be run.  Some of them have active defragmentation (but like the file system, they don’t have a crystal ball, and will often cost performance, not enhance it — so I would just say no to active defragmentation).

A good rule of thumb is that right after you install you system, or any time you install major updates or service packs you should defragment your system.  It’s a good idea to clean off temporary files (like your browser cache, etc) before you defragment.  And you might even want to clean off old restore points (if you have them enabled).

There’s certainly no reason to defragment your system daily or weekly; but an occasional night of running your defragmenter of choice will likely decrease boot time and increase overall system performance.

One other little tid-bit — remove your paging file before defragmenting; then after you’re finished, create a new paging file of a fixed size (ie set the minimum and maximum to the same thing).  That way you have a nicely defragmented paging file that will not cause fragmentation or fragment itself (leading to better system performance).  Of course, if your system has enough memory to run without a paging file, you don’t need one at all.

Video Editing on a PC

I purchased a Mac Pro and Final Cut Studio to do my video editing, simply because I felt that PC solutions were just not there.

Adobe Encore is a joke, the only thing it was good for was crashing (and thinning out your wallet).

Sony Vegas was a descent application (and solid), but difficult to use and didn’t seem to expose as much control as I wanted over DVD production.

Times change; and now I’m not as concerned with DVD production as I am with just video editing, and two of my friends have shown interest in video editing and really don’t want to invest in a Mac (there is only one real choice for video editing from Apple, and that’s a Mac Pro, and the combination of the hardware and software is a little scary).

One of my other friends has used Vegas for quite awhile, and he’s been happy with it (of course he’s never done video editing on a Mac).

I’ve decided my project for the next several days will be to evaluate Sony Vega Pro 9.  I’ll try it out on Windows 7 and write a BLOG post that tries to detail the strengths and weaknesses without directly comparing it to Final Cut Studio; though I may use Final Cut Studio as the “standard” for what a high end video editing suite should do.

Upgrading Drive Firmware

First, if you’re not having problems with your drive (unless it’s brand new, has no data on it, and you don’t have an issue returning it to the place of purchase or manufacturer) DO NOT DO IT.

Second, make sure you give yourself plenty of time, don’t try and do it quickly, or in between other commitments.  Do it when it’s quiet.  Make sure you have a UPS on your computer and that the weather is clear (so that there’s no likelihood of power outages).

Third, run the drive diagnostics from the manufacturer first.  If the drive shows it’s having problems — return it to the manufacturer for replacement (most manufacturers will do advance replacement at no charge with a credit card; that gives you a drive to migrate your data onto, and a shipping container to return the failing drive in).

Fourth, many manufacturers support upgrading firmware directly from Windows (a few from other operating systems).  I high recommend you choose the bootable CD approach — that way there’s no question whether or not you have something installed on your computer that might interfere.  And if you’re using SATA I recommend you set your computer to SATA IDE/Legacy mode to insure that the upgrade (and diagnostics) don’t have any issues with your SATA controller (IDE/Legacy as opposed to SATA/Native, SATA/RAID, SATA/AHCI — different BIOS manufacturers will call it by a different term, but it’s the lowest setting for the controller, likely it’s what the default was).

Fifth, make sure you obtain the firmware update only from the manufacturer’s web site; and make sure that it is for your drive; and that it’s recommended as a general installation or specifically addresses an issue you’re having.

Sixth, make sure you read and follow the manufacturer’s procedure for updating firmware.

Seventh, power off your drive before you attempt to use it after updating the firmware.  Most drives will not use the newer firmware until they are power-cycled; some drives just flat out won’t work until they’ve been “hard reset”.

Hopefully all goes well, but many drives become a brick if your firmware upgrade fails; a few can revert to the previous firmware and keep on running.  If you have problems, contact the manufacturer, most drives under warranty can be replaced — but data recovery is not included.

NOTE:

Upgrading drive firmware may also change the first several sectors of the drive; I highly recommend that you backup the drive before upgrading the firmware.

A signature Mac Book

But not from Steve Jobs, but rather Steve Balmer.

Last week Steve Ballmer, CEO Microsoft Corporation, participated in a meet and greet after speaking at Nashville Technology Council (held at Trevecca Nazarene University) and was ask to sign an individual’s aluminum Mac Book — and he did, right across the Apple logo!

Windows Live Mail Bugs

Make sure you’re sitting down, I wouldn’t want you to fall over — but there are bugs in Live Mail.

I actually did the Beta for Live Mail quite some time ago, and reported several bugs during the course of that — from my experience you’re wasting your time reporting bugs to Microsoft, each and every bug I found made it into the first release, and almost all of them are still there.

Here are two bugs that really need to be fixed.  Both are annoyances (they won’t result in the loss of data for sure); but both of them speak to the attention to quality and detail that simply isn’t part of the Microsoft culture.

The first bug which really needs to be fixed has to do with viewing a folder in an account.  Many times when you perform and operation (like deleting a folder for instance) Live Mail will repaint the folder view; however, it repositions the view port at the first item (but leaves focus where it should be)… the problem is if you have more folders that fit vertically on the screen, you’re looking at an entirely different time zone than the one that has focus.  A simple fix — save the view port position before the operation; restore the view port position after it if and before the repaint.  I guess the programmer that did this code was sleeping during Windows Programming 101.

The second bug which also really needs to be fixed has to do with dragging an email into the file system.  Windows Live Mail will create a file system safe name for the container file from the subject; however, if the subject ends in “…” (and probably many other character sequences) the file doesn’t get a “.eml” file extension, but rather a “._eml” file extension.  I guess the programmer that did this code figured it was right to make the file name file system safe after appending the extension when he should have made the base name file system safe and then appended the extension of “.eml”.

Like I said, these are simple issues — with very simple fixes… but they are fixes that shouldn’t be been necessary since this code should have never gotten out of Beta with these problems (they were reported).  In fact, I could argue that these problems should have never made it into a code build — they should have failed unit tests.

But these problems made it into release code; and these problems have existed for quite some time in release code — all I can say is that the commitment to quality I see in Microsoft software is similar to that that I see in Open Source code… so hopefully Microsoft will begin giving away more and more of it’s software at no charge so that the cost basis and the quality are on par.