What makes an MSDOS application run with CMD instead COMMAND in WinXP?
Marco A. Cruz Quevedo
Once I read that there is a registry setting that makes an MSDOS
application run with CMD instead COMMAND in WinXP. How can I find this
information? What is it related to.?
Thanks in advance for your response.
Best regards
Marco.
---------------------------------------
Freedom is not a permission for chaos.
Jaelani
Generally, the COMSPEC environment variable specifies the default
command interpreter. But all DOS COM & EXE executables always run under
COMMAND (and under NTVDM) because it's required for DOS environment -
regardless the COMSPEC variable value.
What exactly are you trying to accomplish anyway?
Marco A. Cruz Quevedo
Firstly, thank you for your response.
I have a CA-Clipper application (MSDOS .exe ) and when I click it, it
runs under COMMAND, i. e. COMMAND is run FIRST and then it calls my
application. This is the normal procedure in WinNT (XP, Vista). But,
as I mentioned above, I read that CMD can be set as default, instead
of COMMAND, for some applications to run.
I need this because I run the same application under WinVista (in
spanish) but if COMMAND is run, the keyb setting (KEYB SP I need, and
it is set to WinVista) is not taken by default, but KEYB US, which is
not desired. If I first run CMD (KEYB SP is set) and then run my
application, the keyboard setting is correct.
I hope you can help.
Thank you,
Marco
Auric__
> Marco A. Cruz Quevedo wrote:
>>
>> Once I read that there is a registry setting that makes an MSDOS
>> application run with CMD instead COMMAND in WinXP. How can I find this
>> information? What is it related to.?
>
> Generally, the COMSPEC environment variable specifies the default
> command interpreter. But all DOS COM & EXE executables always run under
> COMMAND (and under NTVDM) because it's required for DOS environment -
> regardless the COMSPEC variable value.
>
> What exactly are you trying to accomplish anyway?
OP may be thinking of Windows console programs...
--
- But what did you use to jargon jargon babble babble strange words?
- It took a while to perfect, but chatter chatter jargon jargon computers
technical wizardry babble jargon.
Jaelani
Oh, it's a key thingy... :o
Try these steps (assuming you already have Spanish keyboard layout
installed under Windows):
1. Open Notepad and edit the CONFIG.NT file in your SYSTEM32 folder.
2. At the end of the file, add below new line:
COUNTRY=034,850,%SystemRoot%\system32\country.sys
3. Save the file. May need administrator access in Vista/Win7.
4. Still in Notepad, edit the AUTOEXEC.NT file in your SYSTEM32 folder.
5. At the end of the file, add below new line:
%SystemRoot%\system32\kb16 SP,850,%SystemRoot%\system32\keyboard.sys
6. Save the file. May need administrator access in Vista/Win7. Then exit
Notepad.
7. Run CA-Clipper and test your keyboard keys.
Note:
- It should work. But no warranty.
- The above steps will affects globally and will affect all MSDOS
programs. If you want to affect only for that program you should copy
the above two files (CONFIG.NT and AUTOEXEC.NT) into your Clipper
directory, edit them using above steps, open the Clipper shortcut (e.g.:
in Start Menu / Desktop) property and change the two paths that point to
the two *.NT files to the ones in the Clipper directory.
Marco A. Cruz Quevedo
>
> - Show quoted text -
Thank you very much for the hit. I am going to try and I will keep you
informed.
Regards,
Marco A. Cruz Quevedo
Ntcmdprompt
Runs the command interpreter Cmd.exe, rather than Command.com, after
running a TSR or after starting the command prompt from within an MS-
DOS application.
[http://technet.microsoft.com/en-us/library/bb490953.aspx]
This command should be inserted in config.nt.
Thank you all for your support.
Best regards,
Marco.
---------------------------------------
Freedom is not a permission for chaos.
Marco A. Cruz Quevedo
Any Ideas?
On Aug 22, 11:18 am, "Marco A. Cruz Quevedo" <macr...@myway.com>
wrote: