MSFN Forums > Doing It Wrong

MSFN Forums > Member Contributed Projects > HFSLIP

spinjector

Jul 17 2009, 02:42 PM

I am using the HFANSWER.INI with ISONAME=HFSLIPCD specified, but my ISO keeps coming out named HFSLIPCD_07172009_13h15m.iso.

Is this by design, or am I doing it wrong?

I looked at the part of the CMD file that feeds the command line to CDIMAGE.EXE, but the complexity is such that it'd be easier to ask than for me to figure it out.

This is my HFANSWER file:

CODE

DRIVERCOMP=A
SBOOTPATH=1
MBOOTPATH=
DELCATS=0
BACKUPSOURCE=0
XPIZESW=
FORCEXPIZESLIP=
ISONAME=HFSLIPCD.ISO
ISOTITLE=HFSLIPCD
FORCECDIMAGE=
CDIMGSW=-h -j1 -m
MKISSW=-relaxed-filenames -d -D -N -J -no-emul-boot -no-iso-translate -boot-load-size 4
MAKENOISO=
OVERWRITEISO=
INSTALLRC=1
INCWMPCSKIN=
INCALLSKINS=
NOLOGCOPY=
IE7BACKUP=
IE7GUILOGON=
IE7SVCPACK=
RELEASE=AUTORUN

tommyp

Jul 18 2009, 04:55 AM

Is your file named hfanswer.ini? Or hfanswer.ini.txt? The file should be located in hftools, but you probably knew that anyway.

Yzöwl

Jul 18 2009, 02:15 PM

The code uses the HFSLIPCD part by default, this is user changeable in your case by placing your user defined string after ISONAME= in that ini file.

(You must enter your required string there if you wish to change it, adding the iso extension shouldn't matter since the code is simply using the name without that extension as a replacement for what is currently reading HFSLIPCD, i.e. ISONAME=YOURSTRING in the ini file will produce an ISO with a name similar to this: YOURSTRING_07172009_13h15m.iso.

Quickly looking at the code, it appears as if adding any character after OVERWRITEISO= in the ini file should name the finished file with whatever you have entered as ISONAME= also in that file, i.e.
ISONAME=ChosenName.iso
OVERWRITEISO=1

Also bear in mind that it is simply a file name, if you are not happy with the date and time additions, you can simply rename the file when the script has finished producing it.

spinjector

Jul 18 2009, 03:33 PM

QUOTE (Yzöwl @ Jul 18 2009, 04:15 PM)

Also bear in mind that it is simply a file name, if you are not happy with the date and time additions, you can simply rename the file when the script has finished producing it.

True. I've already put a couple of little tweaks in; I'll just add a rename too. I used to be a BFF (batch file freak) and it's been a joy to wander through this thing.

~thanks

spinjector

Jul 18 2009, 03:35 PM

QUOTE (tommyp @ Jul 18 2009, 06:55 AM)

Is your file named hfanswer.ini? Or hfanswer.ini.txt? The file should be located in hftools, but you probably knew that anyway.

It's the right name in the right place.

Yzöwl

Jul 18 2009, 04:16 PM

QUOTE (spinjector @ Jul 18 2009, 10:33 PM)

QUOTE (Yzöwl @ Jul 18 2009, 04:15 PM)

Also bear in mind that it is simply a file name, if you are not happy with the date and time additions, you can simply rename the file when the script has finished producing it.

True. I've already put a couple of little tweaks in; I'll just add a rename too. I used to be a BFF (batch file freak) and it's been a joy to wander through this thing.

~thanks

QUOTE (Yzöwl @ Jul 18 2009, 09:15 PM)

Quickly looking at the code, it appears as if adding any character after OVERWRITEISO= in the ini file should name the finished file with whatever you have entered as ISONAME= also in that file, i.e.
ISONAME=ChosenName.iso
OVERWRITEISO=1

The renamed ISO is already catered for as above!

spinjector

Jul 18 2009, 05:28 PM

Ok thanks, I'll set the OVERWRITEISO= option as well...

jvidal

Aug 5 2009, 10:05 AM

BTW, your hfanswer.ini file has a ton of empty entries. i.e:
"mbootpath="
"Xpizesw="

If your not entering any value for those, you might as well remove them...

spinjector

Aug 5 2009, 01:49 PM

yea i downloaded the cookie-cutter hfanswer.ini from the web site and just changed the entries i wanted to use, and left it stock otherwise...

Martin H

Aug 6 2009, 02:44 AM

QUOTE (jvidal @ Aug 5 2009, 05:05 PM)

BTW, your hfanswer.ini file has a ton of empty entries. i.e:
"mbootpath="
"Xpizesw="

If your not entering any value for those, you might as well remove them...

No reason to do that IMHO... It dosen't hurt anything, and they're there if you need them later on...

spinjector

Aug 6 2009, 09:36 AM

QUOTE (Martin H @ Aug 6 2009, 04:44 AM)

No reason to do that IMHO... It dosen't hurt anything, and they're there if you need them later on...

Yes that was my understanding as well.

This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.