× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



This is a multipart message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
Craig,

Glad you solved your problem.

Since your techies already diagnosed and solved the problem, for the
benefit of the rest of us on the list, and perhaps the folks at IBM that
have to write the installer, how about posting what it is that WDSc does
to the registry that is causing problems?  Also, are your techies sure
that the problem only happens on XP, and not also on Win2K and NT?

We are on Win2K and use Notes.  I did a glance through my registry and
everything looks fairly orderly, but I do not know what part of the
registry is getting messed up. We definitely installed WDSc after Notes.

Thanks

Mark








craigs@dekko.com
Sent by: wdsci-l-admin@midrange.com
09/27/2002 10:54 AM
Please respond to wdsci-l


        To:     wdsci-l@midrange.com
        cc:
        Subject:        [WDSCI-L] WDSC causing WinXP registry problems (IBM fix 
this please!!!)
Was Re: WDSCI causing InstallShield problem on XP



IBM, please fix how you update the registry of Windows XP during the
install of WDSC (even after Service Pack 2).  It has been proven to be the
cause of other products failing to install.  Yes, others have installed
PalmPilots on Windows XP without problems but they never installed WDSC
before on those.
A techie found and fixed the problem.  The problem was that installing
WDSC
on Windows XP changes the registry enough that certain other products
cannot find Lotus Notes for their install like the PalmPilot if Lotus
Notes
were installed before WDSC.  The PalmPilot installation was looking in the
registry for Lotus Notes but could not find it since WDSC changed the
registry enough.  Reinstalling Lotus Notes allowed the PalmPilot to be
installed.  The techie had to do independent research to find this problem
out given the documentation from Microsoft and IBM.  The techies said that
in the future they will plan on installing XP, then Client Access, then
WDSC, then Lotus Notes.  We have looked at the registry before and it
appears WDSC hacks it up and makes it grow but I think there is a mutual
consensus that WDSC should not have to alter the registry as much as it
does.  I think it used to even use the registry like a cache but I am not
sure if that is still true.  The techies also said that in the future, if
they have install problems on XP, they will try uninstalling everything
that might have happened to be installed before WDSC and then reinstall
with WDSC first.  What is even stranger and ironic is that Lotus Notes is
apparently owned by IBM.  Since IBM owns both WDSC and Lotus Notes, could
you please either make a change in the service pack for this install
problem or document the order you need to install so others don't run into
our same problems.  Lotus Notes was just this case but I think it would be
worth researching what other products might have trouble that rely on the
registry on Windows XP.  We will all be going to Windows XP soon so this
may become more widespread in the future.

Thanks,
Craig Strong






As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.