Uninstalling currupt CA installation

[Guest.Visitor]

Hi, My client access installation is corrupted. The setup program will only attempt to upgrade the programs and I have been unable to completely uninstall CA so I can do a clean install. How can this be done? (I have already tried deleting the entire ca directory... and cleaning ca entries in the registry as best I can - although CA really puts itself everywhere.) John

[Guest.Visitor]

Only thing I could add is that IBM has a document on the knowledge base about Forcing a removal of Client Access. It basically tells you what to remove from the registry, but I it appears you already tried that. Scott

[Guest.Visitor]

I was more or less deleting any reference I could find in the regestery that had anything to do with CA - there is tons and obviously I didn't find the critical ones. Anyway I'll take a look in the knowlege base and see what I can find. I personally feel that it is rude of a software manufacturer not to have a good, easy to use uninstall - and it should actually free up the drive space and registry. I'm also curious if setup can be forced to do a complete install. John UPDATE!!!!! Try to un-install manually by going to the directory where Client Access is installed (the default is C:Program FilesIBMClient Access) and run CWBUNINS.EXE I got this from the knowlege base. It worked like a charm - so I guess rude doesn't apply here. Thanks fo the suggestion. John

[Guest.Visitor]

Where do I find this document so I can be prepared?

[Guest.Visitor]

If you are using Win9x, have you tried running REGCLEAN? The windows registry is so big, it is possible you missed something. REGCLEAN is a registry cleanup program. You can either download it from Microsoft's web site, or give me your email address and I will send you a self-extracting zip file. You can also try this: 1. Reboot your PC to MS DOS mode 2. Delete everything under c:windows emp 3. Delete file c:windowswin386.swp 4. Reboot to Windows Notes: 1. Most installation programs put their work files inside c:windows emp 2. Windows will create a new win386.swp file

[Guest.Visitor]

Here it is: The following are instructions for forcing a re-installation or removal of Client Access/400 for Windows 95. Try to un-install manually by going to the directory where Client Access is installed (the default is C:Program FilesIBMClient Access) and run CWBUNINS.EXE. If Client Access is not in the Add/Remove section, there may also be missing files. However, this may work and does not take long to try. If this is successful, reboot the PC and continue with a normal installation. If this does not work, to attempt a removal by registry manipulation, do the following: Warning: Changes made to the registry can cause serious problems if not done correctly. Ensure you are confident with making changes to the registry before continuing. Using REGEDIT, go to the key: HKEY_LOCAL_MACHINESOFTWAREIBMClient Access and delete it (by right clicking) on Client Access. If PC5250 was installed with Client Access, remove the registry entries at HKEY_LOCAL_MACHINESOFTWAREIBMPersonal Communications and HKEY_LOCAL_MACHINESOFTWAREIBMNSCMPKG. If the NetSoft Router was installed with Client Access, remove the registry entries at HKEY_LOCAL_MACHINESOFTWARENetSoftNS Elite. The Client Access and NetSoft keys must also be deleted from the Current User key (HKEY_CURRENT_USERSOFTWAREIBMClient Access and HKEY_CURRENT_USERSOFTWARENetSoftNS Elite). Note: Only go into the following listed registry location if you are experiencing File Not Found errors when users log on. A customer may receive the message "CWBUITSK.EXE file could not be found" for any user profile logging onto the PC. Remove any string values referencing Client Access within: HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentV ersionRun Then: o Install Client Access again (reloads any missing files). o Un-install Client Access (through the Add/Remove Programs ICON in the Control Panel). o Reboot. (Locked files get deleted after rebooting.) o Install Client Access again. This problem usually seems to manifest itself when problems arise, such as PC hangs or corrupted data, during Client Access installation for Windows 95 or a service pack install failure.