Erasing Free Space with DOS commands.
- Thread starter phibins
- Start date
Thanks for your help AGAIN David.
This is what i typed into RUN,
it said "
"
What was my error????
This is what i typed into RUN,
Code:
Eraser addtask -q [-m<45671da4-9401-46e4-9c0d-89b94e89c8b5>][-s=(now)](-u=<P:\[,clusterTips])it said "
Code:
unknown argument [-m<45671da4-9401-46e4-9c0d-89b94e89c8b5>][-s=(now)](-u=<P:\[,clusterTips])What was my error????
This is one for Joel, when his exam. preparations allow him a little time to post.Thanks for the reply.
Just for other people reading this thread i figured out that all brackets should be removed (which isn't always the case in DOS command lines). and that i was missing an equal sign.
it should look something like this
Except, this still doesn't work, and returns:
Hopefully Joel can help me when he has time,
Thanks again!
BTW
Just for other people reading this thread i figured out that all brackets should be removed (which isn't always the case in DOS command lines). and that i was missing an equal sign.
it should look something like this
Code:
Eraser addtask -m=45671da4-9401-46e4-9c0d-89b94e89c8b5 -s=now -u=<P:\ ,clusterTipsExcept, this still doesn't work, and returns:
Code:
Unknown argument: ,clusterTipsHopefully Joel can help me when he has time,
Thanks again!
BTW
The previous health warning about my small brain applies. But, if I read the instructions correctly, round brackets round the arguments are needed. Also, you specified the root folder of the drive (P:\) rather than the drive as such (P
, and you added a spurious '<' in front of the drive letter.
Thus, I would amend your
Eraser addtask -m=45671da4-9401-46e4-9c0d-89b94e89c8b5 -s=now -u=<P:\ ,clusterTips
to read
Eraser addtask -m=(45671da4-9401-46e4-9c0d-89b94e89c8b5) -s=(now) -u=P:,clusterTips=(true)
But I can't test this, so I have no idea whether it works. You will certainly need to run it from an elevated command prompt (and probably kill the running Eraser process first).
David
, and you added a spurious '<' in front of the drive letter.Thus, I would amend your
Eraser addtask -m=45671da4-9401-46e4-9c0d-89b94e89c8b5 -s=now -u=<P:\ ,clusterTips
to read
Eraser addtask -m=(45671da4-9401-46e4-9c0d-89b94e89c8b5) -s=(now) -u=P:,clusterTips=(true)
But I can't test this, so I have no idea whether it works. You will certainly need to run it from an elevated command prompt (and probably kill the running Eraser process first).
David
Thanks again for the reply david,
The command line definitally wants the round brackets. and how did you know to put
since it doesn't say anything in the 'eraser help'.
Anyway, thanks to that I managed to get it to work like this:
Also, in what forum do i make suggestions for eraser????
The command line definitally wants the round brackets. and how did you know to put
Code:
,clusterTips=(true)Anyway, thanks to that I managed to get it to work like this:
Code:
Eraser addtask -m=45671da4-9401-46e4-9c0d-89b94e89c8b5 -s=now -u=P:,clusterTips=(true)Also, in what forum do i make suggestions for eraser????
Joel
Active Member
...I chuckle reading this thread. This is testament to why I say the command line is not meant for mortals like us to use. 
It's currently only used by the Eraser shell extension, thus the command line interface is easy for a computer to generate and parse... but nearly impossible for humans to read.
Yes, your conclusion at the end of the search was correct, no need for brackets etc. The help screen used those to demarcate option types. Traditionally, <option> was used to refer to mandatory arguments and [option] used to refer to optional arguments, which probably caused your confusion. I apologise for not making the CLI more accessible... I'll try to make it better for 6.2.
It's currently only used by the Eraser shell extension, thus the command line interface is easy for a computer to generate and parse... but nearly impossible for humans to read.Yes, your conclusion at the end of the search was correct, no need for brackets etc. The help screen used those to demarcate option types. Traditionally, <option> was used to refer to mandatory arguments and [option] used to refer to optional arguments, which probably caused your confusion. I apologise for not making the CLI more accessible... I'll try to make it better for 6.2.
Hello,
I am runing the following command line and get the error below.
I am guessing I got the path wrong. Can someone point out my error?
Session: Friday, September 16, 2011 5:07:59 PM
Friday, September 16, 2011 5:07:59 PM Error Value cannot be null.
Parameter name: path
This one without the "\" at the end give me the error below.
Session: Friday, September 16, 2011 5:13:55 PM
Friday, September 16, 2011 5:13:55 PM Error Attempted to access a path that is not on the disk.
Looking at the GUI, looks like its trying to target c:\program files\eraser\temp
Why is it virtualizing the path? How do I direct it to C:\temp from the command line?
I am runing the following command line and get the error below.
Code:
eraser addtask -m=(d1583631-702e-4dbf-a0e9-c35dba481702) -s=now -d=c:\temp\I am guessing I got the path wrong. Can someone point out my error?
Session: Friday, September 16, 2011 5:07:59 PM
Friday, September 16, 2011 5:07:59 PM Error Value cannot be null.
Parameter name: path
This one without the "\" at the end give me the error below.
Code:
eraser addtask -m=(d1583631-702e-4dbf-a0e9-c35dba481702) -s=now -d=c:\tempSession: Friday, September 16, 2011 5:13:55 PM
Friday, September 16, 2011 5:13:55 PM Error Attempted to access a path that is not on the disk.
Looking at the GUI, looks like its trying to target c:\program files\eraser\temp
Why is it virtualizing the path? How do I direct it to C:\temp from the command line?