Drive autodetection sets C: as a device mapping instead of folder mapping

[rcspam]

Hi,

I have install last vineyard on my old wine (win32) install which run like a charm.

Since vineyard install , when i start a exe, it says: "wine: cannot find L"unix\\home\\....."

So howto revert vineyard install to find back my wine config.

Thanks

rcspam

[Christian Dannie Storgaard (cybolic)]

Thank you for reporting this!
Can you send me the full output from when it happens?

[rcspam (rcspam)]

No i have uninstall vineyard.

But i remember only one thing: The vineyard-preferences found win64 but no my win32 wine install and it was impossible to add a new preset.

Can you explain me how to reverse my primary install, i suppose there is only some options to revert, i hope.
It's really very boring because i want avoid to reinstall all my win app on a fresh wine install.
thanks

[rcspam (rcspam)]

precision:

my win32 install was in the default .wine folder

[Christian Dannie Storgaard (cybolic)]

I've just fixed an issue, which could cause a win32 prefix in ~/.wine to be reported as win64, that might help.

I'm still not sure what problem you're having after uninstalling Vineyard. Could you give an example of what you're seeing?

[rcspam (rcspam)]

If i lauch an app:

$ wine ./someApp.exe
fixme:service:scmdatabase_autostart_services Auto-start service L"Bonjour Service" failed to start: 2
fixme:service:scmdatabase_autostart_services Auto-start service L"C-Map Service" failed to start: 2
err:module:import_dll Library mscoree.dll (which is needed by L"C:\\windows\\Microsoft.NET\\Framework\\v4.0.30319\\mscorsvw.exe") not found
err:module:LdrInitializeThunk Main exe initialization for L"C:\\windows\\Microsoft.NET\\Framework\\v4.0.30319\\mscorsvw.exe" failed, status c0000135
err:service:service_send_command service protocol error - failed to write pipe!
fixme:service:scmdatabase_autostart_services Auto-start service L"clr_optimization_v4.0.30319_32" failed to start: 1053
fixme:advapi:RegisterEventSourceA ((null),"System"): stub
fixme:advapi:RegisterEventSourceW (L"",L"System"): stub
fixme:service:scmdatabase_autostart_services Auto-start service L"NIHardwareService" failed to start: 2
fixme:ntoskrnl:KeInitializeSemaphore (0x1129a0 0 2147483647) stub
fixme:ntoskrnl:KeInitializeSemaphore (0x1129b4 0 2147483647) stub
fixme:ntoskrnl:KeInitializeSemaphore (0x1129c8 1 2147483647) stub
fixme:ntoskrnl:ObReferenceObjectByHandle stub: 0x4c 1f03ff (nil) 0 0x542e40 (nil)
fixme:ntoskrnl:KeReleaseSemaphore (0x1129a0 0 1 0) stub
fixme:ntoskrnl:KeGetCurrentThread () stub
fixme:ntoskrnl:KeSetPriorityThread ((nil) 24)
fixme:ntoskrnl:KeWaitForSingleObject stub: 0x1129a0, 6, 0, 0, (nil)
fixme:ntoskrnl:KeReleaseSemaphore (0x1129c8 1 2147483645 0) stub
wine: cannot find L"unix\\home\\rc\\.wine\\drive_c\\Program Files\\someApp.exe"

[Christian Dannie Storgaard (cybolic)]

Could you send the output of "ls -l ~/.wine/dosdevices/" and "ls -ld ~/.wine/drive_c"?
Also, which version of Wine are you using (wine --version)?

[rcspam (rcspam)]

