Author Topic: Wine effect (Read 21418 times)

ChrisMW · « **on:** October 07, 2016, 11:32:46 pm »

Since 13 came out I was eager to try it under Wine. And it is impressively good. Speed, responsiveness, all much improved. Running EA seemed almost so good, I was about to remove it from the Windows machine that I normally run for mostly EA purposes. However, I noticed when importing some C# code from elsewhere, it failed, whereas windows doesn't. the source code in question resides in various sub directories of a tree I was given, and the first couple are empty. Even so, I had the recurse option set (Import source directory). The source directory was located somewhere in my home directory, let's say ~/Documents/Customer/Project/Source/*.* and below. In my Wine box, this shows as Z:\, on my VPC, the same location would be I:\Project\Source\*.* (so a little shorter).

Under wine, there's no recursion, in the VPC it does. Anyone else ran into this?

And I also noticed that EA 13 cannot pick up system DSN's, only user DSN's. Under windows it works with both. That's not a biggie, but the 'don't recurse' behaviour is a little worrying.

Rgds Chris

Eve · « **Reply #1 on:** October 10, 2016, 08:43:32 am »

Glad you like the improvements we have made to running under Wine.

Neither of the reported issues are things that I would expect us to do anything different for Wine. If they are failing, it's probably an issue in Wine that we may need to work around.

I just tested the a recursive code import, and classes were imported from a child directory. Maybe check that the option for recursive code import on the directory import dialog?

I can't test the a system DSN configuration right now, but that does seem unusual. The only recommendation I can think of right now is to run: winetricks --force mdac28

Every time Wine updates the mdac appears to get corrupted somehow, and what it breaks vs what it doesn't confuses me.

ChrisMW · « **Reply #2 on:** October 10, 2016, 10:54:11 pm »

I'll give that a go, but as I've defined the sources as user DSN's, it works well now, just something to watch. When you enter it as a system DSN, it works from the ODBC config (test the connection), but EA says that the DSN isn't there, or not valid. Perhaps it's a Wine and system permissions thingie, I don't use Wine a lot, so could have easily missed things.

For the recurse thing, it does recurse, but doesn't find the same amount of files, so the recurse isn't working as under windows. I can't handover the files and dir structure, without removing stuff.... There's quite a deep nest and quite a lot of empty directories. I'll work on making it handoverable and then post it....

Rgds Chris

qwerty · « **Reply #3 on:** October 11, 2016, 01:05:20 am »

The recursion might be a security issue. Linux systems have a more fine grained setting than Windoze.

q.

ChrisMW · « **Reply #4 on:** October 11, 2016, 02:19:20 am »

I would not expect to, all directories are within my home directory, so if windows can, linux should certainly be able to.
**EDIT** the windows machine runs inside Linux, all contained in my home directory, and the location is offered through a permanent share (VirtualBox)

On a side note, I have one W7 32bit machine that also struggles to use System DSN's. W7 64bit has no problems, Linux/Wine, same as the W7 32bit. I suspect it is something in the ODBC setup, but not sure what. Still looking to what is so different.

Glassboy · « **Reply #5 on:** October 12, 2016, 07:11:13 am »

Quote from: qwerty on October 11, 2016, 01:05:20 am

The recursion might be a security issue. Linux systems have a more fine grained setting than Windoze.

Well firstly the security is based on the file system being used not the O/S, and secondly the Ext family of file systems commonly used for linux is only just starting to catch up with features that NTFS has had for over a decade. For example journalling didn't make an appearance until ext3 in the early 2000s, and transparent encryption not until 2015 in ext4.

Having managed large environments of both, and managed sysadmin teams for both, I can tell you that the common problem is that people coming from a Unix\Linux background take a long time to understand the paradigm for NTFS, whereas people going from the NTFS\Mainframe world have an easier time comprehending 'nix file systems.

ChrisMW · « **Reply #6 on:** October 13, 2016, 10:27:21 pm »

As both the virtual machine and the wine run use mapped drives, I'd suspect we're firmly in SMB territory. It could well be a wine thing. So, I created the map in Wine to identical to the one VirtualBox and ran both. The Wine import yields nothing much

