snooz

Thanks for the splash hide eksasol

You still install QuickTime, this way you don't have too.

Recently switched to Avira Personal and was annoyed by the popup advertisements and the fact you can only update once a day. I figured ways around these limitations and wanted to share it with those of you who use it. By doing them my complaints go to zero on a free application that does everything I need it to. 1) Advertisement pop-ups. They come from avnotify.exe in "C:\Program Files\Avira\AntiVir Desktop" To prevent them from happening do Start | Run | secpol.msc | Software Restriction Policies | Additional Rules | Right click in white space | New Path Rule and set the following... 2) Update more frequently than a day. For those of you who have tried to change the schedule in Avira you cannot change it to anything below a day. You can get around this by disabling the schedule in Avira and handling it through Windows Scheduled Tasks. I am going to assume you know how to create a Hourly task. Here is the command-line: "C:\Program Files\Avira\AntiVir Desktop\update.exe" /DM="1" /NOMESSAGEBOX /receivetimeout=180 /DM="1" hides the message box and /DM="0" shows the box.

Yep you got it. I hate QuickTime so I tried everything to avoid installing it.

That's right. You just need to make some quicktime files available for itunes to open but you don't have to install quicktime. I provided the files you will need.

My skinny package broke pictures in iTunes Store. To get them working again copy CoreVideo.Resources folder and CoreVideo.qtx into QTSystem. You can get them from http://www.megaupload.com/?d=KWIWSJR8 Let me know if anything else is broken.

I went through the registry key and QuickTime folder and got it real skinny. Basically deleted each key and file one by one then opened iTunes to make sure it still worked. Looks like we only need one registry key: [HKEY_LOCAL_MACHINE\SOFTWARE\Apple Computer, Inc.\QuickTime] "QTSysDir"="D:\\Apps\\iPhone\\QuickTime\\QTSystem\\" I shrunk the QuickTime folder down to 17.7 MB from 73.9 MB. All we need is QTSystem which was inspired based off the only required reg location. Inside QTSystem we need: CFCharacterSetBitmaps.bitmap CFUniCharPropertyDatabase.data CFUnicodeData-L.mapping QuickTime.qts QuickTime.Resources QuickTimeAudioSupport.qtx QuickTimeAudioSupport.Resources QuickTimeImage.qtx QuickTimeImage.Resources The folders are... QuickTime.Resources QuickTimeAudioSupport.Resources QuickTimeImage.Resources Inside are a bunch of language folders and I got rid of all of them except English. Here is the skinny download: http://www.megaupload.com/?d=YS5RVP7T Enjoy

All the crap Apple makes you install with iTunes really started to irritate me so I went about hacking it up a bit. I set out to get rid of QuickTime all together and redirect all the folders (iPod for example) into the Program Files\iTunes folder. I will show you how to do it on your own in a few simple steps and then you guys can run with it. 1) First off grap the latest version of iTunes from Apple. 2) Extract iTunesSetup.exe (I used 7-zip) and it will give you the following folders and files: .data .rdata .rsrc .text CERTIFICATE Go into .rsrc | RCDATA and extract CABINET. It will give you the following files: AppleMobileDeviceSupport.msi AppleSoftwareUpdate.msi Bonjour.msi iTunes.msi MobileMe.msi QuickTime.msi SetupAdmin.exe Get rid of the MSI's you don't want to install. I got rid of AppleSoftwareUpdate.msi, Bonjour.msi, MobileMe.msi, QuickTime and SetupAdmin.exe. 3) Next create a Install.cmd to automate the install, this can be used for future versions. msiexec /i AppleMobileDeviceSupport.msi /l*v %TEMP%\AppleMobileDeviceSupport.log /qb If you want to change the folder location for Apple Mobile Device Support you can use the INSTALLDIR= switch seen below. Doing this gave me some strange behavior so I left it default. msiexec /i QuickTime.msi INSTALLDIR="C:\Program Files\iTunes\QuickTime" /l*v %TEMP%\QuickTime.log /qb If you need QuickTime you can use the above command line. You can also use INSTALLDIR= to move the QuickTime folder inside the iTunes Program Files folder. For those of you who hate QuickTime as much as I do this is how you get around installing it. Download this http://www.megaupload.com/?d=KWIWSJR8 This is a package I put together that includes required registry and files for iTunes to function (They are the latest version) without installing. I do not think you need to get updated QuickTime files when a new version of iTunes comes out. I did not try to skinny up the file or registry locations I simply used trial and error to find out the required bulk locations. We could probably get rid of some stuff and get down to the bare essentials. Copy the QuickTime folder anywhere you want. In my case it is located at D:\Apps\iPhone\QuickTime. Edit QuickTime.reg accordingly by changing D:\\Apps\\iPhone\\QuickTime to wherever you decided to put it. Move the QuickTime.reg in the same location as your MSI's. Add the following line to your Install.cmd: reg import QuickTime.reg msiexec /i iTunes.msi IPODINSTALLDIR="C:\Program Files\iTunes\iPod" /l*v %TEMP%\iTunes.log /qb You can use IPODINSTALLDIR= to redirect the iPod folder into Program Files. net stop "iPod Service" net stop "Apple Mobile Device" net start "iPod Service" net start "Apple Mobile Device" After the install I had to restart the services for my iPhone to be detected. This is to avoid rebooting. After all this is done my Install.cmd looks like this: msiexec /i AppleMobileDeviceSupport.msi /l*v %TEMP%\AppleMobileDeviceSupport.log /qb reg import QuickTime.reg msiexec /i iTunes.msi IPODINSTALLDIR="C:\Program Files\iTunes\iPod" /l*v %TEMP%\iTunes.log /qb net stop "iPod Service" net stop "Apple Mobile Device" net start "iPod Service" net start "Apple Mobile Device" When a new iTunes release comes out, extract the MSI's of your choice and all you have to do is run Install.cmd to upgrade. I tested this on two machines and it worked perfect.

