Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


GreenMachine

Developer
  • Content Count

    3,070
  • Donations

    $0.00 
  • Joined

  • Last visited

Posts posted by GreenMachine


  1. Thank you, for putting into words what I had only been thinking about doing.

    I had looked at the hotfix slipstreaming since I started slipstreaming last year, and was always detered by the tediousness, not to mention the warnings in all info I could find about it. My reasons were two fold: 1) To insure that the CD and the instalation had the same files, thus if windows file protection should really need to get back, the right version was on the CD, and not inside some hot fix. 2) Reduce the 30 minutes or so it seems to take to run the hotfixes (never figured out why it works so quicky when doing it from the Windows Update site). Part 1 is solved, but the hot fixes are still run, each and every one. (Sure takes a long tiome to go from 13 to 12 minutes left.) The point of my drawn out post is that whilst running the hotfixes during the instalation, it leaves behind many log files (Q??????.log) and copies of the cat files (SET??.tmp) all over the %SYSTEMROOT%. If you want to keep the install clean and minimailist, you may want to add the command to delete this files.

    And again, thanks for sharing.


  2. From what I've read, the alexa thing in IE is mis-identified by Ad-Aware as a ad/spy ware program (that has the same name). It is, in fact a part of IE, though there does not seem to be any harm in deleting the key, and then Ad-Aware doesn't bug you about it anymore. Just what I've read ... never given me problems in or out.

    From some forum page somewhere ...

    I skimmed through quickly. Most of those are safe to delete. The Alexa registry key is one from Microsoft and is not the alexa that ad-ware is trying to recognize.

    Alexa is a toolbar that some consider spyware (I don't) but the registry key Ad-Aware istrying to delete is from Microsoft, not alexa and is being flagged just because it has the same name.


  3. My 2 cents ...

    ;Right click to (un)register DLL files, open in Notepad by default.
    [HKEY_CLASSES_ROOT\dllfile\shell]
    @="View"
    [HKEY_CLASSES_ROOT\dllfile\shell\Register]
    [HKEY_CLASSES_ROOT\dllfile\shell\Register\command]
    @="C:\\WINNT\\system32\\REGSVR32.EXE \"%1\""
    [HKEY_CLASSES_ROOT\dllfile\shell\UnRegister]
    [HKEY_CLASSES_ROOT\dllfile\shell\UnRegister\command]
    @="C:\\WINNT\\system32\\REGSVR32.EXE /u \"%1\""
    [HKEY_CLASSES_ROOT\dllfile\shell\View]
    [HKEY_CLASSES_ROOT\dllfile\shell\View\command]
    @="C:\\WINNT\\System32\\NOTEPAD.EXE \"%1\""

    ;Open folders in Explorer view.
    [HKEY_CLASSES_ROOT\Folder\shell]
    @="explore"

    ; Open scripts with Notepad by default - do not run.
    [HKEY_CLASSES_ROOT\VBSFile\Shell]
    @="Edit"
    [HKEY_CLASSES_ROOT\VBEFile\Shell]
    @="Edit"
    [HKEY_CLASSES_ROOT\JSFile\Shell]
    @="Edit"
    [HKEY_CLASSES_ROOT\JSEFile\Shell]
    @="Edit"
    [HKEY_CLASSES_ROOT\WSHFile\Shell]
    @="Edit"
    [HKEY_CLASSES_ROOT\WSHFile\Shell\Edit\Command]
    @="Notepad.exe %1"
    [HKEY_CLASSES_ROOT\WSFFile\Shell]
    @="Edit"

    ;Clean up NEW Templates
    ;This will remove these items from the "New" context menu.
    [-HKEY_CLASSES_ROOT\.bfc\ShellNew]
    [-HKEY_CLASSES_ROOT\.bmp\ShellNew]
    [-HKEY_CLASSES_ROOT\.doc\WordPad.Document.1\ShellNew]
    [-HKEY_CLASSES_ROOT\.rtf\ShellNew]
    [-HKEY_CLASSES_ROOT\.wav\ShellNew]
    [-HKEY_CLASSES_ROOT\.zip\CompressedFolder\ShellNew]

    ;Remove WMP Right Click Options (Queue-it-up, etc.)
    ;Remove the Queue-it-up, Burn to CD right click options on Windows Media Player files.
    [-HKEY_CLASSES_ROOT\CLSID\{CE3FB1D1-02AE-4a5f-A6E9-D9F1B4073E6C}]
    [-HKEY_CLASSES_ROOT\CLSID\{F1B9284F-E9DC-4e68-9D7E-42362A59F0FD}]
    [-HKEY_CLASSES_ROOT\CLSID\{8DD448E6-C188-4aed-AF92-44956194EB1F}]


  4. Boy, this one bugged me ...

    My unattended XP CD worked fine, with all the latest critical updates. However, Windows Update consistantly reported that the Blaster Worm update, 823980, needed to be installed. Repeated installs from the site were of no avail. The 823980 Scanner tool, used from another PC, reported that the update had been installed. To make a long story short, after a day of trial and error, it turns out that Windows Update relies on the presence of registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\KB823980 to (very scientifically) determine if the patch has been applied. No "Uninstall" keys are created during a "/N" install, and subsequent install would report that the installation completed successfully, though it obvioussly crapped out once it found the correct file versions, and did not bother to update the registry.

    And this is the patch they are ranting and raving about? No wonder the solution to the famous worm was to take WindowsUpdate offline ...

×
×
  • Create New...