I have the same experience with relaunch window-eyes script not working. It shuts down window-eyes but does not relaunch. Using we7.01, xp Pro Sp3 Jeff Weiss
-----Original Message----- From: Paul Henrichsen [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 04, 2008 12:17 PM To: [email protected] Subject: RE: Updated packages Hi, Jamal. I saw that you had a new relaunch window-eyes script, but it still doesn't work for me. I have tried it both on an xp laptop and on a vista desktop. In both cases, after pressing windows backslash once then again, window-eyes unloads, but never reloads. Just thought you might like to know. -----Original Message----- From: Jamal Mazrui [mailto:[EMAIL PROTECTED] Sent: Monday, November 03, 2008 2:36 PM To: [email protected] Subject: RE: Updated packages Thanks, Chip! Besides maintenance releases, let me mention some recent script enhancements as follows: The Install Packages script now has a Get Files button (Alt-G). It prompts for a download folder, defaulting to the user profile folder. It then downloads all packages (.wepm files) to that folder from the current list. Thus, you can download all packages to a folder if you choose the All filter first. The folder path is remembered between invocations. This may be useful if you want to save package files on disk, since the Install button deletes a pckage from a temporary folder after installation. You can rename a package, e.g., to include its version number, as long as you keep the .wepm extension (Window-Eyes gets the package name from inside the package, not from the file name). The Build Packages script now updates the version number in the package if the convention is used of storing that number in a .xml file with a tag called either ScriptVersion or Script_Version. Thus, you can initially create a package with component files (typically .vbs and .xml), filling in the initial version number, package information, and license text. For subsequent versions, you can refresh the package so that it updates with files with the same names in the user profile folder, and increments the version number to the new one you put in the XML file. Jamal On Mon, 3 Nov 2008, Chip Orange wrote: > Date: Mon, 3 Nov 2008 10:31:12 -0500 > From: Chip Orange <[EMAIL PROTECTED]> > Reply-To: [email protected] > To: [email protected] > Subject: RE: Updated packages > > And keep the great work coming! > > Thank you from one more person! > > Chip > > > > > > ------------------------------ > > Chip Orange > Database Administrator > Florida Public Service Commission > > [EMAIL PROTECTED] > (850) 413-6314 > > (Any opinions expressed are solely those of the author and do not > necessarily reflect those of the Florida Public Service Commission.) > > > > -----Original Message----- > > From: Jamal Mazrui [mailto:[EMAIL PROTECTED] > > Sent: Friday, October 31, 2008 6:27 PM > > To: [email protected] > > Subject: Updated packages > > > > I have updated several packages based on error reports that were > > submitted. Be assured that the reports are reaching me and > > that I read > > each one. > > > > These are bug fix releases, trying to make a script work more > > reliably in > > the ways described by the documentation, or if a problem > > occurs, to abort > > the task gracefully rather than crashing. > > Keep the reports coming! > > > > Regards, > > Jamal > > > > > __________ Information from ESET Smart Security, version of virus signature database 3580 (20081103) __________ The message was checked by ESET Smart Security. http://www.eset.com __________ Information from ESET Smart Security, version of virus signature database 3583 (20081104) __________ The message was checked by ESET Smart Security. http://www.eset.com
