debug.exe Incorrect Version - XP created Boot floppy

[Rupert]

If I open a Command window in XP and run debug.exe this
works fine.

If I use the format floppy option in XP to create a boot
diskette and copy the debug.exe from \windows\system32\
directory
If I try to run debug.exe on the floppy, it will not load
and reports incorrect DOS version.

(I tried to use setver.exe, but the device will not load
from config.sys).

Any ideas please?

 

[Will Denny]

Hi

What you trying to do using debug.exe?

--

Will Denny
MS-MVP Windows - Shell/User
Please reply to the News Groups


| If I open a Command window in XP and run debug.exe this
| works fine.
|
| If I use the format floppy option in XP to create a boot
| diskette and copy the debug.exe from \windows\system32\
| directory
| If I try to run debug.exe on the floppy, it will not load
| and reports incorrect DOS version.
|
| (I tried to use setver.exe, but the device will not load
| from config.sys).
|
| Any ideas please?

 

[Rupert]

Something deep on a hard drive.
I know there are other ways, but this is something I
thought I understood and was portable.
Rupert

 

[Will Denny]

Hi

You need to have command.com present for debug.exe to work.

--

Will Denny
MS-MVP Windows - Shell/User
Please reply to the News Groups


| Something deep on a hard drive.
| I know there are other ways, but this is something I
| thought I understood and was portable.
| Rupert
| >-----Original Message-----
| >Hi
| >
| >What you trying to do using debug.exe?
| >
| >--
| >
| >Will Denny
| >MS-MVP Windows - Shell/User
| >Please reply to the News Groups
| >
| >
| message
| >| >| If I open a Command window in XP and run debug.exe this
| >| works fine.
| >|
| >| If I use the format floppy option in XP to create a boot
| >| diskette and copy the debug.exe from \windows\system32\
| >| directory
| >| If I try to run debug.exe on the floppy, it will not
| load
| >| and reports incorrect DOS version.
| >|
| >| (I tried to use setver.exe, but the device will not load
| >| from config.sys).
| >|
| >| Any ideas please?
| >
| >.
| >

 

[David Candy]

Debug is designed for Dos 5 (or 5.0.5 which is Dos 5 on NT). A boot disk is Windows Millenium (Dos 7.1 from memory). You need setver from windows milenium. Might as well get debug from it instead.

 

[R. C. White]

Hi, Rupert.

The version of Debug.exe in WinXP is designed to run in the "DOS" emulator,
not in true MS-DOS, which is what WinXP puts onto the MS-DOS startup disk it
creates. As you probably noticed, in the "DOS" window, it identifies itself
as:
Microsoft Windows XP [Version 5.1.2600]
with no mention of DOS at all.

I've forgotten the exact Version on the floppy, and I don't want to reboot
from the floppy just to see, but, as David Candy said, it is the version
included in WinME. It is true MS-DOS, NOT the WinXP emulator. If you can
copy Debug.exe from a Win9x/ME source onto your floppy, it should work.

RC

 

[David Candy]

Type
command /kver
to see the MS Dos version. Commands typed in command go to cmd for execution. Cmd is telling you it's version not the Dos version.

--
----------------------------------------------------------
'Not happy John! Defending our democracy',
http://www.smh.com.au/articles/2004/06/29/1088392635123.html

Hi, Rupert.

The version of Debug.exe in WinXP is designed to run in the "DOS" emulator,
not in true MS-DOS, which is what WinXP puts onto the MS-DOS startup disk it
creates. As you probably noticed, in the "DOS" window, it identifies itself
as:
Microsoft Windows XP [Version 5.1.2600]
with no mention of DOS at all.

I've forgotten the exact Version on the floppy, and I don't want to reboot
from the floppy just to see, but, as David Candy said, it is the version
included in WinME. It is true MS-DOS, NOT the WinXP emulator. If you can
copy Debug.exe from a Win9x/ME source onto your floppy, it should work.

RC
--
R. C. White, CPA
San Marcos, TX
(e-mail address removed)
Microsoft Windows MVP

If I open a Command window in XP and run debug.exe this
works fine.

If I use the format floppy option in XP to create a boot
diskette and copy the debug.exe from \windows\system32\
directory
If I try to run debug.exe on the floppy, it will not load
and reports incorrect DOS version.

(I tried to use setver.exe, but the device will not load
from config.sys).

