5 replies to this topic

[atkokus]

This was my first attempt to run AutoPatcher. APUP ran & downloaded everything fine (about 960MB worth of WinXP, .NET, IE, etc.). Ran AutoPatcher and only selected patches that had not yet been installed on my system. It ran all the installs successfully. Clicked 'Finish' which rebooted my machine. After BIOS splash, I only have a flashing cursor in the upper left corner. No other bootable discs/devices are connected to computer (other than single internal hdd). Left for 15 minutes - no change. Rebooted again. Same issue. Booted off a BartPE XPSP3 CD I made - boots fine & HDD is accessible/readable.

Any ideas?

Thanks!

[_def_x_]

Hi atkokus, sorry to hear you're having troubles.

First, AutoPatcher is nothing more than a GUI that chains your selected updates for installation then reboots your system. Unlike say a reg cleaner or a drive partition tool that actually is doing something to a system, AutoPatcher is really pretty useless without the updates (exe files) or regedit to make any selected registry tweaks. If you look at the image I posted, this is AutoPatcher without any updates to install, the program is Official and without any updates AutoPatcher wont even get to the main screen - no Next tab to press.

It is hard to say what update(s) are giving your system troubles - what all did you install? This is not the first time an update has created problems for some systems. 900+MB is a lot of files, did you try to update IE to the next major version (6 to 7, 7 to 8) or install .NET 3.5SP1 along with additional updates? We try to stress a few important things - the user needs to know exactly what they are installing and why (some updates can break some systems). Additionally, install major version updates (IE7, IE8, .NET, DirectX etc) one at a time and not with other patches or updates - get the big things done individually, reboot, and make sure all is well, then apply patches to the new version.

We can try and assist you but you need to elaborate on what specific updates you installed. The problem (from my perspective) is too many users are simply point and click any more and they take few precautions when it comes to updating their system - they select everything in one fell swoop and expect it to work - this can be a crap shoot.

[Cristiano]

that wasn't suppose to happen. possibilities:
- check for the presence of those files, into your boot partition: IO.SYS; MSDOS.SYS; NTDETECT.COM; ntldr. isn't required that boot.ini be present, but it's advisable at least;

- if you have access to that disk, boot with that disk, then select your hd, right-click, properties, tools, check disk and check at least the first option;

- if possible, run an diagnose tool at your disk, if possible, the tool designed by the brand of your hd;

of course, check for cables is an idea too. also, sometimes an defective memory can corrupt things. may be an idea check it as well

[]s

[sullivang]

gUiTaR_mIkE, on 30 December 2010 - 12:44 AM, said:

The problem (from my perspective) is too many users are simply point and click any more and they take few precautions when it comes to updating their system - they select everything in one fell swoop and expect it to work - this can be a crap shoot.

I'd expect a utility like this to work EXACTLY like this, and I'm not surprised users are experiencing problems.

Greg.

[Cristiano]

> I'd expect a utility like this to work EXACTLY like this
i agree, but there's an issue: autopatcher has certain tweaks that can increase system performance, security and other stuff, by changing certain behaviors. do you wanna old search on? do you require disable sharing? do you require enable clear type and other stuff? do you require wmp11, ie8, wga, jornal viewer, messenger 5.1 and other stuff? if not, then you should care about what you select to install. it is in a certain way like your car. just because it shows that has an top speed of 240km/h (~150 miles/h) should you increase to that speed all times, even when is raining or snowing?

[]s

[_def_x_]

Quote

I'd expect a utility like this to work EXACTLY like this, and I'm not surprised users are experiencing problems.

I'm not sure why you bothered to post at all, it sounds like you're not a fan of AutoPatcher in the first place. I guess it was to bless us with your wisdom of how things should work.

Btw, there are many tools including AutoPatcher that do many things but you hope the user understands a bit of good judgement goes a long way. AutoPatcher can start the installation for DirectX, DOTNET, Internet Explorer, perform a few registry tweaks - but do you really want to perform these tasks AT THE SAME TIME - I hope the answer is NO