System Fault: Bad Memory Access - Help required
Crispin Driver
Help!
We are running Microstation 95 under Windows 95 on the following
machine:
Pentium P90
32MB RAM
512kB Cache
1GB HDD
Graphics Card: Datapath Twin Orion 64 running 1 x 15", 1 x 21"
Whenever we try to export files to other formats, we receive the
following error:
System Fault: Bad Memory Access
I have tried the following, to try to identify the problem, but all to
no avail (the machine is now reset to its optimal configuration):
Read the Manuals ! - no help
Removed and checked the pin connections on the RAM chips - no help
Run various system checks on the RAM - OK
Disabled the Internal and External Cache in BIOS - no help
Scanned the HDD for surface/file creation errors - OK
Disabled the virtual memory in Win 95 - sloooow, but no help
Run the system in single screen mode - no help
re-installed Ustation and Graphics drivers - no help
cleared out the old .sfi and .sfo files, and allowed Ustation to create
new ones - no help
And am now fresh out of ideas!
The reason we are having to export these files is because we are unable
to plot anything on our HP7585 plotter - we just get garbled plots! We
have re-installed the s/w and drivers, but without success, so I guess
this is the root problem. If you could help solve either of these, we
would be very grateful.
Thanks in Advance
--
Crispin Driver c.dr...@davallmg.demon.co.uk
Don H. Fu [Bentley]
Crispin,
Do you mean that this happens to ALL file formats to which you have attempted to
export? I suggest you to verify integrity of the DGN file by running EDG and see
what it reports. If your DGN file is clean, we will need more information to
identify the root of the cause. I have forwarded your post to our Tech Support who
will help you to solve this problem.
Regards,
Don Fu
--
+=================================================================+
| Don H. Fu, Ph.D. | Phone: (610) 458-2847 |
| Bentley Systems, Inc. | Fax.: (610) 458-1060 |
| 690 Pennsylvania Dr. | Internet: Don...@bentley.com |
| Exton, PA 19341 | BSI Web: http://www.bentley.com |
+=================================================================+
/
/
/
/
/
/
/
/
/
/
/
/
/
RCrenwelge
In article <U2TqgBAr...@davallmg.demon.co.uk>, Crispin Driver
<c.dr...@davallmg.demon.co.uk> writes:
You may try trimming down the devices/drivers being loaded into memory.
It may be that Ustn is running out of allocated memory because of other
devices/drivers loaded when the machine boots up. Good Luck.
Randy
David Putman
>Help!
>
>We are running Microstation 95 under Windows 95 on the following
>machine:
>
>Pentium P90
>32MB RAM
>512kB Cache
>1GB HDD
>Graphics Card: Datapath Twin Orion 64 running 1 x 15", 1 x 21"
>
>Whenever we try to export files to other formats, we receive the
>following error:
>
> System Fault: Bad Memory Access
>
We also rec'd the infamous Bad Memory message. We got it when we did
repeated rapid zoom-ins also when we where using Decartes. The VAR told
us it was because Microstation was not "cleaning up behind it self" and
was leaving thing behind cluttering up the memory. Never did realy
resolve the problem. And as it was a random thing we have just lived with
it
David @ Icon
Joe Mac
David Putman wrote:
> >We are running Microstation 95 under Windows 95 on the following
> >machine:
> >
> >Pentium P90
> >32MB RAM
> >512kB Cache
> >1GB HDD
> >Graphics Card: Datapath Twin Orion 64 running 1 x 15", 1 x 21"
> >
> >Whenever we try to export files to other formats, we receive the
> >following error:
> >
> > System Fault: Bad Memory Access
> >
> We also rec'd the infamous Bad Memory message. We got it when we did
> repeated rapid zoom-ins also when we where using Decartes. The VAR told
> us it was because Microstation was not "cleaning up behind it self" and
> was leaving thing behind cluttering up the memory. Never did realy
> resolve the problem. And as it was a random thing we have just lived with
> it
Exporting to DXF/DWF/IGES or whatever requires a certain amount of mapping
of attributes, and this is assisted by a bunch ASCII text files. I am in no
doubt that this is not new to you. What you may not be aware of is that
there are a few problems that can crop up as a result of how these files
are edited. These problems _regularly_ result in this MDL Abort thing. I
have seen it *far* too often for my own liking.
I would suggest that you avoid editing them through the MicroStation
dialogues and instead use a normal text editor like Notepad or Dos-Edit.
Make sure that you are not mapping one-to-two, that is that your file does
not have, for example, one colour from one package mapping to two
differenct colours in another. I have seen this.
The sure-fire thing to do would be to edit each and every file, wiping the
contents and manually inserting the values yourself. For example, the
COLOUR.TBL file for DXF/DWG translationwould look something like this:
1<space>0
2 1
3 2
4 3
Autocad values on the left, MS on the right. Autocad afaik does not employ
a colour zero. take the values up to 254 for MS and 255 for Acad.
Also, have seperate sets of tables for Importing and Exporting.
Alternatively, drop me an e-mail and I'll send you mine, which if they
remain too untampered with are pretty fool-proof.
Regards,
Joe Mac.
No run-around statements, only real solutions please.