Getting the ISP javascript file

If you're going to dig around in the files below be sure to have a backup of your Net Usage directory so you can copy everything back if needed. I'm going to assume an intermediate level of knowledge of computers and Windows for this blog. If I've glossed over too many parts please leave a comment and I will update the blog entry as required.

Information on each Australian ISP is recorded in the isps.js file. If you have installed an additional country pack it will be in a file called isps_xx.js where xx is a two letter country abbreviation. Don't go searching your computer for these files yet, you wont be able to find them because they have been stored in a JAR file.

There is heaps of information on the Internet about Firefox JAR and XPI files. To cut a long story short, the JAR and XPI files are just a normal ZIP file. Therefore if you want to get your ISP javascript files you need to rename your JAR files to a ZIP file and then extract the ISP javascript file you want to edit.

This is how it's done (on XP):

1. Go to the Firefox Profile in your Application Data directory by entering %AppData%\Mozilla\firefox\Profiles\ in the Run command on the Start Menu. Navigate to the Extentions directory in your profile. Mine is at

   C:\Documents and Settings\Gerard\Application Data\Mozilla\firefox\Profiles\8ndbqffi.default\extensions

2. Hit CTRL + F and find netusageitem.jar (if your are using an Additional ISP pack you will need to find netusageisps.jar)
3. In the Find Results window right click on the result and select Open Containing Folder. You should end up in your extensions chrome directory.
   
4. Copy the netusageitem.jar and call it netusageitem.jar.bak so you have a backup in case things go bad.
5. Now copy the netusageitem.jar file again but rename it netusageitem.zip
6. You should now have three files in your chrome directory netusageitem.jar.bak, netusageitem.zip and netusageitem.jar (if you are editing an Additional ISP pack you should have netusageisps.jar.bak, netusageisps.zip and netusageisps.jar)
   
   
7. I use Winzip so you may need to change the process slightly for your compression software. You want to extract the isps.js or the isps_xx.js file from the zip file you have just created. When you extract the file you will need to extract it with folder names. Using Winzip, double click on the netusageitem.zip file. You will be presented with a list of files in the zipfile. Click on isps.js and click the Extract button.
   
   
8. Now ensure the Extract to: path is the chrome path for your extension. Ensure the Selected files/folders is marked and Use folder names is ticked. Click Extract. Close Winzip.
   
   
   
   
9. The chrome folder you are in should now contain a content folder. In the content folder is the isps.js or isps_xx.js file you will need to edit.
   
   
   

I use notepad++ to edit my javascript files. It is small, free, has syntax highlighting and can open more than one file at a time. Open the javascript file and have a look. We still have some more setting up to do before we can start the editing process.

Parsing Errors

More often than not, Net Usage will sit there doing it's thing and you will not experience any problems with it. However, at some time the ISP will change their page and your meter may stop working.

You will know the meter is not working because it will display a white cross in a red circle.

When you hover your mouse over the meter it may indicate a "parsing error" has occurred. If the error is a parsing error a debug file should have been created in the Mozilla Profile directory. The full path to the profile directory on my computer is:

C:\Documents and Settings\Username\Application Data\Mozilla\Firefox\Profiles\8ndbqffi.default\

The easiest way to find the profiles directory on your computer is to click on the Windows Start button and click on Run... (alternatively press the Widows-Logo [] key and the R key at the same time). In the Run dialog enter the following command:

%AppData%\Mozilla\firefox\Profiles\

Then hit Enter. A window should be displayed with a folder named something like 8ndbqffi.default. Your folder name will be different, but it should be the right place. Double-click on the folder to open it and find the netusage_debug.txt file.

If the debug file is not there, go back to firefox and left click on the meter to get Netusage to fetch your data again. You will get another parsing error, then go back to the profiles directory and the netusage_debug.txt file should be there.

This is a normal text file but if you open it in notepad the line-breaks will not be displayed correctly. If you want to see what's in the file, right click on the file and select "Open With" from the menu and then click on WordPad. I prefer a program called notepad++ but WordPad will do for just looking at the contents. Don't edit anything in this file, Critter need this file the way it is to work out why Net Usage is not working correctly.

Once you have finished looking at the contents of the debug file close WordPad and don't save any changes. To fix the problem you will need to email this file to Critter (his email address is at the bottom of the Net Usage homepage).