🚀 go-pugleaf

In article <382FC0A3...@pixi.com>,
  drma...@pixi.com wrote:
> GTS wrote:
> >
> > I belive I got it working. I un-installed my drivers, installed them
> > from the SBlive disk (the manufacturer of my PC left a bunch of
stuff
> > out when they did the install) and with the c:\command.com /c
> > c:\duke3d\duke3d.exe  stuff it works.
> > I don't understand why the Cammand.com stuff makes the differance,
but
> > it does. Mine works with LW2 though, and I ain't about to change
> > anything!
> > Thanks for the help!
> >
> hmmm..... Interesting, Command.com is a Dos system file that used to
> tell the computer what version of DOS and such you're using.  The rest
> of it tells the computer to run the file Duke3d.exe in the duke3D
> directory on drive C. It could be that the Win98 version of DOS
doesn't
> work with duke Nukem.  What is LW2.  I'm trying to figure out how to
> setup my autoexec.bat file to load the DOS soundblaster drivers.
>

 Actualy Command.com is the command interpreter for Dos. It's basicly
what drives the command line interface, and allows you to run batch
files, and set the enviroment (such as the variable "PATH"). I don't
really understand why you have to load a secondary copy of
"command.com to get Duke 3d to run (basicly that's what typing COMMAND
does. Typing COMMAND /C someprogram.exe does the same thing, but
exits  that second "copy" of command com when someprog.exe ends) to
get Duke to run, especialy scince it actualy eats memory, but if
it works, that's good. Personaly, I have a dual boot set up to
select between Window$ 95  and Dos 6.22/Window$ 3.11, and I run my
Dos games from 6.22. I have 5 years of experience working
constantly with Dos, and I know inside and out, and yet much
of workings Windoze 95/98 is still a mystery to me :}


Sent via Deja.com http://www.deja.com/
Before you buy.