Hi veritasffg,
I don't have the knockdown solution, but I can sympathise because I run a database in dBASE 5 for DOS which recently just stopped working altogether under Windows 2000 (to my horror).
In my case it appears that the Windows VDM (Virtual DOS Machine) had become corrupted. You can test for this by clicking on Start > Run, then type COMMAND.COM and hit OK. If a DOS window opens, showing the command prompt, then your VDM is ok (according to Microsoft) and the problem must be elsewhere.
If the window won't open, then your VDM is corrupted. This is repairable but not by simply re-installing the VDM. There is a complex sequence of steps to be followed and you can find the full instructions at the Microsoft site - unfortunately I've mislaid the link, so you will have to search for it!
As to (re-)creating a Command prompt shortcut, this is just a matter of right-clicking anywhere on the desktop, selecting New > Shortcut, and referencing it to C:\Windows\System32\Command.com. Having created it, you can drag-and-drop it to anywhere in your Start menu.
Are you getting any specific error messages when your DOS applications fail to run?
Not the biggest thing on your mind right now, I know, but in case you are not aware of it, there is a third-party utility called TameDOS which you can purchase for $US20 or something like that; it loads in the background and enables DOS applications to run smoothly and reliably under the later Windows versions. It is a very professional product and I recommend it without any hesitation.