Getting Starcraft/Brood Wars 1.13f to work under FC5, Cedega 5.2

2006 August 16
by darkness

I was helping someone get Starcraft working in this environment earlier. Here’s a rough account of problems we hit, and how we fixed (or worked around) them:

  • freetype support is on by default. Install cabextract, then install the MS fonts like:

    CABEXTRACT_PATH=`which cabextract` \
    /usr/lib/transgaming_cedega/transgaming_fontinstaller/tg-font-install
    

    Run this as a regular user. (I ran everything about Cedega as his regular user, except for the installation of the RPM.) This makes ~/.transgaming_global/Fonts. Hopefully you can see this gets linked to the C:\Windows\Fonts directory inside your Cedega game directory.

    At this point, the installer (which wasn’t working prior to this) should run.

  • Don’t forget to switch sound to ALSA. I changed the PCM device to default, turned off mmap, turned on “Full Duplex.”

  • Install Starcraft from the CD. The installer exits kind of abruptly, but it seems to work.

  • Install the Starcraft 1.13f patch.
  • Install Brood Wars. The installer will again abruptly exit.
  • If you go look in C:\Program Files\Starcraft (~/.cedega/Starcraft/c_drive/Program Files/Starcraft/ for me) you’ll see a Temp directory. mv everything out of the Temp directory into its parent directory, overwriting any existing files.
  • We installed the game with a loopback mount of the ISO. To play the game we had to define a drive in Cedega. The only place I found to make this change, and make it stick, was in ~/.cedega/.global.delta, which is almost certainly the wrong place (being global, for one, which I take to mean “applies across all games”). The entries I made looked thusly:

    [Drive G]
    "Type" = "cdrom"
    "Path" = "/mnt/loop0"
    "Label" = "STARCRAFT"
    "FailReadOnly" = "y"
    
    
    ;[Drive G]
    ;"Type" = "cdrom"
    ;"Path" = "/mnt/loop1"
    ;"Label" = "BROODWAR"
    ;"FailReadOnly" = "y"
    

    The semicolons are comment characters, so he has to uncomment whichever game he wants to play.

Inexplicably, this seems to work. The version on the version screen says 1.13f. However, we haven’t tried playing Brood Wars yet. This slightly bizarre set of steps was necessary: I’d usually install SC, install BW, then patch them with the Starcraft Brood Wars 1.13f patch. However, the SC/BW 1.13f patch wouldn’t run on his system, throwing up various errors.

Hopefully both SC and BW will play with other 1.13f clients. We’ll have to give it a test.

No Comments

Leave A Comment

Note: You can use basic XHTML in your comments. Your email address will never be published.

Subscribe to this comment feed via RSS