Jump to content


  • Posts

  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by snooz

  1. You still install QuickTime, this way you don't have too.
  2. 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.
  3. Yep you got it. I hate QuickTime so I tried everything to avoid installing it.
  4. 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.
  5. 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.
  6. 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
  7. 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.
  8. 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.
  9. 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.
  10. 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.
  11. http://www.broadcom.com/support/ethernet_nic/faq_drivers.php 79.) How do I install Windows 2000 and Windows XP using Remote Installation Services? Microsoft Remote Installation Service(RIS) Instructions for Adding Broadcom Network Adapter Driver Problem: An error is encountered when attempting to load the Broadcom device driver for a 32-bit version of Windows XP or later operating system using a Windows 2000 Remote Installation Server: File b57w2k.sys caused an unexpected error (21) at line 3752 in d:\xpsp1\base\boot\setup\setup.c. Solution: A modification to the b57win32.inf file can be made to allow for the installation to complete successfully. This will be in conjunction with instructions from the Microsoft Knowledge Base Article 315279 that describe "How to Add Third-Party OEM Network Adapters to RIS Installations." Requirement: The Windows 2000 Server must be running Service Pack 3 or later. Obtain the latest driver for your Broadcom adapter. The driver files included for the Broadcom 57xx adapter are b57win32.inf, b57win32.cat, and b57xp32.sys. Create a copy of the b57win32.inf and b57xp32.sys files and locate them in a separate folder called RIS. This will allow you to distinguish them from the originals. For the b57win32.inf file located in the RIS folder, make the following change using a text editor like Notepad: Locate [Manufacturer] within the file. Review the line below which reads: %BRCM% = Broadcom, NTx86.5.1, NTamd64. Modify that line to read: %BRCM% = Broadcom.NTx86.5.1, NTamd64. The change made replaces the comma and space after "Broadcom" with a period. Save the file. On the RIS server, copy the b57win32.inf and b57xp32.sys files from the RIS folder to the RemoteInstall\Setup\Language\Images\Dir_name\i386 folder. (This allows Setup to use the driver during the text-mode portion of the installation). At the same level as the i386 folder on the RIS image, create a $oem$ folder. Use the recommended structure: \$oem$\$1\Drivers\Nic Copy the original b57win32.inf, b57xp32.sys, and b57win32.cat driver files to this folder. Make the following changes to the .sif file that is used for this image installation: [unattended] OemPreinstall = yes OemPnpDriversPath = \Drivers\Nic Stop and then restart the Remote Installation service on the RIS server. To do this, type the following from a command prompt: net stop binlsvc net start binlsvc
  12. This might work: On Error Resume Next For I = 0 To 9999 If WshShell.RegRead ("HKLM\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002bE10318}\" & Trim(Format(I,"0000")) & "\Afterburner") = "1" then WshShell.RegWrite "HKLM\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002bE10318}\" & Trim(Format(I,"0000")) & "\Works", "1", "REG_SZ" End If Next If you run RegMon you will see that this is not efficiant but it looks like it should work. I don't care about the efficiency too much. I am using this reg key I tested this script Didn't work for me and I also did a regmon and I don't see any activity in this location: HKLM\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002bE10318}
  13. I get some errors On line 3 when it is not commented out I get an invalid syntax error. On line 11 I get "cannot use parentheses when calling a sub". If I don't put the parenthesis in there it gives expected end of statement.
  14. I am trying to automate WLAN adaptor settings with a vbscript. The same as doing a properties on WLAN adaptor and clicking on advanced tab. The main registry path is consistent on every machine: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002bE10318} Problem is the subkey that houses the settings is not consistent. The subkeys will look something like this: 0001 0002 0003 0004 0005 0006 0007 0008 I am trying to figure out a way to search the subkeys for a value that is unique to my WLAN adaptors (Which are all Broadcom) and then once the subkey is identified (0008 for example) write the values that I want in there thus automating the configuration. Here is an example of my WLAN card registry key: I know you can do the same thing with a bcmpn.wpn profile: http://support.dell.com/support/topics/glo...0401E0A551752E7 It works flawlessly if the machine is fresh but if the adaptor or wireless connection reads with a 1,2,3 at the end of the name it stops working. I really need a solution that will work no matter what. VB Gurus help me out
  15. What this reg key changes in IE7 is the menu text "Windows Update" under Tools in the old style "Menu line" (File Edit View etc...), but it will not change at the new button style Tools menu. Thats what I thought you were looking for (change menu text). What do you mean by button style tool menu? Sorry I were unclear. This is a screenshot from the Norwegian IE7, but I think you will see my point Thanks for the pic I get the same behavior. The Menu Tools shows up as Microsoft Update and the Tools Menu Windows Update.
  16. blink I just tested this with an IEAK package and I get exactly what you describe. When I install from the regular package the registry key works. Even with the IEAK package Windows Update still goes to Microsoft Update. If club and babe can confirm they are using IEAK we should know the cause at least.
  17. Try this registry location instead: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server] On the service stuff try this: sc config termservice start= auto sc start termservice
  18. What this reg key changes in IE7 is the menu text "Windows Update" under Tools in the old style "Menu line" (File Edit View etc...), but it will not change at the new button style Tools menu. Thats what I thought you were looking for (change menu text). What do you mean by button style tool menu?
  19. Hmmm can you try and install IE7 install that is not IEAK just to see. Is this a corporate environment are any GPO's in place? I can play around with IEAK tomorrow and see if it messes mine up.
  20. More than likely one of the lines in your cmd has a problem. When using SMS always specify for the package to download locally then execute. Post your script and I can help you with it.
  21. No, it doesn't, at least not in my case. I have IE7 and Microsoft Update and--like BoardBabe--IE7 is still displaying "Windows Update" in Tools. Hmmm . . .Edit: for those interested, you might want to check out the program HERE. Looks like it's designed to revamp the look and feel of your browser. It should but even if it doesn't you can control it with this registry key: [HKEY_CURRENT_USER\Software\Policies\Microsoft\Internet Explorer] "Windows Update Menu Text"="Microsoft Update" That key is created when you install Microsoft Update. If that is not working for you you got something that has messed up IE7. I would run hijackthis and clean up any thing 3rd party with your browser.

  • Create New...