Ciao everybody
Im new in this list!
This is my first question:
I must to develop a user interface for my printer driver (Win NT 4.0). The
DDK sample for an user interface printer driver are present into ps full
printer driver (more complex and not contestual). Into DDK There is’t a
sample for a user interface for a minidrive ported (the original drive is
developed in Win 95 DDK with UNITOOL) driver.
Anyone know where I can find a good sample of a print driver UI component
for NT 4.0?
I see into DDK the sample Cpsui. This sample make a exe file that show some
property printer driver page (system standard and personalized). I know
that: a user interface printer driver is a custom provided dll. The sample
code Cpsui shoud help my to reach my goal?
Thank you very much in advance
Paolo Virgili
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
I don’t understand what you mean when you say that the psui sample is
“more complex and not contextual.” That is the only sample of an
interface dll in the NT4 DDK. If you do not want to go through the
process of writing a complete printer interface dll, you can use rasddui
or implement the oemui customization plugin in the W2K DDK and backport
it to NT4.
-----Original Message-----
From: Paolo Virgili [mailto:xxxxx@custom.it]
Sent: Monday, June 18, 2001 9:28 AM
To: NT Developers Interest List
Subject: [ntdev] UI printer driver
Ciao everybody
Im new in this list!
This is my first question:
I must to develop a user interface for my printer driver (Win NT 4.0).
The DDK sample for an user interface printer driver are present into ps
full printer driver (more complex and not contestual). Into DDK There
is’t a sample for a user interface for a minidrive ported (the original
drive is developed in Win 95 DDK with UNITOOL) driver. Anyone know where
I can find a good sample of a print driver UI component for NT 4.0?
I see into DDK the sample Cpsui. This sample make a exe file that show
some property printer driver page (system standard and personalized). I
know
that: a user interface printer driver is a custom provided dll. The
sample code Cpsui shoud help my to reach my goal?
Thank you very much in advance
Paolo Virgili
You are currently subscribed to ntdev as: xxxxx@microsoft.com To
unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
At 10:50 AM 6/19/01 -0700, you wrote:
I don’t understand what you mean when you say that the psui sample is
“more complex and not contextual.”
more complex: a sample with 2 project, the full driver and user interface
dll, with a lot of code, for me isn’t a simple example. Probably this case
is the best case beacause this sample as a lot of code but this code if
compiled make a full “don’t work” driver. There isn’t a example when set
the page format into driver. A “don’t work” code sample for me isn’t a
valid sample (You should consider the last line into this context, driver
development). The sample is for a PS printer my printer isn’t PS (but this
is the last trouble).
not contestual: I make a minidriv driver an I converted it for the Win NT.
In this context there isn’t an example to extend the UI for a minidriver.
Paolo
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
It has been demonstrated that the psui sample works fine. But I agree
that it will not be applicable in your case since you are not writing a
PS printer driver. Extending the UI for rasdd minidrivers has long been
known to be a limitation. Taking these factors into consideration, and
also that you only want to “extend” the UI, the best approach would be
for you to implement the oemui customization plugin from the W2K DDK and
then backport it to NT4.
-----Original Message-----
From: Paolo Virgili [mailto:xxxxx@custom.it]
Sent: Wednesday, June 20, 2001 2:09 AM
To: NT Developers Interest List
Subject: [ntdev] RE: UI printer driver
At 10:50 AM 6/19/01 -0700, you wrote:
I don’t understand what you mean when you say that the psui sample is
“more complex and not contextual.”
more complex: a sample with 2 project, the full driver and user
interface dll, with a lot of code, for me isn’t a simple example.
Probably this case is the best case beacause this sample as a lot of
code but this code if compiled make a full “don’t work” driver. There
isn’t a example when set the page format into driver. A “don’t work”
code sample for me isn’t a valid sample (You should consider the last
line into this context, driver development). The sample is for a PS
printer my printer isn’t PS (but this is the last trouble).
not contestual: I make a minidriv driver an I converted it for the Win
NT. In this context there isn’t an example to extend the UI for a
minidriver.
Paolo
You are currently subscribed to ntdev as: xxxxx@microsoft.com To
unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
At 10:32 AM 6/20/01 -0700, you wrote:
It has been demonstrated that the psui sample works fine.
Really? I compiled the sample and installed the PS driver into sistem, the
same driver is the POSCRIPT printer driver supplied by Windows NT (same
files).
If I print to a Port or to File the system show an error, and anything will
be printed out.
Paolo
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com