Tag Archives: resolved

ATI / AMD Catalyst 12.2 Preview Driver

ATI / AMD have released the Catalyst 12.2 preview driver you can obtain the driver from here http://support.amd.com/us/kbarticles/Pages/Catalyst122Previewdriver.aspx

The AMD Catalyst™ 12.2 Preview includes all of the features found in AMD Catalyst™ 12.1, plus additional fixes that are not included in the AMD Catalyst 12.1 release.

Highlights of the AMD Catalyst™ 12.2 Preview Windows® release includes:

IMPROVEMENTS

  • AMD Eyefinity 2.1 technology enhancements
  • Additional resolution support:   Users can now choose from a larger set of resolutions when running AMD Eyefinity
  • Dynamic Configuration Changes:  Switching between different display configurations will occur automatically when physically plugging/un-plugging displays
  • HydraVision™ enhancements:  The Windows® Task bar can now be moved and resized based on users preference
  • Profile Manager improvements:  Increased support for Display Groups (including 5×1) and Extended configurations within the Profile Manager

RESOLVED ISSUES

Resolved Issues for the Windows® 7 Operating System

This section provides information on resolved known issues in this release of the AMD Catalyst™ 12.2 Preview software suite for Windows® 7. These include:

  • Call of Duty IV no longer displays random corruption when in DirectX® 9 more and the Edge Detect filter is enabled
  • A black screen is no longer occasionally displayed when running Portal 2 in 3D mode
  • All 3d Anti Aliasing settings are now correctly listed in the Vision Control Center
  • Morphological filtering settings are now correctly listed in the Vision Control Center
  • Civilization V no longer experiences random crashes when run in DirectX® 10 and DirectX® 11 modes
  • Enabling the ‘Edge Detect’ filter in Resident Evil 5 or Just Cause 2 no longer generates a random application crash
  • Battlefield 3 no longer hangs when MSAA is enabled
  • Saints Row III no longer experiences random hangs
  • Rage no longer experiences intermittent hangs when Crossfire is enabled
  • Dragon Age 2 textures no longer flicker when run in DirectX® 9 mode in Crossfire configurations with vsync enabled
  • Crysis Warhead and Battlefield Bad Company 2 no longer experience random crashes when Crossfire is enabled
  • Texture flickering is no longer experienced when playing Battlefield Bad Company 2 in DirectX® 11 mode

KNOWN ISSUES

Known issues under the Windows® 7 operating system

The following section provides a summary of open issues that may be experienced under the Windows® 7 operating system in the latest version of AMD Catalyst™. These include:

  • Vsync may be disabled after task switching when playing Rage
  • Skipping in game cinematics while playing Dragon Age 2 in DirectX® 11 mode may cause stuttering
  • Dirt 3 may experience flickering with Crossfire enabled and run in 3D stereo mode
  • Battlefield – Bad Company 2 may experience random flickering when run in DirectX® 11 mode

Known Issues under the Windows® Vista Operating System

The following section provides a summary of open issues that may be experienced under the Windows® Vista operating system in the latest version of AMD Catalyst™. These include:

  • Windows® Aero options may be missing after installing the latest driver

[RESOLVED] – Microsoft Exchange 2010 – Appointments exceeding 24 hours changed to multiple day All Day Event on Mobile Phones/Devices

Microsoft Exchange 2010 Service Pack 1 ActiveSync does seem to have issues with Appointments exceeding 24 hours that are not all day events (i.e. Friday to Sunday).  I have personally seen this issue with the iPhone 4 and 3GS, both were upgraded to IOS5 which did not resolve the issue.  The latest update “Microsoft Exchange 2010 Service Pack 1 – Hotfix Rollup 6” also does not seem to resolve this problem.

You might wish to test if you have the issue with your ActiveSync enabled Smart Phone or Device, you should be able to replicate the issue by asking a collegue to send you a meeting invite that starts on Friday at 4pm and then finishes on Sunday at 2pm, Once you accept the invite you will find that it has been changed to several all day events (Fri, Sat and Sun) rather than an appointment between the specified time period.

After a long wait it appears that this issue is resolved in Rollup 1 for Exchange Server 2010 – Service Pack 2, you can obtain the Rollup using the link below:

http://www.microsoft.com/download/en/details.aspx?id=28809 – Update Rollup 1 for Exchange Server 2010 Service Pack 2 (KB2645995)

You can see the overall list of fixes/changes in Rollup 1 here:

http://support.microsoft.com/?kbid=2645995

The Fix we are most interested in is “A meeting item displays incorrectly as multiple all-day events when you synchronize a mobile device on an Exchange Server 2010 mailbox”

This was original raised in: http://support.microsoft.com/kb/2549255

You will need to ensure that you have updated your Microsoft Exchange 2010 Server to Service Pack 2 before you can install the Rollup so remember to factor extra time in for this.

You can obtain Microsoft Exchange Server 2010 – Service Pack 2 from here: http://www.microsoft.com/download/en/details.aspx?id=28190

Microsoft do seem to be aware of the issue and mention it in this Knowledgebase article

http://support.microsoft.com/kb/2563324 Current issues with Microsoft Exchange ActiveSync and Third Party Devices

Issue 1.6 – Appointment exceeding 24 hours changed to multiple day All Day Event
When an appointment item’s duration exceeds 24 hours, but is not marked as an All Day Event, Exchange ActiveSync changes the item on the device to become a multi-day All Day Event. The next time that the device synchronizes with the mailbox, the change is propagated from the item on the device to the item on the Exchange Server 2010 mailbox.

Solution
Microsoft is investigating this issue. This problem can occur when using any ActiveSync device synchronizing with Exchange Server 2010.

As you can see Microsoft do not currently have a solution to the problem and may well need to contact Apple and/or Google to produce a fix for both the iPhone and Android based handsets.

I would recommend contacting Microsoft Product Support and your mobile phone manufacturer if this issue is affecting you.  The more users that log the issue the higher priority it will be given and the quicker we can expect to see a fix emerge.