G
Guest
--
Joan
Joan
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
R
RJ
What do you mean...?
R
Ron Sommer
Start, Run, cmd
K
Ken Blake, MVP
Joan said:Nothing
Please ask your questions in the body of your message, not in the subject
line.
You can't literally switch to DOS in Windows XP because, unlike Windows 9X,
there is no DOS in Windows XP. However you can get a command promp tby
entering CMD at the Start | Run line. This gives you a window that looks
like a DOS windows, and for many purposes (but not all) will work the same
way.
If you want to boot to DOS, there's no way to do this from within WIndows
XP, and the only way to do it is to boot from a DOS diskette. Be aware
though, that if you boot from a DOS diskette and your hard drive is NTFS,
DOS won't be able to see it at all (unless you ruin special third-party
software).
For more help, tell us what you want to do in DOS.
P
Pegasus \(MVP\)
DOS is an operating system. There is no DOS under WinXP.
I suspect you mean the Command Prompt. If so, follow Ron
Sommer's suggestion.
I suspect you mean the Command Prompt. If so, follow Ron
Sommer's suggestion.
R
RobertVA
There isn't a DOS mode in Windows XP. Some DOS programs will run in a
Command Prompt window. Look under Start | All Programs | Accesories. For
full screen display under a Command Prompt, try holding the ALT key
while pressing the ENTER key.
Command Prompt window. Look under Start | All Programs | Accesories. For
full screen display under a Command Prompt, try holding the ALT key
while pressing the ENTER key.
W
Winux P
Pull out your old DOS disks and install it on a partition. As stable and as
efficient it's over Windows XP you must ask yourself do you want to revert
to such old technology on a PIV system?
- Winux P
efficient it's over Windows XP you must ask yourself do you want to revert
to such old technology on a PIV system?
- Winux P
R
Ron Sommer
Dos will only install on an active partition.
A boot manager would be needed to install Dos with out reinstalling XP.
A boot manager would be needed to install Dos with out reinstalling XP.
B
Bruce Chambers
Joan wrote:
Not to put too fine a point on it, you can't.
There is no way to reboot a WinXP PC into Real Mode DOS unless
you've set up a dual-boot system. The WinNT family of 32-bit
graphical operating systems, of which WinXP is the latest generation,
has never used, included, or "ridden upon" MS-DOS. The Recovery
Console's CLI (Command Line Interface) is the closest you can come to
the old "DOS mode." What, precisely, are you trying to accomplish?
--
Bruce Chambers
Help us help you:
You can have peace. Or you can have freedom. Don't ever count on having
both at once. - RAH
Not to put too fine a point on it, you can't.
There is no way to reboot a WinXP PC into Real Mode DOS unless
you've set up a dual-boot system. The WinNT family of 32-bit
graphical operating systems, of which WinXP is the latest generation,
has never used, included, or "ridden upon" MS-DOS. The Recovery
Console's CLI (Command Line Interface) is the closest you can come to
the old "DOS mode." What, precisely, are you trying to accomplish?
--
Bruce Chambers
Help us help you:
You can have peace. Or you can have freedom. Don't ever count on having
both at once. - RAH
F
Fred
There isn't a DOS mode in Windows XP. Some DOS programs will run in a
Command Prompt window.
You have a clue, now you have to apply it.
The Command Prompt _is_ DOS mode.
The Help file says, "The MS-DOS mode is a shell in which the MS-DOS
environment is emulated in 32-bit systems, such as Windows."
W
Wesley Vogel
The 16 bit MS-DOS Subsystem uses command.com not cmd.exe.
commmand.com...
---------
Microsoft(R) Windows DOS
(C)Copyright Microsoft Corp 1990-2001.
C:\DOCUME~1\WESLEY~1.VOG>
cmd.exe...
------------------
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\>
[[By default, the MS-DOS subsystem uses a special version of Command.com
that works seamlessly with the other Windows XP subsystems (including piping
and redirection between subsystems)...]]
http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/shell.mspx
Changes to MS-DOS Commands
and
Unavailable MS-DOS Commands
Start | Run | Paste this in the box and click OK...
hh ntcmds.chm::/dos_diffs.htm
MS-DOS subsystem commands
Start | Run | Paste this in the box and click OK...
hh ntcmds.chm::/dos_cmds.htm
--
Hope this helps. Let us know.
Wes
MS-MVP Windows Shell/User
In
commmand.com...
---------
Microsoft(R) Windows DOS
(C)Copyright Microsoft Corp 1990-2001.
C:\DOCUME~1\WESLEY~1.VOG>
cmd.exe...
------------------
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\>
[[By default, the MS-DOS subsystem uses a special version of Command.com
that works seamlessly with the other Windows XP subsystems (including piping
and redirection between subsystems)...]]
http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/shell.mspx
Changes to MS-DOS Commands
and
Unavailable MS-DOS Commands
Start | Run | Paste this in the box and click OK...
hh ntcmds.chm::/dos_diffs.htm
MS-DOS subsystem commands
Start | Run | Paste this in the box and click OK...
hh ntcmds.chm::/dos_cmds.htm
--
Hope this helps. Let us know.
Wes
MS-MVP Windows Shell/User
In
E
Edward W. Thompson
snipBruce Chambers said:Joan wrote:
Not to put too fine a point on it, you can't.
There is no way to reboot a WinXP PC into Real Mode DOS unless
you've set up a dual-boot system. The WinNT family of 32-bit
graphical operating systems, of which WinXP is the latest generation,
has never used, included, or "ridden upon" MS-DOS. The Recovery Console's
CLI (Command Line Interface) is the closest you can come to the old "DOS
mode." What, precisely, are you trying to accomplish?
A bootable floppy or CD works fine for me. Why install the complication of
dual boot?
P
Paul Knudsen
They call it Command Prompt now. In XP, click "Start" "run" type
"cmd" (without the quotes).
"cmd" (without the quotes).
N
NobodyMan
You have a clue, now you have to apply it.
The Command Prompt _is_ DOS mode.
The Help file says, "The MS-DOS mode is a shell in which the MS-DOS
environment is emulated in 32-bit systems, such as Windows."
No matter how you coat it, there is NO DOS in XP. There is an
emulation that looks like DOS, and many DOS commands/programs will run
in it, but many won't. It is an EMULATION, not real-mode DOS.
T
Tim Slattery
NobodyMan said:No matter how you coat it, there is NO DOS in XP. There is an
emulation that looks like DOS, and many DOS commands/programs will run
in it, but many won't. It is an EMULATION, not real-mode DOS.
It's not a DOS emulation, it's a 32-bit command console. It can switch
into 16-bit mode and run old DOS programs, as long as they don't try
to take direct control of hardware (many old DOS games sped things up
by writing directly to the video memory, that's not allowed under XP).
In 32-bit mode, command-line programs can do anything that fully GUI
Windows programs can.
W
Wesley Vogel
command.com is 16-bit. Even though command.com does not execute commands,
cmd.exe does.
[[The MS-DOS command prompt is a 16-bit DOS application that resides in the
COMMAND.COM executable file. Because COMMAND.COM is a 16-bit DOS executable,
Windows NT executes this shell within a Windows NT virtual DOS machine
(VDM). COMMAND.COM is supplied primarily for compatibility with MS-DOS.]]
http://www.microsoft.com/technet/archive/winntas/deploy/shellscr.mspx
--
Hope this helps. Let us know.
Wes
MS-MVP Windows Shell/User
In
cmd.exe does.
[[The MS-DOS command prompt is a 16-bit DOS application that resides in the
COMMAND.COM executable file. Because COMMAND.COM is a 16-bit DOS executable,
Windows NT executes this shell within a Windows NT virtual DOS machine
(VDM). COMMAND.COM is supplied primarily for compatibility with MS-DOS.]]
http://www.microsoft.com/technet/archive/winntas/deploy/shellscr.mspx
--
Hope this helps. Let us know.
Wes
MS-MVP Windows Shell/User
In
T
Tim Slattery
Wesley Vogel said:command.com is 16-bit. Even though command.com does not execute commands,
cmd.exe does.
"Does not execute commands"? What in the world does that mean?
Both command.com and cmd.exe are command interpreters. They present
you with a prompt, you type a command, they figure out what has to be
done to execute that command. Some commands (cd, for example) are
internal to the interpreters, others are executable files that are
located someplace on the disk.
cmd.exe is a 32-bit environment, and is much more capable than
command.com.
W
Wesley Vogel
"Does not execute commands"? What in the world does that mean?
It means that if you have command.com open and type a command, cmd.exe opens
and executes the command. It does not matter if the commands are internal
or external.
Maybe you'll look at the link I provided this time, the same one that I
provided in my previous post.
Try this for yourself.
[[You can see COMMAND.COM automatically execute a 32-bit CMD.EXE shell by
using the Windows NT Task Manager application. Follow this procedure:
1. Right-click in an empty area in the taskbar. From the popup window select
the Task Manager command to start Task Manager.
2. Click the Processes tab to display the list of running Windows NT
processes.
3. Click the Start button in the taskbar and select the Run command.
4. In the Open box, type COMMAND. Then click OK to start a 16-bit command
prompt.
5. Now examine the list of processes in the Task Manager window. You should
see at least one NTVDM process. This is the Windows NT VDM, which NT starts
to allow COMMAND.COM to execute.
6. In the COMMAND.COM window, enter any command which generates lengthy
output (DIR /S is a good choice). When the output begins scrolling, press
Ctrl+S to pause the command.
7. Switch to Task Manager and examine the list of processes again. Notice
that a new CMD.EXE (command shell) is running.
8. Switch to the COMMAND.COM window and press Ctrl+S again. Wait for the
command to complete.
9. Switch to Task Manager again. Notice that the CMD.EXE shell has
disappeared from the Processes list.
10. To close the COMMAND.COM window enter an EXIT command.
This simple experiment shows that every command entered for execution,
regardless of the shell used, is ultimately executed by CMD.EXE, the Windows
NT command shell.]]
http://www.microsoft.com/technet/archive/winntas/deploy/shellscr.mspx
--
Hope this helps. Let us know.
Wes
MS-MVP Windows Shell/User
In
It means that if you have command.com open and type a command, cmd.exe opens
and executes the command. It does not matter if the commands are internal
or external.
Maybe you'll look at the link I provided this time, the same one that I
provided in my previous post.
Try this for yourself.
[[You can see COMMAND.COM automatically execute a 32-bit CMD.EXE shell by
using the Windows NT Task Manager application. Follow this procedure:
1. Right-click in an empty area in the taskbar. From the popup window select
the Task Manager command to start Task Manager.
2. Click the Processes tab to display the list of running Windows NT
processes.
3. Click the Start button in the taskbar and select the Run command.
4. In the Open box, type COMMAND. Then click OK to start a 16-bit command
prompt.
5. Now examine the list of processes in the Task Manager window. You should
see at least one NTVDM process. This is the Windows NT VDM, which NT starts
to allow COMMAND.COM to execute.
6. In the COMMAND.COM window, enter any command which generates lengthy
output (DIR /S is a good choice). When the output begins scrolling, press
Ctrl+S to pause the command.
7. Switch to Task Manager and examine the list of processes again. Notice
that a new CMD.EXE (command shell) is running.
8. Switch to the COMMAND.COM window and press Ctrl+S again. Wait for the
command to complete.
9. Switch to Task Manager again. Notice that the CMD.EXE shell has
disappeared from the Processes list.
10. To close the COMMAND.COM window enter an EXIT command.
This simple experiment shows that every command entered for execution,
regardless of the shell used, is ultimately executed by CMD.EXE, the Windows
NT command shell.]]
http://www.microsoft.com/technet/archive/winntas/deploy/shellscr.mspx
--
Hope this helps. Let us know.
Wes
MS-MVP Windows Shell/User
In
T
Tim Slattery
Wesley Vogel said:It means that if you have command.com open and type a command, cmd.exe opens
and executes the command. It does not matter if the commands are internal
or external.
That page says, in part:
This behavior reveals a quite subtle feature of Windows NT that is
very important. The 16-bit MS-DOS shell (COMMAND.COM) that ships with
Windows NT is specially designed for Windows NT. When a command is
entered for execution by this shell, it does not actually execute it.
Instead, it packages the command text and sends it to a 32-bit CMD.EXE
command shell for execution. Because all commands are actually
executed by CMD.EXE (the Windows NT command shell), the 16-bit shell
inherits all the features and facilities of the full Windows NT shell.
You're right. I'm pretty sure I've seen that page before, but I'd
forgotten that paragraph.
W
Wesley Vogel
If you're like me, you don't use command.com for anything any way. ;-)
I do not run any old 16 bit apps, I only use command.com once in a while to
check something before I post.
--
Hope this helps. Let us know.
Wes
MS-MVP Windows Shell/User
In
I do not run any old 16 bit apps, I only use command.com once in a while to
check something before I post.
--
Hope this helps. Let us know.
Wes
MS-MVP Windows Shell/User
In