138 replies to this topic

[devilhunter]

I made a fresh SL install on my mac mini, and would gladly test out various wrappers if you'd like.
I repartitioned my drive last week for a little Snow Leopard test System, on which i'm trying out different stuff.
You have my e-mail address if i recall...

btw - it should be possible for CoreDuo Mac users to launch Chromium out of the box on 10.6 because the CD CPU uses a 32Bit architecture so basically it shouldn't be possible to execute perl in 64Bit mode in the first place.....

just a random thought. xP

Heh, didn't think of that. That could theoretically work, but it's not limited to Core Duo macs. hackintosh users (hmm, now where to find those...) with P4 chips/Core Duos or the like can also try this out, since these chips are not 64bit capable. But maybe these things are too old for SL, i'm not up to date anymore. Anyone of you guys that managed to get SL running on these chips wanting to test that?

[jimjimjimbob]

where are all these crazed SL maniacs when you need 'em...?

I'm happy to try anything! I've downloaded your wrapper and I'll try some ports with it (CX Games Wrapper 8.0.app) - I'm not sure if you meant this one to be the finalish one.

I tried porting a game using the wrapper and it worked a treat! I've tried it with a few games so far with no real problems other than a few I found using CX normal version 8.0.

I launched it in 32Bit mode - is this what we should do or is there a fix so we don't have to with the wrapper?

[thedoctor45]

check your PM's - both of you

if you don't want to use terminal.app to launch the wrapper you have to make yourself a launcher script like I described in the previous post.
But only if both wrappers I just made fail to run of course.

PS: don't forget to delete the prefs folder!

cheers
thedoctor45

[devilhunter]

I'm happy to try anything! I've downloaded your wrapper and I'll try some ports with it (CX Games Wrapper 8.0.app) - I'm not sure if you meant this one to be the finalish one.

I tried porting a game using the wrapper and it worked a treat! I've tried it with a few games so far with no real problems other than a few I found using CX normal version 8.0.

I launched it in 32Bit mode - is this what we should do or is there a fix so we don't have to with the wrapper?

I'm not quite sure if the startup problem is only PERL related. Why does Codeweavers recommend thinning out the quartz-wm before starting CX in 32bit Perl mode? I think there has to be something else here.

Basically we need a wrapper that works without tweaking anything.
You have already altered your quartz-wm so you currently can't correctly test this i think.
If you want to have the same circumstances that all other SL users have, you need to reverse the process that you made with the terminal commands previously.
Luckily you made a backup of the quartz-wm with 'sudo mv quartz-wm quartz-wm.bak', so replacing the thinned out version with the backup is possible.
Otherwise you're making ports that no other SL user can run, because they didn't use the terminal commands.

Just a thought.

[thedoctor45]

just give it a try right now, we can figure out the details afterwards.

[jimjimjimbob]

Basically we need a wrapper that works without tweaking anything.
You have already altered your quartz-wm so you currently can't correctly test this i think.
If you want to have the same circumstances that all other SL users have, you need to reverse the process that you made with the terminal commands previously.
Luckily you made a backup of the quartz-wm with 'sudo mv quartz-wm quartz-wm.bak', so replacing the thinned out version with the backup is possible.
Otherwise you're making ports that no other SL user can run, because they didn't use the terminal commands.

Just a thought.

I did think of this but it escaped my mind before I really put it into action. I've zipped both and stored them and I've reverted back to the old one now for testing.

I get this using Final

