We are having strange issues with PWB loading up.
We currently have the .ini files and .exe files on a netware 6.5 server share. Roughly 150 computers use PWB to access the library catalog and internet.
We auto run the application on boot up to get around the problem but it can take anywhere from 2-4 minutes to load pwb after clicking the icon. We have all brand new equipment and a fiber backbone to the Novell server.
Is this something that could be cause with sharing the app from a netware share? Is there any troubleshooting we could try to rule out PWB? Thanks for any help you may provide.
Novell 6.5 and PWB v.2 loading issues
Moderators: Tyler, Scott, PWB v2 Moderator
There are a few things that can slow PWB loading. But 2 minutes is pretty excessive. Here are a few things that may help.
Are you using the Shellbar? A hard to resolve shortcut in the Shellbar folder can cause a delay while PWB tries to resolve it.
Are you using the URL or IP filter? PWB needs to read these files when it starts, and a large filter file can cause delays in loading.
PWB needs to read the INI file when it starts, the newer versions of PWB copy the INI file to a temporary file and read it from there to prevent access issue while parsing the file.
Using the full paths to the files in the INI file can help speed loading since PWB will not have to search for the files. Running PWB as the Windows shell can cause even more of a delay because the starting folder is random when PWB is used as the Windows shell.
--Scott
Are you using the Shellbar? A hard to resolve shortcut in the Shellbar folder can cause a delay while PWB tries to resolve it.
Are you using the URL or IP filter? PWB needs to read these files when it starts, and a large filter file can cause delays in loading.
PWB needs to read the INI file when it starts, the newer versions of PWB copy the INI file to a temporary file and read it from there to prevent access issue while parsing the file.
Using the full paths to the files in the INI file can help speed loading since PWB will not have to search for the files. Running PWB as the Windows shell can cause even more of a delay because the starting folder is random when PWB is used as the Windows shell.
--Scott
Thanks for the reply
Scott,
Thank you for the quick reply. We believe the slow loads are caused by a another software called Sam Access Manager (SAM) by Comprise technologies. They have a file called ieclear.exe that is attempting to clear the browser cache, but it is located on the server. We are working with Comprise to come up with a solution.
Thank you for the quick reply. We believe the slow loads are caused by a another software called Sam Access Manager (SAM) by Comprise technologies. They have a file called ieclear.exe that is attempting to clear the browser cache, but it is located on the server. We are working with Comprise to come up with a solution.
PWB can clear the cache itself. If you can disable the cache clearing in SAM you could let PWB do it when it closes.
--Scott
--Scott
Last edited by Scott on Tue Sep 09, 2008 1:42 pm, edited 1 time in total.
PWB loading slow with SAM
Scott is dead on. We had to disable the push of a SAM-related file known as clearie.exe. Once this was completed, PWB loaded right up...Scott wrote:PWB cacn clear the cache itself. If you can disable the cache clearing in SAM you could let PWB do it when it closes.
--Scott