Closed
Bug 58953
Opened 24 years ago
Closed 24 years ago
Custom N6 installer SetupType dialog should display Recommended,Full,&Custom install options
Categories
(CCK Graveyard :: CCK-Wizard, defect, P3)
Tracking
(Not tracked)
VERIFIED
INVALID
M20
People
(Reporter: bmartin, Assigned: vparthas)
Details
Latest N6 CCK build dated:2000-11-01-16 O/S: All Win32 Steps: 1. download and install latest cck build 2. Launch CCK and create a customized N6 build 3. launch the customized build's installer and proceed to the Setup Type dialog 4. View the options on the custom build's Setup Type dialog Results: Only "Typical" and "Custom" are the available options. Next, 1. Download the MN6's N6Setup.exe stub installer 2. Double-click on the N6Setup.exe to launch it 3. Proceed to the Setup Type dialog 4. View the MN6's Setup Type options Results: The MN6 installer's Setup Type dialog options include a "Recommended"(same as Typical), "Full", and "Custom" Expected: Both the customized N6 installer Setup Type and the MN6 installer Setup Type dialog to display the same options: "Recommended", "Full", and "Custom" *** The customized build's config.ini doesn't contain the [Setup Type0] for "Recommended", [Setup Type1] for "Full", and [Setup Type2] for "Custom". It only contains a [Setup Type0] for "Typical" and [Setup Type1] for "Custom". However, the original config.ini file that gets customized is the same as the MN6 one. ***
marking M20 for tracking N6 CCK RTM
Target Milestone: --- → M20
Comment 2•24 years ago
|
||
For a N6 CCK customized setup, you should get the following behavior which works today: 1) 2 packages: Recommended and Custom 2) Both packages should have the exact same items 3) In Custom, you can unselect things 4) In Recommended, you can not unselect things As mentioned, this is currently working in the product so marking invalid.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → INVALID
Marking this Verified Invalid. The Customized N6 builds' installer is as spec'd by Bijal.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•