Ancestry.com problems

For general issues related to PWB v2.

Moderators: Tyler, Scott, PWB v2 Moderator

Post Reply
blaforest
Observer
Observer
Posts: 3
Joined: Thu Mar 16, 2006 7:42 pm

Ancestry.com problems

Post by blaforest »

Hello all. I have a little problem. I am currently using PWB version 2.09 in shell mode using Windows XP Professional. I am having trouble getting the Enhanced Image Viewer to function at all with PWB. Every time I attempt to load the applet it says Error Processing Image Request. It works fine with IE and I have ruled out Group Policy getting in the way so now I'm lost. Has anyone else encountered this issue and if so what did you do to fix it? I am about to pull the last remaining bit of hair out of my head!! Thanks in advance.

Scott
Site Admin
Site Admin
Posts: 2539
Joined: Mon Dec 16, 2002 12:31 pm
Location: Rochester, MN
Contact:

Post by Scott »

The only problem we are aware of with Ancestry.com is the the page starts out in Full Screen view and after exiting Full Screen view it will not go back into Full Screen view, otherwise the site seems to function.

We are currently working on the Full Screen problem, but repeated attempts to contact Ancestry.com have gone unanswered.

Please send a copy of your INI file to support@teamsoftwaresolutions.com and we can test it.

--Scott

blaforest
Observer
Observer
Posts: 3
Joined: Thu Mar 16, 2006 7:42 pm

Post by blaforest »

It has something to do with my .ini config. I am currently troubleshooting this by process of elimination to find out which setting is giving me grief.

Scott
Site Admin
Site Admin
Posts: 2539
Joined: Mon Dec 16, 2002 12:31 pm
Location: Rochester, MN
Contact:

Post by Scott »

If you want to send the INI file I can certainly help in the touble shooting.

--Scott

blaforest
Observer
Observer
Posts: 3
Joined: Thu Mar 16, 2006 7:42 pm

Post by blaforest »

I figured it out. The problem is that I was using a non-existant proxy server(0.0.0.0) and exceptions to control website access. While it works fine for general purpose, it causes minor issues like this. I opted instead to use the url.txt file to filter access. Works like a charm.

I have to say that PWB is the best thing since sliced bread when it comes to securing public access terminals. Love it.

Post Reply