Newsgroups: comp.sys.mac.digest
Subject: Re: ResEdit 2.1.1 & SoftwareFPU incompatibility...
From: ibhan@husc10.harvard.edu (Ishir Bhan)
Date: 24 Dec 92 05:20:33 GMT

Info-Mac@sumex-aim.stanford.edu writes:

>Not that anyone probably really cares, but ResEdit 2.1.1 simply will not open
>ANYTHING if SoftwareFPU is installed ("Can't open resource [-192]" I
>believe).

>Just thought I might be able to save someone else the trouble of rebooting a
>hundred times (like I had to) until the offending cdev is found...

>The author of SoftwareFPU will be informed of this as well..

I had that problem with ResEdit on my docked Duo 230 (but not when it was
undocked).  It happened even when I restarted without INITs.  Reinstalling
the system solved the problem.
--
	       -  Ishir Bhan -  ibhan@husc.harvard.edu  -
				     - - -
	   "The sky and the impossible explode..." -The Cure

------------------------------

Date: Thu, 24 Dec 92 11:04:44 EST
From: James BelBruno (GC-CDSI) <belbruno@PICA.ARMY.MIL>
Subject: StyleWriter & Print Monitor

Forgive me to those who say I shouldn't post this question here. But...I
have been reading the last few days about how StyleWriter comes w/ a
utility ...Print Monitor...to speed up the SW printing basically...while u
work.  I purchased my SW in June.  Did this utility become included
afterwards?
I cannot find this utility at all on my system.  I looked in my SW manual
index could not locate anything about it.  I have had my Mac system for a few
months now and have not realized the full capabilities of it.  This is one
of the examples.         thanks for any help.
JB    Picatinny Arsenal, Dover, NJ

------------------------------

Date: 24 Dec 1992 14:19:16 -0700 (MST)
From: NOHL@CCIT.ARIZONA.EDU
Subject: video out for macs- see me

I have recently compiled a bit of info on video out for a mac.
Its pretty large but now worth leaving on sumex.

so, I know I'll regret it, but, send me E-mail, and I'll
send you a copy of my summary.

Nohl Lyons
Nohl@ccit.arizona.edu

------------------------------

Date: Thu, 24 Dec 92 12:35:59 PST
From: kroemer@apex.ece.ucsb.edu (Herb Kroemer)
Subject: WordPerf/Mac 2.1 <-> DOS 5.1 Transfers (4)

Thanks to Dave Reiser for his comments in #304 on the WP Inter-Platform
Transfer problem.

> ... The biggest problem is that
>fonts on the two platforms (for any software) are not identical. The problem
>is a bit worse for WordPerfect DOS because WPCorp. designed their own fonts
>for the DOS program. No matter what WPCorp does with fonts, unless the same
>type house wrote fonts with identical metrics for both platforms (ATM,
>anyone?) there is _no_ hope of perfect translations.

True enough, but most of what I see can NOT be credibly associated with
font metric problems.

>I'm not sure, but some of the margins and tabs problems may be related. WP
>may be attempting to compensate for known font metric conversion problems.
>I think they'd be better off translating margins and tabs exactly.

If that is indeed what they are doing, I would use rather stronger language
to characterize it. But frankly, I doubt that this is what is going on, and
even if it were, I find some of my transfer problems hard to explain by
this hypothesis.

Here is a rundown:

My problems started when I received a (good-looking) printout of a certain
document that was generated with WP5.1 on a DOS machine, along with a DOS
disk of the same file, done immediately after the printing. My task was to
do assorted contents revisions, andto return it. When I read the disk into
my Mac IIfx (Apple File Exchange or AccessPC; the results were the same),
and opened the transfer with my brand-new WMacP2.1.2, the results looked
messy, quite different than the WP5.1 printout. Some justified paragraphs
had been converted into centered paragraphs, some italics were gone, a
string of underlined blanks showed up out of nowhere, some returns were
missing, and there were assorted horizontal misalignments that might indeed
be font metric related.

I fixed up all the glitches, did my revisions, and saved and printed the
document (it looked gorgeous). I then saved another copy in 5.1 format, for
returning to my partner. Just to check the accuracy of the transfer, I
re-imported the 5.1 version into WPMac: Some tabs in the re-imported
version were simply not at the place where they had been in the 2.1
version, and the page layout was again messed up (although far less bad
than after the original transfer).

Following a call to WP's 800 number, I sent the various disk files and
accompanying printouts to WP for dissection. Stay tuned.

>Also, the file transfer capability definitely falls down on multiple passes
>between platforms. There is some degradation on the return of a round trip.

I can live with that for exotic features, such as fancy page borders, but I
find it inexcusable for features as basic as tabs. To me, multiple passes
are the essence of cross-platform compatibility.

Regards,
Herb K.

------------------------------

Date: 24 Dec 1992 19:53:56 +0100 (CET)
From: tsvetkova@news.rferl.org (Alexei Tsvetkov)

	My apologies for probably causing an unnecessary rush by providing
an ftp address for the Macintalk, which turned out to be something else. As
Murph Sewald informed me, it is a HC external for Macintalk, not the beast
itself.
	I gophered that file and was deceived by the fact that somebody had
archived it under the name Macintalk. There was no way to check it at the
moment.
	Sorry, will try again. Happy holidays.
Alexei Tsvetkov
Munich

------------------------------

Date: 24 Dec 1992 19:54:02 +0100 (CET)
From: tsvetkova@news.rferl.org (Alexei Tsvetkov)

>My daughter's Ehman drive went fritz. Can anyone tell me who services these
>>jobbies now-adays? What is the relevant telephone number and address?
>er and address?

Seems, you are out of luck. Ehman went belly up. If you browse through the
couple of recent issues of MacUser, there should be an article on it and
you might find a phone number, but don't get you hopes too high.
Alexei Tsvetkov
Munich

------------------------------

End of Info-Mac Digest
******************************