Jump to content

Aethec

Experienced Members
  • Posts

    1,701
  • Joined

  • Last visited

Posts posted by Aethec

  1. Viruses still get on the system anyway and things get broken all the time. I clean viruses off customers machines almost daily. When file permissions get screwed up you cant install updates, programs crash and other things happen as well. Had a user who couldn't get a service pack installed. It was because of file permissions. After this repair was ran the service pack is installed. Also a lot of viruses out there mess up the file and reg permissions. The goal of these repairs is to get the system working again after the permissions have been screwed.

     

    The unhide system files I made because of a virus that is out there the marks every single file on the drive as hidden. After seeing it on a few of my customers machines I wanted a way to unhide them again but still leave the system files hidden like they normally are. So that is this repair.

    I understand. But these kind of fixes need big red warnings. Remember, if it becomes popular you'll have people trying to "fix" their computers by checking every checkbox, ruining their computer in the process.

     

    PS: Any idea how to fix a non-working Task Scheduler that says it can't find tasks (this: http://social.technet.microsoft.com/Forums/en/w7itprogeneral/thread/a9e485d3-06ba-4038-a9b8-1b58e73ea4dd except I don't want to delete every single task, because that makes the Task Scheduler useless)? If you do that, I'll build an altar in your honor.

  2. Some of these "fixes" look weird.

     

    Reset File Permissions: "The repair will grant administrators, system, users and everyone full rights to every file on the C: drive."

    WTF? The whole point of Vista/7's strict rights are to avoid getting in this situation ; the only account which should have all these permissions is TrustedInstaller. Otherwise, a virus infecting one user can do anything it wants without having admin rights.

     

    Unhide non system files: "This repair will unhide every file on the system that is not a system file."

    This one should get a big red mention "don't ever do that unless you are really, really sure it's gonna help you".

  3. Or just use IE9 and enable ActiveX filtering to disable everything but the ones you really need, and then enable others on a case-per-case basis. Just like you would do with NoScript.

     

     

    By the way, the "ActiveX exploits" are the same as the NPAPI ones, unlike what many free software fanboys want you to believe IE hasn't got any super-critical unpatched vulnerabilities...

  4. Does this also apply if the CPU came from Intel ?

     

    Yes. The "x86-64" architecture is commonly referred to as AMD64 because AMD invented it, even when talking about Intel processors.

    Checking for the presence of SysWoW64 is a hack, and might stop working in the next version of Windows ;)

     

    (Intel's 64-bit architecture is the Itanium, which failed in the consumer market because it lacks compatibility with 32- and 16-bit instructions - which is also the reason they created UEFI since the standard BIOS is 16-bit only)

  5. 2 GB of RAM should make a difference ; anything above will have a smaller effect.

    SSDs are awesome ; your disk is usually the performance bottleneck, and netbook/notebook drives are usually slow (5400 RPM vs 7200 on normal PCs)

    Win7 x64 probably won't install on your netbook, many Intel Atoms are x86 only.

     

    Do not, ever, ever, ever disable Aero if your graphic card can run it. It offloads the work to the GPU instead of having the CPU handle everything.

     

    PS : A dual-core processor @ 1.66 GHz != a single-core processor @ 3.32 GHz. Multiple cores are much more efficient, because they can do multiple things at the same time.

  6. I know this is over a month since the last post - but this is relevant.

     

    http://arstechnica.c...s-horrified.ars

     

    "a version of WPF built on top of Direct2D"

    The writer doesn't know anything about WPF...

    Direct2D was created because C++ programmers wanted hardware-accelerated graphics since C# programmers had them with WPF, not the other way around. WPF is already fully hardware-accelerated.

     

    Some tech writers need to calm down, think, and realize .NET isn't going to be left behind.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.