Database Users

Windows Mobile 6 Kernel Open Source (also drivers)

I am writing from my pocket pc:
http://www.windowsfordevices.com/news/NS2632317407.html
"Microsoft officially launched the sixth generation of its flagship device software "platform, today. "Windows Embedded CE 6.0" boasts kernel architecture enhancements, new software stacks targeting three high-volume device categories, enhanced development tools, and, for the first time, 100 percent availability of Windows CE's kernel source code. "
Doesn't this mean we can port to any device?

This is for links:
http://msdn.microsoft.com/embedded/community/community/communityprojects/
http://www.codeplex.com/
---
Develop now, pay later
A free 180-day evaluation version of Windows Embedded CE 6.0 is available for download, here. The kit includes the operating system, the standard shared source components described above, and Visual Studio 2005 Professional.
http://www.windowsembeddedkit.com/

sorry to burst your bubble, but CE6.0 is NOT WM6
WM6 is BASED on CE5.2
WM7 will be BASED on CE6.0
Neither will be creatable/editable using the CE shared source as windowsmobile is not shared source.

True hehe
forgot Windows Mobile 6.0 is based on CE 5.2
Was a quick read and post on my pocket pc
Apologies

Might still be useful,
If we can get Windows CE 6.0 to run on a device...
It may be possible to get Windows Mobile 6 to run using a CE 6 core?
Windows CE 6 should be backward compatible with Windows CE 5.2 (although new drivers will probably be needed)
Long shot, but just might work...
(isn't Windows Mobile just a pretty shell for Windows CE?)
Problems:
*Probably against the Microsoft license. (Donations? Maybe can even buy Windows CE 5.2 Tool Suite)
*Windows CE 6 Core needed for Windows Mobile might be significantly bigger than Windows CE 5.2 Core.
*Need to know everything Windows Mobile uses in Windows CE to build a working core.
*Device Drivers may have to be rewritten depending on how much Windows CE 6 differs form Windows CE 5.2 (Will be easier with source code)
*Getting it to work will require quite a bit of development and research

basically, it's not impossible, just highly unlikely.

hehe any volunteers
I know its crazy, but there are huge benefits in getting this to work.
(Far less limitations in what we can do)
I would investigate myself but it looks like I am about to be computerless for the next 4 weeks!

OK, I hate to burst your bubble even further, but I don't think it will be possible at all.
Why?
1) They are only publishing the Kernel, and there is a lot more to the OS than that.
2) Because of the different kernel architecture the drivers will defiantly need to be rewritten and for that they will have to be reverse engineered first. Just look a the state of various Linux projects to see how long and hard something like that would be.
3) M$ is notorious for making OSs that are not forward compatible - namely although the difference between WM 6 and 5 is almost non existent compiling a simple "Hello word" app with WM 6 SDK will prevent it from running on a WM 5 device (bad exe error).
Also, the fact that they are "releasing" the code does not make it open source. It will still require a ton of paper work to get and you will probably have to be a real company or at least an academic establishment to get it.
M$ already gives out a lot of code for previous embedded OSs under special license.
So by the time someone leaks the code, figures out a way to patch together new kernel and additional required components from previous OS, plus reverse engineers and rewrite drivers for a given device not only that device will become obsolete but the whole CE line.
My guess is, a few years from now phone size devices will be powerful enough to run a normal OS like UMPCs do today.

