#OS2/3DS
5 messages in this thread
Doug,
I am running 3ds3 under OS/2.
When I try to render a high res image 6400×4800 I get the following error
messages: "Can't Allocate Image Buffer", "Init of Driver Failed". This
seems to happen only in OS/2. Do you have any ideas? I am configured for
a NULL render display through the "3ds vibcfg".
Also, I have problems doing an alt-esc to 3ds and Ani Pro. In 3ds I always
have to go to the materials editor to refresh my screen in 3ds. As for Ani
Pro there seems to be no way to get back in.
Finally, I am new to OS/2, if you have all the dos settings that should be
set for 3ds and Ani Pro, and if you could supply me with them, I would
greatly appreciate it. I read through the 3ds-os2.txt file that was the
os2 thread between nov93 and dec93. It was helpfull but a summary of the
settings would be more benifitial. I have a p5 w/ 64 meg of ram. I am
mostly concerned with having 1 3DS icon set up. After it is set up, I will
then worry about foreground/background & slave operations.
It was very interesting reading through the os2 thread.
Thanks,
Stephen
Stephen,
<< When I try to render a high res image 6400×4800 I get the following error
messages: "Can't Allocate Image Buffer", "Init of Driver Failed". This
seems to happen only in OS/2. Do you have any ideas? I am configured for
a NULL render display through the "3ds vibcfg". >>
Is this using the latest vib3ds.zip, found in 3D Studio section of the lib,
with the new NULL found at the end of the card list in 3ds vibcfg? If so…
you may wish to post this along with the make/model of your graphics card to
Chuck Walbourn[Vibrant] 71673,2500.
We are not running any OS/2 machines in product support.
jonas[adesk]
Jonas,
I downloaded it a long time ago. I will check the dates on the files.
Stephen
>> "Can't Allocate Image Buffer", "Init of Driver Failed". This seems to
happen only in OS/2. Do you have any ideas? <<
Either your Vibrant Driver is choking or you do not have enough memory
allocated to the DOS session in OS/2 that is running 3DS. Check your
DMPI_MEMORY_LIMIT setting (read on).
>> Also, I have problems doing an alt-esc to 3ds and Ani Pro. <<
Unless the resolution of your OS/2 Desktop matches your Vibrant Display
settings _exactly_ , you are likely to get screen collage when switching
between the Desktop and 3DS. There is currently no "clean" solution for this
since the Vibrant drivers have no way to communicate with OS/2. However, you
can set either your Materials Display or Main Display to match your Desktop.
Then, before switching to the Desktop, go to the module that has matching
settings so OS/2 does not get confused. Alternately, you can shell to DOS
inside 3DS before switching to the Desktop as this effectively places the 3DS
DOS session to text mode, which OS/2 understands.
>> As for Ani Pro there seems to be no way to get back in. <<
I will need a more detailed description of your settings and circumstances when
switching to/from AniPro. Are you trying to run AniPro directly from 3DS?
>> [ . . .] I am new to OS/2, [ . . . ] if you could supply me with [settings]
<<
—-
* Drag a Program object from the Templates folder onto your Desktop. A
settings notebook will pop-up for the settings.
* Use D:\3DS3\3DS.EXE or your current path/filename for 3DS.EXE.
* Use D:\3DS3 or your 3DS directory name for the working directory.
* Click the Session tab on the Notebook and click on the DOS Full Screen radio
button. (3DS usually cannot run in a window due to the Vibrant driver modes.)
{Continues in reply . . . }
{ . . . Continued from parent msg}
* Click the DOS settings button. Below is listed the relevant settings that
work for me — some minor tweaking may be necessary for your particular setup.
DOS_FILES 40 (or more)
DOS_HIGH ON
DOS_RMSIZE 640
DOS_UMB ON
DPMI_DOS_API ENABLED
DPMI_MEMORY_LIMIT 16 (or more, not > than available disk space)
EMS_MEMORY_LIMIT 0 (unless circumstances require it)
HW_ROM_TO_RAM ON
HW_TIMER OFF
IDLE_SECONDS 60 (this setting and the next will disable
IDLE_SENSITIVITY 100 idle detection)
INT_DURING_IO OFF
VIDEO_8514A_XGA_IO_TRAP OFF
VIDEO_RETRACE_EMULATION OFF
XMS_MEMORY_LIMIT 0 (unless circumstances require it)
Note: the DOS_BACKGROUND_EXECTUION setting can be ON if OS/2 finds your
Vibrant Main Display agreeable. This may require some experimentation. I have
not yet tried the "Null" choice from the new Vibrant drivers. I have set up a
special icon that uses plain-vanilla VGA via a special 3DS.SET file when I want
to start a long 3DS render session and shove it to the background.
* Click the Save buttion.
* Click the General tab on the notebook.
* Type a name in the Title box like "3D Studio".
Note: If you want to use the icon supplied with 3DS (3DS.ICO) you will need to
convert it to an OS/2 icon file. Or, I can upload a converted one at your
request.
* Close the Settings Notebook.
* Place the new object in the location of your desire on your Deskotop.
—–
— James E. Coulter — Mindscape Animation Productions —