Speeddymon

This ended up working for me, full code, use and modify as needed @ECHO off ECHO Starting Batch Extract ECHO Adding RAR and ECM to PATH SETLOCAL PATH=%PATH%;C:\Program Files (x86)\WinRAR;C:\Program Files (x86)\ECM ECHO Parsing .part01.rar style files FOR /f "usebackq tokens=*" %%a IN (`dir /a:-d /b /o:gne /s *.part01.rar`) DO (ECHO Changing to %%~dpa & cd %%~dpa & rar e %%~nxa Extracted\) ENDLOCAL The purpose of this program is to take a bunch of ISO images I made a long time ago, extract them one at a time, then run a program called ECM on them to remove the error code stuff from each image file, then recompress it with 7zip, and delete the original rars and the extracted iso and ecm file. It saves me about 50mb per image after compression. That may not seem like a lot, until you consider that I make a backup of everything I ever buy bc I am bad with scratching cd's. I have a 1tb terastation nearly full of images like that (around 700GB of actual usable drive space with raid 5). I've removed the part of the for loop that runs ECM, recompresses the data with 7zip and removes the originals plus extracted stuff. I had to use the usebackq option to the for loop to get it to process the dir command, and set tokens=* to get it to output the full file name including spaces into %%a Hope this helps someone else in the future. Credit for some of the code goes to computerhope.com.

Firstly, is it possible to put the output of a program I am running into an environment variable, or multiple, and if so, how do I do it? What I'm trying to do is take a directory listing and put each line of output into an environment variable which I can then run through a for loop. I'd use shift to shift each new directory I want to go to into %1. The goal is to extract a bunch of rar files in different directories without knowing the full path to each .rar file. Basically a mass extract. Something like the following pseudo code: @echo off for %%dirname in (dir /a:d /o:gne /b /s) do cd %%dirname rar x *.rar It gets all of the directories below the current, traverses them, extracts whatever rar file is in that directory (they are all old style rars with the .rar -> .r00 -> .r01 etc extensions), and then moves on to the next directory.

Microsoft Update Catalog Web Control x64 Addon Microsoft Update Catalog is a site that allows you to manually download any update by searching for it by it's knowledgebase id. It will allow you to search for for updates with the same knowledgebase id on different versions of windows. The Microsoft Update Catalog is located at http://update.catalog.microsoft.com This addon slipstreams the Microsoft Update Catalog Web Control into Windows XP x64 SP2. Note that upon visiting the Microsoft Update Catalog for the first time, the default security settings of Internet Explorer will prompt you to RUN the control. Do not be fooled by the warning, and think it is asking you to install, it is not. Once you accept this, you will need to exit Internet Explorer, and re-visit the site for it to allow you enter. This will only occur the first time you visit the site. Language: English File Size: 67.79 KB MD5: 71d88e67fa34e1ebccb06761a55e748f Download: MediaFire EDIT: Just realized a typo in the entries.ini .. I have fixed it and reuploaded it. The link now points to the fixed one.

So if anyone has been to Windows Update or Microsoft Update since March 25, you may have noticed a new update, KB943729, under Software Updates, the non-critical ones. If you tried to download it manually thru the download center, you might have noticed that after installing, it still shows up in Windows Update/Microsoft Update. This is because the version in the download center is out of date. It was published on 3/6/08, whereas the version on WU/MU was put together on 3/12, even though it wasn't released for just over 2 weeks. Anyways, I just wanted to point out that I have found a valid download location for the one on Windows Update, that is a direct link from Microsoft. Either go to http://catalog.update.microsoft.com and type in the KB ID yourself and find the one for your version of windows, or go to http://www.download.windowsupdate.com/msdo...d734b36ff18.exe for the XP Pro x64 version.

Microsoft Update x64 Addon Microsoft Update is a tool similar to Windows Update, but that may eventually replace Windows Update. Upon visiting the Microsoft Update site, the Microsoft Update ActiveX Control scans your computer to see what updates are available for various Microsoft Software products, including Windows, Office, and a few others. This addon slipstreams Microsoft Update into Windows XP x64 SP2. Note that upon visiting Microsoft Update for the first time, the default security settings of Internet Explorer will prompt you to RUN the control. Do not be fooled by the warning, and think it is asking you to install, it is not. This can be disabled by a registry patch that you run at GUIRunOnce, if you like, but I do not offer that patch. Language: English File Size: 3.46 MB MD5: 102AC563F55DD2C3C03265B40D52B74A Download: MediaFire

