Hello Matt,
On 27-Jun-02, you wrote: > > >> Case in point: Amiga.org. > > The memory cache seems not to be 100% reliably removing entries that > are obviously out of date: although when set to "once per session", > Voyager will *ONLY* check for new pages *ONCE* per *SESSION*. That > means you have to restart V to get it to re-read the page. > > Set it to Always, and it will always check, but sometimes Voyager > isn't keen on the result it gets back (perhaps the details it checks > of the page are no different.. so it cannot tell.. perhaps it simply > doesn't check the information it should..) I'm not sure what's going on, but I know at least on my machine Voyager will sometimes become unstable if I change Verify to either Always or Never. It was working great earlier until I tried to log in to my Amiga.org account. As soon as I did, however, I started getting alerts. After that, the machine decided to give up and reboot. A move that I was highly supportive of. :) (Verify was set to Always at the time. I'm going the safe route and stick with Once per Session.) > This was also reported last week or so on this very list wrt the > Expires: field :) Even though I did go through the posts for the last month, I don't recall seeing it. I was looking for something else at the time though. Still, it's a failure on my part. /me places dunce cap on head and sits in corner. :) Regards Steve -- MadGun68/Binary Assault - Http://home.attbi.com/~madgun68 My configuration: A1200T, BlizzardPPC 603e/240 '060/50, Mediator, Voodoo 3 3000, Realtek 8139B NIC, Soundblaster 128, Powerflyer Gold. _____________________________________________________________________ Voyager Mailing List - http://v3.vapor.com/ Voyager FAQ....: http://faq.vapor.com/voyager/ Listserver Help: mailto:[EMAIL PROTECTED]?Subject=HELP Unsubscribe....: mailto:[EMAIL PROTECTED]?Subject=UNSUBSCRIBE
