Checking existence of command in cmd.exe

I want to run somone from cmd.exe using some procedure, for example WEBUTIL_HOST.HOST ('cmd / c start iexplore' | | url)
Can I somehow check before executing, that command exists and that it will be execute?
Edited by: Ihavoker on 04.02.2011 16:42

InoL wrote:
HOST doesn't return an error when the OS command returns an error. HOST only fails when the HOST call itself fails. So checking form_failure is usually not what you want.
However, in your case you should try:
HOST ('cmd / c start ' | | url);
If you just start an URL, Windows will automatically look for the default browser.I understand, it might seem strange.
Unfortunately, it is necessary to open a web page only IE. However, the browser by default does not necessarily IE. And the forms should check, the IE installed. Ie Command HOST ('cmd / c iexplore' | | url); executed. Just not sure that IE is installed in the default directory.
That is a problem... :(
Edited by: Ihavoker on 07.02.2011 12:16

Similar Messages

Automagically launch progam in command prompt (cmd.exe)?

If one develop a simple Java program that wants input from a user (using for instance the java.util.Scanner class), is there any way to automagically launch the program in a command prompt? I've tried to locate some information about this but it seems that it can't be done and JDeveloper is for GUI programs only.
As for now, I compile and manually opens a command prompt window and use
java -cp . Program.classit works. But I am hoping for an automatic method so that I can just press the "Run" button in Jdeveloper. Anyone? Thanks.
Anders Ericsson
Stockholm, Sweden

Found it myself. Here's the solution. But it doesn't work perfectly! A bug?
In JDeveloper 10.1.3, Project Properties->Run/Debug->Edit
choose the program that should be be the default run target.
Click "Tool Settings" in the left pane and then in the right pane under "Additional Runner Options" select "Allow program input".
It works, but the input works better in the command prompt. The problem is that after entering one input the Input-line looses focus and one have to click it to re-focus. A bug?
However, this lets me use the "Run" button. All in all, a more efficient way of developing programs.
/Anders Ericsson
Stockholm, Sweden

Boot Camp 2.1 HELP? cmd.exe?

I have been trying to update my Boot Camp to 2.1, and I have experienced the issue in the following support article.
http://support.apple.com/kb/HT1845
The article suggest that I do the following.
In Windows, start a command prompt (cmd.exe, sometimes referred to as a command shell). Use Administrative rights if running Windows Vista.
Type one the following command lines in the command shell:
For Windows XP, type: msiexec /update <path to the .msp file>\BCUpdateXP.msp
Can someone give me a dummies guide to how this can be done?
How do I launch "cmd.exe"?
What is <path to the .msp file>?
Thank you!

For anyone interested in the answer to this issue, I have summarized a quick fix.
1)
“Cmd.exe” can be accessed via the “Start” menu and “Accessories” in Windows XP.
2)
To get the “path to file”, simply drag the icon of the update into cmd.exe, and the path will be shown in its proper command sequence.

Execute Script by cmd.exe?

Hi! Is there a possibility to execute some scripts (batch processing) via the command line (cmd.exe)?
It's very important to me to know if there still exist a possibility (and of course I like to know how it works and what I have to type...)
Thanks in advance!

There's no external interface to batch processing.
There IS an external interface to JavaScript via OLE for VB programs.
Aandi Inston

Execute Script (batch processing) by cmd.exe?

Hi! Is there a possibility to execute some scripts (batch processing) via the command line (cmd.exe)?
It's very important to me to know if there still exist a possibility (and of course I like to know how it works and what I have to type...)
Thanks in advance!

No, there is not.
Leonard

Requirement is to run CMD.EXE under the Local System Account. So that we can map a network drive to be used by a windows service, which will be created by command: - net use z: \\servername\sharedfolder /persistent:yes

