🚀 go-pugleaf

The manual for the Mac version of Prodigy says it doesn't run under 
MultiFinder.  After poking around a bit, I figured out how to make them 
co-exist (somewhat).  With a couple of simple changes, you can at least 
run it without having to reboot.

It turns out that the reason Prodigy crashes under MultiFinder is that it 
allocates a huge (280K) non-relocatable block.  It also has no SIZE 
resource, so its default partition size is 384K.  If you increase this to 
750K then the application will run under MultiFinder.

You still won't be able to access any menus, but if you click on a Finder 
icon (on a different screen), then you can switch into the Finder.  
Unfortunately, this is a bad idea (I haven't figured out why, yet); when 
you switch back into Prodigy the screen doesn't update, and you won't be 
able to do anything else.

The best thing to do is to open up the Prodigy application and change the 
resource WIND 130 to have procID 1.  This will prevent you from switching 
out of Prodigy inadvertently.

The only other problem is that when you quit the application, your desktop 
is messed up.  This is only a cosmetic problem.  If, however, you have to 
exit Prodigy abnormally, your system will be messed up.  (Prodigy erases 
the menu bar and modifies GrayRgn; if you crash these things won't be 
restored.)  I'm thinking about ways to work around this problem. 


Larry Rosenstein, Apple Computer, Inc.
Object Specialist

Internet: lsr@Apple.com   UUCP: {nsc, sun}!apple!lsr
AppleLink: Rosenstein1