Tomcat76

Thanks for the reply. I changed the 0 to 128 but I'm still getting the "Installation failed" error messages. Looking at the parameter specifications you provided, I see what's probably causing this: there is no <section> inside any of the nForce4 INFs that's called "DefaultInstall". I changed that to the name of the section that refers to the vendor IDs but that didn't help. I suppose I could try them all, one by one, but who tells me, when I find one which doesn't pop up the error message, that everything that needs to be installed will effectively be installed? Isn't there a way to figure out what Windows is doing when I install the INFs through Device Manager?

I don't know if it's related, but the tutorial reads "filenames here must have 8.3 formatting, and must be without spaces or punctuation" for the HFSVPK_SW and HFSVPK folders. I see you got diskeeper.EXE, reader705.exe, unixutils.EXE and MP10Setup.exe in there. I must say though that I've always renamed files so they match this 8:3 "requirement", so I don't know if it's really a necessity.

Ah, I see. I kept putting the UR1 version (and later the UR1v2 version) in my FIX folder because I wasn't 100% sure. Thanks for the heads up.

I'm not suprised. This thing is the best of its kind. Thanks!

Including scsiport.sys?

@CoRoNe: Well... It looks like ffdshow is creating havoc on my system. Don't know why. Only Haali plays the MP4/M4A files fluently. To continue where I left off... Last time, to get rid of all "skipping problems", I used "Profile 1" as a base and disabled: - ffdshow - AC3Filter - MP3 Fraunhofer - AC3 This time I left AC3 in and everything is still fine. So (aside from ffdshow) it's either the AC3Filter, or Fraunhofer, or both that are contributing to this problem.

You could try this but I have no experience with it. for %%i in (HFDRV\*.inf) do makecab /D CompressionType=LZX /D CompressionMemory=21 %%i copy HFDRV\*.in_ SOURCESS\I386 del /q HFDRV\*.in_ Edit... Ah, I see you want to rename them to hfdrv1, etc. I wouldn't know how to do that.

I voted "other". I got additional fans but they aren't all running at full speed. Fan controller: Zalman ZM-MFC1 CPU fan: Zalman CNPS7000B-Cu Front case fans: 2x SilenX SX-080-14T (8cm) Back case fan: Antec Pro (12cm) MB chipset fan: default on MSI K8N SLI Platinum (DFI quality) GPU fan: Zalman VF700-AlCu on 5V resistor (not controlled) Athlon64 X2 4200+ @2375Mhz (250x9.5); HT 1000Mhz (4x250); MEM FSB 208. The CPU fan is spinning at 1900rpm and the MB fan is tamed down slightly to 4000rpm. The back case fan is controlled as well; it's inaudible when sitting in front of the computer but I don't know the actual speed of it. The two SilenX's (cooling 5 hard drives) are given maximum power (whatever "maximum" means for the Zalman controller). Current CPU temp (normal use): 27°C Current MB temp (normal use): 24°C

Western Digital for me. Seagates are "more reliable", but WDs are much faster, "reliable enough", and the 320GB SE SATA drives are the quietest I've ever owned (idle noise and write noise). It's just a matter of what's most important to you. Maxtors were great when they used Quantum technology (although they were excessively loud) but the drives using their own technology are notoriously unreliable (at least where I live). They also have a bit louder spinning noise, and a MUCH louder write noise; I couldn't stand working with a Maxtor as it would kill the great efforts I've done to not keep my system whisper quiet but completely inaudible.

I've been looking high and low for a solution to install the nForce4 components I need through a batch file. This the the closest I got: %WINDIR%\system32\rundll32.exe setupapi,InstallHinfSection DefaultInstall 0 nvsmbus.inf %WINDIR%\system32\rundll32.exe setupapi,InstallHinfSection DefaultInstall 0 nf4sys.inf %WINDIR%\system32\rundll32.exe setupapi,InstallHinfSection DefaultInstall 0 nvnetbus.inf %WINDIR%\system32\rundll32.exe setupapi,InstallHinfSection DefaultInstall 0 nvenetfd.inf %WINDIR%\system32\rundll32.exe setupapi,InstallHinfSection DefaultInstall 0 nvata.inf For every one of these lines, though, I get an "Installation failed!" dialog box. The final idea is to get this done through SVCPACK.INF. I'd maybe consider DOSNET.INF if required but an unattended install involving WINNT.SIF is out of the question. But first things first: get the batch file going so Windows installs everything automatically instead of popping-up the Found New Hardware dialogs...

Whoops... It looks like I spoke too soon. MP3 files are fine, but M4A files have the "skipping problem". Back to KLite Mega...

That system with 8 SATA drives would consume about 480W at peak usage. I'd recommend the Antec TP2-550EPS12V or the Antec TP-II 550, both 550W.

