Apr 032016

Google Drive API provides a way to get the MD5 checksum of uploaded files. This can be used to verify if files uploaded correctly. I’ve created a small Javascript program that uses the Google Drive API available here: Google Drive MD5 Fetcher. You’ll need to authorize access first, then put the name of the file in the search box and it will fetch MD5s from Google. You can right-click to view source and see how it works.

Jun 012014

I just upgraded my laptop from Windows 7 to Windows 8, and in the process, I was required to uninstall DigitalPersona since it is not compatible with Windows 8. I expected to be able to download a newer version from Dell after the upgrade completed, but that’s not the case. You may be able to apply this update before upgrading, but I didn’t try beforehand.

  1. Visit My Dell Downloads and download DigitalPersona. You may need to register your laptop using Internet Explorer to get a list of software
  2. Install DigitalPersona and restart your computer
  3. Right-click on this link and select Save File As or Save Link As
  4. After you save the file, double-click it to add the changes to the registry. This creates a key that the DigitalPersona installer looks for. If it’s not found, it throws the Dell Personal not installed error
  5. Download either the 32-bit or 64-bit DigitalPersona v6.2.1.309 installer (originally from a forum post here)
  6. Restart your computer
  7. DigitalPersona should now be working. You may need to enroll your finger prints still

Additional information:
The DigitalPersona upgrade checks the registry key HKEY_LOCAL_MACHINE\SOFTWARE\DigitalPersona\Products\Personal\OEM for the value 020. If the key is missing, which was the case on my computer and apparently other peoples, the installer stops reporting a “Dell Personal is not installed. This package can only be installed as an upgrade.” error. The above instructions add that registry key so the installer will work. Additionally, you can use Orca to remove the Dell Personal check launch condition from the installer MSI.

Oct 192012

If you try putting an MSDN key into Anytime Upgrade, it will get started on the upgrade process then eventually fail telling you the key you entered cannot be used for Anytime Upgrade. The trick is to use some other key for the same version. This key, though, does not have to activate. I wanted to upgrade from Home to Professional. Luckily I had my Dell Laptop came with Windows 7 Professional.

  1. Run Anytime Upgrade with any key for the version you want to upgrade to (OEM keys work)
  2. After the computer restarts and updates, run slmgr.vbs /cpky to delete the product key
    slmgr.vbs is available on the internet, on Professional machines, and is probably located somewhere on the install medium
  3. Run slmgr.vbs /ipk XXXX-PRODUCT-KEY-HERE-XXXX
  4. Now slmgr.vbs /ato to activate it

** Each command may take a few minutes to finish even though it looks like it goes through instantly. A dialogue box will open with the results when the command has actually completed.

I highly recommend making a disk image before trying this process in case something breaks in the process. You can use Clonezilla, Acronis, Norton Ghost, among many other programs. There are plenty of guides online

Aug 102012

Early today I was looking for a way to automatically run Disk Cleanup on multiple computers in a domain. I found the /sageset switch which allows you to define the options you want to use in conjunction with /sagerun, but none of the articles mentioned anything about saving the settings for use on multiple computers. Using Regshot 2.0 unicode on Windows XP I determined the settings are saved in:


There is a key for each category and a StateFlags dword value for each configuration made using /sageset. The StateFlags value has a number after it that corresponds to the /sageset number. By exporting a the VolumeCaches key and merging in before running cleanmgr /sagerun, you can easily deploy a Disk Cleanup policy. I won’t have time to thoroughly test this on different machines until Monday, so USE WITH CAUTION.

Jun 132012

I’m not completely sure why this error is generated, but I have a hunch it’s because CutePDF tries to use a list of already installed PostScript print drivers and if none of the pre-configured ones are found, it errors out and will not continue.

  1. Install CutePDF Writer and allow it to error out. Make sure you select to install the PS2PDF tool when it asks.
  2. Go to Devices and Printers and select Add a Printer
  3. Add a Local Printer
  4. Make sure the drop down has an option for CPW2: (CutePDF Writer) otherwise these steps will not work
  5. I went ahead and selected LPT1: (Printer Port)
  6. For driver you’ll need to find a PostScript compatible driver. I went to the HP drivers and selected the HP Color LaserJet 2500 PS¬†driver. The PS at the end represents that it is a PostScript driver. You may have to look in the list, but there should be plenty of PostScript compatible HP drivers you can pick from.
  7. Continue on with the install and finally add the printer
  8. Go back to Devices and Printers and right click on the printer you just selected and choose Printer Properties
  9. You can change the name in the first text box to CutePDF or similar so it’s easier to find and remember
  10. On the Ports tab, change the port to CPW2: (CutePDF Writer).
  11. Apply/Ok after changing the port
  12. Do a test print. If you choose CutePDF (or whatever you named it) you should be prompted with a dialogue box asking where you’d like to save the PDF.