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.

Unable to Extend Volume because the Windows Recovery Partition is in the way

I had to increase the space allocated to a customer's WSUS server VM that had run out of capacity and was keeling over. So I powered off the VM, added the extra capacity to the virtual hard disk, powered it back on, and went into Disk Management to extend the C: drive partition.  However, I discovered that because the Windows Recovery Partition was in between the C: partition and the new unallocated space (similar to the image below which I've copied from Woshub.com ), I was unable to do an "Extend Volume" job. The solution was to move the recovery partition.  This involves disabling it, deleting it, extending your partition as required, and then re-creating the recovery partition and enabling it. Here are the steps involved: Disable existing recovery partition: You will need to disable the existing Windows recovery partition. To do this, run this command from an admin command line/PowerShell:  reagentc /disable If you get the error message "REAGENTC.EXE: Operati...

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