Any ideas please?

 

[R. C. White]

Hi, David.

That's a new one on me! Command /? doesn't show kver in its list of tricks.
Command alone, of course, runs Command.com; from that shell, ver and command
/kver say the same as from Cmd.exe, and kver alone is not recognized.

How did you learn this, David? Where is kver documented? It actually says
"MS-DOS Version 5.00.500"; I suppose that's kind of like SetVer, meaning
that's the version that Cmd.exe emulates?

RC
--
R. C. White, CPA
San Marcos, TX
(e-mail address removed)
Microsoft Windows MVP

Type
command /kver
to see the MS Dos version. Commands typed in command go to cmd for
execution. Cmd is telling you it's version not the Dos version.

--

Hi, Rupert.

The version of Debug.exe in WinXP is designed to run in the "DOS"
emulator,
not in true MS-DOS, which is what WinXP puts onto the MS-DOS startup disk
it
creates. As you probably noticed, in the "DOS" window, it identifies
itself
as:
Microsoft Windows XP [Version 5.1.2600]
with no mention of DOS at all.

I've forgotten the exact Version on the floppy, and I don't want to reboot
from the floppy just to see, but, as David Candy said, it is the version
included in WinME. It is true MS-DOS, NOT the WinXP emulator. If you can
copy Debug.exe from a Win9x/ME source onto your floppy, it should work.

RC

If I open a Command window in XP and run debug.exe this
works fine.

If I use the format floppy option in XP to create a boot
diskette and copy the debug.exe from \windows\system32\
directory
If I try to run debug.exe on the floppy, it will not load
and reports incorrect DOS version.

(I tried to use setver.exe, but the device will not load
from config.sys).

Any ideas please?

 

[David Candy]

I did the lazy way. As long as you don't need /? switch it works. Fully it's

command /k ver
but
command/kver
also works in a command prompt

but
command /kver /?
will give help on command.
Command /k ver /?
will give help on ver (there is a hidden switch /r as well - it tells you if dos is in the HMA)

Command prompt parsing is smarter than GUI processing. Only a space is a delimiter in the GUI. But a switch must be a delimiter so a command prompt will use any delimiter (can only think of space or /). On CP/VMS (an operating system) it is the character after the command that determines the delimiter so
rexx;filename;/p
is same as

rexx filename /p
This allows a filename with a space in it in this example (not that I remember what the rexx switches were or that files could have spaces).

It traditional that parameters olny need to be typed till they match

eg
if a program has allfiles and allfolders as parameters one can type
allfi<rest of chars optional>
or
allfo<rest of chars optional>

--
----------------------------------------------------------
'Not happy John! Defending our democracy',
http://www.smh.com.au/articles/2004/06/29/1088392635123.html

Hi, David.

That's a new one on me! Command /? doesn't show kver in its list of tricks.
Command alone, of course, runs Command.com; from that shell, ver and command
/kver say the same as from Cmd.exe, and kver alone is not recognized.

How did you learn this, David? Where is kver documented? It actually says
"MS-DOS Version 5.00.500"; I suppose that's kind of like SetVer, meaning
that's the version that Cmd.exe emulates?

RC
--
R. C. White, CPA
San Marcos, TX
(e-mail address removed)
Microsoft Windows MVP

Type
command /kver
to see the MS Dos version. Commands typed in command go to cmd for
execution. Cmd is telling you it's version not the Dos version.

--

Hi, Rupert.

The version of Debug.exe in WinXP is designed to run in the "DOS"
emulator,
not in true MS-DOS, which is what WinXP puts onto the MS-DOS startup disk
it
creates. As you probably noticed, in the "DOS" window, it identifies
itself
as:
Microsoft Windows XP [Version 5.1.2600]
with no mention of DOS at all.

I've forgotten the exact Version on the floppy, and I don't want to reboot
from the floppy just to see, but, as David Candy said, it is the version
included in WinME. It is true MS-DOS, NOT the WinXP emulator. If you can
copy Debug.exe from a Win9x/ME source onto your floppy, it should work.

RC

If I open a Command window in XP and run debug.exe this
works fine.

If I use the format floppy option in XP to create a boot
diskette and copy the debug.exe from \windows\system32\
directory
If I try to run debug.exe on the floppy, it will not load
and reports incorrect DOS version.

