There’s one problem which was driving my parents nuts on XP for some time before we finally got around to finding a reasonable solution. For whatever reason, one of their computers insisted on automatically adding the shared network printer on the other machine as the default printer in the list. This regardless of whether we had already assigned a local default, and whether the network printer was already in the list.

Whilst that already caused some consternation when documents would be sent to the wrong machine, it was compounded by the fact that if the printer was offline at the time, Windows XP would spend 100% CPU time trying to find the damn thing, leaving the PC highly unresponsive until the print queue was manually cleared. Meaning the options were between remembering to change the printer on every print job, or forgetting and rebooting the machine in between.

Fortunately, we found the handy little script below on some forum or other (praise be to the original author). It stops Windows’ printer service, deletes any waiting print jobs, and then restarts the service. Copy the lines below into a batch file (or into a simple text file and change its extension to .bat) or alternatively download the same script as a file.

@echo off
echo.
echo Purging the print queue . . .
net stop Spooler
echo Deleting all print jobs . . .
ping localhost -n 4 > nul
del /q %SystemRoot%\system32\spool\printers\*.*
net start Spooler
echo Done!
ping localhost -n 4 > nul

  Clear Printer Queue Batch (240 bytes, 4 hits)

printer · usb · Vista · Windows · xp

It’s a fairly common problem with Windows. Somehow a program manages to create a file with a name containing illegal characters or otherwise outside the file system’s parameters. No matter what you try, you just can’t rid yourself of it. The file certainly isn’t in use and being locked up by another program. Trying to delete or rename the file only results in Windows telling you the file cannot be found: “This is no longer in <location>. Verify the item’s location and try again.” Even running the Command Prompt with administrator privileges doesn’t allow you to move, rename or delete the blasted thing!

Fortunately, I managed to find an easy solution. Fire up the 7-zip File Manager, and rename the file from there. Bingo – don’t ask me how Vista couldn’t manage it, or indeed why 7-zip could, but at least now you can delete the blasted thing! Kudos to the guys on this forum for the answer.

file system · Vista · Windows

Whilst installing the latest version of Juice, a crossplatform podcast receiver on Windows Vista, I came across a rather simple error that prevented the program from functioning correctly on the first load, and then from loading thereafter. The error log generated the following output (where xxx indicates the username):

Traceback (most recent call last):
File "gui.py", line 4, in ?
File "iPodderGui.pyc", line 3573, in main
File "ipodder\configuration.pyc", line 468, in __init__
File "os.pyc", line 154, in makedirs
OSError: [Errno 2] No such file or directory: 'C:\\Users\\xxx\\My Documents\\My Received Podcasts'

Fortunately the fix seems to be quite simple and pain free (though a bit of a hastle to implement manually), found courtesy of Randall’s Life.

1. Change the compatability mode of the application to Windows XP SP2 mode. To do this, right-click the application file, or a shortcut to the program, select properties, click the ‘Compatability’ tab and then tick the box to ‘Run this program in compatability mode for:’ and select the appropriate option from the download menu.
2. Locate the file Ipodder.cfg (normally found under C:\Users\xxx\AppData\Roaming\iPodder) and edit it such that the line reading “download_dir = ‘C:\\Users\\xxx\\My Documents\\My Received Podcasts’” instead reads “download_dir = ‘C:\\Users\\xxx\\Documents\\My Received Podcasts’”.

After that, the program should run normally.

juice · podcasts · Vista

Having recently set up some network storage, I came across a rather irritating problem mapping network drives in Windows XP. The basic setup procedure, as outlined here, worked perfectly on some systems, but failed to retain the stored username/password for network attached drives requiring alternative login details. The solution found, courtesy of this blog, is to map the drives using the following command (replacing U with the drive letter, and NETHOME\LOCID with the relevant UNC network location):

NET USE U: \\NETHOME\LOCID /PERSISTENT:YES /SAVECRED

The necessary username/password details can then be entered and should be stored, allowing the drive to be mapped automatically when the user logs on.

mapped drives · nas · Windows