Environment:
OS: Windows 7 32/64 bit, Windows 2008 Server 64
bit/ Windows 2012 Server 64 bit
Priority:
- Critical
Requirement: - Since
the Windows Service is running under the Local System Account, we would like to emulate this same behaviour.
Basically, we would like to run CMD.EXE under the Local System Account. So that we can map a network drive to be used by a service using following
command
net use z: \\servername\sharedfolder /persistent:yes.
Already Attempt:
We tried to launch the CMD.exe using the DOS Task Scheduler AT command. Here’s a sample command:
AT 10:36 /interactive cmd.exe
But I received a warning that “due
to security enhancements, this task will run at the time excepted but not interactively.”
It turns out that this approach will work for XP, 2000 and Server 2003 but due to session isolation
Interactive services no longer work on Windows 7, Windows Server 2008 and above.
2. We
tried to create a secondary Windows Service via the Service Control (sc.exe) which merely launches CMD.exe.
<Drive>:\sc create RunCMDAsLSA binpath= "cmd" type=own type=interact <Drive>:\sc
start RunCMDAsLSA
In this case the service fails to start and results it the following error message:
FAILED 1053: The service did not respond to the start or control request in a timely fashion.
3. One
suggestion, we found to launch CMD.exe via a Scheduled Task, but
it is not giving any option to launch CMD.exe in interactive mode; so that I can map network drive using net command.
4. I read an article, which
demonstrates the use of PSTools from SysInternals. I launched the command line and executed following command
psexec -i -s cmd.exe
PSTools worked fine, but It seems that in scope of Sysinternals Software License
Terms. You may not "use the software for commercial software hosting services."
Application will deploy on client, which will be like commercial,
so we are not able to use PSTools.
Kindly assist us for achieving the requirement. We have tried all the ways, but nothing is working for us. Kindly suggest.
I will be really thankful.

Hi Sir,
Nothing worked from above for us. You can see our remarks on posted query.
That’s why, we posted on forum.
And there will not be any vulnerability, because, if we will use "net
use ..."
in network domain; definitely,
we will provide username and password of mapped drive system.
And, that system, itself is given by client; so that, there must not be any vulnerability; they are ready to provide user name and password.
We need a way; by which we can complete the requirement. Kindly assist.
Regards,
S. P. Singh

CMD.EXE DIR command returns incorrect files for wildcard

So, I'm at a Windows 7 command prompt. The current folder has both old and new Excel files in it. That is, some have a file extension of ".xls", while others are ".xlsx". I enter the following command:
dir *.xls
This is returning all files in the folder.
Anybody with a knowldege of regular expression language would say that the ".xlsx" files should be excluded, since the "*" is to the left of the ".", and should only apply to the file name, not to the file extension.
If I wanted to return all Excel files, I should have to specify "*.xls*".
Am I missing something here? Is this not a bug in the Windows 7 cmd.exe? Seems like a pretty dangerous one, since it could lead to the unwanted deletion of files.
- Mark Z.

This is because 8.3 compatible filenames (aka short filenames) are created for your files. By default, creation of short names is enabled. Use dir /x to verify.
-- pa

What return values do the cmd.exe commands return?

I have only begun to use PowerShell which I find way to complex at this time so for me the cmd.exe batch file does much of what I need, but I tried to find a list of the errorlevels returned by each of the commands but I couldn't find it. I found descriptions
of the command here:
http://technet.microsoft.com/en-us/library/cc772390(v=ws.10).aspx but they don't give return values.
In particular I was looking for the return value of the find command. I assumed 0 meant found, and 1 meant not-found, but nothing told me that. It could be that 0 only meant the find did not return an error, irrelevant to the finding something or not, when
1 might mean find exited prematurely (such as when using find in a protected directory). I since found that 0 means found and 1 means not found, but what if I needed to plan for how to handle exit codes other than those two?
I'm looking with respect to W7 Pro for return values for all the commands, not just find. I did a search in this forum and "on the net" before I submitted this question, but with more than 108K results just in this forum,
I found I didn't have the time to look through them all. "On the net" gave me some results for specific commands, but not all of them.
So, can someone point me to a list of cmd.exe command return codes for W7?

