lacsap@media-lab.MEDIA.MIT.EDU (Pascal Chesnais) (12/13/90)
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... MIT received some 040 nextstations but no 040 upgrades. NextStation is wicked fun! However several things to piss some people off: - incredibly short monitor cable, if you want a long one, see if you can order the Cube starting point kit instead - keyboard layout has changed!!! They made the return key bigger, inverted L shape, and moved the key above it |\ to the number keypad... Which you can all imagine how annoying it is when you want to do a lot of pipes or do C programming... A real lose if you ask me... I bet the response you get from NeXT about this one is "We had a lot of customers asking for a bigger Return key", yet they probably did not poll a lot of people about the wisdom of moving the | key on a Unix workstation. Oh the keyboard has symbols instead of words like "shift", "tab"... the bug is that the delete and back arrow keys are the same symbol!!! I still like the machines, hope someone can help with the above problems (CL and Frame) so we can upgrade the other 1.0 machines... If you got it work using 2.0 upgrade app let me know too! pasc -- Pascal Chesnais, Research Specialist, Electronic Publishing Group Media Laboratory, E15-348, 20 Ames Street, Cambridge, Ma, 02139 (617) 253-0311 email: lacsap@plethora.media.mit.edu (NeXT)
dml@esl.com (Denis Lynch) (12/22/90)
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