Forum Discussion
Usage meter javascript error
A javascript error occured in the main process. Uncaught exception: Error: Error parsing your configuration file: [C:\Users\Vampy\AppData\Roaming\HughesNet Usage Meter\status-meter.config]: Unexpe...
The following fix for the Javascript error won't cripple your computer. Just don't delete anything other than what's described in the instructions. Regarding Windows, you'll probably have to change your folder options to be able to view Hidden Items to see the AppData folder and its contents described in the directions. To do so, click "View", then check the box for "Hidden Items", as you see in the red boxes in the picture below. When you're finished with the procedure, uncheck "Hidden Items" so they are hidden again, as they are hidden by default for a reason. If you have a Mac, I'm not sure if you have to unhide anything.
The instructions for the JavaScript error. Credit goes to MarkJFine.
In the event that this happens:
1. Fully quit the Usage Meter from it's own menu by clicking on the donut in the menubar and clicking "Quit".
2. Look for the following directory
Windows: C:\Users\[your User name]\AppData\Roaming\
Mac: /Users/[your User name]/Library/Application Support/
3. Carefully delete just the "HughesNet Usage Meter" folder under that and empty the trash.
4. Restart the Usage Meter. This will regenerate all the underlying information as if it were run for the first time, thus correcting the error.
Vampy,
Try uninstalling the status meter and usage meter from your system, then navigate to C:\Users\Vampy\AppData\Roaming\HughesNet Usage Meter\, and delete anything that desides in that folder. Also navigate to c:\program files\hughesnet-usage-meter and delete anything that may reside in that folder. Then download and install the latest version (Should be 6.6) and see what happens.
Didn't know this thread existed. Had the same problem over the weekend when my power blipped because of a storm. The computer immediately restarted, but then I started getting this error, having never encountered it before.
I eventually fixed the problem, though I ended up doing a couple of extra things that, it turns out, I didn't need to do.
I wish I had happened onto this thread sooner.
