Hi Curtis, Did you install the Lookup Term package? If so, that explains why Install Packages is now working for you, as per my explanation below. It was a guess that this might resolve the problem you encountered, so you can help me isolate the issue by trying both with and without Lookup Term installed. Remove it via the Add or Remove Packages dialog. Alternatively, temporarily rename the url2file.exe utility in your profile folder so that Install Packages does not find it.
Jamal On Mon, 11 Aug 2008, Curtis Delzer wrote: > Date: Mon, 11 Aug 2008 00:12:31 -0500 > From: Curtis Delzer <[EMAIL PROTECTED]> > Reply-To: [email protected] > To: [email protected] > Subject: Re: Updated Install Packages > > Hi, v3.4 solved my problem of updates showing that error line. > Thanks, though this may not be what it was about. :) > > Curtis Delzer > > At 01:15 PM 8/9/2008, you wrote: > >Version 3.4 automatically handles the type of package that stops and then > >restarts all scripts, such as GW Toolkit or Homer Shared Object. It also > >should reliably re-activate the Install Packages window after installing a > >package via the Window-Eyes Add or Remove Packages dialog. > > > >If you had trouble getting Install Packages to work before, try installing > >the Lookup Term package in addition. It installs a small utility called > >url2file.exe, which Install Packages will try to use if the default method > >for downloading a package fails. > > > >I invite feedback on how well these changes work. > > > >Jamal >
