DeTard

Unfortunately the trial version can't be activated if I remember correctly.... what were the steps you went through to make this a silent install? I own a license to Alcohol 120% and I'd love to make that install silently but I've always had problems in trying to get that done.

You can set it from the command prompt, yes, but it won't save it beyond that one instance of CMD.exe. If you try running HFSlip again, you'll end up with the same errors once more. Do it as Tomcat76 mentions to not have the problems any longer.

Strange... honestly, mine and John's are almost identical right now so not sure if his will work any different for you. I can get into Windows and start it up and it runs just fine for me. If you ever get a chance, let me know what the error is please.

Updated to include up to 12/3/2007 definitions as well. Removed the TinyLoad download link until I can get it to upload (doesn't work from my workplace).

Umm... Could you give me some information like what the error was and when you get it? I haven't received any errors whatsoever on a fresh install of XP SP2, so I need a little more to work with. Edit: Just verified it again, and it seems to be working exactly as I had intended, and totally silently. Please give me some more info so I can look into why it didn't work for you.

Not sure about the AutoIt of this, but if you need a fix until ddSHADOW has time to work on the script, I have an nLite addon pack that includes a silent and switchless installer for 7.0.2.5. I made sure to remove from the installation the starting up of the Licensing program (though I left the file itself included and intact so the updater doesn't try to download it for you after install) by editing the MSI installer of it. http://www.msfn.org/board/Release-Ad-Aware...25-t108626.html If you want to give that a try...

@heffalump You could just use HFSlip and integrate DX9 right into your windows install. Just get your DX9 Redist file (even if you get the latest one from Nov 2007) and drop it into the HF folder and put your source files into the Source folder. Run HFSlip and voila! You of course can do more than just DX9 with HFSlip, but if this is the only thing you are worried about, it will certainly do the job nearly effortlessly. Will even save you some space maybe from not having to put an silent installer into your install source.

Ad-Aware 2007 Free 7.0.2.5 updated to 12/3/2007 definitions Ad-Aware is no ordinary anti-spyware, it is the original anti-spyware product, offered to consumers worldwide to protect their personal and home computers from malware attacks. And today, with over a quarter of a billion downloads, computer users put their trust in Ad-Aware more than any other anti-spyware software program. Globally trusted on-demand scans and malware removal! Detects and removes Trojans, worms, spyware, and other malicious programs Repairs damage left by malware Internet surfing tracks erased with TrackSweep Incremental updates for faster downloads Efficient computer resource footprint Free software updates throughout license duration Free support from worldwide security volunteer network Website - Ad-Aware 2007 Free File Size - 14.6 MB (15,408,831 bytes) MD5 - 031E72B2FAD1F77C4D14A84AB1B47CC7 Main - Esnips

AIM 6.5 AOL Instant Messenger (AIM) is a free, advertisement-supported proprietary instant messaging and presence computer program which uses the OSCAR instant messaging protocol and the TOC protocol. It was released by AOL in May of 1997. It is the most popular instant message program in the United States. Website - AIM File Size - 11.3 MB (11,851,985 bytes) MD5 - 06CC4FCD6102C945F137A6EADC710C09 Main - TinyLoad Mirror - Esnips

Open With Arguments 1.2 Open With Arguments is an extension for Windows that allows users to directly pass arguments to executable files. Instead of opening a Command Prompt, changing to the appropriate directory, and typing in the filename and parameters, users can right-click on any executable file directly in Windows Explorer, select Open With Arguments, and then enter the parameters. Open With Arguments can be used with both GUI and CLI applications. When launching a CLI application (such as a batch file), the Command Prompt will remain open after execution to allow the user to view any output. Open With Arguments can be configured to work with any executable file format recognized by the Windows shell; by default, it works with .exe, .bat, and .cmd files. Website - Open With Arguments What's new - Changelog File Size - 462 KB (473,252 bytes) MD5 - E4615D44CC25205CAAAB5C627DA82B8A Main - Esnips

3.0.4 Beta is now available.

Ventrilo 3.0.1 Ventrilo can be used for home / personal applications like talking to friends and family, or playing organized online games where Voice Comm can make them more exciting and productive. It can also be used in an enterprise environment as a productivity tool for conducting long distance group discussions. This would also help when using group collaboration programs that don't provide any kind of voice communication support. Website - Ventrilo What's new - Changelog File Size - 2.30 MB (2,422,326 bytes) MD5 - 85864091E2859ABA707D595442D959AB Main - TinyLoad Mirror - Esnips

Honestly, I don't really need any of the files - I pulled them from the June 07 redist and added in the August 07 specific files from that redist, so all should be up to date now. Thanks for the offer though. It was more of a surprise for me to run into finding a corrupt file on Microsoft (I, admittedly wrongly, assume that their files all are without CRC errors internally) and assumed that HFSlip was the problem.

Well, with hashes confirmed, you can safely rule out corrupted files during downloading. It's the actual file on their server that is an issue apparently. I can't give any explanation for those that it is working for other than cached copies of the file back when it did work ... since I guess they released it a second time? For those that it does work for, how many August 2007 files are there in your copy? I have 6 in mine; I'm wondering if they "forgot" to include some August 2007 files and re-released it to include those, but managed to corrupt the contained CABs in the process.

Ok, this is just wierd... I just downloaded from johndoe's direct link and got the same MD5 hashes as I've always gotten. I really believe they updated the file for some reason, and the second release of it was bad. What I think I'm going to do now is get the June 2007 redist, use that, and then include the August 2007 files. My file hashes I'm getting are: DD9488CF38A8028EEF02B47D831A6353 Tomcat or RJARRRPCGP, can you confirm that hash?

Geez... I'm glad at least SOMEONE else has seen the problem that I have with this. For those of you that say to check my hard drive, maybe you didn't read that I saw the exact same problem on two separate computers, on two separate networks (home vs work). If it weren't for that, I would have agreed that it may have been a corrupt file. As for the EXE, yes you can extract from that no problem. I know that DXNT.CAB is not changed from bi-monthly redist to bi-monthly redist, but I actually believe it was corrupted on Microsoft's hard drive somewhere along the repackaging of the CABs. But it's DXNT.CAB itself that I cannot extract from (try extracting KS.SYS from this file and see if it's ok). Thanks for everyone's checking on the file though; it's a fairly big download so thanks for the time you all took to try to confirm the problem. I'm not sure, but for those that have no problem with it, possibly try to clear your browser cache prior to downloading again to make sure when you download, it's not just pulling from cache. It's very possible that Microsoft had a good and a bad release as well, but why they would re-release I don't know.

Did you download from here? http://www.microsoft.com/downloads/details...;displaylang=en I just found that downloading from 2 separate networks (home and work) and extracting it on 2 different computers resulted in the exact same thing - the new redist being corrupt.

Just confirmed it for myself by connecting to my home computer, downloading the Aug 07 redist, extracting it, and then extracting from DXNT.CAB. Again, I have the CRC errors in it. Still using the Aug 07 sources for my new install, but using DXNT.CAB from the original redist of DX9C.

Wow.... I just found the culprit and I'm amazed at what it was honestly. It has nothing to do with HFSlip or even my setup or anything at all - the August 2007 DX9 distro is broken. DXNT.CAB is corrupted and cannot be used. I'm not sure how they even released it with this problem, but it is there. I watched HFSlip much more closely this time around and I saw this lil snippet: Expanding hfcabs\dxnt.cab to work\dx9\d3dim700.dll. Expanding hfcabs\dxnt.cab to work\dx9\ddraw.dll. Expanding hfcabs\dxnt.cab to work\dx9\ddrawex.dll. Expanding hfcabs\dxnt.cab to work\dx9\dinput.dll. Expanding hfcabs\dxnt.cab to work\dx9\dinput.xpg. Expanding hfcabs\dxnt.cab to work\dx9\dplaysvr.exe. Expanding hfcabs\dxnt.cab to work\dx9\dplayx.dll. Expanding hfcabs\dxnt.cab to work\dx9\dpmodemx.dll. Expanding hfcabs\dxnt.cab to work\dx9\dpwsockx.dll. Expanding hfcabs\dxnt.cab to work\dx9\dsound.dll. Expanding hfcabs\dxnt.cab to work\dx9\dsound3d.dll. Expanding hfcabs\dxnt.cab to work\dx9\dx7vb.dll. Expanding hfcabs\dxnt.cab to work\dx9\gcdef.dll. Expanding hfcabs\dxnt.cab to work\dx9\gcdef.xpg. Expanding hfcabs\dxnt.cab to work\dx9\joy.xpg. Expanding hfcabs\dxnt.cab to work\dx9\joy.w2k. Expanding hfcabs\dxnt.cab to work\dx9\pid.dll. Expanding hfcabs\dxnt.cab to work\dx9\pid.xpg. Expanding hfcabs\dxnt.cab to work\dx9\d3d8thk.w2k. Expanding hfcabs\dxnt.cab to work\dx9\d3d8thk.dll. Expanding hfcabs\dxnt.cab to work\dx9\dx8vb.dll. Error in compressed input file format: hfcabs\dxnt.cab. 21 files total. The system cannot find the file specified. FINDSTR: Cannot open WORK\DX9\dxntunp.inf I then went ahead and checked it with 7-Zip and Expand manually and both utilities found problems in the files. I have already downloaded the files multiple times now, and it continues to have the same issues. Can anyone else verify this for me? Again, this is the August 2007 distro only.

I've been using HFSlip for a long time now (pre-version numbers anyhow) and this is the first I've ran into this issue, which I cannot seem to fix, despite it looking like all is well for the duration of running HFSlip. What is happening is that when I include the DX9 CAB files, it is properly detected but the KS.SYS file is deleted at some point during the process and not replaced by the DX9 version. I know that KS.SYS is part of DRIVER.CAB, and that a newer version comes with DX9 (using the Aug'07 distro) in the DXNT.CAB file, but for whatever reason I no longer have a KS.SYS after all is done. It's not in DRIVER.CAB and it's not in i386, and I receive an error during setup. I even see it being copied when it is extracted from DRIVER.CAB. I have a feeling that, unintentionally, the order of things got mixed up at some point. I believe it might be deleting KS.SYS after DX9 integration. Unfortunately I'm home right now (I'm doing this on my laptop at work) so I cannot give the log file or any of the setup files. As soon as I get into my office tomorrow I'll try to get those up here (possibly after copying from a clean Win2K SP4 source again and running HFSlip once more). I may also comment out that line that deletes KS.SYS and see what version of the file I end up with. EDIT: Just wanted to update this to say it isn't HFSlip's fault that KS.SYS was removed, it was due to a corrupt DirectX9 Redist on Microsoft's site. Unless they have fixed it, the August 2007 Redist has several corrupt files, including the June 2007 cab files as well as DXNT.CAB (which is required to slipstream DX9 onto Windows 2000). The solution is to get both June 2007 Redist and August 2007 Redist and use all the files from June and then add in the three new August 2007 files.

Hello, I made a Windows 2000 unattended CD this morning and found, to my surprise, that it wasn't booting as it should. My computer is not seeing this CD as being a bootable and then continues to boot Windows XP that is installed already. When I open up Nero and check the disc info it says it is a bootable CD. Even MagicISO is seeing the ISO I made as being bootable. My Windows XP CDs using nLite 1.2.1 are booting fine it seems, but I'm unsure as to why 2000 it isn't. I usually use direct burn, but when I started having the problems I started using making ISOs to inspect them a little more in depth. Has anyone had similar problems? This is the first time I've ever had a problem with the boot image not properly booting Windows 2000. One more thing to note, I'm preparing my source with HFSlip as I always do, but do not believe that in any way HFSlip can make this unbootable since this is something nLite does at the very end.

LOL, thought you'd also enjoy this..... Before I realized I was reinventing the wheel and used your methods for detecting devices and installing the drivers, I had written a WSH script that checked WMI to detect whether a device I specified existed. If so, it checked to see if the CD I installed from was inserted via CD-ROMS with the VolumeName that was used on my CD. This was called from RunOnceEx, which would then run a SFX 7zip file (waiting for it's completion, the WSH way), which would then run the installer for the drivers after extraction...... I write WSH scripts for logon scripts to an Active Directory domain, and it seems to be the best method for doing so, using internal Windows API calls for things like mapping drives. It also seems to be more elequent that batch files that run external applications. Unfortunately, doing this so often makes me forget that the easy way is also sometimes the best way. Anyhow, I resorted to your method so that I wouldn't have to remember my way and yours, and that it could also help others in case you decide to just add my lines of code to your DriverPacks..... .....oh God, why do I over-complicate things sometimes???

BTW, I forgot to mention that in the .CMD file I attached there are checks for files installed for the Intel chips via the INF method. One thing to note is that igldev32.dll is ONLY in the 852+ drivers, while igfxcfg.exe is in BOTH driver sets. When I looked for a key file that would identify one over the other, I couldn't find anything that was just in the 845 set. So basically, it checks for the 852+, installs, then SKIPS the 845 so as to not install both of them (see the "GOTO DPGC3" line).

Hello, Recently I created several install images using BTS's driver packs to help me with hardware compatibility (using all driver packs and method 2). After using this on some laptops that we have, I found that when the laptops would return from S1 suspend mode, the LCD would power on, but was blank. The computer hadn't locked up, as I found out by typing my password in for the user that was logged in, and hitting Windows key, U, R, then Enter would reboot the computer. The LCD simply was blank and everything else appeared to be working. I went ahead and downloaded the driver installs straight from Intel and found out that in both the 845 and the 852+ installers there were vbiosxxxg.zip files, where "xxx" was the chipset model number for supported chips. So in following BTS's methods, I repackaged the drivers with 852+ having the tree "D\G\I\10" and 845 "D\G\I\11" in a file named "DriverPack_Graphics_Custom.7z" to future proof what I've done in case this isn't incorporated. I also created a copy of the "finish" batch file, renamed it to "BTS_DPs_finish_custom.cmd", and made it run directly before BTS's original file (using RunOnceEx for my installs). Doing it this way fixed the suspend problem. Also note that I have install methods for Synaptics touchpad drivers (so that I can disable Tap to Click since some of our touchpads are overly sensitive), and they are packaged in "D\P\S" (P for PointDevices used in WMI) in a file named "DriverPack_Mice_Custom.7z". Let me know what you think...... EDIT: I had to make a fix to the CMD file that was attached. I found that there is a file named igfxeud.dll to use to key my install off of for the 845, as well as some errors in logic (such as a potential loop from a typo). If you had downloaded it before, please get it again. BTS_DPs_finish_custom.cmd

Sorry, no I THOUGHT it was complaining about filesize, and that was the only thing I could find wrong. I checked for files containing the text ALIIDE.SYS and only a few things seemed to apply. I checked the [FloppyFiles.2] section in there on accident, instead of DOSNET.INF (DUH!) and thought I was all good and the fix wasn't working for me. I haven't had a chance to check things yet, but I will later on today. I'll now return to my little noob hole....