[prev in list] [next in list] [prev in thread] [next in thread] 

List:       wine-devel
Subject:    Re: Winelib portability on USB booted system
From:       Stefan_Dösinger <stefandoesinger () gmail ! com>
Date:       2022-09-29 8:22:39
Message-ID: 264C28EA-B00F-4C3D-8CF6-970E79BC39D7 () gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


Hi,

Wine itself doesn't care how you boot. I am running a pile of games on systems booted \
from NFS. It is possible that there is a difference between the two systems. Are they \
using the same distro, and same version of the distro?

Three things to check:

1) Stupidity check, is the file xerase.exe.so actually there and not e.g. a dead \
symlink? What if you cd into the directory and run it from there? 2) Does winecfg \
work? If it doesn't, something's flawed with the Wine installation 3) use the +module \
debug channel (WINEDEBUG=module wine ...). It will be spammy. Search for xerase.exe \
and see if it reports any library load issues in xerase or its dependencies.

Good luck,
Stefan

> Am 28.09.2022 um 22:44 schrieb Brent Burkholder <bburk@extremeprotocol.com>:
> 
> Update:  decided to delete the extra links in dosdevices… no change
> 
> If I don't use sudo (which the program actually needs, so this is just for a data \
>                 point) then instead I get
> wine: failed to start L"C:\\XERASxlnx\\xerase.exe.so"
> 
> 
> 
> From: Brent Burkholder
> Sent: Wednesday, September 28, 2022 3:33 PM
> To: wine-devel@winehq.org
> Subject: Winelib portability on USB booted system
> 
> 
> We had originally tried a software port using winelib 5, and it was just a no-go in \
> functionality.  Wine 7 is working a LOT better for what we're doing (Windows GUI \
> with ability to do low level Linux hooks), so thank you all for all of the hard \
> work! 
> 
> Unfortunately, even though the software is running great on our development \
> machine, when I try to run it on another system (configured USB boot, should have \
> the same version of wine, etc) it doesn't run at all with pretty much no feedback.  \
> Can anyone help me understand why, or what I need to be looking for? 
> Both systems are starting with the same script (I've done a lot of variations, \
> directly launching myself, and it doesn't seem to matter.) 
> #!/bin/bash
> sudo env "PATH=/opt/wine-devel/bin:$PATH" /opt/wine-devel/bin/wine xerase.exe.so
> 
> 
> The compiling system starts right up.  The USB boot system that I'm trying to run \
> it on gives me 
> 0078:fixme:wineusb:add_unix_device Interface 1 has 2 alternate settings; using the \
>                 first one.
> Wine: failed to start L"F:\\home\\test\.wine\\drive_c\\XERASxlnx\\xerase.exe.so"
> Application could not be started, or no application associated with the specified \
> file. ShellExecuteEx failed: File not found.
> 
> If I do the command directly instead of through a script I get exactly the same \
> thing. 
> If I cut out the env path stuff (1), or keep the path but call just wine (2), or \
> just call wine (bashrc has the path now) same results  • sudo \
> /opt/wine-devel/bin/wine xerase.exe.so  • sudo env \
> "PATH=/opt/wine-devel/bin:$PATH" wine xerase.exe.so  • sudo wine xerase.exe.so
> 	• sudo wine /home/test/.wine/drive_c/XERASxlnx/xerase.exe.so
> 
> 0078:fixme:wineusb:add_unix_device Interface 1 has 2 alternate settings; using the \
>                 first one.
> Wine: failed to start L"F:\\home\\test\.wine\\drive_c\\XERASxlnx\\xerase.exe.so"
> Application could not be started, or no application associated with the specified \
> file. ShellExecuteEx failed: File not found.
> 
> 
> So… observations…
> 	• Not sure where F: is coming from?  C: I might understand (though frankly, I'd \
> just as soon the program realize we're using the unix file structure, not any \
> virtualized windows stuff for what we're doing) 
> 
> When I look at .wine/dosdevices on both systems…
> 
> Build/working system:
> z: -> /
> c: -> ../drive_c
> <com devices>
> .
> ..
> 
> Not working USB booted system:
> z: -> /
> c: -> ../drive_c
> d:: -> /dev/sda1
> g:: -> /dev/sda
> f:: -> /dev/sd5
> e:: -> /dev/sda2
> <com devices>
> d: -> /boot/efi
> f: -> /
> .
> ..
> 
> Any suggestions in changes to compilation or environmental variables to get wine to \
> start running it? 
> I guess I could delete d::, g::, f::, e::, d:, and f: and see if that makes a \
> difference but figured I'd ask the question first 
> 
> 
> 
> 
> Brent Burkholder
> Extreme Protocol Solutions
> bburk@extremeprotocol.com


["signature.asc" (signature.asc)]

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEQxb0tqoFWyeVMl1sPRO8yFRPGiIFAmM1Vc8ACgkQPRO8yFRP
GiKGnRAAjWR1Bk4rocfrVVYJrEc4P2NHXujDOAEOCvp7AGmaHnsNg71Zld+2v4h+
xVV38yB8elf41ftTcqSUuGKEvbl0Do7DOW6ni4nB5hSUyHjJRONsRqTAFiukIduI
gblpywl/djcUdZvQoJ5OBveleBIN+DBFxDk8kqc1x5flBN4m2lumFtyRUr+SDjKD
572H7Sx2JsQOBEXkUUg5jqf/CHx25TL8BvjEOysz1WdEZCrE0jhDuAr9lGsIaZ3y
Q11kt84JEay5Yh78K8xgsZyC/LNE97N027hphDw9/toZt6TTTW46qZl/UC4wtmaf
5QHh6/VLC+gKFZwhNK3auuD1aF8Tza9bZTNiietldWZkenSNG4mSXwua0w8//zKH
Eh1g2dMPq8jlzUnWw9wQPDmDa5s67oGQjdvbeCA10WPk2FoW5DbBohzVtF3/egOT
cGqk9oeLTw61w0W07ZbQUQ5bHEGHp4br+OgqQtZf/BH0oliygjRxQxq737SuWzQq
Gt1zlqbyeBPQV7pqsma5tiKboyS5w0Yc+9avbiGdplpzWRFpiJi7/K3v+HFLu5+A
gunz94d7iPNW0VZGCI2ibOaLmlizltjV+rLrtTA8rLhPSbatcPX1Z4Hw7OozEh1n
KeS90EillWlS9n/6kQWAJcKM6oJbNNcJJUH9ZSFhJMV2C9rTzUc=
=8IwJ
-----END PGP SIGNATURE-----




[prev in list] [next in list] [prev in thread] [next in thread]