Apache OpenOffice (AOO) Bugzilla – Issue 9864
Memory access crash during and after installation
Last modified: 2003-09-08 16:53:51 UTC
While installing (no arguments given to setup.exe), got a "setup.exe - Application Error" window with the message 'The instruction at "0x00cb61f2" referenced memory at "0x00000014". The memory could not be "read".' Running "setup -repair" appeared to work, but now clicking on the "OpenOffice.org 1.0.1" shortcut results in a "soffice.exe - Application Error" window with the message 'The instruction at "0x1c823428" referenced memory at "0x00000384". The memory could not be "written".' I have MSVC 6.0 installed, so I could launch the debugger at this point if it would help. I checked the md5sum on the ZIP file before unpacking.
Please tell at which state of setup the crash occurs. Please provide also more information about your system: e.g. hardware configuration, partition table.
The install crashed during the "registering the components" stage. The system is a networked Dell Dimension 4100. Here is the System Summary report from Computer Managment: Item Value OS Name Microsoft Windows 2000 Professional Version 5.0.2195 Build 2195 OS Manufacturer Microsoft Corporation System Name PC128 System Manufacturer Dell Computer Corporation System Model XPS-Z System Type X86-based PC Processor x86 Family 6 Model 8 Stepping 6 GenuineIntel ~864 Mhz BIOS Version 11/28/00 Windows Directory C:\WINNT Locale United Kingdom Time Zone GMT Standard Time Total Physical Memory 130,352 KB Available Physical Memory 8,812 KB Total Virtual Memory 440,180 KB Available Virtual Memory 144,204 KB Page File Space 309,828 KB Disk partition: Disk 0: C: (primary) 18.62 GB FAT32 Disk 1: D: (primary) 3.91 GB FAT extended: (logical) 24 MB Linux partition (logical) 3.91 GB Linux partition (logical) 71 MB Linux partition E: (logical) 11.17 GB NTFS OOo was installed from and to C:
Thanx for your help. This is one of these 'we can't reproduce here' problem. See at issue 7215. I would suspect the fat32 patition to cause the problem, but even with fat32 we can't reproduce. The only case we have had was a defective fat32 partition. In this case a reformatting or converting to NTFS has solved the problem. But I also know that this is not the best solution for you. We will still be investigating to find out what the $%&$&$&% might cause the problem. *** This issue has been marked as a duplicate of 7215 ***
Duplicate