http://bugs.winehq.com/show_bug.cgi?id=421
------- Additional Comments From aljones(a)lbl.gov 2002-09-05 14:07 -------
from the description:
>* the X bitmap has to be in the format of the X display. So if X is running in
> 15bpp, a 32bpp DIB is converted to 15bpp, the operation is performed in 15bpp,
> and the bitmap is then converted back to 32bpp. Obviously this implies that
> each operation occurs a loss of color resolution (fortunately they should not
> accumulate).
for my version of X this no longer seems to be required:
vendor string: The XFree86 Project, Inc
vendor release number: 40199001
XFree86 version: 4.1.99.1
...
supported pixmap formats:
depth 1, bits_per_pixel 1, scanline_pad 32
depth 4, bits_per_pixel 8, scanline_pad 32
depth 8, bits_per_pixel 8, scanline_pad 32
depth 15, bits_per_pixel 16, scanline_pad 32
depth 16, bits_per_pixel 16, scanline_pad 32
depth 24, bits_per_pixel 32, scanline_pad 32
depth 32, bits_per_pixel 32, scanline_pad 32
even though my screen is only in depth 15, i can
manipulate pixmaps of any depth. i haven't yet
figured out how to manipulate color information in
these other pixmaps (save for just setting the pixel
values directly -- works ok for TrueColor), but
drawing seems to work fine...
arthur
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=421>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=1010
------- Additional Comments From andi(a)rhlx01.fht-esslingen.de 2002-09-05 11:47 -------
Argl, I meant --debugmsg +relay
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=1010>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=1010
------- Additional Comments From andi(a)rhlx01.fht-esslingen.de 2002-09-05 11:46 -------
Did you realize what you just said ? You said it's a *workaround*, not a bug fix.
Thus this bug is still valid :)
(as I'm damn sure that VFP *should* run on a Win 9x based system)
Sounds like there's a problem with some Wine Win9x support code that's being run
when the app decides to switch to Win9x mode instead of NT mode.
So should that bug be reopened ?
(please submit a --debugmsg +Relay log file in win9x mode in this case)
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=1010>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=1010
------- Additional Comments From oscar.valdez(a)plastipak.com.sv 2002-09-05 11:35 -------
No, that's not exactly the way I would interpret things.
At least on Wine, Visual FoxPro "runs" when Wine is imitating NT40, W2K or WXP,
but not when it's imitating W9x. It seems like a simple workaround.
And I say "runs", because I'm still getting OLE exception errors.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=1010>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=1010
------- Additional Comments From andi(a)rhlx01.fht-esslingen.de 2002-09-05 11:24 -------
So you want to tell us that Visual FoxPro only runs on an NT-based Windows version
(NT, Win 2000, XP) and never on a Win 9x system, right ?
Or why else would you consider this bug to be closed ?
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=1010>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=1010
oscar.valdez(a)plastipak.com.sv changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |WORKSFORME
------- Additional Comments From oscar.valdez(a)plastipak.com.sv 2002-09-05 11:11 -------
I've gotten over this problem by setting "nt40", "win2k" or "winxp" as the
Windoze version to imitate.
The Visual FoxPro application now runs, although with "OLE exception errors".
That's a completely different matter though, so I consider this particular case
closed.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=1010>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=1008
mcbridematt(a)hotmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
everconfirmed|0 |1
------- Additional Comments From mcbridematt(a)hotmail.com 2002-09-05 03:29 -------
*** This bug has been confirmed by popular vote. ***
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=1008>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://bugs.winehq.com/show_bug.cgi?id=1007
------- Additional Comments From centaur(a)netmagic.net 2002-09-04 23:55 -------
Here's abbreviated --debugmsg +relay output, though I'm not really sure if I've
gotten the part where it starts to barf. I've done some more reading, and it
sounds to me like CreateToolhelp32Snapshot and friends are typically used for
Windows debugging (is this correct?) so maybe the real culprit is further up the
chain. Any help would be greatly appreciated!
08c58100:Call user32.GetCursorInfo(422a6590) ret=40c743a4
08c58100:Call x11drv.GetCursorPos(422a659c) ret=408279ad
08c58100:Ret x11drv.GetCursorPos() retval=00000134 ret=408279ad
08c58100:Ret user32.GetCursorInfo() retval=00000001 ret=40c743a4
08c58100:Call kernel32.GetCurrentThreadId() ret=40c73473
08c58100:Ret kernel32.GetCurrentThreadId() retval=08c58100 ret=40c73473
08c58100:Call user32.GetQueueStatus(000000bf) ret=40c743d0
08c58100:Ret user32.GetQueueStatus() retval=00000000 ret=40c743d0
08c58100:Call kernel32.GetCurrentThreadId() ret=40c73473
08c58100:Ret kernel32.GetCurrentThreadId() retval=08c58100 ret=40c73473
08c58100:Call kernel32.FreeLibrary(407e0000) ret=40c743f1
08c58100:Ret kernel32.FreeLibrary() retval=00000001 ret=40c743f1
08c58100:Call kernel32.GetProcAddress(40610000,40cbe7f0
"CreateToolhelp32Snapshot") ret=40c74401
08c58100:Ret kernel32.GetProcAddress() retval=40677000 ret=40c74401
08c58100:Call kernel32.GetProcAddress(40610000,40cbe7e4 "Heap32First")
ret=40c7440b
08c58100:Ret kernel32.GetProcAddress() retval=4061771c ret=40c7440b
08c58100:Call kernel32.GetProcAddress(40610000,40cbe7d8 "Heap32Next")
ret=40c74417
08c58100:Ret kernel32.GetProcAddress() retval=40617770 ret=40c74417
08c58100:Call kernel32.GetProcAddress(40610000,40cbe7c8 "Heap32ListFirst")
ret=40c74423
08c58100:Ret kernel32.GetProcAddress() retval=40617738 ret=40c74423
08c58100:Call kernel32.GetProcAddress(40610000,40cbe7b8 "Heap32ListNext")
ret=40c7442d
08c58100:Ret kernel32.GetProcAddress() retval=40617754 ret=40c7442d
08c58100:Call kernel32.GetProcAddress(40610000,40cbe7a8 "Process32First")
ret=40c74439
08c58100:Ret kernel32.GetProcAddress() retval=40678d10 ret=40c74439
08c58100:Call kernel32.GetProcAddress(40610000,40cbe798 "Process32Next")
ret=40c74445
08c58100:Ret kernel32.GetProcAddress() retval=40678d20 ret=40c74445
08c58100:Call kernel32.GetProcAddress(40610000,40cbe788 "Thread32First")
ret=40c74451
08c58100:Ret kernel32.GetProcAddress() retval=406797c0 ret=40c74451
08c58100:Call kernel32.GetProcAddress(40610000,40cbe778 "Thread32Next")
ret=40c7445d
08c58100:Ret kernel32.GetProcAddress() retval=406797d0 ret=40c7445d
08c58100:Call kernel32.GetProcAddress(40610000,40cbe768 "Module32First")
ret=40c74469
08c58100:Ret kernel32.GetProcAddress() retval=40678ad0 ret=40c74469
08c58100:Call kernel32.GetProcAddress(40610000,40cbe758 "Module32Next")
ret=40c74475
08c58100:Ret kernel32.GetProcAddress() retval=40678ae0 ret=40c74475
08c58100:Call kernel32.CreateToolhelp32Snapshot(0000000f,00000000) ret=40c744f7
08c58100:Ret kernel32.CreateToolhelp32Snapshot() retval=000000c4 ret=40c744f7
08c58100:Call kernel32.GetLastError() ret=00443683
08c58100:Ret kernel32.GetLastError() retval=00000002 ret=00443683
08c58100:Call kernel32.TlsGetValue(00000009) ret=00443691
08c58100:Ret kernel32.TlsGetValue() retval=41bd01e0 ret=00443691
08c58100:Call kernel32.SetLastError(00000002) ret=004436dd
08c58100:Ret kernel32.SetLastError() retval=00000002 ret=004436dd
08c58100:Call kernel32.UnhandledExceptionFilter(422a60a0) ret=00444eb6
08c58100:Call kernel32.IsBadCodePtr(7800b322) ret=00449078
08c58100:Ret kernel32.IsBadCodePtr() retval=00000000 ret=00449078
wine: Unhandled exception, starting debugger...
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=1007>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.