Anyone know if CE6 can run on the wizard and if so where can we get a rom for it?
dragonedge said:
Anyone know if CE6 can run on the wizard and if so where can we get a rom for it?
Click to expand...
Click to collapse
Is this crossbow what u r talking about ?
M$ has Launched Windows CE6 Today, I was wondering if anyone has got their hands on it and been able to play around with device compatibility.
Here's a link to the article:
http://msmobiles.com/news.php/5716.html
And here's a link to the trial:
http://www.microsoft.com/windows/embedded/eval/trial.mspx
Thanks for the links. I'm going to download now
dragonedge,
Please post your results, I would be very interested to know if it will run on my wizard.
Thanks,
Clay
dude...
1) you cross posted
2) again, this is released to the manufactuers, it'll be at LEAST 4 to 6 months before we even hear of a device testing this OS
3) what you posted is an evaluation environment for Visual Studio... lol. You're not going to get your hands on something like that that easily.
Windows Embedded CE 6.0 (plug-in for Visual Studio 2005)
Click to expand...
Click to collapse
awwww too bad but shouldn't you be able to create some type of Rom with this? Or is this literally just a developer tool released for a software that hasn't been released or won't be for a long time?
Overview
Windows® Embedded CE 6.0 is a componentized operating system designed from the ground up to power small footprint devices and help developers get them to market fast. Choosing from a wide variety of technology components and pre-existing templates, you can quickly build hard real-time commercial and consumer electronics devices, such as:
Set-top boxes
Thin clients
Digital media adapters
Voice-over-IP (VoIP) phones
Navigation devices
Medical devices
Portable media players
Home gateways
Digital cameras
Networked digital televisions
PDAs
Features
Along with its portfolio of hundreds of carefully tested, easily selectable OS components, Windows Embedded CE 6.0 includes innovative features designed to help promote performance, security, compatibility, and flexibility.
Robust Architecture
Unified Kernel. The redesigned Windows Embedded CE 6.0 kernel now handles more than 32,000 simultaneous processes, each with 2 GB of virtual memory space. The new file system supports larger storage media and file sizes (up to 4 GB), and removable media encryption.
Drivers. Production-quality device drivers help decrease the amount of modification needed for drivers to work with custom hardware, and enhanced driver support in CE 6.0 helps ensure easy portability. Drivers can be run in kernel mode for performance or in user mode for robustness.
Security. The redesigned one-tier security model is SDL compliant and helps ensure that only trusted applications can run on your embedded device.
Compatibility. CE 6.0 works with key processor architectures (x86, ARM, SH4, and MIPS) and, through its compatibility testing tool, has features to help port existing Win32 applications.
Device Performance. Improvements to the kernel architecture have greatly reduced the overhead of system calls between base OS services, resulting in improved operating system performance.
New Media and Communication Components
Windows Embedded CE 6.0 opens up new opportunities to develop compelling products for home and business.
Network Media Devices. You now have the ability to build networked media devices that can consume pictures, videos, and music from a Windows PC via a home network.
Digital Video Recorders. The DVR engine in CE 6.0 empowers you to build devices that can record multiple video streams to a hard drive for later playback
Cellular Networks. The new Cellcore components help enable your CE 6.0 powered devices to easily make data connections and initiate voice calls through cellular networks.
Windows Network Projectors. Users can now connect their Windows Vista™ laptop to a CE 6.0-based projector wirelessly or over any IP network.
Powerful Development Environment
By adding Platform Builder to Visual Studio 2005, Windows Embedded CE 6.0 helps deliver a superior unified embedded developer experience. Developers can now use one common familiar environment to develop both application and operating system software. Development advantages include:
Visual Studio 2005. Platform Builder for Windows Embedded CE 6.0 has been created as a plug-in for Visual Studio 2005 and is customized for developing embedded operating systems and components.
Application Development Options. You can go native or managed by choosing your preferred Microsoft development technology—Win32, MFC, or the .NET Compact Framework (C#, VB).
Device Emulation. The new ARM-based device emulator included with Platform Builder makes it easy to configure, build, and test operating system images.
Editors. Coding and building are faster. Windows Embedded CE 6.0 editors now incorporate Intellisense technology, syntax highlighting, and graphical bib and registry file editors.
Improved Compilers. Based on Visual Studio 2005, the latest compilers increase C++ language conformance; provide better libraries; support CRT, ATL, and MFC; and offer improved run-time security checks (/GS).
Source Code Access. Access to CE 6.0 source code helps developers debug, test, and make changes to an OS image. It also allows you to modify the operating system software to create differentiated features while maintaining control over your intellectual property.
Price
Development Tools: $995.00 USD
Runtime License Cost: (per runtime shipped):
$3.00 USD for Core SKU*
(The Core SKU is a subset of the Windows Embedded CE Core operating system features.)
$16.00 USD for Professional SKU*
(The Professional SKU is a higher-end license that is ideal for devices that require rich multimedia and graphics.)
* Run-time pricing is based on purchase volume of one unit (except Windows CE Core based on 1000 units). Volume discounts are available. Local taxes, tariffs and other costs may apply. Contact a Windows Embedded Authorized Distributor for details.
A complete list of the components included in Windows Embedded CE Core and Windows Embedded CE Pro is available at the Microsoft Download Center.
Details on each component are available at the MSDN Library.
For complete pricing and licensing information, please contact a Microsoft Windows Embedded Authorized Distributor.
In conclusion, this is for manufacturers/developers only. It is of no use to us.
Sounds this is just for developers
GreenRom DevKit is now available. It has the tools for compiling roms from source and a script that installs the rest of the tools you need. Although synaptic and gdebi have been removed, they can be easily installed in the terminal with apt-get. I have written instructions to facilitate the installation of this software. This distro was designed for ease of use and is for both the novice and highly experienced developer. On a side note, neither xda nor myself are rsponsible for any damages that may occur from the Iinstallation of this distro. By downloading and installing you take full responsibility for your own actions. Relax, you know the drill. Follow the instruction to a tee and you'll be fine.
*Note: Contact either metalcated or myself with any questions concerning GRP Dev Kit. You can also contact us over at: http://www.greenromproject.com
Some common questions might be:
?-Why is this important?
!-Because there seems to be a shortage of Android developers as a result of the intimidation of setting up a build environment and having what you need to get started. Now you can install this os and be on your way to becoming a developer if you have the desire.
?-Do I have to install GRPdevkit to my HDD?
!-No, you can install it on a pen/usb drive and run it from that if your bios detects usb drives. Since you will have to run a script to finnish installing a few tools, you can't run it from a live session. Just set up your usb pen drive by partitioning it as you would a hdd, install the devkit and store your progress as you normally would. The decision was made to make this os fit on a cd. Nevertheless, you can install it on your pen drive(usb stick) and carry it with you anywhere!
?-Will I be able to install this alongside another OS?
!-Possibly, although LivLogik and I haven't had any luck with dual booting this nor Ubuntu.
?-Will this screw up my computer?
!-As with any Linux OS that's experimental, the possibility is there, although LivLogik and I have been testing this OS extensively to ensure all the bugs have been work out before making it available to you. Nevertheless, we are in no way responsible for your actions!
?-What if I don't want to dev and just want to use this for an every day system?
!-That will be up to you as this os is attractive and practical. Follow the instructions to the letter and you can install anything else that will suite your fancy.
?-What if I can't burn an installation disk?
!-As with the majority of mainstream Linux Distros, we will be offering an installation disk for a small fee + s&h. LivLogik and I have to come up with a design for the cd decal as I have access to a cd printer. We will post the availability when we come up with it.-Now available
?-How do I use the tools that are in this?
!-There is a get started guide that automatically appears on the desktop. The guide can be disabled in the startup apps settings. The guide explains briefly how to use the tools, however, I didn't include instructions on Eclipse as I've never used it. For Eclipse just go to it's website here: http://eclipsetutorial.sourceforge.net/totalbeginner.html and learn how to use it. Eclipse is used to make programs for Android.
LivLogik will be making a video so that you can see it in action. Enjoy!!
Note: you may need to right click on the desktop and change the wallpaper mode setting from zoom to whatever fits your screen best. -Fixed in update
Stoute will be trying to upload the iso to GRP a.s.a.p.
Pre-installation Instructions
======> Video on partitioning <======
After you download the iso you'll need to burn it onto a cd: http://www.wikihow.com/Burn-ISO-Files-to-DVD and then boot it selecting Live mode. Instructions are basically the same for linux but you'll have to use xfburn, brasero or another app that burns iso files to disc. Next, you may have to use cfdisk to partition your hard drive if the Installer doesn't take you to the partitioner automatically. To do this, open a terimnal and type:
sudo cfdisk
and hit enter. Now you need to select a partition that you want to install to. Pick one and delete it to create a new one or create a new one altogether. You don't have to select type but make sure you make it a primary partition and make it bootable. Then you need to create a swap partition. Make it 512Mb or you could try 256Mb if you have limited hdd space and make sure you choose swap(82) for the type. After you've set up the partitions you can quit the cfdisk and start the Installer. The partitioner may give you some sort of error such as "unable to unmount partition 10GB or something similar. Don't worry about that, just continue with the Installer.
**VBox instructions (Tools now included in new build)
when setting up your vm, you must first choose new. Then when it asks you what system you choose Linux and then for the distro choose ubuntu if you have a 64bit host or choose Gentoo[64bit] if you're using a 32bit host. The rest is pretty much preference. I chose 512Mb for memory. Now when you first boot your newly install vm of grpdevkit, you'll notice that the screen res is 800x600. That's not good unless you're using a laptop or netbook. metalcated wrote some instructions to solve this resolution dilemma as follows:
Installing Guest Additions on Debian
Follow these steps to install the Guest Additions on your Debian virtual machine:
Open the Root Terminal
Install required packages --> apt-get install build-essential module-assistant
Configure your system for building kernel modules by running --> m-a prepare
Click on Install Guest Additions… from the Devices menu, the cd should mount --> /media/cdrom
Run sh /media/cdrom/VBoxLinuxAdditions.run, and follow the instructions on screen
Log out and Log back in... your resolution should be adjusted
~ metalcated
*Note-This distro has sun java 6 installed on it and by downloading this distro you agree to the following:
Code:
[FONT="Arial"][size="1"]Sun Microsystems, Inc. Binary Code License Agreement
for the JAVA SE DEVELOPMENT KIT (JDK), VERSION 6
SUN MICROSYSTEMS, INC. ("SUN") IS WILLING TO LICENSE
THE SOFTWARE IDENTIFIED BELOW TO YOU ONLY UPON THE
CONDITION THAT YOU ACCEPT ALL OF THE TERMS CONTAINED
IN THIS BINARY CODE LICENSE AGREEMENT AND SUPPLEMENTAL
LICENSE TERMS (COLLECTIVELY "AGREEMENT"). PLEASE READ
THE AGREEMENT CAREFULLY. BY DOWNLOADING OR INSTALLING
THIS SOFTWARE, YOU ACCEPT THE TERMS OF THE AGREEMENT.
INDICATE ACCEPTANCE BY SELECTING THE "ACCEPT" BUTTON
AT THE BOTTOM OF THE AGREEMENT. IF YOU ARE NOT WILLING
TO BE BOUND BY ALL THE TERMS, SELECT THE "DECLINE"
BUTTON AT THE BOTTOM OF THE AGREEMENT AND THE DOWNLOAD
OR INSTALL PROCESS WILL NOT CONTINUE.
1. DEFINITIONS. "Software" means the identified above
in binary form, any other machine readable materials
(including, but not limited to, libraries, source
files, header files, and data files), any updates or
error corrections provided by Sun, and any user
manuals, programming guides and other documentation
provided to you by Sun under this Agreement.
"Programs" mean Java applets and applications intended
to run on the Java Platform, Standard Edition (Java
SE) on Java-enabled general purpose desktop computers
and servers.
2. LICENSE TO USE. Subject to the terms and conditions
of this Agreement, including, but not limited to the
Java Technology Restrictions of the Supplemental
License Terms, Sun grants you a non-exclusive,
non-transferable, limited license without license fees
to reproduce and use internally Software complete and
unmodified for the sole purpose of running Programs.
Additional licenses for developers and/or publishers
are granted in the Supplemental License Terms.
3. RESTRICTIONS. Software is confidential and
copyrighted. Title to Software and all associated
intellectual property rights is retained by Sun and/or
its licensors. Unless enforcement is prohibited by
applicable law, you may not modify, decompile, or
reverse engineer Software. You acknowledge that
Licensed Software is not designed or intended for use
in the design, construction, operation or maintenance
of any nuclear facility. Sun Microsystems, Inc.
disclaims any express or implied warranty of fitness
for such uses. No right, title or interest in or to
any trademark, service mark, logo or trade name of Sun
or its licensors is granted under this Agreement.
Additional restrictions for developers and/or
publishers licenses are set forth in the Supplemental
License Terms.
4. LIMITED WARRANTY. Sun warrants to you that for a
period of ninety (90) days from the date of purchase,
as evidenced by a copy of the receipt, the media on
which Software is furnished (if any) will be free of
defects in materials and workmanship under normal use.
Except for the foregoing, Software is provided "AS IS".
Your exclusive remedy and Sun's entire liability under
this limited warranty will be at Sun's option to
replace Software media or refund the fee paid for
Software. Any implied warranties on the Software are
limited to 90 days. Some states do not allow
limitations on duration of an implied warranty, so the
above may not apply to you. This limited warranty
gives you specific legal rights. You may have others,
which vary from state to state.
5. DISCLAIMER OF WARRANTY. UNLESS SPECIFIED IN THIS
AGREEMENT, ALL EXPRESS OR IMPLIED CONDITIONS,
REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED
WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE OR NON-INFRINGEMENT ARE DISCLAIMED, EXCEPT TO
THE EXTENT THAT THESE DISCLAIMERS ARE HELD TO BE
LEGALLY INVALID.
6. LIMITATION OF LIABILITY. TO THE EXTENT NOT
PROHIBITED BY LAW, IN NO EVENT WILL SUN OR ITS
LICENSORS BE LIABLE FOR ANY LOST REVENUE, PROFIT OR
DATA, OR FOR SPECIAL, INDIRECT, CONSEQUENTIAL,
INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER CAUSED
REGARDLESS OF THE THEORY OF LIABILITY, ARISING OUT OF
OR RELATED TO THE USE OF OR INABILITY TO USE SOFTWARE,
EVEN IF SUN HAS BEEN ADVISED OF THE POSSIBILITY OF
SUCH DAMAGES. In no event will Sun's liability to you,
whether in contract, tort (including negligence), or
otherwise, exceed the amount paid by you for Software
under this Agreement. The foregoing limitations will
apply even if the above stated warranty fails of its
essential purpose. Some states do not allow the
exclusion of incidental or consequential damages, so
some of the terms above may not be applicable to you.
7. TERMINATION. This Agreement is effective until
terminated. You may terminate this Agreement at any
time by destroying all copies of Software. This
Agreement will terminate immediately without notice
from Sun if you fail to comply with any provision of
this Agreement. Either party may terminate this
Agreement immediately should any Software become, or
in either party's opinion be likely to become, the
subject of a claim of infringement of any intellectual
property right. Upon Termination, you must destroy all
copies of Software.
8. EXPORT REGULATIONS. All Software and technical data
delivered under this Agreement are subject to US
export control laws and may be subject to export or
import regulations in other countries. You agree to
comply strictly with all such laws and regulations and
acknowledge that you have the responsibility to obtain
such licenses to export, re-export, or import as may
be required after delivery to you.
9. TRADEMARKS AND LOGOS. You acknowledge and agree as
between you and Sun that Sun owns the SUN, SOLARIS,
JAVA, JINI, FORTE, and iPLANET trademarks and all SUN,
SOLARIS, JAVA, JINI, FORTE, and iPLANET-related
trademarks, service marks, logos and other brand
designations ("Sun Marks"), and you agree to comply
with the Sun Trademark and Logo Usage Requirements
currently located at
http://www.sun.com/policies/trademarks. Any use you
make of the Sun Marks inures to Sun's benefit.
10. U.S. GOVERNMENT RESTRICTED RIGHTS. If Software is
being acquired by or on behalf of the U.S. Government
or by a U.S. Government prime contractor or
subcontractor (at any tier), then the Government's
rights in Software and accompanying documentation will
be only as set forth in this Agreement; this is in
accordance with 48 CFR 227.7201 through 227.7202-4
(for Department of Defense (DOD) acquisitions) and
with 48 CFR 2.101 and 12.212 (for non-DOD
acquisitions).
11. GOVERNING LAW. Any action related to this Agreement
will be governed by California law and controlling
U.S. federal law. No choice of law rules of any
jurisdiction will apply.
12. SEVERABILITY. If any provision of this Agreement
is held to be unenforceable, this Agreement will
remain in effect with the provision omitted, unless
omission would frustrate the intent of the parties, in
which case this Agreement will immediately terminate.
13. INTEGRATION. This Agreement is the entire agreement
between you and Sun relating to its subject matter. It
supersedes all prior or contemporaneous oral or
written communications, proposals, representations and
warranties and prevails over any conflicting or
additional terms of any quote, order, acknowledgment,
or other communication between the parties relating to
its subject matter during the term of this Agreement.
No modification of this Agreement will be binding,
unless in writing and signed by an authorized
representative of each party.
SUPPLEMENTAL LICENSE TERMS
These Supplemental License Terms add to or modify the
terms of the Binary Code License Agreement.
Capitalized terms not defined in these Supplemental
Terms shall have the same meanings ascribed to them in
the Binary Code License Agreement . These Supplemental
Terms shall supersede any inconsistent or conflicting
terms in the Binary Code License Agreement, or in any
license contained within the Software.
A. Software Internal Use and Development License
Grant. Subject to the terms and conditions of this
Agreement and restrictions and exceptions set forth in
the Software "README" file incorporated herein by
reference, including, but not limited to the Java
Technology Restrictions of these Supplemental Terms,
Sun grants you a non-exclusive, non-transferable,
limited license without fees to reproduce internally
and use internally the Software complete and
unmodified for the purpose of designing, developing,
and testing your Programs.
B. License to Distribute Software. Subject to the
terms and conditions of this Agreement and
restrictions and exceptions set forth in the Software
README file, including, but not limited to the Java
Technology Restrictions of these Supplemental Terms,
Sun grants you a non-exclusive, non-transferable,
limited license without fees to reproduce and
distribute the Software, provided that (i) you
distribute the Software complete and unmodified and
only bundled as part of, and for the sole purpose of
running, your Programs, (ii) the Programs add
significant and primary functionality to the Software,
(iii) you do not distribute additional software
intended to replace any component(s) of the Software,
(iv) you do not remove or alter any proprietary
legends or notices contained in the Software, (v) you
only distribute the Software subject to a license
agreement that protects Sun's interests consistent
with the terms contained in this Agreement, and (vi)
you agree to defend and indemnify Sun and its
licensors from and against any damages, costs,
liabilities, settlement amounts and/or expenses
(including attorneys' fees) incurred in connection
with any claim, lawsuit or action by any third party
that arises or results from the use or distribution of
any and all Programs and/or Software.
C. License to Distribute Redistributables. Subject to
the terms and conditions of this Agreement and
restrictions and exceptions set forth in the Software
README file, including but not limited to the Java
Technology Restrictions of these Supplemental Terms,
Sun grants you a non-exclusive, non-transferable,
limited license without fees to reproduce and
distribute those files specifically identified as
redistributable in the Software "README" file
("Redistributables") provided that: (i) you distribute
the Redistributables complete and unmodified, and only
bundled as part of Programs, (ii) the Programs add
significant and primary functionality to the
Redistributables, (iii) you do not distribute
additional software intended to supersede any
component(s) of the Redistributables (unless otherwise
specified in the applicable README file), (iv) you do
not remove or alter any proprietary legends or notices
contained in or on the Redistributables, (v) you only
distribute the Redistributables pursuant to a license
agreement that protects Sun's interests consistent
with the terms contained in the Agreement, (vi) you
agree to defend and indemnify Sun and its licensors
from and against any damages, costs, liabilities,
settlement amounts and/or expenses (including
attorneys' fees) incurred in connection with any
claim, lawsuit or action by any third party that
arises or results from the use or distribution of any
and all Programs and/or Software.
D. Java Technology Restrictions. You may not create,
modify, or change the behavior of, or authorize your
licensees to create, modify, or change the behavior
of, classes, interfaces, or subpackages that are in
any way identified as "java", "javax", "sun" or
similar convention as specified by Sun in any naming
convention designation.
E. Distribution by Publishers. This section pertains
to your distribution of the Software with your printed
book or magazine (as those terms are commonly used in
the industry) relating to Java technology
("Publication"). Subject to and conditioned upon your
compliance with the restrictions and obligations
contained in the Agreement, in addition to the license
granted in Paragraph 1 above, Sun hereby grants to you
a non-exclusive, nontransferable limited right to
reproduce complete and unmodified copies of the
Software on electronic media (the "Media") for the
sole purpose of inclusion and distribution with your
Publication(s), subject to the following terms: (i)
You may not distribute the Software on a stand-alone
basis; it must be distributed with your
Publication(s); (ii) You are responsible for
downloading the Software from the applicable Sun web
site; (iii) You must refer to the Software as JavaTM
SE Development Kit 6; (iv) The Software must be
reproduced in its entirety and without any
modification whatsoever (including, without
limitation, the Binary Code License and Supplemental
License Terms accompanying the Software and
proprietary rights notices contained in the Software);
(v) The Media label shall include the following
information: Copyright 2006, Sun Microsystems, Inc.
All rights reserved. Use is subject to license terms.
Sun, Sun Microsystems, the Sun logo, Solaris, Java,
the Java Coffee Cup logo, J2SE, and all trademarks and
logos based on Java are trademarks or registered
trademarks of Sun Microsystems, Inc. in the U.S. and
other countries. This information must be placed on
the Media label in such a manner as to only apply to
the Sun Software; (vi) You must clearly identify the
Software as Sun's product on the Media holder or Media
label, and you may not state or imply that Sun is
responsible for any third-party software contained on
the Media; (vii) You may not include any third party
software on the Media which is intended to be a
replacement or substitute for the Software; (viii) You
shall indemnify Sun for all damages arising from your
failure to comply with the requirements of this
Agreement. In addition, you shall defend, at your
expense, any and all claims brought against Sun by
third parties, and shall pay all damages awarded by a
court of competent jurisdiction, or such settlement
amount negotiated by you, arising out of or in
connection with your use, reproduction or distribution
of the Software and/or the Publication. Your
obligation to provide indemnification under this
section shall arise provided that Sun: (a) provides
you prompt notice of the claim; (b) gives you sole
control of the defense and settlement of the claim;
(c) provides you, at your expense, with all available
information, assistance and authority to defend; and
(d) has not compromised or settled such claim without
your prior written consent; and (ix) You shall provide
Sun with a written notice for each Publication; such
notice shall include the following information: (1)
title of Publication, (2) author(s), (3) date of
Publication, and (4) ISBN or ISSN numbers. Such notice
shall be sent to Sun Microsystems, Inc., 4150 Network
Circle, M/S USCA12-110, Santa Clara, California 95054,
U.S.A , Attention: Contracts Administration.
F. Source Code. Software may contain source code that,
unless expressly licensed for other purposes, is
provided solely for reference purposes pursuant to the
terms of this Agreement. Source code may not be
redistributed unless expressly provided for in this
Agreement.
G. Third Party Code. Additional copyright notices and
license terms applicable to portions of the Software
are set forth in the THIRDPARTYLICENSEREADME.txt file.
In addition to any terms and conditions of any third
party opensource/freeware license identified in the
THIRDPARTYLICENSEREADME.txt file, the disclaimer of
warranty and limitation of liability provisions in
paragraphs 5 and 6 of the Binary Code License
Agreement shall apply to all Software in this
distribution.
H. Termination for Infringement. Either party may
terminate this Agreement immediately should any
Software become, or in either party's opinion be
likely to become, the subject of a claim of
infringement of any intellectual property right.
I. Installation and Auto-Update. The Software's
installation and auto-update processes transmit a
limited amount of data to Sun (or its service
provider) about those specific processes to help Sun
understand and optimize them. Sun does not associate
the data with personally identifiable information.
You can find more information about the data Sun
collects at http://java.com/data/.
For inquiries please contact: Sun Microsystems, Inc.,
4150 Network Circle, Santa Clara, California 95054,
U.S.A.[/size][/font]
If you don't agree with the Sun Java license then don't download this distro!! ;-)
Here's an outside link:
->>>========> GRP DevKit v1.4.3 64 bit <========<<<-
Code:
[color=blue]Change Log: [/color]
(9-17-11 v1.4.3) fixes by metalcated
-updated the repo to the most current (apt-get update)
-updated Kernel from 2.6.32-35 to 2.6.32-36 as well as other packages (apt-get upgrade)
-updated adbinstaller.sh with usability enhancements for the end user
-added LXTerminal replacing mrxvt and terminator (updated wbar icons)
-added A new theme to solve issues with adbinstaller.sh EULA crashing
-added Minor changes to the menubar (usability)
-added VirtualBox Tools for running in a virtual machine (http://www.virtualbox.org/)
-corrected Problem with sudo not working (made changes to the default groups settings)
(9-14-11 v1.4.2)
-added gtk2-engines-murrine murrine-themes(fix by metalcated)
-added mrxvt mrxvt-common(again, fix by metalcated)
-ran sudo update to fix issues with Eclipse install(solution by metalcated)
**above fixes allow installers on desktop to function properly.
(9-14-11 v1.4.1)
-removed Midori browser
-removed Xarchiver
-removed Pinta
-removed mrxvt
-added Terminator terminal(has copy/paste feature)
-added synaptic package manager(install any software now)
-added new sources.list by Metalcated
-added auto-add user to sudoer list by Metalcated
-added root terminal to Wbar
-added Synaptic package manager to Wbar
-added Chrome browser
-added Gimp
-added new GRP DevKit wallpaper
-centered GRP name over Wbar
-changed browser icon in Wbar from Midori to Chrome
-added a launcher on desktop to install:
*SDK&NDK
*adb
*Eclipse
(9-8-11 v1.4)
-removed adb, SDK, NDK, and Eclipse
-removed Chrome browser
-removed Xarchiver
-removed File-Roller
-removed SDK/NDK shortcut(shortcut not needed anymore)
-removed Gdebi
-removed Synaptic package manager
-Debian Squeeze for the base of distro
-added Xfce4 for the desktop
-added Xfce Theme Installer
-added Wbar dock for shortcuts
-added Midori as a lightweight browser
-added Squeeze as a lightweight archiver
-added Xfburn as a lightweight cd/dvd/iso/data burner
-added README guide to autostartup list
-added Linux Mint icons & Mint-x-Meatal-Dark theme
-added Pinta as lightweight graphical editing app
-added Leafpad as lightweight notepad
-added Bleachbit to clean junk files(be careful)
-added new GRP DevKit wallpaper
-added Gpicview as a lightweight image viewer
-added Remastersys installer shortcut on desktop
-changed Remastersys boot menu colors to better accommodate GRP theme.
-repositioned and sized Xfce-panel adding it to top left to make room for Wbar.
-added a script on desktop to manually run in terminal to install:
*SDK&NDK
*adb
*Eclipse
(versions 1.2-1.3 not listed)
(07-22-11 v1.1) :
~Added Chrome Browser
~Added plugin for Gtalk
~Shortcut for SDK/NDK in home folder
~Added shortcut for GRP forum
~Added different wallpaper([color=blue]thanks LivLogik[/color])
(6-?-11 v1) :
~Linux Mint 11(Katya) as Distro base [URL=http://www.linuxmint.com/]Linux Mint11[/URL]
~Remastersys(for building the distro [url]http://remastersys.sourceforge.net/[/url])
~Added GRP custom default wallpaper([color=blue]thanks LivLogik[/color])
~Added Android NDK
~Added Android SDK
~Added all required dependencies for compiling Android OS as follows:
git-core, gnupg, flex bison, gperf, libsdl1.2-dev, libesd0-dev, libwxgtk2.6-dev, squashfs-tools, build-essential zip curl, libncurses5-dev, zlib1g-dev,
sun-java6-jdk, pngcrush, schedtool, lib32z1-dev, lib32ncurses5-dev, lib32readline5-dev
~Added adb(thanks to Tahl:[URL=http://www.rootzwiki.com/showthread.php?589-Android-SDK-NDK-Eclipse-and-ADB-Auto-Installer-(Ubuntu-Linux-Mint)]Tahl's tread[/URL])
~Added Gimp
~Added ThemerStudio(thanks to CorCor67:[URL=http://corcor67.blogspot.com/p/themer-studio.html]CorCor's blog[/URL])
~Added Repo Init to home directory
Credits
I would like to take this time to thank the following
for either their contribution to this project or their
resources:
Treken(me)-Head developer of the GreenRom DevKit
~ metalcated(now the Co-Developer)-For creating a new sources.list and scripting that adds user to the sudoers list during installation of GRP DevKit and many other enhancements.
LivLogik-For his graphical wizardry
Stoute-For the GreenRomProject site
GreenRom Dev Team-For testing and suggestions
Debian-For the base of this distro
XFCE-For a slim and cool desktop
Google-For Android and development tools
Fragadelic-For the Remastersys tool
Tahl-For his adb installer (modified by ~ metalcated)
Shiki-Wise-Shiki-Wise Green Theme (compatibility)
Cliz-For Xfce Theme Installer
*Note: If I left anyone out, I appologize. Let me
know and I'll add you to the list.
Whoever else has tested or is running the Dev Kit let me know so I can include you in the testers credits. ;-)
Thank You xda for providing a site for those of us that need answers!!
Testers:
-metalcated
-treken
-Ask to be added
click on my sig :-/
Moved to Software Development
Thank you for moving my tread!
Pm sent
Sent from my SCH-I510 using Tapatalk
black02ss said:
Pm sent
Sent from my SCH-I510 using Tapatalk
Click to expand...
Click to collapse
I pmed you back.
Thanks for the quick response.
Sent from my SCH-I510 using Tapatalk
This looks great. Thanks for your work.
No prob !
Looks good, I'll definitely have to try this on VMware with my 300GB usb hdd
Sent from my Zio using xda premium
Going to try and get an update uploaded today or tomorrow. Metalcated is working on a script that will add the user to the sudoers list as part of the installation process so you can run sudo commands.
hmm, is this working on a VM?
Yes. Two people are running it on vm
Treken said:
Yes. Two people are running it on vm
Click to expand...
Click to collapse
No luck in Virtual Box here; Whether I push enter at the countdown, or wait, I can't get it to move on from there.
I just recently updated the tread with another distro with some fixes. Also, livlogik over at green rom project can give you sound advice on running in a virtual machine. I don't think he was able to get it going in virtual machine, but I think he got it working in parallel machine, and in virtual box. This is a 64 bit os. So maybe you need to set it up for that? I really don't have much experience with virtual machines. I always install locally
Treken said:
I just recently updated the tread with another distro with some fixes. Also, livlogik over at green rom project can give you sound advice on running in a virtual machine. I don't think he was able to get it going in virtual machine, but I think he got it working in parallel machine, and in virtual box. Thia is a 64 bit os. So maybe you need to set it up for that? I really don't have much experience with virtual machines. I always install locally
Click to expand...
Click to collapse
And there lies the problem, I'm running a 32 bit only processor in the laptop I attempted to run it on (core duo). Goes to show I didn't really read
I actually didn't specify 64 bit. Guess I dropped the ball on that one. I added that to the tread title. Thanks
You mentioned that it can installed to a usb stick, but how??
After you burn the iso to a disc, you plug in your usb stick and boot the cd. When you run the installer, select your usb stick to install to. You'll need to partition it as though it were a hdd.
Ok, Thanks
synergye said:
And there lies the problem, I'm running a 32 bit only processor in the laptop I attempted to run it on (core duo). Goes to show I didn't really read
Click to expand...
Click to collapse
Just found a work around. When you set up your vm in vbox, select gentoo[64bit] and you can run this from a 32 bit host.
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.
BACKGROUND: ACPI carries major security risks.
Ubuntu founder Mark Shuttleworth has likened ACPI to Trojan horses. He has described proprietary firmware (ACPI-related or any other firmware) as a security risk, saying that "firmware on your device is the NSA's best friend" and calling firmware (ACPI or non-ACPI) "a Trojan horse of monumental proportions". He has pointed out that low quality, closed source firmware is a major threat to system security:[12] "Your biggest mistake is to assume that the NSA is the only institution abusing this position of trust — in fact, it's reasonable to assume that all firmware is a cesspool of insecurity, courtesy of incompetence of the highest degree from manufacturers, and competence of the highest degree from a very wide range of such agencies." As a solution to this problem, he has called for open-source, declarative firmware (ACPI or non-ACPI),[12] which instead of containing executable code, only describes "hardware linkage and dependencies".
VULNERABILITY: Windows 10 packages a Windows management interface for ACPI (wmiacpi.sys).
It's a way for low firmware/BIOS to communicate with Windows. Most consumers do not have BIOS code in general and at runtime - so this is a security risk. Bad actors may utilize this interface to gain full access to Windows by modifying low-level code of BIOS, for example. I have seen a BIOS rootkit, Ubuntu founder is spot on. It is safe to hypothesize BIOS rootkits are endemic and are used by intelligence agencies and countless really bad actors who may live nextdoor.
SOLUTION: Remove Windows management interface and Microsoft System Management BIOS driver from a Windows 10 machine BEFORE installation.
It is crucial this interface driver is removed BEFORE installation, not after. This is key. If it's removed post install you have already opened your machine up to manipulation during installation, with damage already done. This removal requires using DISM to unpackage the installation media's boot and install disks, deleting every file (and folder) with "wmiacpi" and "mssmbios" mention in it (see sample code below), repackaging the disks and only then installing Windows.
COMMENTS: Your computer is still vulnerable but less so. Closing as many unneeded Windows services, running a tight firewall, minimizing the machine operational footprint are indispensable for security.
Here's the sample code for file deletion within unpacked boot and install disks from Windows installation media:
Rem delete files
set files=C:\temp\Windows\INF\wmiacpi.inf
set files=%files%;C:\temp\Windows\System32\drivers\wmiacpi.sys
set files=%files%;C:\temp\Windows\WinSxS\Manifests\amd64_dual_wmiacpi.inf_31bf3856ad364e35_10.0.19041.1_none_96ee9c20ffe98c11.manifest
set files=%files%;C:\temp\Windows\System32\DriverStore\en-US\wmiacpi.inf_loc
set files=%files%;C:\temp\Windows\WinSxS\Manifests\amd64_wmiacpi.inf.resources_31bf3856ad364e35_10.0.19041.1_en-us_2d0bb86732bc23a8.manifest
set files=%files%;C:\temp\Windows\WinSxS\Manifests\amd64_wmiacpi.inf-languagepack_31bf3856ad364e35_10.0.19041.1_en-us_8fc1e10debc33cb9.manifest
set files=%files%;"C:\temp\Windows\INF\wmiacpi.PNF"
for %%a in (%files%) do (
takeown /f %%a
ICACLS %%a /grant %username%:F
del /q /f %%a
)
Honestly, having Windows is already pointless if your goal is privacy, so this won't do much. It already communicates with telemetry servers and sends data to Microsoft, who's a part of the PRISM program. Avoid Windows and MacOS and go for GNU/Linux and BSD if this is a concern for you.
Also, you must assess your threat level. You need to do more than harden systems if you're targeted by an APT like the NSA as they also have your information. You also have to neutralize ME, avoid AMD, and run coreboot or libreboot on the computer side.
If the NSA, DOD, DOE, etc wants you, they got you. People need to be more concerned with what they do online.
FB, Twitter etc are all malware.
An internet isolated computer is a safe computer.
Your computer didn't dime you out, you did
More than that, if you spend this much time looking at your PC and phone, you should probably do a real world check as well. Gotta distance yourself from sus people xD.
blackhawk said:
If the NSA, DOD, DOE, etc wants you, they got you. People need to be more concerned with what they do online.
FB, Twitter etc are all malware.
An internet isolated computer is a safe computer.
Your computer didn't dime you out, you did
Click to expand...
Click to collapse
Nah there noobs, they cannot beat our proxies and encryption technologies of the average technophile!