[Bug 30735] New: MS Office 2000 SR1 installs unusable
http://bugs.winehq.org/show_bug.cgi?id=30735 Bug #: 30735 Summary: MS Office 2000 SR1 installs unusable Product: Wine Version: 1.5.4 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msi AssignedTo: wine-bugs(a)winehq.org ReportedBy: ubrammer(a)t-online.de Classification: Unclassified Installation of Office 2000 SR1 at wine 1.5.4 works with a success message. But the programs excel and word die silently latest after the first mousemovement. Further digging in reveals: Installing MS office 2000 SR1 does not install due to bug http://bugs.winehq.org/show_bug.cgi?id=29335 . This bug can be avoided bei copying the contents of the system-folder into windows/system32 and also installing mfc42 with winetricks. Using the above workaround gave the following: The installer crashes from wine-1.3.7 up to 1.5.3 with another bug. The crash was fixed in wine 1.5.4 by http://bugs.winehq.org/show_bug.cgi?id=30571 but the fix did not solve the unusable installation of office 2000. The first bad commit regarding bug 30571 is commit 19a2d144b563f23dacfb127b94948b0f0f89b003 Author: Hans Leidekker <hans(a)codeweavers.com> Date: Fri Nov 12 15:05:55 2010 +0100 msi: Don't rebuild the target path for files from global assembly components. Reverting this commit results in a good install until commit:2a59f016dbe716aaefec9ab94d47d7b8172d0b5b Author: Alexandre Julliard <julliard(a)winehq.org> Date: Tue Dec 20 11:42:45 2011 +0100 mountmgr: Add dynamic devices support using UDisks. Wine with this commit compiled in, give an unusable office 2000 installation. A Wine version before this commit give a good office 2000 installation. A wineprefix with a good installation is usable in later versions of wine, which will not give a good installation. I could not revert commit 2a59f016dbe716aaefec9ab94d47d7b8172d0b5b on top of wine 1.5.4. So I made logs of the install with the bisected version. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30735 --- Comment #1 from Ulrich Brammer <ubrammer(a)t-online.de> 2012-05-20 13:35:51 CDT --- Created attachment 40239 --> http://bugs.winehq.org/attachment.cgi?id=40239 Log of the bad office 2000 install -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30735 --- Comment #2 from Ulrich Brammer <ubrammer(a)t-online.de> 2012-05-20 13:38:03 CDT --- Created attachment 40240 --> http://bugs.winehq.org/attachment.cgi?id=40240 log of the good office 2000 install -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30735 Ulrich Brammer <ubrammer(a)t-online.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hans(a)meelstraat.net, | |julliard(a)winehq.org, | |ubrammer(a)t-online.de -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30735 --- Comment #3 from Hans Leidekker <hans(a)meelstraat.net> 2012-05-21 02:18:35 CDT --- (In reply to comment #2)
Created attachment 40240 [details] log of the good office 2000 install
firstbad.log has this line:
fixme:ntdll:server_ioctl_file Unsupported ioctl 70c00 (device=7 access=0 func=300 method=0)
which is missing from lastgood.log. This line is generated as part of a custom action called ValidateProductID. This action sets a number of properties, the last of which is DigitalProductID. The value of this property is different between the two runs and I suspect it shouldn't be. Can you generate another good trace? -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30735 --- Comment #4 from Ulrich Brammer <ubrammer(a)t-online.de> 2012-05-21 14:41:27 CDT --- Created attachment 40255 --> http://bugs.winehq.org/attachment.cgi?id=40255 Another trace of a good install Here is a second log of a good install. I made also a diff between the exported registries of a good and a bad install just after the installation before a run of an installed product. The differences are surprisingly small. I made this before, but after a start of excel. I had than a lot more registry keys in the good install. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30735 --- Comment #5 from Ulrich Brammer <ubrammer(a)t-online.de> 2012-05-21 14:43:57 CDT --- Created attachment 40256 --> http://bugs.winehq.org/attachment.cgi?id=40256 Comparisan of the registry of a good and a bad install. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30735 --- Comment #6 from Hans Leidekker <hans(a)meelstraat.net> 2012-05-21 15:18:58 CDT --- (In reply to comment #5)
Created attachment 40256 [details] Comparisan of the registry of a good and a bad install.
Looks like your drives are not properly detected in the bad case: --- .wine_office_firstbad_log2/drive_c/bad_after_install.reg 2012-05-21 20:12:02.325174079 +0200 +++ .wine_office_lastgood_log2/drive_c/after_install_good.reg 2012-05-21 20:23:41.625175011 +0200 ... [HKEY_LOCAL_MACHINE\Software\Wine\Drives] -"a:"="floppy" -"c:"="hd" -"e:"="network" ... [HKEY_LOCAL_MACHINE\System\MountedDevices] -"\\??\\Volume{00000000-0000-0000-0000-000000000041}"=hex:00,00,00,00 -"\\??\\Volume{00000000-0000-0000-0000-000000000045}"=hex:00,00,00,00 -"\\??\\Volume{44349c67-b687-486c-8b5c-8a36b2e6379a}"=hex:2f,00,00,00 -"\\??\\Volume{66f7dd3c-a0dc-450f-99c9-c43459245ea8}"=hex:00,00,00,00 -"\\??\\Volume{6fdc1e23-b054-4d75-8d90-d04c37b4eb32}"=hex:2f,6d,6e,74,2f,6b,6e,\ - 6f,78,00 -"\\??\\Volume{8af37df6-8e8a-4d9d-b2f4-06fa2c616429}"=hex:00,00,00,00 -"\\DosDevices\\A:"=hex:00,00,00,00 +"\\??\\Volume{00000000-0000-0000-0000-000000000043}"=hex:2e,2e,2f,64,72,69,76,\ + 65,5f,63,00 +"\\??\\Volume{00000000-0000-0000-0000-000000000044}"=hex:2f,68,6f,6d,65,2f,75,\ + 6c,72,69,63,68,2f,53,6f,66,74,77,61,72,65,2f,6f,66,66,69,63,65,32,6b,2f,4d,\ + 53,4f,46,46,53,42,45,39,2f,00 +"\\??\\Volume{00000000-0000-0000-0000-00000000005a}"=hex:2f,00,00,00 "\\DosDevices\\C:"=hex:2e,2e,2f,64,72,69,76,65,5f,63,00 "\\DosDevices\\D:"=hex:2f,68,6f,6d,65,2f,75,6c,72,69,63,68,2f,53,6f,66,74,77,\ 61,72,65,2f,6f,66,66,69,63,65,32,6b,2f,4d,53,4f,46,46,53,42,45,39,2f,00 -"\\DosDevices\\E:"=hex:00,00,00,00 "\\DosDevices\\Z:"=hex:2f,00,00,00 What distribution do you use? Did you build Wine yourself? Can you compare the Drives tab in winecfg in the good and the bad case? -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30735 --- Comment #7 from Ulrich Brammer <ubrammer(a)t-online.de> 2012-05-21 15:34:57 CDT --- The confusion with the drives is introduces with the commit:2a59f016dbe716aaefec9ab94d47d7b8172d0b5b Author: Alexandre Julliard The drives tab looks identical, because I set it identical just before the install. The commit above does also have the effect of no detected drive c: in winecfg. I had to add drive c: before the install. I install from a copy of the installation CD on my harddrive. I set this path in winecfg just before the install. I made the bad install with a wine version 1.3.35 just set to the commit above and a good install with the same wine version set to the last commit before. I could not made a good install with the actual version, because the commit from A. Julliard can not cleanly reverted at the actual version. I made in the mean time a test. I exchanged the different registry keys regarding microsoft office in a bad install to the keys from a good install. The installation turns into a good one. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30735 --- Comment #8 from Hans Leidekker <hans(a)meelstraat.net> 2012-05-22 02:11:02 CDT --- (In reply to comment #7)
The confusion with the drives is introduces with the commit:2a59f016dbe716aaefec9ab94d47d7b8172d0b5b Author: Alexandre Julliard
The drives tab looks identical, because I set it identical just before the install. The commit above does also have the effect of no detected drive c: in winecfg. I had to add drive c: before the install.
I install from a copy of the installation CD on my harddrive. I set this path in winecfg just before the install.
What is the drive type for the loop mount set to? Is it the same in the good and the bad case? -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30735 --- Comment #9 from Ulrich Brammer <ubrammer(a)t-online.de> 2012-05-23 13:44:29 CDT ---
What distribution do you use? Did you build Wine yourself?
I use stable Debian Squeeze. I build Wine from Git.
What is the drive type for the loop mount set to? Is it the same in the good and the bad case?
I use an SSD for the system data and a harddrive for the home-folder. The harddrive does contain an older installation. The home-folder from this installation is symlinked to /home. Both the SSD and the harddrive have an additional NTFS-partition. The loop mount is the same for the good and the bad case. It is an folder from my home directory on the harddrive. I made an installation test with the actual wine version on a different computer (which is not mine) with the same MS-office installation CD. Distribution: Debian testing mixed with unstable. There MS office installs without problems. So is this an hardware/distribution related problem? -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30735 --- Comment #10 from Hans Leidekker <hans(a)meelstraat.net> 2012-05-23 14:09:35 CDT --- (In reply to comment #9)
What distribution do you use? Did you build Wine yourself?
I use stable Debian Squeeze. I build Wine from Git.
What is the drive type for the loop mount set to? Is it the same in the good and the bad case?
I use an SSD for the system data and a harddrive for the home-folder. The harddrive does contain an older installation. The home-folder from this installation is symlinked to /home. Both the SSD and the harddrive have an additional NTFS-partition.
The loop mount is the same for the good and the bad case. It is an folder from my home directory on the harddrive.
I made an installation test with the actual wine version on a different computer (which is not mine) with the same MS-office installation CD. Distribution: Debian testing mixed with unstable. There MS office installs without problems.
So is this an hardware/distribution related problem?
Possibly. You didn't answer my question about the drive type. You can find it on the 'Drives' tab after clicking the 'Show Advanced' button. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30735 --- Comment #11 from Ulrich Brammer <ubrammer(a)t-online.de> 2012-05-23 14:48:05 CDT --- The drive type is "Automatisch" maybe automatically in the english version. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30735 --- Comment #12 from Hans Leidekker <hans(a)meelstraat.net> 2012-05-23 15:05:00 CDT --- (In reply to comment #11)
The drive type is "Automatisch" maybe automatically in the english version.
Both in the good and the bad case? On my system an iso loop mount is detected as 'Network share'. What happens if you change it to 'Network share'? -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30735 --- Comment #13 from Ulrich Brammer <ubrammer(a)t-online.de> 2012-05-23 15:16:13 CDT --- (In reply to comment #12)
(In reply to comment #11)
The drive type is "Automatisch" maybe automatically in the english version.
Both in the good and the bad case? On my system an iso loop mount is detected as 'Network share'. What happens if you change it to 'Network share'
We may misunderstood. I just choosed a folder from the harddrive, with the content of the installation CD in the drive-tab of winecfg. I did not mounted an iso-file of the CD. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30735 --- Comment #14 from Ulrich Brammer <ubrammer(a)t-online.de> 2012-05-23 15:17:41 CDT --- The type is "Automatisch" in both cases: good and bad. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30735 --- Comment #15 from Hans Leidekker <hans(a)meelstraat.net> 2012-05-23 15:25:48 CDT --- (In reply to comment #13)
(In reply to comment #12)
(In reply to comment #11)
The drive type is "Automatisch" maybe automatically in the english version.
Both in the good and the bad case? On my system an iso loop mount is detected as 'Network share'. What happens if you change it to 'Network share'
We may misunderstood. I just choosed a folder from the harddrive, with the content of the installation CD in the drive-tab of winecfg. I did not mounted an iso-file of the CD.
I see. What happens if you set it to 'Network share'? -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30735 --- Comment #16 from Ulrich Brammer <ubrammer(a)t-online.de> 2012-05-23 15:38:43 CDT --- (In reply to comment #15)
I see. What happens if you set it to 'Network share'?
The change is not accepted. When I call winecfg again, the type stands still at "Automatisch". -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30735 Hans Leidekker <hans(a)meelstraat.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|msi |-unknown --- Comment #17 from Hans Leidekker <hans(a)meelstraat.net> 2012-05-24 01:51:48 CDT --- Looks like UDisks support is not working on your system. It could be a configuration issue or perhaps it was simply fixed in later Debian releases. You could try to narrow it down more by eliminating differences between your system and the system where it works. +mountmgr,+volume traces of a good and a bad run may also provide a clue. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30735 --- Comment #18 from Ulrich Brammer <ubrammer(a)t-online.de> 2012-12-05 15:15:08 CST --- In the meantime I tried several things to narrow down the bug: Changing to Debian Wheezy, made tests in two virtual machines. Lastly I found a hint. Wine does not handle correctly may old floppy drive, which was all the time installed in my computer. After disabling the floppy in the bios, everything worked well, except of the floppy drive of course. I attach a snippet of a relay trace, which shows the behavior. Excel tries several time to access the floppy at each start. The console shows every time the "fixme: CDROM GetMediaType faking success" messages. There is also an another bug. Even if the floppy drive is disabled in winecfg, it is added later again in the registry by just running other programs like regedit. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30735 --- Comment #19 from Ulrich Brammer <ubrammer(a)t-online.de> 2012-12-05 15:17:21 CST --- Created attachment 42720 --> http://bugs.winehq.org/attachment.cgi?id=42720 Request for floppy with fixme CDROM GetMediaType -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30735 --- Comment #20 from Ulrich Brammer <ubrammer(a)t-online.de> 2013-01-04 10:56:49 CST --- Created attachment 43080 --> http://bugs.winehq.org/attachment.cgi?id=43080 Patch to add a fake function for IOCTL_DISK_GET_MEDIA_TYPES and IOCTL_STORAGE_GET_MEDIA_TYPES The Office2000 installer and the later installed office programs call IOCTL_STORAGE_GET_MEDIA_TYPES for device A: if present in wine. In current wine (1.5.20) this is answered with IOCTL_STORAGE_GET_MEDIA_TYPES_EX. The wine function IOCTL_STORAGE_GET_MEDIA_TYPES_EX delivers an incomplete structure of type GET_MEDIA_TYPES whereas IOCTL_STORAGE_GET_MEDIA_TYPES delivers a structure of type DISK_GEOMETRY, which is needed. The patch solves the problem for me. It was also tested with the sample code from: http://support.microsoft.com/kb/115828/en-us According to the above web-page the DISK_GEOMETRY will also be delivered, if there is no floppy in the drive. Since the usage of udisks in wine, drive A: is always present, if a floppy drive is installed and activated in the BIOS. Before udisks drive A: was not present in wine, until added manually. Office 2000 could be installed before udisks even with an installed floppy drive without inserted floppy. This is not the case in current wine. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=30735 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |Installer Status|UNCONFIRMED |NEW CC| |focht(a)gmx.net Component|-unknown |ntdll Summary|MS Office 2000 SR1 installs |MS Office 2000 SR1 fails to |unusable |install if floppy drive | |'A:' present | |(IOCTL_STORAGE_GET_MEDIA_TY | |PES and | |IOCTL_DISK_GET_MEDIA_TYPES | |need to return filled | |DISK_GEOMETRY structure) Ever confirmed|0 |1 --- Comment #21 from Anastasius Focht <focht(a)gmx.net> --- Hello folks, refining summary based on comment #20 Office 2K SP1 downloads: http://www.filewatcher.com/_/?q=+O2KSR1aDL.exe Also needs 'winetricks -q mfc42' Regards -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=30735 --- Comment #22 from Austin English <austinenglish(a)gmail.com> --- This is your friendly reminder that there has been no bug activity for over a year. Is this still an issue in current (1.7.51 or newer) wine? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=30735 super_man(a)post.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |super_man(a)post.com -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=30735 winetest(a)luukku.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |winetest(a)luukku.com --- Comment #23 from winetest(a)luukku.com --- (In reply to Austin English from comment #22)
This is your friendly reminder that there has been no bug activity for over a year. Is this still an issue in current (1.7.51 or newer) wine?
patching file dlls/ntdll/cdrom.c Hunk #1 succeeded at 747 (offset 4 lines). Hunk #2 succeeded at 2954 (offset 26 lines). Patch applies cleanly against wine 1.9.23-git. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
wine-bugs＠winehq.org