So, I decided to have nuhi look at this, and also to take a look at Boooggy's addon. I ended up taking Boooggy's DataStor.edb and putting it in my zip, and it worked.. A few hours later, I got an email from nuhi saying that I had incorrectly named the file.. The file itself was named DataStore.edb instead of DataStor.edb .... Go figure that I wouldn't notice something so stupid. So now I am trying to test it but I think my PSU is failing cause the comp keeps powering down when compressing a 34MB installer, and when I remove that it powers down while recompressing the cabinets..... SO I can't release the pack until I get it tested, but if someone wants to test it for me, please PM me your email, since it is too large to upload here.

But if they weren't installed correctly, you would have compatibility issues because of mixed versions of dll's, not to mention that just because the registry entry is there doesn't mean wu/mu will see the hotfix as installed, because it does check file versions afaik

Yes, the order matters, to an extent. nLite will figure out which updates go where, with the exception being the IE7 installer, and any IE7 updates. What I do is I take my original CD, and integrate IE7 by itself, with no other modification done to the CD, and make an ISO. Then I delete the folder, and extract the IE7 iso into that folder. Then I do all of my hotfix integrations, including IE7 hotfixes (it will figure out which ones go in what order this way), as well as doing all of the other mods (drivers, unattended, patches, and tweaks). Then when nlite gets to the make iso page, I minimize it and run the WMP 11 slipstreamer to integrate WMP11 and all of it's hotfixes. Once that is done, I bring up nlite again and make the ISO. This way when I go to windows update, it shows 0 critical, 0 high priority, and I dont get any compatibility issues.

Hi Boooggy, that pack is great, but I'm a bit of a nut about things (like customers that call support saying that this is wrong etc).. The pack breaks 8.3 filename spec, and includes a cat file that I won't need, to say the least. There's other stuff I could gripe about but, ultimately it boils down to the fact that I am tryin to learn this stuff, so having you do it for me, while much appreciated, doesn't help me figure out why my pack is broken..

That didn't work either. Just to reiterate, the problem is that nlite is not copying the DataStor.ed_ from the temp folder that it extracts addons to, to the source, but it is creating the entries for it in the txtsetup and dosnet files. Possibly a bug?

Thx, I'll try it and report back in a min. What do you mean not using the latest ones? How can I tell? I copied these files from a virtual machine i just installed and went to ms update on.

Anyone? Someone must know why nlite refuses to copy DataStor.ed_ into the source?

So I'm trying to convert xable's MS Update addon at http://xable.net/dl/addons/xable_Microsoft...-v1.1_addon.cab to the 64-bit version of MS Update. I have gotten all the required files, and got the addon to integrate, but when I go to install, 2 files won't copy. wwups2.dll and DataStore.edb .. I found the problem with wwups2.dll .. The entry already existed in TXTSETUP.SIF so I modified the txtsetup_files entry for that file in my entries.ini to mirror that of the entry in TXTSETUP.SIF, but DataStore.edb (DataStor.ed_) for some reason didn't copy to either the AMD64 or I386 directory. Attached are the .inf and entries.ini Note that the entries.ini originally used 100 instead of 1 for the DataStore.edb but that failed, so I changed it to 1, and am testing that now, but I don't know if it will work either. entries_MicrosoftUpdateEngine.ini mu.inf

It shouldn't affect anything with intel processors. It just has a more recent driver date, so when windows looks for drivers for your processor, if this driver supports the processor, windows chooses it over the default one. You dont install this by the inf file, you install it by integrating via nlite's driver integration, or thru device manager, like any other driver. This is NOT an addon, and I will not make an addon version of this. It's too simple to go to device manager, find your processor, right click it and click update driver for me to bother making an addon for it. If this driver does support your processor, the device manager will let you install the driver. If this driver doesn't then it will say unable to find any new drivers for this device. The easiest way to tell if you need this driver is to go to MS update (on a clean non-updated install) and look in the hardware, optional section. If you see anything about AMD Processors, then you know you need it.

There is an update on MS Update for AMD Processors. I couldn't find any info about it on the MS website, but I did manage to find some info about it on the web, and even a download of all of the files it includes so you can manually install it. I've attached it here. It basically enables the AMD Cool'nQuiet features on all processors that support it. This has both the x86 and x64 driver, and the inf will install the proper one for whichever OS (XP or 2k3 32-bit or 64-bit, and possibly even 2k, not sure tho) It can be integrated via nlite's driver integration, and satisfies MS Update. Make sure you integrate this in the driver integration portion, of nlite, not in the Addons section. AMD_Processor_MS_Update.zip

