Does anyone, who use the WindowsEmulator know where I can find and download all the DLL files so I could have an actual full working windows emulator ?

I'm sick of these video game ROM hacking programs not being executable and crashing on me because some DLL is missing or etc....

So would anyone know where I could find all the DLL files for a fully working W.I.N.E. or am I *** out of luck ? .......... :/

I've only used it just enough to know that most applications don't work to their full potential with it.

Can I just say that how frustrating and ridiculous it is that I have to resort to illegal things like using a DVD CSS de-scrambler just to watch a **** movie on Debian just because Bill Gates is a greedy **** who wants to control the computer market with his mediocre OS and I refuse to use it!

This is BS to the max! Why can't Bill just admit that Ubuntu (even though I dislike that distro) is going to put him out of business and that he can't win against open and free software ?

I mean he can't even touch ReactOS, which has a stolen and copied windows kernel, because none of the libraries are DLL's but named something else entirely... How does Bill Gates like to be ****** over like he did with every business he destroyed?

Edit:I just realized, if you are using Ubuntu, then it might be like Mint, which has winetricks preinstalled, and you can open it from your panel menu.  So check there first, before downloading it. /edit


Open a terminal

Then type "wget http://winetricks.org/winetricks"

After the file is downloaded, type the command "sh winetricks"

It will open a GUI that has a list of things to do, and each of these things will take you, eventually, to a .DLL file you might need.  Or it might not.  But it's worth a shot.

Also, if you have a windows disk lying around, there are some .DLL's which can be copied from the system32 folder in an actual windows installation into your wine system 32 folder in Linux.

This post was last modified: 09-21-2012 11:10 PM by Lang.

Microsoft don't have any control over CSS, nor did they pass the DMCA which makes working around CSS illegal.

While they have abused their status in the past, the whole DeCSS affair is nothing to do with them - the reason DVD playback works in most windows software is simply because the developers could afford to pay for the license - with free software this is not realistic as the license requires a fee per copy at a fixed price, so any free software developer which offered it would be liable for an essentially infinite amount of licensing fees as the software is copied by end users.

mplayer on windows won't play a DVD with CSS either unless you have a means to descramble it.

You do know that Bill Gates is no longer the guy in charge at MS right? He still holds a lot of stock and thus gets dividends, and he has immense wealth from when he was CEO, but these days it's ballmer who makes the decisions as new CEO.

As for winning - while i'd love to see free software become the majority default, that's not realistically going to happen anytime soon and there's a long way to go until linux is a real threat on the desktop to windows. The bigger threat is on mobile devices and serverside - while microsoft does have a decent amount of business on the serverside the biggest installations will run some form of linux or BSD - microsoft can't seem to provide a modern OS that doesn't retain the security and reliability issues that windows is famous for.

Were I to advise microsoft, i'd tell them to go back to the basic WinNT kernel, build BSD and linux ABIs on top of it and support more filesystems, swap the drive-lettering system for a proper VFS with mount points, drop the silly GUI, turn off all services by default and allow existing windows services to run on this new platform.

But by then you've basically just got a crappier unix and it'd make more sense to run a real unix kernel from the start and add windows compatibility to that rather than the other way round.

That's slander, literally. It's also bizarrely inaccurate.

The ReactOS kernel has undergone an audit at great cost to the project in terms of delays just to be sure none of the leaked windows code got into it, it was found clean.

ReactOS is based on lots of original kernel code, some sprinklings of BSD and linux device drivers and other misc bits and pieces and a userland built on original code and modified wine DLLs.

The ReactOS project may not be entirely safe on the patent side of things, but they so far seem legit as regards copyright - and personally i'd be opposed to the project if they were literally copying code from windows for 2 reasons:

1. While i'm ideologically against copyright law, i'm not against prohibiting plagiarism - taking credit for someone else's work
   
2. What would be the point of the ReactOS project if it just had the same crappy microsoft code in it? It'd make it less stable and bring legal risks
   

Not to go off topic Gareth, but how the *** do you view the DLL and .exe source coding ? I've tried with Gedit and had no success but my Dad keeps talking about the times he peeked at the source coding for DLL and .exe files... So I wonder how he did it....

