Jump to content

  • Log in with Facebook Log in with Twitter Log In with Google      Sign In   
  • Create Account


Member Since 26 May 2009
Offline Last Active Dec 28 2017 06:15 AM

#106777 Wineskin Engine Repository

Posted doh123 on 24 June 2017 - 10:34 AM

I'll try to get stuff added to Winery when I can.

Was in a motorcycle wreck and busted up really bad, and long road to recovery... all surgeries done now, and starting to recover more.... sorry if seem even more slow than normal.

Thanks for doing builds!

#106453 Wineskin Engine Repository

Posted doh123 on 27 February 2017 - 02:51 AM

View PostIncredible Hulk, on 25 February 2017 - 10:29 AM, said:

Also there is now a Wineskin Xcode project on Github


Don't know who is the maintainer and if this is legit?

its not "Legit" as in officially anything to do with Wineskin.  I assume someone has made a fork... maybe they want to work on it some.  Hopefully if they improve anything they'll submit the changes to me.

#106401 Wine STAGING & CSMT Builds - Engines Available

Posted doh123 on 14 February 2017 - 07:13 PM

View PostGurqn, on 27 December 2016 - 09:26 AM, said:

Actually, I did, and it's possible outside of the wrapper. However, in order to get a wow64 engine with wineskin, the wrapper should have support for that. I've shared some information on my previous posts.



I don't really know what support is needed... is this just about the dylibs being 32 bit?  The goal of Wineskin is to make it like a ported app... so for me, I'd rather have only what is needed there and not some general wrapper that can run anything.  So if I was running a 64 bit app, I'd use 64 bit engine.

#105175 Crossover 15.0.1 Custom

Posted doh123 on 23 January 2016 - 01:10 PM

View PostNRG, on 23 January 2016 - 11:32 AM, said:

I would like to understand ...
it tells you in the error.
programs/winedbg/resource.h:23: error: distversion.h: No such file or directory

line 23 in that resource.h file.

#105170 Crossover 15.0.1 Custom

Posted doh123 on 22 January 2016 - 10:06 PM

I just built and uploaded WS9Wine1.9.2 and WS9WineCX15.0.1

#104096 Wineskin Winery Update?

Posted doh123 on 29 July 2015 - 12:29 PM

Winery installs a master wrapper for you… which is Wineskin 2.6.0 right now.  All the updates your talking about would be in that wrapper, and it would just be say Wineskin 2.6.1 or 2.7.0 or whatever… and Winery itself wouldn't change.  If you manually change things in your 2.6.0 master wrapper (~/Application Support/Wineskin/Wrapper/Wineskin-2.6.0.app/Contents/Frameworks), then it will go into all newly made wrappers after that.

#102445 Getting around a Winemac feature?

Posted doh123 on 03 September 2014 - 10:55 PM

some wild guesses... I'd assume you could just ignore how thats working and make it read in any plist you want... just giving it a full path, or relative from the executable location.  Maybe also read in the wrappers Info.plist to pull what info is needed, or even combine the NSDictionary objects if somehow the winemac driver has one.  I really am not sure totally how the winemac driver works with an Info.plist since its not a standard app bundle.

#102128 Update on Wineskin / Cider in Mac OS X 10.10 Yosemite

Posted doh123 on 05 July 2014 - 03:51 AM

Right now I know of no benefit of dropping 10.6 support.  There were issues with 10.5 which really helped in dropping support... same reason XQuartz also dropped 10.5 and is 10.6+

I have no plans of dropping 10.6 until some major reason comes up, or I have no choice.

#101649 Can anyone help me make a batch file?

Posted doh123 on 05 May 2014 - 05:45 PM

just make a text file called "somename.bat"

inside it put something like this...

start "c:\Program Files\SomeFolderName\First.exe"
start "c:\Program Files\SomeOtherFolderName\Second.exe"
then put that .bat file inside the wrapper somewhere, and set it as your main exe file... and make sure that the "use start.exe" is checked.

