OS/2, eCS & ArcaOS - Technical > Games
Running MGL Doom on Warp 4
Dave Yeo:
Wish I could remember what the problem was with the second device driver fixpak :(
You should have a more recent kernel though it's probably not related to your Doom problem. It's at http://www.os2site.com/sw/upgrades/kernel/w420050811.zip note that they restrict access to OS/2 browsers so wget etc don't work.
Ian B Manners:
--- Quote ---they restrict access to OS/2 browsers so wget etc don't work.
--- End quote ---
or ask me via http://www.comkal.net/ for access and I'll send you a reply email :)
wsgibson:
I have upgraded my kernel to 14.104 as well as run cleanini, checkini, and xfix to cleanup things. I do not see any invalid entries anymore. Thanks for helping with the suggestions. I am still having the same issue though. It seems to me that the Doom exe is looking trying to access a GL double buffering call that is not being provided by my current video driver (SNAP 3.1.8 ). The SNAP 3D OpenGL tests are running very fast with double buffering and no flicker so it seems that my installed video driver should work. I even installed the IBM OpenGL Gold 1.1.1 thinking that perhaps it had the missing feature that is needed.
Any thoughts?
Thanks!
Scott
Dave Yeo:
I just tried mgldoom on my Warp 4 fp15 system with snap 3.1.8, build 505 and it seems to run fine, don't see any errors about double buffering.
It's possible that I have leftovers of SDD laying around but I believe I uninstalled it when upgrading to Snap, and since you state it ran under the eCS demo which wouldn't have any sdd laying around...
My snap settings in config.sys are
--- Code: ---SET VIDEO_DEVICES=VIO_SVGA
SET VIO_SVGA=DEVICE(BVHVGA,BVHSVGA)
DEVICE=E:\OS2\MDOS\VSVGA.SYS
SET GRADD_CHAINS=C1
DEVICE=E:\OS2\GRADD.SYS
DEVICE=E:\OS2\MDOS\VMANWIN.SYS
SET GREEXT=SDDGREXT
SET C1=SDDGRADD
rem SET C1=GENGRADD
DEVICE=E:\OS2\SDDHELP.SYS /Q
--- End code ---
other then that I don't know what the problem on your system is.
ivan:
Scott, if you are going to keep your Warp 4 install I think it would be a good idea to make a backup of the os2 directory and then reinstall fixpak 17 letting it overwrite newer files except the kernel files then re-apply snap 3.1.8 again letting it overwrite files.
I say this because it sounds as if you have parts of the system backleveled and this is causing your problems.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version