When they analyze at the bugcheck data, they discover that the fault is being caused by a Kernel-Mode driver component of their AV program. During their testing of Windows Vista during the Beta, they discover that if they are running an older version (version 11.0) on Windows Vista, that the system randomly bugchecks. In this scenario, we have an ISV who supports several versions of their AV program for multiple Windows platforms, including Windows 9x, Windows ME, Windows NT4 and Windows 2000 / XP / 2003. Now that we've identified the difference between the two types of blocking, let's take a look at a sample scenario that illustrates where an ISV might request a hard block or soft block.
Note: The approval to create hard blocks or soft blocks for a non-Microsoft program must come from that program's ISV In these instances, the program will run, but the user will be presented with a dialog box indicating that there are known compatibility issues. Soft Blocks indicate that the program in question has a compatibility issue, but the effect on the system is not severe.
When a program is hard blocked, the PCA will display a dialog box indicating that the program is blocked due to compatibility issues, and the program will not run. A Hard Block means that the program is known to be incompatible and running the program could result in severe system errors - such as causing a system crash or a no-boot scenario. So, what's the difference between the two?Ī Hard Block, as the name implies, means that this application either will not run or will not install on Windows Vista / Windows Server 2008. Depending on the nature of the issue, the application may be Hard Blocked or Soft Blocked. This list is maintained in the System Application Compatibility Database. When a user launches a program, if that program is on a list of programs that are known to have compatibility issues, then PCA informs the user of this.
Let's get started with looking at Application blocking. Today, we are going to examine some program startup scenarios (specifically application blocking) and discuss the management of the Program Compatibility Assistant. In our previous post on PCA, we discussed several runtime issue detection scenarios. First published on TECHNET on Oct 05, 2007
0 kommentar(er)
