Adrianvdh Posted January 9, 2013 Share Posted January 9, 2013 Sorry for asking this but I'm puzzled how the hell do I use this in a batch file... /MODE <PICKER | READ | BUILD | WRITE | VERIFY | DISCOVERY> Used to tell the program which 'Mode' to open up in. /BUILDINPUTMODE <STANDARD | ADVANCED> Used to tell the program which 'Build Input Mode' to open up in. Only applies to BUILD mode. /BUILDOUTPUTMODE <DEVICE | IMAGEFILE> Used to tell the program which 'Build Output Mode' to open up in. Only applies to BUILD mode. /SRC <Drive Letter | SCSI Address> | "<Folder Name>\" | "<File Name>" | ALLSECTORS | <Custom Number Of Sectors> Used to select the source drive or filename. Drive Letter or SCSI Address applies to READ and VERIFY modes. Folder Name applies to BUILD mode. File Name applies to BUILD and WRITE modes. ALLSECTORS applies to DISCOVERY mode. Custom Number Of Sectors applies to DISCOVERY mode. Examples: /SRC J: /SRC 1:0:0 /SRC "C:\DVD_FILES\VIDEO_TS\" /SRC "C:\DVDIMAGE.ISO" /SRC "C:\BackupProject.IBB" /SRC ALLSECTORS /SRC 2295000 In BUILD mode, you can specify an '.IBB' file as the source. This is an 'ImgBurn Backup Project' file and is a simple text file containing the names of folders / files to add to the image, along with the various configuration options. The simplest way to find the correct syntax for an '.IBB' file is to have ImgBurn create one via the 'Save Project...' option in the 'File' menu, and then look at it in notepad. In BUILD mode, you can specify multiple folders / files directly if you put a pipe character ('|') between them. Example: /SRC "C:\Folder1\|C:\Folder2\|C:\Document1.txt|C:\Document2.txt" /SRCLIST "<File Name>" Used to specify a text file that represents a basic list of folders / files to be added to the 'Source' box. Only applies to BUILD mode. Example: /SRCLIST "C:\BackupList.txt" /DEST <Drive Letter | SCSI Address> | "<File Name>" Used to select the filename or drive. Drive Letter or SCSI Address applies to BUILD, WRITE and DISCOVERY modes. File Name applies to READ, BUILD and VERIFY modes ('DEST' actually means 'Compare' here for VERIFY mode). Examples: /DEST J: /DEST 1:0:0 /DEST "C:\DVDIMAGE.ISO" When in READ mode, you can use '[DISC_LABEL]' | '[DATETIME]' | '[DATE]' | '[TIME]' (without quotes) anywhere in the file name specified with this switch, and the program will replace it with the appropriate value. When in BUILD mode, you can use '[DATETIME]' | '[DATE]' | '[TIME]' (without quotes) anywhere in the file name specified with this switch, and the program will replace it with the appropriate value. Examples: /DEST "C:\DVDIMAGES\[DISC_LABEL].ISO" /DEST "C:\DVDIMAGES\DailyBackup_[DATETIME].ISO" /FILESYSTEM "<File System>" Used to change the value of the 'File System' drop down list. Only applies to BUILD mode. The parameter must match the value within the drop down list exactly. Examples: /FILESYSTEM "ISO9660" /FILESYSTEM "ISO9660 + Joliet" /FILESYSTEM "ISO9660 + UDF" /UDFREVISION "<UDF Revision>" Used to change the value of the 'UDF Revision' drop down list. Only applies to BUILD mode. The parameter must match the value within the drop down list exactly. Examples: /UDFREVISION "1.02" /UDFREVISION "2.50" /VOLUMELABEL "<Volume Label>" Used to set the value of the volume label fields. Only applies to BUILD mode. Length limits are automatically applied. i.e. 32 chars for ISO9660, 16 for Joliet, 126 for UDF. To specify different volume labels for each file system, the following switches are also available: /VOLUMELABEL_ISO9660 "<Volume Label>" /VOLUMELABEL_JOLIET "<Volume Label>" /VOLUMELABEL_UDF "<Volume Label>" These will override what's been set (if anything) by the '/VOLUMELABEL' switch. /SPEED <Write Speed> Used to change the value of the 'Write Speed' drop down list. The parameter must match the value within the drop down list exactly. Examples: /SPEED MAX /SPEED 1x /SPEED 2.4x (or 2,4x depending on regional settings) /COPIES <Number Of Copies> Used to change the value of the 'Copies' drop down list. The parameter must match the value within the drop down list exactly. Only applies to WRITE mode. Example: /COPIES 2 /LAYERBREAK <LBA> Used to tell the program where to put the layerbreak. Only applies to WRITE and DISCOVERY modes and only when burning DVD+R DL discs. Example: /LAYERBREAK 2000000 /ERASE Used to automatically erase / format / overwrite media. /OVERWRITE <YES | NO> Used to force the program to either overwrite all existing files, or never overwrite them. /TESTMODE <YES | NO> Used to make the program simulate the burn - whereby no data is actually written to the disc. Basically, it just checks (or unchecks!) the 'Test Mode' box for you! /VERIFY <YES | NO> Used to make the program verify a disc is readable after it has been burnt. Basically, it just checks (or unchecks!) the 'Verify after write' box for you! /DELETEIMAGE <YES | NO> Used to make the program delete the image after it has been burnt. Basically, it just checks (or unchecks!) the 'Delete Image When Done' box for you! /DELETESOURCE <YES | NO> Used to make the program delete the source files after they've been burnt. Only applies to BUILD mode. *** USE WITH CAUTION *** /EJECT <YES | NO> Used to make the program eject the disc after it has been burnt. Basically, it just checks (or unchecks!) the 'Eject Tray When Done' box for you! /START Used to start the burn process automatically when the program has finished initialising. Basically, it just presses the 'Build' / 'Write' / 'Verify' button for you! /CLOSE Used to close the program when the burn process has finished. Basically, it just presses the 'Close' button for you! /CLOSEINFO Used to close the program when the text file specified by '/INFO' has been created. Basically, it just presses the 'Close' button for you! /CLOSESUCCESS Used to close the program when the burn process has finished AND was successful. Basically, it just presses the 'Close' button for you! /SHUTDOWN Used to shutdown the computer when the program has finished burning. Basically, it just checks the 'Shutdown computer when done' box for you! /WAITFORMEDIA Used in combination with /START and /CLOSE to wait until the program is 'Ready' to burn before trying to start. Normally, if the program isn't 'Ready', the /CLOSE switch causes the program to close without having done anything. /IGNORELOCKVOLUME Used to make the program ignore any 'Access is denied' errors it might run into when it tries to lock the drive for exclusive access, meaning the burn can continue without user intervention. This is mainly for 3rd party applications that are unable to release any 'handles' that they might have open to the drive - thus preventing ImgBurn from obtaining the lock. /NOIMAGEDETAILS Used to stop the program from displaying details about the image. Only applies to BUILD mode. /ROOTFOLDER <YES | NO> Used to automate the 'Root Folder' prompt you get when only adding a single folder to the source list. Only applies to BUILD mode. /BDMVFOLDERS <YES | NO> Used to override the 'Create BDMV Folders' option in the settings. Only applies to BUILD mode. /CERTIFICATEFOLDER <YES | NO> Used to automate the 'Certificate Folder' prompt you get when a 'CERTIFICATE' folder is present at the same directory level as the BDAV/BDMV folder but hasn't been included. It will also override the 'Create CERTIFICATE Folder' option in the settings. Only applies to BUILD mode. /PRESERVEFULLPATHNAMES <YES | NO> Basically, it just checks (or unchecks!) the 'Preserve Full Pathnames' box for you! Only applies to BUILD mode. /RECURSESUBDIRECTORIES <YES | NO> Basically, it just checks (or unchecks!) the 'Recurse Subdirectories' box for you! Only applies to BUILD mode. /INCLUDEHIDDENFILES <YES | NO> Basically, it just checks (or unchecks!) the 'Include Hidden Files' box for you! Only applies to BUILD mode. /INCLUDESYSTEMFILES <YES | NO> Basically, it just checks (or unchecks!) the 'Include System Files' box for you! Only applies to BUILD mode. /INCLUDEARCHIVEFILESONLY <YES | NO> Basically, it just checks (or unchecks!) the 'Include Archive Files Only' box for you! Only applies to BUILD mode. /CLEARARCHIVEATTRIBUTE <YES | NO> Basically, it just checks (or unchecks!) the 'Clear Archive Attribute' box for you! Only applies to BUILD mode. /FILESYSTEMONLY Used to make the program create an image with nothing but the file system in it - i.e. no actual file data (or anything that would normally come after the file data). The image will be useless for anything except looking at the file system layout, you have been warned! Only applies to BUILD mode. *** USE WITH CAUTION *** /OPTIMISEDUPLICATEFILES Used to make the program detect duplicate files within your compilation and only store the data for those files once - thus saving disc space. Only applies to BUILD mode. /BOOTEMUTYPE <0 | 1 | 2 | 3 | 4> Basically, it just modifies the 'Emulation Type' field on the 'Advanced' -> 'Bootable Disc' tab for you! Only applies to BUILD mode. 0 = None (Custom) 1 = Floppy Disk (1.20 MB) 2 = Floppy Disk (1.44 MB) 3 = Floppy Disk (2.88 MB) 4 = Hard Disk Example: /BOOTEMUTYPE 0 /BOOTIMAGE "<File Name>" Basically, it just modifies the 'Boot Image' field on the 'Advanced' -> 'Bootable Disc' tab for you! Only applies when the '/BOOTEMUTYPE' switch is also specified. Only applies to BUILD mode. Example: /BOOTIMAGE "C:\BootImage.ima" /BOOTDEVELOPERID "<Developer ID>" Basically, it just modifies the 'Developer ID' field on the 'Advanced' -> 'Bootable Disc' tab for you! Only applies when the '/BOOTEMUTYPE' switch is also specified. Only applies to BUILD mode. Example: /BOOTDEVELOPERID "LIGHTNING UK!" /BOOTLOADSEGMENT <Load Segment> Basically, it just modifies the 'Load Segment' field on the 'Advanced' -> 'Bootable Disc' tab for you! Only applies when the '/BOOTEMUTYPE' switch is also specified. Only applies to BUILD mode. "Load Segment" should be specified as 4 digit/character hexadecimal value. Example: /BOOTLOADSEGMENT 07C0 /BOOTSECTORSTOLOAD <Sectors To Load> Basically, it just modifies the 'Sectors To Load' field on the 'Advanced' -> 'Bootable Disc' tab for you! Only applies when the '/BOOTEMUTYPE' switch is also specified. Only applies to BUILD mode. Example: /BOOTSECTORSTOLOAD 4 /BOOTPATCHBOOTINFOTABLE Basically, it just checks the 'Patch Boot Information Table' box on the 'Advanced' -> 'Bootable Disc' tab for you! Only applies when the '/BOOTEMUTYPE' switch is also specified. Only applies to BUILD mode. /IBG "<File Name>" Used to make the program write the graph data to a file of the specified name after burning (or verifying if it's enabled). /LOG "<File Name>" Used to make the program write the log to a file of the specified name when closing down. You can use '[DATETIME]' | '[DATE]' | '[TIME]' (without quotes) anywhere in the file name specified with this switch, and the program will replace it with the appropriate value. Example: /LOG "C:\ImgBurn Logs\DailyBackup_[DATETIME].log" /LOGAPPEND When used in combination with '/LOG "<File Name>"', it will make the program try and append to the file rather than overwrite it. /LOGHEADER When used in combination with '/LOG "<File Name>"', it will make the program add a header to the log showing the program version, date and time. It is recommended that this switch be used when creating a new log file that you will later append to via use of the '/LOGAPPEND' switch. The same header is automatically added when using the '/LOGAPPEND' switch so this switch need not be specified. /NOSAVELOG Used to tell the program not to save the log when it's closed. /INFO "<File Name>" Used to make the program write the contents of the drive/media information window (on the right side of the main window) to a file of the specified name after full initialising the media. /PORTABLE Used to make the program skip the sections where it would normally write file association / autoplay / shell extension data to the registry. When used in combination with '/SETTINGS "<File Name>"', you can make it so ImgBurn doesn't make any changes to the PC it's being run on. This is useful if you're running it from a USB pen etc. /LANGID <Language Identifier> Used to tell the program which language to start up in. Values can be in decimal or hexadecimal formats. The appropriate '*.lng' file must exist in the 'Languages' folder. Example: /LANGID 0x0809 /LANGID 2057 Both of the above will cause the program to start with the GUI interface in the 'English (United Kingdom)' language. /SETTINGS "<File Name>" Used to override loading the settings from the registry, and instead load from / save to the specified file. If the file does not exist, default settings will be used and the program will attempt to save to the specified file when it's closed. Even if this switch is not specified, the program will attempt to load from 'ImgBurn.ini' in the application exe's directory BEFORE it loads from the registry. /NOSAVESETTINGS Used to tell the program not to save ANY settings when it's closed. All these command can you please have a full tutorial and examples with it... Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted January 9, 2013 Share Posted January 9, 2013 You use it how I showed you and the other person the other day. The things you see in that file are command line parameters. If you don't know what command line parameters are, you can't have ever used the command prompt (or DOS). To be fair, you're young and so that stuff predates you. Programs that support command line parameters are first called (run) by typing that program's name. You can then instruct the program to do extra stuff by passing it some additional arguments / parameters. So you might run the following from the command prompt... dir That'll give you a directory listing. You could make it show all files (inc hidden ones) by running dir /a where the '/a' argument / parameter makes it show all files. You can normally type [name of program] /? to get a list of arguments / parameters the program supports. So just as I showed you / the other person the other day, you run... ImgBurn /MODE WRITE and it'll start up in Write mode. Just keep adding extra parameters (a space between each one) until it does what you want it to do. Link to comment Share on other sites More sharing options...
Adrianvdh Posted January 9, 2013 Author Share Posted January 9, 2013 (edited) Ah I know what parameters are I just want to know how to aplpy the 'command' you made for ImgBurn fo batch file... ( in the readme.txt it looks weird) ok so for an example i would just make shuffled the commands if i want? Why I'm asking all this is I want to make a batch file where there are options to select and then i make to options and prints it into a batch file and then run it Edited January 9, 2013 by Adrianvdh Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted January 9, 2013 Share Posted January 9, 2013 A batch file is just a plain text file with a .bat file extension, there's nothing special about it. You simply copy + paste the command I provided in that other thread into such a file and then double click the file. It's as easy as that. Link to comment Share on other sites More sharing options...
Adrianvdh Posted January 9, 2013 Author Share Posted January 9, 2013 Yes I know what batch files are I have told you this? I just want to know (sorry for changing this) is there an order of the commands, how many commands do i need and what commands do i need for ImgBurn to work successfully Link to comment Share on other sites More sharing options...
Adrianvdh Posted January 9, 2013 Author Share Posted January 9, 2013 (edited) Oh and another topic in windows 7 you get the option to change to file extension by creating a random file such as a .txt from a .iso for example no I dont have that how do i get it ... and no it just adds the .iso to the file name Edited January 9, 2013 by Adrianvdh Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted January 9, 2013 Share Posted January 9, 2013 You need to tell Explorer to show file extensions. Press the 'Alt' key on your keyboard, click the 'Tools' menu and select 'Folder options....'. Switch to the 'View' tab and then uncheck the 'Hide extensions for known file types' box. Click OK. Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted January 9, 2013 Share Posted January 9, 2013 Yes I know what batch files are I have told you this? I just want to know (sorry for changing this) is there an order of the commands, how many commands do i need and what commands do i need for ImgBurn to work successfully Yes, you told me that you're a master with batch files.... but then you go asking really simple stuff like this which makes me think you're exaggerating your skill level slightly. No, there's no order to the commands. Use what's logical, that's all I do - and what I did when writing the ReadMe. You need to use as many commands as it takes to achieve your goal. I have no idea how many that would be (or which ones)! Link to comment Share on other sites More sharing options...
Adrianvdh Posted January 9, 2013 Author Share Posted January 9, 2013 (edited) Im just asking with these commands because iv never had to deal with a program the implemented cmd ... why batch why not vbs for these commands ... they dont belong in batch they are your own script that is why i need help with them ... Yes, you told me that you're a master with batch files.... but then you go asking really simple stuff like this which makes me think you're exaggerating your skill level slightly. Yes just a little say I'm advansted with batch file .. no one can 'master' a lan Edited January 9, 2013 by Adrianvdh Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted January 9, 2013 Share Posted January 9, 2013 Every dos/command line tool has arguments / parameters like these. If you'd ever done anything with batch files or DOS in general, you'd know that. Why batch and not vbs... well because it's a total waste of time and energy. Don't complicate things just for the sake of it. Link to comment Share on other sites More sharing options...
Adrianvdh Posted January 9, 2013 Author Share Posted January 9, 2013 Why not your own file system a commands running down: READ SPEED=x8 blablabla etc something.whatever No could you help with the win7 post at #6 Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted January 9, 2013 Share Posted January 9, 2013 Why not your own file system a commands running down Seriously, in what world does what you've just written make any sense?! Try actually reading your posts through before you post them. If I keep just reading nonsense from you, I'll ignore everything you say. I told you before why you can't just list things like that. It's because they'd be script variables and nothing at all to do with ImgBurn. How do you expect it to know about random variables you've configured in a script? That's why you pass arguments / parameters as part of the command line. /me shakes head in disbelief Post # 7 answered post # 6. /me shakes head in disbelief again Link to comment Share on other sites More sharing options...
Adrianvdh Posted January 10, 2013 Author Share Posted January 10, 2013 Ok Ok I wont bother you then Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted January 10, 2013 Share Posted January 10, 2013 All I ask is that you don't bother me with stuff that makes no sense. Link to comment Share on other sites More sharing options...
Recommended Posts