http://bugs.winehq.org/show_bug.cgi?id=27981
--- Comment #3 from Patrick J pato.jamriska@gmail.com 2011-08-08 20:01:16 CDT --- I went ahead and did a nuke on wine to test around if there was something else making the problem since I had adobe installed as well. Well, the fresh install got rid of the winspool error, but still gave me the crash line of the stack trace attached. The bug started on 1.3.22 and on from what I was testing on previous versions. I will do the bisect later on and post it. Sorry for the late reply, but I have been busy with a project, and I happen to use this software too much I ended up going back on wine while I had it finished.
(In reply to comment #2)
Do the working versions print the message about winspool.drv.DEVICECAPABILITIES? If not, a change somewhere else has probably made the program start to use this function when it hadn't before, and the correct fix is to implement that function.
Otherwise, a bisect would help.