Quote:
but I think you'd be hard-pressed to do better than ImgBurn.
Sorry that my native language isn't English, but I didn't get that part.
Now I read the imgburn documentation, it appears to be satisfactory.
What I added to my script was:
Code:
; IMGBURN
; Win+Ctrl+I
#^i::Run C:\Arquivos de programas\ImgBurn\ImgBurn.exe
; IMGBURN COMMAND LINE
:*:iburnb::
FormatTime, CurrentDateTime, ,dd-MM-yyyy__HH-mm-ss
send imgburn /dest G /speed 2x /verify yes /start /log "imgburnlog-build__%CurrentDateTime%" /mode build /volumelabel "" /src ""{left}
return
:*:iburno::
FormatTime, CurrentDateTime, ,dd-MM-yyyy__HH-mm-ss
send imgburn /dest G /speed 8x /start /log "imgburnlog-olavo__%CurrentDateTime%" /mode write /volumelabel "True Outspeak %CurrentDateTime%" /src "D:\Olavo\radio do olavo.cue"
return
:*:iburnw::
FormatTime, CurrentDateTime, ,dd-MM-yyyy__HH-mm-ss
send imgburn /dest G /speed 4x /verify yes /start /log "imgburnlog-write__%CurrentDateTime%" /mode write /src "%Clipboard%" /volumelabel ""
Sleep, 200
send {end}{left}
return
This is intended to make it faster to type in the command line parameters. Still, I'm not sure how to get this done: I have multipole files in different locations, even different drives, and I'd like to write a plain text file in which I would add, line by line, the filepaths of the files to be added to the compilation. Such as:
Code:
list.txt
D:\Testes\torar\1a.txt
D:\Testes\torar\sub4\notas1.html
C:\Documents and Settings\All Users\Desktop\Ad-Aware.lnk
.
.
.
(and so on)
Any ideas?
Login
Register
FAQ
Search
)