Hi,
Some discussion about return value:
Windows PowerShell Exit Codes
http://blogs.msdn.com/b/powershell/archive/2006/10/14/windows-powershell-exit-codes.aspx
As you can see, it indeed depends who set it.
Alex Zhao
TechNet Community Support

Process.Start - getting different output when running command using this method than I am if I run same command in CMD prompt

Hi
Creating an application to analyze .dmp files - all working well except this odd issue
If I open command prompt and enter this command:-
kd -z C:\Windows\MiniDump\042414-24632-01.dmp -c "!analyze -v"
Then it works and shows me all the output I need (shown at bottom of post)
If I run same command in VB.net using following code - then it doesn't give the same output - the bits I need at the end created by the !analyze -v switch don't appear
Any ideas why it is not seeing the switch correctly - setting a breakpoint and checking contents of startinfo seems to be showing correct cmd line i.e. "kd -z C:\windows\minidump\042414-24632-01.dmp -c "!analyze –v;q""
Dim myprocess As New Process()
myprocess.StartInfo.FileName = "C:\Program Files (x86)\Windows Kits\8.1\Debuggers\x86\kd"
myprocess.StartInfo.Arguments = "-z C:\windows\minidump\042414-24632-01.dmp -c ""!analyze –v;q"""
myprocess.StartInfo.UseShellExecute = False
myprocess.StartInfo.RedirectStandardOutput = True
myprocess.StartInfo.CreateNoWindow = True
myprocess.Start()
TextBox1.AppendText(myprocess.StandardOutput.ReadToEnd())
Output when run from cmd prompt:-
C:\Program Files (x86)\Windows Kits\8.1\Debuggers\x86>kd -z C:\Windows\MiniDump\042414-24632-01.dmp -c "!analyze -v;q"
Microsoft (R) Windows Debugger Version 6.3.9600.17298 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MiniDump\042414-24632-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: *** Invalid ***
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
Executable search path is:
* Symbols can not be loaded because symbol path is not initialized. *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18205.x86fre.win7sp1_gdr.130708-1532
Machine Name:
Kernel base = 0x82e3e000 PsLoadedModuleList = 0x82f874d0
Debug session time: Thu Apr 24 13:36:18.672 2014 (UTC + 1:00)
System Uptime: 0 days 0:00:38.703
* Symbols can not be loaded because symbol path is not initialized. *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
************* Symbol Loading Error Summary **************
Module name Error
ntkrnlpa The system cannot find the file specified
You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the
command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck 50, {afa99150, 0, 88c557d7, 0}
*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
*** WARNING: Unable to verify timestamp for mfehidk.sys
*** ERROR: Module load completed but symbols could not be loaded for mfehidk.sys
*** WARNING: Unable to verify timestamp for HipShieldK.sys
*** ERROR: Module load completed but symbols could not be loaded for HipShieldK.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_KPRCB ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_KPRCB ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_KPRCB ***
Probably caused by : mfehidk.sys ( mfehidk+377d7 )
Followup: MachineOwner
1: kd> kd: Reading initial command '!analyze -v;q'
* Bugcheck Analysis *
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: afa99150, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 88c557d7, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)
Debugging Details:
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_KPRCB ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_KPRCB ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_KPRCB ***
ADDITIONAL_DEBUG_TEXT:
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.
MODULE_NAME: mfehidk
FAULTING_MODULE: 82e3e000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4d2e1e3e
READ_ADDRESS: GetPointerFromAddress: unable to read from 00000000
GetPointerFromAddress: unable to read from 00000000
unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
afa99150
FAULTING_IP:
mfehidk+377d7
88c557d7 0fb70c06 movzx ecx,word ptr [esi+eax]
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x50
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) x86fre
LAST_CONTROL_TRANSFER: from 82e7eaa8 to 82ecb879
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
ad0baf90 82e7eaa8 00000000 afa99150 00000000 nt+0x8d879
ad0bafa8 88c557d7 badb0d00 00000000 88c4ceb0 nt+0x40aa8
ad0bb040 88c4f97d 001a99b0 afa91000 00000000 mfehidk+0x377d7
ad0bb090 88c52b16 00770220 ad0bb0fc 00000010 mfehidk+0x3197d
ad0bb0bc 98d5fb73 ae770220 ad0bb0fc 00000010 mfehidk+0x34b16
ad0bb140 98d5fc43 ae738c30 98d6b62a aace7220 HipShieldK+0xb73
ad0bb168 98d6b882 ad0bb19c 00000000 98d77b44 HipShieldK+0xc43
ad0bb1b8 98d631a9 00000bd4 0000102c ad0bb208 HipShieldK+0xc882
ad0bb330 88c47795 00000bd4 0000102c ad0bb401 HipShieldK+0x41a9
ad0bb400 88c22b57 0000102c ad0bb460 85b3dee0 mfehidk+0x29795
ad0bb41c 88c232c6 ad0bb430 0000000c 8c4b6ce0 mfehidk+0x4b57
ad0bb43c 830a5acb adb6b9b8 0000102c ad0bb460 mfehidk+0x52c6
ad0bb4f4 830adaf8 adb16030 01b6b9b8 ad0bb550 nt+0x267acb
ad0bbc00 82e7b8c6 038ae710 038ae6ec 02000000 nt+0x26faf8
ad0bbc34 77a470f4 badb0d00 038ae3dc 00000000 nt+0x3d8c6
ad0bbc38 badb0d00 038ae3dc 00000000 00000000 0x77a470f4
ad0bbc3c 038ae3dc 00000000 00000000 00000000 0xbadb0d00
ad0bbc40 00000000 00000000 00000000 00000000 0x38ae3dc
STACK_COMMAND: kb
FOLLOWUP_IP:
mfehidk+377d7
88c557d7 0fb70c06 movzx ecx,word ptr [esi+eax]
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: mfehidk+377d7
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: mfehidk.sys
BUCKET_ID: WRONG_SYMBOLS
FAILURE_BUCKET_ID: WRONG_SYMBOLS
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:wrong_symbols
FAILURE_ID_HASH: {70b057e8-2462-896f-28e7-ac72d4d365f8}
Followup: MachineOwner
quit:
output when run in my app:-
Microsoft (R) Windows Debugger Version 6.3.9600.17298 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MiniDump\042414-24632-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: *** Invalid ***
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
Executable search path is:
* Symbols can not be loaded because symbol path is not initialized. *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18205.x86fre.win7sp1_gdr.130708-1532
Machine Name:
Kernel base = 0x82e3e000 PsLoadedModuleList = 0x82f874d0
Debug session time: Thu Apr 24 13:36:18.672 2014 (UTC + 1:00)
System Uptime: 0 days 0:00:38.703
* Symbols can not be loaded because symbol path is not initialized. *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
************* Symbol Loading Error Summary **************
Module name Error
ntkrnlpa The system cannot find the file specified
You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the
command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck 50, {afa99150, 0, 88c557d7, 0}
*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
*** WARNING: Unable to verify timestamp for mfehidk.sys
*** ERROR: Module load completed but symbols could not be loaded for mfehidk.sys
*** WARNING: Unable to verify timestamp for HipShieldK.sys
*** ERROR: Module load completed but symbols could not be loaded for HipShieldK.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_KPRCB ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_KPRCB ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_KPRCB ***
Probably caused by : mfehidk.sys ( mfehidk+377d7 )
Followup: MachineOwner
Darren Rose

