23 replies to this topic

[Cristiano]

no, because 3 main reasons:
1 - the current version of autopatcher was unable to fully detect seven rc. probably, the same issue will happen to the rtm version;
2 - we don't have any rtm version, only the rc ones;
3 - lack of time;

the reasons 2 and 3 can be bypassed by anyone with goodwill and time. but the 1st reason can be a problem...

[]s

[Angelico_Payne]

Is it true that Autopatcher will no longer be needed in case of updating Win 7 (x64/x86), and that instead of using it, u can just trigger place updates in certain folder and trigger MS update service and then restart (all via 1 batch script)?

[TechSwap]

So that means there won't be any kinda autopatcher for win7 now that it has come out this past Oct 20, 2009? So does that mean we will have to use something like Belarc Advisor to do our own updates rather then use the bloated windows update?? If what you say it true then the later software which is free will become the choice of users whom don't have the bandwidth and or want to manual download and do their own update on their own time. Cause their site does mention support for Win7 O/S. Don't get me wrong I used and still like autopatcher but lately belarc has told me I was missing some netframework and office '07 updates which my previous autopatcher didn't inform me about. I still use both to compare and see what I am missing and what I should look for. To me it's not bad having to source so to be sure one is secured as possible and up to date with the latest that matches ones' setup. I will go and format my test computer one of these days and test how good belarc does on Win7 updates so as to be sure if I should go full out Win7 or wait a bit or I will use the test computer and download the Win7 updates and slipstream it and burn a working Win7 and use that to format making it updated Win7 but I will wait til I get my test computer going.

[_def_x_]

-> So that means there won't be any kinda autopatcher for win7

I would say this last week has created some hope that indeed there may be an AutoPatcher for Windows 7 release BUT, this
is important...This will be more than simply creating a new script, there will need to be additional coding as well, lots of testing
an so on. Windows 7 is New - a release will take some time but looks promising. BUT, yes I said it, we will need someone
with the OS to create and test both AutoPatcher's ability to correctly identify Windows 7, as well create and begin testing a
windows 7 script. BTW, it is still October (for me anyway)

-> So does that mean we will have to use something like Belarc Advisor to do our own updates

You are free to use whatever application best meets your needs, there are a few options out there but the list is getting thin.
It is a lot of work to create an application like AutoPatcher or Belarc let alone maintain it.

-> but lately belarc has told me I was missing some netframework and office '07 updates

If you would make a list of the missing updates and post the information in the appropriate forum(s) it would be appreciated.

-> I still use both to compare and see what I am missing and what I should look for.

I think this is smart, it is always a good idea to get a second or even a third opinion - multiple tools are a good idea.

[Cristiano]

> we will need someone with the OS
i have one of the betas. but i will start buy the parts for my new machine next week (i had to make some room at my credit cards. seven himself is already too expensive around here. something about R$ 680 or about US 387). as it will be an quad-core at least, xp pro is out of question. so, i will buy one retail version of it. probably, 7 ultimate (just because xp mode). but as i will keep the xp scripts, i still have high hopes for new tam members

about belarc, i'm not sure if it includes non public updates, but match all .net public updates may be tricky. but it can be done with autopatcher

[]s

[mbonwick]

I don't know if AutoPatcher will be necessary with Win7. From what I've heard from people who use it, it's possible to get Microsoft Update to download updates into a specific folder, and then run them with a batch script.

[Cristiano]

that it's also possible for all OS's from ms, even win 95. and still, we are here. the issue isn't download all, it's download just the required ones and, from times to times, certain updates become obsolete. if you don't know that, goodbye. yes, you also can look for the replaced ones and remove, but then everyone that needs update a lot of machines (like myself) will require do that alone. and we do their job far more easy...

[]s

[TechSwap]

Well that's good to hear but I ain't that much in a rush to go Win7 just migrating slowly to it but more like testing it to see if it will work as good as XP pro. But that doesn't mean XP is gone from my computer for good just that just that this time hopefully M$ does a better job then ahhhem.. bloated vista... or Mojave...lol... But when you do get a Win7 autopatcher I give it a run when I get the Win7 O/S installed...til then it's still XP pro sp3....for the time being.

[Cristiano]

