#OS/2 Settings
11 messages in this thread
I've installed Warp on a 486DX2 66Mhz; 16MB RAM; Two 325 Hard Drives and a
Cirrus Logic 5428 2Mb. I've download the Os2 settings and config.sys files, and
worked the 3D and Warp definitions. On my background session I've choose the
VGA driver for the main window and the NULL driver for the render window. But,
despite all this modifications on Definitions and in config.sys I still can't
get 3D Studio to render on the background. Every time I change to OS, rendering
stops, meaning that 3D Studio only render in foreground.
Any suggestions?
Thanks in advance Alvaro Nobrega
Try modifying this line in your Config.sys to look like below:
DEVICE=C:\OS2\MDOS\VSVGA.SYS /BGEXEC
In other words, add the /BGEXEC parameter.
— James — Choreo Motion —
James,
I had already that parameter on my config.sys. I've also change the Swap path
and size to 16MB. Rem the IFS=(…) line, and did some other changes. I haven't
yet change the DISCACHE parameter, because I'm waiting to see the correct cache
size for my system. Any more suggestions? Thanks in advance,
Alvaro Nobrega
Alvaro,
Make sure your 3DS display settings are less than or equal to your Desktop
rez/depth, otherwise it probably won't run in the background. Unfortunately, I
have heard of some systems that won't run 3DS in the background no matter
_what_ the settings are. Sometimes the combination of OS, drivers, and
hardware just don't add up.
Before you give up hope, check everything over once more. Sometimes a subtle
mistake can be hidden among the many settings.
— James — Choreo Motion —
James,
>>Unfortunately, I have heard of some systems that won't run 3DS in the
background no matter _what_ the settings are. Sometimes the combination of OS,
drivers, and hardware just don't add up.<<
I've checked and everything. No mistakes and the settings are correct. I guess
I have one of those systems you mentioned. 🙁 I bought Warp because of 3DS.
I'll keep Warp because I like it.
Thanks,
Alvaro
Whether a program running in graphics mode can execute in the background for
some reason depends on how well the video driver was written. You may want to
look around for an updated os/2 video driver. (What card and chipset are you
using?)
Alternatively, you can run the background session using the vibrant null
driver. That way the background session never goes into graphics mode, which
means it oughta run in the background!
By the way, what are your IDLE_Sensitivity settings? If your foreground
session is set too high, the background session never gets any CPU cycles. I'm
running my background session at 100, and my foreground session at about 30.
Try running pulse and just the foreground session. Use F10 to bounce out of
3ds and look to see what cpu utilization you get when 3ds is just sitting there
waiting for you to do something. If it is pegged at 100%, reduce
idle_sensitivity until it drops off.
LAM
Larry,
>>You may want to look around for an updated os/2 video driver. (What card and
chipset are you using?)<<
I'm using a Cirrus 5428 VLB 2MB on a 486DX2 66MHz with 16MB. Next week I'll be
upgrading for a 486DX4 100MB and buy another 16MB RAM.
I've just find out that there are new drivers available in my local IBM BBS. I
could not download this drivers yet because my download limit is too small.
I've let a message and I hope that on Monday I will have the required access to
download this drivers. This might be the problem after all. Someone told me
that there where some problems with Cirrus Drives, but didn't specify which.
As for the idle_sensitivity settings: Background ->100 foreground ->10
I've checked the foreground as well as the background sessions with the Pulse
program and, as expect, the sessions showed no sign of activity while waiting
in the background.
Thanks,
Alvaro
Does your "background" copy of 3DS run in a window? If so, you've got it
properly configured for background execution (about the only thing that can
stop you from there is "DOS_BACKGROUND_EXECUTION" set to OFF). My 3DS system
blew up a couple days ago, so I can't check these things, but I set mine for
16-color VIBRANT on the MAIN display to get it to work in the background.
— Doug Azzarito
Doug,
I've tried both 16 VGA, and VIBRANT Drivers. Unfortunately I can't get the
"background" session to run in a window. I just get a warning message saying
that I can't run this video mode in a Window.
I expected that with 16MB RAM and a 5428 CIRRUS VLB MB would be enough to run
3DS in background. It looks like it won't run after all. I'll be upgrading my
computer next week to a 486 DX2 100Mhz with 32MB. This ought to be good enough
for every program, but I suspect 3DS will not run in background in my system
whatever I do. I'll give up background rendering, but I'll keep OS/2. Thanks,
Alvaro
> I expected that with 16MB RAM and a 5428 CIRRUS VLB MB would be
> enough to run 3DS in background.
It's all up to the video mode. What are you running as an OS/2 resolution? That
may be why you can't run in the background. I can ask some of the video gurus
around here for some suggestions, but first tell me how you have OS/2's desktop
configured (go to the System Setup folder and open the SYSTEM object to check
your resolution setting).
— Doug Azzarito
Doug,
I'm running OS/2 with a resolution of 640×480 256 colours. As for 3DS, I have
the vibrant 640X480, 256 driver for the foreground session and 16 colours for
the background session.
I understand, that there are new cirrus drivers on OS2SUPORT FORUM, but I can't
download it from CompuServe because Lisbon access is still 2400 baud (it would
take hours). I've just checked with and local IBM BBS as those new drivers.
Unfortunately as I've visited this BBS for the first time, I don't have enough
download limit for downloading this drivers. I left a message, and I expect to
be granted more access next week.
Thanks,
Alvaro