Syntax error

I am having the Syntax error problem that Norma discusses: Configuration Warning
"An error occurred reading the startup configuration file.
Please contact your administrator. line XXX:Syntax Error. Illegal character. "

I tried to replace prefs.js files or turn them into .bak files, but I still get the above when opening any of the versions of NS above 4.7 (6, 7.0, 7.1), so I can not keep a prefs log with all my preferences and account info. However, I do not now have prefs.js file on either of my HDD's and the above message still pops up, but without any comment about the problem being on line 63 of prefs.js. Any suggestions on how I can get my NS back. Should I look for mozilla gre files. I am on XP.
Great forum!

 

If possible and the data is not confidential, you might want to post a few lines above Line XXX and a few lines after it of your prefs.js

Have you tried to create a new Netscape profile?

 

Thanks Antony,
However, I think I mentioned there is no prefs.js now on either of my disks. The message stil comes up but with no reference to any file and all the account information that I put in to run NS mail. etc. is no longer present. I have to build new accounts everytime.

 

Have you tried re-installing Netscape?

 

yes, many times. I uninstall, run a Norton Virus scan of the system. check for any prefs.* files, do a new install (the problems started with 7.1) for each of 7.1, 6.?, and 7.0. Same problem comes up. However, with 7.0 I can run NS after okaying the error message. The other installations would just hang up after okaying the error. Of course, even though 7.0 runs, all accounts have to be reconstructed (bookmarks are okay though). Really strange. I also checked for files connected with a Trojan Horse that makes up a new prefs. js file for evil purposes, and have tried the methods listed under Syntex Error by Norma, to no avail. Strange.

 

Hi maddog,

How many versions of Netscape do you have installed, and if more than one, which versions?

You definitely have a prefs.js file, or it wouldn't be possible for you to run Netscape. Even if you delete the prefs.js file Netscape rebuilds the file when restarted. When you deleted the prefs.js file, did you do it when Netscape was open? To view your prefs.js file, look here:
C:\Documents and Settings\user_name\Application Data\Mozilla\Profiles\profilename\xxxxxxxx.slt
NOTE: These files are hidden by default.
To see hidden files:
1. On the Tools menu in Windows Explorer, click Folder Options
2. Click the View tab
3. Under Hidden files and folders, click Show hidden files and folders

Reinstalling Netscape, no matter which version, will not correct your problem. The problem you're having is in your Profile, and to recover, you will need to create a new Profile. Here are guidelines for Creating a New Profile

Let us know if you have further questions.

Ramona

 

Thank you Ramona,
Forgive me for calling you Norma....
I only installed one version of NS at a time after unistalling the previous one thinking that I could overcome the problem that way. As for the prefs.js file, I have done searches on both of my HDDs with no luck, though prefs.bak and prefs.js2 (which is the original prefs.js file that I renamed to keep around just in case) do come up in the search results. This puzzles me. I will check again to make sure I am accessing hidden files. Also, I don't think I changed the prefs file when I had NS open, though I am not sure. My other computers come up with the prefs.js, so I don't think it is my search method. I will go back tonight and try again It sounds so simple, but it isn't, so I must be missing something.
Your knowledge of my favorite browser is impressive!

 

Maddog,

Hey, you can call me Norma if you want to.

The prefs.js file is there, and in the salted folder (*.slt):
C:\Documents and Settings\user_name\Application Data\Mozilla\Profiles\profilename\xxxxxxxx.slt

Since you are running Windows XP, you will need to follow these instructions:

NOTE: These files are hidden by default.
To see hidden files:
1. On the Tools menu in Windows Explorer, click Folder Options
2. Click the View tab
3. Under Hidden files and folders, click Show hidden files and folders

Now this caught my attention immediately:

This is definitely "just in case ", so once you have located your *.slt folder, and find the prefs.js file, rename the file to Xprefs.js, then replace it with the "original prefs.js2" file, which you will rename to prefs.js.

You did say you tried to replace the prefs.js file. Did you already try using the prefs.js2 file, and if so, where did you place the file? This confuses me, as you state that you haven't found the prefs.js file yet. This really isn't a third degree, I'm just trying to get to the same page you're on...

Let us know your progress,

Ramona

 

Norma and Ramona are only an a apart I just noticed, so I guess I am not to out of place.
Well, on my new Dell I loaded NS 7.1 and had the same problem with the Syntax error and I just plugged in a prefs file from my other Dell at work. Error disappeared, preferences came up, all was dandy. I did that because the error showed the problem was in the prefs file so after looking at the contents thereof, I figured a prefs file from my other working machine would be fine. The problem machine is at home and I figured my prefs file was corrupt so I renamed it js2 and then did all the uninstalling and installing I talked about earlier. Since I figured the prefs.js file was the problem I tried to find it after each installation and came up empty. I think I did searches for hidden files (as I usually do) but I may have missed it on the computer at home. I will check tonight.
Also, I have not tried to use the js2 or bak file. I will go and do that tonight (it is 3 pm here in Japan now).
Muchas Gracias again. I feel much better with a Mozilla guardian angel in the background.

 

Hi maddog,

If that prefs.js2 file is the corrupt file, then disregard what I suggested. You don't want to replace what you have with this file. What I would like to see the lines before, including and after line 63 in your prefs.js2 file. This is what Antony was looking for also. Sometimes these syntax errors are as simple as the omission of a comma at the end of the script.

Otherwise, you will need to create a new profile to get rid of the error.

Ramona

 

Well Thank you Ramona and Antony,
I got my NS working again. I have not renamed my prefs.js2 file because I was worried about the same thing. What do I lose if I copy all the files you suggested.
As for Antony's request for lines areound line 63, they wouldn't make any sense because I think there is some Japanese in that portion. I will check again though and try to send it to you for your kind perusal.
I got the monster to work, then shut it down and opened again. No problem. Once I get everything up to snuff, I will upgrade to 7.1 as I like the improvements.
Again Muchas Gracias!! to both of you.

 

Hi maddog,

Great, but I'm waiting for the solution? What did you do to get it to work. Tell all

Never mind about those lines in the prefs.js, since you are up and running...

Ramona

 

Ramona,
I followed the steps you suggested a few posts ago linked to Creating a New Profile. I am not completely finished with all the steps, but it worked well anyway. I will go back tonight and finishe the rest of the work from Copy the News files. I haven't copied my 'w' and 's' files yet and there seem to be some other details, but that worked well.
Hope this is what you wanted in terms of my solution.
Thanks
Hot and humid but nice day here in Tokyo now. Three day weekend coming up and I feel good cause my NS is up and running

 

Hi maddog, and thanks for the feedback, and enjoy your three-day weekend!

Cheers!

Ramona

 

Mille Grazie Ramona,
I am also off for the rest of next week and will be going to Korea for a long postponed visit, without my laptop! However, I will update you if I have any problems with the final solution (?) to my NS problem.