levenum said:
1) They are only publishing the Kernel, and there is a lot more to the OS than that.
Click to expand...
Click to collapse
I don't want to compile the whole of Windows Mobile 6, just the parts that don't allow it to be run on older devices (or newer) e.g. nk.exe
(I haven't downloaded the kit yet so I don't know if this is possible or not, could be, could not be)
levenum said:
2) Because of the different kernel architecture the drivers will defiantly need to be rewritten and for that they will have to be reverse engineered first. Just look a the state of various Linux projects to see how long and hard something like that would be.
Click to expand...
Click to collapse
Many Windows CE 4 (Windows Mobile 2003 SE) drivers are used on a Windows CE 5.2 (Windows Mobile 5) platform. So there is a slight chance they may work in Windows CE 6.
levenum said:
3) M$ is notorious for making OSs that are not forward compatible - namely although the difference between WM 6 and 5 is almost non existent compiling a simple "Hello word" app with WM 6 SDK will prevent it from running on a WM 5 device (bad exe error).
Click to expand...
Click to collapse
An application written in a new operating system will not work in the old operating system.
but an application written in the old operating system usually works in the new operating system.
Otherwise microsoft would have many very unhappy customers.
Windows Mobile (non core parts) are basically old applications...
levenum said:
Also, the fact that they are "releasing" the code does not make it open source. It will still require a ton of paper work to get and you will probably have to be a real company or at least an academic establishment to get it.
M$ already gives out a lot of code for previous embedded OSs under special license.
Click to expand...
Click to collapse
You can already download it
http://www.windowsembeddedkit.com/
levenum said:
So by the time someone leaks the code, figures out a way to patch together new kernel and additional required components from previous OS, plus reverse engineers and rewrite drivers for a given device not only that device will become obsolete but the whole CE line.
My guess is, a few years from now phone size devices will be powerful enough to run a normal OS like UMPCs do today.
Click to expand...
Click to collapse
This thing runs WINDOWS VISTA
http://www.htc.com/product/03-product_HTC_Shift.htm
Heres another one, running windows XP
http://www.sonystyle.com/is-bin/INT...AIONotebookComputers_UX_Series&Dept=computers
We will not know the true amount of work needed until someone tries.
And if it is not a lot of work it will make a few people quite happy.

Well...
Me, i can not see the point in a project like this... Why would you even want to re-do microsofts sh--t.
Use the manpower and resources for the UNI Linux project.. They are allmost done... Just a few glitches now...
I wanna get away from MS asap... but i like this HW...

allNEW FEATURED SDK FOR DEVs

Airplay SDK is unique in providing the
facility to build your application as an
entirely OS-agnostic binary file that contains
native CPU instructions. So no compromise
on performance, yet no need to port your
application between operating systems.
Airplay SDK supports single-click
deployment to all of the following operating
systems: * iPhone OS * Android * Samsung
Bada * Symbian * Windows Mobile * BREW
* Palm/HP webOS * Maemo Additionally,
Ideaworks Labs is working closely with
leading device manufacturers to open up
new distribution opportunities for Airplay
content. Airplay SDK fixes fragmentation
within each operating system by removing
the need for developers to worry about
individual device eccentricities. Here are just
five examples of the hundreds of per-device
problems that Airplay SDK solves: *
Dynamic portrait/landscape screen
switching handled identically for all devices
* Accelerometer API implemented
identically for all devices (despite the large
number of bespoke device drivers and APIs
in the market) * Device-application
interoperability handled identically for all
devices (i.e. your application is guaranteed
to 'play nicely' with the device software, for
example to respond to incoming phone calls
and messages) * Audio handled identically
for all devices (for example, by providing
advanced software sound mixing) * Single
drawing API supports OpenGL ES 1.x,
OpenGL ES 2.0 and super-fast software
rendering, allowing your app to run with or
without any form of hardware graphics
acceleration FEATURES: Save development
time by writing your Airplay app using
vanilla C++ in the IDE of your choice. Airplay
currently supports all versions of Visual C++

[Q] Windows 8 on ARM