well, what i can say about seven... it worked in ancient machines very well. but xp will receive updates only until 2014 and doesn't work so well in quad-core machines as seven does

[]s

[Netizen]

I got Windows 7 x64 installed finally. But I still can't find the time to volunteer.

Sorry guys.

Wife + Promotion in work + BSc.

Hopefully one day I'll be in a position to assist more

[Cristiano]

for sure. but we are still developing an new autopatcher to handle with seven. since we have to build it from scratch, it will take some time yet

by the way: congratulations by your promotion

[]s

[Cristiano]

we are working on it now. first, apup is being developer further. then, an new autopatcher, capable of run under seven without worries will born. but that will take some time yet

[]s

[Kim100]

With Dell and other manufacturers going totally x64 on their windows 7 machines perhaps it is time to bite the bullet and go totally x64 with Autopatcher for windows 7 and finally put 32 bit computing to rest.

I have tried x64 in the past in XP and Vista flavors but the support always seemed to be lacking from hardware and software vendors, they will no longer have the choice of ignoring x64, so past problems should quickly disappear.

Catering for Win7 x64 only would make things a lot easier for the Autopatcher team I would imagine.

I hope it happens

[TechSwap]

Cristiano, on 01 November 2009 - 01:02 AM, said:

well, what i can say about seven... it worked in ancient machines very well. but xp will receive updates only until 2014 and doesn't work so well in quad-core machines as seven does

[]s

Really, that's the first I heard it or missed it somehow. hmm...guess I have to go and check. Cause I do have quad-core machine and if that rings true I might just have to jump to win7 even if I catch the win7 bugs... . I most likely will go Win7 but I had hope for all the bugs LMAO was fixed -that's a dream long go- but if Win7 is good as I read in the other forums I registered then it might be time to take the dip. Then just after that wait for autopatcher to catch with the bugs fixes then I be in business.

[TechSwap]

Kim100, on 12 November 2009 - 07:13 PM, said:

With Dell and other manufacturers going totally x64 on their windows 7 machines perhaps it is time to bite the bullet and go totally x64 with Autopatcher for windows 7 and finally put 32 bit computing to rest.

I have tried x64 in the past in XP and Vista flavors but the support always seemed to be lacking from hardware and software vendors, they will no longer have the choice of ignoring x64, so past problems should quickly disappear.

Catering for Win7 x64 only would make things a lot easier for the Autopatcher team I would imagine.

I hope it happens

That's sounds all good and true but there are more 32 bit machine out there then you would think. I have a quad-core machine and would like to use a win64bit cause you can run 32bit in 64bit only if you get 64bit software will you really see a improvement over 32bit apps. And those software are far and few right now. The software market makers will cater to the mass and world not just US markets. And I know for sure those other markets don't have Win7 or 64bit software to just jump onto.

[Cristiano]

true. but the good thing about seven 64 is that this this one runs even better than the x32 version, even if you have less than 4GB of RAM. but the sad part is the software support. so far, there's just a few that take advantage of an x64 OS

[]s

[TechSwap]

Cristiano, on 12 November 2009 - 11:39 PM, said:

true. but the good thing about seven 64 is that this this one runs even better than the x32 version, even if you have less than 4GB of RAM. but the sad part is the software support. so far, there's just a few that take advantage of an x64 OS

[]s

I know I like to go 64 but man the price is so expensive just for OEM starter package is $179US. wow....it's not expensive but with my budget that takes a hit....I might later this month go 7 but I like to wait for autopatcher win7 before jumping in so I can make sure I get all the needed updates. It never hurts to have 64 that will 32 software still otherwise we be all in a pickle.

[Cristiano]

well, there's 64 bit editions for several versions. it doesn't need to be ultimate, you know. in Brazil, each license is far more expensive than in US and we can't buy it in family packs, nor have the same wallpapers than the rest of the world has (those can be reached with a few tricks, but isn't far you buy for something and find and be forced to that)

as for autopatcher for seven, well, we will start an catalog for the updates this weekend and then start build the modules. but those will not be public for sometime, because we will beta test the new autopatcher first and we are just making an list of the most important bugs and issues that has to be fixed first. and this will take some time yet...

[]s