S4 League Forum

I downloaded it using crossover, it does install all the way.

But there is always an error with S4 that it fails to open url blah blah.ini

So what usually works on windows xp is opening the patcher from the alaplaya folder from the Programs folder that is from the C Drive.

The way you do that is....  
1) Click Crossover while it's open

2) Hover over configure at the top

3) Click Manage Bottles

4) Choose winxp on the side bar

5) Click Advanced tab

6) Click Open C: Drive.

7) and so on.

I tried doing it on crossover.

The patcher shows up, but disappears after 1 second.

So i try to open it again.

It says the patcher is already running, so I'm waiting right now to see if i need to wait for the patcher to be done.

Hopefully it'll work. Spent hours trying to figure crossover out just for this game.

That'd be great if you guys tried it and figured out something.

This is with crossover (not crossover-games)....correct? Also,
it would be an idea to mention your OS/platform specs, so we
know these things (Mac/linux situations are a little different)

Ok...I did try this (crossover linux, =not= crossover-games) and got around the patcher business,
and it downloaded all the game file updates etc etc, but even then it fails to start.

The patcher/launcher GUI uses ieframe for the display, so it seems you need an IE installed into
the same bottle to get that working..

When you go to start the game, a little splash-logo appears briefly in the bottom righthand
corner, which says "HackShield Pro" ..then it crashes. If this 'HackShield Pro' stuff is
anything like Nsoft's 'GameGuard' technology, it is likely the reason this title won't
start (and if so, this title is unlikely to run 'anytime soon' under crossover/wine, due to
the way 'anti-cheat' softwares like this need access to a real running windows kernel)

Note: I will recheck this later -- the URL's trying to be displayed by the patcher/launcher
were generating 403/503 errors, and a quick check using my system browser revealed the same
errors...so I want to eliminate the possibility the failure is/was somehow network related.