Thanks a lot for all quick answers. My original questions:
>I just finished installing and configuring (from scratch) the
>following setup:
>
>Hardware:
>AlphaStation 500/500
>288 MB RAM (256 MB 3rd-party DataRAM memory)
>PowerStorm 4D40
>
>On this I thereafter installed DU 4.0B, C++, Fortran, Pascal and C++
>runtime from the associated products CD. After that I proceeded with
>Open3D 4.1 (O3D410) from the Oct '96 Layered Priducts CD.
>
>All of this went very smooth and most things works perfectly. There
>are some more and less serious problems that appear to be graphics
>related:
>
>The worst problem is that Matlab 5.0 hardly runs at all if it wants to
>use X-windows. All I get is an never-ending barfing of:
>
>"Unaligned access pid=(some pid) <matlab> va=(varies) pc=0x12048175c
>inst=0xb6e00000"
>
>If I run matlab without $DISPLAY set, everything runs fine (no
>graphics of course) and fast as hell too. If I let it run against a
>remote display (in this case a AS200 4/100) I still get a lot of the
>errors but it works.
>
>Matlab v4.2c also produces simliar errors, but can be run with DISPLAY
>on the AS500.
>
>Aside the matlab problem (which for us is the by far most serious one)
>netscape (either the 3.0 shipped with DU4.0B or the 3.01 i normally
>use) tends to crash far more easily on this system than on any other
>DU box that we've got here.
>
>The system that gets closest to this setup is a AS500/266 with a
>PowerStorm 3D30. This system has the same operating system and
>software installed (exactly the same versions).
>
>Any ideas or hints on how to solve this will be greatly appreciated.
>I just finished installing and configuring (from scratch) the
>following setup:
The "unaligned memory access"-problem seems to be a well known one and
it's obviously not restricted to Matlab. The solution (or shall we say
cover-up) is to turn of memory alignment error reporting by issuing a
'uac -p noprint' command. After doing so everything _looks_ pretty
normal at least. It seems as if MathWorks could have done a little
better.
As far as the problems with dying Netscapes are concerned there were
no solutions - but hey, Netscapes dies all the time. A possible cause
could be that DU4.0B requires Open3D 4.2 as indicated by another
response by the manager. I will go about and find myself a newer
distribution.
Thanks again!
/Erik
These were the answers:
---
From: Mike Iglesias <iglesias_at_draco.acs.uci.edu>
We've complained to Mathworks about matlab getting unaligned accesses
on 4.0b. No response as far as I know.
You can use the "uac -p noprint" command to get rid of the error
messages you're seeing if that bothers you.
I've had netscape die a few times on me, but not very often.
---
From: Salil Parikh <parikh_at_ll.mit.edu>
I ran into this problem with ghostscript. I think you'll find that if you
wait long enough, the barfing will stop, and windows will eventually appear.
I'm not exactly sure of what's going on but here is how to fix it. Type
this in the window you launch matlab from, and then launch matlab.
% uac p noprint
Let me know if this stops the barfing.
---
From: smcfa_at_hcia.com (Steve McFadden)
You might try Open3D version 4.2 - DEC tech support has told us that
4.0B
needs Open3D 4.2 if you have specific video cards including the
PowerStorm
series.
---
--
Erik Persson Home: +46 13 12 38 89
Banergatan 9 Work: +46 13 28 24 64
582 32 Linkoping, Sweden e-mail: erik_at_lysator.liu.se
Received on Wed Apr 30 1997 - 00:40:41 NZST