$ ls -l ~/.wine/dosdevices/
drwxrwxr-x 3 rc rc 4096 mars 27 14:58 c:
lrwxrwxrwx 1 rc rc 25 mars 22 21:11 c:: -> /home/rc/.wine/drive_c
lrwxrwxrwx 1 rc rc 12 mars 22 21:11 d:: -> /media/cdrom
lrwxrwxrwx 1 rc rc 8 mars 22 21:11 d::: -> /dev/sr0
lrwxrwxrwx 1 rc rc 4 mars 27 17:13 e: -> /mnt
lrwxrwxrwx 1 rc rc 10 mars 27 17:13 e:: -> /dev/loop4
lrwxrwxrwx 1 rc rc 8 sept. 11 2014 g:: -> /dev/sdi
lrwxrwxrwx 1 rc rc 9 sept. 11 2014 h:: -> /dev/sdh1
lrwxrwxrwx 1 rc rc 8 sept. 11 2014 i:: -> /dev/sr0
lrwxrwxrwx 1 rc rc 8 sept. 11 2014 m:: -> /dev/sde
lrwxrwxrwx 1 rc rc 8 sept. 11 2014 n:: -> /dev/sdc
lrwxrwxrwx 1 rc rc 8 sept. 11 2014 o:: -> /dev/sdf
lrwxrwxrwx 1 rc rc 8 sept. 11 2014 p:: -> /dev/sdd
lrwxrwxrwx 1 rc rc 8 sept. 11 2014 q:: -> /dev/sdj
lrwxrwxrwx 1 rc rc 8 sept. 11 2014 r:: -> /dev/sdh
lrwxrwxrwx 1 rc rc 8 sept. 11 2014 s:: -> /dev/sr1
lrwxrwxrwx 1 rc rc 8 sept. 11 2014 t:: -> /dev/sdg
lrwxrwxrwx 1 rc rc 9 sept. 11 2014 v:: -> /dev/sdc1
lrwxrwxrwx 1 rc rc 1 mars 22 21:11 z:: -> /

$ ls -ld ~/.wine/drive_c
drwxr-xr-x 8 rc rc 4096 août 13 2015 drive_c/

[rcspam (rcspam)]

$ wine --version
wine-1.8

[Christian Dannie Storgaard (cybolic)]

This looks like it might be a problem with the executable you're trying to run not actually existing.
So, 3 questions:
1. Are you sure the someApp.exe file exists?
2. Have you tried running Wine with the full path to the file (e.g. wine ~/Downloads/someApp.exe)?
3. Does running a different Wine application work (e.g. wine 'C:/Windows/Notepad.exe')?

Vineyard doesn't actually change anything when you just run it, so I'm having a lot of trouble figuring out what might have happened to your default Wine prefix :/

[rcspam (rcspam)]

No, no app works...

[Christian Dannie Storgaard (cybolic)]

What happens if you try to run something while forcing 32-bit? (e.g. "env WINEARCH=win32 wine ...")
Also, did you try all three suggestions?

[rcspam (rcspam)]

Same thing:

$ env WINEARCH=win32 wine "~/.wine/drive_c/Program Files/someAPP/someAPP.exe"

wine: cannot find '/home/rc/.wine/drive_c/Program Files//someAPP/someAPP.exe'
$ ls '/home/rc/.wine/drive_c/Program Files//someAPP/someAPP.exe'
 '/home/rc/.wine/drive_c/Program Files//someAPP/someAPP.exe'

The fact is that wine doesn't find the exe.
Is there a PATH option in wine, which had been unset or something like that ?

[rcspam (rcspam)]

Hi Christian,
No more news ?!

[Christian Dannie Storgaard (cybolic)]

Sorry, I've been testing a virtual machine, trying various combinations of Wine versions and the recent versions of Vineyard; creating a 32-bit ~/.wine prefix and then loading Vineyard and/or trying to run it as 64-bit in some way, and I'm afraid I haven't been able to reproduce your problem.

