Printer Driver Upgrade results in crash

NTDEV
1

Hi,

I am trying to install a new printer driver on the already existing one
( upgrade) on Windows 2000.
In the new driver, I have added a new variable to the private devmode.

I tried 2 different methods for installing the new driver

  1. Install the new driver using Printer->Properties->Advanced->New
    Driver.
    The above installation seems to corrupt the driver as some functionality
    does not work and crashes
    when printing.

  2. Uninstall the old driver and re-install the new driver using add
    printer wizard. In this case, driver works fine

Does anyone know why the behaviours are different in the above two
scenarios OR is there any documentation
which suggests that step 2 should be followed whenever there is a change
in the private devmode.

Any inputs on this will be extremely helpful

Thanks in advance
Shalini

2

You have to implement DrvUpgradePrinter or you will keep crashing.If you
already have it implemented, then that code is buggy. The private part
can change and the DrvUpgradePrinter(…) should handle it properly. You
may want to check the msplot on how to go about it. I would say it could
be as simple as calling a SetPrinter(…) inside it.

Hope This Helps
Vipin

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Shalini K (WT01

  • EMBEDDED & PRODUCT ENGINEERING SOLUTIONS)
    Sent: Wednesday, October 27, 2004 5:33 PM
    To: Windows System Software Devs Interest List
    Subject: [ntdev] Printer Driver Upgrade results in crash

Hi,

I am trying to install a new printer driver on the already existing one
( upgrade) on Windows 2000.
In the new driver, I have added a new variable to the private devmode.

I tried 2 different methods for installing the new driver

  1. Install the new driver using Printer->Properties->Advanced->New
    Driver.
    The above installation seems to corrupt the driver as some functionality
    does not work and crashes
    when printing.

  2. Uninstall the old driver and re-install the new driver using add
    printer wizard. In this case, driver works fine

Does anyone know why the behaviours are different in the above two
scenarios OR is there any documentation
which suggests that step 2 should be followed whenever there is a change
in the private devmode.

Any inputs on this will be extremely helpful

Thanks in advance
Shalini

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com