Due to the wish of pc4ever1 i ported the latest open source Version of Greenshot
I did no testing of bugs at all but it runs on my Surface without errors.
Cut
Related
Zip file of mongod.exe
Build of 2.2.2 source from http://www.mongodb.org/downloads
minor settings tweaks to get it to build.
Usage is per normal windows version of mongodb server.
Notes:
mongo shell builds but fails (issues with javascript interpreter) but mongod.exe does run correctly and handles requests from clients NOT running on the surface correctly (tested with MongoVUE from desktop)
node.js with npm install mongodb running on surface seems to connect to mongodb, but I don't know enough to be able to say it's working correctly or not.
Consider this very experimental.
Interesting article on developing VideoLAN VLC app for Windows 8 (as a modern app)
and the issues getting it to compile / run on RT
http://www.neowin.net/news/intervie...ent-about-the-future-of-the-windows-8-vlc-app
When will the Windows RT version of the app be released?
That's a hard question, and has been a source of confusion, notably because too many people can't make the difference between WinRT and Windows RT. (Note that even Microsoft people are confused about this ) So, to compile VLC for WinRT on x86, we use gcc and MinGW to produce the VLC engine, and we compile the UI (in C#) with Visual Studio. The reason is that VS2013 cannot compile VLC, because of the lack of correct support of C99. To compile VLC for WinRT on ARM, aka Windows RT and Windows Phone, we have only two ways: fix gcc-binutils for Windows on ARM or patch VLC and work-around VS2013 bugs. We're trying both at the moment, but we don't know yet the best way. Once VLC is compiled, the app can be released. I will know more about this before the end of the month.
I keep my fingers crossed for gcc fix - that would allow us to port many apps that we can't compile with Visual Studio.
kitor said:
I keep my fingers crossed for gcc fix - that would allow us to port many apps that we can't compile with Visual Studio.
Click to expand...
Click to collapse
Yessssss please if they get us a version of GCC that compiles for RT that would be fantastic.
How is it going?
Hi,
Are there any more news regarding this development?
Well, the Windows Phone version is in beta, so it seems to reason they must have figured out how to target ARM devices. The Windows 8 store version is still x86 only last I heard...
Hi guys, I just got my surface rt And I was wondering should I keep windows 8.1 or just 8? Is it worth it to jailbreak ? Thanks
There are plenty of threads already on this topic...
Anyhow, IMO Windows RT is nigh-useless without jailbreaking. 8.1 helps a little but it's still pretty bad. On the other hand, the RT hacking scene has lost a lot of steam while waiting for an 8.1 jailbreak to come out, and most of the apps that were ported or created specifically for RT are now obsolete versions, abandoned partially complete, or both. They are still useful, but there's limits.
In any case, it really comes down to your use cases. If you need Outlook, use 8.1. If you want to run DOSBox games, use the jailbreak. If you need the latest and greatest Windows Store apps, use 8.1. If you want to try running the x86 dynamic recompilation layer (one of those incomplete-and-abandoned projects, though it works for some normal Windows apps) use the jailbreak. If you want to run the latest version of IE, use 8.1. If you want to use a mostly-functional WebKit-based browser (i.e. not IE), use the jailbreak.
Or you could try contributing to getting the jailbreak working on 8.1, I guess. That would be the best of both worlds, and would probably jump-start development for RT again.
GoodDayToDie said:
There are plenty of threads already on this topic...
Anyhow, IMO Windows RT is nigh-useless without jailbreaking. 8.1 helps a little but it's still pretty bad. On the other hand, the RT hacking scene has lost a lot of steam while waiting for an 8.1 jailbreak to come out, and most of the apps that were ported or created specifically for RT are now obsolete versions, abandoned partially complete, or both. They are still useful, but there's limits.
In any case, it really comes down to your use cases. If you need Outlook, use 8.1. If you want to run DOSBox games, use the jailbreak. If you need the latest and greatest Windows Store apps, use 8.1. If you want to try running the x86 dynamic recompilation layer (one of those incomplete-and-abandoned projects, though it works for some normal Windows apps) use the jailbreak. If you want to run the latest version of IE, use 8.1. If you want to use a mostly-functional WebKit-based browser (i.e. not IE), use the jailbreak.
Or you could try contributing to getting the jailbreak working on 8.1, I guess. That would be the best of both worlds, and would probably jump-start development for RT again.
Click to expand...
Click to collapse
Okay thanks ! Can I go back to win8 by resetting my rt in settings ?
If you save the 8.0 recover image, yes. I'm not sure whether it's saved under normal upgrade circumstances; I removed mine to free up space. You can also download the 8.0 image and restore it.
It's also possible, though a little complicated, to install 8.0 and 8.1 at the same time, in a dual-boot configuration. Doing so uses a lot of the tablet's internal storage though.
I was curious about this, if the android smartphones/tabs powered x86 intel processors can be used such that we can install desktop windows or other x86 OSes?
Unlikely as we would need to build drivers for the phone which is rather difficult when the manufacturers like to have things on lockdown most of the time, also it would probably brake some strange contract with Microsoft as most things do. Look at the Surface and Surface RT
Also the UI (Even Metro) would struggle to work on the display adapter
So in short no we can't run Windows on x86 Android phones, yet anyway
Install Android in Windows without Virtual box
I tried this product DuOS which will install Android version Jellybean in Windows 7/8/8.1 platforms. This one is very simple for use comparing with Bluestacks and has good performance for applications. Refer the link for further details and installation check the website for amiduos:good:
Hey guys,
I noticed that no one has gotten very far on getting Android (x86/IA) up and running on the SP3. I am here to attempt it, and bring together a collection of resources for those who know more about porting from the Ubuntu Kernel Source Code to the Android Kernel.
I used the Android IA 4.4r-1 Image on USB, and booted to the setup screen, although I was unable to test hardware due to the fact that my Type Cover was not working, the Touchscreen doesn't work, a USB Mouse isn't an option because the USB 3.0 port isn't supported OOB, and Bluetooth isn't testable until after initial setup.
I then tested Android-x86 4.4r1 and used the following instructions to make an installer: http://forum.xda-developers.com/showthread.php?t=2703270
In this version, I got a KP upon efivar loading. I then used Li's modified 4.4 kernel (Post #10 in referenced thread), and booted to the setup screen, same exact situation with unsupported everything.
Here is the link to the Ubuntu Thread:
They have compiled a list of working/non-working in their custom kernel:
]
Work In Progress
Mostly a complilation of links and patches from elsewhere.
Working
•Type Cover 3 (both keyboard and trackpad)
•Bluetooth
•3.13 Trusty kernel: partially working after updating the marvell firmware.
•3.16 Utopic kernel: Works without problems
•Touch screen
•Built-in microphone, speakers, and headphone jack
•Wireless (very unstable so far with both Utopic and Trusty kernels).
Not Working
•Cameras
Untested
•MicroSD reader
•Bluetooth pen
Kernel with Type Cover 3 support (keyboard and touchpad)
https://github.com/rubiojr/surface3-kernel
General information
https://github.com/rubiojr/surface3-ubuntu-trusty
Click to expand...
Click to collapse
Here is info about the modified SP3 kernel: https://github.com/rubiojr/surface3-ubuntu-trusty
Here is the link to the modified Ubuntu Kernel: https://github.com/rubiojr/surface3-kernel
If someone can port the features of this kernel to the Android-IA/x86 Kernel (Either should do, but due to Play Store inclusion, x86 would be preferred), it would be glorious.
On the SP1/2, Android-x86 has support for just about everything except WiFi, Bluetooth, G-Sensors, all OOB/
On the SP1/2, Android-IA has support for everything excluding Bluetooth working (the people who compiled it ported the Linux driver for the WiFi card, and it works great), link found here: http://forum.xda-developers.com/showthread.php?t=2536533