M
Michael Solomon \(MS-MVP Windows Shell/User\)
All points well taken.
For the sake of brevity and not wanting to further confuse users to whom I
respond on the subject, I will likely stick to a boiler plate introductory
as follows:
"Though there is a DOS emulator, there is no DOS environment in XP as you
remember it from Windows 9x, hence some of things you are used to doing are
either no longer supported or can't be done..."
After the above intro, I will then endeavor to give them information on how
the task might be accomplished. In my case, the questions to which I
usually respond on this subject usually have to deal with recovery or
recovering files though, sometimes I also respond to questions of why they
are having problems running a particular application.
There is also the case of those who ask before purchasing XP whether or not
their DOS apps will run, a question we really can't answer in advance with
any certainty. I usually tell them, if they have mission critical
applications they must continue to use, they should either maintain their
current machine or dual boot their new system or setup with their current OS
in order to better ensure compatibility.
--
Michael Solomon MS-MVP
Windows Shell/User
Backup is a PC User's Best Friend
DTS-L.Org: http://www.dts-l.org/
Generally speaking the answer "there is no dos" is frequently given to
people trying to run Dos apps. Most dos apps written towards the end of
Dos's lifetime won't run, due to insufficient memory, without configuration.
However they wouldn't have run on a real Dos machine either without
configuration.
There are other configuration issues as well. All would have needed to be
addressed on Dos. XP's Dos, designed to run Line Of Business apps, gives
tons of memory to networking (and other typical corporate requirements).
Home user programs typically didn't use networking but did require the
memory that networking took. The program's manual will nearly always say
what to do to configure the program.
Any Dos program written to the Dos API will work. Nearly all common
departures from the API including direct hardware access will work. With the
addition of a vxd any dos program can access hardware (really access it). MS
provide vxds (built in) for common hardware such as keyboards, mouses,
serial ports, and printer ports. If the program switches to a video mode
that XP doesn't support it makes the program full screen (thus allowing it
direct access to the hardware), if it support it it emulates the hardware.
Except for protected mode memory managers (and some are supported) and
programs using sound cards nearly any non disk utility should work or be
configured to work (which configuration would have been needed in a dos
environment anyway).
I know that some questions are "how do I boot to dos". But many aren't that
get the answer "there is no dos".
For the sake of brevity and not wanting to further confuse users to whom I
respond on the subject, I will likely stick to a boiler plate introductory
as follows:
"Though there is a DOS emulator, there is no DOS environment in XP as you
remember it from Windows 9x, hence some of things you are used to doing are
either no longer supported or can't be done..."
After the above intro, I will then endeavor to give them information on how
the task might be accomplished. In my case, the questions to which I
usually respond on this subject usually have to deal with recovery or
recovering files though, sometimes I also respond to questions of why they
are having problems running a particular application.
There is also the case of those who ask before purchasing XP whether or not
their DOS apps will run, a question we really can't answer in advance with
any certainty. I usually tell them, if they have mission critical
applications they must continue to use, they should either maintain their
current machine or dual boot their new system or setup with their current OS
in order to better ensure compatibility.
--
Michael Solomon MS-MVP
Windows Shell/User
Backup is a PC User's Best Friend
DTS-L.Org: http://www.dts-l.org/
Generally speaking the answer "there is no dos" is frequently given to
people trying to run Dos apps. Most dos apps written towards the end of
Dos's lifetime won't run, due to insufficient memory, without configuration.
However they wouldn't have run on a real Dos machine either without
configuration.
There are other configuration issues as well. All would have needed to be
addressed on Dos. XP's Dos, designed to run Line Of Business apps, gives
tons of memory to networking (and other typical corporate requirements).
Home user programs typically didn't use networking but did require the
memory that networking took. The program's manual will nearly always say
what to do to configure the program.
Any Dos program written to the Dos API will work. Nearly all common
departures from the API including direct hardware access will work. With the
addition of a vxd any dos program can access hardware (really access it). MS
provide vxds (built in) for common hardware such as keyboards, mouses,
serial ports, and printer ports. If the program switches to a video mode
that XP doesn't support it makes the program full screen (thus allowing it
direct access to the hardware), if it support it it emulates the hardware.
Except for protected mode memory managers (and some are supported) and
programs using sound cards nearly any non disk utility should work or be
configured to work (which configuration would have been needed in a dos
environment anyway).
I know that some questions are "how do I boot to dos". But many aren't that
get the answer "there is no dos".