|
ATTN ShadowSystems and MSDOS Query | by Klaranth | 2011-09-03 07:37:36 |
| I believe so, yes. |
by ShadowSystems |
2011-09-03 07:50:24 |
"Dir *.* /s" will take a directory listing of all files, through all subdirectories below the directory in which the command was used.
If used from root, it will list the entire drive's contents.
Using the > pipe to send the output to a text file would dump the results into said text file.
But even if I specify the Drive:Path where to *save* that file, my system believes it is not bound by such niceties and will put it whereever it damn-well pleases.
I have called such files "f4er.txt" just to make them findable by Windows Search, to no avail.
I run a Terminal Window, go to root, and do a manual "dir f4er.txt /s" and it *still* can't find the file.
So, if it's being created, the system can't find it afterwards, and if it's NOT being created, it's not telling me why.
Like I've said before, my system is Possessed.
I'd call the Pope, but he's got my number on BLOCK for obvious reasons.
=-)P |
|
[ Reply ] |
|
if you go into the directory you want | by Klaranth | 2011-09-03 07:59:28 |
|
In Theory, yes. In Practice, No. | by ShadowSystems | 2011-09-03 08:16:09 |
|
I've observed behavior in XP where | by tonyz | 2011-09-03 08:30:50 |
|
I only *wish* that were true with Vista. =-( | by ShadowSystems | 2011-09-03 09:13:47 |
|
WIN+R is probably your problem. | by frostbait | 2011-09-03 09:45:17 |
|
Ah, sorry. A miscom on my part... | by ShadowSystems | 2011-09-03 14:27:18 |
|
S-S: DON'T type "command" JUST "c m d" | by wwill | 2011-09-03 14:37:21 |
|
err? command prompts do support long file names | by Freakazoid | 2011-09-03 09:56:00 |
|
Yes and no actually. | by Sharku | 2011-09-03 10:18:43 |
|
Yup...heed that, ye loony git! | by firehawk | 2011-09-03 10:37:41 |
|
Scripting? How so? | by ShadowSystems | 2011-09-03 14:40:04 |
|
Better, and actually useful, IF | by firehawk | 2011-09-03 16:14:14 |
|
mmmm... mashed 'taters... =-)P (n/t) | by ShadowSystems | 2011-09-03 16:54:50 |
|
Separate commands : Use the Pipeline | (n/t) | by Klaranth | 2011-09-03 17:45:31 |
|
Only if you want to pipe the output... | by firehawk | 2011-09-03 17:47:24 |
|
command 1&command 2 | by Nessalc | 2011-10-14 12:35:51 |
|
Already tried those... | by ShadowSystems | 2011-09-03 14:36:48 |
|
Case is irrelevant. | by firehawk | 2011-09-03 16:15:40 |
|
WAIT! Case-sensitive? | by firehawk | 2011-09-03 16:16:22 |
|
You're more used to Linux, right | by confused.brit | 2011-09-03 17:51:14 |
|
Dunno, lemme go check... | by ShadowSystems | 2011-09-03 18:20:56 |
