Database Users

Windows XP Embedded on HTC devices?

Hi folks
Recenty I got the Windows XP Embedded kit, and I was really satisfied and surprised with the performance of the directly built system on an old machine like a P1 @ 200 MHz with 64 MB of RAM, without a hard disk.
The main goal would be to run truly win32 apps on mobile devices, to give better functionality and compatibility.
Yet the builder supports x86 architecture only, but cannot be a big problem to port it to ARM pocessors.
What might be difficult are these things:
-Getting win32 drivers for built-in devices (ex. integrated SDIO/USB WLAN, BT adapter, touchscreen, and sound devices, and apps for them!)
-Saving user data on turning off (Ebmedded systems are designed for a workstation, like a cash register: prebuilt apps, and nothing more comfort ) like WM200x
If anybody has any suggestion are to get a warm welcome
bye

Yet the builder supports x86 architecture only, but cannot be a big problem to port it to ARM pocessors.
Click to expand...
Click to collapse
Are you kidding me?
This would mean reverse engineering and recompiling every binary in the OS.
Do you have any idea how many hours something like that would take?

yup, you're right, but in theory it's possibe. I've seen a running DOS on a Microchip micro-controller, or for example the Atmel STK 1000 is Linux based, also seen an mPlayer app operational on the demo board at the college.
as you see, i'm not an experienced programmer, but i'm not afraid to ask
Yeah, the basic low-level binaries must be recompiled, and once it's ok, it might be usable with regular win32 apps, until you run an old DOS app, wich directly access the hardware.
A few years ago i was able to port Z80 software to 8086, and it wasn't easy.
I don't really know these things, just want to see opinions, possibilities, and suggestions.

exe files are binarys which are instructions directly for the cpu
it's not parsed by the operating system
so compiling the os is not enough every application needs to be recompiled too

The programs you mentioned have source available in one way or another (since DOS is very old there are clones, like freeDOS).
If you have the full source for an app and the right compiler, porting it to another CPU is feasible.
But, this is not the case with embedded XP. Getting the full source is impossible which means most of the system will have to be rewritten from scratch.
Just look at the Wine project to see what it takes, and they "have it easy" - they are just trying to simulate the APIs not change processor architecture. (Lets make it clear - ARM instruction set is very different from x86).
And as Rudegar said it will not let you run any program that has not been specially compiled for ARM CPU.
I know it sounds like we are trying to kill you idea here but its nothing personal, unfortunately it just isn't feasible. We would all like to be able to run desktop apps on our devices, but simply having embedded XP on them would not accomplish that. Also while many old DOS apps can be run using various emulators like pocketDOS, almost all Win32 apps take more resources than our little gadgets can offer.
I am fairly sure though that in 5 -10 years that problem will be fixed.

<_< man hours or not, reveng'ing this will have a bigger impact than just winDOS Mobile devices. Desktops have a use for this, definitely (because the Vista-Only crap is starting to hit the market). Too bad they don't provide assembly in programming classes anymore, obviously because they don't want anyone else to reverse engineer anything and spoil their foisting fun. <_<
In any case, IIRC XP Embedded is missing the install/uninstall engine, so you can't customize it after it's flashed onto the board. This isn't quite a good start - XPLite or 98Lite are better for reverse engineering from scratch (but they're too powerful for mobile devices).
The other alternative is porting ReactOS, which is a reimplementation of W2K. Those guys are "having a lot of fun" getting things to work, tho. <_<

Maybye Windows CE6 yes, but Windows XP Embedded no, because they must run at 686-AT/X platform IMB. Sorry of my English

linux would be a path
with most linux programs you can compile them yourself
using good old
./configure
make
make install
of cause gui programs could have issues displaying correct
on such a small screen

You MIGHT be able to pull it off by installing a minimal (very!) WinMo firmware and then have it autorun Bochs, which is known to be able to run the PC version of XP.. A customised, thinned-down XPe image should run fine under Bochs.
--W5i2

OTG fun

