Desktop Composition Engine: Difference between revisions

From BetaArchive Wiki
(Created page with 'In early builds of Longhorn, Desktop Composition Engine was used as an eye-candy tool which "twirled" and "twisted" windows when closing or minimizing them in early Longhorn buil…')
 
No edit summary
Line 1: Line 1:
In early builds of Longhorn, Desktop Composition Engine was used as an eye-candy tool which "twirled" and "twisted" windows when closing or minimizing them in early Longhorn builds up to 402x. It works in builds:
In early builds of Longhorn, Desktop Composition Engine was used as an eye-candy tool which "twirled" and "twisted" windows when closing or minimizing them in early Longhorn builds up to 402x that ran using RUNDLL32.EXE. It works in builds:


*3683
*3683
Line 9: Line 9:


The most famous version of DCE is in builds 4015 lab_06N and 4018 lab_06N. The windows slid when moving and there were red boxes in the background. Only very few people have this build because it is securly held in Redmond.
The most famous version of DCE is in builds 4015 lab_06N and 4018 lab_06N. The windows slid when moving and there were red boxes in the background. Only very few people have this build because it is securly held in Redmond.
After the reset, it became known as [[Desktop Window Manager|Desktop Window Manager]] and was not run using RUNDLL32.EXE. It was run as its own application called DWM.EXE if you had compatable hardware.

Revision as of 18:04, 25 June 2011

In early builds of Longhorn, Desktop Composition Engine was used as an eye-candy tool which "twirled" and "twisted" windows when closing or minimizing them in early Longhorn builds up to 402x that ran using RUNDLL32.EXE. It works in builds:

  • 3683
  • 3706
  • 3713
  • 3718

It is mostly 100% broken in 4008, 4011, and 4015 winmain.

The most famous version of DCE is in builds 4015 lab_06N and 4018 lab_06N. The windows slid when moving and there were red boxes in the background. Only very few people have this build because it is securly held in Redmond.

After the reset, it became known as Desktop Window Manager and was not run using RUNDLL32.EXE. It was run as its own application called DWM.EXE if you had compatable hardware.