DosTips.com

You need to provide more details, including, but not limited to: Are we to assume that there will only ever be files with the .RAW and .JPG extensions in that directory? Will there ever be files with a .RAW or .JPG extension which does not have a matching extension of the other type? You are after a...

Or perhaps just this in the Command Prompt:Which should list the full filename, the line number, and then the line containing the case insensitive string Echo of every .bat file on the Z: drive.

TASKKILL /F /FI "WINDOWTITLE EQ "%0"" would work if the i would not add "- file1" and so on. But if I add * to this command it doesn't work: TASKKILL /F /FI "WINDOWTITLE EQ "%0" *" Where is my mistake or does it not work this way? Untested, but have you tried including the wildcard within the doubl...

My script runs correctly in Windows 10. Okay, let me put this to you in a different way; your script does not work correctly in Windows 10 x64, if it is run in a 32-bit cmd.exe instance. It only works correctly in a 64-bit cmd.exe instance, on a Windows x64 OS, and a 32-bit cmd.exe instance on a Wi...

There were a couple of tricky things here: <snip /> <snip /> if "%processor_architecture%"=="AMD64" set "reg_value=%reg_value%4" set "reg_query=reg query "%reg_key%" /v %reg_value%" for /f "tokens=3" %%A in ('%reg_query%') do set "key=%%A" <snip /> I'd advise that you take account of my previous po...

What is strange is that PROCESSOR_ARCHITECTURE=x86 but it really is 64-bit computer. And Shadow tests if "%processor_architecture%"=="AMD64" but SET P shows PROCESSOR_ARCHITECTURE=x86 PROCESSOR_ARCHITEW6432=AMD64 So maybe PROCESSOR_ARCHITEW6432 should be tested and not PROCESSOR_ARCHITECTURE (I don...

Compo's version works. I will check both of them on XP later today. Just to clarify my body text: Here's an example, now tested successfully only on Windows 2000, and Windows 10 x64 in both 32-bit and 64-bit modes) <snip /> The only thing, I'm unsure about is whether the Windows XP x64, version of ...

Here's an example, now tested successfully only on Windows 2000, and Windows 10 x64 in both 32-bit and 64-bit modes) @Echo Off SetLocal EnableExtensions EnableDelayedExpansion Set "sKey=HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" Set PROCESSOR_ARCHITE | %SystemRoot%\System32\find.exe "64" 1>N...

Ignoring the 'maxbytesize', which seems to be unused, perhaps something like this is what you want: @Echo Off SetLocal EnableExtensions DisableDelayedExpansion Set "i=0" ( For /F "EOL=? Delims=" %%G In ('Dir /B /A:-D 2^>NUL') Do ( Set /A i += 1, # = %%~zG SetLocal EnableDelayedExpansion For /F "Toke...

IcarusLives wrote: ↑

14 Apr 2021 11:41

He's unable to access cmd.exe

I'm sorry IcarusLives, but I clearly read the opening post, where it was stated that there was a copy of cmd.exe in the x86 application location, \SysWOW64.

Both sfc.exe and dism.exe also have x86 versions in \SysWOW64, hence my advice.

Have you tries the basics, as administrator, before resorting to a System Restore?

miskox wrote: ↑

12 Apr 2021 15:36

I am sure some of you would be more efficient (Aacini, aGerman...). This is not a competition... (yet).

If you want one of those two to assist you, send them a personal message, instead of telling everyone else that you feel they have less worth to you, and demotivating them.

Please don't try to disrespect me, I was very clear in my opening statement of my last response. You've completely changed your input to include both spaces and doublequotes, and would obviously not therefore, be splitting the string on spaces, would you? You'd be splitting on a doublequote space do...

If your input files are all unquoted, and do not contain spaces or other potentially poison characters, then you could probably simply use something like this:

There's some interesting observations made in the following StackOverflow post, which may potentially assist you.