Gebruik van 'command line parameters'

[Nog niet alle pagina's zijn vertaald.  Dit is een werk van lange adem.  Indien een bepaalde pagina u zeer interreseert maar nog moet vertaald worden, gelieve dan de exacte link naar deze pagina naar ons op te sturen met het verzoek prioriteit te geven aan de vertaling ervan.  Dank u.]

As of IsoBuster 2.2 there is support for (additional) command line parameters.  Additional because before, and as long as we can remember, IsoBuster has supported loading an image file via the command line.

First some general notes:

- IsoBuster is not a console application.  When started with commands, IsoBuster's GUI will still load.    All messages and popups that would appear normally will still appear.  If the task is such that user input is required, that user input (e.g. clicking a button) will still need to happen.
- Commands can be in random order (that includes the path to an image file that needs to be loaded as well)
- If commands are repeated more than once, with different or same content, only the last occurance on the line will be used.
- All commands start with a forward slash '/' except the loading of an image file.  Image files are loaded by simply providing the full path, which assures 100% backwards compatibility with older versions.

Destination path variables:

[Introduced in IsoBuster 2.8.5]
The destination paths used for "/ei","/ef" "/tree" can contain variables.  They are especially useful when combined with (but not limited to) "all" ("/t", "/s", "/ef:").
This way it is possible to (for instance) extract all file systems for all tracks and sessions and put each file system in its own folder with a descriptive folder name, next export file lists of all files to those same created folders, or give the file lists the same name as the folder they are referring to etc.

<%FI> : File System Index
<%FT> : File System Type
<%FN> : File System Name
<%TI> : Track Index
<%TN> : Track Name
<%SI> : Session Index
<%SN> : Session Name

Example:

isobuster.exe /d:d "/ei:c:\my extracted image files\track<%TI>.iso" /t:all 
isobuster.exe /d:d "/ef:all:c:\extracted\<%FI><%FN>"  
isobuster.exe /d:d "/ef:udf:c:\extracted\s:<%SI>-f:<%FI>(<%FN>)" /s:all

Loading an image file:

Simply provide the full path of the image file on the command line.  Put between quotes to optimally support long filenames and blanks in filenames.

Command:

no command

Example:

isobuster.exe "c:\my image files\image1.iso"

Auto-select a drive:

IsoBuster selects by default, the first drive that contains a disc (CD / DVD / BD / HD DVD) or, if no discs are loaded, the first drive in the list.  You can tell IsoBuster to select a specified drive on start up, no matter if there is a disc in that drive or not.  The drive is chosen by means of its drive letter (as IsoBuster detects it).  One character only (e.g. d or e or ...).  This command has lower priority than loading an image file.  If an image file is loaded (see previous command) then that image file is selected by default and this command has no impact at all.

Command:

/d:[drive letter]

Example:

To auto-select drive f:

isobuster.exe /d:f

Extraction of an image file:

With this command you can let IsoBuster start up, and make an image file of the selected disc automatically.  Selection of the disc depends on what drive is selected by IsoBuster.  See previous command for more on that.  If you opened an image file at the same time (see first command) then the image file will be selected and you will be making a new image file of the selected image file (e.g. convert nrg to ibp/ibq).  If you did not open an image file, nor specified a drive (see previous command), then the first drive with a disc present will be selected.  If you specified a drive (see previous command) then that drive will be used.  If no disc is present in that drive, then no extraction will happen.  Also look at commands /et:  /ef:  /c   /t:  and  /s:  to discover more extraction power!  If no extraction type is specified via the command /et: then the created image will be of the managed kind (*.ibp / *.ibq).  IsoBuster will make corrections to the filename extension in case of a managed image file extraction (*.ibp), if the provided filename extension is not correct.  No corrections are made for the other extraction types.  If no destination filename or foldername is provided, IsoBuster will start extraction but will show the BrowseForFolder dialog so that a manual selection can be made.

Command:

/ei:[destination path and filename]

Examples:

Extract the disc to an imagefile with provided name:
All three following examples will create the same files (created_image.ibp and created_image.ibq) because managed image filename extensions are auto-corrected

isobuster.exe "/ei:c:\my image files\created_image1.iso"
isobuster.exe "/ei:c:\my image files\created_image1.ibp"
isobuster.exe "/ei:c:\my image files\created_image1"

Following example will create an ISO file with user data (cfr. TAO)

isobuster.exe "/ei:c:\my image files\created_image1.iso" /et:u

Following example will create an ISO file with raw data (cfr. BIN)

isobuster.exe "/ei:c:\my image files\created_image1.iso" /et:r

Extract the image file to a folder location:
Following example creates CD.ibp to the defined folder

isobuster.exe "/ei:c:\my image files\"

Following example creates CD.tao or CD.iso(*) to the defined folder
(*) depends on the image file extraction options (See ISO / BIN / TAO)

isobuster.exe "/ei:c:\my image files\" /et:u

Following example creates CD.bin or CD.iso(*) to the defined folder
(*) depends on the image file extraction options (See ISO / BIN / TAO)

isobuster.exe "/ei:c:\my image files\" /et:r

Without a destination path and filename, extraction will also start but will launch the BrowseForFolder dialog

isobuster.exe /ei:

Extraction Type (user data, raw or managed):

This command is used in combination with extraction commands: /ei: and /ef:
If it is absent, /ei: will internally default to /ei:m and /if: will internally default to /ef:u
Or in other words, image files are created managed and only user data is extracted for files and folders.  User data is practically always prefered in case of files and folders (raw only exists for engineering purposes).  (Managed does not exist for files and folders, only for image files).

Command:

/et:[Type[u][r][m]]

[Type] comes in three flavours:
u  (User data)
r   (Raw data)
m (Managed)

Example:

isobuster.exe "/ei:c:\my image files\" /et:m

Select a Track:

This command is used in combination with extraction commands: /ei: and /ef:

In case of /ei: (image file extraction) it is used to identify and extract a single track.  This is only useful for engineering purposes as an image of a single track is in most cases of not much use (unless it's the only track).  Only the image file of an entire CD is really useful for end users, but for those tinkering about the functionality exists anyway.

In case of /ef: (file and folder extraction) it is used to identify the track that has the file system we want to extract from.  IsoBuster can find multiple file systems, including older ones in older sessions.  If you specify the track then you tell IsoBuster to use the file-systems attached to that particular track.  If absent, IsoBuster decides for itself and uses the most relevant file-system from the most relevant session/track.  While this feature can be useful, it makes more sense to use /s: (select a session) to tell IsoBuster from which session's file-system(s) to extract.

In case of /scan (find missing files and folders) it is used to determine the session that needs to be scanned.

A track index starts from 1.  If you specify track 0 the command will simply be ignored.  If both a track and a session (see next) are selected, then the session selection is ignored and only the track selection is used.  If a track index is provided and that particular track does not exist, then there will be no extraction and IsoBuster will fail.

[Introduced in IsoBuster 2.8.5]
The index can also be "all" which means that the operation(s) that look at the track property ("/scan", "/ei", "/ef") will execute in a loop for all tracks.

Command:

/t:[Index]

Example:

isobuster.exe "/ei:c:\my image files\" /et:m /t:1
isobuster.exe "/ei:c:\my wave files\" /t:all

Select a Session:

This command is used in combination with extraction commands: /ei: and /ef:

In case of /ei: (image file extraction) it is used to identify and extract a single session (all tracks of that session in one file).  This is only useful for engineering purposes as an image of a single session is mostly of not much use (unless it's the only session).  Only the image file of an entire CD is really useful for end users, but for those tinkering about the functionality exists anyway.

In case of /ef: (file and folder extraction) it is used to identify the session that has the file system we want to extract from.  IsoBuster can find multiple file systems, including older ones in older sessions.  If you specify the session then you tell IsoBuster to use the file-systems attached to that particular session.  If absent, IsoBuster decides for itself and uses the most relevant file-system from the most relevant session. 

In case of /scan (find missing files and folders) it is used to determine the session that needs to be scanned.

A session index starts from 1.  If you specify session 0 the command will simply be ignored.  If both a track (see previous) and a session are selected, then the session selection is ignored and only the track selection is used.  If a session index is provided and that particular session does not exist, then there will be no extraction and IsoBuster will fail.

[Introduced in IsoBuster 2.8.5]
The index can also be "all" which means that the operation(s) that look at the session property ("/scan", "/ei", "/ef") will execute in a loop for all sessions.

Command:

/s:[Index]

Example:

isobuster.exe "/ei:c:\my image files\" /et:m /s:1

Extraction of entire file-systems (root) / files and folders:

With this command you can start up IsoBuster and extract one ore more files or folders automatically.  Selection of the disc depends on what drive is selected by IsoBuster.  
See previous commands for more on that (e.g. loading an image file, extraction of an image file and auto-select a drive).  Also look at commands /et:  /ei:  /c   /t:  and  /s:  to discover more extraction power in combination with this command.  If no extraction type is specified via the command /et: then user data will be extracted (which is almost always the sensible thing to do).  If no track (/t:) or session (/s:) are definded then IsoBuster will use the most plausible and relevant session / track / file-system to extract from.  If no prefered file-system is provided via this command then IsoBuster will decide on the most appropriate file system to use (e.g. choose between UDF, ISO etc.).  If there is a prefered file-system provided and that particular file-system is not available then IsoBuster will not extract (and hence fail).  If no file or foldernames to extract are provided via this command then IsoBuster will extract the entire file-system, which means all files and folders starting from the root of the selected file-system.  If no destination filename or foldername is provided IsoBuster will start extraction but will put up the BrowseForFolder or Save File dialog.

Command:

/ef:[FileSystem:][File or folder name (relative path) |][destination path and filename]

[FileSystem:] is always three characters and comes in following flavours:

iso: (Iso9660, Joliet, Rock Ridge, ... IsoBuster picks the most relevant one)
udf: (UDF)
hfs: (HFS and HFS+, IsoBuster chooses HFS+ over HFS)
ifo: (IFO, showing VOB and IFO files)
boo: (El Torito - Bootable image)
fat: (FAT)
sig: (Files found based on their signature, to be combined with the "/scan" command line parameter)
all: (All file systems found for relevant track or session) [Introduced in IsoBuster 2.8.5]

[File or folder name (relative path) |]

A relative path to a folder or file, starting from the root (but without a drive letter)
Never start with a backlash, just the name or folder.
For instance:
picture.jpg (and picture.jpg exists in the root)
mypictures (and folder mypictures exists in the root)
mypictures\picture1.jpg  (and picture1.jpg exists in subfolder mypictures (which is located in the root))

[destination path and filename]

Where the file / folders are extracted to.  IsoBuster does not check destination folders throuroughly, so it may proceed to extract to the required folder and then run into Windows errors.  In other words, check if the destination folder also exists before you start.

Examples:

Extract the complete (most appropriate) file-system (root) of the most relevant track/session:
Both examples will extract the content to existing folder "my extracted files" (or create that folder when not existing yet (Works only one folder deep))

isobuster.exe "/ef:c:\my extracted files\"
isobuster.exe "/ef:c:\my extracted files"

Following example extracts the UDF file system (assume there's a choice between file-systems, and we want UDF):

isobuster.exe "/ef:udf:c:\my extracted files"

Following example extracts a subfolder ("my docs") from the UDF file system 

isobuster.exe "/ef:udf:mydocs|c:\my extracted files"

Following example extracts a particular file  ("my docs\my letters\letter1.doc") from the ISO file system 
(and from the second session (let's assume there are three sessions on this disc))

isobuster.exe "/ef:iso:mydocs\my letters\letter1.doc|c:\my extracted files" /s:2

Following example extracts a particular file  ("VIDEO_TS\VTS_01_1.VOB") from the IFO file system and extracts it with filename "movie.mpg"

isobuster.exe "/ef:ifo:VIDEO_TS\VTS_01_1.VOB|c:\my extacted files\movie.mpg" 

Following example extracts the boot image file from a MS installation disc

isobuster.exe "/ef:boo:Microsoft Corporation.img|c:\my extracted files\"

Extraction Prompts:

[Introduced as of IsoBuster 2.5]
This command is used in combination with extraction commands: /ei: and /ef:
If it is absent, following default values are used: /ep:pbm and /ep:pfe, wich means that the GUI will prompt when there is a read error, so that the user can make a selection, and that the GUI will prompt when a file is about to be overwritten.

Command:

/ep:[Type]

[Type] comes in following flavours:

For error handling, when a read error is encountered:

pbm: Prompt with Best Matching GUI window
ria: Prompt with Retry Ignore Abort GUI window
rsa: Prompt with Retry Select Abort GUI window
oea: No Prompt, On Error: Abort extraction
oeo: No Prompt, On Error: Ommit the sector
oez: No Prompt, On Error: Zero (replace all data with null bytes, in case of raw only the user data is replaced and the EDC/ECC is calculated)
oee: No Prompt, On Error: Error (replace the sector with erronous data)
All "No Prompt" options during extraction also cause prompts during file system exploration to be suppressed.

For file over-write handling, when the file already exists:

pfe: Prompt with File Over-write GUI window
owr: No Prompt, Over-write the file
now: No Prompt, No Over-write (don't overwrite the file, leave as is and continue to the next file (if appropriate))

Example:

isobuster.exe "/ei:c:\my image files\" /et:m /ep:oez /ep:owr

Open and Close a drive tray:

This command opens or closes the tray.  Default it will open the selected drive's tray if closed, or close it if already opened.  This command can be issued up to 9 times on the command line, so that a drive can be issued the same command a couple of times. For instance before and after an operation. 

Command:

/oc:[Type][Before or After][Wait]

[Type] is either o or c or missing. O for Open Tray and C for Close Tray and in case absent the tray will open if closed or close if opened.  
[Before or After] is either b or a or missing.  B for before an operation (e.g. before extraction of a file), A for after an operation (e.g. after creation of an image file).  In case absent the command is executed before.
[Wait] is a number between 0 - 9 and stands for the amount of seconds that the application will poll the drive, waiting for ready, after the application issued the Open/Close command.  When no value is provided the application will default to 0 in case of opening the tray, and 2 in case of closing the tray.

Example:

isobuster.exe /d:f /oc:c9 /oc:bc9 "/ef:c:\my extracted files\" /oc:oa

The example shows that the tray is closed before the extraction operation.  The command is even issued twice, just to make sure and the time-out is set to 9 seconds each time, so the application will wait (at the most) 18 seconds (or less if the drive signals "ready") before the extraction operation starts.  After the extraction operation the drive tray is opened.

Scan for missing files and folders:

[Introduced in IsoBuster 2.8.5]
This command immediately starts the process that looks for missing files and folders
This command also automatically suppresses a few dialogs.  
When this parameter is passed, the program won't ask if you want to scan, should the content be empty (no found file-systems) after initial mount of the disc or image and it won't suggest to make an .ibp first either in this case.
/scan is executed on the last session of a disc or image file unless /t (track) or /s (session) are specified. In case a track is specified the scan is done on the session the track is in.  In case a session is specified the scan is done on the specified session.  In case track or session are specified and have value "all" then all sessions are scanned.
/scan can be combined with file or image extractions as it is executed before any extractions are executed.

Command:

/scan

Example:

isobuster.exe /d:f /scan "/ef:sig:c:\my extracted files\"

Export a file list:

[Introduced in IsoBuster 2.8.5]
This command allows you to build a file and folder list from a folder or an entire file system.  It takes parameters (tokens) as input that define the layout of the content that is written to the file

Command:

/tree:[FileSystem:][File or folder name (relative path) |][destination path and filename][?Custom string with tokens/variables]

[?Custom string with tokens/variables] can be any string with following tokens/variables that are replaced by their respective values:

<%LBA>  Logical block address
<%FULLPATH>  Full path (e.g. d:\files\file1.txt)
<%RELPATH>  Relative path (e.g. \files\file1.txt)
<%FILE>  File (e.g. \file1.txt)
<%SIZE>  Size of the file, formatted (e.g. 1.4 KB or 2,3 MB or 300 Bytes or ..)
<%BYTES>   Size in bytes only, formatted (e.g. 300 or 2.345 or 44,555,000 or ...)
<%TIMEDATE>  Time and date, formatted (e.g.  28/12/2005 23:22:42 or 12/28/2005 23:22:42 or ...) 
<%TIME>  Time , formatted (e.g.  23:22:42)  
<%DATE>  Date, formatted (e.g.  28/12/2005 or 12/28/2005 or ...) 
<%GMT>  GMT (e.g. GMT -08:00)

Example:

isobuster.exe  /scan /t:all "/tree:all:k:\export\S<%SI>T<%TI>FS<%FI>(<%FT>)(<%FN>).txt?<%LBA>, <%RELPATH>, <%BYTES>"

Sector View:

This command immediately opens the sector view window and shows the chosen sector.

Command:

/sv:[Address]

Example:

isobuster.exe /d:f /sv:2000

Close IsoBuster automatically:

This command closes IsoBuster after the requested (via command line provided) task, for instance after an extraction task (/ei: or /ef:)

Command:

/c

Example:

isobuster.exe "/ef:boo:Microsoft Corporation.img|c:\my extracted files\" /c

Minimize IsoBuster automatically:

This command minimizes IsoBuster after initialisation, before the requested (via command line provided) task, for instance during an extraction task (/ei: or /ef:)

Command:

/m

Example:

isobuster.exe "/ef:ifo:VIDEO_TS\VTS_01_1.VOB|c:\my extacted files\movie.mpg"  /c /m

Do not show the splash screen on startup of the program:

[Introduced in IsoBuster 2.5.5]
This command suppresses the splash screen that is shown when the program starts.

Command:

/nosplash

Example:

isobuster.exe "/ef:ifo:VIDEO_TS\VTS_01_1.VOB|c:\my extacted files\movie.mpg"  /c /m /nosplash

Do not find nor query the drives on startup of the program:

[Introduced in IsoBuster 2.5.5]
This command suppresses the finding of drives when the program starts.  The command can be used when you are only interested in opening image files and when you need no drive support.  It can potentionally speed up program startup, especially when there is a disc mounted in one of the drives.

Command:

/nodrives

Example:

isobuster.exe "/ef:ifo:VIDEO_TS\VTS_01_1.VOB|c:\my extacted files\movie.mpg"  /c /m /nosplash /nodrives

Log Error:

This command logs a simple error code to a file, in case IsoBuster could detect a problem before the actual (via command line provided) task started.  So it does not log read errors or intervention that was required during an extraction process for instance.  However, if the extraction started but was aborted, for whatever reason, then there will still be an error value.  The text file will contain ANSI SBCS text.

Command:

/l:[destination path and filename]

Errors values:

0       No Error (success).
1       No Tracks / Sessions found
2       Track Index provided but this track is not available
3       Session Index provided but this Session is not available
4       No File-system track found
5       No (or not a matching) File-system found
6       Folder name is already in use as filename
7       Not a matching file or folder found
10xx  Extraction aborted by user

Example:

isobuster.exe "/ef:c:\my extracted files" "/l:c:\my extacted files\log.txt"

Log Error-String:

A basic string can be passed along to IsoBuster, to be put in the log file (see Log Error (command /l:)).  Make sure that this string contains the value %%u which is then replaced by the error code (see Log Error).

Command:

/l:txt:[Text]

Example:

isobuster.exe "/ef:c:\my extracted files" "/l:c:\my extacted files\log.bat" "/l:txt:ECHO %%u"

Load plugin(s):

[Introduced in IsoBuster 2.8]
This command allows you to load one or more plugins.  Plugins can be used to interpret image files and/or to write image files
The command can be used multiple times on the command line, to be able to load several plugins at once.
Plugins have priority over the embedded functionality, should there be overlap.

Command:

/plugin:[path and filename of plugin]

Example:

isobuster.exe "c:\my image files\image1.iso" /plugin:c:\my_iso_plugin.dll