Tiny Core Linux

Tiny Core Extensions => TCE Corepure64 => Topic started by: alexo on March 16, 2019, 05:51:59 AM

Title: wine fails
Post by: alexo on March 16, 2019, 05:51:59 AM

Hi forum,

I'm sorry for my numerous posts but I hope I can improve TC that has taken me so much.
I have a problem launching wine:

this is the output of the console:

Code: [Select]

tc@box:~$ wine
tc@box:~$ fixme:service:scmdatabase_autostart_services Auto-start service L"MountMgr" failed to start: 2
Start a program, or open a document in the program normally used for files
with that suffix.
Usage:
start [options] program_filename [...]
start [options] document_filename

Options:
"title"        Specifies the title of the child windows.
/d directory   Start the program in the specified directory.
/b             Don't create a new console for the program.
/i             Start the program with fresh environment variables.
/min           Start the program minimized.
/max           Start the program maximized.
/low           Start the program in the idle priority class.
/normal        Start the program in the normal priority class.
/high          Start the program in the high priority class.
/realtime      Start the program in the realtime priority class.
/abovenormal   Start the program in the abovenormal priority class.
/belownormal   Start the program in the belownormal priority class.
/node n        Start the program on the specified NUMA node.
/affinity mask Start the program with the specified affinity mask.
/wait          Wait for the started program to finish, then exit with its
exit code.
/unix          Use a Unix filename and start the file like windows
explorer.
/ProgIDOpen    Open a document using the specified progID.
/?             Display this help and exit.
 
Right after having installed it a dialog appeared indicating me that mono library was missing.
I installed mono from apps and put it onboot but wine refuses to start.

thank you for your precious help.

    [EDIT]: Fixed  fixme:  message so it displays correctly.  Rich

Title: Re: wine fails
Post by: Juanito on March 16, 2019, 06:27:36 AM

When you first start wine using the icon, it should propose downloading gecko and mono - go ahead and do this rather than using the mono extension.

Note also that most windows apps are multi-lib, whereas CorePure64 is not.

Title: Re: wine fails
Post by: alexo on March 16, 2019, 08:18:24 AM

Hi Juanito,

I removed the .wine folder, uninstalled the mono.tcz extension and restarted wine. It downloaded mono and Geko but there remains a failure in launching the program.
In my previous post the error message I included was not complete, so here it is again:

Code: [Select]

  tc@box:~$ wine
tc@box:~$ fixme:service:scmdatabase_autostart_services Auto-start service L"MountMgr" failed to start: 2
Start a program, or open a document in the program normally used for files
with that suffix.
Usage:
start [options] program_filename [...]
start [options] document_filename

Options:
"title"        Specifies the title of the child windows.
/d directory   Start the program in the specified directory.
/b             Don't create a new console for the program.
/i             Start the program with fresh environment variables.
/min           Start the program minimized.
/max           Start the program maximized.
/low           Start the program in the idle priority class.
/normal        Start the program in the normal priority class.
/high          Start the program in the high priority class.
/realtime      Start the program in the realtime priority class.
/abovenormal   Start the program in the abovenormal priority class.
/belownormal   Start the program in the belownormal priority class.
/node n        Start the program on the specified NUMA node.
/affinity mask Start the program with the specified affinity mask.
/wait          Wait for the started program to finish, then exit with its
exit code.
/unix          Use a Unix filename and start the file like windows
explorer.
/ProgIDOpen    Open a document using the specified progID.
/?             Display this help and exit.


Quote

Note also that most windows apps are multi-lib, whereas CorePure64 is not.

I'm wondering a thing: from the info file of the wine extension it reads that wine is 64 bit whereas most windows applications are 32 bits. Does this mean I cannot execute a 32 bit application from within CorePure64? And finally what does multi-lib mean?

thank you

    [EDIT]: Fixed  fixme:  message so it displays correctly.  Rich

Title: Re: wine fails
Post by: Juanito on March 16, 2019, 08:27:48 AM

The CorePure64 10.0 version of wine does not contain a file named wine, it is called wine64:

Code: [Select]

$ wine64
Usage: wine PROGRAM [ARGUMENTS...]   Run the specified program
       wine --help                   Display this help and exit
       wine --version                Output version information and exit
You will only be able to execute 64-bit windows programs using wine in CorePure64.

Multi-lib means that software can run 32-bit and 64-bit programs.

Title: Re: wine fails
Post by: alexo on March 16, 2019, 08:48:52 AM

Thank you Juanito,

in the apps list it shows me only wine, there is no wine64 apps to be downloaded.
this is the output of uname -a

Code: [Select]