DLLs are compiled code, the source code for DLLs such as the core win32 APIs is not generally available to the public (at least not legally).

You can sometimes decompile them - which means an automated process looks at the machine code and spits out some C/C++ files that are usually only slightly less understandable than the raw machine code in most cases but will implement the same functions.

In general though, decompilation is high black magic and you should treat a compiled binary as a cake - you won't get back eggs and flour from it easily.

Hi all, first post

*eye twitch* this is the opposite of what it stands for. It actually stands for [W]ine [I]s [N]ot (an) Emulator, because it isn't an emulator, it's a compatibility layer. The difference is that an emulator runs the kernel for whatever your emulating, that's why when you download an emulator you always need to get the kernel/bios files from somewhere, and they don't ship with the emulator because they are copyrighted. Wine however is a compatibility layer, meaning it translates all Windows function calls into native Linux ones, it doesn't use the Windows kernel at all (neither does ReactOS, btw).

Doing this would probably cause more harm than good, wine tends to use builtin dlls where possible, and overriding the builtin dlls can often result in breakage. You should only add dlls as and when required.

Unfortunately problems with wine tend to need to be solved on an application specific basis.


If you are having problems the first thing to do is search the Wine AppDB and see if your application has a page, and follow any instructions on that page. The next thing to do is start a fresh wine prefix, run the application with something like "WINEPREFIX=~/.newprefix wine application.exe", this will create a new wine directory called ~/.newprefix, which is clear of any modifications / dlls you may have put in, which can often cause issues, I tend to make a habbit of having a different wine prefix for every application, that way things break less. The other thing to do is run wine --version and compare it with the version at http://winehq.org if you are not running the latest version, upgrade.

If that fails, then ask for help . I can't solve everything but I'll do my best. I'd need the following information to be able to help:

Name of the application you are trying to run, with link to download if possible.
Log of you running it from a terminal
Output from wine --version

I myself run loads of games, etc with wine. It takes a little fiddling, but it does work. With steam porting to Linux later this year hopefully we'll be needing wine less and less, however

This post was last modified: 09-24-2012 03:49 AM by Azelphur.

I have broken wine in this manner before, however if one copies a relatively simple .exe file, like mspaint.exe, or sol.exe, you can copy the required .dll's into the same folder and the application will read those dll's.

Oh, and welcome to AFF

Hi all, first post

marioluvsfries Wrote:

Does anyone, who use the WindowsEmulator

*eye twitch* this is the opposite of what it stands for. It actually stands for [W]ine [I]s [N]ot (an) Emulator, because it isn't an emulator, it's a compatibility layer. The difference is that an emulator runs the kernel for whatever your emulating, that's why when you download an emulator you always need to get the kernel/bios files from somewhere, and they don't ship with the emulator because they are copyrighted. Wine however is a compatibility layer, meaning it translates all Windows function calls into native Linux ones, it doesn't use the Windows kernel at all (neither does ReactOS, btw).

marioluvsfries Wrote:

know where I can find and download all the DLL files so I could have an actual full working windows emulator ?

Doing this would probably cause more harm than good, wine tends to use builtin dlls where possible, and overriding the builtin dlls can often result in breakage. You should only add dlls as and when required.

Unfortunately problems with wine tend to need to be solved on an application specific basis.


If you are having problems the first thing to do is search the Wine AppDB and see if your application has a page, and follow any instructions on that page. The next thing to do is start a fresh wine prefix, run the application with something like "WINEPREFIX=~/.newprefix wine application.exe", this will create a new wine directory called ~/.newprefix, which is clear of any modifications / dlls you may have put in, which can often cause issues, I tend to make a habbit of having a different wine prefix for every application, that way things break less. The other thing to do is run wine --version and compare it with the version at http://winehq.org if you are not running the latest version, upgrade.

If that fails, then ask for help . I can't solve everything but I'll do my best. I'd need the following information to be able to help:

Name of the application you are trying to run, with link to download if possible.
Log of you running it from a terminal
Output from wine --version

I myself run loads of games, etc with wine. It takes a little fiddling, but it does work. With steam porting to Linux later this year hopefully we'll be needing wine less and less, however

A good first post, welcome