A friend of mine was having a strange problem with her Dell XPS system, whereby the active area of the mouse cursor would move with apparent randomness, occasionally being located as it should be at the arrow’s point, sometimes at its middle, other times half an inch below. This post led us to the solution that a simple graphics driver update was required, coincidentally for the same ATI Radeon HD 2600 XT card.

dell · Vista · Windows

It seems that occasionally, Windows Vista users can encounter a rather nasty bug which leaves them unable to log in to their system. If this is their only user profile, this can leave for a very distressing moment, particularly if the user is unfamiliar with Windows’ Safe Mode or various options available on the Vista DVD. The user is confronted with an error message such as the following:

The user profile service service failed the login. User profile cannot be loaded.

Or in German versions:

Die Anmeldung des Dienstes “Benutzerprofildienst” ist fehlgeschlagen. Das Benutzerprofil kann nicht gestartet werden.

From what I can gather, it appears that this problem occurs during Vista’s attempt to create a restore point. The user profile is backed up but no replacement is made. Thus these errors are most often seen after the installation of some new software or drivers, or after a Windows update, which may occur in the background with many users unaware of its activity.

Fortunately, some solutions are available, although not all appear to work in certain circumstances. Nigels blog offers a solution to restore the backup profile by editing the Windows registry. To do this, users need to:

1. Start the machine, and press F8 before Vista begins to load, choosing Safe Mode.
2. Search for the programme ‘regedit’ from the Start menu.
3. On opening this programme, navigate to HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionProfileList
4. Affected profiles can be located by the extension ‘.bak’. This extension should be deleted, the RefCount value should be 0, and the State value should be 0. Change accordingly and reboot the system.

German readers may also refer to this forum post.

Unfortunately this solution appears not to work in all cases. Since this problem generally appears to occur following a Windows Update or other software installation, however, it is equally possible to restore the system to a prior state and restore the working profile(s) to how they were before the incident. This might result in some strange behaviour or odd errors in some programmes, but these problems should only be minor ones. To do this

1. Start the machine in Safe Mode (hitting F8 before Vista loads, as above)
2. Search for the programme ‘rstrui’ in the Start menu.
3. On running the programme, the user should be presented with the option of restoring the system to the most recent restore point (recommended). Restore and restart.
4. Should the recommended option fail to solve the problem, follow the same procedure but use an older restore point. Hopefully one or other should do the trick.

Hopefully with the gradual rollout of Vista Service Pack 1, this type of problem will become less frequent.

Benutzerprofil · Benutzerprofildienst · user profile · Vista · Windows

After reading a review over at freewaregenius.com, I thought I’d check out this neat little program, free for personal use. It offers a way to install programs as a ‘layer’ on your system, transparently noting all changes and additions made in the installation, and enabling you to turn this layer on or off, or seamlessly delete it without worry. Although not limited to creating layers for installations, this would seem the perfect solution for people who wish to try out different versions of a software package without them interfering with one another, or simply test out some software without the hastle of worrying if its installer left anything behind.

However, I came across a problem during the installation that seems, ironically, to be caused by things being left behind. The installer would fail and blurt:

There are file operations pending on this machine. The machine should be restarted, and setup can be run again.

Whilst a reboot should fix the problem, this was not the case for me. Your natural recourse to a problem like this might be to delete everything in your C:\Documents and Settings\your username\Local Settings\Temp folder, as detailed here (in Chinese), however this brought no joy. Instead, some erroneous registry entry was to blame.¹ The solution is to delete the entries and restart, thus:

1. Click Start > Run… and then type regedit.
2. Find the following branch in the registry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager.
3. Double-click the PendingFileRenameOperations entry.
4. Delete any entries and click OK.
5. Close the registry editor and restart the computer.
6. Run the installer again.

If this does not work, another solution would be to export the above registry branch, delete the PendingFileRenameOperations registry entry altogether, run the installer, and then reimport the saved file.

1. Note that these entries are probably only erroneous if they are still present after restarting Windows. Ensure this is the case. [↩]

altiris svs · freeware · review · software