[Beta] Win86emu: Running x86 apps on WinRT devices
- Thread starter mamaich
- Start date
Tried some torrents with new version of your tool, got a bunch of new errors, most of them are similar and are pointing at i<len error(what?). Also, foobar2000 worked. Well, almost. Couldn't load any music, but UI is working, with panelsUI and columnsUI. Some error messages' screenshots are attached.
Can you please share a utorrent.exe from 2.0.2, all that I can find is installers that fail to run under emulation.
UPD: disregard that, you just don't have permission to write in /program files/. Now I have utorrent 2.0.3 installed, but it just crashes when you load a .torrent file like on a screenshot, error with "i<len" can just be ignored. Also, winamp 2.95 runs, but crashes when you load mp3s.
Can you please share a utorrent.exe from 2.0.2, all that I can find is installers that fail to run under emulation.
UPD: disregard that, you just don't have permission to write in /program files/. Now I have utorrent 2.0.3 installed, but it just crashes when you load a .torrent file like on a screenshot, error with "i<len" can just be ignored. Also, winamp 2.95 runs, but crashes when you load mp3s.
Attachments
Last edited:
Could u please share your version of the app? I tried 1.0.3 and it installed however after running of exe file it crashes (
@Мамаич, плиз добей фубар, ну очень не хватает. Спс!
I have an ancient modded foobar2k v.0.9.5 build called foodora. Default UI is not working, choosing "add folder" immediately crashes loader, "add files" just freezes like on screenshot.
Attachments
HexChat for the most part works (it can't seem to be able to save the config, and the working directory is wrong on launch, also the text box for chat doesn't seem to be blocking keystrokes [up, tab, etc...] properly)
mIRC launched and connected then promptly crashed when trying to load the channel list gui.
Edit: If I remove all the channels at the top of mirc.ini mIRC loads, but it seems to have some redrawing issues. The main textbox never updates.
mIRC launched and connected then promptly crashed when trying to load the channel list gui.
Edit: If I remove all the channels at the top of mirc.ini mIRC loads, but it seems to have some redrawing issues. The main textbox never updates.
Last edited:
Mamaich (or other Guru), explain me please, should I use portable version of x86 programs or installable versions (.exe, .msi) with full installation process in your author's application? Tablet (ASUS TF600) is used by my wife. She wants native agent.mail.ru and 2Gis (not online versions!!!), but stupid mail.ru & Gis stuff didn't release versions of those programs for WinRT, as they promissed ((( So, I forced to find the way, to make agent.mail.ru & 2Gis run in WinRT. The solution I see is to run those programs in desktop mode using your author's application. But I don't know what variant of x86 soft do I need - portable or installable...
There's a store app for mail.ru, at least I think, that ICQ by mail.ru should support it. 2gis is not working, I tried it. Also, you may try recompiled Miranda IM client - there's a plugin for mail.ru.
Not so easy ))) Yes, there is mail.ru store app, but its simple post programm to read/write letters without internet-paging funtion. I have letters from mail.ru team with promisses to create mail.ru agent (MRIM-protocol pager) for Win RT and Metro. They lied ((( Same with 2Gis. My wife used to work with mail.agent and 2Gis. She don't want to use on-line versions and some surrogates like miranda or yandex.map. So, I forced to find the way to make those apps to work in WinRT )))
Well, too bad for you, because 2gis is not working with "Can't reserve memory (file is too big or invalid format)" error, and I haven't tried mail.ru client, because I don't use it. WinRT apps like 2gis and mail.ru aren't happening any time soon - 2gis team has been promising an app for wp7 for like, more then a year now, and guess what? There's still no app. It's because people in russia seem to ignore whole wp and winrt platforms, why should developers care then? Best you can get now is 2gis online/yandex maps online, and something like miranda/IM+ for mail.ru. You may try to install it, though, but I'm pretty sure it won't work.
So, but what about not to install, but use portable versions of desired programs? Does Mamaich's application work with portable versions of x86 programs?
Here is an idea. Your the one with a windows RT device and copies of the software. Why dont you try it yourself....
Not this question again...
Just use office for windows RT. Office 2010 will not run on the surface under x86 emulation, too slow.
m00nlighter
Senior Member
Guess it's about time to add "Office 2010/2013 is not supported " to the first post on this topic, along with your excellent explanation on why Office emulation is not viable.
Or possibly just "yo, this forum has a search feature; use it before posting!"
Honestly, I think this type of post does more damage than good.
1. You're getting annoyed because the person didn't search
2. The person didn't actually get a helpful response
3. They probably still won't search anyway, they'll ask again soon enough
Just answer the person, as m00nlighter suggested adding it to the first post, and simply point people there.
Search isn't perfect, and it can be a REAL pain. I know that from experience.
The forum search isn't great, but it works well enough (I use it quite often). You can use Google or Bing or whatever you prefer well enough as well; for example the query
would have found previous references (although in this particular case, the forum search for this thread works perfectly). The hope is that people will learn and save us all themselves included, some time. Re-posting it will just get their post reported (arguably it already should be; "Search before posting" is, no joke, the #1 item on the prominently listed Forum Rules!)
Back on topic: Hey, Irfanview works now! The installer doesn't (it appears to run but fails to actually do anything even when the launcher is run as Admin), but the program itself (copied from an x86 PC) runs pretty well. Only major caveat: it will hang permanently if trying to view a larger-than-desktop image with "Fit only large images to desktop" mode selected. Not sure what's up with that; there's no clear error I can report.
Code:
office "x86 apps on WinRT" site:xda-developers.comBack on topic: Hey, Irfanview works now! The installer doesn't (it appears to run but fails to actually do anything even when the launcher is run as Admin), but the program itself (copied from an x86 PC) runs pretty well. Only major caveat: it will hang permanently if trying to view a larger-than-desktop image with "Fit only large images to desktop" mode selected. Not sure what's up with that; there's no clear error I can report.
Here's some food for thought.
I've been trying to get Dropbox working via the x86 emulator, and after adding the missing DLLs to the x86 emulator's library, I noticed the following runtime errors
R6034 - An application has made an attempt to load the C runtime library incorrectly
R6016 - not enough space for thread data
Just thought i'd throw it out there for anyone who knows more about this and considers diving deeper for compatibility to allow offline syncing on RT
for the record, if you try to run the Dropbox installer, it will also unpack and such but nothing happens after that.
I've been trying to get Dropbox working via the x86 emulator, and after adding the missing DLLs to the x86 emulator's library, I noticed the following runtime errors
R6034 - An application has made an attempt to load the C runtime library incorrectly
R6016 - not enough space for thread data
Just thought i'd throw it out there for anyone who knows more about this and considers diving deeper for compatibility to allow offline syncing on RT
for the record, if you try to run the Dropbox installer, it will also unpack and such but nothing happens after that.
Last edited:
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
96The project is abandoned.
As I no longer own a Windows RT device and I'm not willing to use Windows RT anymore, unless Microsoft would make it more open (at least to run your own desktop apps) - I've decided to stop working on this project.
As usual I'm publishing complete sources of this tool. Feel free to use them in your own projects or to continue developing this one - only leave my copyrights somewhere.
Don't ask me how to build the sources or to explain anything in them. Figure that out yourself.
The project is abandoned. Sorry.
I'm presenting a tool that allows running a set of x86 Windows applications on Windows RT (ARM) tablets. Its goal is to support all apps except for those that:
- require much CPU power,
- use complex features that were cut out from WinRT like D3D9 extensions or OpenGL,
- require drivers or specific services,
- make heavy use of COM interfaces,
- use undocumented windows internals,
- apps that use .NET framework,
- x86 Metro apps,
- 16 or 64 bit Windows programs,
- buggy apps that require special workarounds.
The tool is currently on a beta stage, so don't expect much from it. It is far from being complete, but at least it runs something.
Current version: 0.061
Just a minor update. The project is not dead, I just had no time to continue the development.
Attached the fixed ntdll.nt.dll that works under Windows RT 8.1 (Microsoft removed some NTDLL exports, so I had to add more stubs). This fix is not needed on RT 8.0.
To install it: extract the attached 0.061-ntdll.nt.dll.zip to c:\x86node\windows\SystemNT\ overwriting the existing file.
Autostarting x86 programs does not work on RT 8.1 ("can't install CreateProcessInternal hook"). I'll look on this later.
Don't ask on jailbreaking the 8.1 beta in this thread - there is a good progress on it, more info would be on release (in october or when WZOR would leak the RTM).
Current version: 0.06
Seems that archive is too big to be attached, so I've uploaded it to google drive and here
Installation: extract the archive on your unlocked Windows RT device, run the MSI file and follow the instructions.
Note: Uninstall the previous version before installing a new one.
List of compatible apps is in this post: http://xdaforums.com/showthread.php?p=40924456
Trademarks
Windows is a registered trademark of Microsoft Corporation. ReactOS is a registered trademark or a trademark of ReactOS Foundation. All other trademarks are the property of their respective owners.
Disclaimer
This software is provided "as is". Use it on your own risk. I make no warranties as to performance, merchantability, fitness for a particular purpose, or any other warranties whether expressed or implied. No oral or electronic communication with me shall create a warranty of any kind. Under no circumstances should I be liable for direct, indirect, special, incidental, or consequential damages resulting from the use, misuse, or inability to use this software, even if I has been advised of the possibility of such damages.
I'm trying my best to make the software working, but I can't guarantee that it is free from defects.
All beta versions of this tool would be freeware. You may freely use it for your own, embed it into your tool, but you can't use it commercially without my confirmation. You can disassemble, analyze or modify this tool for yourself - later I'll provide SDK and document its internals. The only thing that is prohibited is changing embedded copyright notices. I reserve the right of making the project commercial, but this does not mean that this would ever happen.
This software contains unmodified binaries from the ReactOS project: a registry editor, cmd.exe, ole32.dll to name the few. Those binaries are left unmodified and are covered by LGPL license. Future versions may contain redistributable binaries provided by Microsoft and/or other companies.
Some more information may be found in my blog. If you want to support development - use the link or press the button on the left side of the post.11Changes:
15 may 2013: DInput and DInput8 changes for Fallout2 keyboard compatibility.
12 may 2013: A minor update. Fallout 2 now works, tested on Russian version from 1C.
01 may 2013: Added the ability to automatically launch x86 applications. Added the shell32 interfaces - so that installers now work (at least NSIS and InstallShield installers are known to be working).
05 apr 2013: Fixed a few bugs.
04 apr 2013: Uploaded a new build after a long delay. Now emulator supports 256-color modes. But due to a limitation on an updated Nvidia driver - 640x480 and 800x600 display modes are no longer supported on Windows RT. You'll see the black lines to the right and bottom of the screen if the program tries to set such mode.
25 feb 2013: The tool now outputs its version to log. Now one x86 program may launch another - so some of the installers and, for example, 7Z GUI frontend can now run under emulation. Added ~80 DLLs. Some of them are stubs (like D3D9.DLL), others are mostly untested. I have not done all that I've planned for this build, publishing it just as an update to show that the work is going on. Do not expect it to run much more than the previous build.
13 feb 2013: more informative errors from launcher. Emulator now supports program paths with spaces. EXE files with relocations are now processed correctly. Some bugfixes in kernel32 and advapi32.
11 feb 2013: fixed a typo in winmm.dll emulation, now pinball has sound. Also updated the launcher.
10 feb 2013: now the program reached the beta stage.
Known problems
No D3D and most of COM interfaces. Lots of programs would crash, don't run or have different issues.
Notes:
The program keeps its settings in the HKCU\Software\x86node\Settings registry key. Supported REG_SZ (string) values are:
DosboxCore: "dynamic", "simple" or "normal". Dynamic is the default as it is the fastest, but the most buggy core.
LogFile: path to the log file. If not present - log file is %temp%\win86emu.log
Supported REG_DWORD values:
LogLevel: 0=no log (default), 4=max logging
added 13 feb 2013: now default log level is 2: warnings+errors, so you don't need to edit registry
There are several compatibility hacks that may be useful. Compatibility settings are stored in HKCU\Software\x86node\Compatibility\[filename.exe] key. "filename.exe" - a name of the emulated EXE file without path. All values are DWORD:
SetProcessAffinityMask = bitmask. Specify which CPUs to use for running a program, read SetProcessAffinityMask description in MSDN. 0 or unset == run on all cores.
NoRaiseException = 1. RaiseException would just return. Now exceptions are emulated correctly, so this hack is no longer needed.
UseDirectRegistry = 1. Do not redirect emulated registry keys to HKCU\Software\x86node. Be careful when using it.
MaxProcessorFeaturePresent = max processor feature number that is "supported". See the IsProcessorFeaturePresent function in MSDN. All requests for the value above specified would return 0. Default: 0 (IsProcessorFeaturePresent always returns 0).
SimulateAdminRights = 1. Lie to installers that call OpenSCManager function to determine that it is running as administrator, allowing these programs to run without elevation. Redirect the "common start menu" and similar folders to the per-user folders.
You can fake the OS version to a running program. Default XP SP3:
OSVersionLo=dword:00000001
OSVersionHi=dword:00000005
OSVersionBuild=dword:00000a28
OSServicepackLo=dword:00000000
OSServicepackHi=dword:00000003
Some information on the project internals may appear in my blog: http://mamaich-eng.blogspot.ru, but this thread on XDA would be the main discussion place.3
It is better to port free download manager as is is opensource.
FDM may be compatible with some of the future versions, but there would be no internet explorer integration. I'm not going to support all those COM interfaces, at least in the foreseeable future.
I'll pause publishing updates for some time as I'm adding several dozens of new system DLLs to the emulator, and need to make them working before making them public. Ws2_32, msimg32 and other requested DLLs are among them. uTorrent 2.x is working now, though with some problems.
You may see it on the Screenshot
NSIS installers are working too (checked with 7Zip official installer), though they can't create shortcuts as I have not implemented that interface yet.3
Not exactly a port, it is a clean remake based on the old ideas.
The idea is very simple:
- a PE file loader (load files, process relocs, run TLS callbacks in an emulation mode). Support import loops (DLL A imports B while B imports A), ordinals, etc.
- a set of wrapper x86 DLLs (kernel32_stub.dll and so on) that "look like" the corresponding Win API functions for an emulated program:
- a 32-bit x86 emulation engine (currently 2 engines: from bochs and from dosbox, planning on adding my own) that intercepts the command "in eax,0xe5", determines which API is needed by a program and passes it to a handler.Code:#define DEFINE_FUNC1(name) \ static const ModuleDef str_##name={DLL_NAME,#name}; \ EXTERN_C DW STUB_EXPORT stub_##name(DW p1) \ { \ DW *p=&p1; \ __asm { mov eax,p } \ __asm { jmp f1 } \ __asm { mov eax,offset str_##name } \ f1: __asm { in eax,0xe5 } \ __asm { mov p,eax } \ return (DW)p; \ } ..... #define DEFINE_FUNC3(name) \ static const ModuleDef str_##name={DLL_NAME,#name}; \ EXTERN_C DW STUB_EXPORT stub_##name(DW p1,DW p2,DW p3) \ { \ DW *p=&p1; \ __asm { mov eax,p } \ __asm { jmp f1 } \ __asm { mov eax,offset str_##name } \ f1: __asm { in eax,0xe5 } \ __asm { mov p,eax } \ return (DW)p; \ } .... DEFINE_FUNC1(AddAtomA) DEFINE_FUNC1(AddAtomW) DEFINE_FUNC7(CreateFileA) -- number in macro == number of parameters to a __stdcall WinAPI function. Compiler automatically generates "ret N*4" at the end of such function. I've decided to use such c+asm approach instead of making a tiny assebler stub, as I can easily implement some of such functions in C directly in a stub DLL plus it simplifies debugging. And the functions have a usual C prologue/epilogue, so that the emulated program may even patch them in runtime, for example for hooks. ...
- native (arm) API handler DLLs (kernel32_yact.dll and so on). They are mostly autogenerated too:
Some of the functions require complex emulation due to their absence in ARM or due to the callbacks to x86 code:Code:#define DEFINE_FUNC1(name) \ EXTERN_C DW STUB_IMPORT name(DW); \ -- this behaves like a function prototype to compiler EXTERN_C DW STUB_EXPORT yact_##name(DW *R) \ -- R - pointer to the x86 stack { \ DW r=name(p1); \ // call the func passing it paramers from the emulated stack, p1==R[0], p2==R[1] and so on LEAVE(1); \ // empty macro, as the stack is unwinded in x86 stub DLL now return r; \ } ... #define DEFINE_FUNC3(name) \ EXTERN_C DW STUB_IMPORT name(DW,DW,DW); \ EXTERN_C DW STUB_EXPORT yact_##name(DW *R) \ { \ DW r=name(p1,p2,p3); \ LEAVE(3); \ return r; \ } ... DEFINE_FUNC1(AddAtomA) DEFINE_FUNC1(AddAtomW) DEFINE_FUNC7(CreateFileA) // as you see - implementation part is identical to an x86 stub, so I can use the same stub-generator tool
Some of the COM interfaces are already implemented, for example DirectDraw and DirectSound, though not heavily debugged. On a desktop emulator build I can already run "Heroes of might and magic 3" and old WinRAR, but there are several RT-specific OS limitations I need to bypass before making them run on ARM. Current work in progress is: overcoming the RT limitations, manually implementing the API functions that callback to a program code (like CreateThread, RegisterClassA and so on), adding stubs for other system DLLs/COM objects.Code:static DWORD WINAPI ThreadProc( LPVOID lpParameter // [0] == orig func, [1] == orig param ) { __EXCEPTION_REGISTRATION_RECORD R; DWORD *Parm=(DWORD*)lpParameter; DWORD *TEB=(DWORD*)PeLdrGetCurrentTeb(); R.Next=(__EXCEPTION_REGISTRATION_RECORD*)-1; R.Handler=(void*)CbReturnToHost(); TEB[0]=(DWORD)&R; // in case of unhandled exception - just return PeLdrNotifyNewThread(NULL,DLL_THREAD_ATTACH); DWORD Ret=EmuExecute(Parm[0],1,Parm[1]); // 1 == number of parameters to the emulated function delete Parm; return Ret; } EXTERN_C DW STUB_EXPORT yact_CreateThread(DW *R) { DWORD* Parm=new DWORD[2]; Parm[0]=p3; // TODO: no out-of-memory checking for now Parm[1]=p4; DWORD StackSize=p2; if(StackSize) StackSize+=1024*1024; // I reserve some space for my own needs (debugging) else StackSize=2*1024*1024; // TODO: I don't support autogrow stacks, so reserve 2 Mb DWORD t=(DWORD)CreateThread((LPSECURITY_ATTRIBUTES)p1,StackSize,ThreadProc,Parm,p5,(LPDWORD)p6); LEAVE(6); return t; }
Manually thrown SEH exceptions are fully supported, but access violation, int3 and similar OS-generated exceptions would cause program to crash. Some of the TEB fields (TLS and the fields required by the Borland compilers) are implemented too.
I don't make pointer translation in an emulated code nor make parameter checks passed to API. As a side-effect - the emulated program may trash the emulator in memory, but this greatly increases speed.
Most of the x86 EXE files don't contain relocations section and need to be loaded on the specific addresses (typically 0x400000). This is not a problem on a desktop, as I can rebase my emulator's EXE to any address I need, and free the corresponding RAM addrs for emulated program, but on ARM - this is a main problem. So currently only EXEs with relocs are supported for emulation, but there are ways to overcome this problem. And some EXEs produced by old Borland compilers contain "broken" relocs, this is a small problem too.
