One view on organising digital photos

This content is 19 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

I’m really bad at organising my digital photos. I’m paranoid about losing irreplaceable photos (like the ones of my son as he grows up fast) and end up copying them to a variety of locations, but I’m not as smart about it as I should be.

In this week’s Connected Home Media update, Paul Thurrott writes about getting organised with digital photography using nothing more than the features within Windows XP. Not everyone will agree that this is how to do it (especially those with a commitment to third party applications which work for them) but its an interesting read, and will probably work for anyone who doesn’t have massive requirements for their digital workflow.

Is the release of Windows XP service pack 3 imminent?

This content is 19 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

I heard a rumour yesterday that Windows XP service pack 3 (SP3) will be released soon. I haven’t been able to substantiate it yet, but it does sound plausible.

It’s been over a year since SP2 was released and, because it was such a massive update, many organisations still haven’t adopted it because they are worried about the impact that the new security features will have on their infrastructure.

I guess because we’ve heard so little about SP3, when it arrives we can expect it to consist basically of a rollup of hotfixes since SP2, plus SP2 itself; but its arrival will mean is that, based on the Microsoft support lifecycle, SP1 will effectively be out of support. Now’s the time to think seriously about SP2/3 adoption!

Microsoft solution accelerator for business desktop deployment (BDD) v2.5 released

This content is 19 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

Thomas Lee reports that Microsoft have released updated versions of the business desktop deployment (BDD) enterprise edition and standard edition solution accelerators.

As he provided my BDD training, Thomas knows far more on the topic than I do and his blog carries details of the improvements in BDD v2.5.

If BDD is a mystery to you, check out my post from earlier in the year about the Microsoft solution accelerator for business desktop deployment, the Microsoft solutions framework and the Microsoft operations framework.

Getting around Windows file protection/system file checker

This content is 19 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

For anyone who’s ever struggled to get rid of a Windows component without Windows file protection/system file checker kicking in, I recommend Wes Miller’s post on how to banish Movie Maker from your system. This doesn’t just apply to Movie Maker – you can use the same method to remove any non-critical (or critical for that matter!) component from Windows.

Microsoft RAW image thumbnailer and viewer for Windows XP

This content is 19 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

When I’m not “messing around with technology” my main hobby is photography and last September I bought a Nikon D70 digital SLR camera. Since then, I’ve taken almost 3000 digital images, all as 6 megapixel JPEG images, but for those images which are a bit more than just family snaps I’d really like to make use of raw mode (without needing to buy Nikon Capture software). Tonight, I found the Microsoft raw image thumbnailer and viewer for Windows XP.

Although this won’t allow me to edit raw images, according to Microsoft, it does provide “the ability to view, organize, and print photos captured in raw image formats from supported Canon and Nikon digital cameras”. There’s also a white paper on viewing and organising raw images in Windows XP.

In fact, there’s a whole load of digital photography resources on Microsoft’s professional photography and digital photography microsites (I picked that tip up via RoudyBob.NET), including a link to Microsoft’s press release on raw support in Windows.

More Windows XP eye-candy

This content is 19 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

Last year, I posted a blog entry about installing the “Energy Blue” theme on a computer running Windows XP Professional.

Now there’s another option for those who are bored with the standard Windows XP wallpaper, but want something that still looks like part of Windows XP – the “New Bliss” wallpaper from the “Royale” theme, which, like Energy Blue, was originally designed for Windows XP Media Center Edition (XP MCE) 2005 but later ported to Windows XP Tablet PC Edition 2005 (and is now available for all Windows XP users). This, and some other interesting wallpapers (Kiwi Bliss, Boulders, etc.) are available from Microsoft in New Zealand (I’m not convinced about the Queen’s birthday version though).

(For those who have access, I quite like the Longhorn.jpg wallpaper from Windows Vista Beta 1 too).

More on integrating device drivers into an unattended Windows build

This content is 19 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

Earlier in the year I blogged about discovering unknown devices in Windows for integration into an unattended build. What I didn’t detail at the time was how to work out which device driver files are needed for a particular device.

Some device driver packages are pretty simple, but others are several megabytes in size. Rarely is the whole driver package required and it is usually sufficient to just copy a few files to the (RIS) installation source – generally:

  • An .INF (setup information) file with an associated .CAT (security catalog) file.
  • One or more .SYS (system) files.
  • Possibly some .EXE (application) and .DLL (application extension) files.

I usually start off by reading the setup information file which relates to the Windows XP version of a driver. It’s straightforward enough to identify the catalog file (used to confirm the digital signature for the other files) from the CatalogFile= line in the [Version] section and for many simple .INFs, it is easy to identify the device driver files from the [SourceDiskFiles] section, but sometimes the setup information file supports a variety of devices and not all of the files are required. For complex driver configurations (e.g. an ATI video driver), I usually copy the .INF and .CAT files to the installation source and then attempt to install the driver from a reference workstation. As Windows XP throws an error each time it is unable to locate a file, I add the requisite file to the installation source, retry and repeat until all the necessary files are present (which normally only takes a few minutes).

