🚀 go-pugleaf

thanks for the advice,

i'll have to try that...



"Myname" <t%e...@ameritech.net> wrote in message
news:Xns933B45AC3F3EAmynameameritechnet@206.141.193.32...
> Hi all. This is my first time posting in this ng.
>
> A couple months ago I bought a new computer with Windows XP and found
> that Duke Nukem 3D 1.3 wouldn't run with the settings I'd used on my old
> computer under Windows 98 (I only use Duke in single-player mode).
>

Thanks for the info, I tried to do the same thing, but duke crashes with the
error message seen at the bottom of this:

Using: 'DUKE3D.GRP'.
KB_Startup: Keyboard Started
Compiling: 'GAME.CON'.
Including: 'DEFS.CON'.
Including: 'USER.CON'.
Found 0 warning(s), 0 error(s).
Code Size:48516 bytes(1425 labels).
Using Setup file: 'DUKE3D.CFG'
CONTROL_Startup: Mouse Present
Loading art header.
Checking music inits.
Checking sound inits.
RTS Manager Started
    Adding DUKE.RTS.
Using .RTS file:DUKE.RTS
Loading palette/lookups.
DPMI_mapPhysicalToLinear() failed!

"Myname" <t%e%s%t@ameritech.net> wrote in message
news:Xns933B45AC3F3EAmynameameritechnet@206.141.193.32...
> Hi all. This is my first time posting in this ng.
>
> A couple months ago I bought a new computer with Windows XP and found
> that Duke Nukem 3D 1.3 wouldn't run with the settings I'd used on my old
> computer under Windows 98 (I only use Duke in single-player mode).
>
> After checking I found it would only run without VESA and with a crappy
> 320x200 screen resolution. Furthermore there was no music, and the sound
> effects were distorted. I managed to get the music back by selecting
> General Midi, 0x330, for the music card in the Duke setup program.
>
> I checked around the web and lurked in this group awhile, then read the
> FAQ and found that NOLFB would fix the VESA problem. It did. (I can't
> get the highest resolution to work, but 640x480 is OK.)
>
> Unfortunately the solution (VDMS launchpad) for fixing the sound problem
> didn't work for me. There's no doubt it improved the sound, but it also
> made the program very sluggish, with poor keyboard response, so it was
> impossible to really play.
>
> So I ignored the VDMS launchpad. If anybody's wondering how to use NOLFB
> and VDMS without the launchpad, here's what I did:
>
> First I copied the file C:\WINNT\System32\autoexec.nt to the Duke3d
> directory and edited that file to change the SET BLASTER command to:
>      SET BLASTER=A220 I7 D1 P330 T3
> After that command I added:
>      c:\duke3d\nolfb.com
>      dosdrv
>
> After saving the autoexec.nt file, I right-clicked on duke3d.exe and
> clicked on Properties. On the Program tab I clicked on Advanced. In the
> Autoexec filename box I entered the path to the new autoexec.nt file.
> (It doesn't seem to matter whether any changes are made on the
> compatibility tab.)
>
> Of course you have to be sure to run the Duke3d setup to (1) use Sound
> Blaster, IRQ7 for the sound FX card, (2) also set the music card to
> Sound Blaster and (3) set the screen to VESA.
>
> That's it. It now runs as well as it did under Windows 98. Thanks to the
> members of this group, especially The Pacifist, for help in
> understanding the problems.
>
> Myname

"Zero 9" <zero9@everyzero.com> wrote in 
news:vg4k962puvpd3b@corp.supernews.com:

> DPMI_mapPhysicalToLinear() 

The error you describe is supposed to be fixed by NOLFB. You can get it 
here: http://www.advsys.net/ken/build.htm 

Sorry, I should have made it clear that I had NOLFB and VDMS installed. And 
make sure the line you add to autoexec.nt points to the directory that has 
nolfb.com. In my case it was c:\duke3d.