PC5250 will not install (setup.exe)

[Guest.Visitor]

I'm trying to re-install CA/400 V3R2M0 on my PC and the setup pgm will not allow me to select PC5250. I've uninstalled a previous copy of CA/400 and run a registry cleanup utility and still the setup pgm thinks I've got PC5250 (or PCOMM) still installed. Help!!! Thanks, Scott

[David Abramowitz]

One of Murphy's Law's, is: Registry Cleanups, Don't! Run REGEDIT, and search for the 5250 string, or other relavent strings. Delete the keys, and try again, and .........be sure to back up your registry first. Dave

[Guest.Visitor]

Scott - You might also look for a directory name (DIR=C:PCOMWIN, for example)under PCSWINin the WIN.INI file. HTH, Steve

[Guest.Visitor]

<blockquote><tt>>>I'm trying to re-install CA/400 V3R2M0 on my PC and the setup pgm will not allow me to select PC5250. I've uninstalled a previous copy of CA/400 and run a registry cleanup utility and still the setup pgm thinks I've got PC5250 (or PCOMM) still installed. </tt></blockquote> You can also try but ***BIG WORD OF WARNING HERE*** back up your Windows registry first. This is a technique I received from IBM that we printed in the July/Aug 1999 AS/400 Network Expert but it involves changing registry entries. BEFORE YOU DO THIS, BE SURE TO BACK UP THE REGISTRY IN CASE OF ACCIDENTAL CORRUPTION. Everyone knows that REGEDIT is the most dangerous program in the universe and it has been known to bring Windows machines to their knees when registry corruption occurs. Make a good copy of the registry and be sure you know how to restore the Windows registry if it gets corrupted. That said, here's the technique IBM gave us to handle problems like this. 1. There's a bug in the uninstall code of certain versions of Client Access for Windows 95/NT and early versions of Client Access Express for Windows. This bug prevents the uninstall program from clearing out all of your Client Access registry entries. This is what is probably what is causing your problem. 2. The workaround is as follows: - Open REGEDIT (again, I caution you to backup your Windows registry and have a plan in place to restore, if needed) - Expand the HKEY_LOCAL_MACHINESoftwareIBM folder in the registry - Since this problem is most often caused by entries in the NSCMPKG or Personal Communications folder, if you see either of these two folders, try deleting them and then try reloading PC5250 I received this workaround from IBM and several people have told me it works. 3. To prevent this problem from occuring on other machines, you can either correct the registry settings if it comes up again or, if you wish, you can load the most recent CA service pack for that version (which will probably include the bug fix) and that should solve your problem. Hope this helps... Joe Hertvik Editor-AS/400 Network Expert mailto:jhertvik@midrangecomputing.com Looking to hook your AS/400 up to the world? Breaking news, articles, tips, we post it all on the AS/400 Network Expert web site (http://www.midrangecomputing.com/ane). Get in the loop with our **free** weekly email alerts by sending an email to: mailto:jhertvik@midrangecomputing.com?subject=Subs cribedf