MSFN Forum: Problem with driver merging, 'inf' files not found - MSFN Forum

Jump to content



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

Problem with driver merging, 'inf' files not found Rate Topic: -----

#1 User is offline   fdv 

  • MSFN Expert
  • Group: Developers
  • Posts: 1,099
  • Joined: 16-July 04
  • OS:Windows 7 x64
  • Country: Country Flag

Posted 21 August 2008 - 12:40 PM

OS: Win2k Server

I am getting a copyfiles error when I choose a merge driver CABs option (option C, if it matters).

The following files are the problem:
pvc.inf
icam3.inf
svc.inf

It must be noted that these three are the only three files in DRVINDEX.INF that end in "INF".

Prior to running HFSLIP, these files are found in DRVINDEX.INF under the [DRIVER] section. (I checked and they are in fact located in the DRIVER.CAB file).

After running HFSLIP, I checked the SOURCESS version of DRVINDEX.INF, and these file entries are gone entirely.

I checked this with HFSLIP versions 1.7.5 and 1.7.8. I have not noticed it previously in Win2k Pro. Clearly, something in HFSLIP is del'ing all "inf" file entries when it assembles DRVINDEX.INF after a merge option is selected.

Have not checked other merge options as option C is my all time favorite. Will check shortly but suspect this won't make a difference.

Edit: Checked non-merge option F and this problem does not occur.

This post has been edited by fdv: 21 August 2008 - 01:23 PM



#2 User is offline   tain 

  • Cyber Ops
  • Group: Super Moderator
  • Posts: 3,443
  • Joined: 24-September 05
  • OS:none specified
  • Country: Country Flag

Posted 11 April 2009 - 07:41 AM

Having similar, yet less consistent problem. With an XP SP3 OEM source, option C yields varying results including:
1. An OS that BSOD's on boot
2. Failed installs due to missing files (similar to FDV)
3. Failed install when the i386/SVCPACK/HFSLIP.CMD is invoked

Just changing to Option F is the medicine that makes it all better.

This is all with a bare bones HFSLIP config:

 
Host OS         - Windows XP

HFSLIP Version  - 1.7.9_beta_g, build 81223

HFSLIP Path     - C:\HFSLIPXP\

OS in SOURCESS  - Windows XP Professional SP3 English

Drivers         - DRIVER.CAB Updated

CD Install Path - Default

CDTAG           - WIN51

===============================================================================
Files in your HF folder:

Files in your HFCABS folder:
wbemoc.cab

Files in your HFGUIRUNONCE folder:

Files in your HFSVCPACK folder:

Files in your HFSVCPACK_SW1 folder:

Files in your HFSVCPACK_SW2 folder:

Files in your HFTOOLS folder:
BOOT.bin
CDIMAGE.EXE

Files in your HFCLEANUP folder:

Files in your REPLACE folder:

=============================================================================== 


#3 User is offline   tommyp 

  • MSFN Addict
  • Group: Developers
  • Posts: 1,664
  • Joined: 09-January 04
  • OS:none specified
  • Country: Country Flag

Posted 11 April 2009 - 12:14 PM

I can't seem to replicate this error. Can you post your hfslip.log on a case where you get this error? I may ask for you to provide your winnt.sif too to see what options you are enabling/disabling (less the SN of coarse).

#4 User is offline   tain 

  • Cyber Ops
  • Group: Super Moderator
  • Posts: 3,443
  • Joined: 24-September 05
  • OS:none specified
  • Country: Country Flag

Posted 11 April 2009 - 02:50 PM

Me? I think you must be talking to FDV. My log was in the codebox. And no /FIX files (WINNT.SIF) were used.

I think my problems may be coming from my SP3 OEM source. Most people slipstream SP3 so perhaps mine is a bit different since it is SP3 on the disc. I get really mixed results using both Options C and F. Hard to reproduce.

#5 User is offline   fdv 

  • MSFN Expert
  • Group: Developers
  • Posts: 1,099
  • Joined: 16-July 04
  • OS:Windows 7 x64
  • Country: Country Flag

Posted 11 April 2009 - 03:51 PM

This was so long ago and I stopped messing around with Server so I don't have a log.
This all works fine on Win2k Pro.

#6 User is offline   tain 

  • Cyber Ops
  • Group: Super Moderator
  • Posts: 3,443
  • Joined: 24-September 05
  • OS:none specified
  • Country: Country Flag

Posted 11 April 2009 - 03:53 PM

I'm still working on this. Might have some sort of actionable feedback soon. But I definitely get different results (working vs non-working) with the two options.

#7 User is offline   tain 

  • Cyber Ops
  • Group: Super Moderator
  • Posts: 3,443
  • Joined: 24-September 05
  • OS:none specified
  • Country: Country Flag

Posted 11 April 2009 - 04:37 PM

No actionable feedback :(

But it seems that setting DRIVERCOMP in HFANSWER.INI (whether C or F) yields less favorable results than manually entering C or F at the prompt. Something to do with how COMPMEM is set, perhaps?

I'm still curious if others have had better/worse luck with an OEM XP SP3 disc.

#8 User is offline   tommyp 

  • MSFN Addict
  • Group: Developers
  • Posts: 1,664
  • Joined: 09-January 04
  • OS:none specified
  • Country: Country Flag

Posted 11 April 2009 - 05:07 PM

Hmmm, that's weird. Tell me, on your sp3 oem disk, is there a driver.cab AND a sp3.cab or there only a driver.cab? I was testing this for a good part of the day and nada.

#9 User is offline   tain 

  • Cyber Ops
  • Group: Super Moderator
  • Posts: 3,443
  • Joined: 24-September 05
  • OS:none specified
  • Country: Country Flag

Posted 11 April 2009 - 05:09 PM

Both cabs exist in \i386.

Share this topic:


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



All trademarks mentioned on this page are the property of their respective owners
Copyright © 2001 - 2011 msfn.org
Privacy Policy