How to copy files in RunOnceEx.cmd

[Rico.JohnnY]

i.e

REG ADD %KEY%\100 /V 1 /D "copy \"%systemdrive%\\abc\\abc.txt\" \"d:\efg\\\"" /f

the sentence above doesn't seem to work... how to correct it ?

[CWorks]

create another .cmd file with the copy command in it and use that in RunOnceEx.cmd that's how i do it

[GreenMachine]

REG ADD %KEY%\100 /V 1 /D "CMD /C COPY \"%SYSTEMDRIVE%\ABC\ABC.TXT\" \"D:\EFG\\"\" /F

[Rico.JohnnY]

thanks a lot

[sleepnmojo]

REG ADD %KEY%\100 /V 1 /D "CMD /C COPY \"%SYSTEMDRIVE%\ABC\ABC.TXT\" \"D:\EFG\\"\" /F

close, you have an extra \ at the end there

[GreenMachine]

@sleepnmojo: Now tell the truth: did you try, or just look? If you tried, you may not have been so quick to post. It was just a favor, but if you want a lesson ... The final backslash is there for two reasons. Firstly, it is included in the failed example at the top of the page. Secondly, it tells the interpreter that you want to copy the file ABC.TXT to the D:\EFG\ABC.TXT, and not E:\EFG. Assuming the exercise is to copy ABC.TXT to another directory, the trainling backslash is required for correct syntax, and to avoid creating the file D:\EFG in the case the directory D:\EFG is non-existant.

Resulting value in the registry:

CMD /C COPY "C:\ABC\ABC.TXT" "D:\EFG\"

[sleepnmojo]

@sleepnmojo: Now tell the truth: did you try, or just look? If you tried, you may not have been so quick to post. It was just a favor, but if you want a lesson ... The final backslash is there for two reasons. Firstly, it is included in the failed example at the top of the page. Secondly, it tells the interpreter that you want to copy the file ABC.TXT to the D:\EFG\ABC.TXT, and not E:\EFG. Assuming the exercise is to copy ABC.TXT to another directory, the trainling backslash is required for correct syntax, and to avoid creating the file D:\EFG in the case the directory D:\EFG is non-existant.

Resulting value in the registry:

CMD /C COPY "C:\ABC\ABC.TXT" "D:\EFG\"

I was actually referring to your \"\" at the end, but since you wanted to teach me something, I'll correct you.

If D:\EFG\ didn't exist, your command wouldn't work. You would need to use XCOPY. Copy gives an error saying it can't copy the file, thus you would have to make one. XCOPY doesn't have that limitation.

[GreenMachine]

OK, you win: you are the smarter a**! Too bad you prefer to nit pick, than to answer the question yourself ... No, it wont copy if D:\EFG\ does not exist - behaviour by design - which is the desired effect, as opposed to creating a text file named D:\EFG.

Reminds me of many of the IT meetings I went to with my Old Man. The speaker would say "Instead of re-inventing the wheel ... ", the Old Man would turn to me and say, "Tha a**hole couldn't even invent a toothpick." Or as he said upon retirement: "OK, we got the game going. Bring on the second string."

I guess I'll go back to my own corner, where nobody is interested in who has the bigger dick ...

[sleepnmojo]

OK, you win: you are the smarter a**! Too bad you prefer to nit pick, than to answer the question yourself ... No, it wont copy if D:\EFG\ does not exist - behaviour by design - which is the desired effect, as opposed to creating a text file named D:\EFG.

Reminds me of many of the IT meetings I went to with my Old Man. The speaker would say "Instead of re-inventing the wheel ... ", the Old Man would turn to me and say, "Tha a**hole couldn't even invent a toothpick." Or as he said upon retirement: "OK, we got the game going. Bring on the second string."

I guess I'll go back to my own corner, where nobody is interested in who has the bigger dick ...

I only nit-pick about cmd files because I find the parser inconsistent in so many cases. Of course most of this will change in longhorn, if they give us the new shell they have been talking about.

I would join you in that corner, but the chairs are over here

[GreenMachine]

I let you know when one frees up!

(You think the interpreter is inconsistent? Play with a few different versions of COMPRESS.EXE ... )