|
I'm waiting for 5.1. It's gotten so much hype I'm expecting it to generate winning Lotto numbers and bake brownies. On the W2K box, I removed everything WDSC-related, including digging into the \program files\IBM directory. I actually started first thing one morning and went back later looking for new objects based on the creation date, so I think I found everything outside the registry (RegCrawler removed > 8,000 "WDSC" keys). I killed Norton 2003 AV and various other processes. The DVD option: it gives my T30 ThinkPad (with current BIOS, Update Connector fixes, and XP SP's) the hardware Blue Screen Of Death. If you're installing from a network drive, you're not loading CD's, so there must be a way to do a "non-CD" install. I think I've seen the procedure for a network drive setup somewhere. Thanks, Reeve > -----Original Message----- > From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On > Behalf Of Vern Hamberg > Sent: Sunday, November 09, 2003 10:30 AM > To: Websphere Development Studio Client for iSeries > Subject: RE: [WDSCI-L] Re: Purging WDSC, et al, from PC > > I recommend getting WDSc 5.1. This requires at least SP2 of Win2K - this > said, as you mention this. I don't know the reqs for 5.0 - should be in the > Installation Notes on the CD. > > Did you also delete the various directories? The one in C:\Program Files, > as well as C:\WDSC? And C:\WDT400? WDT & WDSc v.0 have to be removed > manually, IIRC. > > As for unattended (basically), you can use the DVD. Or, I think, copy each > CD in turn to a directory, either on a network box or locally - if you have > the room. IBM does not explicitly suggest copying from the CDs - it > explicitly mentions the DVD - so you'd do this at your own risk. > > Also, I recommend disabling anti-virus software for the duration. It's not > stated in IBM's docs, AFAIK, but I always do this for IBM software, and > many others. > > HTH > Vern > > At 11:16 PM 11/8/2003 -0500, you wrote: > >I can't get WSDC 5.0 to install on a Win2K box to save my life. I've > >cleaned and scrubbed until both my fingers and disk drives are raw. Even > >after a couple of bouts with various registry cleaning tools, it looks like > >there's still a hidden or non-obvious key interfering with the install > >process. WDT installed fine, so maybe it's time to try WDSC again (I'm > >hoping for spontaneous remission). > > > >It seems to me that as applications get larger and more complex, a > >disproportionately-larger amount of time should be spent on the > >install/remove process (it looks like WDSC adds several thousand keys to the > >registry). Since I don't package PC software, I'm not familiar with how > >packaging utilities work, but I wonder why the WDSC install procedure > >doesn't load all CD's at the beginning of the process so it will run > >unattended. > > > >Well, it's probably time for a cold start anyway. U.S. Thanksgiving is a > >four-day weekend; that should just be enough time to load Win2K SP's. > > > >-reeve > > > _______________________________________________ > This is the Websphere Development Studio Client for iSeries (WDSCI-L) mailing list > To post a message email: WDSCI-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/wdsci-l > or email: WDSCI-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/wdsci-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.