Hm. I think I might have misunderstood the original question. The Driver Signing prompt is probably unrelated to the problem you are experiencing. I'm not sure there what is causing the problem, but it is worth a shot to try the driver signing thing anyways.

There is an update on MS Update for AMD Processors. I couldn't find any info about it on the MS website, but I did manage to find some info about it on the web, and even a download of all of the files it includes so you can manually install it. I've attached it here. It basically enables the AMD Cool'nQuiet features on all processors that support it. This has both the x86 and x64 driver, and the inf will install the proper one for whichever OS (XP or 2k3 32-bit or 64-bit, and possibly even 2k, not sure tho) It can be integrated via nlite's driver integration. EDIT: I have fixed the MS Update issues. The inf included was missing 1 registry key and had the driver date of the original release from AMD. The files were, however identical as indicated by hashtab's CRC32 comparison, so I changed the driver date in the inf, and recompressed the file in zip format AMD_Processor_MS_Update.zip

There is an update on MS Update for AMD Processors. I couldn't find any info about it on the MS website, but I did manage to find some info about it on the web, and even a download of all of the files it includes so you can manually install it. I've attached it here. It basically enables the AMD Cool'nQuiet features on all processors that support it. This has both the x86 and x64 driver, and the inf will install the proper one for whichever OS (XP or 2k3 32-bit or 64-bit, and possibly even 2k, not sure tho) It can be integrated via nlite's driver integration. AMD_Processor_MS_Update.zip

Kel, calm down, someone needs to be the bigger person here and know when to walk away. There is a report post button. Use it. Anyways, aside from the fact that this stuff is against the MS and nlite EULA, the support provided for nlite is only not provided for corporate or business use by nuhi. Anyone else is free to support it if they wish. To answer the question and get this closed, there is an option which can be changed to disable prompts for driver signing. Windows randomly picks what to set this option to in some cases. you can change the option yourself by doing the following: Right Click My Computer and select Properties Click the Hardware tab In the center, click the Driver Signing button Select Ignore - Install the software anyway and don't ask for my approval Select Make this action the system default Click OK twice, and reboot. There is a registry way to do this, but I don't know the exact path. You could probably find it on google, search for "Disable installation prompt for unsigned drivers" or something along those lines. The reason this is happening to be honest, is that most likely some of the drivers you integrated were not properly signed in the first place, or that the drivers you are trying to install on some machines were never signed at all, and so you get this prompt because Windows wants signed drivers, and perhaps the default installer for the drivers signs the drivers, but the way they are being installed now doesn't sign them. Who knows?

The proper way would be to copy your original cd to a folder, and download W2K Service Pack 4. Use nlite to slipstream it, and install in a virtual machine. This way you can see what updates are needed. Once you are up and running on the virtual machine, visit http://www.microsoft.com/mbsa to get the MS Baseline Security Analyzer. Once installed, scan your computer, and it will list all updates needed. Then you have a trimmed list. Once you are looking at the update list, the simplest way to get the updates, In My Opinion, is to go to http://catalog.update.microsoft.com and type in the knowledge base id or the ms security bulletin id (KBxxxxxx or MS0x-xx). Find the appropriate file for your system, and download it. Then once you have them all, open nlite, find your SP4 cd on your drive, select Hotfixes and Update Packs, and insert all of the files you downloaded. Then hit next and yes to start the process. Once done, take the new cd and install it to the virtual machine (format the virtual machine first), and go to windows update to make sure they all installed.

Dang I didn't even know that one. Thx for the info.

I noticed you said you installed .net 2.0 SP1 .. You didn't happen to mention whether it is x86 or x64 framework. That can cause a huge difference. Please specify which you installed, and also try reinstalling it, as it may have gotten corrupted.

in case you didn't already do it, look thru the things you selected for removal in nlite, and make sure you kept nt backup or enabled the NT Backup|Volume Shadow Copy compatibility option, because if you don't keep nt backup then that will disable Automated System Recovery

I'm assuming you use nlite, since this is in the nlite forum, so I just wanted to let you know a few of these tweaks are already in nlite itself, in the tweaks section.

As for the WMP11 updates not being needed, that would be incorrect as well, because the WMP11 updates are applied to WMP11 files, not Windows Files, so even with SP3, the WMP hotfixes will still not be applied. Not to mention that even once SP3 is RTM, it doesn't mean that people won't continue to integrate only SP2, since certain things that some people like (the Address Bar on the Taskbar) are going to be removed.