Windows longhorn build 3718

Windows Longhorn build 3718 is the last currently available Milestone 3 build of Windows Longhorn, which was shared online on 30 April 2004.^[1] It is very similar to build 3713 in features and functionality, albeit with a more stable Windows Explorer.

NFO file[edit | edit source]

        ██                   
       █▒█                    
    ███▒▓▒███              █      ██  ██ ██
     █▒▓▓▓▒█           ███ █      ██  ██ ███
      █▓▓▓█           ███  ██     ██  ██ █  ██
     █▒██▒█          ██    ██ ██  ██  ██ ██    
    ███  ██          █   █ ████   ██  ██ ███   ██
       ██            ████  ███    ██████ █     ██  █
      █████  █    ██ ██    ██     ██████ ██    █ █ █   ███
    ███▒▒▒█   ██  ██ ██                    ██  █  ██   ███
     █▒▓▓▒█   ███ ██ ██             █       █  █  ██  ██ ██
     █▒▓▓▒█   ██████ ██            ███         █  ██  ██  ██
     ██▒▓▒█   ██ ███ ██           █████            █ ██   ███
      █▒▓▒█   ██  ██             █▒▒▒▒██           █ ██       ███
      █▒▓▒█   ██               ██▒▒▓▓▒▒██            ██      ██ ██
      █▒▓▒█   ██               ██▒▓▓▓▒▒▒██            ██    ██   ██
      █▒▓▒█   ██              ██▒▓▓▓▓▓▒▒▒██            ██ █████   ██
      █▒▒█                   ██▒▒▓▓▓▓▓▓▒▒▒██            █ ██  █
      █▒██                  ██▒▒▓▓▓▓▓▓▓▓▒▒▒██             ██
      ██          ███████████▒▒▓▓▓▓▓▓▓▓▓▓▒▒▒███████████    ██
                  ██▒▒▒▒▒▒▒▒▒▒▒▓▓▓▓▓▓▓▓▓▓▓▒▒▒▒▒▒▒▒▒▒███     ███
                   ███▒▒▒▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▒▒████        █
                     ███▒▒▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▒▒▒████
                       ██▒▒▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▒▒▒███
                        ███▒▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▒▒███
                          ██▒▓▓▓▓▓▓▒▓▓▓▓▓▓▓▒▒██
                          ██▒▓▓▓▓▒▒██▒▓▓▓▓▓██
                         ██▒▓▓▓▓▒▒███▒▒▒▓▓▓▒█
                         █▒▓▓▓▓▒▒▒█  ██▒▒▓▓▒▒█
                        █▒▓▓▓▒▒▒██    ██▒▒▓▓▒▒█
                       █▒▒▓▓▒▒██       ██▒▒▓▓▒██
                      █▒▒▒▒▒███         ███▒▒▒▒▒█
                     ██▒▒▒██              ██▒▒▒▒██
                    ██████                  ██████
			    [2004 -- Are you ready?]
         ---[> Proudly Presents For Your Viewing Pleasure <]---

          
             ┌╔════════════════════════════════════════════════╗┐
             │║ █                                            █ ║│
             │║  █  Windows "Codename: Longhorn" Build 3718 █  ║│
             │║  █         Released: 4/30/2004              █  ║│
             │║ █          Leaker: EmoAddict15               █ ║│
             └╚════════════════════════════════════════════════╝┘
         			CRC Value -- CADF1F2A
				Size -- 535,867,392 bytes
         
                    ┌──────────────────────────────────────┐   
                    │               Overview               │   
                    │ A "new" longhorn build for you guys  │
                    │ to play with.  Better grab the 	   │
                    │ fucking tissues.			   │
                    │ 					   │
                    │ Apparently, DCE doesn't need a dx9   │
                    │ GPU like we all thought.  The menu   │
                    │ to enable DCE effects is in Display  │
                    │ Settings and Advanced.  So go there  │
                    │ enable it, have a fucking blast kids.│
                    │ Fuck, I'm cool.			   │
                    └──────────────────────────────────────┘

                    ╔══════════════════════════════════════╗
                    ║             Directions               ║
                    ║    				   ║
 		    ║	** BE SURE YOUR DATE IS **	   ║
 		    ║	** 11/30/02 !!!!!!!!!!! **	   ║
                    ║					   ║
                    ║  1. Extract                          ║
                    ║  2. Burn the ISO ( It's bootable     ║
                    ║      AND untouched ).		   ║
                    ║  3. Run setup.exe in windows or      ║
                    ║     winnt.exe from DOS (recommend    ║
                    ║     using Smartdrv.exe if doing a DOS║
                    ║     install, unless you're booting   ║
                    ║     from the CD. 			   ║
                    ║  4. Installing using a .NET RC1 key, ║
                    ║     like this one:		   ║
                    ║     TM44C-92G7F-29924-2J8VH-RPCKB    ║
                    ║  					   ║
                    ║  >> .NET RC1 Key Database coming	   ║
                    ║     soon <<			   ║
                    ╚══════════════════════════════════════╝

                    ╔══════════════════════════════════════╗
                    ║        ..Visit iNFLUENCE..           ║
                    ║  This year, we're innocent, I promise║
                    ║   				   ║
                    ║  IRC: irc.lifeclot.net		   ║
                    ║  Channel: #Toastednet                ║
                    ║  Channel: #BetaOS			   ║
                    ║      				   ║
                    ║  Setup a BOT and share 3718!         ║
                    ╚══════════════════════════════════════╝


                    ╔══════════════════════════════════════╗
                    ║           ..Greetings..              ║
                    ║  NightDarker  -- My Nigga		   ║
                    ║  `Night   -- Best M$ Whistler Cracks ║
                    ║  meelWORM -- #eXPerience ;)	   ║
                    ║  ^^Matt^^ -- I wouldn't be here.     ║
                    ║  Bullz    -- iNFL wouldn't exist...  ║
                    ║  Citra    -- Best M$ Cracker	   ║
                    ║  Reflectiax -- Sorry I leaked this,  ║
                    ║                but you quit the scene║
                    ║                :(	 		   ║
                    ║  Cpu Killer			   ║
                    ║  Mandy Cat -- :-*			   ║
                    ║  Katy -- You're famous now, kid.	   ║
                    ║					   ║
                    ╚══════════════════════════════════════╝




DeC -- Fuck you, asshole.  You're the whole reason this got leaked. That and my stupidity.
BOFH -- Fuck you too.  You're a fucking retard and disgrace to the scene.

New features and changes[edit | edit source]

[edit | edit source]

The Sidebar is now transparent by default, however, the option to disable the transparency was removed.

Media Center[edit | edit source]

Media Center is now referred to as «Media Center» in the Add or Remove Programs applet, replacing the previous «Freestyle» mention.

Bugs and quirks[edit | edit source]

General[edit | edit source]

• The «Low Risk» and «High Risk» text overlaps in the Windows Trust Manager.

• The new taskbar cannot be right clicked.
• DiskPart does not function and will tell the user that This version of diskpart is not supported on this platform.

• The sidebar will fail to render properly when adjusting the resolution.

Media Center[edit | edit source]

It is not possible to install the Windows Media Center, as the required components are not present on the installation media.

Control Panel[edit | edit source]

• Due to the addition of the WinFS task pane, the user cannot view system drives or folders like System32. Alongside this, the option to switch the Control Panel to Classic View is no longer accessible, making most Control Panel applets completely unaccessible.
  • Deleting the WebView key in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer will revert the task pane to its Windows XP counterpart, allowing the user to switch the Control Panel to Classic View.
• Display Properties mentions the Luna theme as the Plex theme.

MyTVApp[edit | edit source]

MyTVApp can no longer be opened, due to a crash in AvalonBrowserInteropProxy.exe.

Desktop Compositing Engine[edit | edit source]

The Desktop Composition Engine only renders the user interface on the hardware layer, while the software layer is rendered as a black screen or leftover data. As a result, attempting to use software capturing methods (such as Print Screen) will not result in a proper capture of the screen. Most hypervisors only render the software layer, usually resulting in a black screen upon starting DCE.

File differences[edit | edit source]

Gallery[edit | edit source]

Setup[edit | edit source]

• Introduction

• User information

• Product key entry

• Computer name and credentials

Interface[edit | edit source]

• Logging in

• First boot

• Avalon error upon opening MyTVApp

• Minimizing effect for DCE

• Closing effect for DCE

• Olive Green Luna theme

• Silver Luna theme

• Safe to shutdown screen

References[edit | edit source]

Windows Longhorn was the pre-release codename for Windows Vista and was the successor to Windows XP and Windows Server 2003 (built from NT 5.2 codebase). Development on the OS started in May 2001 and went through two unique development cycles separated by a development reset in 2004. The reset occurred as Microsoft’s development staff had lost focus on the project as a whole and what was required to be done in order to bring it to market. Features were being written into the OS at an alarming rate with a significant lack of QA or vision of true requirement. This combined with Microsoft’s trustworthy computing initiatives caused the reset.

Several features of Longhorn planned that were actually shipped include the glass replicating Aero theme (which followed the Slate and Jade themes from earlier builds), along with the Windows Sidebar — although this was shipped as a standalone utility where as most builds (at least in pre-reset) shipped this as part of explorer.exe. Numerous improvements to the Windows Explorer, along with an updated Internet Explorer 7, Windows Media Player 11, instant search, new 3-d games and other items made it into the final version of Windows Vista.

A few screenshots and a video have been doing the rounds across the net recently, indicating the leak of a build that is about two years old. What is so special about this release? This build carries the DCE, or Desktop Composition Engine, it is the DirectX, video-accelerated graphics engine in Longhorn. It will be a part of the Aero User Interface. Longhorn is the name given to the currently in development next version of Windows by Microsoft. It is expected to debut sometime between 2006 and 2007. Click the link below to see more.

In some respects this is old news, but seeing as a few other tech sites are also giving these screenshots some more exposure, I thought we might as well too.

Source: FlexBeta

Anonymous

Actually, just to correct a point that Raptor has just made, the current MacOS X UI is built chiefly on resolution-dependent bitmaps (e.g. all the buttons etc.), not resolution-independent (i.e. vector) imagery.

I don’t beleive ever claiming anything about the UI (eg. buttons being vector based). Quartz is capable of both vector based and bitmaped support. Just because the UI is implemented today (or in pre 1999) doesn’t mean that it is incapable of using vectors.

The point I made above directly supports why the UI elements would be bitmap based. Vector images for UI make no sense unless you are drawing the elements using the GPU, it is infact slower if you use vector images becuase you have to do a two step conversion. As I illustrated full hardware accelration would require gobs of video memory, which was not avaiable in 199x when Aqua was developed or in 2001 for Quartz Extreme. Todays Displays do not require vector images, bitmaps serve fine. Avalon is based on the assumption that at the time of release, there will be very high resolution displays and cheap 3D graphics cards with atleast 64MB RAM or 128MB for better performance (with microsoft’s recommendations track record I would say 256MB)

Aqua looks just as stunning on a 800×600 12″ display or a 23″ display at 1920×1200. I haven’t tried it on any other displays. But for todays Apple systems bitmaps are fine and perfrom well.

3c. (vector level) retention automatically fast(er)

Once you are not drawing retained vectors with the GPU, there is no particular reason why it should be faster than immediate mode drawing, and experience with DPS, for example, showed that it almost never was.

The reason for this is that you are doing extra work: building up the retained graphics representation from the application-level representation, and then drawing that. Drawing directly from the application-level representation eliminates one step. -mweiher http://www.ondotnet.com/pub/a/dotnet/2004/03/08/winfs_detail_3.html…

My point was the architecture is already in place, becuase Raynier claimed it would need a whole scale redesign. Also people claiming the Apples UI being bitmap based is a “bad thing”. It is a set of implementation compromises given the state of hardware at the time desgin and release. But the fact that the architecture is in place is a testament to the Quartz design team. When the hardware catches up Quartz will implement full vector based rendering. The hardware is already catching up in 2004 (powerbooks with 128MB cards).

1. High DPI displays

Quartz will be quite capable of adapting to high DPI displays, just not using the mechanism you envisage. In fact, Quartz uses the PDF/Postscript imaging model, which as you may recall, is device independent and theoretically arbitrarily scalable, and practically scales at least to imagesetter and film-printers, with around 2500 dpi, and has done so for a couple of decades.

The mechanism is quite simple and has been in uses for several decades: apply a device-transform with a higher scale factor before any other rendering is done. Voilá, you get a bitmap rendered at a higher resolution.

Your proposed mechanism of applying a compositing transform to the completed Window is unlikely to work well even in the Windows world, because it assumes that *all* drawing by *all* applications will use the retained vector API. This assumption seems unlikely unless non-retained APIs are removed, and completely hopeless once you consider legacy applications. -mweiher

You really must reag the rest of the discussion from which I pasted these sections.