Today I found my SOURCESS folder after nLite was definitely too big.
117MB !

I would have been happy but a clean XP -SP0- goes down to 110MB.
Of course, I add functionnalities with SP1 and other updates but 7MB is IMO too much.

I compared files present with and without HFSlip in I386 after nlite and I found that some or rather many DirectX files are present in both I386 and driver.cab. I think this should be cleaner.
And it seems it also happens with other files (ntkrnl*.exe)

Files in driver.cab and directly in i386 seem to have the same version but I'm not 100% positive.


PS: I used "dir /S /B >> dir.txt". If needed, I can provide those listings.

I made a quick and maybe dirty AHK app:


You need to extract driver.cab somewhere.
Then, at the second dialog, enter the folder you extracted driver.cab to and select all files (ctrl+A).


I have 2.2MB of duplicates in my nlited SOURCESS.

NB: ntkrnlmp.exe has to be in I386.



http://sharpnet.ai-network.net/camarade/duplicates.exe
(don't, at least for the moment, it will go public and legal [I hope] later)

Are DirectX and Windows Installer slipstreamable ?

yes, i don´t have any problem. HFSLIP is good slipstreamable tool. (win2k).

Yes. DirectX CABs go in HFCABS (only the *d3dx9* ones) and Windows Installer goes in HF.

@Camarade_Tux

Yes, there are a couple of dupes. It's just that so far nobody ever tried to figure out which files can be deleted and which not. There are several files that have to be both in SOURCESS\I386 and in DRIVER.CAB/SPX.CAB. It's very time consuming to check this for all OS versions and all SP levels so it's not really "top priority".

FYI, Nlite doesn't remove some things when selected. I'm not sure if this is by design or what. I have asked Nuhi a bunch of times to remove some additional files, but the requests fell of deaf ears (or maybe eyes). This is why I created HFCLEANUP. With HFCLEANUP, I can create a ultra slim and updated 2k with no need for nlite. Total duration is about about 8 minutes. . It was my answer to fixing a fully slipstreamed 2k with the least amount of keystrokes and programs to install on my system. HFCLEANUP can be tailored to XP too, a majority of the reducers can be used on 2k/xp/2k3 at this point. All I can say is that if you won't need something in your source, don't slipstream it in the first place. For example, why slipstream wmp10 and then remove it with nlite? Seems foolish IMO.

Also, FWIW, an NLITEd HFSLIP works best when selecting the merged cabs (A, B or C). This will eliminate a bunch of dupes in the cabs and produces the smallest footprint i386 folder.

Camarade_Tux - OT - What is your favorite flavor of linux?

Just to be sure that we're on the same page... Camarade_Tux correctly noticed that all new driver cab binaries are copied "loose" into SOURCESS\I386 as well even though some of them (possibly the majority) don't have to be. HFSLIP doesn't delete them from the working folder after they are added into DRIVER.CAB or SPX.CAB.

Quickly, with only SP1 slipstreamed (will check with no SP slipstreamed later):

• Files in driver.cab AND in i386
  CODE
  acpi.sys
  acpiec.sys
  adpu160m.sys
  aha154x.sys
  aic78u2.sys
  aic78xx.sys
  aliide.sys
  amsint.sys
  asc3350p.sys
  asc3550.sys
  asc.sys
  atapi.sys
  binlsvc.dll
  cbidf2k.sys
  cd20xrnt.sys
  cdrom.sys
  cmdide.sys
  cpqarray.sys
  dac2w2k.sys
  dac960nt.sys
  disk.sys
  dpti2o.sys
  fdc.sys
  flpydisk.sys
  ftdisk.sys
  hal.dll
  halaacpi.dll
  halacpi.dll
  halapic.dll
  halmacpi.dll
  halmps.dll
  halsp.dll
  hidclass.sys
  hidparse.sys
  hidusb.sys
  
  
• Files present in i386 AND in sp1.cab
  
  CODE
  1394bus.sys
  acpi.sys
  atapi.sys
  ati2dvaa.dll
  ati2dvag.dll
  ati2mtaa.sys
  ati2mtag.sys
  ati3d1ag.dll
  ati3d2ag.dll
  atinbtxx.sys
  atinmdxx.sys
  atinpdxx.sys
  atinraxx.sys
  atinrvxx.sys
  atinsnxx.sys
  atinttxx.sys
  atintuxx.sys
  atinxbxx.sys
  atinxsxx.sys
  cdrom.sys
  disk.sys
  dxg.sys
  flpydisk.sys
  hal.dll
  halaacpi.dll
  halacpi.dll
  halapic.dll
  halmacpi.dll
  halmps.dll
  hccoin.dll
  hidclass.sys
  hidir.sys
  i8042prt.sys
  imapi.sys
  intelide.sys
  irbus.sys
  kbdclass.sys
  mrxsmb.sys
  mutohpen.sys
  ntkrnlmp.exe
  ntoskrnl.exe
  ohci1394.sys
  pci.sys
  pciidex.sys
  pcmcia.sys
  sbp2port.sys
  scsiport.sys
  serial.sys
  sfloppy.sys
  tffsport.sys
  usbccgp.sys
  usbehci.sys
  usbhub.sys
  usbohci.sys
  usbport.sys
  usbstor.sys
  usbuhci.sys
  viaide.sys
  wacompen.sys

It seems SP1 itself adds lots of duplicates.

This post has been edited by Camarade_Tux: May 7 2006, 02:06 AM

See how difficult it is?

I just wanted to make my list complete :
Duplicates on a DELL XP SP0 CD:


I'll see what can be removed, probably next week.


And my favorite flavor of Linux is ... the one that lets me use my Radeon mobility X700 on my 16/10 screen at its native resolution.
I used to run SuSe. I sucked my install and could not install again because of *dead* HD.

I don't intend to mess with the duplicates that MS add themselves; they might be in I386 for a purpose. What I'm going to try to achieve with HFSLIP:

- updated binaries should be in DRIVER.CAB (as is the case now)
- updated binaries for driver files that co-exist in I386 should be updated (as is the case now)
- updated binaries for driver files that only existed in DRIVER.CAB previously should NOT be added into I386 (this behavior would be new)
- binaries for driver files that didn't exist at all should only be added into DRIVER.CAB unless they are required in I386 (this behavior would be new)

The above is for merging options A/B/C. With the other merging options, the cab file to deal with is SPX.CAB.

Tux - You can do delete these extras with a RIN file in HFCLEANUP. Read up on the hfexpert page to see how to do it. You'll need to do a driver merge option to take advantage of the reduction. Hint on the file creation...

1394bus.sy
1394vdbg.sy
abp480n5.sy
acpi.sy
acpiec.sy
etc

Tomcat76, I think those added files may be needed for recovery console or things like that so I'm with you on not removing them by default. But who really knows what is their use ?

tommyp, I had not yet checked HFCLEANUP and it seems really powerful. Thanks.