Two things of note in your last post (if accurate) which were not obvious from your prior posts: (1) The message does not appear when you open the 16-bit shell (command.com) (2) When you open the 32-bit shell (cmd.exe) the message appears.after. the shell opens, not before. QuoteIf a file command.bat does not exist, is there a way I can reconfigure Quotethe way command prompt starts in Windows or do I need to reinstall QuoteWindows to make command prompt work without the command.bat file? As I don't have Vista installed, I'm averse to making suggestions re configuring that OS version. I don't know why you're obsessing about this. It's an informational message only. The command prompts are working.
Aug 29, 2019 The first method you can use to open the command prompt as a Windows 10 administrator is to use the Power User Menu. This is a hidden menu that appears near the Start menu. You can open it by using the key combination Windows + X. Among the options listed, you should see Command Prompt (administrator). Just click it to run it. HOW TO FIX Administrator: X:windowssystem32cmd.exe How to Repair Administrator: X:windows.
If you want to go to all the trouble of reinstalling Windows and all of your software, just to eliminate an innocuous message, it's your dime/time. If it were happening on my PC and I couldn't track down the source, I would give it what it wants. Create a simple command.bat file in C:windowssystem32 such as: @echo off rem Dummy file to appease Windows and let me sleep at night The message should go away when you open a command prompt. As previously noted by Sheng Jiang, this has nothing to do with Visual C and therefore is off-topic in this forum. If you need to pursue it further, I suggest you find a Vista support forum or newsgroup. Quotedisplays the message: 'C:Windowssystem32command.bat' is not recognized' QuoteI have command.exe, but I am not sure if the path is corrupted Quoteelse must be corrupted or something. Looks like your grammar is corrupted, or at least fractured.;-) Where did you see command.exe?
AFAIK, neither command.bat nor command.exe are part of a normal Windows installation. I don't know what they use in Vista, but under XP and prior it has always been command.com (not.exe) and is in the c:windowssystem32 directory. Also, command.com is a 16-bit legacy shell - Win32 releases since at least NT have used the cmd.exe shell.
I cannot find anywhere the command.bat file it is referenced either, but I guess my computer is trying to run this file once command prompt opens. But when I checked to see where it was on my computer, I couldn't find a command.bat on there either. Command prompt is going to the right location to open in my computer, but I am guessing it is referencing the wrong file once it opens or something. I am not sure if my computer needs this command.bat file to operate command prompt, or if it needs a different file and I am not sure how to change the file command prompt uses once it opens? Tobymacfan - You need to articulate your problem much more clearly. You are using too general a description for anyone to clearly understand what you are doing. QuoteI am relatively new at Visual Studios, and I am trying to get it to work Quoteon my vista.
Back up a bit, and tell us how far you have gotten with installing VS and which version you are installing. Can you open the VS IDE?
Quoteit is affecting command prompt every time I open it Every time you open WHAT? The command prompt or VS? First, clarify.how. you are trying to open the command prompt window. Are you trying to do it from inside the VS IDE? For example, by clicking on the menu item: Tools-Visual Studio 2008 Command Prompt Or are you trying to start it some other way? See if you can open a console window this way: Click on the Start menu on the Windows task bar.
Click on 'Run'. In the dialog that opens type in cmd and then click on OK. A console window should open. Display your environment variables by typing in this: set more Look down the list for the comspec variable and tell us what it says. It should look like this (assuming Vista hasn't changed): ComSpec=C:WINDOWSsystem32cmd.exe.Copy.
from the screen the comspec line and.paste. it into a post here. Do NOT type it in manually. Use the Windows clipboard to show.exactly. what is there. The symptoms you describe indicate that something is not configured correctly on your system.
It clearly is not unique to or limited to VC or VS. A few observations on the info you have supplied in your last post: QuoteWhen I create a project and try to execute the code the program compiles Quoteand tells me there are build errors. QuoteIf I click to continue it runs the programs No, it can't do that. If there are build errors there will be no program to run. QuoteWhen I click on 'run' from the start menu, it does not allow me to copy Quoteand paste the text. I have no idea what you're talking about. When you select 'Run' from the Start Menu it should open a dialog with an edit box for you to type the name of the program you want to run.
Quotebut it displays the message StartQuote Microsoft (R) Windows DOS (C)Copyright Microsoft Corp 1990-2001 C when I open command prompt from the start menu. Quoteit does not allow me to copy and paste the text into the post. How are you trying to copy to the clipboard? You should be using the System Menu at the left of the title bar of the console window. Click on the System Menu, select Edit, then Mark.
Move the flashing cursor to the start of the text to be copied, hold the shift key down and move to the end of the selection then press Enter. Or just choose Select All and press Enter. You should also be able to right-click anywhere on the console window to get the Edit menu to pop up. Use the Clipboard Viewer to confirm that the copy succeeded. QuoteI am just wondering why my command prompt is giving me this message Quotethat the batch file is not recognized as an internal or external Quotecommand, operable program or batch file. Because no such file exists. QuoteI feel that this problem is independent of VS, but is showing up when QuoteVS executes code.
That appears to be correct. It shows up whenever you try to open a console window. Something is not configured correctly in your Windows installation. Check your search path (and then your entire hard disk) for a file named cmd.bat and if found examine its contents.
If such a file exists, for example in windowssystem32, it may get executed whenever you run 'cmd' instead of or before cmd.exe gets executed. To demonstrate, if I create a file in windowssystem32 named cmd.bat and I put these lines in it: @echo off call C:Windowssystem32command.bat cmd.exe then whenever I run cmd (no extension) I will see this output on the screen: C:cmd 'C:Windowssystem32command.bat' is not recognized as an internal or external command, operable program or batch file. Microsoft Windows XP Version 5.1.2600 (C) Copyright 1985-2001 Microsoft Corp. C: In short, if someone or something has created a batch file named cmd.bat which was intended to first call a file named command.bat and then invoke the 32-bit shell, cmd.exe, you will get the results you are seeing. (Assuming that command.bat does not now exist.) - Wayne. Two things of note in your last post (if accurate) which were not obvious from your prior posts: (1) The message does not appear when you open the 16-bit shell (command.com) (2) When you open the 32-bit shell (cmd.exe) the message appears.after.
the shell opens, not before. QuoteIf a file command.bat does not exist, is there a way I can reconfigure Quotethe way command prompt starts in Windows or do I need to reinstall QuoteWindows to make command prompt work without the command.bat file?
As I don't have Vista installed, I'm averse to making suggestions re configuring that OS version. I don't know why you're obsessing about this.
It's an informational message only. The command prompts are working. If you want to go to all the trouble of reinstalling Windows and all of your software, just to eliminate an innocuous message, it's your dime/time. If it were happening on my PC and I couldn't track down the source, I would give it what it wants. Create a simple command.bat file in C:windowssystem32 such as: @echo off rem Dummy file to appease Windows and let me sleep at night The message should go away when you open a command prompt. As previously noted by Sheng Jiang, this has nothing to do with Visual C and therefore is off-topic in this forum.
If you need to pursue it further, I suggest you find a Vista support forum or newsgroup.
After the repair bootable has been created, boot from the USB and arrive at the Windows set up screen. From here, you will press the shift+F10 to open up the command prompt. This prompt has administrative privileges and will allow you to access the files in the already installed Windows OS.Note: Please make sure that UEFI secure boot is disabled, if needed please change the boot sequence.Now from here, you have to find the drive letter of the installed OS, normally it remains the C: drive, but every once in a while this changes. You can use the dir command to search through each letter and see if the directory displays. However, you can also use the diskpart utility with the command list volume to get a sense of the volumes and the letters attached.X:Sources dir a:orX:SourcesdiskpartDISKPART list volumeAfter you find the operating system, you then want to copy over the sticky keys file as a backup, then replace the sticky keys file in System32 with the command prompt, this will allow you to access the command prompt from the login screen.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
March 2023
Categories |