Page 1 of 1
WIN51IP.SP3 left behind in my SOURCE folder? not being dumb i swear! =-)
#1
Posted 13 July 2009 - 03:05 PM
I've just noticed that if I use HFSLIP to slipstream SP3 into my SP2 source, it leaves a copy of the WIN51IP.SP3 file in the SOURCE folder, as well as the SOURCESS folder.
Is this normal/intended..?
SP3 isn't slipstreaming into my source, is it? Doesn't look like it to me, but thought I should ask.
I tried searching the forum for an answer but got wayyy to many search results to make heads, tails, or toes of it. =-)
Thanks.
Is this normal/intended..?
SP3 isn't slipstreaming into my source, is it? Doesn't look like it to me, but thought I should ask.
I tried searching the forum for an answer but got wayyy to many search results to make heads, tails, or toes of it. =-)
Thanks.
#4
Posted 30 July 2009 - 11:50 PM
since we're talking about leftovers, why does hfslip leave some unneeded files in the sourcess root folder?
As far as i recall, the're boot.catalog, boot.bin and hfslip.log.
These files shouldn't be there...I always delete them, and never had any trouble.
hfslip.log is also stored in hfslip's root folder and the other two are absolutely unneeded.
bye!
As far as i recall, the're boot.catalog, boot.bin and hfslip.log.
These files shouldn't be there...I always delete them, and never had any trouble.
hfslip.log is also stored in hfslip's root folder and the other two are absolutely unneeded.
bye!
This post has been edited by jvidal: 30 July 2009 - 11:52 PM
#5
Posted 31 July 2009 - 09:00 AM
NOLOGCOPY=1 in your HFTOOLS\HFANSWER.INI file to stop the log from being copied to the SOURCESS folder.
and
The BOOT.BIN is are used to burn a bootable Winblow$ Setup CD if you have mk-whatsit or CDIMAGE in your HFTOOLS\ folder. If I remember correctly, BOOB.BIN is created under the following circumstances: BBIE.EXE is in your HFTOOLS\ folder, and an original Windows Setup CD is in your CD drive. BBIE sucks the boot sector from the CD as BOOT.BIN and saves it for whatever burning software is used to make the resulting CD bootable.
Not sure what BOOT.catalog is tho; might be something to do with a multiboot-CD. I haven't ventured into that territory yet. One brain-cramping project per month please... =-)
and
The BOOT.BIN is are used to burn a bootable Winblow$ Setup CD if you have mk-whatsit or CDIMAGE in your HFTOOLS\ folder. If I remember correctly, BOOB.BIN is created under the following circumstances: BBIE.EXE is in your HFTOOLS\ folder, and an original Windows Setup CD is in your CD drive. BBIE sucks the boot sector from the CD as BOOT.BIN and saves it for whatever burning software is used to make the resulting CD bootable.
Not sure what BOOT.catalog is tho; might be something to do with a multiboot-CD. I haven't ventured into that territory yet. One brain-cramping project per month please... =-)
#7
Posted 01 August 2009 - 09:56 AM
I did a quick google search, and boot.catalog is related to mkisofs, and so you have the option of using cdimage.exe instead, and with that, then hfslip dosen't add anything extra into the sourcess folder for making an iso(however, mkisofs just writes the file to the first sector of the iso, which becomes the boot-block when burned to disc, and dosen't add it into the main root of the iso, just like cdimage.exe)...
(Personally, then i feel that there's no reason to use a non-win32-native tool compiled with mingw or cygwin, when theres a perfectly fine native win32 tool available in cdimage.exe; but that's just me, and not that there's anything wrong with Jörg Schilling's cdrecord suite of tools at all...)
(Personally, then i feel that there's no reason to use a non-win32-native tool compiled with mingw or cygwin, when theres a perfectly fine native win32 tool available in cdimage.exe; but that's just me, and not that there's anything wrong with Jörg Schilling's cdrecord suite of tools at all...)
#8
Posted 01 August 2009 - 11:46 AM
i prefer/use cdimage as well... i couldn't find the right version of mkisofs, nor make the versions i did find to work... when i started using cdimage, it worked perfectly the first time, so that's what i stuck with...
This post has been edited by spinjector: 01 August 2009 - 11:47 AM
#11
Posted 02 August 2009 - 07:54 PM
Well, it seems something is not quite right then, because IT IS THERE (I'm not making it up...why would I?).
Anyway, after switching to cdimage.exe and adding "NOLOGCOPY=1" to hfanswer.ini, none of those 3 files are present now (just like it should be).
oh, PD: just before starting the iso building process (Or is it after??? not sure right now), I see a "file not found" error mesage in the DOS BOX.
I have always ignored it. since everything works just fine.
bye!
In case you're wondering, check out my log...
Anyway, after switching to cdimage.exe and adding "NOLOGCOPY=1" to hfanswer.ini, none of those 3 files are present now (just like it should be).
oh, PD: just before starting the iso building process (Or is it after??? not sure right now), I see a "file not found" error mesage in the DOS BOX.
I have always ignored it. since everything works just fine.
bye!
In case you're wondering, check out my log...
Attached File(s)
-
HFSLIP.zip (1.13K)
Number of downloads: 0
This post has been edited by jvidal: 02 August 2009 - 07:59 PM
Page 1 of 1

Sign In
Register
Help


MultiQuote



Report