LeveL

Yeah the WIM image is a bit bigger, for example if you do this: Run the image through vLite (just do a tweak or two) Mount the image with imagex.exe Remove files from "Windows\winsxs\Backup" Unmount the WIM image Then it does end up a tiny bit bigger, run it through vLite and it ends up about the size it was, so what I am saying is, I can remove every file inside "Windows\winsxs\Backup" and still the image is no smaller which means all those files are duplicated somewhere, they have to be, its something like 350Mb of files, compressed thats got to amount to what, at least 50Mb of space in the WIM image or something, I mean you'd lose SOME Mb's off the WIM image from deleting 350Mb worth of files but the image stays the same size. Nevermind, I am going to integrate all hotfixes into a fresh copy of Vista, then mount the image and use this handy (free) tool to see if those files in "Windows\winsxs\Backup" are duplicated, they must be, if they're not then I will go bonkers!

Did that work? Yes it did work - sort of... When a WIM image is unmounted, it stores duplicate files only once in the WIM image. Thats how you can have Home, Standard, Business etc all lumped into one DVD and its under 3Gb. I did manage to delete the 1700 or so files in "Windows\winsxs\Backup" and the OS installs fine, but doing that saves no space at all on the ISO, meaning all those files are duplicated somewhere, maybe not the same file names, but the checksums will be the same, so I guess the Backup folder files themselves have backups somewhere! Typical Microsoft, backup of a backup of a backup of a backup.

I am guessing the files are in C:\WINDOWS\winsxs\Backup but I cannot delete anything in there, even after giving myself full control on the permissions for the folder and removing all attributes. Thats on an installed Vista though, I am going to try to delete them all in the WIM image so they never appear there to start with.

A function to stop Windows making hotfix backups in WinSXS. So without this ability to uninstall hotfixes, you would not be able to uninstall hotfixes, but would save a lot of space. I posted about this here: http://www.msfn.org/board/Slipstreaming-Ho...mp;gopid=712704 Apparently the size of the ISO only increases when integrating hotfixes because it makes backups of the older files. Pfffff! I don't want to ever uninstall any hotfixes and don't want all those backup files although I searched WinSXS for the KB numbers of a few hotfixes and none of them appear anywhere.

Thanks, this explains it. Now I guess my mission is to find out how to not include the uninstall functionality. It could even be a suggestion for vLite perhaps? To switch on or off the option to be able to uninstall the hotfixes. I know I don't need those Greek or Czech fixes but Windows Update will say I need them if I don't include them! I guess its probably possible to: 1 - Mount the WIM image after using vLite. 2 - Removing all the hotfix backup files from the WinSXS folder. 3 - Reseal the WIM image. WinSXS though... thats no mans land, its so packed with folders with massive long names etc, okay here goes...

Might be the ACPI. When you boot off a Windows disc and it is flashing through all the files bottom left (loading files) press F5 and choose "Standard PC". Its just a suggestion but I have had Windows 2000 freeze on me in VMware for like 20 or 30 minutes before it decides it can work. What you describe sounds more like a Hardware Abstraction Layer problem rather than booting off the disc because from what I gather you can actually boot from a disc, its the part of setup after that thats the problem? "setup inspects my hardware configuration then hangs for 10 mins or so" yep, sounds like the HAL is screwy, but choosing "Standard PC" works.

In this folder: C:\Documents and Settings\All Users\Application Data\Microsoft\User Account Pictures\ You have these files: Administrator.bmp guest.bmp In this folder: C:\Documents and Settings\All Users\Application Data\Microsoft\User Account Pictures\Default Pictures\ You have these files: airplane.bmp astronaut.bmp ball.bmp beach.bmp butterfly.bmp car.bmp cat.bmp chess.bmp dirt bike.bmp dog.bmp drip.bmp duck.bmp fish.bmp frog.bmp guitar.bmp horses.bmp kick.bmp lift-off.bmp palm tree.bmp pink flower.bmp red flower.bmp skater.bmp snowflake.bmp All these files are the same size - 48 x 48 pixels. So if you're doing an unattended install and put a BMP image here: CD-ROM:\$OEM$\$Docs\All Users\Application Data\Microsoft\User Account Pictures\myimage.bmp And leave all others out, Windows might just choose that one image (it seems that it randomly chooses images). I guess theres a reg setting though so if you wanted to, you could have like 4 users all with their own pic there. Of course this is all normally done after Windows has installed. If you're not doing unattended, you'd have to xcopy the file after install somehow, you'd still probably need a winnt.sif file even if it only has the command at the end to run the CMD file but duh... then you might as well have an $OEM$ distribution folder on the CD, OK I will shut up now.

