Replicants 0 Posted July 22, 2000 Is it possible to set BUFFERS= in Windows 2000? Many DOS games check for it and refuse to install if its not 20 or more. Share this post Link to post
DosFreak 2 Posted July 22, 2000 C:\Winnt\system32\config.nt C:\winnt\system32\autoexec.nt Share this post Link to post
Replicants 0 Posted July 23, 2000 It will accept FILES= but BUFFERS= get ignored! Share this post Link to post
BladeRunner 0 Posted July 23, 2000 I think you have reached a time in computing you wont forget in a hurry From this day forward: Your gonna have to dump those old DOS games. If the game requires a 'Buffers=' line then it really isn't designed for Win98 let alone Win2000. Take a look at the newer releases, are there any games similar? ------------------ PIII 650 Coppermine, ABit BE6-II, 384MB PC100 RAM (Samsung), Matrox G400MAX, SB Live! Value, Intel 10/100 NIC, Adaptec 2940UW, IBM 7200 ATA66 22GB HD, IBM 7200 ATA66 20GB HD, Pioneer 32x/6x SCSI DVD, Yamaha 4416 SCSI CD-RW, Iomega Zip 100 SCSI Internal, Iiyama Vision Master Pro 410. Windows 2000 Only Share this post Link to post
Replicants 0 Posted July 23, 2000 If only there was a patch to let DOS programs believe that there were buffers available... Share this post Link to post
DeadCats 0 Posted July 24, 2000 If all the program is doing is checking config.sys for a BUFFERS=n statement, then why not create one? ------------------ "This year will go down in history. For the first time, a civilized nation has full gun registration. Our streets will be safer, our police more efficient, and the world will follow our lead into the future!" -Adolph Hitler, 1935 Share this post Link to post
Phantom_578 0 Posted August 3, 2000 Have had same problem under NT4 - still looking for a way around it - anybody out there have any ideas? Share this post Link to post
elomire678 0 Posted August 9, 2000 What DOS games are you guys trying to install? I've never run into a DOS game asking for the Buffers statement. If all else fails, you could dual boot. I just wish NT had the same DOS options as OS/2, ie. run DOS from drive a:. That would solve the problem. Share this post Link to post