Program: Wine (Wine Is Not an Windows Emulator)
Site: http://www.winehq.org/
Description: It allows that Windows Apps run on Linux (It works as a compatibility lawyer)
License: GNU Lesser General Public License (http://www.winehq.org/site/license) (Freeware and OpenSource)
Other:
I have a new amazing idea, but first I will explain how it works:
Wine is a compatibility lawyer between the OS (Linux or Mac) and the Apps for Windows.
It also creates a folder that is the virtual hard drive for the Windows Apps.
Now my idea:
Porting Wine to windows would allow installing programs locally on the pen, plus, it would no more need Wine to be installed on Linux for running PAM and PA Apps; becoming really portable.
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
You have a very interesting idea, but I would guess, difficult to accomplish. These guys are getting very good (excellent, really) at porting open source Windows apps to USB portability. Taking even a simple app across OS's is a lot more difficult - and Wine isn't simple!
You are requesting to port wine from linux to windows. Not to make wine portable.
Better suggest this feature at the wine project, but I don`t think the chances are high to implement it.
It`s also possible to run the linux kernel inside windows (colinux + more user friendly forkes). Wine can run inside this posix windows environment. Now just someone need to find time to put this all together.
It is also a solution, but sounds like a very slow one...
"Those people who think they know everything are a great annoyance to those of us who do." Asimov
CoLinux requires admin rights for many reasons.
Vintage!
Wait, it is useless to ask this to the Wine project, because Wine is to run Windows apps in Linux, but porting it to Windows would allow it to run apps in a lawyer, saving all setting on the portable device easily, and that's not the Wine purpose. The original Wine purpose would be useless in Windows.
By the way, who goes to the Wine site will see a download link to the Windows version: that is for developers to replace the original Windows APIs with their own, and not for a full working Wine.
Plus, making Wine portable, ONLY making Wine portable, on Linux, and adding features to the PAM allow that any Portable App run on Linux, instead of porting the Linux version of the apps, having to deal with the "dependency hell".
Blue is everything.
It's easier to make it from scratch via hooking. Wine is an emulation of Windows API functions and as such would not work in Windows. The functions you are thinking of are implemented via hooking through a layer (not lawyer
).
----
Ryan McCue.
Blog.
So all that Airbus-delay trouble over here in Europe is because of YOU!
Simeon.
"If you're not part of the solution, you're part of the precipitate."
API hooking via trampoline ( the most powerful technique, except using a helper process as a debugger, but this option works slowly and isn't that clean ) is not thread safe. But it can be...with own implementation of thread API. Here wine could be useful.
"Those people who think they know everything are a great annoyance to those of us who do." Asimov
I'm fairly sure WINE is written in non-portable (platform portable) code written specifically for Linux.
----
Ryan McCue.
Blog.
So all that Airbus-delay trouble over here in Europe is because of YOU!
Simeon.
"If you're not part of the solution, you're part of the precipitate."
I also think so, that's why I'm not eager to do it. But it could still be better than writing everything from scratch.
"Those people who think they know everything are a great annoyance to those of us who do." Asimov
There are already binaries of wine for windows http://www.winehq.org/site/download Just scroll down and you'll find a windows package for wine
-----------------------------
"I don't fear Computers. I fear the lack of them" Isaac Asimov
your friendly neighbourhood moderator Zach Thibeau
Yep, you're right, it is written portably. But I took a quick look inside and it looks like the project is very solid - a lot of references to other parts, it'd be probably necessary to take whole kernel. And making virtual machine out of it would be probably easier...but it seems to be too much even for 10 people team. (Wine's authors file lists 795, which gives average of c.a. 100 KB of code+documentation+resources / person, the team core is probably much smaller).
"Those people who think they know everything are a great annoyance to those of us who do." Asimov
Ok, forget about the porting Wine to Windows. But, for Linux, its easy to make it portable, in my theory (I don't know any type of programing), because there is no Registry; and there aren't very dependencies. That way, it's easy to run PortableApps on Linux, instead of making the Linux version of PortableApps (making Firefox for Linux Portable, by example) because of the "dependency hell":
for those of you who use Windows, the programs are heavy because they have all what they need for working (becoming the system heavy because of the same "miniapps" repeated for diferent programs); on Linux, there are "the apps", and the "miniapps" that make "the apps" work. On linux, (most of the times) we have a program that treats of that dependencies for us. But for developing a Linux PortableApp it is necessary to download the dependencies and making them portable too. That way I think that is easier making Wine portable (2 dependencies or something) than making X dependencies portable for each app.
That version of Wine for Windows is for developers: it replaces the API's of windows with their own for checking if they work properly (I've read it somewhere on their site).
Oh! And sorry for that error (lawyers, where was I thinking?).
____________________
Portimão's Blogger
Blue is everything.
Anyway, I'm actually working on something at the moment to do just that. It uses a hooking component (undecided at the moment) and Steve's spy_dll.
I'll be sure to post on these forums if/when I finish it.
Oh, and shouldn't that be "what", not "where"
I couldn't understand your post with lawyers, I assumed you were talking about something else.
----
Ryan McCue.
Blog.
Olah, Senior Blobby. Taco, taco, taco, taco, burrito.
By Idiots.
"If you're not part of the solution, you're part of the precipitate."