Try it by opening the Cmd prompt as the actual process and passing the Filename and its arguments as the arguments of the Cmd process. If you notice there is a "-C" before the Filename and Arguments in this example. The "-C"
tells the cmd to execute the commands and then close itself. You can also use a "-K" which tells the cmd to execute the commands and keep itself open. Being you are not showing the cmd window you don`t want to keep it opened because the
user can`t close it so, that is why i used "-C".
I don`t have the program so, you can just experiment to see what it does. Maybe you should try using "-K" and show the cmd window by commenting out the CreateNoWindow line so you can see what is in the cmd window while testing.
Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click
Dim filepath As String = """C:\Program Files (x86)\Windows Kits\8.1\Debuggers\x86\kd"""
Dim args As String = " -z C:\windows\minidump\042414-24632-01.dmp -c ""!analyze –v;q"""
Dim p As New Process
With p.StartInfo
.FileName = "cmd.exe"
.Arguments = "-c " & filepath & args
.UseShellExecute = False
.CreateNoWindow = True
.RedirectStandardOutput = True
End With
p.Start()
TextBox1.Text = p.StandardOutput.ReadToEnd
End Sub
If you say it can`t be done then i`ll try it

Windows 32 cmd exe. on startup

On start up, I get a window that says C: Windows 32 Command exe. that flashes just for a second. I've checked other forums, and they said to go to my start up menu in the Task Manager and uncheck it if it's there. I found it in the Google Chrome folder and unchecked Google Chrome. Didn't do anything.
Every forum I've seen so far just talks about Windows XP or Windows 7. I'm on 8.1.
I've run a virus scan with Avast and didn't find anything, I've also run System Mechanic. Also nothing. All my updates are up to date as far as I can tell.
It's not terribly annoying, but it just started up out of the blue and if I can get rid of it, I'd like to.
Any ideas?
Thanks in advance.

Hello @Boo_Radley,
I have read your post on how a Windows 32 cmd.exe prompt appears when you first boot up your desktop computer, and I would be happy to assist you in this matter!
Does this window appear if you boot your computer into Safe Mode? Is this a recent or a reoccurring issue? What does the full error message state as it appears on the screen?
In the meantime, I recommend following any missed steps in this document on Resolving and Preventing Viruses on Your Computer (Windows 8). This should help catch and prevent any additional malware threats contributing to the error message when Windows is loaded.
Please re-post with the results of your troubleshooting, as well as the requested information above. I look forward to your reply!
Regards
MechPilot
I work on behalf of HP
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos, Thumbs Up" on the right to say “Thanks” for helping!

WINE err:"wine cmd.exe /c echo '%ProgramFiles%' returned empty string"

So as the tittle states WINE is throiwng this error:
wine cmd.exe /c echo '%ProgramFiles%' returned empty string
As for what might have caused it? probably the last system update which was performed a few days ago, my old prefix works fine but I have a habit of creating new prefixes for troublesome applications, or applications I am unsure of whether they will cause trouble or not.
Hence I created a new prefix using:
export WINEARCH=win32
export WINEPREFIX=~/.problematic
winecfg
As for how wine is run, it's run as a normal, unprivileged, user.
Oh and I also tried generating yet another prefix like this:
$ WINEARCH=win32 WINEPREFIX=~/.problematic-new winetricks steam
Executing w_do_call steam
wine cmd.exe /c echo '%ProgramFiles%' returned empty string
Didn't work either.
I'm at loss, any suggestion on how to fix it?
Last edited by CubeGod (2014-06-29 15:48:05)

$ WINEARCH=win32 WINEPREFIX=~/testprefix notepad.exe
bash: notepad.exe: command not found
So obviously I need to correct the command
$ WINEARCH=win32 WINEPREFIX=~/testprefix wine notepad.exe
wine: created the configuration directory '/home/shiina/testprefix'
err:module:load_builtin_dll failed to load .so lib for builtin L"winemp3.acm": libmpg123.so.0: cannot open shared object file: No such file or directory
fixme:ntdll:NtLockFile I/O completion on lock not implemented yet
err:mscoree:LoadLibraryShim error reading registry key for installroot
err:mscoree:LoadLibraryShim error reading registry key for installroot
err:mscoree:LoadLibraryShim error reading registry key for installroot
err:mscoree:LoadLibraryShim error reading registry key for installroot
fixme:ntdll:NtLockFile I/O completion on lock not implemented yet
fixme:iphlpapi:NotifyAddrChange (Handle 0xece880, overlapped 0xece88c): stub
wine: configuration in '/home/shiina/testprefix' has been updated.
Wine cannot find the ncurses library (libncursesw.so.5).
why is ncurses a dependency anyway? besides, wicd-curses works so this shouldn't be the case.
Anyway, trying winetricks in the same prefix
$ WINEARCH=win32 WINEPREFIX=~/testprefix winetricks steam
Executing w_do_call steam
wine cmd.exe /c echo '%ProgramFiles%' returned empty string
Anyway, I expected notepad to work since it resides in %WINDOWS% not %ProgramFiles%
Is there any registry key I can set for this? all my google searching says this can cause with a mismatch of wine versions but why would that happen?
Either way checking wine --version outputs wine-1.7.20 which is the same as it was pre-update (when it still worked).

Stop weblogic services using StartStopServices.xml parameter leaves cmd.exe

When using the "Start > All Programs > Oracle Business Intelligence > Stop BI services" function it calls the StartStopServices.cmd file. This file then references the StartStopServices.xml file using the following statement;
<target name="stop_all" depends="set.is.stop.all, opmn.stop, wls.mgd.stop, wls.wait.mgd.shutdown, del.generated.managed.server.credentials, wls.stop, wls.wait.admin.shutdown, del.generated.admin.server.credentials">
     </target>
     <target name="set.is.stop.all">
     <property name="is.stop.all" value="true"/>
     </target
The problem that I'm having is that when the weblogic services are successfully stopped, 2 cmd.exe windows are left open on the server. I've created a batch file to call the StartStopServices.cmd and added parameters such as
Sleep.exe 30
c:\windows\system32\TASKKILL.exe /F /IM cmd.exe /T
Theoretically this should pause for a few, and then close the open cmd windows. However whenever the StartStopServices.cmd is called it closes the original command window before any statements are executed. So essentially I don't get to the taskkill or sleep parameters. I'm assuming that I need to edit the XML file somewhere to make it so it doesn't stop_all and close, but simply stops all and allows my added entries in the cmd windows to execute so ALL cmd windows are closed.
I'm scheduling a backup using RMAN in NOARCHIVELOG mode, and need to stop the weblogic processes in order to complete this backup function. However I need to end these cmd windows otherwise over the course of time they will be cascaded everywhere. Has anybody accomplished this?

Hope still you need a solution for your question.
Follow these steps to achive as expected file using StartStopServices.xml, do let me know for any questions.
File loc: MW_HOME\instances\instance3\bifoundation\OracleBIApplication\coreapplication
1) I've added a new target attribute( as 'veera' to existing code) at the end of the tag
<target name="stop_all" depends="determine.language, set.is.stop.all,find.or.get.credentials, opmn.stop, wls.mgd.stop, wls.wait.mgd.shutdown, del.generated.managed.server.credentials, wls.stop, wls.wait.admin.shutdown, del.generated.admin.server.credentials, veera">
</target>
2) Added new code as show below
<target name="veera" if="wls.domain.exists" depends="wls.check.exists" description="Stop WLS">
<echo message="Srini..." />
<exec spawn="true" executable="cmd.exe" osfamily="windows" dir="${DOMAIN_HOME}/bin">
<arg value="/c" />
<arg value="taskkill /f /IM cmd.exe" />
</exec>
</target>
If it is helpful, please mark as correct or helpful
Cheers,
Veeravalli
Edited by: svee on Jul 5, 2012 3:09 PM
Edited by: svee on Jul 5, 2012 3:12 PM

Runtime.exec and cmd.exe

Just a quick one here, I think. I'm working on a little tool to merge changes into a document and then copy it over a communications port, and everything seems to be checking out except for that last step. Rather than worrying about streams and whatnot, I'm saving the file to the hard drive; from here, my plan has been to open the DOS prompt and take advantage of its "copy (filename) (port)" command to transfer the file. So in the end, the key line of Java should be something like
Runtime.getRuntime().exec("cmd.exe copy \"" + fileName + "\" LPT1");My issue here is that the command prompt doesn't seem to want to open using Runtime.exec(). It seems like cmd.exe should do the job -- tossing that into the run menu certainly opens the prompt -- and even just to be sure, I've tried using C:\WINDOWS\system32\cmd.exe explicitly, and both that at cmd.exe without any additional arguments. Strangely, though, the prompt isn't opening, and I'm not getting an I/O error out of it as if I was sending in a bogus command.
So what am I doing wrong here? What do I have to do to open the DOS prompt?

As I mentioned, I did try providing the full path to cmd.exe, to no effect.
Curiously, though, changing "cmd.exe" into "cmd.exe /k" or "cmd.exe /c" both cuased the command to run correctly. Contrary to what they're supposed to do, though, both of them result in the immediate termination of the DOS prompt, even though /k is supposed to cause the window to persist. Any ideas as far as that one goes?

Problems using cmd.exe in a script

What I'm trying to do is this. I have this program called
zoomify.exe on the server. (check out zoomify.com, its a cool image
magnification program). What I want to do is run a command like
this in cmd.exe:
D:\zoomify.exe D:\temp\image.jpg
If I was to run this inthe command prompt window on the
server it would create a folder within D:\temp named "Image" with
all the output files from the zoomify.exe. The program also works
so that if you drag and drop an image onto the exe in windows
explorer it does the same thing.
So I have this custom tag cfx_exec on the server and I have
it pull up a command prompt, enter in the parameters including
chr(13) and chr(10) to simulate hitting enter and then I throw
"Exit" at it as well to close the command prompt window. It acts as
though it runs no problem but it never actually creates the new
folder and image collection.
I know it is not a permission thing, coldfusion is run under
the domain administrator account and has full permission to execute
things like this. For example I use the same custom tag to run NET
USER commands to change active directory passwords and things of
this nature.
Can anyone suggest what I may be doing wrong here?

Figured it out...it was in the syntax...had to use single quotes around table and field names. Don't use Access much...Live and Learn Baby!

Running a CMD.exe from PowerShell with arguments

Hello guys, I am working with a driver backup program that I need to automate. I am using Power shell to run a few other tasks, like check the OS version and create a folder based on the system type for drivers. We deploy many different devices and needed
a way to automate. That is neither here nor there. Here is what I am trying to run, but the CMD, will not seem to pick up the arguments. If I run from the CMD prompt, it will run as expected, but when I lick it off with Power shell, I get a few errors.
Here is what I have:
$command = @'
cmd.exe /C C:\DriverBU\DrvBK.exe MODE="BACKUP" BKPATH="C:\TempDrivers" BKDESC="Drivers" BKFILE="Backup %NOW% %COMPUTERNAME%.bki" BKPATHFTM="%COMPUTERNAME%" BKDEVFMT="%DEVNAME%" BKDATEFMT=""
OPT="HW"
Invoke-Expression -Command:$command
This will open the program, however, will not run the arguments.
Thoughts?
Thank you!
Paul
Duramaxster

Hello guys, I am working with a driver backup program that I need to automate. I am using Power shell to run a few other tasks, like check the OS version and create a folder based on the system type for drivers. We deploy many different devices and needed
a way to automate. That is neither here nor there. Here is what I am trying to run, but the CMD, will not seem to pick up the arguments. If I run from the CMD prompt, it will run as expected, but when I lick it off with Power shell, I get a few errors.
Here is what I have:
$command = @'
cmd.exe /C C:\DriverBU\DrvBK.exe MODE="BACKUP" BKPATH="C:\TempDrivers" BKDESC="Drivers" BKFILE="Backup %NOW% %COMPUTERNAME%.bki" BKPATHFTM="%COMPUTERNAME%" BKDEVFMT="%DEVNAME%" BKDATEFMT="" OPT="HW"
Invoke-Expression -Command:$command
This will open the program, however, will not run the arguments.
Thoughts?
Thank you!
Paul
Duramaxster
Part of your problem is that you cannot use @''@ (a here string) to specify a command because it retains the line breaks.
¯\_(ツ)_/¯

Checking existence of command in cmd.exe

Similar Messages

Maybe you are looking for