Build ID: 200162004 comm. Steps to Reproduce: (1) Create a new profile. (2) Run Mozilla. (3) Now run Mozilla again, because it didn't come up for you. Suddenly startup is fast! But that's because turbo mode is now on by default, and I didn't get asked. Not to mention that in the Advanced preferences pane, the turbo mode option is unchecked. Do you have a default value for this pref in all.js?
->paw/jrgm, for turbo qa.
There is no pref. Let me look into this, the code as I checked in had this off as default. But sean said he did some hacking to the config.ini file which may have changed that.
woks for me. is there a mozilla.exe shortcut in your shortcuts folder? I just installed and there is not, and the checkbox for enabling this in the installer is not set. Resolving INVALID.
Right, the checkbox isn't checked. But it's preloading. kerz saw the same thing. Might be commercial only.
I tried commercial twice, win98 and NT. Works great. Can either of you boys demo this for me?
ok, this is not my bug. If you get turbo mode behaviour on a new profile, that is some issue with the turbo mode code internally. All my installer and prefs stuff does is write or remove a shortcut from the startup folder. That is working great. Please assign this to whoever is responsible for turbo mode internals.
I think that person is Bill Law who just left (last week) for a 7 week sabbatical. Anyone knows how his backup person is? I hear rumors it could be Samir, but I'm not sure.
Conrad touched turbo mode stuff recently also (bug 86021). --> him This is an rtm stopper.
can we get some other folks pounding on this. seems like we are getting unpredicatble results... I installed the build from 6/21, did not select turbo, (it was not on by default) and didn't get turbo.
I'm still not seeing this. Turbo being on has nothing to do with a profile. Syd, if I understand what your pref does, it does not affect the prefs at all, only creates or deletes the shortcut in startup items. From what I can see, the only thing which can turn it on is this: http://lxr.mozilla.org/seamonkey/source/xpfe/bootstrap/nsNativeAppSupportWin.cpp#533 when it came from the command line.
From what different people have seen, can we say: - this happens when the program is installed by the installer - it doesn't happen with a trunk build that somebody builds themselves
I'll try a new build now. Make sure you're using commercial installer. kerz saw it too.
Last night, I was testing a fix to a bug which involved starting up with new profiles on commercial. I did this tons of times and never saw this problem. If you're seeing this only with the installer, that gives us a pretty good clue :-)
Just talked with syd and ssu. It worked for me in a new commercial installer build. I swear it didn't work yesterday :-) Ask kerz!
Mmm. Hallucinogens. verified wfm.