FLIC play wiht R4 Rel 5
2 messages in this thread
3d studio Ver 4 Release 5
When I view/play a large flic (over 5 MB) from from 3d studio, the
system hangs at the same frame in each flic and a cold boot is then
required. This problem was not present in your previous release, (It
either hangs just after the flic starts to play or mid-way.)
As I did not encounter this problem with the previous Release of R4, I
loaded an older version from a tape backup. The problem was then
solved using this older Version 4 Release 3.
As I would like to use the latest version of the product, do you have
any suggestions ? This is the hardware I am using and the various
options I have tried:-
Pentium 90
Hard disk access speed 1.8MB per sec.
56 MB RAM
Video card Number 9, GXE64 Pro
a) I slowed the playback from 15 frames per sec to 1 frame per second
b) The VIBRANT driver option was changed to ADESK
c) I then suspected that it may have something to do with the newer VIBRANT
driver for the
Number 9 video card I was using. I copied across the older versions of
VIBRANT.RES and
VIB3DS.VLM but got an initialization error. Perhaps there is something I could
do here to to
establish if the new VIBRANT driver is really the problem ?
d) I should finally mention, that when I installed the latest release, I chose
the UPGRADE option.
Thank you for your assistance.
<<3d studio Ver 4 Release 5>>
Are you talking about the Vibrant drivers being at Release 5? If so, there is
an update to this driver, version 1.0.6. Download VIB3DS.ZIP for the latest
drivers.
<<b) The VIBRANT driver option was changed to ADESK>>
Do you mean for the Flic Playback? You should still be able to use Vibrant for
this choice.
Also, when you upgrade from one release to another, it is possible for memory
conflict to arise on the system. Included below are some instuctions for
diagnosing a memory conflict. Please see if the same problems happen in the
"stripped" environment.
-brian
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.