#101398 Wine STAGING & CSMT Builds - Engines Available

Posted doh123 on 12 April 2014 - 11:34 AM

I'd say one extra thing... put your 10.6 SDK at the older location... /Developer/SDKs

This is so when Xcode.app gets updated, you don't get your SDK wiped out.  Winery will look in this location first for the SDK.

#101377 Wineskin --> Cider (Batman Arkham Origins)

Posted doh123 on 10 April 2014 - 02:27 PM

10.6 has AMD/ATI graphics driver issues you cannot fix.  This will always show up in Wine usage.  Apple only fixed these bugs in later OS releases... and never for 10.6.  You do know 10.6 -> 10.9 upgrade is free right?

#101215 Hello, I need a little guideline help.

Posted doh123 on 25 March 2014 - 12:35 AM

View PostDankoB, on 24 March 2014 - 09:19 PM, said:

The fact that it calls on .NET does not sound promising though. If you still have your Windows license you can install Bootcamp on a partition and access Windows that way or install Parallels (a virtual machine application for Mac OS X)
Actually .NET could actually make it easier since you could just make sure its all compatible with Mono and not need to change much.

View PostPersonal Hayabusa, on 24 March 2014 - 10:05 PM, said:

I delved into the issue better today. What I could conclude is exactly what you said ("... you go through line by line and replace ...", "... start from the ground up and replace all ..." ... ). I know little about the UNIX-like systems, in particular, also I am a newbie on Mac OS X. We can say that I have to read up deeply on Mac OS and Xcode documentations. The hard part,  I suppose, is figuring out what the "counterparties" functions, libraries, ... of MS are for Mac OS. I'm beginning to think that maybe I should learn very well how the Apple operating system works and then rewrite my source codes from scratch.
Sometimes there is a lot more to it than just changing commands to something that works with the systems current frameworks... sometimes they work so differently you have to change around the logic of how the code operates.  Basically, I'd take it one method/function at a time... if it has a certain input and a certain output, just make sure those are still the same.  Some things can get harder, like if there is heavy use of DirectX which would need major changes.

I'm not big on system specific code, so you may want to look into the most cross-platform code you can.  One way people do that is using Mono, which is an open source implementation of .NET.  If you make your code for Mono, it makes it easy to get it on multiple platforms.  The only reason my main code for Wineskin is OS X specific, is because the software really has no use beyond OS X, since its designed just to run Windows programs on OS X.

#101177 Help?

Posted doh123 on 23 March 2014 - 03:06 AM

you mean 1280x800 ? or 1440x900?

In game resolutions shouldn't change unless a mod changed them...

#101164 Wineskin 2.6.0 Beta

Posted doh123 on 21 March 2014 - 07:46 PM

Short lived beta 2... I put up a RC1 now.

Wineskin 2.6.0 RC 1 !

Fixes in RC 1

  • the Uninstaller button in Wineskin.app should work now if the wrapper was already running when it was pushed.
  • Running multiple tools in Wineskin.app should work with the Mac Driver
  • Running multiple CustomEXEs should work with the Mac Driver
  • Kill Wineskin Processes button will correctly kill processes just for the given wrapper, and clear up the lock file, without affecting other running wrappers of any type.
  • Winetricks update should be parsing Descriptions correctly to always get the English version
  • The D3DBoost checkmark should function properly now
  • Wineskin.app should load much quicker if the set EXE is not found when you try to launch the wrapper.

#101152 Wineskin 2.6.0 Beta

Posted doh123 on 20 March 2014 - 09:44 PM

View PostDankoB, on 20 March 2014 - 07:48 PM, said:

*edit...seems to be working great after a refresh. The only issue I came across was that the menubar name appears as WineskinWineskinDefault3324. I tried it out with an application that uses multiple windows. I reacted exactly as it does with Wineskin2.5.12. So far so good.
Thats the default menu bar name... its *supposed* to change it to the App Name if its ever set here... I made it mainly to do it during wrapper creation, so the wrapper creation bug from Winery is probably helping that.