RogueSpear

It depends on the complexity of the install and also if I've ever done the application before. Something like QuickTime Alternative that I've done a hundred times and has nothing particularly special about it, probably takes me like 15 to 20 minutes. The Micosoft AntiSpyware took a long time because there was all kinds of problems that had to be solved, but further versions will hopefully not take so long. But as a rule, with a new app I've never repacked before, if I don't run into anything unsuall, I figure about a half hour to repack and then a half hour to test it out. Sometimes it takes quite a bit longer, but rarely does it ever take less time than that. It's a process that involves a lot of steps and a lot of things to do. None of it is overly complex, but it also took me a few years of experience doing it to find all of the little things to watch out for. There's a lot of "gotchas" and a lot of little tricks to repack something.

The problem with PowerDVD is that it's not freeware. I've decided against posting commercial application repacks with the reg info or serial missing. Just don't need the potential hassle.

You can do an awful lot with VBscript for sure. More than just calling executables to run. If you want to see various examples of VBscript, click on the link in my signature for the RIS guide. Starting with the third post in that thread are some scripts. If you are the type who picks stuff up easy, you'll probably learn from the examples. But you'll really need to find some scripting web sites or books to be able to get the most out of it and it will take some time to pick up too.

Not posting a problem, just wanted to say sweet work on this solution. I've learned more about AutoIt from you and your examples than I can really explain. Thanks again!

You may want to try integrating the latest RealTek driver for RIS only. In other words, just the .inf and .sys files in the i386 directory and restart the BINL service. My advice would be to NOT use the latest drivers for the PnP enumeration part of setup. Let it grab the default drivers that Microsoft supplies with XP. They seem to be the only drivers where the RealTek NIC will initialize and become active in time for the Machine half of Group Policy to apply. It took me months to figure this one out. And like a numbskull, I always try the new drivers from RealTek whenever they update them just to see if they've fixed the problem. But sadly and predictably, they never work right. Even sadder still is that RealTek seems to have infected the laptops and motherboards of nearly every vendor out there. Must be that nobody can resist saving a nickle when they design their products.

I'm about to go bed. It's probably the last time I will go to bed and still have my best friend with me. I got JP almost 18 years ago from a friend of mine who could no longer own a cat. An orange and white tabby with a little bit of attitude but a large warm heart, he could often be mistaken for a dog the way he always wanted to be by my side. He saw me grow up. He was always there to make me feel better during times heartbreak and sadness. He's without question the best friend I've ever had. Kidney disease and an over active thyroid have taken their toll and he just doesn't have the fight left in him to win that battle anymore. I'd give him one of my own kidneys if I could. Wouldn't even have to think about it. I love you buddy, and I'm going to miss you.

As an experiment, perhaps remove the XP default sound drivers with nLite and see if the new one get picked up then.

This is a 919GAG so prolly not much different. I'm using an nVidia 6600. Perhaps that's the culprit.

@Fencer128, do you ever get any BSODs on computers with a RealTek HDA? Says something to the effect of "IRQ not less or equal than". I'm getting these blue screens for seemingly no reason at all (doesn't matter what I'm doing). I have one free PCI slot left which I had planned on filling with an additional NIC card but I also have a SoundBlaster Live! that's starting to look as though it may need a home.

It works. One of my clients seems to like the more questionable web sites (he owns the business so I guess he can surf wherever he wants). Anyway, he was browsing to some sights that even made me blush and all the while those little boxes that slide up from the corner to warn you of stuff being block kept on appearing. So it did seem to be working. Also when I first installed MS AntiSpyware on his computer it eliminated a few dozen infections. It was actually kind of cool. It was like watching two militaries duking it out. Luckily MS AntiSpyware won the battle.

@Fencer128, in case you're interested in a real easy one, ViewSonic offers all of their monitor drivers in a single download (HELLO OTHER MONITOR MAKERS!). Ahem.. anyway, it's a small d/l that has seemingly hundreds of monitor drivers all in one. As if that wasn't enough they also have downloads for Nokia and OptiQuest monitors in one handy file.

