Closed Bug 58586 Opened 26 years ago Closed 26 years ago

NetscapeCCKUninstall.exe is not getting installed to windows directory

Categories

(CCK Graveyard :: CCK-Installation, defect, P3)

x86
Windows NT

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: bmartin, Assigned: vparthas)

Details

latest N6 CCK build dated: 2000-10-27-18 O/S: Win95,98,NT4,2000,Me Steps: 1. Download latest N6 CCK build and install to a clean machine 2. Search local hard drive for NetscapeCCKUninstall.exe Results: File not found. Exoected the NetscapeCCKUninstall.exe to get installed to the Windows\ directory
The following section of the CCK config.ini states where the NetscapeCCKUninstall.exe file should live on users' machine(s): [Copy File1] Timing=post smartupdate Source=[SETUP STARTUP PATH]\NetscapeCCKUninstall.exe Destination=[WINDIR] Fail If Exists=FALSE
marking as M20 for tracking N6 CCK RTM
Target Milestone: --- → M20
Status: NEW → ASSIGNED
marking fixed
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
Re-opening... The NetscapeCCKUninstall.exe is not getting installed. N6 CCK build dated: 2000-11-08-12
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
In Config.ini... [Copy File1] Timing=post smartupdate Source=[SETUP STARTUP PATH]\NetscapeCCKUninstall.exe Destination=[WINDIR] Fail If Exists=FALSE should be changed to: [Copy File1] Timing=post smartupdate Source=[XPI PATH]\NetscapeCCKUninstall.exe Destination=[WINDIR] Fail If Exists=FALSE Also, there's a typo in the config.ini: [Windows Registry1] Root Key=HKEY_LOCAL_MACHINE Key=Software\Microsoft\Windows\CurrentVersion\Uninstall\Netscape 6 Client Customization Kit 6 .0 to: [Windows Registry1] Root Key=HKEY_LOCAL_MACHINE Key=Software\Microsoft\Windows\CurrentVersion\Uninstall\Netscape 6 Client Customization Kit 6.0
Marking Fixed. The neccessary changes have been made in the config.ini.
Status: REOPENED → RESOLVED
Closed: 26 years ago → 26 years ago
Resolution: --- → FIXED
Marking this Verified Fixed.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.