It seems like the days of slipstreaming dozens upon dozens of hotfixes into Windows and the ISO size remaining (virtually) the same are gone, with Windows XP in nLite this was no problem. I used to throw in a ridiculous amount of hotfixes like 120 or 130 and the ISO increased by only 0.02Mb! Lets face it thats twenty kilobytes and so its irrelevent to even count that as a size increase IMO. But around May/June when I was only slipstreaming say 5 or 10 hotfixes into Windows Vista with vLite, I could just about squeeze the OS on a 700Mb ISO without removing any services, IE7 or WMP11, in fact I managed to even keep "Windows Mail" after removing the files from the sources folder fro an upgrade (at the time vLite did not do this) but now, I strip EVERY last thing out of Vista in vLite (for test purposes, I would never use a fully stripped one) and slipstream all 95 hotfixes and end up with an ISO thats way oversized like 900Mb or something! All these: Windows6.0_KB932471_v2_x86.msu Windows6.0-KB905866-v12-x86.msu Windows6.0-KB905866-v13-x86.msu Windows6.0-KB925528-x86.msu Windows6.0-KB925902-x86.msu Windows6.0-KB927084-x86.msu Windows6.0-KB928089-x86.msu Windows6.0-KB928439-x86.msu Windows6.0-KB929123-x86.msu Windows6.0-KB929399-x86.msu Windows6.0-KB929427-x86.msu Windows6.0-KB929451-x86.msu Windows6.0-KB929547-v2-x86.msu Windows6.0-KB929615-x86.msu Windows6.0-KB929685-x86.msu Windows6.0-KB929735-x86.msu Windows6.0-KB929761-x86.msu Windows6.0-KB929762-x86.msu Windows6.0-KB929763-x86.msu Windows6.0-KB929777-v2-x86.msu Windows6.0-KB929824-v2-x86.msu Windows6.0-KB929916-x86.msu Windows6.0-KB930163-x86.msu Windows6.0-KB930178-x86.msu Windows6.0-KB930194-x86.msu Windows6.0-KB930585-x86.msu Windows6.0-KB930857-x86.msu Windows6.0-KB930955-x86.msu Windows6.0-KB931099-x86.msu Windows6.0-KB931174-x86.msu Windows6.0-KB931213-x86.msu Windows6.0-KB931573-x86.msu Windows6.0-KB931621-x86.msu Windows6.0-KB931671-x86.msu Windows6.0-KB931768-x86.msu Windows6.0-KB931836-x86.msu Windows6.0-KB932246-x86.msu Windows6.0-KB932385-x86.msu Windows6.0-KB932406-x86.msu Windows6.0-KB932590-x86.msu Windows6.0-KB932637-x86.msu Windows6.0-KB932638-x86.msu Windows6.0-KB932649-v3-x86.msu Windows6.0-KB932818-x86.msu Windows6.0-KB932988-x86.msu Windows6.0-KB933360-x86.msu Windows6.0-KB933566-x86.msu Windows6.0-KB933579-x86.msu Windows6.0-KB933590-x86.msu Windows6.0-KB933612-x86.msu Windows6.0-KB933729-x86.msu Windows6.0-KB933872-x86.msu Windows6.0-KB933928-x86.msu Windows6.0-KB935280-x86.msu Windows6.0-KB935652-x86.msu Windows6.0-KB935807-v2-x86.msu Windows6.0-KB935855-x86.msu Windows6.0-KB936004-x86.msu Windows6.0-KB936021-x86.msu Windows6.0-KB936150-x86.msu Windows6.0-KB936357-x86.msu Windows6.0-KB936710-x86.msu Windows6.0-KB936782-x86.msu Windows6.0-KB936824-x86.msu Windows6.0-KB936825-x86.msu Windows6.0-KB937077-x86.msu Windows6.0-KB937123-v2-x86.msu Windows6.0-KB937143-x86.msu Windows6.0-KB938123-x86.msu Windows6.0-KB938126-v3-x86.msu Windows6.0-KB938127-x86.msu Windows6.0-KB938194-x86.msu Windows6.0-KB938637-x86.msu Windows6.0-KB938929-x86.msu Windows6.0-KB938952-x86.msu Windows6.0-KB938979-x86.msu Windows6.0-KB939159-x86.msu Windows6.0-KB939165-x86.msu Windows6.0-KB939653-x86.msu Windows6.0-KB939778-x86.msu Windows6.0-KB939786-v3-x86.msu Windows6.0-KB940069-x86.msu Windows6.0-KB940105-x86.msu Windows6.0-KB940646-x86.msu Windows6.0-KB940716-x86.msu Windows6.0-KB941090-v2-x86.msu Windows6.0-KB941202-x86.msu Windows6.0-KB941229-v2-x86.msu Windows6.0-KB941229-x86.msu Windows6.0-KB941542-x86.msu Windows6.0-KB941600-x86.msu Windows6.0-KB941651-x86.msu Windows6.0-KB942089-x86.msu Windows6.0-KB942813-v3-x86.msu Windows6.0-KB942903-x86.msu Windows6.0-KB943544-x86.msu Theres also a few others you have to mess about with to do, that are exe files (BitDefender Update, Windows Update "update" and MSRT), also Windows6.0-KB941649-v2-x86.msu although its a MSU file, does not get slipstreamed by vLite, at least Windows Update claims I need that one after installing, even though i did slipstream it in vLite, heard a lot of people with serious problems with that update, namely unescapable BSOD's (in safe mode!) etc. I just had to silently install it afterwards with /quiet /norestart and its fine. MS have probably fixed the problems it had now. So - these hotfixes ARE increasing the ISO size by a lot! Its a shame because I used to be able to squeeze Vista onto a 700Mb CD without really losing anything important, now you cannot even strip it completely and fit it on a CD if its got all hotfixes included. You can't win(dows). Note: These two hotfixes are absolutely massive; Windows6.0-KB932637-x86.msu (87.6mb) Windows6.0-KB932638-x86.msu (95.4Mb) KB932637 is a language fix for Czech KB932638 is a language fix for Greek I wonder if its mainly because of these two massive updates (183Mb for just those 2) that its increasing the ISO size so much? There another big one: Windows6.0-KB941229-v2-x86.msu (16.9Mb) After this they range from 10Mb down to 139Kb.

