Page 2 of 5

Re: XY with WINE on Linux... anybody tried it?

Posted: 15 Jan 2014 14:31
by admin
The bug is related to the shell column handlers (the same information bits that are shown in the File Info Tips). So I'd assume you also don't get File Info Tips under Ubuntu.
40k wrote:I'm doing some more testing today to see what works and what not. When I'm done I will write an appreview on WineDB.
XY is obviously a Windows file manager but I have to say: There is absolutely NOTHING on unix that even comes within a thousand kilometers of XY when it comes to GUI file management. There's just nothing. Potential new market?
Well, DEFINITELY! :biggrin: :cup: :whistle:

Re: XY with WINE on Linux... anybody tried it?

Posted: 15 Jan 2014 15:49
by 40k
admin wrote:The bug is related to the shell column handlers (the same information bits that are shown in the File Info Tips). So I'd assume you also don't get File Info Tips under Ubuntu.
40k wrote:I'm doing some more testing today to see what works and what not. When I'm done I will write an appreview on WineDB.
XY is obviously a Windows file manager but I have to say: There is absolutely NOTHING on unix that even comes within a thousand kilometers of XY when it comes to GUI file management. There's just nothing. Potential new market?
Well, DEFINITELY! :biggrin: :cup: :whistle:
I did some digging around and this is what I have thus far:

works:
+ disk space indication for wine PREFIX partition is correct (on my system WINEPREFIX sits on another partition than root
+ access to the UNIX file system is respecting permissions as far as I can see. Can't view /root or other root access only locations. I never run wine as root so that behavior seems normal to me.
+ deleting files
+ move or copying files works usin xycopy but only by using ctrl+c ctrl+V
+ right click menu XYPLORER features (To clipboard, Rename Special, etc...)
+ quick file preview (including mouse down blow up for images). Image preview can be a bit slow when switching between images (not instant, more like 1 second)
+ thumbnails (slow!)
+ visual filters
+ color filters
+ scripting: At the moment most of my scripts work. It's difficult to test because most of them are to do with file handling and don't deal well with wineprefix yet. Most promissing so far is that run() is able to start native UNIX applications. Essentially that means that Xyplorer as access to /bin/bash which in turn allows you to do anything on the UNIX side of things from within xy :)

issues:
- XY returns throwable error on start-up
- disk space indication for root partition is slightly different from "df" return value (within 1% accurate)
- (wine performance) search result sorting slows down considerably when a lot of items are involved. sorting 5000 items on name in my home folder took around 5 seconds.
- When search hits folders owned by root XY locks up. Can not reproduce this consistently. May have other cause.
- UNIX symbolic links are not displayed
- Custom File Assosciations are somewhat broken. They work by themselves and Xy is able to launch native UNIX applications from their full path (e.g. /usr/bin/vlc) but the file path that is fed to the executable is corrupt (it contains the Windows drive letter which is not accepted in UNIX). In theory, you could write a shell script that regexes out the drive letter to make the path legal. I'm going to explore that more later because it means XYplorer could be used to navigate to a file and then it hands over the file handling (pdf, video, audio, etc...) to the UNIX native program. Native file handling can be done by editing the wine registry but obviously that's a chore compared to our file assosciations.
http://wiki.winehq.org/FAQ#head-a2e0e85 ... ebfefa7ce4

broken:
- tooltips
- tip of the day
- ALL right click menu shell commands associated with WINDOWS

Re: XY with WINE on Linux... anybody tried it?

Posted: 15 Jan 2014 17:19
by j_c_hallgren
40k wrote:broken:
- tip of the day
Wasn't that removed due to being outdated and unused? I think so...

Re: XY with WINE on Linux... anybody tried it?

Posted: 15 Jan 2014 20:12
by 40k
j_c_hallgren wrote:
40k wrote:broken:
- tip of the day
Wasn't that removed due to being outdated and unused? I think so...
You're right. I assumed the initial error was because XY tried to call tips of the day which requires extensions that don't work.
More good news though. I have managed to get Custom File Associations to work by dispatching the requests to a small shell script.