Me thinks the person at the bottom right is the one telling the truth...

@CoRoNe: I don't seem to have any of the problems I mentioned above with DirectShow FilterPack (except MPC still not being able to play some of the MPEG1 files but I don't care about that). I use DSFP 1.9 + ffdshow 20051221 + QT Alt 1.67 + Real Alt 1.46. It's a bit of a hassle getting everything installed and configured, though; a few clicks here and there is enough for KLite Mega. I'm gonna try and see if I can somehow automate the install of DSFP, QT Alt and Real Alt, but ffdshow is gonna be more difficult: I need to verify if all the customizations I make during install as well as those after install (per the instructions in your readme file) can be done with registry hacks. Also, the M4A format still needs to be configured in Windows.

Good work, the_guy. I couldn't get anything to work but your inf actually added something to the registry. I corrected the problems with it here: [Version] Signature = $Windows NT$ AdvancedINF = 2.0 [DefaultInstall] AddReg = AddReg.Halt [AddReg.Halt] ; 239887 HKLM,"System\CurrentControlSet\Control\HAL","14140000FFFFFFFF",0x00010001,16

0x4, "CurrentControlSet\Control\HAL","14140000FFFFFFFF", 0x00000010 I don't know if that would be correct. I used ConvRegToInf.exe.

I'd think so. For 2K, they are not in the two cabs we are including with HFSLIP, and SP2 for WinXP was released before these updates even existed.

Why both? The reg patch did it for me. Does the boot.ini tweak do more? I'm not sure that would be a good idea.

It seems I cannot quote anyone and make a new post out of it. It's always added into the previous post I posted in the same thread. Am I doing something wrong?

Hell yeah! Athlon64 X2 4200+ @ FSB250 (2375Mhz). The temp was 42°C. I applied the reg patch, rebooted, and was disappointed at first to see it only got to 41°C. But I decided to wait and sure enough the temperature dropped quickly one degree at a time to 31°C in roughly 4 minutes. I wish I had continued to follow that thread...

On my computer: Opera + common sense. I never needed an anti-spyware program. On computers I build for others: MS Anti-Spyware, Spybot S&D and Lavasoft AdAware. The first two could use some improvement in their interface, though. MS Anti-Spyware looks horrible on wide screen systems (I can show you screenshots with incomplete backgrounds and items/text that are out of view and unreachable because of the lack of a scrollbar). Spybot S&D's real-time helpers are of no use for novices because the text on the buttons is obscured in the popup dialogs (since one of the later 1.3 builds).

The old one didn't run on 2K? I could've sworn it did... this is in the december redistributable. Yeah, I know. I wanted to know from "the guys who want the new stuff in" if this file should be included as well.

I really can't understand his way of reasoning. Either he ends up behind Homer Simpson in an IQ test, or he does this on purpose. The fact that he's misinterpreting and misquoting sources and presents them in a way to brain-inject the underlying, hidden message that "IE is better at everything covered" is so sickening obvious that his rebuttals --basically repeating the same thing-- give me a migraine headache...

Something like this, I'd suspect... but I never tried it... md WORK\D3D expand WORK\DX9\Feb2005_d3dx9_24_x86.cab -F:*.dll WORK\D3D expand WORK\DX9\Apr2005_d3dx9_25_x86.cab -F:*.dll WORK\D3D expand WORK\DX9\Jun2005_d3dx9_26_x86.cab -F:*.dll WORK\D3D expand WORK\DX9\Aug2005_d3dx9_27_x86.cab -F:*.dll WORK\D3D expand WORK\DX9\Dec2005_d3dx9_28_x86.cab -F:*.dll WORK\D3D makecab /D CompressionType=LZX /D CompressionMemory=21 WORK\D3D\d3dx9_24.dll makecab /D CompressionType=LZX /D CompressionMemory=21 WORK\D3D\d3dx9_25.dll makecab /D CompressionType=LZX /D CompressionMemory=21 WORK\D3D\d3dx9_26.dll makecab /D CompressionType=LZX /D CompressionMemory=21 WORK\D3D\d3dx9_27.dll makecab /D CompressionType=LZX /D CompressionMemory=21 WORK\D3D\d3dx9_28.dll del /q WORK\D3D\*.dll copy WORK\D3D\* SOURCESS\I386

I stand corrected. I was apparantly looking at the wrong file... the one that's actually referred to as "redistributable" by MS. They really made a mess out of it now; "DirectX End-User Runtimes (December 2005) Full Download" is the current redist... I have a question... You guys are talking about the D3DX9* updates... but what about the October update, xinput9_1_0.dll? @FDV... Apparantly not. Each of the DLLs mentioned earlier reside in a separate CAB file of their own, and then there's an additional distinction being made between x86 and x64. That makes 10 DLLs in 10 CAB files of which five are requested (if the October update can be ignored).