I just want to celebrate the beauty of the otg cable. I ordered one on eBay and just got to play with it today. First thing I did was plug in my flash drive, perfect. I could access, move copy, delete to my hearts content with root explorer. Then I plugged a USB hub and hooked up the mouse and keyboard from my desktop, perfect. I admit I get really excited over little things

USB connectivity isn't a little thing. The ability to interact with other devices is critical for a mobile device. Think of all the different USB modules available for the x86 laptop--printers, wifi adapters, OTA TV modules, etc etc. You'd want your tablet to be able to do the same thing, and more.
It's good that Android now covers the basic stuff (KB/mouse/cam/joys), but I'd like to see universal stub drivers for different types of devices, that vendors can use to build on, like what Windows has. That would vastly extend the tab's functionality, more than just the usual media consumption shtick that tabs are pigeonholed for.
Android has some momentum coming from its success in smartphones, but it still has a long way to go. Win8 and Intel x86 will be joining the tablet fun in the coming months. If Win8-on-tab can offer much of Windows' functionality w/ a revamped touch GUI, it will be a compelling value proposition. Android isn't a lock.

Win8 won't be able to do it with the same power consumption as ARM using x86. Windows 8 on ARM will not be the same as all programs etc. will need to be ported to ARM architecture including all drivers etc.

Win8 will run on both x86 and ARM. One assumes that the functionality (specifically, driver support) will be roughly the same on both. If the ARM version falters, consumers will gravitate to the x86 rev.
The x86 doesn't need to have the same power efficiency as ARM, it just needs to be in the same neighborbood. x86-on-tab will be able to leverage some of the vast library of existing Win/Lin x86 software, which by itself is a huge value proposition, more than enough to offset the battery-life disadvantage.
Present netbooks can already hit 4-5 hr. It isn't a stretch to see x86 tabs, with improved process and sans HDD, to get close to the 7-8 hr avg that HC tabs are presently getting. The knock on Win7 tabs isn't as much about batt life as it is about Win7's clunkiness on a touch device.
This isn't to say that Win8 is better, only that the tablet market is wide open, and no OS is a favorite. My present handicapping has Win8 and Android as neck-and-neck, assuming competent execution of said efforts. The longer Android takes to mature, the more the scales tip in favor of Win8.
Per Intel's recent blurb, Oak Trail will hit the tab scene this year. We'll know its power efficiency soon enough.

