Early versions of Windows were pretty graphic user interfaces - desktops. This stemmed from the fact that they were run from the operating system MS-DOS and used the mechanisms in the field even file handling. On the other hand, even these early 16-bit operating environment had some features of a full operating system, such as having their own executable file format and their own device drivers (timer, display devices, printers, mouse, keyboard or sound generating devices) used by applications. Differently than was possible in MS-DOS, Windows overlays allow you to run multiple applications simultaneously, operating in the mode of cooperative multitasking. Another feature of the 16-bit Windows implementation was to use a complicated system of segmented virtual memory is supported in software, and this system enabled the application to run a size in excess of the amount of available computer memory. Segments of data were brought to the memory and removed from it, if only the free space has fallen dangerously. The data also underwent the movement, if the application does not require constant monitoring by the CPU, for example, waiting for the introduction of user data. The environment using this technology to Windows 1.0, released in 1985, and Windows 2.0 (year 1987), together with the associated environmental Windows/286.
Windows/386 introduced into the environment of the kernel for 32-bit protected mode CPU and monitor virtual machines. For the period of the session created an overlay of one or more virtual 8086 environments, enabling the virtualization of devices (video card, keyboard, mouse, timer and interrupt controller) for each of them. User-visible effect of this technology was the ability to run multiple environments, MS-DOS mode, multi-tasking to expropriation, each of which was run in a separate window (graphics applications MS-DOS required a transition to full screen mode). Applications designed for Windows was still running in multitasking mode, cooperative, and each was placed in a separate environment.
Environment Windows 3.0 (year of publication 1990) and Windows 3.1 (year 1992) significantly improved the above-described mechanisms, primarily through the use of virtual memory and are loaded virtual device drivers (VxD). which allowed individual DOS windows running in multitasking shared use of contractual devices. With these solutions, Windows applications can be run in 16-bit protected mode (both the Windows environment to work in standard mode and enhanced mode, processor 386) to give access to several megabytes of memory, were also exempt from having to use virtual memory system supported by software. Continue to operate in a common address space, where they were partially protected by the memory segment, and their execution is accomplished in a cooperative multitasking mode. For Windows 3.0, Microsoft also wrote in assembler part of the key features of the environment, reducing memory requirements and accelerated platform for its operation.
After an introduction to the Windows for Workgroups 3.11 32-bit file access, the Windows platform could eventually resign from the management of files by the DOS operating system. Using the features of the new mechanism, the Windows 95 operating system made it possible to use long file names, and their limitations DOS file names (8 characters plus 3 extension names) has been reduced to the role of the boot loader when the computer starts. Windows 95 and ME, the successor to version therefore had two nuclei, the environment: just after take-off run DOS, and a moment later, multi-tasking environment (desktop). DOS itself was supplied with Windows, making it (partially) handle long file names, if its applications were called from Windows. Microsoft's competitors do not accept these new heat. The most important feature of the new system was able to run 32-bit multi-threaded graphics programs operating in multitasking mode of expropriation. Unfortunately, the need to maintain backward compatibility with 16-bit programs meant that the GUI components were still 16-bit, this does not fully reentrant, which resulted in reduced system performance and stability of his troubles.
Windows 95 was released in three versions: the first one debuted in 1995 and another in 1996 and 1997. Two later versions were only available in the OEM editions, and one of the most important features are implemented in a FAT32 file system and correct operation of USB devices (version OSR2.1). Another product was a series of Windows 98, which appeared on the market twice - in 1998 and known as Windows 98 Second Edition a year later. In 2000 Microsoft released Windows Me (Me is a shortcut Millennium Edition), based on the code of Windows 98, but in matters of appearance is designed as Windows 2000. Another introduced in Windows Me System Restore was the option that allowed the user to restore the system settings for a specific day. It was not warmly welcomed the solution, because in many cases resulted in conflicts. Windows Me was adopted in the market as "filler" on the road to a full merger of the two branches developed by the Microsoft operating systems. Microsoft product but did not give sufficient time to "settle" on the market before it introduced Windows XP.
Monday, March 7, 2011
Saturday, March 5, 2011
Offering a Perfect Solution for Cost-Effective and Efficient Database Req
Microsoft Access database is one of the most popular desktop database systems at the moment. Although the nature of requirement of a database solution for any organization changes from time to time and as such few issues do crop up over time, there is no doubt that MS Access affords the best possible solution in its class.
No wonder, it is overwhelmingly preferred over other database management systems for all its advantageous features vis-à-vis other database solutions. Also, one of natural advantage of MS Access is that it is a product of Microsoft. One of the questions often asked before considering a database is how long is the product likely to be available and supported? And in this regard, no other database management system can dominate MS Access. Being a product of Microsoft, availability and support of this database is assured for several years to come. Again, when it comes to development consulting and support, no other desktop database system can match what Access enjoys.
There are also other reasons that explain why Microsoft Access is the most widely used desktop database system in the world. For one, Access database is quite flexible. Although this database solution is especially developed for small organizations where it is intended to support about fifty simultaneous users, it is possible to link together few Access databases. Moreover it can also be ported with larger database like SQL Server. Again, it requires lesser investments to develop, implement, and maintain Access database.
MS Access comes as a part of Microsoft Office Professional suite of business products and as such you may not require additional database software. It can also seamlessly integrate with other products of Microsoft Office suit such as Excel, Word and Outlook etc. Lastly, it can be placed on your website so that it is accessed by remote users as well. MS Access as such has many features which can be advantageous for your organization. And if you want to develop Microsoft Access software, you can rely on Alpha Software, which one of the leading database developers offering several kinds of database software development at one of the most competitive prices.
No wonder, it is overwhelmingly preferred over other database management systems for all its advantageous features vis-à-vis other database solutions. Also, one of natural advantage of MS Access is that it is a product of Microsoft. One of the questions often asked before considering a database is how long is the product likely to be available and supported? And in this regard, no other database management system can dominate MS Access. Being a product of Microsoft, availability and support of this database is assured for several years to come. Again, when it comes to development consulting and support, no other desktop database system can match what Access enjoys.
There are also other reasons that explain why Microsoft Access is the most widely used desktop database system in the world. For one, Access database is quite flexible. Although this database solution is especially developed for small organizations where it is intended to support about fifty simultaneous users, it is possible to link together few Access databases. Moreover it can also be ported with larger database like SQL Server. Again, it requires lesser investments to develop, implement, and maintain Access database.
MS Access comes as a part of Microsoft Office Professional suite of business products and as such you may not require additional database software. It can also seamlessly integrate with other products of Microsoft Office suit such as Excel, Word and Outlook etc. Lastly, it can be placed on your website so that it is accessed by remote users as well. MS Access as such has many features which can be advantageous for your organization. And if you want to develop Microsoft Access software, you can rely on Alpha Software, which one of the leading database developers offering several kinds of database software development at one of the most competitive prices.
Friday, March 4, 2011
First look Microsoft SharePoint 2010 beta spreads the wealth II
Backup is improved. The backup and restore capabilities built into SharePoint 2007 were blunt instruments. In SharePoint 2010 you can be more selective about restores by browsing an unattached content database, locating the sites or lists you need, saving them, then restoring them to the production database.
Scripts and sandboxes
While script-based administration has detractors as well as supporters, I find the PowerShell command support in SharePoint 2010 to be a big plus and a big improvement over the older (but still maintained) Cmd.exe and Stsadm.exe environments. Yes, there are too many cmdlets to learn easily (100 core Windows cmdlets and 300 SharePoint cmdlets), but they have a help system, they pipe together in logical ways, and in many cases you'll only have to figure out a command sequence once, then save the script and apply it to other sites. Overall, that's a big time saver over going through the GUI for every site in every farm.
On a SharePoint server with many custom controls and large lists, one site that hogs CPU, memory, or database requests can damage the performance of all the sites on the server or even all the sites using the database. Throttling and list controls in SharePoint 2010 allow an administrator to control this per Web application.
In addition, custom solutions can be sandboxed, meaning that they can be given a restricted set of permissions and resource quotas, then run isolated. Sandboxing reduces the risk of allowing site owners to deploy their own solutions, balancing freedom against safety. Quota templates keep the overhead of controlling sandboxed solutions reasonable.
Branding in SharePoint 2010 has been made easier by revamping the way themes work. SharePoint 2010 themes are now compatible with PowerPoint themes. In many cases, companies will be able to import existing PowerPoint themes to apply the fonts and colors of the corporate brand. Perhaps future SharePoint sites won't all look like they've been turned out with the same cookie cutter.
SharePoint 2010 for developers
SharePoint 2010 is much more attractive for developers than SharePoint 2007 ever was. I wouldn't be surprised to see many ASP.Net developers adopt SharePoint 2010 for their larger customized sites. There will be less code to write, without giving up too much in the way of flexibility.
The list of improvements is long. In addition to better API support and more extension points, there is better tool support in Visual Studio 2010, Visio, and SharePoint Designer 2010. There's a straightforward way to connect to line-of-business applications. Many functions have been exposed to RESTful interfaces. There are more application templates. Debugging and monitoring are much better. And sandboxes offer a measure of protection for custom applications that was lacking previously.
Visual Studio 2010 offers a dozen SharePoint 2010 project types in two languages, C# and Visual Basic. Empty projects are used more often than you'd think, as containers for multiple controls, workflows, and other project items. A Visual Web Part is a new kind of project that combines a Web Part class with an ASP.Net user control; the latter can be designed visually within Visual Studio 2010, which makes Web Part design much easier than writing code to instantiate child controls. The downside of a Visual Web Part is that it cannot be deployed to a sandbox.
SharePoint workflows can be sequential or state machines, and they can be one-offs or parameterized reusable workflows. Workflows can be designed using Visio or SharePoint Designer in addition to Visual Studio. In SharePoint 2010, workflows do not have to be associated with a list. They can instead be site-level workflows, with their own start pages; this is an improvement.
Microsoft MCTS Certification, MCITP Certification and over 2000+ Exams at Actualkey.com
Scripts and sandboxes
While script-based administration has detractors as well as supporters, I find the PowerShell command support in SharePoint 2010 to be a big plus and a big improvement over the older (but still maintained) Cmd.exe and Stsadm.exe environments. Yes, there are too many cmdlets to learn easily (100 core Windows cmdlets and 300 SharePoint cmdlets), but they have a help system, they pipe together in logical ways, and in many cases you'll only have to figure out a command sequence once, then save the script and apply it to other sites. Overall, that's a big time saver over going through the GUI for every site in every farm.
On a SharePoint server with many custom controls and large lists, one site that hogs CPU, memory, or database requests can damage the performance of all the sites on the server or even all the sites using the database. Throttling and list controls in SharePoint 2010 allow an administrator to control this per Web application.
In addition, custom solutions can be sandboxed, meaning that they can be given a restricted set of permissions and resource quotas, then run isolated. Sandboxing reduces the risk of allowing site owners to deploy their own solutions, balancing freedom against safety. Quota templates keep the overhead of controlling sandboxed solutions reasonable.
Branding in SharePoint 2010 has been made easier by revamping the way themes work. SharePoint 2010 themes are now compatible with PowerPoint themes. In many cases, companies will be able to import existing PowerPoint themes to apply the fonts and colors of the corporate brand. Perhaps future SharePoint sites won't all look like they've been turned out with the same cookie cutter.
SharePoint 2010 for developers
SharePoint 2010 is much more attractive for developers than SharePoint 2007 ever was. I wouldn't be surprised to see many ASP.Net developers adopt SharePoint 2010 for their larger customized sites. There will be less code to write, without giving up too much in the way of flexibility.
The list of improvements is long. In addition to better API support and more extension points, there is better tool support in Visual Studio 2010, Visio, and SharePoint Designer 2010. There's a straightforward way to connect to line-of-business applications. Many functions have been exposed to RESTful interfaces. There are more application templates. Debugging and monitoring are much better. And sandboxes offer a measure of protection for custom applications that was lacking previously.
Visual Studio 2010 offers a dozen SharePoint 2010 project types in two languages, C# and Visual Basic. Empty projects are used more often than you'd think, as containers for multiple controls, workflows, and other project items. A Visual Web Part is a new kind of project that combines a Web Part class with an ASP.Net user control; the latter can be designed visually within Visual Studio 2010, which makes Web Part design much easier than writing code to instantiate child controls. The downside of a Visual Web Part is that it cannot be deployed to a sandbox.
SharePoint workflows can be sequential or state machines, and they can be one-offs or parameterized reusable workflows. Workflows can be designed using Visio or SharePoint Designer in addition to Visual Studio. In SharePoint 2010, workflows do not have to be associated with a list. They can instead be site-level workflows, with their own start pages; this is an improvement.
First look Microsoft SharePoint 2010 beta spreads the wealth
You'd also think that Microsoft has locked all SharePoint users into installing Microsoft Office, but SharePoint 2010 includes Office Web Apps, the new Web-based editions of Word, Excel, PowerPoint, and OneNote. In the brief time I spent with them when evaluating the SharePoint beta, the Office Web Apps looked very promising, at least for viewing documents. (See InfoWorld's "first glimpse" at the Office Web Apps Technical Preview and InfoWorld's comparison of Office Web Apps with Google Docs and Zoho.)
SharePoint 2010 for IT professionals
SharePoint 2010 promises IT professionals improved productivity, a scalable unified infrastructure, and flexible deployment. These features can be used to help provide governance and high availability. But again, they come at the cost of needing an up-to-date 64-bit server and database infrastructure.
Although server requirements are narrower, client support is broader. SharePoint 2010 fully supports 32-bit IE 7, IE 8, and Firefox 3.x running on Windows. Also, 64-bit IE 7 and IE 8, Firefox 3.x on non-Windows systems and Safari 3.x are supported as "level 2" browsers; they can be used to administer the site, but pages may not render with perfect fidelity. IE 6 is not supported. Site administrators can tune their content and CSS to support additional browsers for reading the site, but keep in mind that the AJAX and ASP.Net code used for editing SharePoint content is complex and under Microsoft's control.
I applaud Microsoft for dropping IE 6 support in SharePoint 2010. The company points out that it's not standards-compliant, which is not exactly breaking news. I hope Microsoft can stick to that decision; it might pave the way for the rest of us to be able to drop IE 6 support for our Web products.
Administrators have a choice of installing SharePoint 2010 with a GUI or with configuration files and PowerShell scripts. The former is easier; the latter is better for server farms and for disaster recovery. A new requirement is a Farm Passphrase, which protects a server farm from unauthorized server drops and adds.
Smooth transitions
Upgrades can be done in place or by attaching a database backup from SharePoint 2007 to a new SharePoint 2010 installation. Databases can run read-only during the upgrade to minimize downtime. Administrators can force all sites to upgrade to the new master pages and CSS, or allow each site owner to run with the old styles, preview the upgrade, correct any issues, and finally switch over to the new styles.
Administrators now have more control over SharePoint site proliferation. It's a two-pronged strategy: Use Active Directory Markers to keep track of SharePoint servers, and/or use Group Policies to control where SharePoint can and can't be installed.
The redesigned Central Administration pages in SharePoint 2010 are easier to understand and use; there's a lot less searching for tasks than before, and a lot less jumping around from menu to menu is required. The new layout is reminiscent of the Windows Vista control panel, but don't let that dissuade you -- it's still much better organized than before. The new ribbon interface does help to keep like functions clustered, and the new wizards make some of the harder setups easier to complete successfully.
Best Microsoft MCTS Training – Microsoft MCITP Training at Certkingdom.com
It's always been relatively easy to convert Word documents to SharePoint pages, as well as to display PowerPoint slides online. In SharePoint 2010, you can also use Excel Services or Visio Services to publish spreadsheets or diagrams for browsing.SharePoint 2010 for IT professionals
SharePoint 2010 promises IT professionals improved productivity, a scalable unified infrastructure, and flexible deployment. These features can be used to help provide governance and high availability. But again, they come at the cost of needing an up-to-date 64-bit server and database infrastructure.
Although server requirements are narrower, client support is broader. SharePoint 2010 fully supports 32-bit IE 7, IE 8, and Firefox 3.x running on Windows. Also, 64-bit IE 7 and IE 8, Firefox 3.x on non-Windows systems and Safari 3.x are supported as "level 2" browsers; they can be used to administer the site, but pages may not render with perfect fidelity. IE 6 is not supported. Site administrators can tune their content and CSS to support additional browsers for reading the site, but keep in mind that the AJAX and ASP.Net code used for editing SharePoint content is complex and under Microsoft's control.
I applaud Microsoft for dropping IE 6 support in SharePoint 2010. The company points out that it's not standards-compliant, which is not exactly breaking news. I hope Microsoft can stick to that decision; it might pave the way for the rest of us to be able to drop IE 6 support for our Web products.
Administrators have a choice of installing SharePoint 2010 with a GUI or with configuration files and PowerShell scripts. The former is easier; the latter is better for server farms and for disaster recovery. A new requirement is a Farm Passphrase, which protects a server farm from unauthorized server drops and adds.
Smooth transitions
Upgrades can be done in place or by attaching a database backup from SharePoint 2007 to a new SharePoint 2010 installation. Databases can run read-only during the upgrade to minimize downtime. Administrators can force all sites to upgrade to the new master pages and CSS, or allow each site owner to run with the old styles, preview the upgrade, correct any issues, and finally switch over to the new styles.
Administrators now have more control over SharePoint site proliferation. It's a two-pronged strategy: Use Active Directory Markers to keep track of SharePoint servers, and/or use Group Policies to control where SharePoint can and can't be installed.
The redesigned Central Administration pages in SharePoint 2010 are easier to understand and use; there's a lot less searching for tasks than before, and a lot less jumping around from menu to menu is required. The new layout is reminiscent of the Windows Vista control panel, but don't let that dissuade you -- it's still much better organized than before. The new ribbon interface does help to keep like functions clustered, and the new wizards make some of the harder setups easier to complete successfully.
Thursday, March 3, 2011
Apple Updates QuickTime for Windows Kills Two Bugs
Apple has released QuickTime 7.6.8 for Windows, which fixes two vulnerabilities limited to the Windows version.
The first glitch was the famous (in some circles) '_Marshaled_pUnk' vulnerability. Apple left this value in QuickTime for Windows as a valid parameter, but removed the code to handle it. This allowed an attacker to place their own code to run. Check out a video of the vulnerability in action below.
The second issue is described as "Viewing an image in a maliciously prepared directory." What it seems to be is the Windows malicious DLL loading problem as implemented in the QuickTime Picture Viewer. Apple removed the current working directory from the search path to fix the bug.
The first glitch was the famous (in some circles) '_Marshaled_pUnk' vulnerability. Apple left this value in QuickTime for Windows as a valid parameter, but removed the code to handle it. This allowed an attacker to place their own code to run. Check out a video of the vulnerability in action below.
Best Microsoft MCTS Training – Microsoft MCITP Training at Certkingdom.com
The second issue is described as "Viewing an image in a maliciously prepared directory." What it seems to be is the Windows malicious DLL loading problem as implemented in the QuickTime Picture Viewer. Apple removed the current working directory from the search path to fix the bug.
The Microsoft Certified Professional Program
The Microsoft Certified Professional (MCP) program provides the best MCSA required exams method to prove your command of current Microsoft products and technologies. The exams and corresponding certifications are developed to validate your mastery of critical competencies as you design and develop, or implement and support, solutions with Microsoft products and technologies. Computer professionals who become Microsoft certified are recognized as experts and are sought after industry-wide. Certification brings a variety of benefits to the individual and to employers and organizations.
The Microsoft Certified Professional program offers multiple certifications, based on specific areas of technical expertise:
Microsoft Certified Professional (MCP). Demonstrated in-depth knowledge of at least one Microsoft Windows operating system or architecturally significant platform. An MCP is qualified to implement a Microsoft product or technology as part of a business solution for an organization.
Microsoft Certified Solution Developer (MCSD). Professional developers qualified to analyze free 70-291 test questions, design, and develop enterprise business solutions with Microsoft development tools and technologies including the Microsoft .NET Framework.
Microsoft Certified Application Developer (MCAD). Professional developers qualified to develop, test, deploy, and maintain powerful applications using Microsoft tools and technologies including Microsoft Visual Studio .NET and XML Web services.
Microsoft Certified Systems Engineer (MCSE). Qualified to effectively analyze the business requirements, and design and implement the infrastructure for business solutions based on the Microsoft Windows and Microsoft Server 2003 operating system.
Microsoft Certified Systems Administrator (MCSA). Individuals with the skills to manage and troubleshoot existing network and system environments based on the Microsoft Windows and Microsoft Server 2003 operating systems.
Microsoft Certified Database Administrator (MCDBA). Individuals who design,implement, and administer Microsoft SQL Server databases. Microsoft Certified Trainer (MCT). Instructionally and technically qualified to deliver free Microsoft certification exam questions Official Curriculum through a Microsoft Certified Technical Education Center (CTEC).
Microsoft MCTS Certification, MCITP Certification and over 2000+ Exams at Actualkey.com
The Microsoft Certified Professional program offers multiple certifications, based on specific areas of technical expertise:
Microsoft Certified Professional (MCP). Demonstrated in-depth knowledge of at least one Microsoft Windows operating system or architecturally significant platform. An MCP is qualified to implement a Microsoft product or technology as part of a business solution for an organization.
Microsoft Certified Solution Developer (MCSD). Professional developers qualified to analyze free 70-291 test questions, design, and develop enterprise business solutions with Microsoft development tools and technologies including the Microsoft .NET Framework.
Microsoft Certified Application Developer (MCAD). Professional developers qualified to develop, test, deploy, and maintain powerful applications using Microsoft tools and technologies including Microsoft Visual Studio .NET and XML Web services.
Microsoft Certified Systems Engineer (MCSE). Qualified to effectively analyze the business requirements, and design and implement the infrastructure for business solutions based on the Microsoft Windows and Microsoft Server 2003 operating system.
Microsoft Certified Systems Administrator (MCSA). Individuals with the skills to manage and troubleshoot existing network and system environments based on the Microsoft Windows and Microsoft Server 2003 operating systems.
Microsoft Certified Database Administrator (MCDBA). Individuals who design,implement, and administer Microsoft SQL Server databases. Microsoft Certified Trainer (MCT). Instructionally and technically qualified to deliver free Microsoft certification exam questions Official Curriculum through a Microsoft Certified Technical Education Center (CTEC).
Wednesday, March 2, 2011
How to Install Windows 7
So you’ve decided to take the Windows 7 plunge, having heard all the paeans to Redmond’s latest operating system. For many users, setting it up will be a simple case of popping in the installation disc and following the prompts. But there are a few steps you should take and decisions you need to make before and during the process.
Check Your Machine’s Specs
The first thing to do is check whether your desktop or laptop PC is capable of running Windows 7. If it’s already running Vista with acceptable performance, then the answer is yes. Officially, you need at least a 1-GHz CPU and 1GB RAM, but testers of the OS have successfully got it running on machines as out of date as a 266-MHz Pentium II with 96MB of RAM. Go ahead and try that kind of thing if you want, just don’t use your license key on that type of machine. It may run, but you’ll spend a lot of time waiting for it, and it won’t display the glassy new Aero interface and enhancements.
Best Microsoft MCTS Training – Microsoft MCITP Training at Certkingdom.com
If you’re unsure whether your current system can run Windows 7, download and run Microsoft’s Upgrade Advisor to assess your hardware’s capabilities. When I ran it on an aging XP laptop, it told me I needed to back up my files and perform a Custom installation (see below), that my hard disk didn’t have enough free space (you need 16GB), and that the laptop wouldn’t run Aero Desktop. The good news, however, was that my 1.6-GHz CPU and 1.5GB RAM were sufficient. The advisor actually checks a lot more than the basic system requirements, and it lists every piece of hardware and software you have installed at the bottom of its report.
Choose an Edition
There are lots of different editions of Windows 7, but only three you can buy: Home Premium, Professional, and Ultimate. For most people, Home Premium will make the most sense. If your company decides to upgrade, Professional supports domain joining, network backup, and XP emulation. Ultimate includes everything in both other versions, and adds BitLocker encryption.
The key thing to consider here is that you have to do a clean installation—without the ability to carry your apps along—if you move from one level of Vista to another level of Windows 7, say from Vista Home Premium to Windows 7 Professional. The exception is Windows 7 Ultimate, which will let you perform an in-place upgrade from any level of Vista—as long as you don’t change whether you’re using the 32- or 64-bit version.
Don’t forget to look into special pricing offers, such as those for students and family packs. And if you’re installing on a machine you’ve freshly built, you can pay less for OEM versions that don’t include all the packaging and support. The Student upgrade license is just $29.99, and PC part suppliers offer the OEM versions at steep discounts as well.
Choose 64-bit or 32-bit
Any computer manufactured in the last few years will probably have a 64-bit capable CPU. The rule of thumb is that if you have, or intend to install, more than 3GB of memory on your PC, you want 64-bit Windows.
And don’t worry about your old 32-bit programs—compatibility features inside Windows allow most of these to run in the 64-bit OS, the exceptions generally being antivirus software and hardware drivers. One significant holdback, however, is Adobe’s Flash: If you run the 64-bit version of Internet Explorer that comes with Windows 7, you won’t be able to view Web sites that use Flash. But there’s an easy fix: Run 32-bit IE for those sites until Adobe gets with the program.
Both 32- and 64-bit installation discs come in the Windows 7 box, so you only have to specify which you want if you’re downloading the code. In short, my recommendation is that if your system can run 64-bit software, go for it: You’ll be using your CPU and memory more efficiently, and you’ll be future-proofed for upcoming 64-bit apps. —next: Back Up Your Data >
Subscribe to:
Posts (Atom)