Hey this is my first time trying Linux. I installed Ubuntu 9.04 about an hour ago. The reason why I installed was I wanted to play Diablo II. I tried everything and couldn't get the game to run on Vista. So I'm dual boot running Vista and Ubuntu. I wanted the easiest to understand Wine. I didn't want to download the developers version, I wanted the latest stable version. I downloaded wine-1.0.1.tar.bz2 from sourceforge. Is that right, I'm not used to all the linux abbreviations? A year ago I didn't even know what a .iso was.
Follow the instructions here instead http://www.winehq.org/download/deb What you download is the source code which would need compiling.
On Mon, Sep 7, 2009 at 9:25 AM, NewtoLinux<wineforum-user at winehq.org> wrote:> Hey this is my first time trying Linux. I installed Ubuntu 9.04 about an hour ago. The reason why I installed was I wanted to play Diablo II. I tried everything and couldn't get the game to run on Vista. So I'm dual boot running Vista and Ubuntu. I wanted the easiest to understand Wine. I didn't want to download the developers version, I wanted the latest stable version. > > I downloaded wine-1.0.1.tar.bz2 from sourceforge. Is that right, I'm not used to all the linux abbreviations? A year ago I didn't even know what a .iso was.The 1.0.1 is getting old... you should definitely get latest version if possible According to http://wiki.winehq.org/WineReleaseCriteria, wine 1.0 was tagged as being able to run correctly for (at least) the following apps * Photoshop CS2 tryout * Microsoft Powerpoint Viewer 97 and 2003 * Microsoft Word Viewer 97 and 2003 * Microsoft Excel Viewer 97 and 2003 Latest 1.1.* should work better (short of potential regressions); see winehq's download section for more information
Ahhh, I get it I was reading up on Wine and the program basically is always in beta. I've always stayed away from beta testing. I might as well download the latest version from the .deb packages archive page. Wine 1.1.29 i386, -dev This was the link that started this whole experience with me trying Linux: http://appdb.winehq.org/objectManager.php?sClass=version&iId=49 so I'll post more if I don't understand it. How hard is the instructions on the page for a linux noob and Wine noob?
Alright, I was able to install Wine successfully. Now I just got to figure out how it works. Is there an easy application to test it with?
NewtoLinux wrote:> Ahhh, I get it I was reading up on Wine and the program basically is always in beta. I've always stayed away from beta testing. I might as well download the latest version from the .deb packages archive page. > Wine 1.1.29 i386, -dev > > This was the link that started this whole experience with me trying Linux: > http://appdb.winehq.org/objectManager.php?sClass=version&iId=49 > > > so I'll post more if I don't understand it. How hard is the instructions on the page for a linux noob and Wine noob?Some notes you should be aware of: Archives that contain the tar.gz or tar.bz2 extensions (also called tarballs) usually are source archives. This means that you would have to compile the source code yourself into an usable application. Instead, there are .deb archives containing pre-compiled binaries that you can just use. Usually. There are also DEBs that have -dev in their name, these are development packages and pretty much the same as the gz/bz2 tarballs: they only contain the source code. For quick and easy installation of the latest Wine, go here: http://www.winehq.org/download/deb
I think I found one of the books you are referring to. http://oreilly.com/catalog/9780596006280/ Too bad it wasn't at my college's library. It looks old but I doubt a lot of the command line/console stuff hasn't changed.
NewtoLinux wrote:> I think I found one of the books you are referring to. http://oreilly.com/catalog/9780596006280/ > > Too bad it wasn't at my college's library. It looks old but I doubt a lot of the command line/console stuff hasn't changed.You could Google up one or two simple bash tutorials on basic commands. I assumed you knew at least the cd command because it's one of those things similar to DOS and even Windows' command "prompt".
Ok, I did what you said and I googled a few bash tutorials and I got the idea of the cd command. I have the diablo II shortcut on my desktop. So I typed in Code: ls . I saw the Desktop in my directory and type in cd Desktop. Took me a long time to figure out the cd command is case sensitive. I then typed ls again. I Saw in my terminal: Diablo II.Desktop Diablo II - Lord of Destruction.lnk Diablo II - Lord of Destruction.Desktop I then tried Code: wine "Diablo II" and I tried wine "Diablo II.desktop", wine "Diablo II.Desktop", wine "Diablo II.Desktop.exe etc. None of them worked. The terminal printed either bad exe format or Module not found. What gives and what do these error msgs mean?
NewtoLinux wrote:> Ok, I did what you said and I googled a few bash tutorials and I got the idea of the cd command. I have the diablo II shortcut on my desktop. So I typed in > Code: > ls > > . I saw the Desktop in my directory and type in cd Desktop. Took me a long time to figure out the cd command is case sensitive. > > I then typed ls again. I Saw in my terminal: > Diablo II.Desktop > Diablo II - Lord of Destruction.lnk > Diablo II - Lord of Destruction.Desktop > > I then tried > Code: > wine "Diablo II" > > and I tried wine "Diablo II.desktop", wine "Diablo II.Desktop", wine "Diablo II.Desktop.exe etc. None of them worked. The terminal printed either bad exe format or Module not found. What gives and what do these error msgs mean? > >The .desktop items should show as icons on your desktop. Double-click them and Diablo II should start. If you see a popup which states that there was a serious error, then you will have to run the program from the terminal as described in the following FAQ: http://wiki.winehq.org/FAQ#head-3b297df7a5411abe2b8d37fead01a2b8edc21619 And you should post the results back here if you get < 20 lines. Otherwise, capture the results to a logging file: http://wiki.winehq.org/FAQ#head-a37de3282d447376d2220d20a278ae52258551a4 and post the resultant file to a site like pastebin.com and post the URL to the pastebin.com page here. Please understand that we may or may not be able to assist you based upon your prior postings to this volunteer supported forum. James McKenzie
NewtoLinux wrote:> Ok, I did what you said and I googled a few bash tutorials and I got the idea of the cd command. I have the diablo II shortcut on my desktop. So I typed in > Code: > ls > > . I saw the Desktop in my directory and type in cd Desktop. Took me a long time to figure out the cd command is case sensitive. > > I then typed ls again. I Saw in my terminal: > Diablo II.Desktop > Diablo II - Lord of Destruction.lnk > Diablo II - Lord of Destruction.Desktop > > I then tried > Code: > wine "Diablo II" > > and I tried wine "Diablo II.desktop", wine "Diablo II.Desktop", wine "Diablo II.Desktop.exe etc. None of them worked. The terminal printed either bad exe format or Module not found. What gives and what do these error msgs mean?.Desktop files are not .exe files. Wine will not be able to run them. If you installed the game to for example C:\Program files\Diablo, you will have to cd to "~/.wine/drive_c/Program files/Diablo" (including double quotes) and run the exe from there. The ~ means your home directory by the way (/home/username).
What NewToLinux tried should perfectly work though if there was a folder named Program Files
Ok I did the exact same thing I did last time except I typed ls -a before typing cd .wine. This time Code: cd "Program Files" worked. Shrug, I got it to work. On a side note Diablo II now works. Both from terminal and the shortcut on the desktop. I was fooling around with wine's virtual desktop. Apparently Diablo II won't run on my system unless I'm using a virtual desktop. I was running 800x600 resolution. Just tried without virtual desktop and both ways failed. I could post the error msg from the terminal if someone wanted to see. Is there a way to print screen the terminal or copy it and attach it to my msg? I'm going to go fool around with virtual desktop some more.