So i see this is a popularish topic probably more as 64bit operating systems become more popular. I'm getting overwhelmed and can't figure this out. How can I make it so I can use wine and also wine64? I don't understand the directions it tells me to look at another page for the packages needed...Well I see no needed packages area. Some times it's running 64bit programs directions I find. Basically I first off only care about getting wine itself installed on my 64bit version of slackware 14 lets start there everyone shall we? Thank you. :)

(2) is much more complex and also not yet ready for prime time. Wine64 (wow64) is essentialy a Windows multilib environment. Compile wine as specified: http://wiki.winehq.org/Wine64 and you will still need to convert Slackware64 to multilib, as above. Wine64 is very experimental.

I run Wine32 for various Windows 32 bit games. Personally, I see very little need, other than educational perhaps, to fiddle with Wine64/WoW64. There is really no compelling Windows64 software that doesn't have a perfectly suitable, sometimes better, native Linux alternative.

fatalerror0x00

10-24-2012 09:18 AM

Wine status

Yeah I've decided to find a more linux native way of remoting into my computer rather than going through the trouble of wine when 1. I only need it for one program so far and 2. I'm not comfortable with going through the this whole wine process yet just switching back to linux after years of returning to windows because linux and me couldn't get along for even an hour before I was fed up :P I was rushing things now I'm just gonna try to take this slow I think and wait out on this but please continue to post your opinions and how to do this and I'll read up on it in a few weeks to see if maybe I'm ready for this project :) thanks peeps! :)

business_kid

10-24-2012 10:10 AM

Wine 32bit is established, running, pretty good at what it does, and installs into any system with 32 bit libs available. If you have 64 bit, you'll need Alien Bob's offerings for 32 bit. I usually clone the git, build the latest, and install it somewhere with a $DESTDIR, e.g.
make DESTDIR=/tmp/wine install
Then switch there and make a pkg of it.

As windows is going 64 bit in places, developers kind of reluctantly started into a 64 bit version, There's not much software, there's not a lot of interest, but it's there. Windows and it's software is still mainly 32 bit. Wine64 is there for playing with. Some day down the road, they will merge fully, and you can have a multilib 64/32 bit windows. Right now it's a little better than alpha - it's not 'will it crash' but more 'how will it crash, and will it do anything before it does?'

It is typical really - when everyone had 32 bit PCs there was 16 bit software all over windows. Now we have in the main 64 bit systems, and there's 32 bit software :-//. Maybe we'll have to wait for 128bit cpus before windows goes 64bit.

fatalerror0x00

10-24-2012 10:35 AM

Idk I upgrading to Windows 64 bit as of 7 because I saw a huge increase in sales of 64 bit operating systems around where I live (Maine so this is like wtf you'd expect this in the city) Everything you buy for computers are now 64bit you have to fight to find something in a store thats 32bit anymore (meaning you need to special order it and even then sometimes the store doesn't allow that option) It's really weird that you say that though everything for computers are now 64bit at least around here and I feel that back in XP (I started using XP full out near the end of it's supposed lifespan (vista)) but never stoped using it til 7 cause vista wasn't stable in general and then windows 7 came out successful in 32bit and 64bit it seems. I've actually ran into less issues with 64bit than 32bit which I feel is very rare but maybe because everything i use is made for 64bit systems too. Anyway it's great to hear your opinions :) Thanks business_kid

jtsn

10-24-2012 11:19 AM

Quote:

Originally Posted by business_kid
(Post 4813891)

It is typical really - when everyone had 32 bit PCs there was 16 bit software all over windows. Now we have in the main 64 bit systems, and there's 32 bit software :-//.

There is no problem in having 32 bit software. If it doesn't need the bigger address space, it saves memory and space in the CPU caches. There is even an effort to make it available to x86-64 without using i386 code: https://sites.google.com/site/x32abi/

Quote:

Maybe we'll have to wait for 128bit cpus before windows goes 64bit.

There won't be CPUs with 128 bit addressing. And we already have 128 bit XMM registers, even in legacy mode.

business_kid

10-25-2012 04:05 AM

Quote:

Originally Posted by jtsn
(Post 4813942)

There is no problem in having 32 bit software. If it doesn't need the bigger address space, it saves memory and space in the CPU caches. There is even an effort to make it available to x86-64 without using i386 code: https://sites.google.com/site/x32abi/

Agreed. However, it is legacy code that is really the issue. To find a 64bit core running software with bugfixes for obsolete and buggy 32 bit chipsets, or 16 bit chipsets, and not taking advantage of the best that 64bit cpus can offer is less than ideal. And sure, there are 8, 16, 32, & 64 bit assembler instructions for 64bit cpus, and using less than the full width is often a good idea.

Quote:

Originally Posted by jtsn
(Post 4813942)

There won't be CPUs with 128 bit addressing. And we already have 128 bit XMM registers, even in legacy mode.

That we will see. IIRC, there already are some in existence, but not in PCs. When you've gone as fast as you can, the only way to get more power is to go wider. And yes, a 64 bit cpu should be able to write out 128 bits, in 2 chunks of 64. Every smaller cpu width had that option also. Even the humble 8088 could write a 32 bit number. But this line of conversation is hijacking the topic, so we should not pursue it.

lexish

11-04-2012 11:16 PM

so im brand new to slack ware i went to the alien site n got the gcc n glibc txz packages but when i run upgradepkg it comes back with bad command... so as im brand new to slackware i dunno what im doing wrong. i know this is a newbie question but since im trying to install wine id appreciate the help

allend

11-04-2012 11:23 PM

If you have not had that package installed before then upgradepkg will fail. Either use 'installpkg' or 'upgradepkg --install-new'.

For instance, to install the multilib gcc/glibc, you will use (as root) multilibpkg has below :

Code:

$ multilibpkg --mirror @alienbase.nl-13.37 --install

multilibpkg ver. 1.1.110412 (stable)
(WARNING) You're using multilibpkg in mode --install, while the system is not
(WARNING) in run level 1: current runlevel is (3).

Do you want to continue (Y/N) ? Y
[--install] Started on Mon Nov 5 09:33:50 2012
[--install] Using multilib-mirror http://taper.alienbase.nl/mirrors/people/alien/multilib/13.37
[--install] Local system is Slackware/x86_64 version 13.37.0
[--install] Mirrored multilib dedicated to Slackware/x86_64 version 13.37
[--install] Downloaded packages will be stored into /var/cache/multilibpkg

[--install] 12 package(s) were found (0,062 sec.)

[--install] Downloading 64-bit multilib packages...
....

To install the 32-bit compatibility layer, you will use (as root) compat32pkg as below :

Code:

$ compat32pkg --mirror @Worldwide-13.37 --install layer-32

compat32pkg ver. 1.5.120822 (stable)

[--install] Started on Mon Nov 5 09:40:47 2012
[--install] Using mirror ftp://mirrors.kernel.org/slackware/slackware-13.37
[--install] Local system is Slackware/x86_64 version 13.37.0
[--install] Mirrored system is Slackware/i486 version 13.37
[--install] Slackware-32 packages will be stored into /var/cache/compat32pkg/slackware-32
[--install] compat32 packages will be stored into /var/cache/compat32pkg/compat-32
[--install] Configuration file for "layer-32" : /etc/compat32pkg/multilib-32bit-packages.lst version 1.5.120817
[--install] Trusted external commands : installpkg,upgradepkg,c32pkg-notify-send