Has anyone else experienced problems with Reference USA under PWB? Currently, all copies of PWB we have running will give an error message (PWB error message for "Activity.txt") when a person attempts to print pages from Reference USA. If you leave print page up for more than a moment, it then CRASHES PWB 2.04 entirely. Workstations experiencing this problem are running Windows 2000, and use PWB 2.04, and have basic URL.txt limiting in effect for access to the hard drive.
I'm assuming it's possible Reference USA is attempting to access the hard drive when printing... I also tried recording the history while doing this to see what was loading and saw something like "res://c://winnt/shocdlc.dll" loading at the point a person clicks either the Ref USA Print button, or ANY PWB button.
Please advise. Let me know if more info will help sort this out.
Reference USA
Moderators: Tyler, Scott, PWB v2 Moderator
-
mmcevoy
More Information on Ref USA
More information on this topic:
The problem appears to be URL.txt based. Reference USA for one reason or another attempts to access the hard drive (file://c://winnt/system32/shdolc.dll) when a person attempts to go BACK from the Print Screen either by means of a javascript "back" button at the bottom of the print screen, or via the PWB back button. Sometimes, it simply crashes PWB.
I can find no explanation for this behavior. Any help would be appreciated.
The problem appears to be URL.txt based. Reference USA for one reason or another attempts to access the hard drive (file://c://winnt/system32/shdolc.dll) when a person attempts to go BACK from the Print Screen either by means of a javascript "back" button at the bottom of the print screen, or via the PWB back button. Sometimes, it simply crashes PWB.
I can find no explanation for this behavior. Any help would be appreciated.
-
mmcevoy
This may not be a PWB problem afterall... InfoUSA contacted me in regards to the problem and had this to say:
We are in the process of revamping the manner in which ReferenceUSA.com prints, changing this action from a JavaScript to a simple html call which more than likely will correct this issue. We have encountered several other similar issues which has prompted us to
modify this portion of the site. As for an eta on the fix, I am uncertain as to when we will roll this change live as our developers are working on it as we speak.
Therefore, I assume that the problem is just the sites code. So if anyone else is having this problem, please note that InfoUSA appears to be working on it.
We are in the process of revamping the manner in which ReferenceUSA.com prints, changing this action from a JavaScript to a simple html call which more than likely will correct this issue. We have encountered several other similar issues which has prompted us to
modify this portion of the site. As for an eta on the fix, I am uncertain as to when we will roll this change live as our developers are working on it as we speak.
Therefore, I assume that the problem is just the sites code. So if anyone else is having this problem, please note that InfoUSA appears to be working on it.