When you run mozilla -turbo it just flashes a screen and then disappears, this is the lcorrect behavior. After this launch mozilla and because the dll's are still in memory it comes up faster now. It doesn't cause mozilla to come up any faster on the first launch but subsequent launches are faster (first launch means the mozilla -turbo launch). This switch doesn't speed up mozilla but rather tells it to load the dll's and to keep them loaded so that if you open and close mozilla often it comes back up quickly. This is implemented in Netscape 6.2 on windoze in the preferences with the load at startup option and is equivalent to that if you put this in the startup forlder or cmd file. Andy Erik P. Olsen wrote:
>Interesting. I am not sure whether my observation is due to a slow >processor or that turbo doesn't work. I also get the blank mozilla >window for about one second and then nothing. But I can see the >process is there. Can you verify that the mozilla.exe -turbo process >is there after the blank window is gone? > >Regards, >Erik P. Olsen > >On Sat, 15 Dec 2001 08:21:12 GMT, Ralph Cohen wrote: > >>Turbo still doesn't work here with build 2001121319 (Warp4+FP12). All >>I get is a white window that briefly pops up and then closes. I can't >>run Mozilla at all with the -turbo option. You had mentioned earlier >>that you were going to be working on the turbo option a bit in 0.9.6. >>Has any of that been done already in the daily builds? >> > > >
