MSFN Forums: WIN51IP.SP3 left behind in my SOURCE folder? - MSFN Forums

Jump to content


Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

WIN51IP.SP3 left behind in my SOURCE folder? not being dumb i swear! =-) Rate Topic: -----

#1 User is offline   spinjector 

  • Member
  • PipPip
  • Group: Members
  • Posts: 104
  • Joined: 11-June 09

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.

Ad Bot #1 User is online   Sponsor Icon

  • Advert Bot
  • Group: Ad Bots
  • Posts: 0
  • Joined: --

Warn Status

Warning level: 0%

0
  • +
  • -

#2 User is offline   tommyp 

  • MSFN Addict
  • Icon
  • Group: Developers
  • Posts: 1,602
  • Joined: 09-January 04
  • Gender:Male
  • OS:none specified
  • Location:3 hours away from FDV
  • Country: Country Flag

Posted 13 July 2009 - 03:28 PM

The 2 byte identification sp3 file is normal and intended. Msft has been putting sp# filenames at the root directory of install CDs since w2k. When you slipstream a service pack with hfslip, it gets slipstreamed into the source folder.

#3 User is offline   Martin H 

  • Friend of MSFN
  • PipPipPipPipPip
  • Group: Members
  • Posts: 786
  • Joined: 24-November 06
  • Gender:Male
  • OS:none specified
  • Country: Country Flag

Posted 13 July 2009 - 03:34 PM

HFSLIP slipstreams the SP into the SOURCE folder.

Edit: Beaten by TommyP :)

This post has been edited by Martin H: 13 July 2009 - 03:35 PM


#4 User is offline   jvidal 

  • Advanced Member
  • PipPipPip
  • Group: Members
  • Posts: 319
  • Joined: 14-November 05
  • Gender:Male
  • Location:Santiago, Chile

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!

This post has been edited by jvidal: 30 July 2009 - 11:52 PM


#5 User is offline   spinjector 

  • Member
  • PipPip
  • Group: Members
  • Posts: 104
  • Joined: 11-June 09

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... =-)

#6 User is offline   jvidal 

  • Advanced Member
  • PipPipPip
  • Group: Members
  • Posts: 319
  • Joined: 14-November 05
  • Gender:Male
  • Location:Santiago, Chile

Posted 31 July 2009 - 04:35 PM

I have boot.bin in hftools, there's no need to copy it to the sourcess folder (totally useless).
Boot.catalog is not needed also.
thanks on the nologcopy tip, btw!

#7 User is offline   Martin H 

  • Friend of MSFN
  • PipPipPipPipPip
  • Group: Members
  • Posts: 786
  • Joined: 24-November 06
  • Gender:Male
  • OS:none specified
  • Country: Country Flag

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...)

#8 User is offline   spinjector 

  • Member
  • PipPip
  • Group: Members
  • Posts: 104
  • Joined: 11-June 09

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


#9 User is offline   jvidal 

  • Advanced Member
  • PipPipPip
  • Group: Members
  • Posts: 319
  • Joined: 14-November 05
  • Gender:Male
  • Location:Santiago, Chile

Posted 01 August 2009 - 01:48 PM

yeah, maybe that's it. I use mkisofs.
I'll try cdimage.

thx!

#10 User is offline   Martin H 

  • Friend of MSFN
  • PipPipPipPipPip
  • Group: Members
  • Posts: 786
  • Joined: 24-November 06
  • Gender:Male
  • OS:none specified
  • Country: Country Flag

Posted 01 August 2009 - 02:41 PM

Hmm, i just looked at the code quickly, and i don't understand why you have boot.bin in SOURCESS, since that shouldn't be possible:
HFTOOLS\mkisofs.exe %MKISSW% -b %BBIN% -o "%TEMPISO%" -V "%ISOTITLE%" %SOURCE%
	DEL/Q/F SOURCESS\BOOT.BIN


#11 User is offline   jvidal 

  • Advanced Member
  • PipPipPip
  • Group: Members
  • Posts: 319
  • Joined: 14-November 05
  • Gender:Male
  • Location:Santiago, Chile

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...

Attached File(s)


This post has been edited by jvidal: 02 August 2009 - 07:59 PM


Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic


1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users