#EXIT DOS PROBLEM
3 messages in this thread
It seems to me that the necessity of exiting DOS and restarting 3DS each time a
rendering is made that exceeds available RAM and pages to disk is a bug, even
if it is documented. Im maxed out on my motherboard at 32mb and cannot upgrade
as often as I would like. Any fix in sight? With a couple of complaints like
this I still find 3DS to be by far the best 3d program Ive worked with. Thanks,
ED
/EXIT
Ed the need to exit 3DS to recover your swap file switch is annoying to me too.
I would prefer it to recover on a frame by frame basis, swapping only when
necessary. But, as I understand this is a Pharlap dos extender "limitation"
not a 3DS bug. The same thing will occur in other software using pharlap. I
won't call this a bug but instead a design limitation which all things in life
have. 3DS users are just typically pushing things to the limits. Maybe when
Windows NT is the OS for 3DS we won't have this problem but then we'll most
likely encounter other problems and limitations.
Ed:
Unfortunately, this is not technically a 3DS problem, but a PharLap problem.
PharLap is the company which wrote the virtual memory program which allows 3DS
to use more memory than the amount of RAM that you have by swapping to disk.
If you have a network, another reason to exit to DOS and restart, by the way,
is for you to run a program to sync your computer clocks to the network master.
We have found that the clocks tend to drift a bit over time, and network
rendering is much happier with accurately synched clocks. We put this command
in the batch file which runs 3D Studio.
Greg Pyros