Axed

Good point TC. Maybe im just slow, but for some reason i didnt think of the extra features like adding in codecs automagically, easy appreplacements, etc when it came to XP. I think i've been fiddling with Win2k to much!

KiKi, im sorry if this has been covered before, but why are you using hfslip at all if your going to use the RVM Pack? Most, if not all of the updates covered by hfslip would already be in the RVM pack i would have thought? Dont get me wrong, its great your testing hfslip because they can always use more testers, but i was wondering. Personally, the reason i use hfslip is so i dont have to use the RVM pack.

Im not a devel, just a user but i can give you a quick answer bashrat. HFSlip always leaves a HFSLIPWU.INF file in the i386 directory.

midiboy, since the driverpacks have the backups of your old files why dont you just restore them, run HFSlip then do the driver packs again? And on your second post, i believe you'll find you need a virgin source for every slipstreaming method (hfslip, ryanvm, etc) other then microsofts "slipstream" which just uses svcpack. I think the basic idea to creating a cd/dvd like this is you have a fairly secure disc to begin with, so you can easily jump on microsoft update without to many worries and download any extra updates with just the microsoft firewall enabled.

Have you considered it may just be dirty? Just clean out the ram slot CAREFULLY with a cotton bud that has been dipped in methylated spirits. The cotton bud shouldnt be dripping, just have a little on it. Do the same with the ram stick connectors. Make sure its completely dry before putting the ram back in. If you feel uncomfortable with any of this, dont do it. Get someone who is techinically minded to do it for you.

Yes, lfn is completely supported in .inf installers.

dziubek - Have you tried running these addon packs thru a different program such as nLite or the RyanVM slipstreamer to see if its the update packs? A way you could test them is to extract all the cabs into a single directory, remove the .ini files, then extract all the .in_ files. You will then have *namehere*.inf files. To test the addons, right click each addon .inf and select Install. If it does not work (doesnt do anything) just delete the pack because it wasnt tested, or the creater is lazy which means its liable to have errors. This isnt for system update packs like WMP10 or RyanVM Update Pack only application addon packs. Otherwise, they should all install properly and you'll know pretty fast which ones are worth keeping because they work and which ones arent. Do this on a virtual machine. These addonpacks can cause havoc on your computer. And ill say it again, these addonpacks can cause problems when installing XP unless they are perfectly working. Mind you, im not against all application addon packs. The "nLite Application Add-Ons" tend to be quite good because they dont modify the sysoc which is what causes incomplete system installs when the sysoc errors from a bad inf. At least if theres an error in the "nLite Application Add-Ons" packs, the system install keeps going properly...

edit: removed post because i didnt read all the threads properly. I originally suggested a possible way of adding driverpack support but hadnt read all the info fully. From what people say, the big problems are all the .inf files point to special driver directories under weird names. Looks extremely difficult to do and time consuming to do.

By the look of it, the problem is with one of your addons. Find your Sysoc.inf file (sysoc.in_ compressed in your i386 dir) and check that, see if there are any weird errors in it also. "Slipstreams" such as these you have used arent a very good way to install a program because unless they are written perfectly, one single broken one will stop every single one of them from installing. Have you tried all these updates in another program such as nLite to make sure its not just a HFSlip problem? What it looks like to me is one of those addon makers didnt specify the %maininf% properly in his entries_whatever.ini. I suppose you could extract all the cab files and search for %maininf% in them to see which ones use it, then check them for errors by hand. Even then, there are obviously more errors in the secondary inf files that are called in your sysoc file since its not installing any of them.

I've added myself. I havent been around HFSlip for long but its definately my favourite way to slipstream updates since i can choose exactly what i need and i dont get a bunch of other random stuff i most likely will never need!

Hi, My Via Rhine 2 network card doesnt work with the current most upto date Network Drivepack. I created the CD by NLiting it (without removing original windows XP network drivers) and then adding the driverpacks before compiling the ISO. This Network card gets picked up as an AMD PCINET Family PCI Ethernet Device (or something like that, it scrolls to fast) but i know for a fact it is a Via Rhine 2 Chipset from when i had Linux installed with my own kernel compiled with only that network support. It worked under these conditions perfectly. The error it says while attempting to install the driver is "Service installation section of this INF is invalid". All i am allowed to select then is the Finish button. My other version of Windows XP without the driverpack picks up this Network card as : PCI\VEN_1106&DEV_3043&SUBSYS_14201186&REV_06\2&EBB567F&0&68 : Amertek C110TX PCI Fast Ethernet Adapter #2 This is the only network card i have installed in both this system, and my other computer i attempted to reinstall Windows XP on (2 of exactly the same card, came in a doublepack years ago..). I tried the same network card in my other computer to get that HwId.

Celtic druids builds are older, and not as fast as Milans builds on AMD systems i believe. Celtics also dont work on as many computers because of the optimisations he uses. Use Milans builds. I've been using his most recent for awhile now and it works perfectly. Celtic stopped making new builds because milan started making them again.

I only just discovered HFSlip and i love it! Thanks guys!! I had weird errors with RyanVM packs and i didnt like how i couldnt pick what i wanted to install.. I love the flexibility! And, it just works.. What better way to compliment software then it just working? Thanks! With regards to The Core Pocket Media Player (TCPMP for short) heres the page with beta versions. If your interested, i can also send you the AVC decoder they released at one stage which uses about half the resources as directshow. I can play AVC files on my pc with almost no cpu useage! When even a junker like this old AMD system (athlon 1000 no sse) can play files using this program, you know its good! Mind you, it will become a payware program when it becomes a final, but if its not to expensive it'll definately be worth it for those of us who dont really have a need for extremely fast computers. Im waiting eagerly for a linux version that works in MythTV and an xbox version so that we can use even more low spec systems for playing movies.

The quality and resources used in ffdshow depends entirely on who did the builds. You have to download a good build such as these builds by the creater milan. Try to avoid the others, many of the gcc builds have annoying bugs such as not working on non-sse computers and the ic9 builds are slower on AMD machines. Milan's builds might have a couple of bugs still, such as vorbis audio stutters occasionally and dvd decoding not working, but other then that it works extremely well. If your after a completely independant non-directshow you should also look at The Core Pocket Media Player which uses almost no resources and can be used on almost any pc that will install xp to run most videos.

I also love this program! My biggest problem with it tho is that you cant save hashes easily, or i just havent worked out how to do it yet.

Cinema Craft Encoder basic. $56, but the fastest encoder on the market with extremely good quality, as long as you keep the bitrate above 3000. For your processor, make sure you get the most recent version, others will crash because of you not having SSE instructions.