#3DS/IPAS Problems
9 messages in this thread
I am a 3DS R3 user and have had no problems with the software until adding IPAS
#6 & #7. First off, any time I try to render an animation with a SKIN object,
I get the error message "cannot create temporary file:
C:\3DS3\TEMP\$FLIW1$.TMP" while it is Encoding 256-color image. Stills render
fine. I also noticed today that the message has started showing up when I
render animations without SKIN objects that before rendered fine. Second
problem is with the sample file SKINDRGN.3DS. When I try to render either a
still or an animation of this file I get the error "can't create .LOC file"
while it is Transforming Objects… After receiving this error, I cannot open
anyother .3DS files and if I try to exit to the dos window, I get the message
"Error Calling Program". Please let me know what can be done to fix these
problems…
It sounds like you just ran out of hard disk space, and that it happened at
about the same time you started using skin.axp. The "cannot create temporary
file" while encoding is a classic giveaway, since you're probably in either
Medium or High palette mode while doing this. First, if you're using High
palette, drop down to Medium and see if it still happens. Then, if it does,
drop down to Low. How much free hard disk space have you got before entering
3DS? Are you using a swap file when rendering?
– G
First of all, thank you for your quick response. The mystery is not solved
though. I have 1.9 gigs free space on my drive before entering 3DS. In
addition to that, I have been running on the Low palette setting. What else
might it be?
hmmm…. I'm pretty sure this isn't related to IPAS routines, but if you want
me to be 100% positive, you'll have to simplify the file to just a reproducible
case and send it to me (with an explanatory text file) via binary email. If I
can't reproduce it, it'll point back to a possible hardware problem within your
configuration (most likely either a bios, hd controller or other
incompatibility with Phar Lap).
The next diagnostic step is definitely for you to find that reproducible case.
If you can't then you'll have to start looking at your hardware. The first
thing I'd do (in that case) is try to run the sequence on another computer and
see what happens then.
– G
I tested 3DS and the new IPAS modules on a different system. They seem to be
working fine. I am not using PHAR LAP on either system. The system I am
having trouble with is a Pentium 90 EISA/PCI (32 megs on motherboard, 2 gigs in
the drive). The system it works on, though a bit slow, is a 486/33 with 8 megs
and 20 megs left on the HD. Thus, I assume it is not the software that is the
problem. But why isn't it running on the Pentium? Hints? Clues? Ideas?
Unfortunately, that's what I suspected. Heck… I've never even heard of a
combination PCI/EISA machine. Interesting! My guess is that there's probably
a bios setting (caching, etc) that'll make the difference. Perhaps one of the
hardware experts here on the forum can offer some suggestions. (I'm basically
a hardware idiot.)
– G
Simplified and rewrote CONFIG.SYS and AUTOEXEC.BAT. IPAS and 3DS both seem to
be working fine now. Thank you for your help…
>> I am not using PHAR LAP on either system.
Well if you're not, you're not using 3DS! 3DS has the Phar Lap DOS Extender
built into it — so when you're runngin 3DS, you're in running the CPU in
protected mode.
There are some others online here that have solved their initial problems w/
P90's, but the first thing you need to do, until they jump in, is strip down
the CONFIG/AUTOEXEC to the minimum you can to function, try it, and, if it
works, start adding things back in, line by line, until you have a failure.
Good luck.
Dave
Think the answer has been found. Simplified and the rewrote sections of my
CONFIG.SYS and AUTOEXEC.BAT. IPAS and 3DS both seem to run fine now. Thank
you for your help…