Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!gatech!psuvax1!wuarchive!usc!apple!voder!pyramid!leadsv!esl!esl.ESL.COM!news From: dml@esl.com (Denis Lynch) Newsgroups: comp.sys.next Subject: Re: 2.0 - CommonLisp and Frame - 040 Message-ID: Date: 22 Dec 90 01:12:43 GMT References: <4334@media-lab.MEDIA.MIT.EDU> Sender: news@esl.ESL.COM Reply-To: dml@esl.com Distribution: usa Organization: ESL Inc., Sunnyvale, CA Lines: 37 In-reply-to: lacsap@media-lab.MEDIA.MIT.EDU's message of 12 Dec 90 21:15:41 GMT In article <4334@media-lab.MEDIA.MIT.EDU> lacsap@media-lab.MEDIA.MIT.EDU (Pascal Chesnais) writes: We just got a 2.0 distribution disk, we scrubbed disks and layed down the new OS. We copied allegro and frame onto the system. Ran upgrade frame package, and tried rebuilding CL. CL did not build ld claiming that there is a cputype mismatch! Frame starts and promptly crashes with a DPS error... Has anyone hand massage these two things into running on their 2.0 systems? I would be pretty angry to find out we have to wait a while before we get upgrades... Ya know, I was hoping that I was the only one with this stupid Frame problem. Here's what you need to do to fix it: su to whoever owns the FrameMaker app cd where-ever-you-put-it/FrameMaker.app/.fminit2.0/next mv makerbegin.ps makerbegin.ps.broken mv makerprint.ps makerprint.ps.broken sed "s/NR/NP/" makerbegin.ps.broken > makerbegin.ps sed "s/NR/NP/" makerprint.ps.broken > makerprint.ps In other words, change the definition of NR back to a definition of NP, like it used to be. **Beware** I have only tested the result for a little while, so no promises! I can't help but wonder if there is more than one version of the FrameMaker executable out there. How could this have slipped through any kind of testing at all??? (It's pretty hard to miss the fact the the app doesn't come up at all, isn't it?) Any other info would certainly be appreciated! Denis Lynch, ESL Inc. dml@esl.com