Wine problems

English Applications
#1

Hi,

I’m new to OpenSUSE and need some help with WINE. I have installed it as per the instructions on the OpenSUSE help guide (Wine - openSUSE). When I try and run iTunes setup from a terminal at the root login, using this code:wine /home/louise/Download/itunes64setup.exe

I get this error:

linux-eqln:~ # wine /home/louise/Download/itunes64setup.exe
Trying to load PE image for unsupported architecture (AMD-64)
err:process:create_process starting 64-bit process L"Z:\home\louise\Download\itunes64setup.exe" not supported on this environment
wine: Bad EXE format for Z:\home\louise\Download\itunes64setup.exe

Please help! If anyone has other suggestions for getting iTunes up and running or just syncing an iPhone in OpenSUSE, please let me know.

#2

Hi Louise, and welcome to the forum.

Haven’t tried iTunes myself in WINE, but I believe WINE is 32bit although you can install it on a 64bit openSUSE. I would suggest you need a 32bit version of iTunes to have a chance of running it under WINE.

#3

I agree AFAIK Wine is 32 bit only.

#4

And if you look at the WineHQ - Wine Application Database
iTunes sucks big time

We already know that though:X

Could you run windows in Virtual Box and go that route?

#5

Thanks for all your tips. I did try an iTunes 32bit version and it installed. But the installation does suck… which is mentioned on the Wine forum. I’ll try the virtual machine.

I’m basically trying to sync my iphone. So if there are any other suggestions please send them through.
:wink:

Thanks again.

#6

Louise78 wrote:

>
> Thanks for all your tips. I did try an iTunes 32bit version and it
> installed. But the installation does suck… which is mentioned on the
> Wine forum. I’ll try the virtual machine.
>
> I’m basically trying to sync my iphone. So if there are any other
> suggestions please send them through.
> :wink:

An XP virtual machine did the trick here. You’'l face a couple of nuisances
re. sharing the USB connection but it’s usable.

–
Will Honea

#7

Thanks Will,

I have installed VirtualBox and now get the error:
[INDENT]*Kernel driver not installed (rc=-1908)

The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Re-setup the kernel module by executing

‘/etc/init.d/vboxdrv setup’

as root. Users of Ubuntu, Fedora or Mandriva should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary.*[/INDENT]

Any suggestions?

#8

Virtual Box (Sun Version) Install HowTo - openSUSE Forums

Basically you now need to open a terminal and become su -
and do:

/etc/init.d/vboxdrv setup

#9

Thanks.

This is what I get when I run that command:
linux-eqln:~ # /etc/init.d/vboxdrv setup
Stopping VirtualBox kernel module done
Recompiling VirtualBox kernel module, NOT. It has been packaged.Recompiling VirtualBox netflt kernel module, NOT. It has been packaged. done
Starting VirtualBox kernel module failed
(modprobe vboxdrv failed. Please use ‘dmesg’ to find out why)
linux-eqln:~ #

#10

I posted a guide. Read it.

Please post result of:

rpm --query --all '*kernel*'
#11

Thanks for the other guide, I’m still working my way through it. The result of the command you described is:
kernel-default-2.6.31.12-0.2.1.i586
linux-kernel-headers-2.6.31-3.4.noarch
kernel-desktop-2.6.31.12-0.2.1.i586

#12

See the list of required packages in my guide

  • kernel-source
  • linux-kernel-headers
  • kernel development Eg: kernel-default-devel
  • pam-devel
  • gcc
  • make

Part of your confusion might be you have 2 different kernels

*kernel-default-2.6.31.12-0.2.1.i586
linux-kernel-headers-2.6.31-3.4.noarch
kernel-desktop-2.6.31.12-0.2.1.i586

*You really only need one, I wonder which you are using.
This will tell us

uname -a
#13

Linux linux-eqln 2.6.31.12-0.2-desktop #1 SMP PREEMPT 2010-03-16 21:25:39 +0100 i686 i686 i386 GNU/Linux

#14

So it’s obvious which you are using. When you build VBox to this kernel it will not work if you decided to boot to kernel-default, you would have to build to that kernel also.
I’m not going to start telling you to remove the other kernel because it’ll confuse you.
Try and make sure you have the required packages, reboot, and run the build command again.