Closed Bug 146039 Opened 23 years ago Closed 20 years ago

CCK/NCADM Uninstaller doesn't check if WizardMachine.exe is running before uninstall

Categories

(CCK Graveyard :: CCK-General, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX
Future

People

(Reporter: jimmyu, Assigned: smeredith)

Details

Reproducible: Always Steps to reproduce: 1) luanch CCK/NCADM WizardMachine.exe 2) go to Control Panel > Add/Remove Programs 3) select CCK/NCADM to uninstall Expect result: CCK/NCADM gets uninstalled, and some files still lives. Actual result: Uninstall should check for any instance of CCK/NCADM is running and ask to close CCK/NCADM before uninstall. Just like the core client.
TM -> Future per triage.
Target Milestone: --- → Future
Looks like the CCK installer/uninstaller problem. Reassigning to appropriate owner, Yumi.
I spoke to Curt in the installer team and it seems that I can add the following to the installer's config.ini for both NCADM/CCK to implement this change: [Check Instance1] Class Name=MozillaWindowClass Window Name= ;*** LOCALIZE ME BABY *** Message=Setup has detected that an instance of <NCADM/CCK> is currently running. Please quit <NCADM/CCK> before continuing Setup. Click Retry to perform the check again, or Cancel to exit Setup. The Class Name needs to be a uniqe identifier for the app. Using VCC++ Spy++ tool the current class name showing when WizardMachine.exe is running is: Class Name=#32770(Dialog) which I guess is a generic name. Shruti/Steve can that generic name be easily changed to something more specific?
At first glance, no, I can't figure it out. That part of the cck code is pretty messy. I'll take the bug and give it back when I figure that part out.
Assignee: shrutiv → smeredith
Old CCK.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.