VOGONS


D3d

Topic actions

First post, by Luke

User metadata
Rank Newbie
Rank
Newbie

Ive been looking at this forum for a couple of hours now reading all the relevant problems, and perhaps against my better judgement, have decided to post 😀.

My system specs are below, and extra details can be found in my profile. I have been trying to get Duke Nukem 3D to work on my system now for a couple of days, with no success, I have tried using VDMS, the update and the launcher in combination, and have also tried lowering all my settings to the lowest, but still, when I try to play the sound, it freezes in both the setup test and the game itself.

As a final act of desperation, I also tried another sound emulator (SoundFX 2000) which produced the same freezing effect.

I know that the common solution would be to either dual boot, or just give up, but isnt there anything else I could try?

Thanks in advance,

Luke

System specs-

CPU and CPU Speed Intel Pentium III 733 (733MHz)
Motherboard and Chipset Aopen G980, Unknown VIA chipset
Video Card and Video RAM Matrox Graphics Millenium G200 AGP
Sound Card Creative Labs Sound Blaster Live Value
System RAM Amount and Type 256MB PC-100
Operating System Windows XP Professional

Reply 1 of 1, by Nicht Sehr Gut

User metadata
Rank l33t
Rank
l33t

Originally posted by Luke My system specs are below, and extra details can be found in my profile.

Thank you. That prevents the usual "20 Questions" we have to ask.

I have tried using VDMS, the update and the launcher in combination, and have also tried lowering all my settings to the lowest, but still, when I try to play the sound, it freezes in both the setup test and the game itself.


BUILD games and a few others have a bug when used with latest updated VDMSound+GUI.

Try using the right-click "Run with VDMS" shortcut that does not have the musical note on the game's executable (or batch file) and also for the game's SETUP program.

Note that the "Run with VDMS" shortcut that does not have the musical note activates the default "command line" version of VDMSound, which means that it will ignore these settings placed in the VDMSound shortcut and use the default VDMSound settings instead.

These will be for a SoundBlaster 16 with an IRQ of 7, Address 220, an 8-bit DMA of 1, then a 16-Bit DMA of 5 and uses the General MIDI configuration.

It is possible to use a "Brute Force" workaround that allows you to still use the GUI with BUILD games, although it will usually incur a performance hit.

On your game's .VLP shortcut (created by the GUI the first time it's run), get it's properties, click "Advanced", go to the "Troubleshooting" tab, "check" the "Custom Configuration" box and paste the following into the open text area:
[VDMServicesProvider.config]
fixPOPF = 1


Also, be aware that VESA does not work the same way under NT like it works in Win9x. Some graphic cards are more compatible than others. Start with a basic VGA mode of 320x200. If it works properly, go back to your setup and try the VESA screenmodes.

If they don't work, create a batch file to start the game with easy to remember name like GO.BAT and use NOLFB.COM or similar tool to force use of an alternate video mode.
---------------------------------------------------------------
C:\PATHWAY\NOLFB.COM
DUKE3D.EXE

---------------------------------------------------------------
Edit to match your game name and pathway.

I know that the common solution would be to either dual boot, or just give up,...

I preach "Dual-Boot" on a regular basis, it works very well as a fail-safe backup in case a title just won't work properly in NT. There are still a number of titles that fit this description.

Due to various in improvements in tools and advice, I can run Duke3D in XP at 800x600 with reasonably good audio, but I still prefer running it 1024x768 with audio cranked to maximum capacity under Win98.