Loading GLX bundle glxCGL.bundle (using Apple's OpenGL)
Display mode: Rootless Quartz -- Xplugin implementation
PseudoramiX screen 0 added: 1280x779 @ (0,21).
PseudoramiX screen 0 placed at X11 coordinate (0,0).
[DRI] screen 0 installation complete
Screen 0 added: 1280x779 @ (0,21)
Screen 0 placed at X11 coordinate (0,0).
can't open default display

And this using Perl

Loading GLX bundle glxCGL.bundle (using Apple's OpenGL)
Display mode: Rootless Quartz -- Xplugin implementation
PseudoramiX screen 0 added: 1280x779 @ (0,21).
PseudoramiX screen 0 placed at X11 coordinate (0,0).
[DRI] screen 0 installation complete
Screen 0 added: 1280x779 @ (0,21)
Screen 0 placed at X11 coordinate (0,0).
can't open default display

They both then quit.

[thedoctor45]

did you try both quatz-wm files, with and without the 32-bit command?

does it always crash?

also remember the prefs folder!

[devilhunter]

Tried it also, both quit with and without the 32bit Perl command.
I'm only using the standard quartz-wm file.
Jim, how's the thinned out version behaving?

[jimjimjimbob]

Changing Quartz back to the edited one with perl I get:

_XSERVTransmkdir: Owner of /tmp/.CrossOver should be set to root
Loading GLX bundle glxCGL.bundle (using Apple's OpenGL)
Display mode: Rootless Quartz -- Xplugin implementation
PseudoramiX screen 0 added: 1280x779 @ (0,21).
PseudoramiX screen 0 placed at X11 coordinate (0,0).
[DRI] screen 0 installation complete
Screen 0 added: 1280x779 @ (0,21)
Screen 0 placed at X11 coordinate (0,0).
dyld: warning, DYLD_ setting caused circular dependency in /Volumes/Windoze Stuff/Work in Progress/8-0/Perl/CX Games Wrapper 8.0 Perl.app/Contents/SharedSupport/X11/lib/libGL.dylib

And then with Final

_XSERVTransmkdir: Owner of /tmp/.CrossOver should be set to root
Loading GLX bundle glxCGL.bundle (using Apple's OpenGL)
Display mode: Rootless Quartz -- Xplugin implementation
PseudoramiX screen 0 added: 1280x779 @ (0,21).
PseudoramiX screen 0 placed at X11 coordinate (0,0).
[DRI] screen 0 installation complete
Screen 0 added: 1280x779 @ (0,21)
Screen 0 placed at X11 coordinate (0,0).
dyld: warning, DYLD_ setting caused circular dependency in /Volumes/Windoze Stuff/Work in Progress/8-0/Final/CX Games Wrapper 8.0.app/Contents/SharedSupport/X11/lib/libGL.dylib

This is both just running it straight - they then crash. When telling them to run in 32Bit using the terminal thing they both work fine.

To confuse everyone further (sorry!) using the original quartz and telling it 32Bit gets the "can't open default display" error.

also remember the prefs folder!

We may (well... I) sound like amateurs but we're not I've still got the good old script that deletes them for me

[devilhunter]

Hm, i thought so.
So not just the Perl command can be used, thinning out the quartz-wm is necessary.
Back to square one, but now we know more.

[jimjimjimbob]

Hm, i thought so.
So not just the Perl command can be used, thinning out the quartz-wm is necessary.
Back to square one, but now we know more.

At least we've got a fix for the old games and people can still play them on 10.6

[thedoctor45]

so that means we're stuck here.

too bad - looks like thinning out quartz-wm and using a launcher script is the only option for now.

I'm out of ideas - any suggestions guys?

[devilhunter]

By the way, is it me or is Snow Leopard launching the CX ports insanely fast?
I'm talking about 2 seconds here flat from cold start. In Tiger and Leopard it takes bloody ages.
Can you confirm this jim?

I'm out of ideas - any suggestions guys?

Sadly, no.
My hopes rest on the macosforge for a backwards compatible xquartz...
Their SL Roadmap is currently at 80% done, we'll see if this brings out anything useful.

[jimjimjimbob]

By the way, is it me or is Snow Leopard launching the CX ports insanely fast?
I'm talking about 2 seconds here flat from cold start. In Tiger and Leopard it takes bloody ages.
Can you confirm this jim?

Definitely! It was the first thing I noticed - I usually click it to launch and then go and write an email or something waiting for it to load but not any more! I'm guessing something to do with GCS or the way SL sorts out the threads.

[MoDFoX]

Where is it that defines what executable is launched?
I always thought it was the "CrossOver Chromium" in the info.plist, but after changing the name it didn't affect it at all.
If I can tell it where it is, I can possibly make a temporary fix.

[devilhunter]

It's the 'Executable file' string in the Info.plist. This line doesn't accept anything else than the name of the mac os unix executable in the Mac OS Folder.

[slacker25]

im currently back on windows but will be fixing soon so i should be able to throw in with ya guys and hopefully get snowleopard working

[MoDFoX]

It's the 'Executable file' string in the Info.plist. This line doesn't accept anything else than the name of the mac os unix executable in the Mac OS Folder.

I don't think it is, I deleted the string and it worked fine.

[TheDoh123]

Doh123, just check out the cached page of it!

http://74.125.93.132...p;client=safari

I also attached a word document that looks prettier. Enjoy!

thanks!

[Macintosher]

Hey guys,

I'm glad I found you on here, I am very sad that the forum is down, but I got some good news for ya, I have found someone who's willing to sponsor the game porting team and pay the monthly hosting fees . Could anyone of you forward this to loco? Unfortunately, I don't have his email address...

Best wishes,
Macintosher