Closed
Bug 81437
Opened 25 years ago
Closed 25 years ago
Small square box after launching setup.exe should be resized
Categories
(CCK Graveyard :: CCK-Installation, defect, P3)
Tracking
(Not tracked)
VERIFIED
FIXED
M21
People
(Reporter: blee, Assigned: kysmith)
References
()
Details
(Whiteboard: nscckb1?)
To see this,
Extract cckinstaller.zip (URL above) and launch setup.exe.
Click Client Customization Kit button.
==> After a progress bar titled "Extracting ..." briefly shows up and goes away,
another small square box appears for a moment before Welcome to Netscape CCK
dialog shows up. This square box is so small no content is visible except the
truncated string ("Netsca...") at the top.
Comment 1•25 years ago
|
||
That's an installer issue. I don't know if Kyle knows how to fix that. cc;ing
ssu for any pointers.
I think I know what you are seeing. I'm guessing that there was a string (maybe
even more than one) that is missing from the config.ini that cck's installer
uses.
So the problem now becomes to track down this missing string (if this is indeed
the case). I'm guessing that it's something along the lines of:
[General]
MSG_INIT_SETUP=Initializing Setup, please wait.
in the file: install.ini (generated from install.it). This message is suppose
to show up at startup of setup.exe, before the welcome dialog shows up.
But I'm just guessing that it's this string....
Updated•25 years ago
|
Priority: -- → P3
Target Milestone: --- → M21
Added "nscckb1" to Status Whiteboard.
This is sort cosmetic, but since this is the user's first impression of the
product, it'd be nice if we could fix this for the Beta.
Whiteboard: nscckb1
Do we have an older installer (maybe 6.0 CCK) that does not have this
problem? If so, maybe we can compare the .ini files and to try and find
any missing strings.
In addtion to the zip installer, this is reproducible with the
2001-06-05-14 blob installer.
Whiteboard: nscckb1 → nscckb1?
Found the problem. The problem is that whoever is updating the CCK installer
(setup.exe, setuprsc.dll, config.ini, install.ini, etc...) is not updating all
the files that go along with the installer.
For this bug, config.ini is really old. It is missing a [Strings] section.
Since config.ini is not up to date, it makes me wonder if the other files are
up to date...
| Assignee | ||
Comment 7•25 years ago
|
||
Currently the build process takes the config.ini file from
ns/cck/cckcd and puts it into the cck installer. There is now a config.ini file
delivered every time we run the seamonkey builds, should that one be put into
the cck installer instead of the one in ns/cck/cckcd?
Also I question the license.txt and readme.txt files in the installer...they
currently come from
ns/cck/license and
ns/cck/readme respectively.
These 2 files are also now delivered every time we run the seamonkey builds.
Should these files be put into the cck installer instead of the ones from the
ns/cck tree?
I don't know how the cck build process is suppose to work. I didn't set
it up. However, wherever the setup.exe is coming from, all its support files
need to come from the same place and same build as well.
a quick workaround would be to copy the [Strings] section from the good
config.ini into the bad config.ini file. That will take care of the problem for
now.
| Assignee | ||
Comment 10•25 years ago
|
||
do you eman the strings section from the seamonkey config.ini that is delivered
as part of the seamonkey builds?
Comment 11•25 years ago
|
||
We should not be replacing the config.ini in ns/cck/cckcd with the config.ini
from the seamonkey builds. The config.ini in ns/cck/cckcd is for the CCK
installer. Similarly, license.txt and readme.txt files are CCK specific. None of
these files must be replaced.
Comment 12•25 years ago
|
||
add the following to the end of the bad config.ini file:
[Strings]
;*** LOCALIZE ME BABY ***
Message Verifying Archives=Verifying integrity of archives, please wait...
This will fix this bug.
| Assignee | ||
Comment 13•25 years ago
|
||
Workaround checked into tree...thanks Sean!
| Assignee | ||
Comment 14•25 years ago
|
||
Checked blob installer, the workaround is good.
| Assignee | ||
Comment 15•25 years ago
|
||
Verifying FIXED
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
| Reporter | ||
Comment 16•25 years ago
|
||
Still happens in 6/8 bld
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
| Reporter | ||
Comment 17•25 years ago
|
||
The blob installer link took me to the previous bld.
Fixed in 6/8 bld.
Status: REOPENED → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•