[wpkg-users] Some unknown never before seen error message while uninstall check
Hi All I get this error which I've never seen before on 1 host trying to wpkg-enable. 2009-02-11 08:36:51, DEBUG : Checking existence of package: ActiveState Perl 2009-02-11 08:36:51, ERROR : Error when searching registry sub-keys at 'HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall'|Code: 80004002; Descriptions: No such interface supported 2009-02-11 08:36:51, ERROR : Message: 'length' is null or not an object|Description: 'length' is null or not an object|Error number: 800a138f|Stack:undefined|Line: undefined| Greets Mike - wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] Special install command not working
Rainer Meier wrote: > Hi Mike, > > Mike Burgener wrote: >> echo yes | >> > \\server\wpkgsoftware\arm\rvds\Utilities\Installer\2.1\1047\win_32-pen >> ti um\wh.exe install -p RVDS --source %SOFTWARE%\arm\rvds\ --target >> "%programfiles%\ARM" --env SYSTEM regedit /s >> > \\server\pcsoft\install\pkgs\packages\registry\license_server_rvds.reg >> xcopy /E /Y "\\server\pcsoft\install\ARM_RVDS_301\MWPerlWin" >> > "%programfiles%\ARM\IDEs\CodeWarrior\CodeWarrior\5.7.0.1899\13\win_32- >> pe >> ntium\bin\Plugins" >> xcopy /E /Y "\\server\wpkgsoftware\arm\rvds\patches" >> "%programfiles%\ARM\RVCT\Programs\3.0\586\win_32-pentium" >> >> However, this seems not to work >> >> Installer waits for "echo yes |" input >> >> Kind regards and greets > > First of all .bat extension is not used since long time. You > should switch to .cmd extension. Ok, I will have a look at that. > > As I don't know the wh.exe tool and if it correctly works > when echoing "yes" to it I don't know if it is really hanging at this > specific line. However you can easily run your cmd script now > manually (without WPKG). Make sure it runs unattended before > continuing to run it via WPKG. When it works you might try again > using WPKG. I think I already tested it manually, but I will recheck, I have currently another bigger problem with wpkg, so this can wait. Thanks for help already Greets Mike > > br, > Rainer - wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
[wpkg-users] Problem installing VNC device driver
Hi all, Thank you by the excellent software. I have a interesting question that is taking me 2 weeks and I still can not solve it. When i install UltraVNC 1.0.2, it fails to install the video device driver that is needed to burn less CPU with UltraVNC. When i install it using the local administrator account, is runs fine, but when i install it using the SYSTEM user (that is used by the WPKG Service) the device appears in the display items, but it indicates a problem with the yellow color in it icon. It appears that it do not find the file drivers. This files, are already installed, at install device driver point, in the local disk. Someone have some light that can help me? Thank You. -- | | Joel Franco Guzmán .''`. | self-powered by : :' : | Debian Linux `. `' |at BraSil `- - wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] Stopping installations being called each time WPKGruns...
Hiya, I stand corrected ;-) > -Original Message- > From: wpkg-users-boun...@lists.wpkg.org [mailto:wpkg-users- > boun...@lists.wpkg.org] On Behalf Of k.e.jo...@bton.ac.uk > Sent: 11 February 2009 02:33 > To: Chris Wilcox > Cc: wpkg > Subject: Re: [wpkg-users] Stopping installations being called each time > WPKGruns... > > Hi, > > > -Original Message- > > From: wpkg-users-boun...@lists.wpkg.org [mailto:wpkg-users- > > boun...@lists.wpkg.org] On Behalf Of Tomasz Chmielewski > > Sent: 10 February 2009 22:06 > > To: Chris Wilcox > > Cc: wpkg > > Subject: Re: [wpkg-users] Stopping installations being called each > time > > WPKG runs... > > > > Chris Wilcox schrieb: > > > > > That gets me to my question - the commercial system I use will > never > > > initiate a package installation if the local and network ini file > > says > > > that the package is already installed. With WPKG, it seems you > MUST > > > specifiy conditions to prevent this occuring? Most of the software > I > > > use is educational stuff and is not listed in any of the WPKG > silent > > > installer pages - it can often be quite difficult to work out what > > > condition syntax to use to prevent installs repeating at each > > > workstation boot - MSI's handle this a little better as they don't > > > normally repeat the whole install, but many exe based installations > > > insist on re-installing even if the app is already on. > > > > > > Am I missing something obvious here? Should WPKG try to repeat > > installs > > > at every boot if the package does not have any condition syntax? > > > > You missed this one: > > > > http://wpkg.org/Execute_once_/_always > > > > Does it solve your problem? > > > > > > Hi Tomasz, > > I'm not entirely sure Chris meant that. I think he was talking more > about the general > complexity of package definitions as a whole. > > Hi Chris, > > Most commercial systems rely on solely on getting a clean exit from an > install and > then updating their files to say software is installed. In an ideal > world this is totally > correct and just "works". In an un-ideal world, just because an > installer says it worked, > it's not necessarily true that it worked the way you expected. I see > what you mean but in > some ways you're highlighting a problem with the commercial systems. > They don't "check", > they make assumptions... > > WPKG hedges its bets because, quite frankly, dumb things happen. > Installers can sometimes > screw up without appearing to fail and if they don't re-check things > you > also run the risk > of admins and power users fiddling with stuff behind their backs. > > The "checks" are simple tests to look for some key registry entry, > file > or other thing to > verify if a package is installed or not. It's kept flexible so WPKG can > be a general launcher > of software and not just installers but you can also put more checks in > to handle power users > and admins playing with things. > > I have to admit working out the "checks" to confirm something is > installed can be a pain > but it is literally a precautionary test to check if software got > installed. I generally > only use the "uninstall" key check to confirm things. I've rarely used > the other checks > because most people fear my wrath if they play around with their > systems > ;-) > > The things is, as you quite rightly say, WPKG *always* performs these > checks. I don't think > anyone has queried that before and that's a bonofide comment. I'm > wondering if you really > could streamline WPKG to not need checks... hrmmm... It's worth > thinking > about! I'll try > and do some groundwork for the devs and see if I can make a case for it. > And ...and here I'm corrected ! As Rainer says, if you don't supply checks... no checks are made... doh! Back to reading the code again! Keith > I come from an educational background too. Even worse, we teach > "Business" here so the software > is expensive and full of copyright protections! If you'd seen the utter > rubbish with activation > keys, internet activation and registration dialogs our software throws > up you'd understand why > I'm glad I've got WPKG to play with! > > I've tried just about everything from repackaging software, making my > own self-healing MSIs, > using AutoIt (to automate keypresses) through to fighting old > InstallShield setups and recording > response files to replay to it. Installers are just nuts nowadays! > > I agree totally with you on the MSI front. MSI's are a much cleaner > way > of installing software. > I also have to admit that they're a right pain to write correctly! MS > has not approached > MSI with an idea of making it simple! > > Ho hum, > > Anyway, I'd better get back to other things... > > Have fun, > > Keith > > > > > > -- > > Tomasz Chmielewski > > > > > --- > > -- > > wpkg-users mailing list archives >> > > http://lists.wpkg.org/pipermail/wpk
Re: [wpkg-users] Stopping installations being called each time WPKG runs...
Hi, > -Original Message- > From: wpkg-users-boun...@lists.wpkg.org [mailto:wpkg-users- > boun...@lists.wpkg.org] On Behalf Of Tomasz Chmielewski > Sent: 10 February 2009 22:06 > To: Chris Wilcox > Cc: wpkg > Subject: Re: [wpkg-users] Stopping installations being called each time > WPKG runs... > > Chris Wilcox schrieb: > > > That gets me to my question - the commercial system I use will never > > initiate a package installation if the local and network ini file > says > > that the package is already installed. With WPKG, it seems you MUST > > specifiy conditions to prevent this occuring? Most of the software I > > use is educational stuff and is not listed in any of the WPKG silent > > installer pages - it can often be quite difficult to work out what > > condition syntax to use to prevent installs repeating at each > > workstation boot - MSI's handle this a little better as they don't > > normally repeat the whole install, but many exe based installations > > insist on re-installing even if the app is already on. > > > > Am I missing something obvious here? Should WPKG try to repeat > installs > > at every boot if the package does not have any condition syntax? > > You missed this one: > > http://wpkg.org/Execute_once_/_always > > Does it solve your problem? > > Hi Tomasz, I'm not entirely sure Chris meant that. I think he was talking more about the general complexity of package definitions as a whole. Hi Chris, Most commercial systems rely on solely on getting a clean exit from an install and then updating their files to say software is installed. In an ideal world this is totally correct and just "works". In an un-ideal world, just because an installer says it worked, it's not necessarily true that it worked the way you expected. I see what you mean but in some ways you're highlighting a problem with the commercial systems. They don't "check", they make assumptions... WPKG hedges its bets because, quite frankly, dumb things happen. Installers can sometimes screw up without appearing to fail and if they don't re-check things you also run the risk of admins and power users fiddling with stuff behind their backs. The "checks" are simple tests to look for some key registry entry, file or other thing to verify if a package is installed or not. It's kept flexible so WPKG can be a general launcher of software and not just installers but you can also put more checks in to handle power users and admins playing with things. I have to admit working out the "checks" to confirm something is installed can be a pain but it is literally a precautionary test to check if software got installed. I generally only use the "uninstall" key check to confirm things. I've rarely used the other checks because most people fear my wrath if they play around with their systems ;-) The things is, as you quite rightly say, WPKG *always* performs these checks. I don't think anyone has queried that before and that's a bonofide comment. I'm wondering if you really could streamline WPKG to not need checks... hrmmm... It's worth thinking about! I'll try and do some groundwork for the devs and see if I can make a case for it. I come from an educational background too. Even worse, we teach "Business" here so the software is expensive and full of copyright protections! If you'd seen the utter rubbish with activation keys, internet activation and registration dialogs our software throws up you'd understand why I'm glad I've got WPKG to play with! I've tried just about everything from repackaging software, making my own self-healing MSIs, using AutoIt (to automate keypresses) through to fighting old InstallShield setups and recording response files to replay to it. Installers are just nuts nowadays! I agree totally with you on the MSI front. MSI's are a much cleaner way of installing software. I also have to admit that they're a right pain to write correctly! MS has not approached MSI with an idea of making it simple! Ho hum, Anyway, I'd better get back to other things... Have fun, Keith > > -- > Tomasz Chmielewski > > --- > -- > wpkg-users mailing list archives >> > http://lists.wpkg.org/pipermail/wpkg-users/ > ___ > wpkg-users mailing list > wpkg-users@lists.wpkg.org > http://lists.wpkg.org/mailman/listinfo/wpkg-users - wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] Stopping installations being called each time WPKG runs...
On 2/10/09, Rainer Meier wrote: > > Most of them can be worked around by installing them on a reference > system (or virtual machine) and just re-package them with 7-zip self > extractor or similar. Then crate a small batch script whcih is silently > extracting it, registering some DLL or adding registry keys. Removing is > simple: Just delete the program directory. Whenever I encounter installers like this or even when I would rather not deal with installers in particular situations, I use UniExtract to extract the application files from the installer (works pretty good for many different types and versions of installers). This saves you from having to install them just to obtain the necessary files. Also, the tool seems to extract installer scripts and such too. You can look at those to see what other changes it makes to the system (registry, etc) and then make those appropriate changes manually when creating the batch/cmd files to do the installation. - wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] Special install command not working
Hi Mike, Mike Burgener wrote: > echo yes | > \\server\wpkgsoftware\arm\rvds\Utilities\Installer\2.1\1047\win_32-penti > um\wh.exe install -p RVDS --source %SOFTWARE%\arm\rvds\ --target > "%programfiles%\ARM" --env SYSTEM > regedit /s > \\server\pcsoft\install\pkgs\packages\registry\license_server_rvds.reg > xcopy /E /Y "\\server\pcsoft\install\ARM_RVDS_301\MWPerlWin" > "%programfiles%\ARM\IDEs\CodeWarrior\CodeWarrior\5.7.0.1899\13\win_32-pe > ntium\bin\Plugins" > xcopy /E /Y "\\server\wpkgsoftware\arm\rvds\patches" > "%programfiles%\ARM\RVCT\Programs\3.0\586\win_32-pentium" > > However, this seems not to work > > Installer waits for "echo yes |" input > > Kind regards and greets First of all .bat extension is not used since long time. You should switch to .cmd extension. As I don't know the wh.exe tool and if it correctly works when echoing "yes" to it I don't know if it is really hanging at this specific line. However you can easily run your cmd script now manually (without WPKG). Make sure it runs unattended before continuing to run it via WPKG. When it works you might try again using WPKG. br, Rainer - wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] Stopping installations being called each time WPKG runs...
Hi Chris, Chris Wilcox wrote: > That gets me to my question - the commercial system I use will never > initiate a package installation if the local and network ini file says > that the package is already installed. With WPKG, it seems you MUST > specifiy conditions to prevent this occuring? This is partially true. If a package is "new" and has never been applied to a host (ie the package does not exist within local "%systemroot%\systrem32\wpkg.xml" then WPKG will first run the defined checks to check if the package is already installed. If it is installed, then WPKG will just add this information to wpkg.xml and no installation command is performed at all. But if the checks yield that the software is not installed yet (or there are no checks defined at all) then WPKG will run the install commands and then re-execute the checks to see if the package is now properly installed. One main difference to your "commercial system" I see is that WPKG is able to re-run the checks on each run to verify that the package is still properly installed (assuming that proper checks are defined). So it is true that you must specify a decent set of checks to allow WPKG to detect that a package is already installed in case the package is already there when WPKG is first run. If these checks do not exist WPKG will run the installation to make sure the package is installed. Assuring proper state of the target machine(s) is one of the most important attributes of a software deployment system. Such a system is quite useless if it allows the state to report a working installation without verifying it. This could leave a client in a broken state without even giving any notification to the administrator. So if WPKG reports that the package is properly installed then it IS VERIFIED AND PROPERLY INSTALLED. One more word about specifying no checks at all. This means WPKG will install the package and then assume it's installed (without further verification on next run). WPKG in this case only re-executes a command if the package version is increased (upgrade) or the package is removed from the profile (uninstall). > Most of the software I > use is educational stuff and is not listed in any of the WPKG silent > installer pages - it can often be quite difficult to work out what > condition syntax to use to prevent installs repeating at each > workstation boot - MSI's handle this a little better as they don't > normally repeat the whole install, but many exe based installations > insist on re-installing even if the app is already on. No problem here. I use some educational sites as well where specific educational software is deployed. It's true that most of these installers are totally useless and do not allow silent installations. Most of them can be worked around by installing them on a reference system (or virtual machine) and just re-package them with 7-zip self extractor or similar. Then crate a small batch script whcih is silently extracting it, registering some DLL or adding registry keys. Removing is simple: Just delete the program directory. The checks of course cannot refer to uninstall entries then but instead a simple check on file existence (main program binary) or file version are decent checks. As written above adding a decent check for file existence (main program binary) prevents WPKG to re-install the program even if WPKG is run for the first time. WPKG will log that it starts installation and then runs the checks to find that the application is already on the system. No re-installation will be done. > Am I missing something obvious here? Should WPKG try to repeat installs > at every boot if the package does not have any condition syntax? Yes, you're missing something. As written above WPKG will install the package only once if there are no checks at all. If there are correct checks defined then even the first installation can be skipped if the application is already on the system. br, Rainer - wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] Special install command not working
Mike Burgener schrieb: >> cmd /C echo yes | \\server\installer.bat > > My package command now looks like that: > > /> >> Also, for simplicity, you could place all that in one script >> (your installer.bat). > Ok. I made this and my .bat now looks like that: > > echo yes | > \\server\wpkgsoftware\arm\rvds\Utilities\Installer\2.1\1047\win_32-penti > um\wh.exe install -p RVDS --source %SOFTWARE%\arm\rvds\ --target > "%programfiles%\ARM" --env SYSTEM > regedit /s > \\server\pcsoft\install\pkgs\packages\registry\license_server_rvds.reg > xcopy /E /Y "\\server\pcsoft\install\ARM_RVDS_301\MWPerlWin" > "%programfiles%\ARM\IDEs\CodeWarrior\CodeWarrior\5.7.0.1899\13\win_32-pe > ntium\bin\Plugins" > xcopy /E /Y "\\server\wpkgsoftware\arm\rvds\patches" > "%programfiles%\ARM\RVCT\Programs\3.0\586\win_32-pentium" > > However, this seems not to work > > Installer waits for "echo yes |" input What command does wait for "yes"? Just test your script in cmd.exe window. If it works there, it should work with WPKG as well. Also, are you sure it waits for "yes"? You use different server shares, can it be a permission problem there? -- Tomasz Chmielewski http://wpkg.org - wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] Stopping installations being called each time WPKG runs...
Chris Wilcox schrieb: > That gets me to my question - the commercial system I use will never > initiate a package installation if the local and network ini file says > that the package is already installed. With WPKG, it seems you MUST > specifiy conditions to prevent this occuring? Most of the software I > use is educational stuff and is not listed in any of the WPKG silent > installer pages - it can often be quite difficult to work out what > condition syntax to use to prevent installs repeating at each > workstation boot - MSI's handle this a little better as they don't > normally repeat the whole install, but many exe based installations > insist on re-installing even if the app is already on. > > Am I missing something obvious here? Should WPKG try to repeat installs > at every boot if the package does not have any condition syntax? You missed this one: http://wpkg.org/Execute_once_/_always Does it solve your problem? -- Tomasz Chmielewski - wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] Quiet on the list?
Chris Wilcox schrieb: > No e-mail from the list since the middle of last week? Is it just me? Looks like something needed a kick... Should be working now. -- Tomasz Chmielewski http://wpkg.org - wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
[wpkg-users] [Bug 143] New: Feature: Other Protocols than samba
http://bugzilla.wpkg.org/show_bug.cgi?id=143 Summary: Feature: Other Protocols than samba Product: WPKG Version: other Platform: PC OS/Version: All Status: NEW Severity: enhancement Priority: P3 Component: wpkg.js AssignedTo: man...@wpkg.org ReportedBy: flor...@lagg.at QAContact: wpkg-users@lists.wpkg.org Hi, is there a possibility to support other protocols than samba? I currently think of using an HTTP/FTP Site where the packages are hosted. This would scale much better for me as I think of offering automated installation services to my customers. Thanks for your comments. -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug. - wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
[wpkg-users] Quiet on the list?
No e-mail from the list since the middle of last week? Is it just me? Chris _ Windows Live Messenger just got better .Video display pics, contact updates & more. http://www.download.live.com/messenger- wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] Special install command not working
Tomasz Chmielewski wrote: > Mike Burgener schrieb: >> Hi guys >> >> Thanks for all the help already. >> >> This special install command does not succeed. >> >> Any suggestions? >> >> > > As some "DOS" commands are not executables, you have to start > them with cmd.exe interpreter: > > cmd /C echo yes | \\server\installer.bat My package command now looks like that: > > Also, for simplicity, you could place all that in one script > (your installer.bat). Ok. I made this and my .bat now looks like that: echo yes | \\server\wpkgsoftware\arm\rvds\Utilities\Installer\2.1\1047\win_32-penti um\wh.exe install -p RVDS --source %SOFTWARE%\arm\rvds\ --target "%programfiles%\ARM" --env SYSTEM regedit /s \\server\pcsoft\install\pkgs\packages\registry\license_server_rvds.reg xcopy /E /Y "\\server\pcsoft\install\ARM_RVDS_301\MWPerlWin" "%programfiles%\ARM\IDEs\CodeWarrior\CodeWarrior\5.7.0.1899\13\win_32-pe ntium\bin\Plugins" xcopy /E /Y "\\server\wpkgsoftware\arm\rvds\patches" "%programfiles%\ARM\RVCT\Programs\3.0\586\win_32-pentium" However, this seems not to work Installer waits for "echo yes |" input Kind regards and greets Mike - wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
[wpkg-users] Stopping installations being called each time WPKG runs...
Hi all, I'm used to a commercial package allocation tool which behaves a little differently to WPKG in respect of how it decides if a package is installed or not. The package install commands are, like WPKG, all held in network based ini files. Each workstation has a network based and local based ini file. The network based ini file gets updated if the management tools allocate/de-allocate/re-allocate a package. The local ini file contains details relating to the last time the application installer tool checked for new package commands e.g.1) Allocate a package to PC1, ini file on network has new line added: Flash10 = INSTALL_PENDING 2) On reboot, workstation checks it's own ini file against network one and spots new line 3) Workstation checks the package ini file for Flash10 and installs the package according to the install commands 4) Workstation updates it's own ini file with line: Flash10 = INSTALLED 5) Workstation alters line in network ini file with the line: Flash10 = Installed If a package install fails then the line would instead read: Flash10 = INSTALL_FAILED The install ini file for each package can then be altered however you wish and you know each workstation will always use the latest version of this file. It also makes it a little easier to track installed/failed packages centrally. That gets me to my question - the commercial system I use will never initiate a package installation if the local and network ini file says that the package is already installed. With WPKG, it seems you MUST specifiy conditions to prevent this occuring? Most of the software I use is educational stuff and is not listed in any of the WPKG silent installer pages - it can often be quite difficult to work out what condition syntax to use to prevent installs repeating at each workstation boot - MSI's handle this a little better as they don't normally repeat the whole install, but many exe based installations insist on re-installing even if the app is already on. Am I missing something obvious here? Should WPKG try to repeat installs at every boot if the package does not have any condition syntax? Chris _ Windows Live Messenger just got better .Video display pics, contact updates & more. http://www.download.live.com/messenger- wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
[wpkg-users] PDF to Word Doc Converter v1.1
Has anyone gotten PDF to Word Doc Converter v1.1 at www.hellopdf.com to work with WPKG? I've tried every flag listed at http://www.appdeploy.com/articles/commandline.asp as well as googled for a silent install method for it and no luck, it still puts up a dialog box asking yes/no to if you want to install it. Has anyone gotten it to silently install or can recommend another free pdf to word converter? - wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
