#os2
12 messages in this thread
we want run 3d-studio as a background-task under os2 warp.
resolution could be vga mode.
regards franz 100712,2663
Download files os2txt.zip in lib 9 (a capture of a message thread about running
3ds under os/2) and 3dsos2.zip, which describes the settings to use for
foreground and background sessions of 3ds under os/2.
As the writer of the second file, I'll warn you that there is not a really good
way to run 3ds in the background and perform productive work in the foreground.
At least in os/2 version 2. os/2 warp may or may not be better.
LAM
thanks for yout tips (os2tips.txz from 1993?).
try your settings, but we have no chance to run 3d-studio in background – task
stop and run only in forground.
anything with our grafikcard(miro-s3-868) settings?
regards franz
The ability to run 3ds as a svga or vga session in the background depends on
whether the os/2 video driver supports it. Most drivers seem to support it,
some do not. With your card, I'm not sure, but it should. You are probably
using drivers written by S3, which always seem to support it. You do have the
"/BGEXEC" parameter specified on the video device driver line in config.sys,
don't you?
If all else fails, you can select the "null" driver from vibrant's driver list.
If you use this driver, all screen output is routed to "the big bit bucket",
and the screen is left in text mode. If 3ds has a problem starting up (like a
control file for that machine's ID already exists), you won't ever see the
error message, so I prefer not to go that way if possible.
Leave a reply on whether you are using the /bgexec parameter, and what vibrant
driver you are using for your background session.
LAM
< you are using the /bgexec parameter>
yes behind vsvga.sys
what means ncdebug=4000 in your config.sys
and which parameter are importent for the backgroundsession
< what vibrant driver you are using for your background session.>
1.) vibrant 3-8-95, s3 864/964
2.) main=vga, mat=vesa, render=null
it still not run
regards franz
The ncdebug statement could have come from anywhere <g>. I don't think that it
is important for the concern at hand.
It sounds like the os/2 video driver isn't supporting background execution if
the application is in graphics mode. Bummer. About all I can suggest is to
try selecting the "null" vibrant driver (it should be at the bottom of the list
of vibrant supported chipsets). You'll have to start up the background session
to go into slave mode automatically. Try this and see if you can submit a net
render job to it.
LAM
larry,
<try selecting the "null" vibrant driver>
it runs.
on question to your list of rendering times. it's right, that your background
tasks, are faster than in forground and sametime like dos tasks?
regards . franz
Generally speaking, if you are doing paging while running 3ds, running under
os/2 will be faster than running under dos. Os/2 will handle the paging, and
can do it faster than the PharLap dos extender in 3ds.
As long as I didn't have other tasks running at the same time, I generally
found that running under os/2 added at most about 10% to the rendering time
over dos.
Background sessions renders are a bit faster than foreground sessions due to
the use of the null driver – nothing is ever drawn to the screen.
Please remember the timings I gave in that file were for os2 ver 2.1. The Warp
version of os/2 includes settings for dos session priorities. By adjusting the
priority settings, you may be able to get a foreground and a background session
running smoothly (being able to render in both) without a big performance hit.
LAM
larry,
now our "null" session runs very stabil and as fast as under dos. thanks for
your tips.
our only problem is, how to exit a null seesion correct, so the task is set to
fail in the net queue and we can clean it.
regards . franz
3ds will still accept keyboard input, so you just need to do and escape and a
carriage return. This all isn't the cleanest way of doing things, but it works
<g>.
LAM
Hi! I've seen you're using 3D Studio under OS/2. I've recently installed Warp
in my system and can't run 3DS 3.0 within it… It seems to load and everything
but it suddenly displays trash, like if it crashed or something, and the
session is there but can't do nothing because I just see trash on my screen…
did you have the same problem someday? how can I fix it? I'm currently runing
it from MS-DOS (I use boot manager) but I hate to switch my OS everytime.
My computer is a Mitac Pentium/60 MHz with 8Megs in RAM, Avance Logic PCI video
card ALG2301 with 1MB DRAM.
Thanks in advance…
Eddie Castaneda
I haven't had any video problems running 3ds under os/2 like you are. It
definitely sounds like a video driver problem of some sort. Have you tried
just using the vga or vesa driver to verify that everything is ok that way? You
may also want to try decreasing your resolution to see if that helps.
I am presuming that you are running 3ds in a full screen window. If you are
trying to run in a dos window that is the cause of the problem.
In a full screen window, 3ds should be able to use and abuse the video system
without a problem. As far as I know, nothing in os/2 should interfere.
LAM