Enchantermon on 3/10/2005 at 18:05
Quote Posted by descenterace
That'll be the DOS/4GW extender.
But I'm not using DOS/4GW.
Enchantermon
ToxicFrog on 3/10/2005 at 18:09
Quote Posted by Enchantermon
But I'm not using DOS/4GW.
SS1 has DOS4GW built into it. All explicitly using an external copy of it does is override the version built into SS1 with the version you provide.
Enchantermon on 3/10/2005 at 20:11
Quote Posted by ToxicFrog
SS1 has DOS4GW built into it. All explicitly using an external copy of it does is override the version built into SS1 with the version you provide.
Ah. Understood.
Enchantermon
Nameless_Voice on 5/10/2005 at 12:08
I'll try that second patch when I get home, doubt it'll work though.
Does anyone have a patched version of Dos4GW that doesn't try to access the serial ports? That Click Ignore-Alt Tab Three Times-Click Ignore-Alt Tab Three Times thing goes on my nerves.
Shadowcat on 6/10/2005 at 00:28
Coincidentally, I just happened upon this:
(
http://forum.enderzero.net/viewtopic.php?p=12119)
Quote:
I have just been made aware of a new DOS extender (new as in modern.) It's called DOS32. It takes the place of DOS4GW. So instead of say calling System Shock with "DOS4GW.EXE CDSHOCK.EXE" You just do "DOS32.EXE CDSHOCK.EXE"
Supposedly it's WAY faster, and works better with the DOSBox Dynamic CPU core. (I guess it helps less with the other CPU modes, but Dynamic is the best one anyway.) I don't know whether it will help our current non-DOSBox System Shock setups or not, but it's supposed to be more stable than the old ones, and faster. I'm going to try it tonight.
The link is: (
http://dos32a.sourceforge.net/)
You can just call it the way I mentioned above, or even just rename DOS32.EXE to DOS4GW.EXE and call it good.
It has a utility that comes with it, that will search a game for a built in extender (many old DOS games had these,) and replace it with DOS32.This thread is also referenced:
(
http://vogons.zetafleet.com/viewtopic.php?t=6260)
And as the source code to DOS/32 is available, if it does cause problems with the serial port (and doesn't already provide an option to ignore it), someone could presumably compile a version that left that part out.
Sounds awesome. I think I'll go and make mention of this in GenGaming...
descenterace on 6/10/2005 at 08:26
DOS/32 is great. It's my primary source of information regarding the workings of extenders and the DOS Protected Mode Interface.
The tool for removing an existing extender is particularly useful, since IDA won't disassemble an app that contains an extender.
dvwjr on 8/10/2005 at 19:18
Quote Posted by IceNine
Runs like a top here. Chops below 15FPS in 1024 though, but it's all software so I kind of expected that.
I was wondering how you were able to determine the "15 FPS" for System Shock (HiRes) at 1024x768. Is it sort of an estimate or were you able to determine frame-rate for this DOS protected mode game in another fashion?
Thanks for any info,
dvwjr
ToxicFrog on 13/10/2005 at 16:43
Quote Posted by Infinitron
Greetings. I am a lurker. I read this forum mainly because of Zylonbane's posts. That guy is fecking hilarious.
But that's not important right now. Those of you who are having trouble with this patch and certain Nvidia video cards may find the utilities mentioned here useful :
(
http://www.jonsguides.com/dosgames/settler2.html)
Oh, excellent!
TNT, Enchantermon, Gudadantza - could you test this out and see if it works?
miklogik on 13/10/2005 at 17:50
Quote Posted by Infinitron
But that's not important right now. Those of you who are having trouble with this patch and certain Nvidia video cards may find the utilities mentioned here useful :
(
http://www.jonsguides.com/dosgames/settler2.html)
Good news! Strangely, I just installed SS1 for the first time last night, and was sad to see the HR patch did not work with my (probably) GeForce4 Ti4200. This new suggestion is good timing! Will try this tonight after work. A further link - this one regarding NoLFB - also verifies the GeForce issues,(
http://advsys.net/ken/build.htm) http://advsys.net/ken/build.htm:
Quote:
Some newer video chipsets (most notably those based on the GeForce4 series) do not support VESA with resolutions above 640x480 under Windows NT/2K/XP. I believe this is due to a conflict between the VESA driver and the operating system and not NOLFB. If your monitor goes into a standby/power-off mode, and you are using a resolution above 640x480, please remember to also try 640x480 mode!
Keep up the good work!