[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 8 and the Death of the Command Line(?)

http://catholictechgeek.blogspot.com/2012/08/does-windows-8-and-winrt-mean-death-to.html
The article above has my full thoughts, but I wonder if there is a bit too much push for the graphical user interface in Windows 8 (and WinRT) and because of this, the survival of the command line in Windows (the thing that a bunch of the rom tools run on) is in jeopardy.

Given how worthless winRT is, useful programs like kitchens will never, ever appear on them. MS will have to keep the command line unless they want to lose everyone to linux/mac.
Even android phones have a working command line.

Just thought I would confirm that the Command line (cmd) is still present in Windows 8. As far as I'm aware there was never any talk about removing it.

they will never remove the command prompt, neither the new powershell....
on RT version, the final user will never use it.. but I think that will be present...

m0nkf1sh said:
Just thought I would confirm that the Command line (cmd) is still present in Windows 8. As far as I'm aware there was never any talk about removing it.
Click to expand...
Click to collapse
Correct, the command line is still there as well as PowerShell.
WinRT resembles Windows 8 in UI looks only. Nothing under that is the same as Win8.
It's like comparing an Android Device to a Desktop PC and wondering why you can't run the same programs on them.

Talderon said:
WinRT resembles Windows 8 in UI looks only. Nothing under that is the same as Win8.
hem.
Click to expand...
Click to collapse
actually it is still the NT kernel in WInRT adapted to ARM underneath I believe, similar to Windows phone, but yeah possibly no command line but i'd hope maybe powershell might be there...

And now the whole situation of "same program, different architectures" is back (after about 6 years).I remember back in the early days of Windows Mobile, you had the issue a developer releasing different builds of the some program for ARM, MIPS, and SH3. Eventually, ARM won out and program installation packages were (somewhat) standardized. Now, we have the issue between ARM and x86. Luckily, Microsoft has made this easier with the windows 8 store, so things aren't fragmented like before. This is probably why there is no real Desktop mode included in the ARM build of Windows 8.

Steven855 said:
And now the whole situation of "same program, different architectures" is back (after about 6 years).I remember back in the early days of Windows Mobile, you had the issue a developer releasing different builds of the some program for ARM, MIPS, and SH3. Eventually, ARM won out and program installation packages were (somewhat) standardized. Now, we have the issue between ARM and x86. Luckily, Microsoft has made this easier with the windows 8 store, so things aren't fragmented like before. This in probably why there is no real Desktop mode included in the ARM build of Windows 8.
Click to expand...
Click to collapse
I don't see an issue with ARM vs. x86 in this same context as the x86 tablet will run like an Ultra Mobile PC.
ARM will be treated the same as Mobile Phones of the same architecture as it is today.

>However, there is still no word yet on whether Microsoft will include the command line for the ARM build of Windows 8.
According to this presentation slide of PowerShell 3.0 (at TechEd 2012), PS3 will support Windows RT. If PS is present, by extension CLI is available.
http://video.ch9.ms/teched/2012/na/WSV414.pptx

e.mote said:
>However, there is still no word yet on whether Microsoft will include the command line for the ARM build of Windows 8.
According to this presentation slide of PowerShell 3.0 (at TechEd 2012), PS3 will support Windows RT. If PS is present, by extension CLI is available.
http://video.ch9.ms/teched/2012/na/WSV414.pptx
Click to expand...
Click to collapse
And there we have it folks!
I am still waiting on word on when we can pre-order the MS Surface. So far, from the Spec's everyone else has shown for their offerings, not much reason to jump ship to another brand. (yet)

Press Windows Key +X and you'll see two command prompts shortcuts...

this should be clarified - ROM tools in Windows RT aren't going to have a barrier in the shape of a command line so much as they'll have a barrier in that all current windows ROM utilities are either for x86 CPUs or Java (and java has no Windows ARM VM) and as such wouldn't run on WinRT's command line anyway.

I don't think an X86 emulator will be an option for Windows RT and the ARM architecture either.

The command line is actually alive and well in Windows 8 and Windows Server 2012. If anything Microsoft is moving the capabilities of the command line forward in recent years. The Power Shell allows to configure a huge part of Windows and Server Software based upon it (e.g. Exchange) that previously was not easily configurable through scripts.
Concerning Windows RT on ARM tablets the problems go much deeper than the command line. The RT-Apps won't be able to install device drivers for Smartphones to access them - this will also be true for official companion apps. Unless there is a class driver like for many printers, keyboards, etc. Windows RT simply won't support connection to those devices (again, this only applies to the ARM version).
For many reasons x86 isn't going anywhere and this limited support of peripherals is just one of them.

According to the Synofsky blog post, RT does support at least the v4 print class driver, but not v3. No mention is made for other peripherals, however.
http://blogs.msdn.com/b/b8/archive/2012/07/25/simplifying-printing-in-windows-8.aspx
It depends on what role MS sees for RT going forward. If RT is to be a limited OS to compete with Android/iOS, then printing support may be it. But if RT is to be a full counterpart of x86, other peripherals support will need to happen.
Looking long term, ARM will play a larger role than x86 in the trend of ever-smaller devices, with increasing emphasis on battery life. From this, my educated guess is that RT won't be the ugly duckling for long.
Let's face it, RT is a work-in-progress. Peripheral support is Windows' strongest card against the other mobile OS'es (and Linux). My take is that it will happen contigent to the above, but it won't be this initial iteration.
In short, don't take the limitations of this v1.0 as being cast in stone.

Talderon said:
Correct, the command line is still there as well as PowerShell.
WinRT resembles Windows 8 in UI looks only. Nothing under that is the same as Win8.
It's like comparing an Android Device to a Desktop PC and wondering why you can't run the same programs on them.
Click to expand...
Click to collapse
Actually, that is factually incorrect. Windows RT shares substantial code with Windows 8, as Microsoft has confirmed many times in the Windows 8/RT development blog.

Samsung Ativ 500T. Android dual boot? Upscaling?

I believe the best hackers/minds/tinkerers in the internet are typically found in these forums, so I like to post the most intricate questions that all other forums failed to answer as my last resort. As they say, save the best for last. (No pressure, lol)
Issue 1:
Upscaling. Atom Clovertrail Z2760 does not have any upscaling option built into its Intel Graphics Control Panel. It is a known issue with all atom 2760 devices including my own tablet Samsung Ativ 500t, as well HP Envy X2, Asus Vivotab Smart, Asus Vivotab tf810c. etc.
The problem presents itself when attempting to run an old game designed for a resolution of 800 x 600, for example. When you go into "full screen" mode, what you get is a still tiny window with huge black bars all around. Somebody suggested using the windows magnifier, but that cuts off some of the game screen.
So, is there any third party mods to the Intel drivers, third party upscaler software, or anything of the sort I can use to solve this situation? Intel did not develop official drivers, and people contacting Samsung were pretty much told "screw you, we dont care"
Issue 2:
Android:
Research found that Bluestacks does not seem to work with my particular tablet. I encountered an interesting thing called Android X86, which Im sure you guys already know about. While going through their website, my head exploded. I do not have the savvy to reconfigure a kernel, or make a bootable USB drive using Linux without..well..Linux. I was just hoping that somebody has successfully installed Android x86 in a more recent Windows 8 tablet. I have found instances of people who did in older Windows 7 tablets, like the Acer w500 for example, but no one yet with specific information no how to install this on a clovertrail tablet.
I was hoping could help me out getting this done. Being able to dual boot the Sammy Ativ 500 would be a dream come true.
Thank you very much for your time.

There's a thread literally right next to this one that talks about installing Android-x86 on a Win8 tablet. You might start there...
The usual solution to the options for display scaling not appearing in the driver control screen is to put Windows into a lower resolution (for example, 1024x768 or 800x600) and then usually (though I haven't tried on Clover Trail) the option you're looking for (display scaling) will appear.

GoodDayToDie said:
There's a thread literally right next to this one that talks about installing Android-x86 on a Win8 tablet. You might start there...
The usual solution to the options for display scaling not appearing in the driver control screen is to put Windows into a lower resolution (for example, 1024x768 or 800x600) and then usually (though I haven't tried on Clover Trail) the option you're looking for (display scaling) will appear.
Click to expand...
Click to collapse
Yeah I tried that. I also tried the whole f11 thing. Nothing. Did not notice that other thread. will go check into it.

GoodDayToDie said:
There's a thread literally right next to this one that talks about installing Android-x86 on a Win8 tablet. You might start there...
The usual solution to the options for display scaling not appearing in the driver control screen is to put Windows into a lower resolution (for example, 1024x768 or 800x600) and then usually (though I haven't tried on Clover Trail) the option you're looking for (display scaling) will appear.
Click to expand...
Click to collapse
Im sorry if Im blind but..which thread are you referring to? I assumed it was the Iconia w700 one but saw no mention of Android X86

Near the end of the w700 thread its become a android-ia discussion not android-x86.
Anyway. The clovertrail CPU used in the 500t ONLY supports windows and will likely refuse to boot anything but windows. It might well be possible to male it boot the Linux kernel eventually but only with that kernel configuration you mentioned not wanting to do. Basically its not possible right now, but if it is possible one day there are 2 solutions to your making a usb drive in Linux without Linux. Firstly, ubuntu is free if you are willing to install it on another machine first (I think you can buy ubuntu DVDs or burn one yourself from windows). Secondly you can make bootable usbs in windows.
Android on clovertrail could eventually work, probably easier job than the surface RT guys have. The clovertrail replacement will be back to normal and support any x86 OS, I don't know why clovertrail has such a restriction, it just does.
Bluestacks for surface pro apparently works fine on clovertrail as does jar of beans. I haven't tried either one myself but have heard the various complaints about bluestacks working or not working.

The driver does not support upscaling.
I'm not sure if there is a hardware upscaler in the PowerVR SGX545 core or not.
but it can be done with software, like upscaling a lowres framebuffer to a highres framebuffer (f.e 640x480 -> 1366x768) and using opengl or directX for filtering or interpolation.
It has to be either done by the driver or as a dll hooked into a directdraw/directX/opengl application.
Driver would be the best option because it would be universal and work with all applications.

darkleafar said:
I believe the best hackers/minds/tinkerers in the internet are typically found in these forums, so I like to post the most intricate questions that all other forums failed to answer as my last resort. As they say, save the best for last. (No pressure, lol)
Issue 1:
Upscaling. Atom Clovertrail Z2760 does not have any upscaling option built into its Intel Graphics Control Panel. It is a known issue with all atom 2760 devices including my own tablet Samsung Ativ 500t, as well HP Envy X2, Asus Vivotab Smart, Asus Vivotab tf810c. etc.
The problem presents itself when attempting to run an old game designed for a resolution of 800 x 600, for example. When you go into "full screen" mode, what you get is a still tiny window with huge black bars all around. Somebody suggested using the windows magnifier, but that cuts off some of the game screen.
So, is there any third party mods to the Intel drivers, third party upscaler software, or anything of the sort I can use to solve this situation? Intel did not develop official drivers, and people contacting Samsung were pretty much told "screw you, we dont care"
Issue 2:
Android:
Research found that Bluestacks does not seem to work with my particular tablet. I encountered an interesting thing called Android X86, which Im sure you guys already know about. While going through their website, my head exploded. I do not have the savvy to reconfigure a kernel, or make a bootable USB drive using Linux without..well..Linux. I was just hoping that somebody has successfully installed Android x86 in a more recent Windows 8 tablet. I have found instances of people who did in older Windows 7 tablets, like the Acer w500 for example, but no one yet with specific information no how to install this on a clovertrail tablet.
I was hoping could help me out getting this done. Being able to dual boot the Sammy Ativ 500 would be a dream come true.
Thank you very much for your time.
Click to expand...
Click to collapse
I made a post about this, and i was able to make it boot to ''chose your language screen'' also it boots in safe mode.

Good News People!
I got android x86 installation to boot perfectly, going to install now. posting instructions when i can.

Good news. bad news.
With a program called easyuefi you are able to get it to boot to android x86 installation, however keyboard is not working when choosing an hard drive partition. in grub screen it works fine.
make a new partition, extract android x86 iso there.
Now open up easyuefi and click add entry
When choosing a boot file, In your extracted android x86 files there is a folder called efi.
choose 32bit efi file and click ok. well add to description android so it wont whine about missin description. Now at the easyuefi boot entry screen click on the entry you just created and choose one time boot, now click on power and choose reboot and then click yes.

Cyanogen based android x86 boots fine in live mode but the resolution is ''out of range'' the cyanogen bootlogo is really wide and bugged out, welcome screen is pixeled out.

Not working my friend. Any other suggestions or updates
justanpotato said:
With a program called easyuefi you are able to get it to boot to android x86 installation, however keyboard is not working when choosing an hard drive partition. in grub screen it works fine.
make a new partition, extract android x86 iso there.
Now open up easyuefi and click add entry
When choosing a boot file, In your extracted android x86 files there is a folder called efi.
choose 32bit efi file and click ok. well add to description android so it wont whine about missin description. Now at the easyuefi boot entry screen click on the entry you just created and choose one time boot, now click on power and choose reboot and then click yes.
Click to expand...
Click to collapse
not working

Ghalilo said:
not working
Click to expand...
Click to collapse
Posted to remixos section of xda, asking help with pictures that remix os actually boots but i still have some problems with it.
Remember to install android files to its own partition on your 500t hard drive / preinstall it there. You can add, modify and remove partitions from Disk Management.
I got remix os to boot with their own installer and cyanogenmod based android x86 android image with easyuefi.
remember to disable from bios the boot protection.
https://forum.xda-developers.com/remix/remix-os/samsung-ativ-500t-boot-remix-os-t3500257