(I tried to use setver.exe, but the device will not load
from config.sys).

Any ideas please?

 

[R. C. White]

Hi, David.

Thanks for the mini-education. ;^}

I get mixed results when I try those command lines. Surprisingly (to me),
when I type just
command /k
I get into a new command interpreter, just as if I type Command alone.
Nothing seems to happen onscreen, but if I type Exit, I go back to Cmd.exe.
If I type
command /kver
or
command /k ver
I see the Version AND I'm in the new interpreter. And there are variations
on this theme.

If I'm not paying attention, I can be several layers deep in new
interpreters! It takes several Exits to get back to Cmd.exe. And the
keyboard is sluggish; there's a noticeable delay before a typed character
appears onscreen until I get back there.

command /kver /r
tells me:
MS-DOS Version 5.00.500
Revision A
DOS is in HMA

I've forgotten what HMA is (if I knew). Is that the High Memory Area that
we used to use in MS-DOS? (The terms Extended and Expanded Memory are still
rattling around somewhere just beneath the surface of my brain, it seems.)
And I barely recognize the name Rexx.

Not that I really want to get into (or back into) all this stuff. Just need
enough to keep me from tripping over something while I'm in the "DOS"
window - where I spend some time every day. Or to keep me from giving wrong
or misleading advice to someone asking such questions here.

RC
--
R. C. White, CPA
San Marcos, TX
(e-mail address removed)
Microsoft Windows MVP

I did the lazy way. As long as you don't need /? switch it works. Fully it's

command /k ver
but
command/kver
also works in a command prompt

but
command /kver /?
will give help on command.
Command /k ver /?
will give help on ver (there is a hidden switch /r as well - it tells you if
dos is in the HMA)

Command prompt parsing is smarter than GUI processing. Only a space is a
delimiter in the GUI. But a switch must be a delimiter so a command prompt
will use any delimiter (can only think of space or /). On CP/VMS (an
operating system) it is the character after the command that determines the
delimiter so
rexx;filename;/p
is same as

rexx filename /p
This allows a filename with a space in it in this example (not that I
remember what the rexx switches were or that files could have spaces).

It traditional that parameters olny need to be typed till they match

eg
if a program has allfiles and allfolders as parameters one can type
allfi<rest of chars optional>
or
allfo<rest of chars optional>

--
----------------------------------------------------------
'Not happy John! Defending our democracy',
http://www.smh.com.au/articles/2004/06/29/1088392635123.html

Hi, David.

That's a new one on me! Command /? doesn't show kver in its list of
tricks.
Command alone, of course, runs Command.com; from that shell, ver and
command
/kver say the same as from Cmd.exe, and kver alone is not recognized.

How did you learn this, David? Where is kver documented? It actually
says
"MS-DOS Version 5.00.500"; I suppose that's kind of like SetVer, meaning
that's the version that Cmd.exe emulates?

RC

Type
command /kver
to see the MS Dos version. Commands typed in command go to cmd for
execution. Cmd is telling you it's version not the Dos version.

--

Hi, Rupert.

The version of Debug.exe in WinXP is designed to run in the "DOS"
emulator,
not in true MS-DOS, which is what WinXP puts onto the MS-DOS startup
disk
it
creates. As you probably noticed, in the "DOS" window, it identifies
itself
as:
Microsoft Windows XP [Version 5.1.2600]
with no mention of DOS at all.

I've forgotten the exact Version on the floppy, and I don't want to
reboot
from the floppy just to see, but, as David Candy said, it is the version
included in WinME. It is true MS-DOS, NOT the WinXP emulator. If you
can
copy Debug.exe from a Win9x/ME source onto your floppy, it should work.

RC

If I open a Command window in XP and run debug.exe this
works fine.

If I use the format floppy option in XP to create a boot
diskette and copy the debug.exe from \windows\system32\
directory
If I try to run debug.exe on the floppy, it will not load
and reports incorrect DOS version.

(I tried to use setver.exe, but the device will not load
from config.sys).

Any ideas please?

 

[David Candy]

If he emails me I'll send him debug from millenium.

The HMA was a bug in the 80286 processor. But people found a way to get more dos memory from it (conventional memory sort off) so the bug is now a feature. The 80286 allowed the memory to roll over but instead of going to 0 address it went into extended memory above 1024K for 64K.