As this is a developers forum - lets share here information on WoA (Windows on ARM) architecture.
What is known for now from different sources:
- WoA 8 would require UEFI to boot (instead of BIOS on x86), ACPI is required too. So no WoA to existing devices (they don't have UEFI/ACPI and I don't think that anyone would waste his time on emulating them).
- No native support for x86 apps on ARM, nor ARM apps on x86. Only .NET apps would work in both worlds.
But it is possible to create an emulator similar to DosBox that would run native x86 programs on WoA and, for example, I'm currently working in this direction.
- Though existing C++ apps can be recompiled for ARM from sources, it is not a 100% working solution. Current VS11 contains a rather limited set of ARM libraries - no DirectX libs earlier than 11, no import libraries for NtDll.Dll and similar DLLs.
I don't have access to any WoA builds, so I can't check whether these features are completely removed from ARM, or those LIBs are just not present in current VS11 build. But at least now we can compile test apps for ARM and analyze the code (though we don't have where to execute them yet).
- Native WoA programs use THUMB2 instruction set (ARMv7 and above). Though ARM instruction set would be supported too.
- According to "Microsoft Portable Executable and Common Object File Format Specification v8.2" WoA machine type in PE files would be 0x1c4, and some new relocations types are added (for example IMAGE_REL_BASED_ARM_MOV32T = 7). IDA understands such EXE files, though complains on relocs.
- SEH is implemented in a different way than on x86 (similar to x64, google for RtlAddFunctionTable to get the idea).
- WoA is more secure by default. For example TPM can be rarely found on x86, but it would be required on ARM.
- Most of existing drivers are source-code compatible with ARM (of cause if not using x86-specific stuff). But ARM would never allow to load unsigned drivers (unlike x86 Win7/8).
- As platform is completely new - all ARM drivers would be added to windows update site to simplify our life. Some obsolete hardware like 1394 is not implemented at all, so there would not be so many drivers for ARM llike for x86.
- All binaries would be the same for all SoC providers.
- No "native" ARM VisualStudio - developer tools are x86 only.
WoA requirements from different sources:
- 10.1” display with 1366x768 min resolution (though smaller screens may be supported with reduced functionality)
- Volume Control, Windows, Rotation, Lock power buttons
- Dual core CPU with hardware accelerated GPU
- at least 1 Gb RAM
- min 16 Gb fixed storage
- 100mW idle power in standby
- there are rumors that there would be standart "Phone call API" ("Apollo" UI)
Does anyone have access to ARM WDK? It would definitely contain a complete set of import libraries and would provide lots of info on WoA internals in headers/documentation. Seems that Windows 8 WDK on MSDN does not have ARM tools

so your bottom line says: no w8 on arm (ever)?

I'm not quite sure where you found that it requires ACPI. I didn't turn anything up.
The UEFI requirement is expected, and I doubt will be that much of a hurdle. UEFI is all open, and it should be pretty trivial to chainload a UEFI-compatible environment on top of the existing firmwares, provided that nvidia doesn't provide us with an implementation to start with, which I suspect they'll do.
For the emulator, I believe the best thing to do would be to provide something opposite of WINE, something that'd emulate the instructions, but pass API calls and translate between the two. A full Windows SDK will likely come out for ARM processors once it's finalized, if it's not already out. Have you checked in the Ultimate build of VS2011, or the express build?
Everything I could find relating to the TPM says that it's optional, but will be automatically utilized if available.
The rest is pretty inconsequental, at least to what I think most people here are interested in.
nvidia started a windows 8 development program for ARM (Clickey here), but I haven't seen anything else from it, has anyone else gotten anything?

mamaich said:
As this is a developers forum - lets share here information on WoA (Windows on ARM) architecture.
What is known for now from different sources:
- WoA 8 would require UEFI to boot (instead of BIOS on x86), ACPI is required too. So no WoA to existing devices (they don't have UEFI/ACPI and I don't think that anyone would waste his time on emulating them).
Click to expand...
Click to collapse
Actually they said it would continue to support BIOS for older devices.
See: Current machines dual-booting Windows 7 and Linux should be able to upgrade to Windows 8 without wiping out the Linux install. As Microsoft notes in the Building Windows 8 blog, “We will continue to support the legacy BIOS interface.” However, machines using UEFI instead of BIOS “will have significantly richer capabilities” including faster boot times and greater security. (from Arstechnica)

That's for x86. ARM was said to require UEFI. Besides, there is no real bios on Android tablets, at least not a common platform.

netham45 said:
I'm not quite sure where you found that it requires ACPI. I didn't turn anything up.
Click to expand...
Click to collapse
I've got it in one of the "windows-on-arm" non-public documents dated the first half of this year. While UEFI,ACPI,TPM are an option for x86, they are required for ARM hosts.
So no custom WM8 bootloaders, drivers, patched kernel on ARM hosts (like "windows activators" do) until sign keys would be leaked or some backdoors would be found. Of cause this is good as this would make rootkit creation more difficult, and require device drivers signed by MS (so we'd get more stable OS) but I really don't think that this "protection" would last more than 1-2 months after WoA would be released.
For the emulator, I believe the best thing to do would be to provide something opposite of WINE, something that'd emulate the instructions, but pass API calls and translate between the two.
Click to expand...
Click to collapse
I'm already working on such tool. It emulates x86 instruction set with dosbox or bochs CPU emulation library (I'm using both of them for debugging purposes, while working on my own one that would be much more simple->faster), translates x86 WinAPI to "native" host WinAPI + emulates API that is not present or differently implemented on WoA. It is designed to be truly cross-platform, so just a recompilation + creating several thunks/stubs would be necessary when I'll get my hands to an ARM host running windows8.
Of cause programs that use heavy anti-debugging, self-modifying code, undocumented features and SEH tricks would not work. Currently it is rather far from being finished (I have to implement&debug WinAPI and COM thunks that cannot be automatically generated) but old games like "heroes of might and magic" are already working fine in a test environment.
A full Windows SDK will likely come out for ARM processors once it's finalized, if it's not already out. Have you checked in the Ultimate build of VS2011, or the express build?
Click to expand...
Click to collapse
Of cause I'm talking about "ultimate" VS11, as express is designed to target mostly .NET (though ARM compiler is present there too).
And WDK that it published on MSDN does not allow creation of ARM drivers. I'm currently in a process of renewing my company's MSDN subscription, so I can't prove that myself, but I've read that on OSR forums.

I am waiting to hack my iPad and put win8 on it

I would hope touchpad would be the next viable option. Hp could still make more and just dump W8 on it. Thanks all of you for working this thread. I will be reading your progress as it unfolds. Good Luck devs and if I can find anything you will be the first to know.
Sent from my mwp6985 / Trophy using XDA Windows Phone 7 App

Some information on Win8 "Apollo" is available. Apollo - is a name for a new "windows phone" OS from MS.
- Apollo is based on the same "desktop" code as Windows 8. No Windows CE at last!
- Apollo would provide the same user experience as old Windows Phone 7.x - Metro UI, People hub, builtin office apps, etc. Seems that software compatibility with WinPhone 7.x apps would be preserved, but this is just my own guess.
- All applications on Apollo are required to be signed, similar to Windows Phone 7.
- Device drivers can be written only by IHVs, MS and OEMs, not by ISVs. This would be a problem for antivirus vendors or tools like daemon-tools.
- There would be a "built-in" eMMC card with OS and vendor partitions, and maximum one SD card. eMMC supports NTFS, SD-card supports only FAT/exFAT.
Build-in eMMC would have C:\ drive letter, SD-card would be D:\ if present.
eMMC contains several partitions. Some of them would be made readonly during boot.
- Near Field Communication is built in.
- The same list of sensors as in WP7 Mango is supported.
- There would be BSOD like in a desktop OS
- Unproven, but it seems that only .NET ("Splash UI framework" and "Silverlight") APIs would be available to independent developers. So no native code again.
- Seems that x86 architecture is supported for Apollo too.

Windows Phone SDK 8.0 Download

The Windows Phone Software Development Kit (SDK) 8.0 provides you with the tools that you need to develop apps and games for Windows Phone 8 and Windows Phone 7.5.
Overview
The Windows Phone SDK 8.0 is a full-featured development environment to use for building apps and games for Windows Phone 8.0 and Windows Phone 7.5. The Windows Phone SDK provides a stand-alone Visual Studio Express 2012 edition for Windows Phone or works as an add-in to Visual Studio 2012 Professional, Premium or Ultimate editions. With the SDK, you can use your existing programming skills and code to build managed or native code apps. In addition, the SDK includes multiple emulators and additional tools for profiling and testing your Windows Phone app under real-world conditions.
System requirements
Supported operating systems: Windows 8, Windows 8 Pro
Windows 8 64-bit (x64) client versions
Hardware:
4 GB of free hard disk space
4 GB RAM
64-bit (x64) CPU
Windows Phone 8 Emulator:
Windows 8 Pro edition or greater
Requires a processor that supports Second Level Address Translation (SLAT)
If your computer meets the hardware and operating system requirements, but does meet the requirements for the Windows Phone 8 Emulator, the Windows Phone SDK 8.0 will install and run. However, the Windows Phone 8 Emulator will not function and you will not be able to deploy or test apps on the Windows Phone 8 Emulator.
Instructions
Choose the language version you want to install and click the Download button for the WPexpress_full.exe file. Follow the instructions to install the SDK. Note that each localized version of Windows Phone SDK 8.0 is designed to function with the corresponding localized operating system and localized version of Visual Studio 2012.
Note - Windows Phone SDK 8.0 installs side-by-side with previous versions of the Windows Phone SDK. You don't need to uninstall previous versions before beginning this installation.
Download the release notes which are in a separate file. For Windows Phone SDK 8.0 documentation and samples, see the Windows Phone Dev Center.
To start VS Express for Windows Phone, click the application in the Apps list. If you have Visual Studio Professional, Premium or Ultimate installed on the computer, the VS Express for Windows Phone shortcut won't appear. Instead, start your Visual Studio instance as usual and then create Windows Phone SDK 8.0 projects using the installed Windows Phone templates.
If you try to run a project in Windows Phone Emulator and Hyper-V is not enabled, you will be prompted to turn on Hyper-V. Turning on Hyper-V requires you to restart your computer.
Note: this release is also available in .iso format. Choose one of the following options for handling downloaded ISO images:
(Recommended) Write the image file to a blank DVD.
(Alternative) Mount the image file virtually as DVD devices.
Download WebSite: http://www.microsoft.com/en-us/download/details.aspx?id=35471

So how do you learn how to use an SDK? I've always had an interest but there is never any obvious guide of how to program. I picked up UE3 SDK quickly but that is because there was like 30GB of tutorials on it, where can I do the same for this SDK?
Thanx.

You learn visual C#/B/C++. You do not directly use the SDK, you use the development tools in it

Venekor said:
So how do you learn how to use an SDK? I've always had an interest but there is never any obvious guide of how to program. I picked up UE3 SDK quickly but that is because there was like 30GB of tutorials on it, where can I do the same for this SDK?
Thanx.
Click to expand...
Click to collapse
First learn Silverlight/C# and then read the SDK documentation,
To put it in simple words SDK just gives all the functions that u can use on Windows Phone.

Typically, if you learn any C# API (other than windows forms) you will learn all the others. They are very similar to each other, only some few twinks here and there due to platform differences.
---------- Post added at 11:46 PM ---------- Previous post was at 11:28 PM ----------
The SDk is bugged, emulator does not work. Says it wants virtualization and my PC doesn't have it, when it clearly does. Both Android and Windows Phone 7.5 emulators work fine.
Kinda failish...from Microsoft.
oh well...the SDK system requirements are pretty damned huge. My CPU does not support SLAT apparently...

So I can just go to the Visual Studio website and follow the tutorials there? I have bad eye sight so I learn better from videos and listening instead of reading lots of text which takes me far longer to do. Luckily typing is easier as you know what you're typing on the keyboard so you don't have to pay as much attention on reading the text on screen.

Your processor needs SLAT support (extended Virtualization) also called VT-x by Intel. It is available from the Core i3/i5/i7 processors or newer AMD processors. This is due to the fact that the WP8 Emulator relies on Hyper-V instead of VirtualPC which was used for WP7. So if you have a Core 2 processor your hardware does lack required features. This is not a bug in the SDK.
On learning development of WP Apps there are series that take you around the SDK like this one: http://www.jeffblankenburg.com/2010/09/30/31-days-of-windows-phone-7/ It's still for WP7 but almost everything said there still applies for WP8, although in WP8 it was much extended. There are also Development Webcasts and Hands-On Labs you can try out. You can Google for those - there is lots of content on the topic.
But as was said before - it would be beneficial to know some C# beforehand.

I keep installing the SDK but visual studio express 2012 for windows phone doesnt appear in my start menu, says everything is installed fine, Any ideas?
Edit:btw using windows 8 x64 Evaluation Version

Do you have a regular version of Visual Studio 2012 installed? In that case the SDK integrates itself with the regular version and just adds the project type there.

StevieBallz said:
Do you have a regular version of Visual Studio 2012 installed? In that case the SDK integrates itself with the regular version and just adds the project type there.
Click to expand...
Click to collapse
That will be the one,, Cheers for reply.

Since no college near me teaches any programming and I have to work, I better start teaching myself.
Can any one tell me where to start?
Thanx.

Venekor said:
Since no college near me teaches any programming and I have to work, I better start teaching myself.
Can any one tell me where to start?
Thanx.
Click to expand...
Click to collapse
https://dev.windowsphone.com/en-us
http://www.windowsphonegeek.com/Resources
http://www.freebookspot.es/Comments.aspx?Element_ID=259285 (book)

Does WP8 have any new ringtones/notifications or wallpapers?
I dunno if that stuff would be in the SDK, but it'd be cool to have a dump of those files.

Weird Visual Studio basically does everything for you, I was expecting you'd have to make everything from scratch. Not what I wish'd for really as I did want that experience, those guides don't teach you how to understand the language, just how to create something quickly. Kinda like when you were at school reading from a text book and they never taught you the foundations of how to create your own sentences, always taught pre existing ones.

You can look for manuals for Visual C# around the web, there are a couple of free ones created by Microsoft, but you won't find any videos.
Once you understand the basics, it will be pretty easy to get started on creating complex apps. This is the beauty of C#

can anyone give me MD5 or SHA-1 hash of the iso? thx.

If you want to learn programming from the ground up I guess it would be best to start with a regular book on programming with Visual C# 2010 or something along those lines (2012 books are still rare I guess).
The problem with starting out on Smartphone platforms is simply that there is nothing like Console programs that allow you to easily experiment with language features without having to care a lot about more complex concepts like asynchronicity, Event-models, data-binding, etc.
While I can do a simple:
public static void main(String[] args) {
Console.WriteLine("Hello World!");
}
on the Desktop to arrive at a program that outputs those famous words to the screen on the phone it is more like with a PCs GUI programming.
There you have to instantiate a Window (or Page on the Phone), place a Label control (both of which are classes) and assign a property of the label to the text. Algorithmically a lot of information is hidden in those classes. This is mainly due to the fact that during actual development people don't want to and don't need to care about the details behind those things but for learning how to do things the effect is pretty devastating.
So my suggestion would be: Take a book on C# development and work through the basic concepts of Methods, Classes, Properties, EventHandlers and then before diving into the details of WinForms development switch over to the Phone SDK and acquaint yourself with the workings of the according UI Toolkit.

how can i tell if my computer has a processor that supports Second Level Address Translation (SLAT)
my laptp is intell pentum and my desktop is amd phantom x4?

Your laptop won;t support it.
I am not entirely sure about the AMD though.
There is a tool for that in the SDK download page.

[DOWNLOAD] Windows 10 Technical Preview for Enterprise

Windows 10 Technical Preview for Enterprise:
FAQ for IT professionals
Get answers to common questions around compatibility, installation, and support.
Windows 10 Technical Preview for Enterprise is a very early look at what’s ahead for Windows. After you install Technical Preview, you'll automatically receive updated preview builds as we move through the development process. These early releases are an opportunity for you—as an IT professional—to download and test these builds in your environments, and provide feedback that will help us improve the final product.
Jump to: Download and requirements | Windows Insider Program | Administration and deployment | User experience | Help and support
Download and requirements
Where can I download Windows 10 Technical Preview for Enterprise?
You can download 32-bit and 64-bit versions of Windows 10 Technical Preview for Enterprise from the TechNet Evaluation Center. The preview is available in English, Portuguese (Brazil), and Chinese (Simplified). If you want to try Technical Preview for personal use, visit Windows.com.
note iconImportant: Windows Update will be set to automatically install important updates as they become available. You won’t be able to turn off automatic updates in Technical Preview, but you will be able to choose between a fast or slow update cadence. To change when preview builds are installed, open PC settings, click Upgrade and recovery, click Preview builds, and then click Change the time my PC installs preview builds..
What are the system requirements?
For details, see Windows 10 Technical Preview for Enterprise system requirements.
What are the hardware requirements?
Windows 10 Technical Preview for Enterprise will work with most of the same devices and programs as Windows 8.1. In some cases, a device or program will require an update, or you may need to uninstall some programs and then reinstall them after installing the preview. Here are some things to consider:
For 64-bit installations, a small number of older PCs may be blocked from installation because they don't support CMPXCHG16b, PrefetchW, and LAHF/SAHF.
To use touch, you need a tablet or monitor that supports multitouch.
Technical Preview is not supported on devices running Windows RT or Windows Phone.
When does the preview expire?
April 15, 2015. If you’re running Windows 10 Technical Preview for Enterprise, we’ll start to send you notifications on April 1, 2015 to remind you that it’s time to upgrade your machine to a newer version.
Back to top
Windows Insider Program
What is the Windows Insider Program?
This program enables you to find out what updates are included in each preview build, and provide feedback directly to the teams building Windows using a special feedback app. After you download Windows 10 Technical Preview for Enterprise, you should join the Windows Insider Program.
Back to top
Administration and deployment
Where are the administrator tools?
You can get to the administrative tools by pressing Windows key + X. You’ll see familiar tools such as Programs and Features, Mobility Center, Power Options, Event Viewer, Device Manager, and Computer Management.
Are there any deployment tools available to support the preview?
Because Windows 10 Technical Preview for Enterprise is an early build, we don’t yet support deployment tools such as the Microsoft Deployment Toolkit and the Windows Assessment and Deployment Kit (Windows ADK). We suggest that you install the preview directly on a PC in your test environment so you can explore the familiar UI and test your line-of-business apps.
What is involved in migrating from earlier versions of Windows to the Windows 10 Technical Preview for Enterprise?
You can migrate volume licensed computers, managed using System Center Configuration Manager software distribution or Group Policy, to Technical Preview using the in-place upgrade process. For more information, see Try it out: Windows 10 Technical Preview for Enterprise. Here are some things to consider:
If you're running Windows 8.1, Windows 8, or Windows 7 and your system language isn't English, Chinese (Simplified), or Portuguese (Brazil), you can only keep your personal files when you upgrade. You won't be able to keep your apps or Windows settings.
If you're running Windows 8.1, Windows 8, or Windows 7 and have installed a language pack or a language interface pack (LIP), they'll be removed when you install Technical Preview.
Back to top
User experience
What should I look for?
In Technical Preview, you’ll find lots of updates to features that your users will enjoy. You’ll find easier ways to get and use apps, find and manage files, and personalize and change settings. Users can choose either the Start menu or the Start screen. For organizations running Windows 7, the Start menu will be familiar and welcoming. You don’t have to worry about retraining your staff to learn new ways of working with Windows. For more information, see How to use Windows 10 Technical Preview.
Will I have to learn new ways to perform familiar tasks?
You will perform most familiar tasks in Technical Preview the same way you did in previous versions of Windows. Many of the same keyboard shortcuts work in Technical Preview (for example, Windows key + E and Windows key + R). You copy files, manage tasks, and administer the computer with the same tools.
What other features or product changes can I expect?
For more information about what features and other product changes are in store for Windows 10, see Introducing Windows 10 for Business.
Back to top
Help and support
Where can I find support for Technical Preview?
For technical questions, go to the Windows 10 Technical Preview for Enterprise IT pro forums. You’ll find one forum for general questions, another for deployment questions, and a third forum for submitting feedback. We’ll gather information from the feedback forum and share that with our engineering teams, but we won’t necessarily respond to items on the feedback forum like we do with other forums.
http://www.microsoft.com/en-us/evalcenter/evaluate-windows-technical-preview-for-enterprise
Sent From Windows 7 On HTC Droid DNA

The next version of Windows is engineered for the way you live and work, protected against cyber risks and threats, and managed for continuous innovation.
Need more information? See*what's new in Windows 10 Technical Preview for Enterprise.*
*
Languages
English (United States), English (Great Britain), Chinese (Simplified), Portuguese (Brazil)
*
Editions
Windows 10 Technical Preview for Enterprise 64-bit ISO
Windows 10 Technical Preview for Enterprise 32-bit ISO
Preinstall Information
Note: This is an early preview. Carefully read the information below before you continue with the download.
Review Windows 10 Technical Preview for Enterprise system requirementsRegister, then download and install full-featured software. Trial expires April 15, 2015Receive email with resources to guide you through your preview
Installation Guidelines
Plan ahead. Back up your files and settings before installing this preview.*While Windows 10 Technical Preview for Enterprise is only available in English, Chinese, and Brazilian Portuguese, the English version can be installed in all markets where Windows is available.*Upon installation, Windows will prompt you to activate. A product key is not required for this software.*In order to use Windows 10 Technical Preview for Enterprise, you must sign in to your PC with a Microsoft account. The option to create a local account will be made available at the time of the final release.*
If you decide that you want to install Windows 10 Technical Preview for Enterprise using one of the provided ISO files, you won't be able to uninstall it. In addition, after you install Windows 10 Technical Preview for Enterprise, you won't be able to use the recovery partition on your PC to go back to your preview version of Windows. A clean installation of your former operating system will be required, and you will need to re-install all of your programs and data.*
*
Product Key
Upon installation, Windows will prompt you to activate. A product key is not required for this software. For recovery scenarios, the following key may be used: PBHCJ-Q2NYD-2PX34-T2TD6-233PK
*
Things to Know*
Windows 10 Technical Preview for Enterprise is prerelease software that may be substantially modified before it's commercially released. It is designed for IT professionals interested in trying out the next version of Windows on behalf of their organizations. Microsoft makes no warranties, express or implied, with respect to the information provided here. Some product features and functionality may require additional hardware or software. We do not recommend that you install this preview if you are not an IT professional or not professionally managing corporate PCs or devices. We also do not recommend that you install this preview on your primary home or business PC.*
Windows 10 Technical Preview for Enterprise should work with the same devices and programs that work with Windows 8.1. In some cases, a device or program might not work or may require an update, or you might need to uninstall some programs and then reinstall them after installing the preview.*
Windows 10 Technical Preview for Enterprise is not supported on Windows RT devices.
For 64-bit installations of Windows 10 Technical Preview for Enterprise, a small number of older PCs will be blocked from installing the preview because they don't support CMPXCHG16b, PrefetchW, and LAHF/SAHF.*
To use touch, you need a tablet or monitor that supports multitouch.
To access the Windows Store, and to download and run apps, you need an active internet connection, a screen resolution of at least 1024 x 768, and a Microsoft account.
Downloading Windows 10 Technical Preview for Enterprise could take a few hours. The exact time will depend on your provider, bandwidth, and traffic (ISP fees may apply). For technical questions, please visit the*Windows 10 Technical Preview for Enterprise Forums.*
Sent From Windows 7 On HTC Droid DNA