#3ds4
6 messages in this thread
RECENTLY I RAN INTO AN ALLOCATOR PROBLEM WITH 3DS4
I HAVE A P90 WITH 32 MEGS RAM AND A STEALTH 64 VIDEO CARD
I HAVE TRIED EVERY CONFIGURATION SO FAR EVEN WITH CLEAN
AUTOEXEC AND CONFIG.SYS FILES.
THE PROBLEM CAN BE RECREATED BY LOFTING AND OBJECT.
USE THE BUGLE LOFT IT THEN GOTO THE 3D EDITOR AND
MERGE AD3DLOGO FOR A BASIC LIGHT SETUP. THEN GO BACK
TO THE LOFTER AND LOFT IT AGIN THIS TIME WITH THE SAME NAME
YOU LAST USED. THE GO BACK TO THE EDITOR AND MERGE THE SCENE
THE SCREEN SHOULD SCROLL STRAIGHT UP. PLEASE HELP
Hi Chris,
<< clean boot.. >>
Do you mean that you can recreate your problem whne following the following? ..
Title: Clean system boot; diagnostics for memory conflict…
Description:
To confirm that the problem is caused by a memory conflict, re-start the
computer with simplified settings (a 'stripped system') and see if the problem
goes away.
For DOS-only computers, a stripped system means that the computer is rebooted
without terminate and stay resident (TSR) programs nor device drivers that are
not absolutely necessary for the operation of the operating system and
computer. The Autodesk program should also be configured for VGA display if
possible, to rule out display driver conflicts.
To reboot into a stripped system for 3D Studio and Animator Pro, change the
system files as follows:
CONFIG.SYS should contain only:
FILES=40
BUFFERS=20
AUTOEXEC.BAT should contain only:
PATH=<your path>
PROMPT=<your prompt>
You may want to use the DOS SYS command to create a bootable floppy for this
trouble-shooting exercise and place these simplified system files on the
diskette. Or, you may edit the existing CONFIG.SYS and AUTOEXEC.BAT files
currently on the hard disk (make back-up copies first). Make sure you have a
bootable DOS floppy on hand, just in case the computer has trouble rebooting.
Note: Quarterdeck QEMM users may find it helpful to review the QEMM
trouble-shooting documentation and use the Analyze utility to track down memory
conflicts.
Trouble-shooting:
If the program now operates correctly, the next step is to determine which
program or driver in your system files is causing the conflict. Edit the
CONFIG.SYS and AUTOEXEC.BAT files, adding one device driver or TSR command at
a time, rebooting, and starting 3D Studio/AAPRO until the error reappears.
When the error happens, the last item you added to the configuration is
probably the trouble maker. Once we know which drivers are conflicting, we can
determine the proper course of action.
If you are using special display adapters (for example, a Targa frame buffer),
you should check the documentation that came with the display driver to see if
special memory settings or EMS exclusions are needed.
I've done all of that
I've tried every system setting I used to repair computers so I know the drill.
I am convinced it is 3d studio not vibrant graphics or anything else
I used the vesa settings to read the bug report as with true color you can't do
this
Are you able to recreate the problem