Skip to main content

The Need for Speed with DOSBox

I recently stumbled upon my beloved old copy of the absolutely fantastic original "The Need for Speed". This fabulous game came out in 1994 and blew me away. My sister, her boyfriend (now husband) and I spend a crazy number of hours playing this game. It rocked!

How to get it to play now though...? Well, I've used the wonderful DOSBox before for playing Doom 2 and Commander Keen and the like. This software runs in Windows (XP for example) and emulates a DOS environment with an old SoundBlaster 16 soundcard. Would it work with TNFS (The Need for Speed)?

After a lot of trial and error I finally got it working after getting a tip from a forum on a site called "alldeaf" (www.alldeaf.com). I hadn't mounted the CDROM drive properly. Here's what you need to do:
  • Create a folder/directory on root of your C: drive called "tnfs" (i.e. c:\tnfs)
  • Run DOSBox
  • Type "mount c c:\tnfs"
  • Type "mount d d:\ -t cdrom"
  • Type d:
  • Type "install"
  • Follow the on-screen instructions
Hopefully this should do the trick for you. What a trip down amnesia lane! It really brought me back! It's still a brilliant game even if the graphics are a bit grainy.

Comments

Burby said…
Hello Steve,

funny that I did the same just now! My friends and me spend hours and hours with racing, telling each other the new minimum time.

Did you get the videosequences running? If so, I would be very interested for a "howto". For me its not visible, just jammed pixel with sound.
Thank you!
Martin
MIke said…
Thanks for that, i still have a bit to learn about using dosbox, now there's a little bit less i need to learn.
Cheers.
Mike
Unknown said…
When I try to do this it says the following: "getvesainfo - IVALID VESA INFO. VESA driver is installed?" Any ideas?

Popular posts from this blog

Where are SCANPST.EXE and/or SCANOST.EXE?

I sometimes have to deal with customer computers whose Outlook PST or OST files have become corrupted.  Very often the fix is to run SCANPST.EXE on the offending PST/OST file.   However, every time I go to do this I forget where the two executable files are.  Here is where they are on a Vista machine running Office 2007: C:\Program Files\Microsoft Office\Office12 I hope this helps.

Resolve WSUS Server issue that gives "Cannot save configuration because the server is still processing"

This is a pretty infuriating error and can sometimes crop up as a result of running a "wsusutil reset" command. First of all, give the server some time, and then a bit more...  but you've probably already done this. These steps may help to resolve the situation: - Install Microsoft SQL Management Studio (free download) - Run SQL Management Studio and start to connect to the WSUS database - Enter this in the "Server Name" box:  \\.\pipe\MICROSOFT##WID\tsql\query - Expand the "Databases" tree - Right-click on "SUSDB" and choose "New Query" - Paste this query in:     UPDATE tbSingletonData     SET ResetStateMachineNeeded = 0 - You should see a message like "1 row affected", which is good - Quit SQL Management Studio - Open "Services" and restart the "WSUS Service" - Now, open WSUS

Logon Scripts in Group Policy not running

Problem  Was having difficulty with a logon script I had created and was deploying to users via Group Policy. The script was to customise printer settings for certain users. But it just wasn't running when the users would logon to their PCs. The GPO was applying properly, and I could run the script manually without issue. Cause It turns out that it was happening because, by default, logon scripts don't run for 5 mins after logon occurs on a Windows client PC. Solution This can be adjusted by setting the "Configure Logon Script Delay policy" to "Enabled" and then configuring a better delay. Note: if this policy is set to disabled or not configured, the default delay of 5 mins will apply. I initially set this delay to "0" but found that wasn't successful.  Perhaps the script needed a small delay. So I set it to "1" (1 minute) and it worked nicely. I must also note that during the troubleshooting process, I read many recommendations to e...