Yea, I'll take a peek at that. I can't ever recall seeing a manufacturer actually update the driver a monitor so with these it may be just as well to dump them all into directories by manufacturer.

Well like I said.. I could be wrong but I hope you understand how hesitant people are these days to not only give out information, but to run a utility and sign up for some kind of online updating service that the utility uses, when there isn't much info to go on.

If you are in fact serious about this project, then I would suggest you have it looked over and possibly carried on BetaNews.com, Softpedia.com, MajorGeeks.com, etc.. something. I don't want you to take this personally, but you're asking for people's First and Last names in order to get an ID. Maybe I'm wrong, but I smell a rat. Your web site is pretty bare of any real information and your WhoIs record is practically empty.

You really do need a "belt & suspenders" approach to spyware. No single product is even close to being sufficient on it's own. Most installations that I support use Symantec AntiVirus throughout. Starting with version 10, they've included some rudimentary spyware protection. Actually the protection really isn't all that bad, the management of it is. To supplement this I have repacked Spybot S&D and that gets installed on everything as well. Just for good measure I pump out all of the registry entries generated by SpywareBlaster as they are updated. For those machines that are dedicated to a single user, usually a single user who "needs" administrative privledges (think bosses), I also install Microsoft AntiSpyware. I don't buy the whole Opera / Firefox argument either. For starters, only a masochist would try to deploy and manage that in the enterprise, not to mention the cascade of help desk calls from deer in the headlights users who would be scared to death of something they've never seen before. Second, a good admin would use WUS, SMS, or some other solution to keep every workstation up on security patches. Third, IE is manageable through AD. The last point is the one that matters most to me. I've gotten to be downright draconian in my management of IE, yet everyone is still able to get their work done, everyone can still run their little eBay business from their cubicle, and in the last 8 years I've had ONE problem with spyware. And that was.... c'mon guess.... on the bosses computer. The guy who had to have admin priveledges. The guy that gets paid six figures to surf TwistedHumor.com and some other unmentionables all day long. Sorry for all the sarcasm. I had to suffer fools all day this happy Monday.

I didn't even know to ask.. I mean could you imagine Honda using a Chevy engine in their automobiles?

@cluberti, I can't even believe you mentioned that I just got a new work desktop and I specifically told the guy that the mobo had to be an Intel. I've always had the smoothest experiences with Intel's motherboards. Well don't you know it, it's an Intel mobo alright, but this thing has a friggin Marvell Yukon on it! I guess there's nothing that you can count on anymore. Next thing you know the sun will rise in the west. My problems with the Yukon were even more insidious as the standard fare drivers were not working at all. Only the Intel supplied Yukon drivers worked. That is until Marvell released new drivers, which I luckily grabbed before they took them down again. And yes, I had to fiddle with the .inf even then. Talk about a fun day last week.

