DOS applications on XP?

  • Thread starter Thread starter Dave
  • Start date Start date
D

Dave

Sorry for the ingorant question, but if XP is based
on 2000, does that mean support for DOS goes away?

I have 2 machines, a 2000 sp3, and a WInME. Many of the
things I install/run on WinME. come from my Win95 days
and work perfectly, but most of those same things fail to
load on Win2000 (telling me the OS is incompatible, or
just downright don't work).

So, the question is, will most things that worked in a
DOS/Win95 environment work in XP, or will they fail like
on Win 2000?

Thanks

Dave
 
There is support for a huge number of applications - even DOS ones - on
Windows XP. However, not all of them will work. There is a software
compatibility tool which you can use to resolve some problem, but in the
end, it depends what software you are talking about.
 
They will fail like win 2000. Like dos you need to setup the dos environment for your program. Most Dos programs work.
 
Where can you find the settings for the dos environment? I have one xp pro
computer that runs a dos app fine and another that will not. Trying to find
out where the difference could be.

Thanks,

Michael
(e-mail address removed)

They will fail like win 2000. Like dos you need to setup the dos environment
for your program. Most Dos programs work.
 
Look in c:\windows\system32\autoexec.nt and config.nt. Settings here apply to Dos and Win 3.1 programs. Biggest problem is that a lot of Dos Progs want memory, as configured by default XP gives em services which chew up memory. Try disabling various things, eg if the program doesn't use the network then don't load the network drivers.

You can specify edited copies of the files be used in the shortcut to a dos program.
 
What makes you think I could have any idea about a secret problem. Why did you bother to waste your time making posts without any information. Did you expect me to compile a 40 000 word monograph for you on every dos program in the world.

I want to know what goes through the head of you and people like you (who number in the thousands each day) when you make posts without mentioning the problem and then demand solutions to secret problems.

Lets look at some common question.

"I can't delete a file or folder?" - They never mention which file or folder.

"I can't see a particular web page?" - The never mention the page.

"I can't run a program?" - They never mention the program.

And of course they NEVER ever say what they actually did and what EXACTLY happened.
 
David,

Sorry to have made the assumption that one could read the thread. However,
since some details would seem to help. Here goes.

Old DOS accounting software, custom designed. Under Windows NT and WIN2000
and "most" computers with WinXP I can successfully run the command "forcedos
ra.exe and the programs run fine. On one laptop with XP the program freezes.
I am simply searching for ideas that might cause one copy of xp to not work.
As I stated in the previous post. the config.nt and autoexec.nt files are
identical. Are you aware of any other settings that might require
adjustment. Thanks.


What makes you think I could have any idea about a secret problem. Why did
you bother to waste your time making posts without any information. Did you
expect me to compile a 40 000 word monograph for you on every dos program in
the world.

I want to know what goes through the head of you and people like you (who
number in the thousands each day) when you make posts without mentioning the
problem and then demand solutions to secret problems.

Lets look at some common question.

"I can't delete a file or folder?" - They never mention which file or
folder.

"I can't see a particular web page?" - The never mention the page.

"I can't run a program?" - They never mention the program.

And of course they NEVER ever say what they actually did and what EXACTLY
happened.
 
All windows applications are dual dos /windows application. Usually the dos application merely says "This Program Requires Microsoft Windows".

Likewise in OS/2 there were dual OS programs, OS/2 and MS-Dos. ForceDos is meant to specify the program should be run as a dos program rather than as an OS/2 program.

Prior to Windows 2000 the NT platform supported OS/2. As the OS/2 is a sub system, like Windows and Posix, but unlike MSDos and Win16 (they are emulators), which was designed to Run MS-Dos programs - Windows used the OS/2 subsystem by default to run Dos programs. Possibly forcedos could force a dos app into the dos system.

Regardless, there is no OS/2 system in windows 2000 or XP. Therefore forcedos is unnecessary. Perhaps your database is a dual os/2 / dos application (aka bound application).

Custom databases are based on well known (to programmers) programs. It will still be based on an application. See if you can get this from the version info, splash screen, etc.
 
Back
Top