The final vLite will probably be made before Server 2008 is even officially released. Nuhi you do SO much man. Server 2008 isn't even out for months yet and you're talking about vLite final.

That is a bloody good point aviv00, or at least a good suggestion, since vLite is only in beta, maybe Nuhi has not yet coded this into it, but (and I am no C# coder) I am sure if theres no component there to select, vLite cannot possibly remove things like that (Aero, WMP11).

I tested this and it does indeed work. Sorry if you wasted time reading the 1st post. At least anyone finding this thread knows how easy it is to do now.

Is it possible to add a folder to the root of your Windows drive when Vista installs? The way I am doing it is like this: 1 - Use imagex.exe to mount the "install.wim" image. 2 - Copy the folder to the root of the mount folder. 3 - Unmount the image with imagex.exe and use the /commit command. It does add the folder into the WIM image, but will this folder thats added end up on the root of the Windows drive, or do I also have to add the folder name to a file somewhere?

Why, x86 also has the Driver Signing Policy! I should know, it popped up about sixty million times after I tried to integrate drivers into the DVD. I hate this OS.

True, but this does not make the unsigned driver popup appear. That only appears because of unsigned drivers. A few members @ driverpacks.net are already using a makeshift BASE to slipstream the packs, I just tried it with vLite since its a lot more advanced (I mean its fully implemented in vLite and is official) than the makeshift one a few people have tried and succeeded with. I only gave up with that because no one has answered the question there about why the Vista BASE slipstreamer is asking for a "Drivers.xml" file. What the hell is that? "Drivers.xml" There is no such file in the mounted image, or anywhere. So wait... if I somehow remove all the drivers that are not WHQL signed, it can't ever popup asking abou tthat, right? because all the CAT files are there for the drivers? All I gotta do now is find some way to show only the folders in a search that do not have a CAT file in the folder! Searching is easy but NOT searching, sheesh...

So, I extracted all Bashrats driverpacks and integrated all these with vLite. When Windows Vista is installing, I get the annoying popup saying the driver is not signed. Has anyone found any solution to this yet? I clicked "Install anyway" 20 times and left it a while. After about 10 minutes of leaving the 21st popup there, it just rebooted and finished installing but skipped out all my post install scripts! So I guess you have to sit there clicking the popup over and over and over again huh? There are many people asking about this and I have not found any solution. A good idea I saw was to make a "fake" certificate for every driver to make Vista think it is a legitimate (digitally signed) driver. Microsoft are just complete suckers for doing this - 99% of those drivers in Bashrats packs are unsigned, if you were to remove all the unsigned drivers, there would be no drivers left! I have looked through all 24 pages of topic titles for the answer to this, no one seems to have any answer. Nuhi says over and over again just click the popup... http://www.msfn.org/board/index.php?s=&amp...st&p=691943 http://www.msfn.org/board/index.php?s=&amp...st&p=685236 http://www.msfn.org/board/index.php?s=&amp...st&p=679974 http://www.msfn.org/board/index.php?s=&amp...st&p=672116 http://www.msfn.org/board/index.php?s=&amp...st&p=654277 http://www.msfn.org/board/index.php?s=&amp...st&p=641411 http://www.msfn.org/board/index.php?s=&amp...st&p=619442 So I guess there is no fix for this yet? Why do people keep asking about x64 when it happens on x86 as well? Like I said, I got 20 popups and just stopped clicking it after that, then Windows carried on installing, none of the drivers (Ethernet + Sound) worked (VMware) BTW I did not even remove any components, its a complete install.

OK thanks for the quick reply. Well, I integrated 92 hotfixes into the "Ultimate" version and the source folder went from 2.52GB to 2.84GB. So it added 320Mb. So if I add these to the "Enterprise" and "Home" etc it adds 320Mb each time, holy schmidt!!! Think I better just make a disc thats just the Ultimate version on its own... I guess if you have that version it kinda negates all the other versions since it does absolutely everything all the other versions do (and more).

When you use vLite, lets say just to integrate hotfixes... it only gives the choice of adding them to one version of Vista (on the Ultimate DVD) so do you have to go through every single choice to add the hotfixes to all the choices?

On your CD or DVD, if you include all current Bashrat driverpacks (no 3rd party Driverpacks) like so... DPC710.7z DPCP7041.7z DPGA710.7z DPGB710.7z DPGC7091.7z DPL7091.7z DPM708.7z (Not the latest) DPSA710.7z DPSB710.7z DPW7092.7z The OEM folder will take up 282Mb on the CD or DVD. Then add about 4Mb for MassStorage drivers added to I386. Just allow 300Mb and you'll be fine, which means you have to get Windows to under 400Mb. Just use nLite and remove the Tour, MSN Explorer, Administrative Tools pack... theres a lot of useless stuff you can remove and get it to under 400mb. I have a fully functional ISO thats about 200Mb, half the size! Unless you speak about 25 languages, those are the first to go... then you can get away with adding IE7 and WMP11 as an "addon" in nLite, and also slipstream hotfixes etc... its all easily possible to fit inside 700Mb.

This is an awesome program, but I am having problems configuring it. I have tried various combinations with the XML settings, sometimes the Found New Hardware wizard comes up asking for files like "sbsetup.exe" (Sound Blaster file) and other times, this doesn't pop up but it seems no drivers install. I am using Bashrats driverpacks, so no drivers are compressed (all are broken down to their SYS and INF files, the driverpacks 7z files are already decompressed off the CD and onto the hard drive with the RELATIVE setting in the XML config file and a pre-prepared folder full of drivers. I have always used the SetupCopyOemInf method because I know using all Bashrats driverpacks goes well over the 4096 character limit for the Registry. Still, I don't think my XML file is right! If anyone else is using Bashrats packs and this program, can you please post your XML file in code tags? It doesn't matter if your path to the driver folder is different to what I would use - my main problem is... not knowing if devices are installing, because I am testing in VMware and it always has a perfect Device Manager with no devices that need any drivers installing! I don't know if the XML should have the "forced" setting on "Yes". I think when I set that, devices do install but I get the Found New Hardware wizard popping up... eeeeek! Can anyone post an XML configuration that they KNOW is tried and tested with Bashrats (unpacked) drivers? Well, here is what I think is my final XML file but I still don't know if drivers are installing. I will have to try to set the time aside to do a real install on my real system and do it for real... <?xml version="1.0" encoding="utf-8"?> <settings> <basic_configuration> <choice>automatic</choice> <drivers> <drivers_drive>RELATIVE</drivers_drive> <drivers_directory>\D</drivers_directory> <drivers_packed>No</drivers_packed> <drivers_copy>No</drivers_copy> <drivers_copy_path></drivers_copy_path> <drivers_copy_delete>No</drivers_copy_delete> <options> <method>SetupCopyOemInf</method> <registry_path>Begin</registry_path> <problem_ids>01,10,18,24,28,37,39</problem_ids> <update_all>No</update_all> <plug_and_play> <option>Internal</option> <time_to_wait>15</time_to_wait> </plug_and_play> <shutdown> <auto_reboot_when_nessecary>No</auto_reboot_when_nessecary> <auto_reboot_when_done>No</auto_reboot_when_done> <auto_login>Yes</auto_login> <notify_when_done>Yes</notify_when_done> </shutdown> <time_to_run>0</time_to_run> <force_run>No</force_run> <device_manager>No</device_manager> </options> </drivers> <log> <log_overwrite>No</log_overwrite> <log_to_file>Yes</log_to_file> <log_filename>hardware.log</log_filename> <log_path>$ProgramDir</log_path> <log_option>Simple</log_option> </log> <gui> <hide_legacy_devices>No</hide_legacy_devices> <fade_in_effect>No</fade_in_effect> </gui> </basic_configuration> </settings>

OK, this is tough to work out - I stripped a lot of stuff out of Windows... ... but nevermind all that - all I want to ask is, how do these 2 folders get created when Windows installs: %ProgramFiles%\Windows Media Player %ProgramFiles%\Internet Explorer If the question was "How does system32 get created" the answer would be: In I386 there is a file "TXTSETUP.SIF". Open this with Notepad and VOILA! there it is under [WinntDirectories] like so: [WinntDirectories] 1 = "\" 2 = system32 3 = system32\config 4 = system32\drivers 5 = system 7 = system32\ras 9 = system32\spool 10 = system32\spool\drivers 11 = system32\spool\drivers\w32x86\3 12 = system32\spool\prtprocs 13 = system32\spool\prtprocs\w32x86 14 = system32\wins 15 = system32\dhcp 16 = repair 17 = system32\drivers\etc 18 = system32\spool\drivers\w32x86 19 = system32\drivers\disdn 20 = inf 21 = Help 22 = Fonts 23 = Config 24 = msagent\intl 25 = Cursors 26 = Media This is as the section implies "WINNT" directories (its called "WINDOWS" in XP, WINNT is from Windows 2000 but I guess Microsoft just skimped a bit here and called the section in the TXTSETUP.SIF file for XP "[WinntDirectories]") So thats it man, all this refers to is Windows directories, theres no mention of "Documents and settings" or "Program Files" so how are THOSE folders created? Totally perplexed as to how Windows makes these folders.

When something is posted here in code tags like in this post: http://www.msfn.org/board/index.php?s=&amp...st&p=635349 What file is that code meant to be in and where is the file?! I am having a nightmare trying to dual boot Knoppix (DSL) with Slax using cdshell. The problem is that cdshell already comes with an isolinux folder and isolinux.cfg, if you put Knoppix in it works but when I add Slax to it (under its own boot folder) even when cdshell.ini points to the slax BIN file it still boots DSL! Heres the post explaining it: http://www.msfn.org/board/index.php?s=&amp...st&p=685537

AAAAAAAAAGH! OK now thats over with, heres the problem: I want to multi-boot Slax (the live one from HERE along with DSL from HERE) I am using cdshell.ini to chain these. The problem is, whatever I do it is always booting into DSL! The Slax CD comes with 2 folders "boot" and "slax". I put the Slax folder on the root of my multi-boot CD. (Knoppix is already there for DSL) Now, to boot DSL, I did not have to modify anything, it just worked with the command in cdshell.ini saying this: if $lastKey == key[1]; then bcdw Boot isolinux\isolinux.bin So, I made a sub-directory INSIDE the multi-boot CD's BOOT folder called "slax" and inside that slax folder, I put all the slax boot files. So, this slax comes with its own "isolinux.cfg" file in its own isolinux folder. I have altered all the options in this "isolinux.cfg" file, where it used to say for example "KERNEL /boot/vmlinuz" it now says "KERNEL /boot/slax/vmlinuz" because what used to be the "boot" folder for the Slax CD is now "BOOT/slax" on the multi-boot CD. So my isolinux.cfg file (now inside "boot/slax") is like so: PROMPT 0 TIMEOUT 200 DEFAULT /boot/slax/vesamenu.c32 LABEL xconf MENU LABEL Slax Graphics mode (KDE) KERNEL /boot/slax/vmlinuz APPEND vga=769 initrd=/boot/slax/initrd.gz ramdisk_size=6666 root=/dev/ram0 rw autoexec=xconf;kdm LABEL pchanges MENU LABEL Slax Graphics mode with Persistent Changes KERNEL /boot/slax/vmlinuz APPEND vga=769 initrd=/boot/slax/initrd.gz ramdisk_size=6666 root=/dev/ram0 rw changes=/slax/slaxsave.dat autoexec=xconf;kdm LABEL copy2ram MENU LABEL Slax Graphics mode, Copy To RAM KERNEL /boot/slax/vmlinuz APPEND vga=769 initrd=/boot/slax/initrd.gz ramdisk_size=6666 root=/dev/ram0 rw copy2ram autoexec=xconf;kdm LABEL startx MENU LABEL Slax Graphics VESA mode (1024x768) KERNEL /boot/slax/vmlinuz APPEND vga=769 initrd=/boot/slax/initrd.gz ramdisk_size=6666 root=/dev/ram0 rw autoexec=kdm LABEL slax MENU LABEL Slax Text mode KERNEL /boot/slax/vmlinuz APPEND vga=normal initrd=/boot/slax/initrd.gz ramdisk_size=6666 root=/dev/ram0 rw LABEL memtest86 MENU LABEL Run Memtest utility KERNEL /boot/slax/mt86p All I have changed is where it used to say /boot it now says /boot/slax Problem is - even though I am linking cdshell.ini directly to the isolinux.bin file inside "boot/slax" like this: if $lastKey == key[2]; then bcdw Boot slax\isolinux\isolinux.bin It is STILL booting DSL! How the hell can it possibly?! The isolinux.cfg file I have put above there in code tags IS next to the isolinux.bin file I am linking to in cdshell.ini - how can it still boot DSL? Help, please, I have tried this so many ways now and nothing works!

Yes, they are all still there in I386. At one point I even added the HFSLPxxx.INF files to the advanced box in nLite, just to make certain they were kept, but they were all kept anyway. Yes. This is whats so strange. The [WinntDirectories] section still lists 999 = HFSLIP too! I have managed to work around it by just removing the line in HFSLIP.CMD that does RD /Q /S %SYSTEMROOT\HFSLIP and simply removing the HFSLIP folder later on when Windows logs in (its unattended so it always had a few apps installing and tweaks after install) Here's the log: HFSLIP_LOG.zip

Here's what I did: 1 - Got XP with SP2 already slipstreamed as my source. 2 - Put all the hotfixes and other files in the relevant folders. 3 - Ran HFSLIP (v1.6.2) 4 - Stripped WMP and IE out with nLite. (I added all the files from HERE to the advanced box in nLite) 5 - Tried to install the OS and got a message saying it cannot find C:\WINDOWS\HFSLIP\HFSLP200.INF (It says this for the #200 all the way to the last file #281) if I get past the 81 errors, Windows installs fine after this. I realized the problem - in the file I386\SVCPACK\HFSLIP.CMD it says: RD/Q/S %SYSTEMROOT%\HFSLIP So I put REM in front like this: REM RD/Q/S %SYSTEMROOT%\HFSLIP Tested the ISO again and its fine. I don't know why the HFSLIP.CMD is removing that folder before the INF files are accessed.

When I extracted them (which I didn't need to do) of the two new August hotfixes for MSXML, only one of them didn't install, that was the "msxml.msi" which despite the short name, is the August one. When I left it alone and just put the EXE (white icon) hotfixes in, it worked. So extracting the MSI files out of the two new hotfixes, yes one of them did work but the msxml.msi one didn't. Nevermind, nice to know it doesn't even require any extracting, just dump all August hotfixes in the HF folder and it works! Can't thank you enough for HFSLIP, it makes things so easy. It even puts in all the new DirectX files like d3dx9_35.dll