|
Howard, Thanks for your response. Here are the answers to your questions the techie gave me: 1. Corporate WinXP. 2. Yes Win XP SP1 is loaded. 3. Notes is 5.0.11 4. Pylon 402 5. Not sure on that. Thanks, Craig Strong **Howard wrote: I don't think WDSC 4.0 changed registry of Lotus Notes. I need some information to investigate this problem. Please provide us the following information on the machine the customer has problem. 1. WinXP (Pro or Home edition) 2. Does customer's machine have WinXP SP1? 3. What is the version of Lotus Notes? 4. What is the version of PalmPilot? 5. What is the version of installShield used to package PalmPilot (if you know)? Thanks Howard Lau WebSphere Development Studio Client for iSeries Install Team IBM Toronto Lab Phone: 905-413-2828, Tie Line: 969-2828 E-mail: howardl@ca.ibm.com Notes ID: Howard Lau/Toronto/IBM ----- Forwarded by Howard Lau/Toronto/IBM on 09/27/2002 11:31 AM ----- Mike Hockings To: Howard Lau/Toronto/IBM@IBMCA 09/27/2002 11:09 cc: AM From: Mike Hockings/Toronto/IBM@IBMCA Subject: [WDSCI-L] WDSC causing WinXP registry problems (IBM fix this please!!!) Was Re: WDSCI causing InstallShield problem on XP Hi Howard, Just in case you are not subscribed to the list I thought this may be of interest to you... Kind regards, Mike Mike Hockings, P.Eng. WebSphere Development Tools for AS/400 - CODE/Designer & WebFacing ! IBM Canada Ltd. Laboratory hockings@ca.ibm.com voice 905 413 3199 ----- Forwarded by Mike Hockings/Toronto/IBM on 27/09/2002 11:08 AM ----- craigs@dekko.com Sent by: To: wdsci-l@midrange.com wdsci-l-admin@mid cc: range.com Subject: [WDSCI-L] WDSC causing WinXP registry problems (IBM fix this please!!!) Was Re: WDSCI causing InstallShield problem on XP 27/09/2002 10:54 AM Please respond to wdsci-l 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 ** Craig previously wrote: Someone here got a new PC with Windows XP and installed the WDSC 4.0 with Service Pack 2. Except for having it hang and having to restart the base installation (not the service pack), everything installed fine. When they try to install the PalmPilot which uses the InstallShield, the install hangs. We looked at the environment variables and they appear to be what they should be according to the installnotes.htm. Installing an older version of the PalmPilot software gives a HotSync error but we can't decide not to install that HotSync. I think he said he installed the PalmPilot after WDSC was already installed on his old PC with Windows 2000 without any problems. The techies are running out of ideas. They are wondering if they should just uninstall WDSC and see if that will allow them to install the PalmPilot. Anyone have this happen or have any idea what could cause this? No one else here has had a problem with installing software on Windows XP but no one else has installed WDSC on their Windows XP either. I think WDSC is the only variable. Please let me know any thoughts you might have. Thanks, Craig Strong
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.