Re: XY with WINE on Linux... anybody tried it?

Posted: 15 Jan 2014 20:26
by admin
Looks very good all in all. :appl:

In your error message OS is reported as "WinXP Pro x64 (Service Pack 2), 64-bit". So I assume I have no chance to verify that I'm in fact on Ubuntu? It's just a virtual Windows box?

Re: XY with WINE on Linux... anybody tried it?

Posted: 15 Jan 2014 22:15
by 40k
admin wrote:Looks very good all in all. :appl:

In your error message OS is reported as "WinXP Pro x64 (Service Pack 2), 64-bit". So I assume I have no chance to verify that I'm in fact on Ubuntu? It's just a virtual Windows box?
It must be fairly easy. I'm able to execute native applications from within Xyplorer so Xy must surely be able to access the host system. There's no virtual box involved at all. I believe that would make the whole thing pointless, you could just as well run a virtual windows machine entirely in that case.

Guess I'll be spending the rest of the night with my nose in the Wine docs.

Re: XY with WINE on Linux... anybody tried it?

Posted: 16 Jan 2014 03:37
by 40k
Copying using XYcopy works fine. The dialogue is not updated in real-time and the progress bar will suddenly jump forward but the actual data transfer is the same as on Windows.
Don't try to use "Customize Toolbar", it completely crashes wine. You can easily customize the toolbar in your regular ini file so not a problem.

Re: XY with WINE on Linux... anybody tried it?

Posted: 16 Jan 2014 07:29
by admin
So why the OS is reported as "WinXP Pro x64"? Is that just a coincidence in version numbers (v5.2)?

Re: XY with WINE on Linux... anybody tried it?

Posted: 16 Jan 2014 11:33
by 40k
admin wrote:So why the OS is reported as "WinXP Pro x64"? Is that just a coincidence in version numbers (v5.2)?
The Wine environment is configured to emulate a particular Windows version. WinXP is the default setting.

Re: XY with WINE on Linux... anybody tried it?

Posted: 16 Jan 2014 12:39
by 40k
Found a problem that most likely will cause XY not to be usable after all.
After random periods of use XY will start throwing the following error when changing directories:

Code: Select all

Error:  	13 (0x0000000D)
Desc:   	Type mismatch
Dll:    	0
Proc:   	pList@21

Source: 	XYplorer
XY ver: 	13.60.0000
OS:     	Windows 7 Ultimate Edition N (Service Pack 1), 64-bit
Locale: 	1033
ANSI:   	1252
ACP:    	ANSI Latin 1
DBCS:   	No
DPI:    	96 (100%)

Date:   	16/01/2014 12:33:05
When this error appears only the subdirectories of that folder will appear. The files only "appear" when you drag the selection box inside the folder at random. That in turn causes the error to appear again. Scrolling in the tree sometimes triggers this error as well. I have a feeling it has to do with folder content listing.

All in all there's massive potential for XY under Wine, but as it stands this is probably the end of the road. Learned a lot in the last day or so, so can't complain :)

Don > I'm leaving my Wine install as it is, if you need info about how to config etc... send me a PM :D

Re: XY with WINE on Linux... anybody tried it?

Posted: 16 Jan 2014 14:18
by 40k
I've decided on a new approach. In my previous setup I was using a copy of my windows XY data folder that sits on another "drive" outside of the wine environment. So now I've restarted with a completely clean wine environment and a fresh xyplorer install.

What we learned so far:
+ "Customize Toolbar' now works normally. The crash-y behavior is gone

Re: XY with WINE on Linux... anybody tried it?

Posted: 16 Jan 2014 14:35
by admin
That "pList@21" error comes in Details mode?

Re: XY with WINE on Linux... anybody tried it?

