[Prev][Next][Index][Thread]

Re: Executor 1.99q12 fatal error



On 4 Apr 1996, EADEANS wrote:

> running Aldus SuperPaint 3.5--it happens on startup after reading
> Preferences and displaying the logo. I don't know if it'll ever work under
> Executor, but I wanted to let you guys know because I *really* want to run
> it because for some items it's better than PhotoShop on WinOS2.
> 

Aha!! I really want to use SuperPaint, too. I just tried V. 2.0. under
E1.99Q12. It warned me that the app was not 32-bit clean and might not
work at all...and then went on to work pretty darn good. Until...I tried
to type text in the draw mode. Then it crashed with the following dump:

eax=5f80001b ebx=00000000 ecx=00087768 edx=00000000 esi=00000000 edi=00000000
ebp=001fa95c esp=001fa95c cs=00a7 ds=00af es=00af fs=00ef gs=00cf ss=00af
Call frame traceback EIPs:
	0x000b0c8e
	0x0008d80a
	0x0008db7b
	0x000dace2
	0x000ede64

I should add, too, that the line width part of the draw palette is 
slightly skewed. Otherwise, it seems to work quite well. I tried it 
again, and was able to type text in the paint mode, and in fact, cut/copy 
that text to the draw mode. But when I tried to type text in draw mode 
again, it created a huge(like, down to the bottom of the page!) rectangular 
text frame, and wouldn't give me a stable cursor. Didn't crash again, 
though, although it looked for a few moments like it wanted to. I thought 
perhaps if I upgraded to 3.x I might be more successful, but now, dunno.

Any guesses on the prognosis for this app?

Steve Lelchuk
Principal Secretary		User Services Specialist
Minnesota Center for		Department of Philosophy
  Philosophy of Science		University of Minnesota
mcps@maroon.tc.umn.edu          lelch001@maroon.tc.umn.edu




Follow-Ups: References: