🚀 go-pugleaf

	I have now tried out three more GIF viewers, and all of them have
failed in the same way ("Error in EXE file" + partial system lockup) after
beautifully displaying one GIF picture.  Here are some straws it occurred to
me to clutch at:
	Does it make any difference that I'm starting the viewer programs
from a ramdisk in extended (expanded?) memory?
	Does it make any difference that I have a bunch of memory-resident
stuff?
	Is there a way of converting EXE files to COM files, and would
*that* make any difference?
	I call these straws, because I still suspect that the real problem
is a cheap, non-register-compatible EGA card, and I'm reluctant to spend the
money for the upgrade at the moment.  Is any of those straws worth going to
the trouble of testing?  Or am I just going to have to be temporarily
content with rebooting after each GIF picture?  (It makes for a *slow*
slideshow!)  Thanks for listening.

-- 

JAY ROSENBERG  Dept. of Philosophy  CB# 3125  UNC  Chapel Hill, NC  27599
...{decvax,akgua}!mcnc!ecsvax!unbent         ...tucc!tuccvm!ecsvax!unbent  
   unbent@ecsvax.UUCP      unbent@ecsvax.BITNET      unbent@unc.BITNET