Windows 7 upgrade options

by ThomasFox 7. August 2009 09:02

Microsoft has finally set a release date for Windows 7 - October 22, 2009!

With the release coming up in just a few months, some of our clients have been asking about upgrade options. Most PCs that are shipping now include a coupon or a code to upgrade to Windows 7 when it is released. Depending on what version of Windows you are currently running, the upgrade can be pretty simple, or could require a format and reload of your PC.

Here's the bad news: If you're running Windows XP, there is no easy upgrade path for you. You'll have to locate all of your software CDs, backup all of your personal files, and then perform a fresh install.

Windows Vista users have it a little bit easier, with most versions of Vista compatible with their Windows 7 counterpart for purposes of doing an in place upgrade. An in place upgrade means you won't have to reinstall all of your programs - Windows 7 will install over top of and replace your existing Windows Vista installation.

Microsoft has provided a chart that helps with figuring out the best options for you to move to Windows 7. Note that only where you see a green box are you able to retain your installed programs and configurations. Any other situation (the blue boxes) will require a format and reload. (Note: You can click on the chart to open it full size in a separate window.)

Categories: Windows 7 | Windows Vista

How To Deal With Stop Errors

by ThomasFox 4. January 2009 21:32

Stop Errors: Causes

Stop errors can occur due to both software and hardware problems. These include: buggy software programs, faulty or incompatible audio and video drivers, damaged hard disks, a corrupt registry, malware infections, and malfunctioning hardware components, including a faulty motherboard, RAM, or bad power supply.

Stop Errors: Triggers

Stop errors can be triggered by very simple operations, such as plugging in a hardware device - like a printer or a pen drive - or due to any other random event. At times, stop errors may indicate the cause of the error, such as a faulty driver or a system file, and you may be able to fix the error by dealing with the indicated problems. However, sometimes the displayed stop error may mask the root cause and you may end up receiving more errors after you fix the first one. In this case, the real task is to find the root cause of the problem.

General Stop Errors: Troubleshooting

You may use the following steps to troubleshoot a stop error that does not display a specific error message.

  1. Shutdown your PC and open the PC cover.
  2. Ensure that all hardware components and devices are properly seated in their slots.
  3. Start your PC and use a hardware diagnostics tool to run tests on the system and identify any faulty hardware. If you find any, replace it.
  4. Ensure that all hardware components and devices installed on your computer are  in the Windows XP Hardware Compatibility List (HCL). If they are not, replace them with compatible hardware.
  5. Remove/uninstall any new hardware or software.
  6. Use the Fixing a Problem option in the Windows XP Help and Support to view and then perform the steps that may help you identify and resolve possible cause of the stop error.
  7. Open the Event Viewer to see if any error code is recorded for the stop error. If it is, use this code to search for a possible resolution on the Microsoft Knowledge base Web site.
  8. Update your antivirus and antispyware software and then perform a thorough full system scan to eliminate any virus or spyware infection that may be behind the error.
  9. Use a reliable registry tool to scan, clean and repair your Windows registry.
  10. Ensure that your Windows XP operating system and all software and device drivers are updated with the latest service packs and security releases. If they are not, search for, download and install these updates.
  11. If the stop error is stopping from logging on to your computer, start the PC, press F8 and then select the Last Known Good Configuration option and then press Enter.

Specific Stop Errors: Troubleshooting

Some stop errors are displayed with a specific error message that makes it easy to determine the exact cause of the error. The following are some of the examples of such errors along with their descriptions:

You may use the following steps to troubleshoot a software and device driver-related stop error.

  1. Use the Sigverif.exe utility to ensure that the driver identified in the stop error is a signed driver or not.
  2. Use the Device Manager utility to uninstall and then reinstall the driver that caused the error, or to search for, download and install an update for the driver generating the stop error.
  3. If you have recently installed a new driver or a driver update, uninstall or disable it and check to see if the error goes away. If it does, then this new driver or update must be removed or repaired to permanently get rid of the error.
  4. In case your video driver is not shipped with Windows XP, try to switch to the standard VGA driver or another compatible Windows XP video driver.
  5. Use the System Restore utility to revert your system back to the time when it was error-free.
  6. Try to remove any recently added RAM. Delete the pagefile.sys file and then restart your PC. If you do not receive any error now, it might indicate that the new RAM chip is either faulty or incompatible with your system.

You may use the following steps to troubleshoot a file system stop error:

  1. If your computer has a SCSI adaptor, do the following:
    • Install the SCSCI driver.
    • Disable sync negotiation for SCSI devices.
    • Ensure that SCSI chain is properly terminated.
  2. If your computer has IDE devices, do the following:
    • Ensure that the onboard IDE port is defined as Primary only.
    • Ensure that the Master/Slave/Only settings of your IDE drives are correct.
  3. Use hard disk tools, such as chkdsk and Disk Defragmenter to check your disk for errors.
  4. Run antivirus and antispyware scans to remove any malware infections. Use a registry repair tool to clean your registry and repair any invalid entries within it.
