I installed libva-1.5.1-x86_64-1alien.tgz, OpenAL-1.17.1-x86_64-2alien.txz and wine-1.9.23-x86_64-1alien.txz. But when I try to execute anything (either as user or root) by invoking "wine *.exe" it responds...

# wine Vcc.exe
bash: /usr/bin/wine: No such file or directory

Now Vcc.exe is present...

# ls
IDE.dll Vcc.exe Welcome to Vcc.pdf harddisk.dll orch90.dll
KeyMap.ini Vcc.ini fd502.dll mpi.dll uninstall.exe

and /usr/bin/wine is also available and executable...

# ls -al /usr/bin/wine
-rwxr-xr-x 1 root root 9704 Nov 29 09:35 /usr/bin/wine

So what have I missed? Thanks for any suggestions.

You need multilib to use Eric's wine. Check out his blog post for more information on it.

Thanks for the speedy reply.

Hello ionmich,

This is what i did to get Wine working on my Slackware 14.2 x64 installation.

Quick steps:

1. Read and follow "Enabling multilib" section here: http://www.slackware.com/~alien/multilib/
2. Install Slackpkg+ from: http://slakfinder.org/slackpkg+.html
3. Configure Slackpkg+ by reading man page for slackpkgplus.conf and making suitable changes in slackpkgplus.conf
4. Install the dependencies for AlienBob's Wine package (OpenAL and libva)
5. Install AlienBob's Wine package

Detailed reading:

The Slackware multilib documentation at: http://docs.slackware.com/slackware:multilib

Hope this assists you in getting Wine working!

Regards,
Sattva

1 members found this post helpful.

Thanks for the suggestions. I failed yet again and decided Slackware was not for me. Regrettable as Slackware was one of the first Linux distros I started with years ago. But I use a lot of old and odd software that requires a lot of tweaking that's difficult for me.

Thanks again for your time.

I fail to see how these instructions were too hard to implement?

1 members found this post helpful.

I too had trouble getting wine to work. Then it dawned on me to read the docs and to expand and study the tgz for clues.
Turns out the command I had to use was not but should be LOL, notepad is just an example. I do not have a multilib system

What is the wine emulator? The Wine Is Not an Emulator emulator?

1 members found this post helpful.

its a little work to go multilib and get wine going but its worth it. pretty much have to do the same with any other 64bit system.

1 members found this post helpful.

But many of those systems are either already multilib or will draw in multilib automatically when you try to install a 32bit or multilib program.

Don't get me wrong, I love Slackware and I prefer how it handles multilib, but other distros do simplify the process a bit (at the expense of making it harder for someone to troubleshoot and resolve problems).

1 members found this post helpful.

I think everybody expected multilib to be a temporary thing. There is less need for multilib now than there was in 2009, and so there less incentive for simplifying or integrating it than there was in 2009. And other distros are starting to go 64-bit only.

Let's face it, multilib is an enabling technology for non-free applications where the owners don't give a damn. We're not as snooty as Debian about the non-free aspect, but it still means nobody else can fix and build the applications. And if the owners don't give a damn, it's a bit demotivating...

1 members found this post helpful.

Are you looking for Color Computer 3 specific emulation? Here a few 6809 emulator web sites with software the does run natively on linux -- Coco 1 and 2 for sure, not sure about 3 though or drivewire support:

http://www.6809.org.uk/xroar/
http://www.roug.org/soren/6809/
http://atjs.mbnet.fi/mc6809/

I've built wine using my own packages and had VCC up and running as well on a 64bit multilib setup. Perhaps you can uninstall all the -?alien.tgz packages and built wine yourself?