🚀 go-pugleaf

In article <1993Jan26.042652.26256@odetics.com> frank@odetics.com (Frank Merrow) writes:
>Hi,
>
>I do not have an OS/2 system up yet, but I am being gently pushed
>in that direction.  I asked the FrameMaker folks if my MS-Windows
>version would run under OS/2.  The official answer is "not reliably".
>Then I noticed the one byte patch in the OS/2 FAQ (thank you
>Tim).  I less trusting individual might think that FrameMaker had
>deliberatly put an OS/2 incompatable instruction in the code, but I
>would never think such a thing!
>
>At any rate, I was wondering if anyone had actually attempted the
>patch and how well FrameMaker then runs under OS/2.  Also, once
>patched will the MAKER.EXE file still run under MS-Windows?  FrameMaker
>is the ONE program that is holding me to MS-windows.

As the orginator of said patch, though I have never acknowledged it,
perhaps I ought to comment..

As near as I can tell, on my standalone 486 system (ie. no LAN products),
it works as well as it did under DOS+WINDOWS.  No differences that I can see.
Editing, templates, fonts, printing, etc.. all work just peachy.  Note that
FrameMaker prefers Windows 3.1 for the truetype fonts, but it works just fine
under windows 3.0.. some font names differ, that's all.

The patched file works just fine under DOS+WINDOWS as well, so long as you
ensure that you only try it in Windows Enhanced mode, never "standard" or "real"
modes (the patch simply removes the check for those).  Under OS/2, either 
standard mode or (beta 2.1) Enhanced mode are fine.