Tags:
Categories:

Defrag Myth Busters – What You Should Know

by ThomasFox 1. January 2009 15:26

There are many serious misconceptions about fragmentation which, if believed, can lead to significant computer damage.  Debunking these myths could save your system or network.

Fragmentation is one of the most serious problems that plague computers around the globe.  It accounts for billions in lost revenue and production.  It is also one of the leading causes of a wide range of common computer problems, system failures, and early hardware replacement.  Why don’t users and IT departments take more action to protect themselves against fragmentation?  The following defrag myths may explain why.   

Myth:  My system or network doesn’t have fragmentation. Wrong.  It is estimated that there are over 700 million PCs actively-in-use in the world today, and every single one of them has fragmentation issues to one degree or another.  The reason? Fragmentation is an unavoidable by-product of all Window’s-based operating systems.  Thus your system or network is basically “born” with this defect from the beginning – a situation basically unknown to many users.    

Myth:  I already have defrag software already preinstalled in my operating system. This myth is, perhaps, more responsible than any other for the many misconceptions about defragmentation software.  There IS a kind of defragmentation software that comes pre-installed with many operating systems - but it is a technological dinosaur.  Don’t be misled:  There is no comparison between the modern versions of this technology and what comes pre-installed.  The best advice is to download a copy of a modern defrag software and see the differences for yourself (see below).  

Myth:  Defragmenting my network during work hours will causes disruptions in performance. This is a major and legitimate concern among IT professionals.  Administrators cannot afford to take chances during the workday, and are often forced to work nights and weekends in order to do systems maintenance (like defragmentation).  But choosing a high performance defragmenter that is specifically designed for networks will allow a systems administrator to defrag the system without affecting productivity.  Companies such as Diskeeper (www.diskeeper.com) make highly advanced network defragmentation software which is completely transparent when running in the background. 

Myth:  I have to replace my computer due to slow performance. Not necessarily.  Fragmentation is the scattering of data and files across the hard drive.  As fragmentation builds up, pieces of data become increasingly scattered, and the read/write head takes longer and longer to write and retrieve data.  This shows up as sluggish, slow performance, and eventually freeze-ups and systems failure.  It is very possible, however, that a defrag of the system with a high quality defragmenter will restore your ailing system or network to maximum performance. 

Myth:  Using defrag software is a hassle. Another misconception stemming directly from the use of the pre-installed version.  Unfortunately, it’s a lot like comparing a horse-and-buggy to a race car.  The bundled version makes defragmentation a hassle because it is indeed S-L-O-W.  It takes forever to do a not-very-good-job of defragmenting your drive or server.  Modern defragmentation software is lightening fast by comparison and the best ones are so completely automatic that you can basically forget about them and not worry about fragmentation issues any longer once they’re installed.    

Myth: Defrag software is expensive.  The best companies have a full line-up of defragmentation products that one can choose from online.  Whether you’re a home user, small business, government agency, or huge company with hundreds of servers and thousands of workstations, you can find a download to suit your needs and give the software a trial run.  The cost savings could potentially be enormous.  Research shows that the resultant increase in productivity, the reduction of down-time, and the increased longevity of hardware make the relatively low cost of defragmentation software insignificant by comparison.   

Don’t let a myth prevent you from finding out whether your system is running at peak performance or not.  The best recommendation is to talk with one of our technicians at Tech Experts - we'll help you understand your options for effective disk defragmentation.

Categories: Maintenance

Excel 2003: "Math class is hard!"

by ThomasFox 14. December 2008 15:28

Microsoft tech support folks say a patch released last week to fix security vulnerabilities in Excel 2003 causes the spreadsheet to multiply things incorrectly.

The error shows up if a patched version of Excel is linked to a real-time data source through macros built with Visual Basic for Applications, according to Microsoft.

The patch, known as MS08-014, was released for Excel 2003 Service Packs 2 and 3.

Microsoft said that the company has issued a new patch -- to patch last week's patch. They've patched the patch!

If you're not running Excel 2003, this release doesn't apply to you and you don't need to be concerned about the patched patch.

The original patch was designed to plug a security hole that could allow remote code execution if users open Excel in certain ways -possibly allowing an attacker to gain control over affected systems.

This is just the latest in a long line of Excel-related math problems. Last year Microsoft issued a patch for Excel 2007 for a problem that caused Excel 2007 to produce significant multiplication errors. That flaw occurred during calculations that would ordinarily result in, or be close to, the number 65,535. Instead, Excel 2007 would produce a result of 100,000.

It isn't just Microsoft and Excel that have math issues from time to time. Does anyone remember the Pentium FDIV recall from 1983?

We're just glad they usually get fixed pretty quickly!

Tags:
Categories: MSOffice