ok, so ive done forum stuff, google stuff, linux chat room stuff an no wine still. can someone walk a newb through wine on puppy 3.01.
i have installed wine-0.9.58.pet and it says its installed succesfully but still get bash: wine: command not found.
A side note - how do i become root, the password is woof i believe but terminal wont accept root????
How to get Wine working in Puppy 3.01?
Actually the "wine" command is somewhat important if you have not installed MU's Rox mime types dot pup package (see the wine page on the wiki at puppylinux.org. I am not sure why you are getting that error though. You should get some kind of message telling you how to properly use the command (a usage message), as the proper way to use the wine command is to follow it with a space and then the location of the Win$ exe file you with to execute. The location specified needs to be in Win$ format of course, such as C:\\Program\ Files\\YourDirectory\\YourApplication.exe The C: references the /root/.wine/drive_c directory and the reason for the extra back slashes is to escape either a space or a backslash.
I have run the exact same wine package in puppy 301 using the instructions on the wine page at the puppylinux.org wiki only subsituting the much newer dot pet that you apparently already have. Basically it sounds like you have not configured wine yet and, so it is not working. You will either need to run the configuration tool or use MUs dot pup (see wiki) to get a working configuration. I suggest the latter as it is the simplest way. Short of that Muppy and mini-muppy both have wine preconfigured. Good luck.
I have run the exact same wine package in puppy 301 using the instructions on the wine page at the puppylinux.org wiki only subsituting the much newer dot pet that you apparently already have. Basically it sounds like you have not configured wine yet and, so it is not working. You will either need to run the configuration tool or use MUs dot pup (see wiki) to get a working configuration. I suggest the latter as it is the simplest way. Short of that Muppy and mini-muppy both have wine preconfigured. Good luck.
-
n1n31nchn41l5
- Posts: 107
- Joined: Fri 21 Mar 2008, 07:53
-
Béèm
- Posts: 11763
- Joined: Wed 22 Nov 2006, 00:47
- Location: Brussels IBM Thinkpad R40, 256MB, 20GB, WiFi ipw2100. Frugal Lin'N'Win
You could type sh winecfg but it's not normal if wine is properly installed.
You could try to search on wine with pfind and see where if and where wine is installed.
Is it indicated in the package manager that wine is installed?
(the right pane)
You could try to search on wine with pfind and see where if and where wine is installed.
Is it indicated in the package manager that wine is installed?
(the right pane)
Time savers:
Find packages in a snap and install using Puppy Package Manager (Menu).
Consult Wikka
Use peppyy's puppysearch
Find packages in a snap and install using Puppy Package Manager (Menu).
Consult Wikka
Use peppyy's puppysearch
Hi n1n31nchn41l5,
I don't know if this is your problem, but when I downloaded the wine version 0.9.58 .pet I too got "command not found" when I typed either wine or winecfg in a terminal.
Turned out that although petget told me wine had installed OK, the file I got when I downloaded wine was in fact about half the size it should have been.
To check a downloaded file...
... in rox navigate to where your downloaded file is, then right-click on some white space in the window and select "Window" then "Terminal here". Then type "md5sum wine-0.9.58.pet" (without the quotes) and see if the number you get, agrees with the published md5 that should be present where you got the wine .pet from. If it does, your download is fine. If it doesn't, your download is faulty *or* the file stored on the server you downloaded from, is faulty.
I tried downloading this wine .pet a number of times and from a number of different places, before I finally got a download that checked out OK. That one then installed properly in the Puppy that I am currently using - Fire Hydrant 3.01c FH_Jwm3.01c
I've found that many of my recent problems have been caused by faulty files/downloads. As a result I now routinely check the md5 before I install anything new.
Hope this helps.
All the best,
MrToad
I don't know if this is your problem, but when I downloaded the wine version 0.9.58 .pet I too got "command not found" when I typed either wine or winecfg in a terminal.
Turned out that although petget told me wine had installed OK, the file I got when I downloaded wine was in fact about half the size it should have been.
To check a downloaded file...
... in rox navigate to where your downloaded file is, then right-click on some white space in the window and select "Window" then "Terminal here". Then type "md5sum wine-0.9.58.pet" (without the quotes) and see if the number you get, agrees with the published md5 that should be present where you got the wine .pet from. If it does, your download is fine. If it doesn't, your download is faulty *or* the file stored on the server you downloaded from, is faulty.
I tried downloading this wine .pet a number of times and from a number of different places, before I finally got a download that checked out OK. That one then installed properly in the Puppy that I am currently using - Fire Hydrant 3.01c FH_Jwm3.01c
I've found that many of my recent problems have been caused by faulty files/downloads. As a result I now routinely check the md5 before I install anything new.
Hope this helps.
All the best,
MrToad
-
n1n31nchn41l5
- Posts: 107
- Joined: Fri 21 Mar 2008, 07:53
YES ITS LISTED IN the right pane of the package managerBéèm wrote:You could type sh winecfg but it's not normal if wine is properly installed.
You could try to search on wine with pfind and see where if and where wine is installed.
Is it indicated in the package manager that wine is installed?
(the right pane)
and as far as i can tell its all there mr toad
-
n1n31nchn41l5
- Posts: 107
- Joined: Fri 21 Mar 2008, 07:53
-
n1n31nchn41l5
- Posts: 107
- Joined: Fri 21 Mar 2008, 07:53
MrToad wrote:Hi n1n31nchn41l5,
Interesting. That's completely different to the md5 that I get with the wine-0.9.58.pet that I have.
Where did you get your wine .pet from, and what md5 was listed there for you to compare with what you get when you do the md5sum instruction?
MrToad
since im so new and bad at this mr toad can u give me the link to where u got yours. I'll delete mine and then download the same one u have and install it. We know yours works so hopefully it will here also????
Hi again, n1n31nchn41l5, sorry about the delay - a time-zone thing I expect. Here in the UK I last posted very late at night then went to bed!
OK, here's exactly what I just did on my spare Fire Hydrant 3.01 Puppy box that did not have wine installed on it - so first I suggest that you start the Puppy package manager (in the Setup sub-menu that's in the main menu) and uninstall your current wine .pet before carrying on:
I got my wine-0.9.58.pet from here:
http://www.esnips.com/doc/4aed0e47-973e ... ine-0.9.58
Save the file. Don't run it yet.
I then did md5sum wine-0.9.58.pet to get the md5 number.
(Navigate to where you saved the file, right-click in the white-space in the window, select Window then Terminal here, then do that command)
My result was
7cf3365d03e8b77fa5d765d2522a26be wine-0.9.58.pet
If you do the same, and get the same number, we're doing OK so far.
Next, you need the opengl .pet from here:
http://www.murga-linux.com/puppy/viewtopic.php?t=26717
As you are using Puppy 3.01, select the opengl for puppy 3 and download the file.
Runing the md5sum command on the file gave me:
64b36953b98c3c5da5b02d73e1d77d9c xorg_OPENGL-7.2.pet
(Note the capital letters. Case is important in Linux. Some of us refugees from MS Windows sometimes forget this...)
If you do the same, and get the same number, we're still doing OK.
Now click on the wine .pet and wait until it has finished installing.
Now click on the opengl .pet and wait until it has finished installing.
On my (well, ttuuxxx's actually, but it's running on my box - thanks ttuuxxx!) Fire Hydrant version of Puppy 3.01 I got a message telling me it wanted to uninstall "" - which I don't understand but which I got on on my other Fire Hydrant as well and it didn't seem to break anything so I ignored it and carried on.
Next I rebooted just to clear out any odd bits of code. Suggest you do the same.
Open a terminal and type winecfg - you'll get lots of messages scrolling past, including some that might worry you. Don't worry. After a few seconds the wine configuration GUI should come up.
At this point I closed down the wine configuration GUI and found an MS Windows program - a simple one. Notepad.exe is good. I right-clicked on this program and selected File then Set Run Action. Where it says Enter shell command, insert the word wine then a space, and click on Use Command. Now try clicking once on your MS Windows program and see what happens...
Hope it works OK for you.
A few comments: why didn't I just take the wine .pet from the page I got the opengl file from? Because I just repeated *exactly* the procedure I did before, using the same .pet as I did last time, as you requested: a known good one. I might do a reinstall using that other wine .pet (just out of curiosity) but I wanted to get this to you as soon as possible as I know what it's like to spend hours fiddling and getting nowhere. Why did I install the wine .pet before the opengl .pet and not the other way round? Same reason.
For your interest, I just compared the md5's on today's fresh set of downloads with the md5's of the downloads I had left on my other machine after last week's wine installation, and they are the same.
Best wishes,
MrToad
OK, here's exactly what I just did on my spare Fire Hydrant 3.01 Puppy box that did not have wine installed on it - so first I suggest that you start the Puppy package manager (in the Setup sub-menu that's in the main menu) and uninstall your current wine .pet before carrying on:
I got my wine-0.9.58.pet from here:
http://www.esnips.com/doc/4aed0e47-973e ... ine-0.9.58
Save the file. Don't run it yet.
I then did md5sum wine-0.9.58.pet to get the md5 number.
(Navigate to where you saved the file, right-click in the white-space in the window, select Window then Terminal here, then do that command)
My result was
7cf3365d03e8b77fa5d765d2522a26be wine-0.9.58.pet
If you do the same, and get the same number, we're doing OK so far.
Next, you need the opengl .pet from here:
http://www.murga-linux.com/puppy/viewtopic.php?t=26717
As you are using Puppy 3.01, select the opengl for puppy 3 and download the file.
Runing the md5sum command on the file gave me:
64b36953b98c3c5da5b02d73e1d77d9c xorg_OPENGL-7.2.pet
(Note the capital letters. Case is important in Linux. Some of us refugees from MS Windows sometimes forget this...)
If you do the same, and get the same number, we're still doing OK.
Now click on the wine .pet and wait until it has finished installing.
Now click on the opengl .pet and wait until it has finished installing.
On my (well, ttuuxxx's actually, but it's running on my box - thanks ttuuxxx!) Fire Hydrant version of Puppy 3.01 I got a message telling me it wanted to uninstall "" - which I don't understand but which I got on on my other Fire Hydrant as well and it didn't seem to break anything so I ignored it and carried on.
Next I rebooted just to clear out any odd bits of code. Suggest you do the same.
Open a terminal and type winecfg - you'll get lots of messages scrolling past, including some that might worry you. Don't worry. After a few seconds the wine configuration GUI should come up.
At this point I closed down the wine configuration GUI and found an MS Windows program - a simple one. Notepad.exe is good. I right-clicked on this program and selected File then Set Run Action. Where it says Enter shell command, insert the word wine then a space, and click on Use Command. Now try clicking once on your MS Windows program and see what happens...
Hope it works OK for you.
A few comments: why didn't I just take the wine .pet from the page I got the opengl file from? Because I just repeated *exactly* the procedure I did before, using the same .pet as I did last time, as you requested: a known good one. I might do a reinstall using that other wine .pet (just out of curiosity) but I wanted to get this to you as soon as possible as I know what it's like to spend hours fiddling and getting nowhere. Why did I install the wine .pet before the opengl .pet and not the other way round? Same reason.
For your interest, I just compared the md5's on today's fresh set of downloads with the md5's of the downloads I had left on my other machine after last week's wine installation, and they are the same.
Best wishes,
MrToad
Hi again n1n31nchn41l5,
Hey, regarding what you said about yourself in your last post, even the experts were new to all this once! I'm still not much more than a noob myself - I reckon I deserve an award for being bad at stuff! - so I'm grateful for the patience of the folks on this forum. If you stick around for a while I'm sure that you too will soon find that they're a friendly and helpful bunch, and an integral part of what makes Puppy so much fun. Anyway, prompted by your posts and my own early odd results, I've been playing around a bit with wine .pets and thought you might find this of interest...
I took my spare PC and cleared off my Fire Hydrant Puppy from it (copied the files to a USB memory stick and then deleted them off my hard disk - Puppy makes backups/reinstallations easy!)
Then I put Barry's standard Puppy 3.01 on this spare PC.
Then I downloaded BOTH the wine-0.9.58.pet and the opengl .pet for Puppy 3, from the first post on:
http://www.murga-linux.com/puppy/viewtopic.php?t=26717
When I did the md5sum command on the wine .pet I just downloaded, I got this:
655edf30085677349de1a9f9a0c203ad wine-0.9.58.pet
Which is different from the value given in the md5sum for this file that is linked to from the same page:
ccd305487a7927905ea1256d293a0af6 wine-0.9.58.pet
I believe that this data refers to files at http://puppylinux.ca
I then repeated the wine-0.9.58.pet download. On the new download I got the same md5sum as for the previous download. Repeating this procedure (two separate download attempts) on another machine gave exactly the same md5sum as before. Both times.
Crunch time: on attempting the wine/opengl installation as before, it did not work.
Typing winecfg at a terminal prompt gave me a "not found". Clicking on a MS windows exe (after setting the run action) file did nothing.
Repeating everything from scratch on a fresh Puppy 3.01 - just in case -gave the same (lack of) results.
I next uninstalled wine from the last failed attempt, rebooted, and duplicated the procedure I outlined in my last post, obtaining a fresh wine-0.9.58.pet from the link I posted and getting the same md5sum as per my previous post:
7cf3365d03e8b77fa5d765d2522a26be wine-0.9.58.pet
This time wine worked fine.
It looks as if there may be something wrong with the wine-0.9.58.pet (and the published md5sum?) at http://puppylinux/ca
(To forum moderators: I have emailed the site owner about it, and wonder if in the meantime a warning could be added to the first post at:
http://www.murga-linux.com/puppy/viewtopic.php?t=26717
until somebody a lot brighter than me sorts it out?)
Hope you got your wine working OK n1n31nchn41l5.
MrToad
Hey, regarding what you said about yourself in your last post, even the experts were new to all this once! I'm still not much more than a noob myself - I reckon I deserve an award for being bad at stuff! - so I'm grateful for the patience of the folks on this forum. If you stick around for a while I'm sure that you too will soon find that they're a friendly and helpful bunch, and an integral part of what makes Puppy so much fun. Anyway, prompted by your posts and my own early odd results, I've been playing around a bit with wine .pets and thought you might find this of interest...
I took my spare PC and cleared off my Fire Hydrant Puppy from it (copied the files to a USB memory stick and then deleted them off my hard disk - Puppy makes backups/reinstallations easy!)
Then I put Barry's standard Puppy 3.01 on this spare PC.
Then I downloaded BOTH the wine-0.9.58.pet and the opengl .pet for Puppy 3, from the first post on:
http://www.murga-linux.com/puppy/viewtopic.php?t=26717
When I did the md5sum command on the wine .pet I just downloaded, I got this:
655edf30085677349de1a9f9a0c203ad wine-0.9.58.pet
Which is different from the value given in the md5sum for this file that is linked to from the same page:
ccd305487a7927905ea1256d293a0af6 wine-0.9.58.pet
I believe that this data refers to files at http://puppylinux.ca
I then repeated the wine-0.9.58.pet download. On the new download I got the same md5sum as for the previous download. Repeating this procedure (two separate download attempts) on another machine gave exactly the same md5sum as before. Both times.
Crunch time: on attempting the wine/opengl installation as before, it did not work.
Typing winecfg at a terminal prompt gave me a "not found". Clicking on a MS windows exe (after setting the run action) file did nothing.
Repeating everything from scratch on a fresh Puppy 3.01 - just in case -gave the same (lack of) results.
I next uninstalled wine from the last failed attempt, rebooted, and duplicated the procedure I outlined in my last post, obtaining a fresh wine-0.9.58.pet from the link I posted and getting the same md5sum as per my previous post:
7cf3365d03e8b77fa5d765d2522a26be wine-0.9.58.pet
This time wine worked fine.
It looks as if there may be something wrong with the wine-0.9.58.pet (and the published md5sum?) at http://puppylinux/ca
(To forum moderators: I have emailed the site owner about it, and wonder if in the meantime a warning could be added to the first post at:
http://www.murga-linux.com/puppy/viewtopic.php?t=26717
until somebody a lot brighter than me sorts it out?)
Hope you got your wine working OK n1n31nchn41l5.
MrToad
-
Béèm
- Posts: 11763
- Joined: Wed 22 Nov 2006, 00:47
- Location: Brussels IBM Thinkpad R40, 256MB, 20GB, WiFi ipw2100. Frugal Lin'N'Win
I have the same issue with the download from the post of wolf_pup. The md5 doesn't correspond.
I did the download of the referenced site ESNIPS but there is no md5.txt to download, so a correct verification can't be made.
However I have the same md5 as referenced in Mr Toad's post.
As I prefer a sfs approach I will not install this pet right now.
I did the download of the referenced site ESNIPS but there is no md5.txt to download, so a correct verification can't be made.
However I have the same md5 as referenced in Mr Toad's post.
As I prefer a sfs approach I will not install this pet right now.
Time savers:
Find packages in a snap and install using Puppy Package Manager (Menu).
Consult Wikka
Use peppyy's puppysearch
Find packages in a snap and install using Puppy Package Manager (Menu).
Consult Wikka
Use peppyy's puppysearch
I've re-uploaded wine. The old wine before had a MD5SUM of 655edf30085677349de1a9f9a0c203ad which is strange,the correct MD5SUM is ccd305487a7927905ea1256d293a0af6. I dont know why it was like that, file sizes matched, but the MD5SUM didnt. 
anyway, someone dl it and report back.
anyway, someone dl it and report back.
[img]http://img230.imageshack.us/img230/8595/ubd6467dp2.png[/img]
[url=http://www.tinyurl.com/54tu74]Visit The Repository[/url] - Helpful and hard-to-find treats for Puppy 3.
[url=http://www.tinyurl.com/c5a68f]Click Here for Puppy Support Chat, + Helpful Links.[/url]
[url=http://www.tinyurl.com/54tu74]Visit The Repository[/url] - Helpful and hard-to-find treats for Puppy 3.
[url=http://www.tinyurl.com/c5a68f]Click Here for Puppy Support Chat, + Helpful Links.[/url]
Hi Wolf Pup,
testing now...will report in a few minutes
EDIT: ccd305487a7927905ea1256d293a0af6 wine-0.9.58.pet is correct
Eric
testing now...will report in a few minutes
EDIT: ccd305487a7927905ea1256d293a0af6 wine-0.9.58.pet is correct
Eric
Last edited by Caneri on Mon 14 Apr 2008, 23:00, edited 1 time in total.
[color=darkred][i]Be not afraid to grow slowly, only be afraid of standing still.[/i]
Chinese Proverb[/color]
Chinese Proverb[/color]
md5sum from this link http://puppylinux.ca/bugs/wine-0.9.58.pet
is ccd305487a7927905ea1256d293a0af6 wine-0.9.58.pet
is ccd305487a7927905ea1256d293a0af6 wine-0.9.58.pet
[color=darkred][i]Be not afraid to grow slowly, only be afraid of standing still.[/i]
Chinese Proverb[/color]
Chinese Proverb[/color]
I did find one other issue using the 0.9.5.8 dot pet. When I installed it temporarily needed much almost 50% more space in my pup_save file than the install script checked for. The script still completed and reported that wine installed properly, but wine would not run. When I increased my pup_save file size for another purpose and happened to go back and try wine 0.9.5.8 again It worked fine. This time automatically running the winecfg tool upon successful installation. If you are still having issues after all that Mr.Toad, Wolf Pup, and Beem have contributed you might increase your pup_save file a bit.
-
n1n31nchn41l5
- Posts: 107
- Joined: Fri 21 Mar 2008, 07:53
sorry about the delay in my reply - my puppy got so sick it had to go to the vets to be put to sleep. BUT i was finally able to get a new puppy at the pound and am back in buisness again.
MR TOAD - a very many thanx especially to you for all the effort you have expended to help me out so far. I have got up to the point in your post Mr. Toad where its time to install with the same results you have acheived. But thats where a new problem starts up.
This is what puppy tells me now:
The wine-0.9.58.pet package has been downloaded to /root/.packages,
however there is not enough room to uncompress and install it.
The free space is 27804 blocks but it is estimated you will
need 49584 blocks temporarily for the expansion and install.
Note: If you are using a pup_save.3fs personal storage file,
it can be made bigger -- see Utilities menu.
This script will now delete the package and exit...
I have a 1.25G pup_save file so i dont know what to do. I know there is a .pup file that is a fix for this problem but dont know what it is......
MR TOAD - a very many thanx especially to you for all the effort you have expended to help me out so far. I have got up to the point in your post Mr. Toad where its time to install with the same results you have acheived. But thats where a new problem starts up.
This is what puppy tells me now:
The wine-0.9.58.pet package has been downloaded to /root/.packages,
however there is not enough room to uncompress and install it.
The free space is 27804 blocks but it is estimated you will
need 49584 blocks temporarily for the expansion and install.
Note: If you are using a pup_save.3fs personal storage file,
it can be made bigger -- see Utilities menu.
This script will now delete the package and exit...
I have a 1.25G pup_save file so i dont know what to do. I know there is a .pup file that is a fix for this problem but dont know what it is......
-
Béèm
- Posts: 11763
- Joined: Wed 22 Nov 2006, 00:47
- Location: Brussels IBM Thinkpad R40, 256MB, 20GB, WiFi ipw2100. Frugal Lin'N'Win
Resize personal space is the menu item and that's what you ought to do.
Now the difficulty is to find the value to increase.
The install speaks in blocks and the resize script speaks MB.
I would try 64MB to start with.
Now the difficulty is to find the value to increase.
The install speaks in blocks and the resize script speaks MB.
I would try 64MB to start with.
Time savers:
Find packages in a snap and install using Puppy Package Manager (Menu).
Consult Wikka
Use peppyy's puppysearch
Find packages in a snap and install using Puppy Package Manager (Menu).
Consult Wikka
Use peppyy's puppysearch
I think this will take about another 85mb to get the install completed. Try 64 and then 32 some of the memory used during the install will be made available after the install (only needed during the install). The If my calculations are correct as well as my recollection of this script not accurately calculating the space required. See the post above.