ID: 35875 Updated by: [EMAIL PROTECTED] Reported By: csaba at alum dot mit dot edu -Status: Open +Status: Feedback Bug Type: COM related Operating System: WinXP Pro PHP Version: 5.1.1 Assigned To: wharmby New Comment:
So, it's 7th of June, what about the tests? :) Previous Comments: ------------------------------------------------------------------------ [2007-04-11 21:00:21] csaba at alum dot mit dot edu Hi Andy, First, in case I haven't yet expressed appreciation for your examining the series of COM bugs I reported, a big THANK YOU to you. I appreciate it very much. I am currently traveling and not in a position to do the testing that you asked. Once I arrive back on about April 24, I will attend to carrying out the tests. Thanks, Csaba ------------------------------------------------------------------------ [2007-04-11 14:59:12] [EMAIL PROTECTED] Please try using this CVS snapshot: http://snaps.php.net/php5.2-latest.tar.gz For Windows: http://snaps.php.net/win32/php5.2-win32-latest.zip Hi Csaba, Is this still an issue for you with the latest level of PHP ? I have taken your supplied testcase and corrected the typo: popup ("In the catch")==> mypopup ("In the catch") to get it to run from command line and it runs as you describe; 2 pop-ups before IE is terminated and 2 after. Next I scheduled it to run with AT command and again all was OK. I ran it as both: AT 13:18 %comspec% "/K php <path.to.testcase>" and AT 13:18 /interactive %comspec% "/K php <path.to.testcase>" and both ran fine at the specified time; I just had to use Windows Task Manager in the first case to dispose of IE and so prompt the 3rd and 4th popups. Next I scheduled it using schtasks. On my Windows XP system I do have a user-id & password and I scheduled the task in 2 ways: schtasks /Create /SC once /TN schTest /TR "php.exe <path.to.testcase>" /ST 14:12:00 /RU "<computer name>\<id>" (and supplied password when promoted) and schtasks /Create /SC once /TN schTest /TR "php.exe <path.to.testcase>" /ST 14:15:00 /RU "System" and again both times the script ran at the specified time with all 4 pop-ups. Can you please re-try with latest PHP snapshot on your system and let me know the result. Regards Andy ------------------------------------------------------------------------ [2007-04-11 13:16:56] [EMAIL PROTECTED] Hi Wez, I will take a look at this one next Regards Andy ------------------------------------------------------------------------ [2006-01-03 14:11:45] [EMAIL PROTECTED] Assigned to the maintainer, don't expect any response. ------------------------------------------------------------------------ [2006-01-03 11:55:03] csaba at alum dot mit dot edu I have some additional information on this problem. If I schedule the php task using SchTasks as "Gabor", shown below, then the php script runs fine. In order to be able to do this on my single user, no password system I must first allow Scheduled Tasks to be run without password as described here: http://groups.google.com/group/microsoft.public.windowsxp.general/browse_frm/thread/c1b603be72394ee2/ Then, at the command window I type (on one wrapped line): C:\phpApps>schtasks /Create /SC once /TN schTest /TR "php.exe c:\phpApps\schTest.php" /ST 11:23:00 /RU "Gabor" Just to repeat the original problem: There is a discrepancy when scheduling (as SYSTEM - the default for AT) the php task vs. the vbscript task to do essentially the same thing. The php task errors when its created IE attempts to run code within the task while the vbscript task runs fine. Both scripts run fine when run directly from the command window. Csaba PS. The problem is also exhibited if I ask IE to call into PHP directly (via a PHP class) instead of directing it into a ScriptControl. I illustrated the method shown above because it is the direct analogue of the standard VBScript approach, but I can also provide a "pure" PHP way. However, in that case, when the script is scheduled as SYSTEM (via the AT command) the error is: Permission denied ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/35875 -- Edit this bug report at http://bugs.php.net/?id=35875&edit=1