Some device drivers include a subfolder within the [SourceDiskNames] section. In this case you have a choice – either edit the .INF (not recommended as it will break the digital signature), or place the appropriate files (geneally all except the .INF and the .CAT into an appropriately named subfolder and extend the OemPnPDriversPath in the [Unattended] section of the unattended setup file.

One final note. In my unattended build, I have support for a variety of PC models, some of which use different drivers for what would seem to be identical hardware. For example, both the IBM ThinkPad T40 and the Compaq Evo N620c have an Agere Systems AC’97 Modem, but the driver version I downloaded from IBM and integrated into the build for the T40 was not recognised by the N620c (due to different PCI device instance IDs – the T40 implementation is PCI\VEN_8086&DEV_24C6&SUBSYS_05241014&REV_01\3&61AAA01&0&FE whilst the N620c is PCI\VEN_8086&DEV_24C6&SUBSYS_00580E11&REV_03\3&61AAA01&0&FE). I didn’t have access to a spare T40 in order to regression test a version of the driver with support for both device instances (assuming there is one), so I downloaded a version of the driver from HP, which does work with the N620c. Although the .INF and .CAT files are different, both the IBM and HP drivers have a number of files in common (AGRSM.SYS, AGRSMMSG.EXE and AGRSMDEL.EXE – albeit with different date and time stamps), so I left the newest versions of the common files in place (which happen to be the IBM versions). As I haven’t changed the files for the IBM driver, the T40 build should be fine, but the N620c build fails a check on the digital signature due to a mismatch between the file versions. There are two ways around this: either place the two driver versions into different folders and extend the OemPnPDriversPath in the [Unattended] section of the unattended setup file; or disable the check for signed drivers as detailed in Microsoft knowledge base article 314479.

Grabbing screenshots using the Microsoft virtual machine remote control client

This content is 19 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

I just discovered this and think it’s really useful…

I’m in the process of documenting a client’s server configuration, using a virtual machine with a VPN connection to the client’s network and then a remote desktop protocol (RDP) connection to their servers. Because the VPN is within a virtual machine, I’m constrained by the limitations of the Microsoft virtual machine remote control (VMRC) client and thought I could only take full screen screenshots, using VMRC’s Remote Control | Special Keys | Send Print Screen menu commands. What I found (completely by accident) is that if I use the mouse to send the print screen command, the whole screen is captured; however, if I use the keyboard (Alt+R | right cursor | down cursor | carriage return) it acts like an Alt+PrtSc, and only the contents of the active window are copied to the clipboard.

I’m not sure if this is true for all clients (I haven’t tested further), but my setup was:

  • Windows Server 2003 SP1 host.
  • Virtual Server 2005 (v1.1.465.0 SE).
  • Windows XP SP2 guest (with virtual machine additions 13.206 installed), VPNed into the client’s network using the Cisco Systems VPN client (v4.6.02.0011) and then RDPed into a Windows 2000 SP4 server (RDP client v5.1.2600.2180).

Use drag and drop to quickly open files in Notepad

This content is 19 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

I use Windows Notepad a lot and, a few months back, I posted a tip for Send to… Notepad to help people open text files from a context-sensitive right click. Whilst watching me struggle to edit a load of text files with strange file extensions (as he taught me how to use PHP yesterday), Alex came up with another suggestion. It’s probably well known, but if you create a link to Notepad on the Windows quick launch bar (just drag and drop from the start menu), you can drag and drop files onto it and they will open in Notepad. Simple, but very, very useful!

Microsoft’s Online Crash Analysis – so maybe it is useful after all

This content is 19 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

My Windows-based PC just crashed (hardly surprising given all the rubbish I have installed on it recently – despite all of the bad press that Windows attracts, I maintain that a well-patched and well-managed Windows NT, 2000, XP or Server 2003 system will generally be reliable).

In the past, if this has happened, I have ignored the message about error reporting (“yeah, yeah, yada, yada – I need to get back to work and did I manage to save that document I was working on before it crashed?”… etc.) but this time I let it report the problem – and I read the results. It was even useful.

You see what happens, is that if I experience a blue screen crash event, or stop error, while using Microsoft Windows XP (or later), I can upload the error report to the Microsoft Online Crash Analysis (MOCA) site for analysis (Microsoft say this is “to further improve the quality and reliability of Windows”). They then analyse the error report and prioritise it based on the number of customers affected by the error in the report. They then try to determine the cause of the error submitted, categorise it according to the type of issue encountered, and send relevant information when such information is identified.

What I like is that, using MOCA, I can check the status of the error report for 180 days and this time it told me that my system “crashed because the random access memory containing Windows program code was corrupted. Microsoft is unable to determine if this corruption was caused by a hardware or software issue. The nature of the corruption suggests that a hardware issue is more likely. To determine if this is the case, Microsoft developed a Windows memory diagnostic that tests your PC memory. We recommend you download and run this tool on your computer system”.

Sure, so the Windows memory diagnostic tool didn’t find any memory errors so I still don’t know why the PC crashed, but at least it feel like someone actually cares and is trying to fix things… much better than just getting a blue screen of death (or even a red screen of death!).