Hello,
as you all know, PDFCreator currently does not work properly under Windows Vista. The upcoming Version 0.9.5 will have basic Vista support, but the main problem has not been solved.
The problem is, that Vista has a strict security system, that does not allow the way PDFSpooler.exe tries to start PDFCreator under the context of a user.
Is there someone who has already done this under windows Vista?
We have the possibility to do this in C (not C# oder C++) oder in Visual Basic 6.
Any help, hints oder experience is appreciated here, as we have spent several days on this issue without a result.
We are offering a bounty of 150$ for the first one who can solve this.
regards,
Philip
Hi Philip,
I had to struggle just the same, but finally could solve the problem. What is happening is this:
Vista has a build in mechanism which - by ways unknown to me - checks each starting program if it might need administrative rights. This mechanism is not perfect and is the reason you see the Vista Security warning.
What you can do about it is to add the information to the executable what access rights are needed. This is done via the resource compiler rc.exe. You have to create a so called manifest file. This contains a section where the program access rights are defined:
uiAccess="false"/>
After compiling the resource file to a res file, this has to be implemented and compiled with your project. Vista then sees the manifest and does not use his checking mechanism.
If you need a step by step description, please come back to me. Since this discovery all my programs are behaving well under Vista.
Now, where can I dig up the bounty :-)
Cheers,
Martin
PS I have send you a mail with the coding via this forum....
Hello,
there is not this dialog showing up, that Other rights are required. The System user should have all rights and we have tried a manifest file, but that did not work as we hoped it would. Some forums said that the manifest must be sotred in the exe, some say that it musn't and that it has to be as as seperate file in the same folder. Both did not work for us :-(
Have you tried your solution?
regards,
Philip
Hi Philip,
Yes, I have tried it and it is working fine with two programs in a corporate environment.
Both applications are realized in VB6. The compiled manifest resource file is added to the VB6 project (so it is included in the executable, and this is the only way it should work).
So I am sure that we will get yours running as well.
Just to rephrase what we are talking about:
Under Vista, in an non-admin context, an application should start without any notification from the Vista UAC. It is assumed that the application is behaving accordingly, meaning:
- it does not write to the registry and if so only to the the HKCU hive
- it does not write to any file (e.g. ini) and if so only to ones located at the appropriate users settings folders (C:\users\...)
If your application is behaving like this, and you get notifications from the Vista UAC, then indeed this should be solvable by including a manifest.
Please confirm that the applications behaves like described above and tell me in what language the application is written. Have you seen the examples I send you via mail?
Cheers,
Martin
Hi Phillip,
I don't have a solution for you but can tell you what I did to get PDFCreator to run better in Vista. I am running PDFCreator 0.9.4 RC1. First I turned off the User Access junk then I installed PDFCreator. I had tried to turn off the User Access stuff while PDFCreator was installed but that seemed to have no effect.
After doing this I now only get a warning message in an "Interactive services dialog detection" window with the following content:
"A program can't display a message on your desktop
The program may need information or permission to complete a task.
Why does this happen?
-> Show me the message
-> Remind me in a few minutes
Program Details:
Program(s) or devices(s) requesting attention.
Message title: PDFSpooler
Program path: C:\PDFCRE~1\PDFSPO~1.EXE
Received: Today, September 13, 2007, 2:16:42 PM
This problem happens because of partial incompatibility with Windows Vista.
Please contact the program or device manufacturer(s) for more information."
This only happens once after a reboot of the machine. If I click on the "Show me the message", the screen will go black for a few seconds then reappear just as it was. No message has ever been shown to me. I can then close the warning message window and continue with my regular work. I can also just close the message warning window without trying to see the message and everything is OK. I can also ignore the message warning and it will hang around for a while then go away by itself and never come back. If I don't notice it right away it will lurk on the Windows Task Bar with a reddish color to it. Again after a while it just goes away.
I have never tried to click on the "Why does this happen?" link so I don't know what it says. Maybe next time I will try that.
I don't understand and probably never will. MS has done a horrible job of masking over their broken code with this layer of garbage code all in the name of making your computer safer from viruses. I don't think it helps and just gets in the way of great tools like PDFCreator. I am sorry you are having a tough time getting around this but I know you will succeed soon.
If you would like me to test something for you please let me know.
Bill Rich
Principal Consultant
Wilandra Consulting LLC
Hello,
no, that is not quite the problem we are facing.
We have a service (Print Spooler) which launches our PDFSpooler. The PDFSpooler should call PDFCreator under the users context. Therefore, it has to load the users environment to read the registry settings etc. This ist, where the API functions fail.
So it is not about User Account Control, but about the permission system, but we could not find out what it is exactly.
regards,
Philip
Hi!
That's not possible under VISTA.
Vista isolates services in a special Session 0.
http://www.microsoft.com/whdc/system/vista/services.mspx
(download the .doc at this page...)
The only solution is to start a process in the user session at logon (tray-icon), that communicates via inter process communication (Pipes, Sockets, Remoting, DCOM) with the service. This user session process can then start any other process within the users environment.
hth
cu
How do other PDF printers like FreePDF (http://www.shbox.de/fpx732.htm), NovaPDF (http://www.novapdf.com/) and CutePDF (http://www.cutepdf.com/) solve this problem? At least CutePDF also uses Ghostscript and is Vista ready, they say.
Can the 2 following links help you?
http://wwwbeta.microsoft.com/technet/technetmag/issues/2007/06/UAC/default.aspx?loc=en
http://www.codeproject.com/useritems/UAC__The_Definitive_Guide.asp
Best regards, and good luck !
Rolf
From what I can tell, the UltraVNC team has struggled with similar issues. See http://www.uvnc.com/vista/
Their forum is at http://forum.ultravnc.info/viewforum.php?f=32
Found this, not even got Vista so can't test:
http://www.tweak-uac.com/programming/vista-elevator2/
Remote Applications have a similiar problem. Would this be helpful? http://www.uvnc.com/vista/
Here are some hints I come up with after reading some of your source code:
Most of the VNC servers for Windows seems to have similar problems regarding Session 0 on Vista, but UltraVNC seems to have worked around it recently. Probably worth taking a look to see what they did.
This may be a shot in the dark, but it seems to work for me.. although there may be some other permissions that I have set that allowed it to work.
On the printer setup for the PDFCreator Printer - Configure Port for the Printer (the port runs PDFSpooler.exe and redirects the Print Output to the PDFSpooler).. Then check "Run as User", then PDFSpooler.exe can start as a user, and the PDFCreator seems to work fine on Vista for me ?
Can anyone else try this out and let me know ?
If this works, all that needs to change in the installation of the printer.. everything else seems to work fine.
This work for me only on Business Edition of Vista and with an administrative user.
The bug remains on Home Edition or with not administrative users
Ciao
That fixed the annoying message that came up once after every reboot. I have tried two reboots so far and no message box about wanting to show me a message from pdfSpooler.
Bill Rich
Principal Consultant
Wilandra Consulting LLC
This solution worked for me as well, to set the printer port to "Run as User". I also did not get the typical message after a reboot. I am running Vista Home Premium with an admin account.
Adam
problem solved or?
cfbwlbzk http://smjoagwd.com csmilwhs hsfcbbgy lclxhqpc [URL=http://miikhmre.com]uazaymik[/URL]
The PDFCreator 0.9.4 RC1 works in Vista Bussiness, but befor printing on PDFCreator printer I must run PDFCreator.exe and leave it in a background. After that every document is converted to PDF :).
I have turned off User Account Control.
Printer drivers install as well :)
It will be nice to put in PDFCreator printer drivers put a command that will run PDFCreator.exe imeditly after print process begin. It is nice that PDFCreator.exe is addred defaulty to autostart/
greets.
Could someone from PDFForge.org post a status update as to what Vista problems have been solved and what ones need addressing? I would like to help with what is outstanding.
Fyi,
Darwin
DesktopEngineer.com
Since I don't have Windows Vista, can you post the error messages and information of the bugs occurred when using PDFCreator in Windows Vista please? I want to do research online.
vista does not allow writing to system directories.
temp files or writen to these directories.
vista does not allow writing to regitry.
except to the hkey_user, start_up info and other info is writen here wich is not allowed and there for not avalible.
it all in the installation and the use of files in retricted folders and retricted regitry entries.
The problem is in the program pdfspooler. This program is started by the printer service with the rights of the "LocalService".
pdfspooler uses the API LoadUserProfileA und this function fails only in Vista with the error message "A client has no rights.".
Please take a look at the program pdfspooler.
Frank
xqhlllpw http://wfjjlyhq.com qgehcige oryattml aktxlnyv [URL=http://jsisqjhl.com]zfcknoth[/URL]
Hi Philp
And idea is to put the pdfcreator.exe like a service.
All the new software (steam, ati install and so on) has a service for they can work well on vista.
¿ Why no take this funcionality for pdfcreator works ?
Regards
Victor
Sorry for my english. A'm from Ukraine.
Vista Home Premium. PDFCeator works correctly after settings:
Control Panel -> Printers -> PDFCreator -> Properties -> Ports -> Select port "PDFCeator" and click "Port Settings".Here check "Run as User" and save this.
Russian:
??? ?????????? ?????? PDFCreator ???? ??????????: ?????? ?????????? -> ???????? -> -> ???????? -> ????? -> ??????? ???? "PDFCeator" -> "????????? ????" -> ???????? ??????? "Run as user" ? ????????? ?????????.
still think it the file and reg. sharing that the problem.
vista will return success even when not.
vista uses virtual files and reg.
One app with higher uac will see system files where lower one sees virtual files which or diferent.
please see http://msdn2.microsoft.com/en-us/library/bb530410.aspx
Do not use the registry as an inter-process communication mechanism. Services and user applications will have different views of the key.
Remember that virtualized resources are per-user copies of global resources
[URL=http://vytcoflh.com]bafjsyxt[/URL] iqmgkawk http://zseopwru.com lgwukmxl kltmssdw utzlzxqw
I have some experience making apps Vista Compatible. I can be of help if you'd like. I believe what your looking for is to launch the UI portion as the interactive user and not local system which the port monitor is running as.
I've found this site rather useful:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=404082&SiteID=1
Take a look at the CreateProcessAsUser. Using WTSGetActiveConsoleSessionId and WTSQueryUserToken and DuplicateToken so you can launch the process as the appropriate user in the interactive users session.
I'm not clear on how your doing the IPC which could pose another issue.
Artur Sá Menezes - Webmaster / Designer / Computer Science.
wrotes::
THERE ARE NO PROBLEMS
===========
using PdfCreator under
Windows Vista Ultimate,
in my installations.
THUS, SOLVED, by observing this::
I generate 1 PostScript Level 3 file (color), using the previously configurated Xerox DocuColor 8000 PS3 WRITING TO FILE as output (no LPT, Bluetooth or Wi-Fi); from a page comming from a site using graphics and TTF fonts (Apple Computer site). I drag'n drop the resultant PostScript (PS) file to the list to be printed.
Result::
Well terminated, no problems, all right / all types of output (PDF, JPG, etc). I choose PDF as output under PdfCreator.
Important Note:: I allways use "Compatibility Mode", as my standard, to output PS (I do not use fast or other options). I can use A4, A3 and others, with any margins or orientations. All right. All works fine.
How can you get a problem? Tell me how, please.
_______________
Artur.
NOTE: If anyone want to know:: I have a double boot MBR system, with Win-XP Pro SP2 // Win-Vista Ultimate Pro. I can use other boots, like Kalango Linux (love it!), Ubuntu Linux, Win-98 or something I want, from my flash memory or MP4 player (both works as USB-FDD - see your BIOS). Since I put a boot there and be a FDD device, it works good -- it is similar to the way as virtual machines uses "ISO's machine mirrors with boot"(s), to start.
_______
End.
Vista Home Premium. PDFCeator works correctly after settings:
Control Panel -> Printers -> PDFCreator -> Properties -> Ports -> Select port "PDFCeator" and click "Port Settings".Here check "Run as User" and save this
............
This worked for me, thanks!
Edit: I guess I replied to the wrong thread, this method was posted above by xandyx
I just loaded (and I am not all that happy about it, but I'm biting the bullet..) Vista 64bit. One of the first things I installed is PDFCreator. As you'd guess, it wouldn't work.
I was also having a rough time getting my bluetooth dongle working because it didn't have M$ signed drivers. I found a site that recommended pressing F8 when windows first starts up (yes - where you'd find the choice to get into safe mode) to select "Disable driver signing verification". My bluetooth worked, and whaddayaknow - so does PDFCreator!
"Vista Home Premium. PDFCeator works correctly after settings:
Control Panel -> Printers -> PDFCreator -> Properties -> Ports -> Select port "PDFCeator" and click "Port Settings".Here check "Run as User" and save this"
Thanks much, this worked for me!
Adam
"Vista Home Premium. PDFCeator works correctly after settings:
Control Panel -> Printers -> PDFCreator -> Properties -> Ports -> Select port "PDFCeator" and click "Port Settings".Here check "Run as User" and save this"
Thanks much, this worked for me!
Adam
I just got my new PC with Vista Home Premium. UAC has been a bind for me in developing software even before I got my first Vista machine, but I'm keen on the idea in principal, so I don't want to disable it.
I always have PDF creator installed, and it has gone on Vista PDQ. ;)
After some fiddling I discovered that it works fine... so long as you have the PDFCreator.exe running (like you would do on a server setup), so I told it to run PDFCreator.exe (after many Error 0x00000001 and 0x000000aa messages) minimized after it received a print.
This worked peachy, and the errors were solved by enabling myself to change the sharing options of the not shared printer, and then not changing them.
Clear as mud, actually it just authenticates me as an interactive administrative user and not just some rogue script. I later discovered that I can also select "Run as Administrator -> Properties" to achieve the same thing, in no simpler or quicker a fashion, but at least this makes more sense.
Then I came back here to see what other's had suggested about the problem. I enjoyed the challenge, and since the bounty was up, I presumed nobody had a complete solution yet.
Adam seems to have pretty much the same solution as me. @Adam "Great Minds Think Alike" ;)
So, in very simple terms, the fix is...
I cannot reproduce your problem. I created a Vista basic user account and logged on to Vista but the PDFCreator seems to be working perfectly. I am running a Dell Lat C6oo with Vista Business 32bit with Office 2000 SR1 SP3. Granted it is a standalone with no Vista updates applied but I have not encountered any problems with PDFC 0.9.5 If you need any more info please contact me @ my email.
Hello,
(I have Microsoft Windows Vista Ultimate x64.)
It seems that the problem is the User Account Control restricting access. This program needs to run with administrator rights.
To do things with admin rights, many programs require elevation. You need to tell Vista to elevate each EXE file that needs administrator rights.
For each EXE file (only if they need it), create a file named the same as the EXE + ".manifest", e.g: "PDFSpooler.exe.manifest".
In the manifest file, copy the following:
______________________________________________________
<?xml version="1.0" encoding="utf-8"?>
<asmv1:assembly manifestVersion="1.0" xmlns="urn:schemas-microsoft-com:asm.v1" xmlns:asmv1="urn:schemas-microsoft-com:asm.v1" xmlns:asmv2="urn:schemas-microsoft-com:asm.v2" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<assemblyIdentity version="1.0.0.0" name="MyApplication.app"/>
<trustInfo xmlns="urn:schemas-microsoft-com:asm.v2">
<security>
<requestedPrivileges xmlns="urn:schemas-microsoft-com:asm.v3">
<!-- UAC Manifest Options
If you want to change the Windows User Account Control level replace the
requestedExecutionLevel node with one of the following.
Limited User:
<requestedExecutionLevel level="asInvoker" uiAccess="false" />
Administrator:
<requestedExecutionLevel level="requireAdministrator" uiAccess="false" />
Highest possible:
<requestedExecutionLevel level="highestAvailable" uiAccess="false" />
If you want to utilize File and Registry Virtualization for backward compatibility then delete the requestedExecutionLevel node just below:
-->
<!-- Change this -->
<requestedExecutionLevel level="requireAdministrator" uiAccess="false" />
<!-- ^ Change this ^ -->
</requestedPrivileges>
</security>
</trustInfo>
</asmv1:assembly>
______________________________________________________
Then, after you pick from the options I listed in the text above and delete the commands, embed the manifest file(s) into the corresponding EXE(s) when you compile it/them.
You might just choose what I put in for default:
______________________________________________________
<?xml version="1.0" encoding="utf-8"?>
<asmv1:assembly manifestVersion="1.0" xmlns="urn:schemas-microsoft-com:asm.v1" xmlns:asmv1="urn:schemas-microsoft-com:asm.v1" xmlns:asmv2="urn:schemas-microsoft-com:asm.v2" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<assemblyIdentity version="1.0.0.0" name="MyApplication.app"/>
<trustInfo xmlns="urn:schemas-microsoft-com:asm.v2">
<security>
<requestedPrivileges xmlns="urn:schemas-microsoft-com:asm.v3">
<requestedExecutionLevel level="requireAdministrator" uiAccess="false" />
</requestedPrivileges>
</security>
</trustInfo>
</asmv1:assembly>
______________________________________________________
I hope this helps! (And I also hope that I get the $150!)
Hi, I am not sure this will solve the problem but I found some code to launch an application under the context of a user in vista. I didn't tried it but it seems good.
Here is the link : http://www.codeproject.com/KB/vista-security/VistaSessions.aspx and more specifically look at the LaunchAppIntoDifferentSession() function.
I think you don't need the usermode application and the communication stuff.
I made it work just by running this single command after installation. Tested on both vista sp0 and sp1.
[quote]
start "" "%allusersprofile%\microsoft\windows\start menu\programs\startup\pdfcreator.lnk"
[/quote]
Keep the money. I want PDFCreator to work out of the box! :)
/KB
By disabling UAC PDF Creator works with no problems. I know this is not a solution, but it may be a valid workaround.
Maybe guys who report PDF Creator working fine are using Vista with UAC disabled.
By the way, after I disabled UAC and restarted Vista, PDF Creator started prompting me for the filenames of all the test pages I had sent previously (with UAC enabled). Definitely the problem is related to elevation.
Thanks.
never had any problems with pdf creator on vista but then again i also have the UAC (Vista Nagging) disabled
i found a similar software with same problem. bellows are two solutions. hope the info helps.
*******************************************************************
It seems there are two workarounds to get Primopdf 3.1 to work with Vista, Either
1. Turn off User Account Control and restart, or
2. Give full control to 'everyone' for the C:/Windows/Temp folder by right-clicking, choosing properties/security/edit, highlighting 'Everyone' and checking 'full control'. (If 'Everyone' is not visible, it can be added via Add/Advanced/Find Now).
Both worked for me, but the second allows you to keep user account control functioning.
*************************************
for more detail, http://forums.primopdf.com/showthread.php?p=3116
credit to them
I am having the same problems. I checked the log after an error occured and it stated problems with "redmonnt.dll". Windows then reported a spooler problem. And in the ptrinter record it showed that it was holding the document because there was no paper. No duh, Computer!!
I hope these hints might help but they are probably already known.
One hint from another user to set "run as user" didn't have any effect for me.
one other thing I noticed was that the printer in the background was "microsoft XPs print writer" normally I have my HP720c series here. I would like to know how to change this!! the field is only grayed and I can't get it back to black, in order to change this.
The problem started tuesday. Monday I printed a pdf with a password. since then I can't even get a .txt file to print correctly as a pdf.
good luck at bug hunting!!
bill
one more thing. I hit "reset all settings" to stop using the password for printing. ever since the settings screen comes up in english instead of german. my local setting!!
please help!!
Am Vista Problem arbeiten wir und sind bis jetzt gut vorangekommen. Was passiert wenn Du in den Einstellungen wieder die deutsche Sprache wählst?
Frank
hab der sprache wieder zurück, war nur überrascht darüber wenn man die Einstellungen zurück setzt. Aber am meisten wündere mich über der plätzliches Ausfall vom PDF creator.
Weiterhin viel glück!! Tolle Arbeit im ernst!!
Hi,
ist jetzt das Problem mit Vista gelöst, ohne die Vista UAC zu deaktivieren bzw. die PDFCreator.exe im Autorun zu halten?
grüße
aka
HI again, simple simon here,
I've been looking at some of these hints and trying simple things. I turned off the UAC and everything worked fine. When the UAC is on I have to open the monitor as Administrator to get PDFcreator to the next step. Windows does not automatically prompt me! Is this the problem you guys are working on?? PDFcreator having the proper authentication to start the spooler on its own? I have mylaptop only just over a month and haven't been able to get all the test versions upgraded yet! could some licsense be overdated and that's why my PDFcreator just stopped working one day. meaning windows thinks it is a hostile program and wants more authentication?
Have you all seen this? Would it help work around some of the Vista issues?
http://neosmart.net/blog/2008/ireboot-and-working-around-uac-limitations/
http://developers.slashdot.org/developers/08/04/27/2013215.shtml
hope this helps
Alan
you might want to ask the guys at neosmart how they did it, it seems they had the same problem and somehow found a way around the pesky UAC and its security model.
http://neosmart.net/blog/2008/ireboot-and-working-around-uac-limitations/
this surfaced today on slashdot and first thing i thought after reading it was PDF Creator :)
http://developers.slashdot.org/article.pl?sid=08/04/27/2013215
quote from neosmart:
===
The resulting application has an installer - which requires admin privileges, of course - which installs and launches the background service. The background service has full permission to do what we need to get operating system XXXX to be the default option for the next boot, but - in line with the Windows Service Model - cannot be interacted with by end users.
The installer also adds a normal UI application which sits in the taskbar (from where end-users may interact with and use iReboot) and communicates with the backend service via a custom API which must not require the execution of any privileged code. The service can do whatever it wants (well, whatever we want it to do, but lets not get picky here!), but the client program must only perform actions which normal, unprivileged users have permission to execute.
By using a standard inter-process communication API we avoided the need for any special actions on behalf of the client application, effectively separating logic (residing and executing on the backend service, free from the many limitations of UAC) and presentation/design (the client application, bound to obey UAC's every wish).
=====
details - this was not enough, just reporting that there was a security issue. The previous post about how neo**** did it is probably correct.
( search on Slashdot for it )
I also thought it might be a digital rights issue, and that putting in a dummy digital signature might work...
Oh well...
Hello,
I want to admit, that Microsoft describes a function with the name "CreateProcessAsUser" to start processes in user mode from Session0 (Session for Services).
Further informations can be found here:
http://msdn.microsoft.com/en-us/library/ms682429(VS.85).aspx
Best regards,
Andreas
Hi all,
I'm successfully using PDFCREATOR on my Vista Ultimate SP1
1 - I've modified the properties of the following files :
C:\Program Files\PDFCreator\PDFCreator.exe
C:\Program Files\PDFCreator\pdfenc.exe
C:\Program Files\PDFCreator\PDFSpooler.exe
2 - Right click -> 'properties' -> 'compliance' & I forced those EXE files to be runned as 'Windows XP SP2' programs.
3 - I rebooted my workstation and gotcha !!! PDFCREATOR is running perfectly...
I hope this help other users...
Thanks to PDFCreator team for this very good tool ;)
I am a novice at this -- would appreciate detailed explanation of how to do it.
so far I found :
I installed PDFCreator 0.9.5 in Vista 32bit with no installation problems.
One problem using --
PDFCreator or
PDFCreator-printMonitor
must be already running in order for Print to PdfCreator to work.
There are identical bugs in both XP and Vista=32bit when you try to:
1. Save as PNG (no file saved), and to BNP (large file saved which appears blank).
2. Save as JPG, and PCX get only p1 of multipage file
By contrast, e.g. "paperport" saves one JPG per page when saving multipage pdf as jpg's.
Any hints how to fix these?
Hi,
ich denke das ich die Lösung haben. Der Quellcode ist zwar in C# jedoch wird größtenteils die Win32 API verwendet. Dadurch ist es möglich diese Lösung auch für andere Programmiersprache verfügbar zu machen.
Vom Prinzip muss der Inhalt aus dem "\bin\Release" Order in das PDFCreator Verzeichnis kopiert werden und im "redmon EE Configuration" der Pfad auf die ausführebare Datei "PDFSpoolerEx.exe" umgebogen werden.
Funktioniert nicht nur unter einem Administrator sondern auch unter einem Gast Konto.
Link zum Quellcode samt ausführbarer Dateien:
http://rapidshare.com/files/122389632/PDFSpooler.zip
grüße
aka
Hello peter!
Well i think i might have the solution to your problems my friend...
the problem must be happening because of conflicts with the user account control thing on vista...
basically u just need to give administrator rights to run the especific task...
all you do is right click the shortcut for pdfcreator
click on the compatibility tab
and select run as administrator! that's it!
works perfectly
here's an image of the property change:
http://img156.imageshack.us/my.php?image=pdfcreatorsz3.jpg
i use windows vista business 32 bit original ;)
i trust in the future u will figure how to do that automatically ;)
best of luck and kind regards from new zealand
Marcio Cattini
Hi.
Not a programmer but I always thought this must be a user space problem because of the dialogue which pops up.
XP runs services and userspace0 in the same session.
Vista separates the service space from all user spaces.
New APIs are provided for the two spaces to talk.
Without the API no service can present a dialogue to a user in Vista.
Cant find where I read it but it was one of those supposedly exciting "What's new in the New upcoming Vista" articles by MS.
Hope this wasn't stupidly irrelevant.
Is the problem solved? Is there a fix? If so, what - exactly - is the solution?
Thanks
Hi:
First, I don't speak very well english.
Second, If the installation program put a link to the pdfcreator in the folder "start" (direction: Start-->All programs-->Start) program will work perfectly. I think than is a temporary solution. It's ok?
Please, try you and you say me.
Bye
A vida é cultura, e a cultura é libre
Life is culture, and the culture is free
This looks a lot like the behavior that Norton 2009 has introduced. Norton 2009, by default, detects that pdfspool.exe attempts to open the process id used by ccsvchst.exe, then blocks pdfspool.exe from completing it's mission. I have not looked at the source code, but maybe pdfspool.exe is looping through the process ids to get info and triggers a reaction from Vista, just like Norton's behavior. In Norton, you can suppress the behavior by turning off "Norton Product Tamper Protection". Maybe all that has to be done is to exclude some process ids from interrogation.
Another approach is shown in http://www.codeproject.com/KB/vista-security/VistaSessions.aspx
where the author demonstrates a way to launch the required application from a service into the current user session with local system account privileges. He goes on to say "The concept which I use is very straightforward. I have a normal user mode application which communicates with a service through custom messages. On receiving the custom message, the service will launch the requested application (that I want) under the system account. To get hold of a local system account I used the winlogon's token in the required session since winlogon.exe runs under the local system account. (In Vista, services are present in session 0 and the first user logs on in session 1 and so on, unlike in XP)."
I am working on it and near to solve this problem as i get 80% positive results of my work i turn in to programming line since i leave offering business web hosting service along with the cheap ecommerce web hosting because i thought to start something challenging in life so come to programming line to make some thing good and solve people problems, one of my friend who is still in the business of reseller hosting thinks that there is much better future so he remain there. every one has a different concept but i would like to be here working on vista and all up coming OS.