Jump to content
Slice

Wine development reasons

31 posts in this topic

Recommended Posts

Hi all,

 

There are two reasons to open Wine development at this place.

1. There are problems and bugs in Wine that specific to Hackintosh and can't be discussed with wine developers.

2. They works under LGPL license that is really {censored}. It slows down development, it prevents from brain-storming, it rejects doubtful sources, it rejects for example DXTn textures support because wine developers fear US patents on this format. For my mind wine may support it. It is games developers problem if they can use such textures but it is not a restriction for drivers to interpret them.

So, I want to create wine engine including best patches and technologies even thou official wine can't do this.

 

Better license for my mind is Boost license. They also {censored} on LGPL.

 

I already on the way. My latest engine is

Can be used with updated Wineskin Wrapper

 

I called my project "Wine Sherry"  :thumbsup_anim:

Share this post


Link to post
Share on other sites
Advertisement

hi..

 

may be the name could be "beer" or "tequila" or "cachaça", so the "wine"guys can not even sue you, using the name "wine"..

 

but, with any name, it is a great project..

c.frio

Share this post


Link to post
Share on other sites

OK, let it be simple "Sherry".

 

Now some words about Hackintosh specific bugs.

They come mostly from unsupported hardware, namely videocards even thou such card works without problems with full QE/CI/OpenGL/CUDE etc.

Wine sources contains a list of cards that can be found in real Macs.  :whistle:

Hackintosh users have much more variants. (AMD HD7850 with devID=0x6819 for example). The DeviceID can be corrected by DSDT or by Clover's function "FakeID" but it is not enough.

My AMD HD6670 with devID=0x6758 look native. But no! OpenGL drivers see it as "Turks XT Prototype" and wine can't understand such identification.

This is first Hackintosh specific patch.

 

Second patch is old known "AMDSpeedHack". Without it games in OSX

  /* MacOS dx9 GPU drivers more GLSL vertex shader uniforms than supported by the hardware, and if
   * more are used it falls back to software. While the compiler can detect if the shader uses all
   * declared uniforms, the optimization fails if the shader uses relative addressing. So any GLSL
   * shader using relative addressing falls back to software.
   *
   * ARB vp gives the correct amount of uniforms, so use it instead of GLSL.
   *
   * In addition, AMD Radeon HD GPUs advertise > 256 constants and can support this in HW, but the
   * driver nevertheless falls back to software if more than 256 are used. This is fixed in MacOS
   * 10.8.3 */

But wine developers tell that there are no real Macs with the combination of conditions. Moreover the hack leads to other problems.

I investigated what are the problems and correct this patch.

Look speed in 3DMark2001 in 10.7.5 with non-Apple Nvidia 7300LE cards

                      Wine <-> CX   <-> Sherry
Game2 Low details     30.8 <-> 28.1 <-> 41.4
High details          28.2 <-> 16.8 <-> 28.2
Vertex shaders         8.3 <-> 19.8 <-> 29.9
Advanced Pixel Shaders 4.8 <-> 37.2 <-> 39.2

Share this post


Link to post
Share on other sites

I seems to understand.

Although Wine is open-source but Crossover is a commercial product. As some developers from Codeweaver company works on Wine they don't want free package will be successful. They want CX will be better.  :angry:

Share this post


Link to post
Share on other sites

I will wait for one more developer. Go to hibernate.

Slice... If needed I can open the repo to be public...

Let me know

 

ErmaC

Share this post


Link to post
Share on other sites

I think yes. We have no unlawful contents here.

Ok I will perform the changes and the github repo will be public.

 

EDIT:

 

Done!

Now the repo is public.

Also Slice is the admin of the repo.

 

ErmaC

Share this post


Link to post
Share on other sites

Will you guys make this project into an app, for ease of use for us non-programmers?

The state of Wine on Mac OS X is the last thing that keeps me from deleting Windows.

I know that with your efforts and your new techniques and knowledge, Wine for OSX might get to be even better than Wine for Linux, which I have used a lot, and is pretty buggy.

Share this post


Link to post
Share on other sites

Will you guys make this project into an app, for ease of use for us non-programmers?

The state of Wine on Mac OS X is the last thing that keeps me from deleting Windows.

I know that with your efforts and your new techniques and knowledge, Wine for OSX might get to be even better than Wine for Linux, which I have used a lot, and is pretty buggy.

What do you mean "easy to use for non programmer"?

See, these are windows applications that looks and can be launched as ordinary Mac applications.

Is it easy enough?

Снимок экрана 2016-02-20 в 22.34.07.png

 

 

PS. Sherry inside.

Share this post


Link to post
Share on other sites

Wow! I thought Wine on Mac OSX was still pretty experimental! It looks real good! Keep up the good job :D

What I meant was easy to install for a non coder.. I dont like too much when I have to build from source.. I can do it but it is hard..

I cannot wait till you release the app, so that we dont have to compile at every update..

Share this post


Link to post
Share on other sites

I uploaded 7z archive containing binaries ready to use in MacOSX.

 

The keyword is "Wineskin". Google what is it, how to download and how to use.

Next step is "How to apply custom engine to wineskin".

The custom engine is Sherry.

Share this post


Link to post
Share on other sites

I uploaded 7z archive containing binaries ready to use in MacOSX.

 

The keyword is "Wineskin". Google what is it, how to download and how to use.

Next step is "How to apply custom engine to wineskin".

The custom engine is Sherry.

Wow i didnt know, great job

Share this post


