RyanVM

The TV Wonder uses the same chip as the one I linked you to FWIW

The first thought that comes to mind is "Eww, Tiger Direct." The second thought is, you get what you pay for. But I suppose you don't really lose a whole lot if you go with either of those, so you could always give it a try. But if it were my money, I'd probably get something which is known to be of higher quality (ATI Theater 550 = yummy)

errr...click OK?

I've got a Leadtek WinFast TV2000 Deluxe personally. Works fine. However, if you're willing to expand your price range just a little bit, this is one of the best analog tuner cards you can get (IMO): http://www.newegg.com/Product/Product.asp?...N82E16815117802 $65 after MIR (There's also a regular PCI version if you don't have any PCIe x1 slots on your motherboard)

Happens to the best of us

There's a reason I call the donations on my site a Tip Jar. If you're donating as a form of payment, I think your intentions while noble are misguided. The reason I make them available to people is because some people are grateful for the time and effort I put into my work and want to in essence buy me a beer for my work I can tell you that I in no way ever intended the donations on my site to be some form of payment with strings attached. I highly doubt Bashrat did either.

Well, I dunno then

The error isn't nLite.inf's fault (as I was trying to tell you by linking to ViVa's post and subsequent discussion). Like that thread says, the problem is that nLite.inf isn't in txtsetup.sif, so sysoc.inf can't find it. While it's admirable that you've spent all that time trying to hunt down the problem, the answer's been right in front of you the whole time

It's the same exact process, the SiI drivers were just an example. Why don't you open the files it tells you to open and see if you can find the relevant sections. Come on, it won't bite BTW, there's an entire forum dedicated to questions like these...

It's only running in the background if you've got a non-legit copy. At which point, I don't feel any obligation to help. Sorry.

I don't know of a specific distribution, but you could always use Hulk's thread as a guide for what fixes you need and create such a CD yourself with a simple batch file.

My guess is socket AM2 CPU support

I took the liberty of extracting just the driver files. They're attached in the RAR file below. AMD.rar

Probably the same bug as ViVa's. http://www.msfn.org/board/index.php?s=&sho...ndpost&p=507690

I think you need to read my site a bit more carefully. It says not to integrate the update pack onto an already-nLited CD. It says nothing about nLiting a CD with the Update Pack integrated into it...

Regarding drivers, it sounds like you're either trying to install 32bit drivers on a 64bit OS or 64bit drivers on a 32bit OS. Make sure you get the right drivers to match the version of Windows you're installing. Both sets are available from nvidia.com

Of course, to see what (if any) problems there are with using my pack, it would only take one VM install to find out Seriously, there's zero risk whatsoever. I can understand being cautious, but do so within reason .

Muaaahhhh I beat you finally Hmm, that sounds like a challenge to me

VMs are the best way to test software changes.

What I find funny is that they keep doing this tit for tat, and yet neither seems to have said a word to the other person about doing it. What is this, first grade? Act like a grownup and confront him about it if you don't like it. Otherwise, it's his system and I don't see what right you have to go against his intentions on his system.

So, should I put a new MMC in my pack just to break you again? Of course, I kid. I know you fixed that once and for all.

If you're using an English XP, my Update Pack is the easiest way to integrate the hotfixes with a negligible performance penalty.

If you're using RIS, there are some very gifted RIS people on my boards that can probably help you.

You know, the directions on my site specifically say that you can NOT integrate the pack over a previously-nLited install. I strongly suggest you read the directions more carefully before continuing any further.