1. GET PLUTONIUM PACK (optional)
after downloading and installing it, you'll need the CRACK
(http://www.megagames.com/cgi/download/download.cgi?action=search&category=cracks&search=DUKE3D14.ZIP)
to
remove CD protection from Duke Nukem Atomic
2. SOUND
you have to install VDMSound ( at http://ntvdm.cjb.net), which
emulates old DOS sound cards, then download
CLI2NOP.ZIP (www.pacifist.co.uk/duke/cli2nop.zip), decompress it into
Duke Nukem directory and type "CLI2NOP
-2 duke3d.exe dukent.exe", which eliminates some old interrupts that
slow down the sound. Eventually, you'll
also need dnsndfx.exe (ftp://ftp.3drealms.com/patches/dnsndfx.exe) if
you have problems with your PCI audio
card (the patch works only on v1.3d or better)
3. VIDEO (VESA)
you need duke3d-nolfb.zip to enable old vesa modes
(http://www.advsys.net/ken/nolfb.zip)
4. NETWORK GAMING
"icommit.exe" seems not to work with Windows XP. Any solution?
5. HOW TO PROCEED
go to command prompt, type "DOSDRV" (it will load VDMSound driver),
run setup and configure the audio card
(SB16, a220h irq7 DMA1), then exit.
Create with a text editor a batch file named "DUKE.BAT" containing
these lines:
@echo off
nolfb
dosdrv
dukent
Then type "DUKE": the game will run with sound and a great 800x600
graphic under Windows 2000/XP!
You can find original game patches at
http://www.3drealms.com/downloads.html
Mark, with all due respect, you shouldn't describe this as a cure for
2000/XP problems. More like a list of suggestions. As it stands, they
can cause as much trouble as they cure.
> 2. SOUND
> you have to install VDMSound ( at http://ntvdm.cjb.net), which
> emulates old DOS sound cards, then download
>
> CLI2NOP.ZIP (www.pacifist.co.uk/duke/cli2nop.zip), decompress it into
> Duke Nukem directory and type "CLI2NOP
This is not needed and not recommended for XP owners as the most
recent VDMSound (with Update 1) contains the proper "fixPOPf" support
to run without using CLI2Nop.
Also, people should know that this is a hack that will reduce the
stability of the game itself (make it more prone to crash). Results
vary from frequent crashes (just a few minutes) to rarely, with the
majority somewhere between the two. In any case, if you're playing a
modified "CLI2Nop" Duke3D and it suddenly drops to the desktop (or
some other crash variant), this is why.
If you're trying to run it using 2000, however you have no other
choice. In any case, I recommend you try Snover's modified version of
Cli2Nop instead at:
http://vogons.zetafleet.com/showthread.php?s=d860c7ef134c151ea60a19110f52d0ec&threadid=31
It seems to result in more stable executables.
(That's the VOGONS message board at http://vogons.zetafleet.com,
Magrathea area > Deep Thought forum > CLI2NOP FAQ post by Stiletto.)
> also need dnsndfx.exe (ftp://ftp.3drealms.com/patches/dnsndfx.exe) if
> you have problems with your PCI audio
Actually, this shouldn't needed as there is no direct-to-hardware
access in 2000 or XP. The sound card that the program "sees" is a
virtual one, and Vlad's program passes the data along to your real one
through the OS.
> 3. VIDEO (VESA)
> you need duke3d-nolfb.zip to enable old vesa modes
> (http://www.advsys.net/ken/nolfb.zip)
Good advice for some, but not all. This is apparently true for most
GeForce owners (GeForce 4 owners may be limited to 640x480 VESA
resolution), but for some ATI owners it may actually prevent VESA
screens from displaying properly
> 5. HOW TO PROCEED
Most people will prefer to use Vlad's LaunchPad with "Update 1" to
simplify/speed up the process. There is, however, a bug when you use
this combo with some games (especially BUILD games like Duke3D. I
detail this, plus give a work-around in the "Problem Children" thread
at the VOGONS messageboard:
http://vogons.zetafleet.com/showthread.php?s=d860c7ef134c151ea60a19110f52d0ec&threadid=726
> Then type "DUKE": the game will run with sound and a great 800x600
> graphic under Windows 2000/XP!
Hopefully so. Performance under Win9x is still better, but at least it
can run with reasonable performance on an NT OS.
No!
Bad!
Don't do this!
This is WRONG. (At least for XP, less-so for W2K)
Go here:
http://vogons.zetafleet.com/showthread.php?threadid=726
More concisely (for Windows XP):
* Get VDMSound [http://ntvdm.cjb.net]
* Get update1 and VDMSLaunchpad 1.0.0.7
[http://vdmsound.sourceforge.net/files/]
* Install VDMSound. Overwrite with files from update1. Unzip the
launchpad to the same directory and run INSTALL.BAT.
* Get NOLFB.COM [http://www.advsys.net/ken/build.htm] and unzip it
to your Duke directory
* Right-click on the DUKE3D executable and choose the "Run with
VDMS" option that has a musical note icon next to it. Go to the
"Advanced" options. In the AUTOEXEC.NT box, insert PATH\TO\NOLFB.COM,
where PATH\TO\ is obviously the path to where NOLFB.COM is -- your
Duke directory. Go to the "Troubleshooting" tab and check "Custom
Configuration". Insert this into that box:
[VDMServicesProvider.config]
fixPOPF = 1
Click OK and save this configuration. Now, whenever you want to play
Duke Nukem 3D, double-click the DUKE3D.VLP file.
For Windows 2000, use the CLI2NOP found at
http://vogons.zetafleet.com, NOT the one linked to by this guy. It
causes fewer crashes and works generally better. Plus, I made it. :D
- CS
VOGONS - Very Old Games On New Systems
http://vogons.zetafleet.com