Wrong What I find ironic is you are taking credit for the solution when as someone else pointed out that Microsoft released it. Your accusing me of not giving credit when you are the one guilty of it. I appreciate the solution none the less.

Some boards don't like linking to other sites. I mentioned your name and the board that is not "ripping". Shows a lot about you since I praised your work and gave you credit.

Normal process usually entails hex editing sfc_os.dll. I am testing SP3 RC1 and I could not find anyone who had hacked it yet. Searching the net I found a guy who figured out a way to make XP think it was in safe mode thus SFC/WMP is disabled. The cool thing about this hack is no matter what previous or future version you are running WFP can be disabled in the same manner. Using the hex editor method the values constantly change. He also found out a way to enable the security tab when your machine is not a member of a domain. FYI just in case: rshx32.dll = Security tab sfc_os.dll = WFP Credit goes to Neowinian on neowin.net forums for the solution: Here's how to make the Windows XP file system think it's in safe mode. This will disable Windows File Protection, and also add the Security tab when you right-click on a file in Explorer and select Properties. Step 0: XP ships with a simple hex editor called DEBUG.EXE that is required for this procedure. If you deleted it, put it back in the windows\system32 directory -- you can remove it afterwards if you wish. Step 1: Click Start>Run, type in SERVICES.MSC and press the <enter> key. Find the entry labeled Cryptographic Services and double-click it. Change the startup type to Disabled and click Apply, then click the Stop button, and then click OK. (Note: if you already had Cryptographic Services disabled, omit this step as well as step 8.) Step 2: Open a CMD.EXE Command Prompt window and type the following commands: cd \windows\system32 ren rshx32.dll rshx32.old ren sfc_os.dll sfc_os.old You will probably receive warning messages from Windows File Protection after each REN command. Make sure to select the options to ignore the warning and allow the files to be renamed. Step 3: Type the following commands: cd \ del rshx32.dll /s del sfc_os.dll /s cd \windows\system32 copy rshx32.old rshx32.dll copy sfc_os.old sfc_os.dll IMPORTANT!!! You MUST rename the files in Step 2 before you can copy them in Step 3, or this procedure will not work! Step 4: Type the following command: DEBUG rshx32.dll You'll now have a minus-sign as a prompt. Type the following command: S 100 8000 74 00 5C 00 4F DEBUG will return a line of the form: 0ADE:0AC0 The four-character letter-number combination after the colon is what you must enter in the command below. Now type the following three commands: E 0AC0 74 00 00 00 4F (use the value returned to you above and not 0AC0!!!) W Q Step 5: Type the following command: DEBUG sfc_os.dll You'll now have a minus-sign as a prompt. Type the following command: S 100 8000 74 00 5C 00 4F DEBUG will return a line of the form: 0ADE:0AC0 The four-character letter-number combination after the colon is what you must enter in the command below. Now type the following three commands: E 0AC0 74 00 00 00 4F (use the value returned to you above and not 0AC0!!!) W Q Step 6: Type the following commands: copy rshx32.dll dllcache copy sfc_os.dll dllcache Step 7: Close the Command Prompt window, open Regedit, and go to the following key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SafeBoot Create a new DWORD value called OptionValue and give it a value of 1. Close Regedit. Step 8: Run the SERVICES.MSC program, select Cryptographic Services, change the startup type to Manual, and click Apply. Do not start the service! (Note: omit this step if Cryptographic Services was disabled before you began this procedure.) Step 9: Reboot your system. That's it! You will now have the security tab at all times, and Windows File Protection will be disabled. If you would like to remove the tab and re-enable Windows File Protection, use Regedit to change OptionValue to 0, and then reboot your system. The method used to patch RSHX32.DLL and SFC_OS.DLL should work on any version of the file, including future versions issued in upcoming service packs or hotfixes. Please note that if you apply these patches, they will take precedence over safe mode. This means that you must first set OptionValue to 1 in the registry before you boot into safe mode in order to see the security tab and to have Windows File Protection disabled.