Posted: 16 Jan 2014 15:41
by 40k
admin wrote:That "pList@21" error comes in Details mode?
Yes, I have details mode on by default. In fact, I did not think of changing it to see if it made a difference. I'll go back to my old wine environment to see if I can reproduce. The good news (I suppose) is that I'm not able to consistently reproduce this behavior, so at least it's not a code breaking bug.

Re: XY with WINE on Linux... anybody tried it?

Posted: 16 Jan 2014 15:45
by admin
Unfortunately there is a BIG bunch of code happening at pList@21 so it would be a long way to actually isolate the problematic line.

Re: XY with WINE on Linux... anybody tried it?

Posted: 16 Jan 2014 16:06
by 40k
admin wrote:Unfortunately there is a BIG bunch of code happening at pList@21 so it would be a long way to actually isolate the problematic line.
Here's the terminal dump from wine when xyplorer starts. The last couple of lines are concerning the error that appears on every boot (proc: IB@160)

I can probably supple a similar log should the pList@21 error appear. Does that help you any way at all?

Code: Select all

fixme:olepicture:OleLoadPictureEx (0xf01d34,3646,0,{7bf80980-bf32-101a-8bbb-00aa00300cab},x=0,y=0,f=0,0x32f944), partially implemented.
fixme:olepicture:OleLoadPictureEx (0xf01d34,550,1,{7bf80980-bf32-101a-8bbb-00aa00300cab},x=0,y=0,f=0,0x32f8e4), partially implemented.
fixme:olepicture:OleLoadPictureEx (0xf01d34,551,1,{7bf80980-bf32-101a-8bbb-00aa00300cab},x=0,y=0,f=0,0x32f8e4), partially implemented.
fixme:olepicture:OleLoadPictureEx (0xf01d34,697,1,{7bf80980-bf32-101a-8bbb-00aa00300cab},x=0,y=0,f=0,0x32f884), partially implemented.
fixme:olepicture:OleLoadPictureEx (0xf01d34,301,1,{7bf80980-bf32-101a-8bbb-00aa00300cab},x=0,y=0,f=0,0x32f884), partially implemented.
fixme:olepicture:OleLoadPictureEx (0xf01d34,280,1,{7bf80980-bf32-101a-8bbb-00aa00300cab},x=0,y=0,f=0,0x32f884), partially implemented.
fixme:olepicture:OleLoadPictureEx (0xf01d34,247,1,{7bf80980-bf32-101a-8bbb-00aa00300cab},x=0,y=0,f=0,0x32f884), partially implemented.
fixme:olepicture:OleLoadPictureEx (0xf01d34,553,1,{7bf80980-bf32-101a-8bbb-00aa00300cab},x=0,y=0,f=0,0x32f884), partially implemented.
fixme:olepicture:OleLoadPictureEx (0xf01d34,551,1,{7bf80980-bf32-101a-8bbb-00aa00300cab},x=0,y=0,f=0,0x32f884), partially implemented.
fixme:olepicture:OleLoadPictureEx (0xf01d34,301,1,{7bf80980-bf32-101a-8bbb-00aa00300cab},x=0,y=0,f=0,0x32f8b4), partially implemented.
fixme:olepicture:OleLoadPictureEx (0xf01d34,334,1,{7bf80980-bf32-101a-8bbb-00aa00300cab},x=0,y=0,f=0,0x32f8b4), partially implemented.
fixme:olepicture:OleLoadPictureEx (0xf01d34,25984,1,{7bf80980-bf32-101a-8bbb-00aa00300cab},x=0,y=0,f=0,0x32f914), partially implemented.
fixme:olepicture:OleLoadPictureEx (0xf01d34,180,1,{7bf80980-bf32-101a-8bbb-00aa00300cab},x=0,y=0,f=0,0x32f8b4), partially implemented.
fixme:olepicture:OleLoadPictureEx (0xf01d34,163,1,{7bf80980-bf32-101a-8bbb-00aa00300cab},x=0,y=0,f=0,0x32f8e4), partially implemented.
fixme:olepicture:OleLoadPictureEx (0xf01d34,180,1,{7bf80980-bf32-101a-8bbb-00aa00300cab},x=0,y=0,f=0,0x32f8b4), partially implemented.
fixme:olepicture:OleLoadPictureEx (0xf01d34,163,1,{7bf80980-bf32-101a-8bbb-00aa00300cab},x=0,y=0,f=0,0x32f8e4), partially implemented.
fixme:olepicture:OleLoadPictureEx (0xf01d34,774,1,{7bf80980-bf32-101a-8bbb-00aa00300cab},x=0,y=0,f=0,0x32f914), partially implemented.
fixme:olepicture:OLEPictureImpl_get_hPal unimplemented for type 3. Returning 0 palette.
fixme:olepicture:OleLoadPictureEx (0xf01d34,164,1,{7bf80980-bf32-101a-8bbb-00aa00300cab},x=0,y=0,f=0,0x32f914), partially implemented.
fixme:olepicture:OleLoadPictureEx (0xf01d34,334,1,{7bf80980-bf32-101a-8bbb-00aa00300cab},x=0,y=0,f=0,0x32f914), partially implemented.
fixme:olepicture:OLEPictureImpl_get_hPal unimplemented for type 3. Returning 0 palette.
fixme:olepicture:OleLoadPictureEx (0xf01d34,334,1,{7bf80980-bf32-101a-8bbb-00aa00300cab},x=0,y=0,f=0,0x32f914), partially implemented.
fixme:olepicture:OLEPictureImpl_get_hPal unimplemented for type 3. Returning 0 palette.
fixme:olepicture:OleLoadPictureEx (0xf01d34,334,1,{7bf80980-bf32-101a-8bbb-00aa00300cab},x=0,y=0,f=0,0x32f914), partially implemented.
fixme:olepicture:OLEPictureImpl_get_hPal unimplemented for type 3. Returning 0 palette.
fixme:olepicture:OleLoadPictureEx (0xf01d34,334,1,{7bf80980-bf32-101a-8bbb-00aa00300cab},x=0,y=0,f=0,0x32f914), partially implemented.
fixme:olepicture:OLEPictureImpl_get_hPal unimplemented for type 3. Returning 0 palette.
fixme:olepicture:OleLoadPictureEx (0xf01d34,334,1,{7bf80980-bf32-101a-8bbb-00aa00300cab},x=0,y=0,f=0,0x32f914), partially implemented.
fixme:olepicture:OLEPictureImpl_get_hPal unimplemented for type 3. Returning 0 palette.
fixme:olepicture:OleLoadPictureEx (0xf01d34,334,1,{7bf80980-bf32-101a-8bbb-00aa00300cab},x=0,y=0,f=0,0x32f914), partially implemented.
fixme:olepicture:OLEPictureImpl_get_hPal unimplemented for type 3. Returning 0 palette.
fixme:olepicture:OleLoadPictureEx (0xf01d34,334,1,{7bf80980-bf32-101a-8bbb-00aa00300cab},x=0,y=0,f=0,0x32f914), partially implemented.
fixme:olepicture:OLEPictureImpl_get_hPal unimplemented for type 3. Returning 0 palette.
fixme:olepicture:OleLoadPictureEx (0xf01d34,334,1,{7bf80980-bf32-101a-8bbb-00aa00300cab},x=0,y=0,f=0,0x32f914), partially implemented.
fixme:olepicture:OLEPictureImpl_get_hPal unimplemented for type 3. Returning 0 palette.
fixme:olepicture:OleLoadPictureEx (0xf01d34,334,1,{7bf80980-bf32-101a-8bbb-00aa00300cab},x=0,y=0,f=0,0x32f914), partially implemented.
fixme:olepicture:OLEPictureImpl_get_hPal unimplemented for type 3. Returning 0 palette.
fixme:olepicture:OleLoadPictureEx (0xf01d34,334,1,{7bf80980-bf32-101a-8bbb-00aa00300cab},x=0,y=0,f=0,0x32f914), partially implemented.
fixme:olepicture:OLEPictureImpl_get_hPal unimplemented for type 3. Returning 0 palette.
fixme:olepicture:OleLoadPictureEx (0xf01d34,334,1,{7bf80980-bf32-101a-8bbb-00aa00300cab},x=0,y=0,f=0,0x32f914), partially implemented.
fixme:olepicture:OLEPictureImpl_get_hPal unimplemented for type 3. Returning 0 palette.
fixme:olepicture:OLEPictureImpl_SaveAsFile (0x1592a0)->(0x1fa900, 0, (nil)), hacked stub.
fixme:wincodecs:PngDecoder_Block_GetCount 0x12a1038,0x32f3c8: stub
fixme:shell:SHGetImageList Unsupported image list 2 requested
fixme:olepicture:OleLoadPictureEx (0xf4e51c,1167,1,{7bf80980-bf32-101a-8bbb-00aa00300cab},x=0,y=0,f=0,0x32f250), partially implemented.
fixme:olepicture:OleLoadPictureEx (0xf4e51c,1167,1,{7bf80980-bf32-101a-8bbb-00aa00300cab},x=0,y=0,f=0,0x32f250), partially implemented.
fixme:olepicture:OleLoadPictureEx (0xf4e51c,14995,1,{7bf80980-bf32-101a-8bbb-00aa00300cab},x=0,y=0,f=0,0x32f250), partially implemented.
fixme:olepicture:OLEPictureImpl_FindConnectionPoint no connection point for {33ad4ed2-6699-11cf-b70c-00aa0060d393}
fixme:olepicture:OLEPictureImpl_FindConnectionPoint no connection point for {33ad4ed2-6699-11cf-b70c-00aa0060d393}
fixme:olepicture:OLEPictureImpl_FindConnectionPoint no connection point for {33ad4ed2-6699-11cf-b70c-00aa0060d393}
fixme:olepicture:OLEPictureImpl_FindConnectionPoint no connection point for {33ad4ed2-6699-11cf-b70c-00aa0060d393}
fixme:olepicture:OLEPictureImpl_FindConnectionPoint no connection point for {33ad4ed2-6699-11cf-b70c-00aa0060d393}
fixme:olepicture:OLEPictureImpl_FindConnectionPoint no connection point for {33ad4ed2-6699-11cf-b70c-00aa0060d393}
fixme:olepicture:OLEPictureImpl_FindConnectionPoint no connection point for {33ad4ed2-6699-11cf-b70c-00aa0060d393}
fixme:olepicture:OLEPictureImpl_FindConnectionPoint no connection point for {33ad4ed2-6699-11cf-b70c-00aa0060d393}
fixme:olepicture:OLEPictureImpl_FindConnectionPoint no connection point for {33ad4ed2-6699-11cf-b70c-00aa0060d393}
fixme:olepicture:OLEPictureImpl_FindConnectionPoint no connection point for {33ad4ed2-6699-11cf-b70c-00aa0060d393}
fixme:olepicture:OLEPictureImpl_FindConnectionPoint no connection point for {33ad4ed2-6699-11cf-b70c-00aa0060d393}
fixme:olepicture:OLEPictureImpl_FindConnectionPoint no connection point for {33ad4ed2-6699-11cf-b70c-00aa0060d393}
fixme:olepicture:OLEPictureImpl_FindConnectionPoint no connection point for {33ad4ed2-6699-11cf-b70c-00aa0060d393}
fixme:ole:RemUnknown_QueryInterface No interface for iid {00000019-0000-0000-c000-000000000046}
fixme:olepicture:OLEPictureImpl_FindConnectionPoint no connection point for {33ad4ed2-6699-11cf-b70c-00aa0060d393}
fixme:olepicture:OLEPictureImpl_FindConnectionPoint no connection point for {33ad4ed2-6699-11cf-b70c-00aa0060d393}
fixme:olepicture:OLEPictureImpl_FindConnectionPoint no connection point for {33ad4ed2-6699-11cf-b70c-00aa0060d393}
fixme:olepicture:OLEPictureImpl_FindConnectionPoint no connection point for {33ad4ed2-6699-11cf-b70c-00aa0060d393}
fixme:olepicture:OLEPictureImpl_FindConnectionPoint no connection point for {33ad4ed2-6699-11cf-b70c-00aa0060d393}
fixme:olepicture:OLEPictureImpl_FindConnectionPoint no connection point for {33ad4ed2-6699-11cf-b70c-00aa0060d393}
fixme:olepicture:OLEPictureImpl_FindConnectionPoint no connection point for {33ad4ed2-6699-11cf-b70c-00aa0060d393}
fixme:olepicture:OLEPictureImpl_FindConnectionPoint no connection point for {33ad4f92-6699-11cf-b70c-00aa0060d393}
fixme:ole:OLEFontImpl_IPersistStreamInit_InitNew (0x1dde54), stub!
fixme:ole:OLEFontImpl_IPersistStreamInit_InitNew (0x1dd324), stub!
fixme:ole:OLEFontImpl_IPersistStreamInit_InitNew (0x138217c), stub!
fixme:ole:OLEFontImpl_IPersistStreamInit_InitNew (0x15f464), stub!
fixme:olepicture:OLEPictureImpl_FindConnectionPoint no connection point for {33ad4f92-6699-11cf-b70c-00aa0060d393}
fixme:olepicture:OLEPictureImpl_FindConnectionPoint no connection point for {33ad4f92-6699-11cf-b70c-00aa0060d393}
fixme:olepicture:OLEPictureImpl_FindConnectionPoint no connection point for {33ad4f92-6699-11cf-b70c-00aa0060d393}
fixme:ole:OLEFontImpl_IPersistStreamInit_InitNew (0x21f7d4), stub!
fixme:ole:OLEFontImpl_IPersistStreamInit_InitNew (0x1df27c), stub!
fixme:ole:OLEFontImpl_IPersistStreamInit_InitNew (0x1df27c), stub!
fixme:olepicture:OLEPictureImpl_FindConnectionPoint no connection point for {33ad4ed2-6699-11cf-b70c-00aa0060d393}
fixme:olepicture:OLEPictureImpl_FindConnectionPoint no connection point for {33ad4ed2-6699-11cf-b70c-00aa0060d393}
fixme:olepicture:OLEPictureImpl_FindConnectionPoint no connection point for {33ad4ed2-6699-11cf-b70c-00aa0060d393}
fixme:olepicture:OLEPictureImpl_FindConnectionPoint no connection point for {33ad4ed2-6699-11cf-b70c-00aa0060d393}
fixme:olepicture:OLEPictureImpl_FindConnectionPoint no connection point for {33ad4ed2-6699-11cf-b70c-00aa0060d393}
fixme:olepicture:OLEPictureImpl_FindConnectionPoint no connection point for {33ad4ed2-6699-11cf-b70c-00aa0060d393}
fixme:ole:OLEFontImpl_IPersistStreamInit_InitNew (0x130381c), stub!
fixme:netapi32:NetShareEnum Stub ((null) 2 0x32edac -1 0x32edb0 0x32ed94 0x32ed9c)
fixme:shell:ShellDispatch_QueryInterface not implemented for {7fd52380-4e07-101b-ae2d-08002b2ec713} (unknown)
fixme:shell:ShellDispatch_QueryInterface not implemented for {37d84f60-42cb-11ce-8135-00aa004bb851} (unknown)
fixme:shell:FolderImpl_Items (0x20c9640,0x32f54c)
fixme:shell:FolderImpl_QueryInterface not implemented for {df0b3d60-548f-101b-8e65-08002b2bd119} (PSSupportErrorInfo)