The Windows import finds the sources, there are 13 of these shots in total to cover all that was imported, I'll just show one

And a shot of the settings, which was the same for Wine as well as VirtualBox. I checked with the Wine Explorer that I can see the .java files before importing. And I can.

(Sorry for the ugly blotches, but I am obligated to blotch out some bits)

One other thing I noticed in Wine, if you detach the projectbrowser, it remains on your screen, even when you change desktops. Which is somewhat odd, and most likely a Wine problem. I run LMDE2, so my wine is a little old: 1.6.2

Chris

Glassboy · « **Reply #7 on:** October 14, 2016, 07:22:18 am »

If the target for those mappings is a Windows server, then it could be that support for older versions of SMB has been turned off. Microsoft is pushing quite hard and IIRC disabling things by default.

ChrisMW · « **Reply #8 on:** October 14, 2016, 09:29:39 pm »

In both cases it maps to the Linux host, Wine supports drive mappings and Virtualbox does also. It's the same location, but I use mappings because vary long names can cause Windows to barf on occasion. And to even things out, I wanted the path to be equal, in length, drive letter. I tested using Wine Explorer to determine I can see and read the file, using the same path. Notepad under wine opens the files. So I think I can rule out a permission issue. As Wine is not windows, I would not immediately assume that it is something Wine has turned, where Windows 7 hasn't.

Glassboy · « **Reply #9 on:** October 17, 2016, 07:11:10 am »

Personally I think how well SAMBA implements CIFS is over hyped. I'm yet to see a version that doesn't present quirks to the client.

ChrisMW · « **Reply #10 on:** October 17, 2016, 07:26:08 am »

The point being, under windows 7, running under VirtualBox, connecting to the Linux host, it works. This is something VB aranges for, Just like under Wine, there's a mapping facility. AFAIK I don't even run samba, I don't share files that way. So I'm not getting the point you're making....sorry

Glassboy · « **Reply #11 on:** October 17, 2016, 09:57:02 am »

Quote from: ChrisMW on October 17, 2016, 07:26:08 am

The point being, under windows 7, running under VirtualBox, connecting to the Linux host, it works. This is something VB aranges for, Just like under Wine, there's a mapping facility. AFAIK I don't even run samba, I don't share files that way. So I'm not getting the point you're making....sorry

My impression is that Virtualbox uses SAMBA for CIFS. I could be wrong.

Eve · « **Reply #12 on:** October 17, 2016, 10:11:58 am »

Chris,

I suspect that the recursive code import is going to come down to Wine misbehaving in some way. It's likely we are using different functions to list files than Wine explorer.

~~What version of Wine are you using?~~ I see you're using Wine 1.6.2. Any chance you can try with a newer version of Wine? We generally assume a more recent version than that.
Does the recursive code import fail on older versions of EA with the same Wine version?

Also, I notice black rectangles next to tree icons. We saw those during the beta against XP and Vista, but thought they were corrected. What build of EA are you using now? What Windows version is Wine set to? (run winecfg)

Yes, the floating windows do always seem to be drawn when changing desktops. I've assumed that's a Wine issue... but maybe we could find a way around it.

ChrisMW · « **Reply #13 on:** October 17, 2016, 05:23:15 pm »

I'll check with an older version, would 12.1 be ok? or older?

I run LMDE, which is Debian+, I would have to see how to build it from scratch. I run a 64bit Linux, and wine is a little tricky to setup in that environment, so it might take time.

I've set Wine to be Win7 as a default standard. it made little difference, although I did have it still at XP when I installed. AFAIK the main difference is that the black lines started to show up further down the tree, but I could very well be mistaken. I've also noticed that sometimes you need to drag elements using the black bar, if you want them on a diagram. Hadn't paid too much attention to it, the workaround is pretty easy.

Will let you know.

ChrisMW · « **Reply #14 on:** October 17, 2016, 07:07:51 pm »

Under 12.1 I still get the black bars to the left of the icons and the import seems to be processing more files, but the net effect is the same as with 13, no classes...

Trying EA 10

Sparx Systems Forum

News: