Closed
Bug 205422
Opened 22 years ago
Closed 22 years ago
-turbo broken in Mozilla 1.4 (OS/2)
Categories
(Core Graveyard :: QuickLaunch (AKA turbo mode), defect)
Tracking
(Not tracked)
VERIFIED
WORKSFORME
People
(Reporter: khill, Assigned: mkaply)
Details
User-Agent: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.3; MultiZilla v1.4.0.2) Gecko/20030509
Build Identifier: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.3; MultiZilla v1.4.0.2) Gecko/20030509
In Mozilla version 1.3, it was possible to rename mozturbo.exe to
mozturboexe.bak and invoke "Mozilla -turbo" in the startup folder. This left a
good chunk of code resident in memory and subsequent instances of Mozilla
started very quickly. Following the same procedure with versions 1.4a and 1.4b,
subsequent instances of Mozilla will not start.
Reproducible: Always
Steps to Reproduce:
1.rename mozturbo.exe to mozturboexe.bak
2.enter "mozilla -turbo" (verify that Mozilla is in memory)
3.enter "mozilla". (program does not load).
Expected Results:
In versions of Mozilla up to and including 1.3, this procedure allowed for rapid
starting of the browser.
Comment 1•22 years ago
|
||
->Quicklaunch / mkaply
Assignee: rjc → mkaply
Component: RDF → QuickLaunch (AKA turbo mode)
OS: other → OS/2
QA Contact: gbush
Summary: -turbo in Mozilla 1.4a and 1.4b no longer works under OS/2 as it did in version Mozilla1.3 → -turbo broken in Mozilla 1.4 (OS/2)
Assignee | ||
Comment 2•22 years ago
|
||
I'm not seeing this problem at all.
Perhaps multizilla is interfering?
Can you try this with a fresh Mozilla install and profile?
Assignee | ||
Comment 3•22 years ago
|
||
Did you do any additional testing of this?
We're not seeing this problem.
Assignee | ||
Comment 4•22 years ago
|
||
Please test this again or I will close the bug.
Assignee | ||
Comment 5•22 years ago
|
||
This works fine for me and we have had no other reports of it not working.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
Updated•13 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•