http://bugs.winehq.org/show_bug.cgi?id=1142
------- Additional Comments From wine(a)deesconsulting.com 2004-10-10 07:49 -------
This bug is also present in Crossover Office Pro 3.0.1, based on wine version
20040505, at least in networked environments (NFS, SMB). I have not tested it
locally.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=1142
------- Additional Comments From wine(a)deesconsulting.com 2004-10-10 07:34 -------
I suspect this may be a duplicate of bug 1071, and I can confirm it is present
in Codeweavers Crossover Office Professional 3.0.0 with Office XP. 3.0.0 says
it's based on wine version 20040213.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=2507
Summary: Fallout: mouse doesn't move at all
Product: Wine
Version: unspecified
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-directx
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: wsapplegate(a)myrealbox.com
Executive summary :
~~~~~~~~~~~~~~~~~~~
Fallout is and old (circa 1997) RPG, published by Interplay. Upon recently
trying to reinstall the game, I came across a problem : the mouse wouldn't
move. Even performing the installation through the keyboard wasn't of much
help, since the game exhibited the same problems (it also grabbed my pointer,
I needed to escape the uncontrollable game window by changing virtual desktop
and moving the pointer out of the way).
Analysis :
~~~~~~~~~~
Quite frankly, I really don't know enough about DirectInput to know why that
problem appeared, but I've at least found what causes it. The problem appears
since WINE 20040615, which has seen an overhaul of several DirectInput-related
files. The problem is located in the file dlls/dinput/device.c and has
apparently been caused by a CVS commit on 2004-06-02[1]. In the function
create_DataFormat(), the following lines are changed :
- (wine_format->rgodf[i].dwType &
asked_format->rgodf[j].dwType)) {
+ (/* Then check if it accepts any instance id, and if not, if
it matches Wine's
+ * instance id.
+ */
+ ((asked_format->rgodf[j].dwType & 0x00FFFF00) ==
DIDFT_ANYINSTANCE) ||
+ (DIDFT_GETINSTANCE(wine_format->rgodf[i].dwType) ==
DIDFT_GETINSTANCE(asked_format->rgodf[j].dwType)))) {
Reverting this change makes the mouse to work again.
[1]
http://cvs.winehq.com/cvsweb/wine/dlls/dinput/device.c.diff?r1=1.16&r2=1.17…
How to reproduce :
~~~~~~~~~~~~~~~~~~
Assuming you have a Fallout CD in drive D:,
* run "wine 'd:\\_setup.exe'" (alternatively, if the game is already
installed, run "wine <path to the game directory>\falloutw.exe")
* notice you cannot move the mouse
Solutions and workarounds :
~~~~~~~~~~~~~~~~~~~~~~~~~~~
I've found no workaround for this problem. Reverting the change in
create_DataFormat() works for me, but is probably incorrect (I haven't been
able to ascertain what effects it could have on other DirectInput-based
software).
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=2506
wsapplegate(a)myrealbox.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Platform|Other |PC
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=2506
------- Additional Comments From wsapplegate(a)myrealbox.com 2004-10-10 03:54 -------
[cont'd. Sorry, clicked on Commit by mistake]
... an affected version, a possible workaround is to install the game
partially, copy the missing files manually, then edit the file fallout.cfg in
the installation directory, and edit the paths by hand.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=2506
Summary: Fallout installer reports incorrect disk space
Product: Wine
Version: unspecified
Platform: Other
OS/Version: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: wine-kernel
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: wsapplegate(a)myrealbox.com
Executive summary :
~~~~~~~~~~~~~~~~~~~
Fallout is an old (circa 1997) RPG, published by Interplay. The game doesn't
use a standard installer (like InstallShield or similar). Rather, Interplay
did write a custom installer. While recently trying to reinstall this game, I
was confronted to a weird problem : the reported disk space was about 268 MiB
instead of 2147 MiB as previously reported. Both values are in fact incorrect
(the hard disk has much more than 2 GiB), but the latter allows for a complete
installation, while the former only allows a limited installation, the
remainder being read from the CD-ROM.
Analysis :
~~~~~~~~~~
A quick investigation shows that the problem only occurs since WINE 20040505.
Not coincidentally, this version contains changes to the GetDiskFreeSpace*
functions. Tracing the _SETUP.EXE function calls, it indeed appears it makes
calls to GetDiskFreeSpaceA(), which in turn calls GetDiskFreeSpaceW(). This
functions returns values capped at 2 GiB, with the following parameters : 4096
bytes per sector, 1 sector per cluster, 524287 clusters. From the behaviour
exhibited by the installer, it unfortunately appears the programmers used a
16-bit sized variable to store the clusters value, thus generating incorrect
results when this number is above 65535, as reported by the new
GetDiskFreeSpaceW().
How to reproduce :
~~~~~~~~~~~~~~~~~~
You need (1) a HDD with more than 2 GiB free space and (2) a copy of Fallout.
Then, execute the following steps (assuming your CD-ROM is mounted as D:)
* run "wine 'd:\\_setup.exe'"
* notice the free space reported for the hard disk is incorrect
Solutions and workarounds :
~~~~~~~~~~~~~~~~~~~~~~~~~~~
I personally solved the problem by kludging the GetDiskFreeSpaceW() function
in dlls/kernel/volume.c to report a number of cluster below 65535 (for a 2 GiB
disk, it reports 512 bytes * 64 sectors * 65535 clusters), but it's most
probably incorrect (these values are not consistent with the values reported
by NtQueryVolumeInformationFile()). If you run
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=824
------- Additional Comments From randy.galbraith(a)cox.net 2004-10-10 00:05 -------
I would like to see if I could resolve this bug. However, I'm having some
difficulty understanding the exact nature of the original description. In
particular, can the import/export steps below be reproduce on Windows XP or just
Windows 95/98/ME? I.e., does Unicode support get in the way?
Here is an example program I wrote in an attempt to recreate this issue:
http://members.cox.net/~rgalbraith10/wine/bug824/demo824.chttp://members.cox.net/~rgalbraith10/wine/bug824/Makefile
When this program is run on Windows XP (compiled with gcc under cygwin) the
exported registry looks like this:
[HKEY_CURRENT_USER\Software\Wine\Bug824]
"Empty Value0"=hex(7):
"Empty Value1"=hex(7):00,00
"Empty Value2"=hex(7):01,00,00,00
When the program is run under Wine (20040914) the exported registry looks like this:
[HKEY_USERS\randy\Software\Wine\Bug824]
"Empty Value0"=hex(7):00
"Empty Value1"=hex(7):00
"Empty Value2"=hex(7):01,00
So, we can see "Empty Value0" is reporting "00" (which is the issue at hand).
However, what am I to make of Windows XP's "00,00" and "01,00,00,00"? I assume
this is because Unicode support, but is part a worry?
Interestingly user.reg in Wine stores these entries as this:
[Software\\Wine\\Bug824] 1097383218
"Empty Value0"=str(7):""
"Empty Value1"=str(7):""
"Empty Value2"=str(7):"\1"
Would it be correct to assume the basic issue is the choice of "str(7)" as the
data type for REG_MULTI_SZ?
Since this is my first ever post to Wine/Bugzilla, I would appreciate any
helpful netiquette points (i.e. should I post to mailing list/newsgroup first,
are URLs (as above) preferred over attachments).
Kind regards,
-Randy Galbraith
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=1511
------- Additional Comments From hallo(a)michael-kaufmann.ch 2004-09-10 15:41 -------
Now I understand... If the buffer is NULL *and* count is zero, GetObject
should return the size of the object.
This is also fixed. I don't know whether Mike McCormack has read this bug
report, but he has fixed it with this patch:
http://www.winehq.org/hypermail/wine-patches/2003/07/0289.html
So we can safely close this bug.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.