#fli rendering problem
5 messages in this thread
Every time I try to render a fli (320×200) in 3ds4 I get this message just
after rendering the first frame to the hard drive:
cannot create temp file c:\3ds4\temp\$fliw/$.tmp
What is going on. I have been rendering fli/flc's without any problem for
months then all of a sudden this message rears its head.
I would appreciate any help on this one.
Brad
<<cannot create temp file c:\3ds4\temp\$fliw/$.tmp>>
Usually, this means you have run out of disk space. How much do you have
available? Try freeing up a large chuck and see if the error goes away.
-Brian
Brian,
I have over 1/2 gig on c:\ drive (swap drive) and 300 mb free on d:\ drive. I
can render the images as gif's then use vpost to make a flic but I still can't
render a fli from scratch. I'm lost on this one.
Brad
There might be something else conflicting with Phar Lap (memory Manager) when
it tries to write the swap file. Use the information below to see if there is
some kind of conflict on the system.
-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.
Thank you Brian for the help. It was a memory problem caused a conflict with
the network and cd rom. A config.sys and a autoexec.bat that has two
selections- one for 3dstudio/cd-rom and the other selection for the network did
the trick.
Again I appreciate your help in this matter.
Brad