tc@box:~$ uname -a
Linux box 4.19.10-tinycore64 #1999 SMP Tue Dec 18 15:18:54 UTC 2018 x86_64 GNU/Linux
tc@box:~$
 
I attach the snapshot of the list of extensions availabe in apps showing wine.

Title: Re: wine fails
Post by: Juanito on March 16, 2019, 08:51:39 AM

The extension is named wine, but the executable in the wine extension is /usr/local/bin/wine64

Title: Re: wine fails
Post by: alexo on March 16, 2019, 09:15:05 AM

ok, but I don't understand why I cannot launch the application from the ondemand entry - named simply wine

Title: Re: wine fails
Post by: Juanito on March 16, 2019, 09:54:03 AM

If an app is ondemand, you first have to load it - either using tce-load or the icon

Title: Re: wine fails
Post by: alexo on March 16, 2019, 10:12:57 AM

Ok understood.

If I don't launch it from the ondemand entry wine64 does not exist. After I did that the command wine64 is available from the command line. So after having installed mono and gecko wine works correctly. You can consider this post as solved.

thank you for your kind patience.

cheers

Title: Re: wine fails
Post by: alexo on March 16, 2019, 11:25:57 AM

I'm sorry to be here again,
but there is still something that is missing:

winecfg dialog shows that wine version 2.0.3 fails to connect to the mount manager, as can be seen from the attached screenshot.

TinyCore 32 bit has wine version 4.2 that is perfectly working.

a final note:
wine creates many many big files in the home directory and the backup process takes many minutes to complete.

I hope that some kind soul could update wine for CorePure64.

thank you

Title: Re: wine fails
Post by: Juanito on March 17, 2019, 04:34:59 AM

wine updated

Have you tried a permanent home to make your backup quicker?

Title: Re: wine fails
Post by: alexo on March 17, 2019, 05:37:23 AM

Hi Juanito,

honestly I don't know how to set a permanent home. I'll find it in the wiki section of TC home page.
But I run CorePure64 from a USB stick and. It boots from a notbook that has Trisquel linux on it.

Thank you again,

cheers

Title: Re: wine fails
Post by: alexo on March 17, 2019, 08:26:08 AM

Hi Juanito,

persistent home and opt done. But I have to warn tinycore users that this process even if it speeds up a bit the backup it tremendously slows down the reboot - in particular the recovery from mydata.tgz

I'll keep a long backup but a fast booting.

Thanks again for updating wine.

Title: Re: wine fails
Post by: Rich on March 17, 2019, 09:10:25 AM

Hi alexo

Quote from: alexo on March 17, 2019, 08:26:08 AM

... persistent home and opt done. But I have to warn tinycore users that this process even if it speeds up a bit the backup it tremendously slows down the reboot - in particular the recovery from mydata.tgz ...

It sounds like you didn't remove  /home  and  /opt  from your backup when you made them persistent. With a USB drive that
would certainly explain a slow boot time. After you have booted up with persistent  /home  and  /opt  directories, remove
the   home  and  opt  entries from your  opt/.filetool.lst  file and run a backup.

Title: Re: wine fails
Post by: alexo on March 17, 2019, 11:53:32 AM

Hi Rich,

now it's ok. But I have a question: with persistent /opt and /home directorys, should I perform the backup manually to store commands in opt and files in home or is it automatic when I shut down giving backup in the exit dialog?

thank you for having corrected the output of the wine command. I tried but hadn't been able to do it.

cheers

Title: Re: wine fails
Post by: Rich on March 17, 2019, 12:21:19 PM

Hi alexo

Quote from: alexo on March 17, 2019, 11:53:32 AM

now it's ok. But I have a question: with persistent /opt and /home directorys, should I perform the backup manually to store commands in opt and files in home or is it automatic when I shut down giving backup in the exit dialog? ...

Backup is performed automatically if it is selected in the exit dialog. Persistent  /home  and  /opt  directories means they no
longer need to be backed up because they exist as actual directories on your USB stick. Any changes you make to those
2 directories is written directly to the USB stick. Most backups consist of configuration files that get modified for things like
sound or Xorg for example.

Quote

thank you for having corrected the output of the wine command. I tried but hadn't been able to do it.

After 30 minutes you can no longer edit your posts. If a correction is required after that, let me know.

Title: Re: wine fails
Post by: alexo on March 17, 2019, 01:11:59 PM

Thanks for the explanations.

Quote

After 30 minutes you can no longer edit your posts. If a correction is required after that, let me know.

It was not a question of time - even if it's good to know that this limit exists. Rather it was a formatting typo that I even if I tried was not able to correct. I don't know why there was that long white space I couldn't eliminate.

Thank you to all of you at Tinycore 

cheers