Command-prompt syntax question::Forward slant character

[riprap]

Hello, All
[I looked for an XP group designed for command-line questions, but
couldn't find one!]
Recently I caused a large amount of unwanted data deletion while
mucking around in the command prompt window and I'm trying to learn
what I did wrong....
What I was trying to do was to delete all the files out of
"C:\Documents and Settings\<username>\Local Settings\Temporary Internet
Files". So I brought up a command window, navigated to that directory,
and typed in "/*.*" (without the quotes), and hit Enter. Immediately
the screen was filled with hundreds of files that were being deleted,
scrolling downward until I realized that there was a whole lot more
being deleted than what I intended...Luckily I knew enough at that
point to hit Ctrl+Break, which brought the destruction to a stop.
It took between 2.5 and 3 hrs to repair all the deletions to the
various usernames accounts.
Sorry to make this so lengthy, but all I'm trying to learn is: What
the Sam Hill did I do wrong? I was under the impression that, when you
had already placed the command-cursor in the directory you wanted to
reach, that by hitting a forward-slant ("/") any commands after that
character would be restricted solely to operating within that
directory. Evidently not.
If anyone could help me out with this question it would be much
appreciated.
riprap
suffering from the usual confusion

 

[neil]

Hi,
I must admit I've never seen the "/" used in that way. To delete files from
the folder you are in you would type "del *.*"

Neil

 

[AJR]

First - you may not have been at C:\..\..\..\Temporary internet files when
you executed "del \*.*". Second - if you inserted "<username>" as a variable
place holder - may have been the problem (strictly "guess" on my part).

Big question - why not use disk cleanup via system tools?

 

[riprap]

Hello, AJR and neil:
Thanks for taking the time to reply...
I admit that when things 'went sideways' things happened pretty
quick, and I'm not absolutely 100% sure what the syntax I used was....I
thought it was "del/*.*". but as far as being in the right directory
location (TIF), I'm pretty sure that's a fact.
As far as AJR's question, "why not use disk cleanup via system
tools", that's a very good question! I guess that, generally speaking,
working from command-line just seems faster and more to-the-point (not
to mention more powerful) than working thru a GUI.

I guess it didn't 'ring a bell' with anyone, the syntax "del/*.*" ?

Like I sd, thanks much for the replies. Have an excellent day. (And
AJR: When I posted the filepath with "<username>", I was just using it
as a placeholder; actually the correct user's name was entered [ )
riprap
living under the bridge, 11 degrees below in evans, co.

First - you may not have been at C:\..\..\..\Temporary internet files when
you executed "del \*.*". Second - if you inserted "<username>" as a variable
place holder - may have been the problem (strictly "guess" on my part).

Big question - why not use disk cleanup via system tools?

Hello, All
[I looked for an XP group designed for command-line questions, but
couldn't find one!]
Recently I caused a large amount of unwanted data deletion while
mucking around in the command prompt window and I'm trying to learn
what I did wrong....
What I was trying to do was to delete all the files out of
"C:\Documents and Settings\<username>\Local Settings\Temporary Internet
Files". So I brought up a command window, navigated to that directory,
and typed in "/*.*" (without the quotes), and hit Enter. Immediately
the screen was filled with hundreds of files that were being deleted,
scrolling downward until I realized that there was a whole lot more
being deleted than what I intended...Luckily I knew enough at that
point to hit Ctrl+Break, which brought the destruction to a stop.
It took between 2.5 and 3 hrs to repair all the deletions to the
various usernames accounts.
Sorry to make this so lengthy, but all I'm trying to learn is: What
the Sam Hill did I do wrong? I was under the impression that, when you
had already placed the command-cursor in the directory you wanted to
reach, that by hitting a forward-slant ("/") any commands after that
character would be restricted solely to operating within that
directory. Evidently not.
If anyone could help me out with this question it would be much
appreciated.
riprap
suffering from the usual confusion