3DS Allocator Error
7 messages in this thread
Nik,
We are using 3DS R4.1C on a 486/66 with 32MB RAM, 1+GB HD, Diamond Speedstar
24X (1 MB VRAM), DOS 6.22, Windows for Workgroups 3.11, Targa 64 card, and
Animax animation controller. 3DS is not run under Windows, but MS Himem.sys
and Smartdrive are active. The system also has LiquidSpeed runing the Vibrant
drivers for the Speedstar card. While our MS mouse is undergoing surgry, a
Genius mouse with it's driver is being used. This system has been running 3DS
R3 properly for many months.
The problem occurs ocasionally during a SAVE File operation in the 3D Editor.
The message
Allocator Error – Invalid handle: XXXAAA
comes up as text with a black background, as if the machine was in 132 column
DOS text mode. It generally crashes the whole machine. We recorderd two
instances, with XXXAAA = 360FFC, and 380FEC. It has been noticed that the
longer between save operations (30 min or more), the more likely the occurance
of the error is. We now save more often, but still find problems.
Thanks for your time,
Rich Schwartz
Rick, I'm out of the office this week, and don't have a reference for what
causes your error. You might repost your question in the 3DS section, rather
than the IPAS section, addressed to ALL (or perhaps, Brian Rudolph).
The usual recommendation we have is to note if it can be reproduced at will –
usually it's a bug of some sort. Most likely it's a conflict with memory
addresses, so that booting plain (or removing some of the hardware, like the
Targa) is necessary to get to a starting point where the error goes away. It's
tough, I know, with failures taking so long to occur. Add components/drivers
back until the error creeps in.
Make sure you have the latest drivers for all your components.
Hopefully, this will help, unless the Allocator error is caused by something
else. I believe that we have something about this in Product Support though.
Nik,
Thanks for the responce, I'll run the system "clean" and see what
happens. I was hoping for a quick fix such as "Oh yeah, that happens if…".
Thanks for your time,
Rich
Any luck withyour Allocator error?
The system boots off of a SCSI drive, and we checked all of the termination
settings and cables to see if that affects it. No conlusive answers yet. We
have not used 3DS much this week, we plan to start a comprehensive testing of
the system on Monday by turning off all the drivers.
Thanks for your interest, we'll keep you posted.
Rich Schwartz
Rich,
I caught Niks answer to you, and have basically the same respone. Can you
recreate it in a stripped environment, consistently? By stripped environment we
mean that your CONFIG.SYS has FILES and BUFFERS statements only, and
AUTOEXEC.BAT has your mouse driver only. Nothing else is loaded. In that
configuration, does the error still happen? If yes, then we know to look at
your hardware, if no, then we know to look at your system configuration.
-Brian
Brian,
Thanks for the responce, I'll run the system "clean" and see what
happens. I was hoping for a quick fix such as "Oh yeah, that happens if…".
Thanks for your time,
Rich