Issue 1765 - OO not functioning after upgrading 638 to 638C w/o deleting all files at deinstallation
Summary: OO not functioning after upgrading 638 to 638C w/o deleting all files at dein...
Status: CLOSED IRREPRODUCIBLE
Alias: None
Product: Installation
Classification: Application
Component: code (show other issues)
Version: current
Hardware: PC Windows 98
: P1 (highest) Trivial (vote)
Target Milestone: ---
Assignee: Unknown
QA Contact: issues@installation
URL:
Keywords:
: 1959 (view as issue list)
Depends on:
Blocks:
 
Reported: 2001-10-03 12:02 UTC by simonbr
Modified: 2003-09-08 16:53 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description simonbr 2001-10-03 12:02:19 UTC
After upgrading to 638C from 638, Writer crashes at attempts to open existing 
files, if the previous installation is not removed completely.

I installed build 638C after removing build 638. When removing 638, I had not 
ticked the box specifying that documents and setting files not be removed.
In the setup program, there was mention of older dll's being copied; I 
selected "replace all".
After the installation had finished, I opened a Writer window and clicking on a 
name in the recently-used files at the bottom of the file menu, a dialog popped 
up "an unrecoverable error has occurred-all modified files have been saved- 
etc. etc."
After clicking on the OK button, two "illegal operation" dialogs followed (I 
failed to copy the register/stack dump in first instance, however see the 
following).
I tried to start a Writer instance again, but now nothing appeared to happen 
anymore (the window did not appear, no dialogs, or anything). Even after 
restarting Windows I could not start Writer anymore.
So, I removed the installation. I got a warning that the quickstarter was still 
running, but its icon was not in the system tray; I killed it using the  
CtrlAltDel dialog.
I installed again 638C and clicked on another file name in the recently-used 
list, which I know has only formatted text, no pictures etc. The same happened 
as before; this time I copied the dumps:

SOFFICE caused an invalid page fault in
module TL638MI.DLL at 015f:1c82df27.
Registers:
EAX=00008000 CS=015f EIP=1c82df27 EFLGS=00010206
EBX=00008000 SS=0167 ESP=0086eab0 EBP=00000000
ECX=00000000 DS=0167 ESI=00000000 FS=0f87
EDX=010c0550 ES=0167 EDI=00652458 GS=0000
Bytes at CS:EIP:
8a 45 4e 84 c0 75 14 68 10 0c 00 00 8b cd e8 96 
Stack dump:
00008000 00000000 0211c290 1c82d3e1 00652458 00008000 0211c290 0211c8f4 
0211c908 00000000 1c9039b7 00000000 0211c290 0211bab4 0086ed40 0211c290 

SOFFICE caused an invalid page fault in
module SFX638MI.DLL at 015f:1d5e7f61.
Registers:
EAX=0000048b CS=015f EIP=1d5e7f61 EFLGS=00010246
EBX=00000001 SS=0167 ESP=0086d9fc EBP=018c43cc
ECX=007331b8 DS=0167 ESI=1c719920 FS=0f87
EDX=0086da1c ES=0167 EDI=1c719920 GS=0000
Bytes at CS:EIP:
8b 80 94 00 00 00 85 c0 89 06 74 09 8b 08 50 ff 
Stack dump:
018c43ac 00000000 1d51798f 1c719920 0086daec 00000000 00000300 00000000 
01101b20 018c43cc 0086dd94 1d69157d 00000001 01102d06 018c43ac 0086dae0 

I removed the installation and installed again.
Now I opened a writer window and tried to use the file->open dialog to open a 
file.
When I clicked on a file name, the "unrecoverable error (etc)" dialog 
immediately popped up. In this case, clicking the OK button on the dialog did 
not do anything. I had to kill soffice using CtrlAltDel.

Finally, I removed the installation, now ticking the box "remove all files".
After re-installing I found that there were no "recently used files" but I 
could open a file in Writer using the file-open dialog.
Saving at another location, closing the window, in another writer window the 
file was in the recently used files; clicking on it opened the file without 
provblems.
I notice though that settings made in the previous installation are still 
active (for example, I had selected "grid visible" and it is still visible).
Also, the text files in the <OO>/user/work directory had NOT been removed! 
(read <OO>=c:/program files/openoffice.org638; I did not change directory 
preference at installing).
Comment 1 Olaf Felka 2001-10-09 13:03:26 UTC
Hi Matthias,
should this be possible? Or must OOo have the same Build IDs to install 'over' the rest of an unistalled version?
Comment 2 Olaf Felka 2001-10-29 15:09:44 UTC
*** Issue 1959 has been marked as a duplicate of this issue. ***
Comment 3 Mathias_Bauer 2001-11-09 10:30:10 UTC
I don't understand that.
Did you install 638c into the same directory as your 638? This would
be definitely a desaster.
How did you manage to install a 638c without deinstalling the 638?
Usually this is prohibited because we don't have an update
installation feature (IMHO).
Without manipulating the sversion.ini file it is not possible to use
two versions of OO with the same major version ( like OO638 and OO628c
) in paralell. But if you know how to manipulate sversion.ini, there
is no problem to let OO638 and OO638c cooperate.

So please give more information about what you've done exactly.
Comment 4 simonbr 2001-11-10 10:37:20 UTC
Hi Mathias, 
I *did* deinstall 638 first!
I just checked the option in the deinstall script so it would not 
delete any documents I might have prepared using it.
It seems reasonable to assume that you can then safely install a new 
version in the same location. In any case, it appears I'm not the 
only one to have assumed this (see issue 1959). 
I agree with Jonathan's suggestion that, if a new version of OOo is 
being installed in a location that contains incompatible files from 
previous versions, the install script should emit a warning.
Best regards, 
Simon.
Comment 5 Mathias_Bauer 2001-11-23 09:55:41 UTC
Perhaps we have a problem in this kind of "update" installation. This
should be examined by the installation team.
Comment 6 dirk.voelzke 2002-01-22 14:52:46 UTC
It looks like OO 638C doesn't like the registry files of 638. After 
removing ..\share\config\registry\.. and ..\user\config\registry\.. 
and doing a setup repair everything works fine. The 641C doesn't have 
these problems.
Comment 7 michael.bemmer 2003-03-13 09:50:21 UTC
As mentioned on the qa dev list on March 5th I will close all resolved
<wontfix/duplicate/worksforme/invalid> issues. Please see this posting for
details. First step in IssueZilla is unfortunately to set them to verified.
Comment 8 michael.bemmer 2003-03-13 09:51:17 UTC
As mentioned on the qa dev list on March 5th I will close all resolved
<wontfix/duplicate/worksforme/invalid> issues. Please see this posting for
details. First step in IssueZilla is unfortunately to set them to verified.
Comment 9 michael.bemmer 2003-03-13 10:26:12 UTC
As mentioned on the qa dev list on March 5th I will close all resolved
<wontfix/duplicate/worksforme/invalid> issues. Please see this posting for details. 
Comment 10 michael.bemmer 2003-03-13 10:26:33 UTC
As mentioned on the qa dev list on March 5th I will close all resolved
<wontfix/duplicate/worksforme/invalid> issues. Please see this posting for details.