After you install or upgrade the printer driver on a Windows Vista-based or on a Windows Server 2008-based computer, some temp files that have a size of 0 bytes are created in the following folder:

%SystemRoot%\system32\spool\drivers\w32×86\3

Note: The temp files have a name, such as BUD.tmp. The placeholder represents a series of numbers.

Additionally, these temp files are not deleted automatically.

This problem may occur if the newly installed or upgraded printer driver includes the Unidrv.dll driver for Windows Vista or for Windows Server 2008.

Consider the following scenario:

• You print some documents.
• The printer driver is based on Microsoft Universal Printer Driver (Unidrv).
• The rendering occurs on a computer that is running an x64 version of Windows Server 2008, of Windows Vista, or of Windows Server 2003.
• The printer driver includes some font metrics data in its resource DLLs. The data is in formats compatible with versions of Windows earlier than Windows 2000. (This situation usually occurs in drivers for old nine-pin printers.)
• Text strings that are output to the printer are formatted in a device font.

In this scenario, certain printer drivers may print the text characters by using incorrect ASCII character codes. Therefore, the output may be rendered by using incorrect fonts. Additionally, text that is formatted in bold or italic fonts may be rendered differently on a 32-bit platform than on a 64-bit platform. In this case, the 32-bit platform output is correct.

Notes:

• This problem occurs only on x64 versions of Windows Server 2008, of Windows Vista, and of Windows Server 2003. It does not occur on x86-based versions of these operating systems.
• Documents are rendered before they are printed. This problem occurs on the computer on which rendering is performed. Rendering may occur on the client or on the print server, depending on several factors specific to each configuration. Therefore, to understand whether the hotfix that is described in this article is applicable, you must consider the platform type (32-bit or 64-bit) for the client and for the print server.

Environment
Novell iPrint for Linux Open Enterprise Server Support Pack 1 Driver Store
Novell iPrint for Linux Open Enterprise Server Support Pack 2 Driver Store
Novell iPrint for NetWare Novell NetWare 6.5 Support Pack 6 Print Manager
Novell iPrint for NetWare Novell NetWare 6.5 Support Pack 7 Print Manager
Novell iPrint Client for Windows Vista 5.04

Situation
When trying to add a Kyocera printer drive using the From File option on a Microsoft Vista workstation, an error is returned. The error is:

Error Message: {No paging File Specified}
No Paging File was Specified in the system configuration

Error Group: Windows
Error Code: 578

A paging file had been configured. The driver couldn’t be uploaded via the From System option as the printer driver didn’t exist in the system.

An article listing how to copy printer forms from one computer to another. Keep reading →

You may experience one or more of the following symptoms on a Windows Vista-based or a Windows Server 2003-based computer that uses a Hewlett-Packard (HP) printer:

• When you try to install a printer, the Add Printer Wizard stops responding.
• The computer stops responding.
• The print spooler stops responding.
• The print spooler crashes, and you receive one of the following error messages, as appropriate for your situation.
  • When you use an administrator account
    

    Connect to Printer
    —————————–
    Windows cannot connect to the printer.
    Operation could not be completed (error 0×000006be).
    Either the printer name was typed incorrectly, or the specified printer has lost its connection to the server.
    For more information, click Help.

  • When you use a user account
    

    Connect to Printer
    —————————–
    Windows cannot connect to the printer.
    Operation could not be completed (error 0×000006be).
    You do not have sufficient access to your computer to connect to the selected printer.

On a Windows Server 2003 or Windows Vista based computer, when you try to upgrade HP printer drivers, it hangs at the finish window. If you try to restart the spooler, the following error message occurs:

Unable to install printer driver, Operation could not be completed.

You try to install third-party printer drivers for cross-architecture support in Windows Vista or in Windows Server 2008. After you do this, you may be prompted for the location of the Windows printing components for the third-party printer drivers. The message indicates that the printer drivers that are being installed are incomplete and that the missing drivers must be added.

When you use the Binary protocol or the Tagged Binary Core Protocol (TBCP) to print from a PostScript printer on a Windows Vista-based computer, the Printer Spooler service stops responding. Or, the print application closes with an error message. Additionally, the following event is logged in the Application log:

Source: Application Error
Event ID: 1000
Information: Faulting application printdrvstress.exe, version 6.0.6000.16386, time stamp 0×454a010d, faulting module ntdll.dll, version 6.0.6000.16386, time stamp 0×4549bdc9, exception code 0×80000003, fault offset 0×00042ea8, process id 0×36c, application start time 0×01c74c0a5dea560b.

After you install Windows Vista Service Pack 1 (SP1) on a Windows Vista-based computer, the default printer may change to Microsoft XPS Document Writer. Additionally, when you try to do a print job, you are asked to save the print job as a file.

This problem occurs most frequently if you had set a network printer as the default printer.

Sorry for the backup! My posting software was giving me problems, I think I’ve got it worked out now.

• Vista’s driver ills aren’t just Microsoft’s fault
  There’s plenty of blame to go around.
  (tags: Drivers SP1 )
• Users blast Microsoft over Vista SP1 schedule
  Lots of users, like me, questioning why SP1 can’t be released to technical users, even if it is held back from Windows Update.
  (tags: SP1 )

Keep reading →