About AutoPatcher November 2006...  

178 members have voted

  1. 1. Pick what releases you want for November!

    • Full, Lite, Update, QMUP
      30
    • Full, Lite, Update
      40
    • Full, Lite, QMUP
      11
    • Full, Lite
      36
    • Full, QMUP
      36
    • Update, QMUP
      6
    • Update
      19


Recommended Posts

OMG nooooo :( i need update release, so what is WMP11 and IE7 is out you might aswell download it from microsoft plus there WGA protected and i speak for most people here that most people who use autopatcher are using it because there windows isnt legit so they won't have any use for these 2 files.

But i really need the Update Release as im formating my Computer soon.. i don't need no other release other then that one :(.

just my 2 coppers worth:

why dont we start having a regular schedule for full releases (Jan, Apr, July, Oct), with updates between. then if it is posted clearly and prominently, there will be fewer questions as to which is coming out.

Also, i vote update and QMUP

McG

I'm not sure if having a 'scheduled full' releases will justify issuing one out if it's less than a few dozen megs for an update.

Having said that, I'd prefer a full release...:)

I don't care much for the QMUP so my vote was null though.

Raptor - whatever you'll come up with - I, as I guess many here, will be most grateful for!

forget ie7 and wmp11 because uses wga check on install and unattended setup don't possible

autopatcher has to remain unattended during install because end users don't have much technician skills

i forgot to tell you that installer 3.1 v2 setup needs fixing because displays an anoying error during install

forget ie7 and wmp11 because uses wga check on install and unattended setup don't possible

autopatcher has to remain unattended during install because end users don't have much technician skills

i forgot to tell you that installer 3.1 v2 setup needs fixing because displays an anoying error during install

If you are afraid of wga check, don't install them :devil:

I agree with Project Mayu. The contents to be included. MS did not include WP11 nor .net v3 in November updates. Some of these updates were delayed for additional 2 days :angry:. I was brassed off because i thought ms normaly inc all updates 2nd tuesday of every month.

Greetings....

My understanding is that the Lords of MS have determined IE 7 to be in the category of critical security updates, however, to minimize the support load, they have decided to spoon feed distribution to the masses via Microsoft Update on a limited scale.

My opinion (free and you get what you pay for) is that this technically makes IE7 a go for inclusion with autopatcher XP if the intent is to help people maintain patched and secure systems.

On the flip side.... I've already run into a situation with a university using collaborative / white board software plug ins that have crashed gloriously after IE7 is installed. So yes.... there are some compatibility issues with 3rd party stuff.....

It boils down to whether the need is to keep autopatcher as a tool to keep current with the latest thinking at microsoft or to allow people who use autopatcher a chance to test for compatibilty issues.... how long will that take vs how soon do folks want a more secure / feature packed browser.....

Life is full of trade offs.... just ask my ex.....

You make a good point about IE7 being a security update, but IE6 SP2 is still in Microsoft's support lifecycle - and security patches will continue. IE7 still has compatibility issues (as you mentioned) so it should be optional until such time that IE7 is mainstream(Say, the retail release of Vista). It's like how AutoPatcher continued to support Windows XP SP1 after the release of SP2.

I think that there should be a Full release... Get the work done so you don't fall behind in any updates. And a QMUP to keep supporting those that use or depend on it.

Well, it seems to me that Autopatcher is intended to be used by the majority and not the minority. As long as IE6 is being used over IE7 by a significant percentage, it seems only logical to focus on IE6 still. I myself like IE7 and all, but it's use is not dictated by either myself or the use of AP.

CFT1119_102011128AB.png

According to Net Applications, you can see the current trends of browser usage as of Oct '06.I'd think if you set a threshold of IE6 to IE7 users, say a ratio of 60/40 respectively, then that would be a more appropriete time to change focus of which IE browser that AP is focused on.

Another alternative to consider is simply setting a timeframe down. Just make an announcement like "Autopatcher will no longer offer further support of IE6 after XX of 2007".

IE7 and WMP11 not important because nobody uses it

I don't like your tone of voice.

JC Denton (Deus Ex)

Full

With

IE 7

WMP 11

Dot net 3

and remove all old patches that don't apply to above, such as ie6 updates and dot net 2 as its in 3

All that + WD.

You make a good point about IE7 being a security update, but IE6 SP2 is still in Microsoft's support lifecycle - and security patches will continue. IE7 still has compatibility issues (as you mentioned) so it should be optional until such time that IE7 is mainstream(Say, the retail release of Vista). It's like how AutoPatcher continued to support Windows XP SP1 after the release of SP2.

WMP10 is optional, and so will be WIE7 and WMP11 (logically).

Well, it seems to me that Autopatcher is intended to be used by the majority and not the minority. As long as IE6 is being used over IE7 by a significant percentage, it seems only logical to focus on IE6 still. I myself like IE7 and all, but it's use is not dictated by either myself or the use of AP.

You've got point, but you're forgetting that there were months until the majority started using (for example) SP2 after it had been released.

You make a good point about IE7 being a security update, but IE6 SP2 is still in Microsoft's support lifecycle - and security patches will continue. IE7 still has compatibility issues (as you mentioned) so it should be optional until such time that IE7 is mainstream(Say, the retail release of Vista). It's like how AutoPatcher continued to support Windows XP SP1 after the release of SP2.

There may be a time in the not too distant future when MS support guru's respond to IE performance and security issues with the "just upgrade to IE 7" catch phrase to resolve reported issues and close vulnerabilities.....

Also... in the not too distant future.... if users have automatic updates enabled, as they should, then they will be receiving the IE7 install via WU... they will wake up one morning, launch IE7 and wonder "how did I get here?".... (saw david byrne just the other day... he's same as he ever was)... unless they have installed the IE7 blocking tool, that's going to be a very common scenario.... from my understanding everyone should be updated by Vista rollout to the masses late January... once IE7 is installed, embedded in the registry, etc.... one will have to essentially rebuild / reinstall XP SP2 to restore IE6 (this from experience).... also keep in mind that the Lords of MS have determined it far more cost effective to support only one version of IE....

If I'm understanding the intent of those hard working and dedicated folks that put together this wonderful gizmo called AutoPatcher (note... proper use of case....and respect).... it's to help us be able to patch/update either computer OS builds "built from scratch" or large and incomprehensible numbers of workstations... the process would drive even normal tech geeks (oxymoron) completely insane without the use of this tool.... how far ahead of the curb are our benefactors intending to stay?

Ok..... enough babbling on.... here's another log for the thought fire.... how long before MS realizes "hey... you know what... we need to patch IE7 because of the (fill in the blank) vulnerability...." .... this makes me wonder (humbly).... do the folks at autopatcher want to continue providing patches for both IE6 and IE7?.... what about size of D/L and bandwidth (considering that many of those using AutoPatcher do so because of lack of these)...

BTW to everyone working on AutoPatcher.... It's your project and do it anyway you see fit... Thanks very much and have a good holiday week... Happy Thanksgiving to everyone...

I remember that SP2 came out when AutoPatcher Full was near 250-300mb. With Microsoft not releasing SP3 for Windows XP for a year to come, I'm afraid that AutoPatcher releases will keep getting bigger and bigger. :(

Thats ok I have auotpatcher on a external 2.5 laptop hard drive enclosure, as long as it stays under 30 gigs i'll be happy :laugh:

well, if someone is thinking about remove old updates if ie7 or wmp11 is installed, forget about it. i've installed that just to see what can i found on windows update. i've found this list:

critical

KB873339

KB885835

KB885836

KB886185

KB887472

KB888302

KB890830

KB890859

KB891781

KB892130

KB893756

KB894391

KB896358

KB896423

KB896424

KB896428

KB898461

KB899587

KB899591

KB900725

KB901017

KB901214

KB902400

KB904706

KB905414

KB905749

KB908519

KB908531

KB910437

KB911280

KB911562

KB911564

KB911565

KB911567

KB911927

KB912919

KB913580

KB914388

KB914389

KB916595

KB917422

KB917953

KB918439

KB919007

KB920213

KB920214

KB920670

KB920683

KB920685

KB921398

KB922582

KB922616

KB922819

KB923191

KB923414

KB923789

KB923980

KB924191

KB924270

non critical

KB829019

KB900930

KB904942

KB909520

KB914440

KB920342

if someone wanna see by himself, there's updates for wmp 7, 9, 10 on that list. some of them are not listed even also updates for wmp10. and, by the way: autopatcher size is almost the same. i was unable to do an silent instalation for ie7 or wmp11, but i believe that it may be possible. if you bypass wga, it may work, but i believe that it will break the rules

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Brave Browser 1.91.168 by Razvan Serea Brave Browser is a lightning-fast, secure web browser that stands out from the competition with its focus on privacy, security, and speed. With features like HTTPS Everywhere and built-in tracker blocking, Brave keeps your online activities safe from prying eyes. Brave is one of the safest browsers on the market today. It blocks third-party data storage. It protects from browser fingerprinting. And it does all this by default. Speed - Brave is built on Chromium, the same technology that powers Google Chrome, and is optimized for speed, providing a fast and responsive browsing experience. Brave Browser also features Brave Rewards, a system that rewards users with Basic Attention Tokens (BAT) for viewing opt-in ads. This innovative system provides an alternative revenue model for content creators and a way to support the Brave community. SlimBrave Neo takes all the good things about Brave and makes them even better by keeping everything clean, light, and privacy-focused. It removes the extra clutter, turns off features you might not need, and cuts down on anything that could slow you down or collect unnecessary data. Because it relies on simple settings and policies instead of modifying the browser itself, you still get full Brave compatibility—just in a smoother, lighter, and more privacy-friendly package. Brave Browser 1.91.168 changelog: Web3 Added “Get Started” section to the “Portfolio” page. (#54029) Added the ability to view “Asset Distribution” in “Portfolio”. (#54028) Added dotted texture to wallet line chart. (#54216) Migrated Jupiter swap provider to “Gate3”. (#51848) Updated the “Permission” panel to display the site origin. (#54482) Updated NFT balance fetch to remove duplicate entries prior to fetching balances. (#55036) Fixed missing back button on the “Deposit Funds” page. (#55842) Fixed reloading an account tab redirecting to the “Accounts” page. (#54826) Leo Added support for text file uploads with renderer-based extraction. (#54062) Added PDF text extraction at upload time. (#51911) Updated display of Brave Leo attachment previews to scroll horizontally instead of vertically. (#54258) Updated the “Copy” button for the code block header to be sticky when scrolling. (#53704) Updated the staged content in the Leo side panel to be the active tab. (#53533) Updated the search terms in the answer’s footer to be left aligned. (#54204) Fixed crash which could occur in certain cases when using multiple tool requests. (#55438) General Added support for Brave Origin. (#37127) [Security] Added the ability to disable or delay automatic extension updates when brave://flags/#brave-user-extension-auto-update is enabled. (#7200) Enabled ability to force context menu using “Shift + Right Click” by default. (#54790) Improved performance by caching adblock DATs. (#27161) Updated background color for PWA install button in the omnibox. (#54736) Fixed tab hover card position when using vertical tabs. (#54199) Fixed extra border displaying around the content area when vertical tabs are used on macOS. (#54153 & #52961) Fixed audio farbling distortion in multi-voice Web Audio API synthesized music. (#52906) Upgraded Chromium to 149.0.7827.54. (#55943) Download: Brave Browser 64-bit | 1.2 MB (Freeware) Download: Brave Browser 32-bit View: Brave Homepage | Offline Installers | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Thanks Microsoft but no, I find both iterations of Outlook terrible nowadays and switched back to Thunderbird at home.
    • Happens to the best of us, bro. 😛 
    • Thanks to some of the other recent Windows improvements, I'm optimistic about this one. My quick wishlist would be: perf like the older menu, merge both menus or at the very least, the older menu should be a flyout, not a simulated click to the old menu, and lastly, a customization window to let users move items from one menu to another, so I could bring Send To back to the main menu, and the OneDrive settings to the older.
  • Recent Achievements

    • One Year In
      CHUNWEI earned a badge
      One Year In
    • Conversation Starter
      FBSPL earned a badge
      Conversation Starter
    • Week One Done
      I2D earned a badge
      Week One Done
    • Week One Done
      Dr Jared Dental Studio earned a badge
      Week One Done
    • Week One Done
      RG INVESTMENT GROUP earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      466
    2. 2
      PsYcHoKiLLa
      253
    3. 3
      Skyfrog
      80
    4. 4
      FloatingFatMan
      63
    5. 5
      Michael Scrip
      62
  • Tell a friend

    Love Neowin? Tell a friend!