MikeyChris
Extraordinary Member
- Joined
- Jan 2, 2012
- Messages
- 40
- Thread Author
-
- #1
OK, before I start, I admit this is old school. That said, we often fall back on things that have worked in the past. I recently installed Win 10 Pro 64 bit and am getting familiar with it. I was wondering how many different .msc commands there were, so I thought I could use the following command to find out (using a command line DIR command, issued from c:\, inside powershell as admin):
dir *.msc /s > mscfiles.txt
When I ran that command and argument, I got this in reply from WIndows:
dir : Second path fragment must not be a drive or UNC name.
Paramater name: path2
At line:1 char:1
+ dir *.msc /s >MSCFile.txt
+ ~~~~~~~~~~~~~~~~~~~
+ CategoryInfo: InvalidArguement (bunch of stuff here)
+ FullyQualifiedErrorID: DirArguementError (more stuff here)
When I ran the same command sans the redirection to the text file (i.e. dir *.msc /s) , it ran fine, but the text blew by too fast to read, of course. Running the PAUSE switch (dir *.msc /s /p) did yield human-readable text (in screen sized chunks), but I want an actual list.
Soooo what am I doing wrong? Is redirection to a text file not supported by the DIR command any more? If I drop the space between msc and the switch (dir *.msc/s> mscfiles.txt) the command runs with no error, but the text file is a zero byte file with no list of msc files (remember the same command sans the redirection did indeed scroll all msc files through at light speed). Any ideas are appreciated.
dir *.msc /s > mscfiles.txt
When I ran that command and argument, I got this in reply from WIndows:
dir : Second path fragment must not be a drive or UNC name.
Paramater name: path2
At line:1 char:1
+ dir *.msc /s >MSCFile.txt
+ ~~~~~~~~~~~~~~~~~~~
+ CategoryInfo: InvalidArguement (bunch of stuff here)
+ FullyQualifiedErrorID: DirArguementError (more stuff here)
When I ran the same command sans the redirection to the text file (i.e. dir *.msc /s) , it ran fine, but the text blew by too fast to read, of course. Running the PAUSE switch (dir *.msc /s /p) did yield human-readable text (in screen sized chunks), but I want an actual list.
Soooo what am I doing wrong? Is redirection to a text file not supported by the DIR command any more? If I drop the space between msc and the switch (dir *.msc/s> mscfiles.txt) the command runs with no error, but the text file is a zero byte file with no list of msc files (remember the same command sans the redirection did indeed scroll all msc files through at light speed). Any ideas are appreciated.