Last Comment Bug 139838 - Configuration Warnings during startup
: Configuration Warnings during startup
Status: RESOLVED DUPLICATE of bug 193638
Product: SeaMonkey
Classification: Client Software
Component: General (show other bugs)
: Trunk
: x86 Windows 98
-- normal (vote)
: ---
Assigned To: Matthias Versen [:Matti]
: imajes - QA account - use instead
Depends on:
Blocks: startup
  Show dependency treegraph
Reported: 2002-04-24 12:04 PDT by Steven Bush
Modified: 2009-08-27 03:56 PDT (History)
0 users
See Also:
Crash Signature:
QA Whiteboard:
Iteration: ---
Points: ---


Description User image Steven Bush 2002-04-24 12:04:10 PDT
With the most recent build that I downloaded (w32-talkback, build id:
2002042403), I receive two dialog boxes reporting configuration warnings during
the startup of the browser.  They both appear immediately after the splash
screen appears when attempting to execute mozilla.exe after extracting all the
files from the file and overwriting my previous version (which
I believe was 20020401xx)

The first error reports:
An error occurred reading the startup configuration file.  Please contact your
administrator.  line 47: Reference Error: defaultPref is not defined

Second error is very similar:
An error occurred reading the startup configuration file.  Please contact your
administrator.  line 47: Reference Error: config is not defined

To my knowledge, I have not touched my configuration file in a very long time.
Comment 1 User image Matthias Versen [:Matti] 2002-04-24 12:43:03 PDT
Can you please try this :
Uninstall mozilla, delete all files that are not deleted by the uninstaller in
c:\programs\ (but save your plugins) and reinstall mozilla
Comment 2 User image Steven Bush 2002-04-25 12:37:51 PDT
Okay... I didn't reinstall, but I did the following and the warnings stopped:

1. Went into /defaults/pref
2. created a folder called "old"
3. moved the files "config.js" and "initpref.js" into that folder.

everything seems okay now...

"config.js" had the following information (after a lengthy license block):



"initpref.js" had the following information that I believe was causing the
difficulty (there was other information as well:
// --- Preference initialization functions ---
//    Moved to native functions:
//    pref        -> pref_NativeDefaultPref
//    defaultPref -> ""
//    userPref    -> pref_NativeUserPref
//    lockPref    -> pref_NativeLockPref
//    unlockPref  -> pref_NativeUnlockPref
//    getPref     -> pref_NativeGetPref
//    config      -> pref_NativeDefaultPref   (?)

// stubs for compatibility
var default_pref = defaultPref;
var userPref = user_pref;

Comment 3 User image Matthias Versen [:Matti] 2002-05-01 18:08:11 PDT
wfm -> corrupted prefs file
Comment 4 User image Matthias Versen [:Matti] 2003-02-16 21:48:55 PST
Comment 5 User image Matthias Versen [:Matti] 2003-02-16 21:50:41 PST

*** This bug has been marked as a duplicate of 193638 ***

Note You need to log in before you can comment on or make changes to this bug.