> On Monday, Decem1:55 AM Christian Kaiser wrote: > DEVMODE structure somewhere, and a failure to properly report this, but that's pure > Without seeing some code example, it is hard to guess I'd suspect a bad parameter int he Unfortunately, I can't offer more advice now than trying a google search. I will follow this thread and if any new information arises I'll add that > to set the error code for some kinds of printers. > It is not clear if the documentation is lying, or the CreateDC implementation is failing > I recall that in the past this problem has been cited, but I don't recall the resolution. > a DEVMODE to the API if it cannot be different from the default one,
> customers pass a modified DEVMODE and are quite happy). In my eyes, that sentence is nonsense (99.999% of our > DocumentProperties() of that printer), though modified (orientation > explain what that means? I do pass a valid DEVMODE (from > structure other than the current DEVMODE." - can somebody please > b) The docs for say "The function will return NULL for a DEVMODE > a) how can CreateDC() return NULL and GetLastError() of 0? This is not > - call like CreateDC("WINSPOOL", pszDriver, NULL, pDEVMODE), all > - other apps can print to that printer. > We have a customer who gets NULL as result of CreateDC() using a > On Friday, Novem9:31 AM Christian Kaiser wrote: I also tried overriding the default security settings of the process and set it to 'PROCESS_ALL_ACCESS' without any luck. The 32-bit process runs under an User-Account that has been granted Administrator privileges. I tried disabling the UAC feature on Windows 7 but it seems to make no difference. I also gave it a try on Vista 圆4, Windows 2008 V2 and confirmed that the behavior is consistent. While printing from other 32 bit apps using our 64 bit driver, the issue is not reproducible. Weirdly, this issue is only reproducible while printing from Adobe 32 bit PDFL Engine using our 64 bit driver. I could not find anything in the system or application logs as well. The CreateDC call returns NULL, but simultaneoulsy GetLastError also returns zero (not pointing to any error). I have a custom driver that tries to create a printer device context using CreateDC API from a 32-bit windows process. I have just run into an issue while printing from a specific 32 bit application engine using 64 bit driver on Windows 7.
0 kommentar(er)