It should run at normal speed in a full screen window. It's slow cause Windows is emulating a video card if it's windowed.

--
----------------------------------------------------------
'Not happy John! Defending our democracy',
http://www.smh.com.au/articles/2004/06/29/1088392635123.html

Hi, David.

Thanks for the mini-education. ;^}

I get mixed results when I try those command lines. Surprisingly (to me),
when I type just
command /k
I get into a new command interpreter, just as if I type Command alone.
Nothing seems to happen onscreen, but if I type Exit, I go back to Cmd.exe.
If I type
command /kver
or
command /k ver
I see the Version AND I'm in the new interpreter. And there are variations
on this theme.

If I'm not paying attention, I can be several layers deep in new
interpreters! It takes several Exits to get back to Cmd.exe. And the
keyboard is sluggish; there's a noticeable delay before a typed character
appears onscreen until I get back there.

command /kver /r
tells me:
MS-DOS Version 5.00.500
Revision A
DOS is in HMA

I've forgotten what HMA is (if I knew). Is that the High Memory Area that
we used to use in MS-DOS? (The terms Extended and Expanded Memory are still
rattling around somewhere just beneath the surface of my brain, it seems.)
And I barely recognize the name Rexx.

Not that I really want to get into (or back into) all this stuff. Just need
enough to keep me from tripping over something while I'm in the "DOS"
window - where I spend some time every day. Or to keep me from giving wrong
or misleading advice to someone asking such questions here.

RC
--
R. C. White, CPA
San Marcos, TX
(e-mail address removed)
Microsoft Windows MVP

I did the lazy way. As long as you don't need /? switch it works. Fully it's

command /k ver
but
command/kver
also works in a command prompt

but
command /kver /?
will give help on command.
Command /k ver /?
will give help on ver (there is a hidden switch /r as well - it tells you if
dos is in the HMA)

Command prompt parsing is smarter than GUI processing. Only a space is a
delimiter in the GUI. But a switch must be a delimiter so a command prompt
will use any delimiter (can only think of space or /). On CP/VMS (an
operating system) it is the character after the command that determines the
delimiter so
rexx;filename;/p
is same as

rexx filename /p
This allows a filename with a space in it in this example (not that I
remember what the rexx switches were or that files could have spaces).

It traditional that parameters olny need to be typed till they match

eg
if a program has allfiles and allfolders as parameters one can type
allfi<rest of chars optional>
or
allfo<rest of chars optional>

--
----------------------------------------------------------
'Not happy John! Defending our democracy',
http://www.smh.com.au/articles/2004/06/29/1088392635123.html

Hi, David.

That's a new one on me! Command /? doesn't show kver in its list of
tricks.
Command alone, of course, runs Command.com; from that shell, ver and
command
/kver say the same as from Cmd.exe, and kver alone is not recognized.

How did you learn this, David? Where is kver documented? It actually
says
"MS-DOS Version 5.00.500"; I suppose that's kind of like SetVer, meaning
that's the version that Cmd.exe emulates?

RC

Type
command /kver
to see the MS Dos version. Commands typed in command go to cmd for
execution. Cmd is telling you it's version not the Dos version.

--

Hi, Rupert.

The version of Debug.exe in WinXP is designed to run in the "DOS"
emulator,
not in true MS-DOS, which is what WinXP puts onto the MS-DOS startup
disk
it
creates. As you probably noticed, in the "DOS" window, it identifies
itself
as:
Microsoft Windows XP [Version 5.1.2600]
with no mention of DOS at all.

I've forgotten the exact Version on the floppy, and I don't want to
reboot
from the floppy just to see, but, as David Candy said, it is the version
included in WinME. It is true MS-DOS, NOT the WinXP emulator. If you
can
copy Debug.exe from a Win9x/ME source onto your floppy, it should work.

RC

If I open a Command window in XP and run debug.exe this
works fine.

If I use the format floppy option in XP to create a boot
diskette and copy the debug.exe from \windows\system32\
directory
If I try to run debug.exe on the floppy, it will not load
and reports incorrect DOS version.

(I tried to use setver.exe, but the device will not load
from config.sys).

Any ideas please?

 

[Rupert]

Thanks a lot for all your help.

I'll ask locally ror an ME debug, if I fail to locate,
then will take up David's kind offer.

Regards

Rupert

-----Original Message-----
If he emails me I'll send him debug from millenium.

