Build & Windows 2000 problems

[Guest]

I just installed Build V1.4 on my computer at work which uses Windows2000 and it doesn't acknowledge any keypad functions, ie: ENTER to switch between 2D & 3D mode.
Has anyone else had this problem and if so is there any way to fix it?

[Joe Siegler]

Do you have all the Build files in your Duke game directory? Make sure they're there.

Also, make sure they're not "read only" either, that can cause problems.

------------------
Joe Siegler - Webmaster, 3D Realms
Join the TiVolution! (http://www.tivo.com)
---
Got a Duke Nukem Forever Question?
Go read the OFFICIAL FAQ before posting about it! (http://www.dukeworld.com/faq/dukeforever/index.html)
Click here for info on how to use this UBB (http://www.3drealms.com/ubb/faq.html)

[Guest]

None of the files are Read Only and it looks like all the files are loaded. When I hit Keypad ENTER in 2D mode it gives the message 'Highlighted line pointers checked'...same response as the regular ENTER. Also, the cursor keys aren't responding. I've selected the Keyboard & Mouse option in Build Setup so I don't think that's the problem either.
Has anyone else had problems with Windows2000 and Build? Maybe they're just not compatible?

[Phoenix]

?? Use the 'Enter' at the the numeral area or what ever it is called. The button to the very very right of a standard key board.

------------------
>>Hank<<

Time waits for no one ...

[TerminX]

No, BUILD will simply not function correctly in Windows 2000. All of your suggestions have no relevance - it just doesn't work.

You're lucky you can even get 2D mode in Windows 2000 at all. Your best bet will be to use a boot disk and boot to straight DOS, providing your drives are formatted FAT32 instead of NTFS.

-TX

------------------
Project X TC - http://www.dukeworld.com/projectx
Mapster - http://dukertcm.totalconversions.com/mapster

[Guest]

Bummer! Guess I'll have to go back to doing my homework at lunchtime.
Thanks for all your help and suggestions!

[j.h]

i run build and duke perfectly in windows 2000.

------------------
================
j.h

[TerminX]

If "perfectly" means no sound or a video mode above 320x200, then yes, you run them perfectly.

-TX

------------------
Project X TC - http://www.dukeworld.com/projectx
Mapster - http://dukertcm.totalconversions.com/mapster

[j.h]

well i run it in 640x480.
with windows 98 i had no sound with duke,but now ive never had a problem.

------------------
j.h

[TerminX]

You're confusing Windows 2000 with Windows ME.

-TX

------------------
Project X TC - http://www.dukeworld.com/projectx
Mapster - http://dukertcm.totalconversions.com/mapster

[j.h]

sorry,i thought they were the same thing.
im using windows ME

------------------
j.h

[Carger2000]

Looks like Ken stays busy with answering
questions, releasing patches for a long time..poor soul http://www.3drealms.com/ubb/images/icons/wink.gif
That he is still willing to help people
out and releasing sound problem patches.
Top bloke!

------------------
C2000, The Map Masters
=======================

[icculus]

This is a quote from an email exchange Ken Silverman and I had about BUILD's keyboard code:

---
* That outp(0x20,0x20); in keyhandler IS in a bad place. It turns out that the Win98 keyboard emulator works with it there, but the WinNT keyboard emulator doesn't! Go ahead and put it at the end of the interrupt handler - just beware of the early "return"!
---

There you have it.

I never fixed this in my BUILD port (since it's irrelevant unless you compile a DOS binary), but if anyone wants to make a patch and send it to me, I'll plug it into the codebase.

Note that the Windows and Linux ports of BUILD (http://www.icculus.org/BUILD/) don't have this problem, since they use abstractions instead of touching the hardware directly. I'm told it isn't completely stable yet on NT/2000, and there will probably be other troubles editing Duke maps, but feel free to give it a whirl.

--ryan. (icculus@lokigames.com)