IPrintOemDriverPS::DrvGetDriverSetting example

device driver

    Sponsored Links

    Next

  • 1. How do you execute an app that needs admin privs from a user acct?
    I've got a device driver for a custom pci device, that exposes an ioctl interface to user mode appications. Under Windows Vista, the only way to exeucte the app is with an account that has admin privs. Is there any way to use a standard non-admin user account to execute the app? /Russ
  • 2. Send raw data to USB device
    My boss wants me to write a driver to download USB driver directly into a mobile device. After the USB driver is downloaded into the mobile device, I need to download the rest of system image via the same USB cable. Therefore, I cannot use standard USB driver( like WinUSB) to achieve it because there is no USB driver in the device at the first place. I think I need a simple protocol to communicate between PC and the mobile device. The simple protocol should be simple enough to be stored in the ROM of the device. The main issue is that I don't know how to bypass the whole USB protocol stack and transmit raw data to the device direclty. Is it possible with the Microsoft driver framework?
  • 3. Kernel mode code signing - Test signing
    Hi, I am upto go with making Test signing for my driver set (UsbSer.sys + MyConvert.INF). i followed the KMCS_walkthrough.doc which explains how to proceed to obtain a test sign the data in summary says so - 1. Prepare a computer for test-signing. 2. Create a test certificate by using MakeCert. 3. Create a catalog file by using MakeCat or Inf2Cat. 4. Test-sign the catalog file by using SignTool. 5. Install the test certificate in the Trusted Root Certification Authorities certificate store. Now coming to my issue, i am through step 2. but for step 3 (using the Toaster examples .CMD script file in WDK(6000)) i am not able to generate a .cat file to proceed further in which "Signability" tool is used in the .cmd file did anyone encounter the same before, i came to know that "INF2Cat" is the one much effective, but in vain, neither i could get it as standalone nor with "winqual submission tool .msi setup". Thankful if any one could suggest how to proceed either "how to generate a .CAT file using signability" else a place to get inf2cat.exe (and its components). -- Thanks in advance, Shankar G.

IPrintOemDriverPS::DrvGetDriverSetting example

Postby patricerolland » Sat, 24 May 2008 19:33:27 GMT

hi all, i have a pb to use DrvGetDriverSetting it is not working with
some feature like "Orientation", do you have an example ?

thanks in advance
Patrice

Similar Threads:

1.How to use IPrintOemDriverUI::DrvGetDriverSetting

I'm trying to use IPrintOemDriverUI::DrvGetDriverSetting method to get
information about user selection of "n-up" or "booklet". I also tried
on "Orientation". Both don't work. Can anybody give me a hint?

Thanks.

LONG APIENTRY OEMDocUICallBack(..){
.....
  char nup[]="OEMGDS_PSDM_NUP";//"Orientation";
  POEMUIPROCS pOemUIProcs = pOEMUIParam->poemuiobj->pOemUIProcs;
  if (!pOemUIProcs->DrvGetDriverSetting(pOEMUIParam->poemuiobj,
         nup,&dmNup, sizeof(DWORD),&bcNeeded,&dwOptionsReturned)) 
         {
              //do something.
         }
....
}

Can I use other DLL method such as DrvQueryJobAttributes?

2.ODBC Driver Example Code

I am new to Microsoft and have been tasked with writting and ODBC Driver. 

I've looked through the MSDN site and found a number of articles that 
discuss ODBC Driver development. I've read through the ODBC API reference 
manual and have a pretty good idea what needs to be done. 

What I need to move forward is to find some example code that I can look at. 
An article that identifies the steps to creating and deploying an ODBC driver 
would be great!

Does anyone know where I can find some ODBC Driver example code? Would it 
help if I had an MSDN Subscription?

Any suggestions would be appreciated.

Thanks,

3.ODBC Driver Source Example

4.genprint example in WDK

I am aware that there are a few threads on this topic already,
however, I still have some more questions that I think are unanswered
as I'm having trouble getting this example built and installing it to
explore what it is doing.

From the documentations, from what I understand, I'm supposed to build
genprint.dll using "build" in the build environment. In my case, I
have used the Windows XP x86 Free/Checked Build Environment. However,
no dll gets built, and I'm getting the following message.

C:\WinDDK\6001.18000\src\print\genprint>build
BUILD: Compile and Link for x86
BUILD: Loading c:\winddk\6001.18000\build.dat...
BUILD: Computing Include file dependencies:
BUILD: Start time: Tue May 13 10:43:55 2008
BUILD: Examining c:\winddk\6001.18000\src\print\genprint directory for
files to
compile.
    c:\winddk\6001.18000\src\print\genprint - 9 source files (7,549
lines)
BUILD: Saving c:\winddk\6001.18000\build.dat...
BUILD: Compiling c:\winddk\6001.18000\src\print\genprint directory
BUILDMSG: Warning : The sample c:\winddk\6001.18000\src\print\genprint
is not va
lid for the current OS target.
BUILD: Linking for c:\winddk\6001.18000\src\print\genprint directory
BUILD: Finish time: Tue May 13 10:43:56 2008
BUILD: Done

The next step, from what I can understand, is copy genprint.dll into a
Windows systems directory and build a simple program that uses
AddPrintProcessor to install the printer without the inf file, but
I'll ask about that another day.

My question is what exactly is going on with WDK refusing to link.
Thanks.

5.CPSUISAM example and Printer Property Sheet in General

I have the following questions after going through the CPSUI example and what 
I have for my printer driver so far:

For the CPSUI example
1.	in SetupComPropSheetUi , Do I have to use a COMPROPSHEETUI structure for 
using treeview rather than PROPSHEETPAGE structure?
in the TVTestCallback of the CPSUISAM
2.	what does 鈥淐PSUICB_REASON_OPTITEM_SETFOCUS鈥?mean by "input focus"?
3.	Does the switch-cases on DMPubID look at the range box values and other 
drop-down menus + yes/no conditions?
In general:
4.	Does DrvDocumentPropertySheets and DrvDevicePropertySheets have to be 
implemented at the same time to ensure that the custom dialog data structure 
and the property sheet structures are working properly? What would you 
recommend on progressing on migrating the CPSUISAM example? Should I have 
somewhat an empty DrvDocumentPropertySheet and DrvDevicePropertySheet first, 
then fill in each structure one at a time? I don't feel confident about 
filling everything at the same time (or at least migrating everything on that 
example from the CPSUI setup callback onwards.

6. Where is the MSI-X example?

7. send buffers in ndis-wdm miniport example of wdk

8. Need simple C# USB driver example - communicating with slow device



Return to device driver

 

Who is online

Users browsing this forum: No registered users and 37 guest