[Bug 2096] Quicken 2000 Deluxe crashes/Bad parm to CreateBitmap

[Wine Bugs]

http://bugs.winehq.org/show_bug.cgi?id=2096

------- Additional Comments From [e-mail]  2007-05-01 09:51 -------
The application still crashes, using wine 0.9.27 (as distributed by the Fedora
Project as wine-core-0.9.27-1.fc6), as this trace shows:

trace:bitmap:CreateBitmapIndirect 20x16, 65536 colors returning 0x4358
trace:bitmap:CreateCompatibleBitmap             0x4358
trace:bitmap:CreateCompatibleBitmap (0x31c,20,16) =
trace:bitmap:CreateBitmapIndirect 20x16, 65536 colors returning 0x435c
trace:bitmap:CreateCompatibleBitmap             0x435c
trace:bitmap:CreateBitmapIndirect 1614982020x1615206720, 2 colors returning 0x4484
trace:bitmap:CreateBitmapIndirect 1614982020x1615206720, 2 colors returning 0x4488
trace:bitmap:CreateCompatibleBitmap (0x31c,1614982020,1615206720) =
fixme:bitmap:CreateCompatibleBitmap got bad width 1614982020 or height
1615206720, please look for reason
trace:bitmap:CreateCompatibleBitmap             (nil)
trace:bitmap:CreateCompatibleBitmap (0x31c,1614982020,1615206720) =
fixme:bitmap:CreateCompatibleBitmap got bad width 1614982020 or height
1615206720, please look for reason
trace:bitmap:CreateCompatibleBitmap             (nil)
X Error of failed request:  BadAlloc (insufficient resources for operation)
  Major opcode of failed request:  53 (X_CreatePixmap)
  Serial number of failed request:  9234
  Current serial number in output stream:  9261

Unfortunately, this is the most recent version of wine that I have readily
available.  More unfortunate is the fact that I don't have enough time to spend
on getting to the root cause, although I've spent considerable time on this in
the past.  If someone is willing to spend some time with me on this, I can be
persuaded to dive back in (although it might be time consuming just to get to a
point where I'm able to do any real debugging work - i.e., set up a working cvs
version).

I can't verify this, but after looking at the patch, it seems to me that I tried
it to no avail.  If this bug becomes active again, I could give it another shot.
 However, after refreshing my memory on C syntax, it doesn't look like it will
work in the case provided above (both height and width are huge). (It looks like
it just prevents the message if one of the height or width is zero.  Am I
reading this right?  It's been a while since I've used C...)

This is a real pain when printing checks, but the checks do print (the crash is
after sending the spool file).  I just have to manually enter the check numbers
- after re-launching Quicken, of course...

HTH,

Carl