The HMA was a bug in the 80286 processor. But people

found a way to get more dos memory from it (conventional
memory sort off) so the bug is now a feature. The 80286
allowed the memory to roll over but instead of going to 0
address it went into extended memory above 1024K for 64K.

It should run at normal speed in a full screen window.

It's slow cause Windows is emulating a video card if it's
windowed.

--
----------------------------------------------------------
'Not happy John! Defending our democracy',
http://www.smh.com.au/articles/2004/06/29/1088392635123.ht ml

Hi, David.

Thanks for the mini-education. ;^}

I get mixed results when I try those command lines. Surprisingly (to me),
when I type just
command /k
I get into a new command interpreter, just as if I type Command alone.
Nothing seems to happen onscreen, but if I type Exit, I go back to Cmd.exe.
If I type
command /kver
or
command /k ver
I see the Version AND I'm in the new interpreter. And there are variations
on this theme.

If I'm not paying attention, I can be several layers deep in new
interpreters! It takes several Exits to get back to Cmd.exe. And the
keyboard is sluggish; there's a noticeable delay before a typed character
appears onscreen until I get back there.

command /kver /r
tells me:
MS-DOS Version 5.00.500
Revision A
DOS is in HMA

I've forgotten what HMA is (if I knew). Is that the High Memory Area that
we used to use in MS-DOS? (The terms Extended and Expanded Memory are still
rattling around somewhere just beneath the surface of my brain, it seems.)
And I barely recognize the name Rexx.

Not that I really want to get into (or back into) all this stuff. Just need
enough to keep me from tripping over something while I'm in the "DOS"
window - where I spend some time every day. Or to keep me from giving wrong
or misleading advice to someone asking such questions here.

RC
--
R. C. White, CPA
San Marcos, TX
(e-mail address removed)
Microsoft Windows MVP

I did the lazy way. As long as you don't need /? switch it works. Fully it's

command /k ver
but
command/kver
also works in a command prompt

but
command /kver /?
will give help on command.
Command /k ver /?
will give help on ver (there is a hidden switch /r as well - it tells you if
dos is in the HMA)

Command prompt parsing is smarter than GUI processing. Only a space is a
delimiter in the GUI. But a switch must be a delimiter so a command prompt
will use any delimiter (can only think of space or /). On CP/VMS (an
operating system) it is the character after the command that determines the
delimiter so
rexx;filename;/p
is same as

rexx filename /p
This allows a filename with a space in it in this example (not that I
remember what the rexx switches were or that files could have spaces).

It traditional that parameters olny need to be typed till they match

eg
if a program has allfiles and allfolders as parameters one can type
allfi<rest of chars optional>
or
allfo<rest of chars optional>

http://www.smh.com.au/articles/2004/06/29/1088392635123.htm
l

Hi, David.

That's a new one on me! Command /? doesn't show kver in its list of
tricks.
Command alone, of course, runs Command.com; from that shell, ver and
command
/kver say the same as from Cmd.exe, and kver alone is not recognized.

How did you learn this, David? Where is kver documented? It actually
says
"MS-DOS Version 5.00.500"; I suppose that's kind of like SetVer, meaning
that's the version that Cmd.exe emulates?

RC

Type
command /kver
to see the MS Dos version. Commands typed in command go to cmd for
execution. Cmd is telling you it's version not the Dos version.

--

Hi, Rupert.

The version of Debug.exe in WinXP is designed to run in the "DOS"
emulator,
not in true MS-DOS, which is what WinXP puts onto the MS-DOS startup
disk
it
creates. As you probably noticed, in the "DOS" window, it identifies
itself
as:
Microsoft Windows XP [Version 5.1.2600]
with no mention of DOS at all.

I've forgotten the exact Version on the floppy, and I don't want to
reboot
from the floppy just to see, but, as David Candy said, it is the version
included in WinME. It is true MS-DOS, NOT the WinXP emulator. If you
can
copy Debug.exe from a Win9x/ME source onto your floppy, it should work.

RC

If I open a Command window in XP and run debug.exe this
works fine.

If I use the format floppy option in XP to create a boot
diskette and copy the debug.exe from \windows\system32\
directory
If I try to run debug.exe on the floppy, it will not load
and reports incorrect DOS version.

(I tried to use setver.exe, but the device will not load
from config.sys).

Any ideas please?

.