Link to post
Share on other sites

is this needed ? Now we have

Intel® Virtualization Technology for Directed I/O (VT-d) on skylake. can't wait to update my hardware to test it out. 
 
But anyway, if you can get wine sherry working that would be great, to entirely bypass os. Nice. Will test it.

Share this post


Link to post
Share on other sites

 

is this needed ? Now we have

Intel® Virtualization Technology for Directed I/O (VT-d) on skylake. can't wait to update my hardware to test it out. 
 
But anyway, if you can get wine sherry working that would be great, to entirely bypass os. Nice. Will test it.

 

What about Haswell ? Any way tomake VT-d work well with Haswell?

Share this post


Link to post
Share on other sites

What about Haswell ? Any way tomake VT-d work well with Haswell?

No. chipset and cpu has to support it. full gpu acces within virtual machine. yes :)

Share this post


Link to post
Share on other sites

its windows emulator.

 

installed wineskin. copied your engine ~/Library/Application\ Support/Wineskin/Engines

created blank wrapper.

 

Let's try something basic. WinRAR

post-39112-0-30773900-1456402434_thumb.png

 

 

kinda works. 32bit exec. only.

Share this post


Link to post
Share on other sites
fixme:process:start_process Wine Sherry 1.9.4 is a testing version based on WineHQ.
err:process:create_process L"Z:\\Users\\duffs\\Desktop\\winrar-x64-531.exe" not supported on this installation (x86_64 binary)
Application could not be started, or no application associated with the specified file.
ShellExecuteEx failed: Bad EXE format for Z:\Users\duffs\Desktop\winrar-x64-531.exe.

err:wincodecs:PngDecoder_CreateInstance Failed reading PNG because unable to find libpng16.16.dylib
err:menubuilder:convert_to_native_icon error 0x80004005 getting frame 0
err:wincodecs:PngDecoder_CreateInstance Failed reading PNG because unable to find libpng16.16.dylib
err:menubuilder:convert_to_native_icon error 0x80004005 getting frame 0
err:wincodecs:PngDecoder_CreateInstance Failed reading PNG because unable to find libpng16.16.dylib
err:menubuilder:convert_to_native_icon error 0x80004005 getting frame 0
err:wincodecs:PngDecoder_CreateInstance Failed reading PNG because unable to find libpng16.16.dylib
err:menubuilder:convert_to_native_icon error 0x80004005 getting frame 0
err:wincodecs:PngDecoder_CreateInstance Failed reading PNG because unable to find libpng16.16.dylib
err:menubuilder:convert_to_native_icon error 0x80004005 getting frame 0
err:wincodecs:PngDecoder_CreateInstance Failed reading PNG because unable to find libpng16.16.dylib
err:menubuilder:convert_to_native_icon error 0x80004005 getting frame 0
err:wincodecs:PngDecoder_CreateInstance Failed reading PNG because unable to find libpng16.16.dylib
err:menubuilder:convert_to_native_icon error 0x80004005 getting frame 0
err:wincodecs:PngDecoder_CreateInstance Failed reading PNG because unable to find libpng16.16.dylib
err:menubuilder:convert_to_native_icon error 0x80004005 getting frame 0
err:wincodecs:PngDecoder_CreateInstance Failed reading PNG because unable to find libpng16.16.dylib
err:menubuilder:convert_to_native_icon error 0x80004005 getting frame 0
err:wincodecs:PngDecoder_CreateInstance Failed reading PNG because unable to find libpng16.16.dylib
err:menubuilder:convert_to_native_icon error 0x80004005 getting frame 0
err:wincodecs:PngDecoder_CreateInstance Failed reading PNG because unable to find libpng16.16.dylib
err:menubuilder:convert_to_native_icon error 0x80004005 getting frame 0
err:wincodecs:PngDecoder_CreateInstance Failed reading PNG because unable to find libpng16.16.dylib
err:menubuilder:convert_to_native_icon error 0x80004005 getting frame 0
err:wincodecs:PngDecoder_CreateInstance Failed reading PNG because unable to find libpng16.16.dylib
err:menubuilder:convert_to_native_icon error 0x80004005 getting frame 0
err:wincodecs:PngDecoder_CreateInstance Failed reading PNG because unable to find libpng16.16.dylib
err:menubuilder:convert_to_native_icon error 0x80004005 getting frame 0
err:wincodecs:PngDecoder_CreateInstance Failed reading PNG because unable to find libpng16.16.dylib
err:menubuilder:convert_to_native_icon error 0x80004005 getting frame 0d

error. do i need something. libpng.

 

don't know how to make shourtcut to winrar. Custom executable launcher works but how to put it in /Applications folder. 

 

 

Share this post


Link to post
Share on other sites

its windows emulator.

 

Wine Is Not Emulator

 

You should do the follow (sorry for absent step by step instructions)

1. Download Wineskin Winery. Launch it.

2. Install one Wine engine that proposed by Winery. Quit.

3. Go to ~/LibraryApplication Support/Wineskin.

4. Place here WS9WineSherry64 - this is essential if you want 64 bit.

5. 

cp -R ~/Downloads/WrapperUpdate5/* ~/Library/Application\ Support/Wineskin/Wrapper/Wineskin-2.6.2.app/Contents/Frameworks/

6. Start Winery again.

7. Create new blank Wrapper with Sherry engine.

This wrapper will be able to start 64bit Windows applications. 

libpng-64 included into WrapperUpdate5 unlike libraries provided by native Wineskin.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

×