[glentium]

I have long been using ImgBurn (http://www.imgburn.com/) to burn images (like the resulting ISO of HFSLIP). When HFSLIP is finished, I ran another batch file that calls ImgBurn to burn the ISO.

I wonder if any other is also using this...

As you can see from the attached screenshot, it supports command-line parameters to burn images directly to discs. Since HFSLIP provides for automatically creating the ISO by calling MAKEISOFS, I was wondering, again, if HFSLIP could also support a feature to call ImgBurn to directly burn the HFSLIPped ISO when it is finished. Another flag could be added in HFANSWER.INI to give user this option.

Just a suggestion, though...

Attached File(s)

•  ImgBurn.jpg (44.97K)
  Number of downloads: 143

[tommyp]

Give us your batch file and I'm sure we can incorporate it.

[glentium]

here it is:

Thanks!

Attached File(s)

•  Burn.cmd (180bytes)
  Number of downloads: 49

[Yzöwl]

What about including the option therefore to use cdburn from the 2003 Resource Kit or CreateCD for XP 2003 users?

[glentium]

that would be better because that is console-base. but does it support most DVDRW+/- media (i had problem with the built-in Windows burner with regard to such and this guys mentioned something about it: cdburn problems with DVD)? what about compatibility with the latest firmware in new drives? BTW, ImgBurn is an active project and support the latest drives and media.

This post has been edited by glentium: 25 August 2006 - 06:24 PM

[Super-Magician]

cdburn will not burn DVD. To do that, you must use dvdburn, which is a separate file.

[glentium]

oh, ok.
whichever would be the best option. as long as it could incorporate well with HFSLIP. but if dvdburn use the same windows service, we could still run into incompatibility problems with certain drives. might as well incorporate one that would be compatible with most, if not all, drives (like ImgBurn , though, CreateCD seems neat also)

This post has been edited by glentium: 25 August 2006 - 10:21 PM

[Tomcat76]

Personally, I'd prefer to avoid anything that relies on the XP/2K3 built-in burning engine. It needs to work on Win2K too.

I think the best thing is that everything is regulated from HFANSWER.INI and that HFSLIP assumes no defaults. These would be the variables:

NOBURNISO=
BURNISOCMD=

The BURNISOCMD variable should contain the command to execute the ISO burning. If this is not set or if it is empty, no burning will take place. If you want to bypass ISO burning even when you added the BURNISOCMD command, set NOBURNISO to 1.

What do you think of this?

[glentium]

Just checked.. CreateCD doesn't seem to burn CD/DVD images, though, I'm not sure. It seems to only burn directly from a folder with option to make it bootable by specifying a bootable CD image.. If CreateCD is incorporated, the MAKEISOFS would be skipped, and burn SOURCESS folder directly. But sometimes we need the ISO to test it on a virtual machine. Also, correct me please if I'm wrong, but CreateCD seems to be an outdated project. I would still prefer making the ISO through MAKEISOFS then burn it, that is using ImgBurn..

I also do not like to rely on the windows imapi service. These are all, of course, my personal preferences. The final decision on what to incorporate depends on TommyP.

This post has been edited by glentium: 26 August 2006 - 06:17 AM

[glentium]

For the sake of testing, I tried incorporating the attached batch file. I placed it after :MAKEISO routine and is also called after :MAKEISO is called...

It works! on mine, at least

what do you think of this?

Attached File(s)

•  burniso.cmd (870bytes)
  Number of downloads: 28

This post has been edited by glentium: 28 August 2006 - 09:44 PM

[tommyp]

I'm kind of swamped for the next few weeks (or months) doing non-computer activities, so I really can't test & incorporate. A few Q's. Is your CMD smart enough to pick which drive has the cd burner?

[glentium]

ok we understand. better give priorities to more important matters.

i'm still figuring out how to automatically pick up the correct burner. Perhaps, some, like me, have two writers in their computers so it complicates that part.. but if a CD/DVD+/-RW has been HFSLIPped before, we could easily locate what drive it is in. But if it's a blank CD/DVD, then it would be quite difficult..
right now, from what I tested that works, the simplest solution is specify it in HFANSWER.INI

[Super-Magician]

glentium, on Aug 29 2006, 06:53 AM, said:

right now, from what I tested that works, the simplest solution is specify it in HFANSWER.INI

Yes, I think this would be more appropriate.

[Super-Magician]

Hmmm...just wanted to revive this thread and see if TommyP or Tomcat are still interested in it. It seems like a good idea .

[pdxrob]

I'm here to second the notion of reviving this thread.

I would also add that I use the cdburn.exe from the Win2k3 Server resource kit which is freely available to all for download. Once the resource kit is loaded or the file is extracted, it could be put in the path or called from the HFTOOLS directory.

In any case Tomcat76's suggestion of using NOBURNISO and BURNISOCMD to control the burning application means any utility that takes a command line will work.

Just for the record the usage for cdburn.exe if very simple and limited, and is surprisingly fast. It also outputs a percentage display as it burns and supports erasing prior to a burn for RW media.

C:\HFSLIP>cdburn
Usage:
cdburn <drive> -erase [image [options]]
cdburn <drive> image [options]
Options:
-erase Erases the disk before burning (valid for R/W only)
-sao Writes the image out in "session at once", or cue
sheet, mode (default is "track at once")
-speed Speed of burn, or 'max' for maximum speed
-imagehaspostgap Use if your image already contains a 150 sector postgap
The [image] must be provided unless the -erase flag is set.
If both an image and -erase are provided, the media will be
erased prior to burning the image to the disc.

[Tomcat76]

HFSLIP 1.0.4rc5 supports the following variables for CD burning:

NOBURNISO=
CDBURNAPP=
CDBURNSW1=
CDBURNSW2=

HFSLIP uses the following command to burn the ISO:
%CDBURNAPP% %CDBURNSW1% "%TEMPISO%" %CDBURNSW2%

TEMPISO is an HFSLIP internal name for the ISO it has created. You can clearly see the difference between the CDBURNSW1 and CDBURNSW2 variables.

Unless cdburn.exe or dvdburn.exe is used, CDBURNAPP should contain the executable name of the burning program of your choice, including the path. If there are spaces in the path, it should be quoted.

If CDBURNAPP is not defined, HFSLIP looks in the HFTOOLS folder for either cdburn.exe or dvdburn.exe.

When using cdburn.exe or dvdburn.exe, you must specify at least the drive letter in the CDBURNSW1 variable, and HFSLIP defaults to CDBURNSW2=-max if CDBURNSW2 is not defined.

The purpose of NOBURNISO should be pretty straightforward, I think...

Here's a few examples:

ImgBurn.exe:
NOBURNISO=
CDBURNAPP="%PROGRAMFILES%\ImgBurn\ImgBurn.exe"
CDBURNSW1=/MODE ISOWRITE /SRC
CDBURNSW2=/DEST E: /START /COPIES 1 /ERASE /OVERWRITE YES /CLOSESUCCESS /WAITFORMEDIA

cdburn.exe (in HFTOOLS):
NOBURNISO=
CDBURNAPP=
CDBURNSW1=E:
CDBURNSW2=

cdburn.exe (in HFTOOLS) with erase:
NOBURNISO=
CDBURNAPP=
CDBURNSW1=E: -erase
CDBURNSW2=

dvdburn.exe (in HFTOOLS):
NOBURNISO=
CDBURNAPP=
CDBURNSW1=E:
CDBURNSW2=

dvdburn.exe (in HFTOOLS) with erase:
NOBURNISO=
CDBURNAPP=
CDBURNSW1=E:
CDBURNSW2=/Erase

[Super-Magician]

If both cdburn and dvdburn are present in HFTOOLS, which one does HFSLIP default to?

[Tomcat76]

dvdburn.exe

But it will set the wrong switch if you didn't specify CDBURNSW2.

It's maybe better to default to cdburn.exe...

[glentium]

...will be testing asap, thanks for adding this feature.

[Tomcat76]

RC6 still defaults to DVDBURN.EXE, but it no longer sets the wrong switch if CDBURN.EXE is present as well.