Corrupt Pref.js

Hello,

I have a problem which some clever person may know the solution to. I work on an IT Helpdesk and we have a recurring issue with the pref.js file in Netscape (Netscape 7.01
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01)

What happens is when a user loads up Netscape Mail their account is not present and there is a "free webmail" account under their usual acount. This problem also restricts users from surfing to websites outside our intranet/domain.

So, we take a look at the size of the pref.js file, if it's not 9 or 10k we presure it has become corrupt. The solution? well we look in the users back up files (there is a nightly backup for all users which is stored in a hidden directory on their network drive) for a 9 or 10k file and restore it to the Netscape directory, or we delete the file and ask the user to log out and log back in again, this creates a new pref.js which brings every back to normal.

When asked what has gone wrong, our usual answer is a lack of disk space corrupts the pref.js file. Now this does seem to effect it, if the user has less that 1mb on their networked drive, they are likely to suffer from the corrupt prefs problem. However sometimes this is not the case.

Anybody got any ideas?

 

I looked at your post, yesterday, and I shrugged my shoulders, not knowing anything much about networks. But, since no one has replied. I will through some ideas.
The free webmail thing is irrelevant. It is there is you do not have webmail set up. Some people resent it, as an intrusion, but it is harmless. But you can right click on it and delete. It may or may not come back.
If the pref.js file is corrupted, I would start from scratch.
But, first, I wanmt to make sure that Netscape is closed when you try to restore the backup file.
I do not have to worry about a network, and I can set up a new profile in minutes, with no further problem. It beats hitting the head against the wall, which happens when attempts are made to restore the pref.js file.
I found out that more 90% of the problem lie in something ******* up in the profile, which, for simplicity sake may have been carried on from some earlier version which is now incompatible.
I don't know what is the situation, but, please look at these possibilities