I wrote a GUI to change the settings of a printer, based on pre-defined
configurations that get loaded from an ini file.

The program works without a hitch on the 1st run. However, after I run
the program, the printer driver appears 'locked' until I reboot the
machine. After the reboot, start/settings/printers reflect the change
of the last attempt.

How can I force the OS to let go of the printer driver for further
editing without a reboot? Or, what is a common mistake that I may have
made, that keeps the driver locked based on the 1st call of
SetPrinter()?

On 24 May 2005 07:55:26 -0700 in comp.periphs, "#2pencil"
<number2pencil (AT) gmail (DOT) com> wrote:

You're better using printer preferences to setup the printer, then
regedit to dump the printer registry settings to a file, and finally
add a shortcut to the registry settings file in your startup folder.

--
Thanks. Take care, Brian Inglis Calgary, Alberta, Canada

Brian.Inglis (AT) CSi (DOT) com (Brian[dot]Inglis{at}SystematicSW[dot]ab[dot]ca)
fake address use address above to reply