Starting up xorriso-tcltk with -hardlinks "on" if xorriso version >= 1.3.0

frontend/xorriso-tcltk

@@ -147,6 +147,9 @@ set expect_broken_pipes "0"
 # Whether to use command -move rather than -mv. Possible since xorriso-1.2.8.
 set use_command_move 1
 
+# Whether to enable -hardlinks mode "on". Too slow before xorriso-1.3.0.
+set use_command_hardlinks_on 1
+
 
 # Local copies of xorriso state
 
@@ -789,7 +792,7 @@ proc localfs_filetype {path} {
 #
 proc check_xorriso_version {} {
   global sieve_ret result_list pre_msglist xorriso_version min_xorriso_version
-  global use_command_move
+  global use_command_move use_command_hardlinks_on
   global reply_conn
 
   set version "0.0.0 (= unknown)"
@@ -820,6 +823,9 @@ proc check_xorriso_version {} {
   if {$xorriso_version < "1.2.8"} {
     set use_command_move 0
   }
+  if {$xorriso_version < "1.3.0"} {
+    set use_command_hardlinks_on 0
+  }
   set_display_msg $disp_en_mem
 }
 
@@ -868,11 +874,17 @@ proc setup_xorriso {} {
 # Commands which should also be at the start of a log script
 #
 proc xorriso_loggable_init_cmds {} {
+  global use_command_hardlinks_on
+
   set cmd "-for_backup"
 
-  # There is a performance problem in xorriso with -hardlinks on and
+  # Before xorriso-1.3.0 there is a performance problem with -hardlinks "on"
-  # image manipulations. So for now -hardlinks is set to off.
+  # and image manipulations before xorriso-1.3.0.
-  set cmd "$cmd -hardlinks off"
+  if {$use_command_hardlinks_on == 0} {
+    set cmd "$cmd -hardlinks off"
+  } else {
+    set cmd "$cmd -hardlinks on"
+  }
 
   set cmd "$cmd -backslash_codes on"
   set cmd "$cmd -follow mount:limit=100"
@@ -4379,7 +4391,7 @@ The GUI window is separated into three main areas:
   - allows to scan for optical drives,
   - to aquire them and load their ISO directory tree,
   - to aquire ISO image files from hard disk as pseudo drives like DVD+RW,
-  - to blank CD-RW, DVD=RW, DVD+RW, BD-RE and format DVD-RW, BD-R,
+  - to blank CD-RW, DVD-RW DVD+RW, BD-RE and format DVD-RW, BD-R,
   - to trigger writing of ISO sessions (which get defined in the third area),
   - and to burn image data files from hard disk to optical media.
 
@@ -4862,11 +4874,13 @@ See xorriso command -stream_recording."
 burn a data file from hard disk onto the output drive.
 The address of the disk file is taken from the neighboring text field.
 
+If you do not plan to append further data to the medium, then consider
+to enable the \"Close\" switch.
+
 No input drive may be aquired. (Delete all characters from the field
 \"Input drive/image\" and hit Return to give up the input drive.)
 
 The medium in the drive must be blank.
-
 (It is well possible to burn image files to appendable media. But the
 image needs to be prepared for the address offset. Who can do that can
 as well use one of the command line tools for burning the result. E.g.