Wine doesn't have any sort of PATH option, apart from the dosdevices and drive_c you listed for me, and Vineyard doesn't set or change anything on just loading/reading a prefix (apart from temporary environment variables, that aren't set or kept when not using Vineyard).

I don't know what else to look at :/
You're sure "wine 'C:/Windows/Notepad.exe'" didn't work, right?

[rcspam (rcspam)]

Oops sorry, yes "wine 'C:/Windows/Notepad.exe' or "wine
'C:/Windows/Explorer.exe.exe' works.
If i start with..

$ wine "/home/rc/.wine/drive_c/windows/notepad.exe"
wine: cannot find '/home/rc/.wine/drive_c/windows/notepad.exe'

if i want start a program from "C:"

$ env WINEPREFIX="/home/rc/.wine" wine 'C:\\Program
Files\\MyProg\\MyProg.exe'
wine: cannot find 'C:\\Program Files\\MyProg\\MyProg.exe'

Very strange !!!

2016-03-31 0:51 GMT+02:00 Christian Dannie Storgaard <email address hidden>:

> Sorry, I've been testing a virtual machine, trying various combinations
> of Wine versions and the recent versions of Vineyard; creating a 32-bit
> ~/.wine prefix and then loading Vineyard and/or trying to run it as
> 64-bit in some way, and I'm afraid I haven't been able to reproduce your
> problem.
>
> Wine doesn't have any sort of PATH option, apart from the dosdevices and
> drive_c you listed for me, and Vineyard doesn't set or change anything
> on just loading/reading a prefix (apart from temporary environment
> variables, that aren't set or kept when not using Vineyard).
>
> I don't know what else to look at :/
> You're sure "wine 'C:/Windows/Notepad.exe'" didn't work, right?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1562501
>
> Title:
> After run vineyard, my wine app doesn't start anymore
>
> Status in Vineyard:
> Incomplete
>
> Bug description:
> Hi,
>
> I have install last vineyard on my old wine (win32) install which run
> like a charm.
>
> Since vineyard install , when i start a exe, it says: "wine: cannot
> find L"unix\\home\\....."
>
> So howto revert vineyard install to find back my wine config.
>
> Thanks
>
> rcspam
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/vineyard/+bug/1562501/+subscriptions
>

[rcspam (rcspam)]

I have found the problem...

In Fact, i suppose vineyard had changed the dosdevices tree.
I have create new wine dosdevices dir in my wine dir:

$ mv .wine .wine-BU
launch wine to create a new wine dir
$ mv .wine-BU/dosdevices .wine-BU/dosdevices-BU
$ cp .wine/dosdevices .wine-BU/
$ rm .wine
and
$ mv .wine-BU .wine

launch winecfg and to detect automatically in devices tab

and all my apps works again.

my dosdevices , you can compare to the above one https://bugs.launchpad.net/vineyard/+bug/1562501/comments/7

$ ls -l dosdevices
total 0
lrwxrwxrwx 1 rc rc 10 mars 31 09:02 c: -> ../drive_c
lrwxrwxrwx 1 rc rc 6 mars 31 09:35 d: -> /cdrom
lrwxrwxrwx 1 rc rc 8 mars 31 09:36 e:: -> /dev/sdd
lrwxrwxrwx 1 rc rc 8 mars 31 09:36 f:: -> /dev/sde
lrwxrwxrwx 1 rc rc 8 mars 31 09:36 g:: -> /dev/sdf
lrwxrwxrwx 1 rc rc 8 mars 31 09:36 h:: -> /dev/sdg
lrwxrwxrwx 1 rc rc 8 mars 31 09:36 i:: -> /dev/sr0
lrwxrwxrwx 1 rc rc 4 mars 31 09:02 j: -> /mnt
lrwxrwxrwx 1 rc rc 10 mars 31 09:02 j:: -> /dev/loop4
lrwxrwxrwx 1 rc rc 17 mars 31 09:35 n: -> /media/rc/WIN7
lrwxrwxrwx 1 rc rc 22 mars 31 09:35 o: -> /media/rc/DATA_NTFS
lrwxrwxrwx 1 rc rc 21 mars 31 09:35 q: -> /media/rc/BOOT_MAV
lrwxrwxrwx 1 rc rc 21 mars 31 09:35 r: -> /media/rc/HOME_MAV
lrwxrwxrwx 1 rc rc 11 mars 31 09:35 t: -> /home/rc
lrwxrwxrwx 1 rc rc 1 mars 31 09:02 z: -> /

I hope it can help you to found the eventually bug

[Christian Dannie Storgaard (cybolic)]

Spot on! You found it :) I completely missed the line with just "c:" in your original listing, sorry!
Yes, this looks like a bug indeed, I'll get on it!

Thanks for tracking it down and reporting it!