×

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.




I need to reinstall V5R1 WDT/400 on a Win2K system; WSDCi and WSSD had been
installed previously.  WDT/400 has been installed prior to WDSCi and WSSD.

 

So I ran through the WDSC remove process; it blew up.  I tried various
combinations and permutations of uninstall actions; finally I gave up and
tried to load WDT/400.

 

I'm now looking at my 8th attempt to install it (I've done it successfully
on numerous other machines but not with WDSCi lingering).  Other than the
fact that I can't apply SP5 or it crashes after I apply SP5, I've noticed
things like CODEDSU.exe and CODEPROJ.exe haven't been installed in the
WDT400 directory.  I'm doing everything normally: loading from CD, etc.  I
reboot frequently (after installing VA Java, as required, and after manual
cleanup) and have killed Norton's virus checker.  I use WinDoctor to hunt
out orphan entries.

 

I've reviewed IBM's article #1041546, gone to Add/Remove programs and
removed everything in sight, and deleted all the product directories.  I've
dug into the registry and deleted the entries documented in the article
(although there are *thousands* of registry entries left over from Webfacing
and WebSphere Studio) and anything related to "IBM_WDT" or "SP5".  I've
zapped all the *.MSI and *.MST entries created in the last few days.  I've
rebooted so many times I'm starting to think I'm back in the old AS/400 days
of rebooting a dozen times to get a couple of PTF packages applied.

 

I must be overlooking something.I'd very grateful for any advice (on this
problem, anyway!).

 

Thanks,

Reeve 

 

 


This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.