Hi:

After an exciting demo was well received, I installed the WDSc client on 
most of our programmers' PCs. The installation per se seemed to go well, 
but it took quite a long time on each machine. That's because the program 
is an absolute leviathan (no wonder there is a DVD option). We tested a 
number of features and they looked promising. Things seemed awfully slow 
at times, even on the PC that was upgraded the most recently. OK, there is 
more than enough potential bang for the buck to justify some occasional 
chugging.

As soon as we tried to run compiles or anything actually productive, we 
started getting hard halts (PC side). Then came the dawning realization 
that nobody, anywhere, seems to know everything needed to make the ~!@# 
thing WORK. Even sent one member of the department to a Chicago area user 
group at which the erstwhile Mr. Pluta was the featured speaker. She asked 
if there is a list ... a web site ... a person ... from whom or from which 
we can find exactly what all the requirements are to run WDSc (installed 
software, system values, etc.). To date, no joy.

The best we can do seems to be the "fix the current error then see what 
the next error is" approach; very much akin to the "debug by compiling" 
approach. We don't have time for that, especially when we can't find any 
documentation on the current error [wry grin]. Yes, we eventually solved 
each problem, at least until we gave up. But everyone in our organization 
who was testing WDSc has shrugged and gone back to SEU/PDM. There may be 
one or two who use WDSc for some "views", but there is no buzz about the 
program anymore.

Darrell

Darrell A. Martin  -  630-754-2187
Manager, Computer Operations
dmartin@xxxxxxxxxxxxx

midrange-l-bounces@xxxxxxxxxxxx wrote on 12/18/2006 02:50:14 PM:

-----Original Message-----
From: ALopez@xxxxxxxxxx
Sent: Dec 18, 2006 3:31 PM
To: midrange-l@xxxxxxxxxxxx
Subject: RE: Saving the System i: Fight Rather Than Switch

<<<  I'd be interested to see how many people are using WDSC today, 
and how many have found errors that completely stop them from working. 


I loaded onto my workstation and tried it out eight months ago.  It 
slowed me down so I stopped using it.  When I get to a point where I
can devote some time to the process, I shall try it again.  I need 
the exposure.


Robert Munday
Munday Software Consultants
Montgomery, AL
on assignment in Dublin, OH
Time Magazine's Person Of The Year 2006


-- 
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.






This e-mail, including attachments, may contain information that is 
confidential and/or proprietary, and may only be used by the person to 
whom this email is addressed. If the recipient of this e-mail is not the 
intended recipient or an authorized agent, the reader is hereby notified 
that any dissemination, distribution, or copying of this e-mail is 
prohibited. If this e-mail has been delivered to you in error, please 
notify the sender by replying to this message and deleting this e-mail 
immediately.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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

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.