I can't say for certain, but I don't think you'll need the bus driver to perform a RIS boot. You use the same NIC driver for a RIS boot as you do for the actual PnP enumeration. BUT there are some slight differences here. For instance, often times the inf file needs to be modified in order for the RIS boot to see the driver and utilize it. Also, you don't need the .CAT file or any of the accompanying .dll files, etc if there happen to be any. Just the .INF and the .SYS files. I don't have any personal experience with performing a RIS install of an nforce system, but I have heard in several threads here that it can be problematic at best. From what I can tell looking at one of the nforce NIC driver sets from DP LAN, there are two .inf files, nvenetfd.inf and nvnetbus.inf. I'm going to go out on a limb and say that you need the first one for performing a RIS boot because it has all sorts of registry entries in it for the NIC settings. Looking inside this .inf file I can see an immediate problem. Here is the begining of the .inf file: [version] Class = Net ClassGUID = {4D36E972-E325-11CE-BFC1-08002BE10318} Signature = "$Chicago$" Compatible = 1 CatalogFile = NVENETFD.CAT Provider = %Nvidia% DriverVer = 04/06/2005, 4.8.2 [Manufacturer] %Nvidia% = Nvidia,NTx86.5.1 [ControlFlags] ExcludeFromSelect = {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV008C,\ {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV00DF,\ {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV0038,\ {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV0057 [Nvidia] %NVENET.DeviceDesc% = NVENET_2k.NDI, {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV008C %NVENET.DeviceDesc% = NVENET_2k.NDI, {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV00DF %NVENET.DeviceDesc% = NVENET_2k.NDI, {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV0038 %NVENET.DeviceDesc% = NVENET_2k.NDI, {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV0057 [Nvidia.NTx86.5.1] %NVENET.DeviceDesc% = NVENET_XP.NDI, {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV008C %NVENET.DeviceDesc% = NVENET_XP.NDI, {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV00DF %NVENET.DeviceDesc% = NVENET_XP.NDI, {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV0038 %NVENET.DeviceDesc% = NVENET_XP.NDI, {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV0057 There are two problems with it as far as RIS is concerned. First, we need to truncate the lone entry under [Manufacturer] and second we need to eliminate the section titled [Nvidia] and then rename the second section to [Nvidia]. So the above section of the .inf file will now look like this: [version] Class = Net ClassGUID = {4D36E972-E325-11CE-BFC1-08002BE10318} Signature = "$Chicago$" Compatible = 1 CatalogFile = NVENETFD.CAT Provider = %Nvidia% DriverVer = 04/06/2005, 4.8.2 [Manufacturer] %Nvidia% = Nvidia [ControlFlags] ExcludeFromSelect = {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV008C,\ {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV00DF,\ {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV0038,\ {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV0057 [Nvidia] %NVENET.DeviceDesc% = NVENET_XP.NDI, {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV008C %NVENET.DeviceDesc% = NVENET_XP.NDI, {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV00DF %NVENET.DeviceDesc% = NVENET_XP.NDI, {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV0038 %NVENET.DeviceDesc% = NVENET_XP.NDI, {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV0057 This procedure seems to be SOP for most vendor's default .inf files. Backing up just a little bit.. I think that all you need to perform a RIS boot will be your modified nvenetfd.inf and nvefdxp.sys. It's possible that you will have to rename nvefdxp.sys to nvenetfd.sys. I ran into a problem like that with RealTek. Give it a shot and let us know how you make out. Oh yea don't forget to restart that BINL service either.

Do the first half of a Method 1 slipstream. then look in the directory UACD_ROOT\DPFiles... they're all there compressed and everything. Even using custom DPs in addition to BTS' they all fit on a CD.

When I first run the application it tells me that the definitions are from today. So I don't know exactly when it's grabbing them (on app start, on app install, etc). It really seems good enough for my purposes. If you want to see for sure, just run SysInternals TCPView during the install or for that matter enable a firewall that makes you permit applications on a per app basis. One thing I thought I had set properly was to hide the tray icon, but it seems to eventually pop up in the tray. Oh well this seems like as good as its going to get from me until the beta cycle ends. I'll spend more time, which I don't have much of, once the final is out.

Actually any movie coming out of Sony these days requires DVDFab Decryptor. I hate to say it, but even though DVD Decrypter is IMHO a far superior product, it's becoming less and less relevant by the day.

It seems to be doing it all on it's own from what I'm observing..

Ok, I think I finally got it. Hoping some of you might be willing to test this out. This is a switchless silent installer of V1.0.701. There is no need to execute any command line options after the installer either. The configuration differs from the default as follows: novice user, script blocking agent is disabled, and there is no connectivity to SpyNet. Microsoft AntiSpyware - 4.56MB MD5: E7426C174DA63260B1337035A4C786D6

I am quite the NOOB when it comes to multiboot CD\DVDs and also with PE environments. Well not using them so much as making my own, but as far as Windows x64 goes, the BTS DPs are not meant to work under that environment. Sure, some of the drivers may have built in compatibility with x64 and other may work even if that wasn't explicitly put in the driver, but there are plenty of drivers in the DPs that simply are not compatible with x64.

The inf file may need to be modified as well. If you attach the inf file here I'll take a peek at it.