Use http://pastebin.com/ (or equiv.) for copy -> paste.
Do not post wine logs in forums.
Keep post relevant to running or getting the application to run
Only relevant and well descriptive links allowed.
WINE has no trouble with Starcraft and Broodwars' copy protection. If you've installed it and still get the "Insert Starcraft CD" message, make sure your CD-ROM drive is listed in your config - and that it's marked as a CD-rom drive, not a local hard drive.
1) run wine config (winecfg)
2) Click drives. If yours isn't listed, Add it.
3) Select your cdrom drive, click show advanced, then set type to CD-ROM drive.
4) Hit "OK" to save and exit.
If this changes your the drive letter that it was installed from, you might have to run regedit, and manually update this registry key: "HKEY_LOCAL_MACHINE\Software\Blizzard Entertainment\StarCD" to reflect this.
HOWTO - Multiplayer
To get ipx network support, IPX will have to be enabled in the kernel, and you need some userspace
utilities, usually called ipx-utils; and IPX must be started (there
should be an initscript).
(change eth0 for the name of your ethernet/wireless card)
The frame type (802.2) needs to be equal for everyone. It is
recommended to use ethernet II instead of 802.2. If playing with
computers with Windows, make sure their frame type is set to what you
have, and not 'automatic'. It may cause issues if you forget it.
if you update the game to 1.15.2 then you can also play using UDP
Cure for slowness
If the game runs slow on your machine then look at this page
Use the key "DirectDrawRenderer" and add that to your registry with the value "opengl"; you may also need to add the key "RenderTargetLockMode" with the value "readtex".
(Found under HKEY_CURRENT_USER/Software/Wine/Direct3D using regedit)
If the above trick does not work, or causes your Starcraft to crash on launch:
- Remove the DirectDrawRender registry entry.
- Use your Wine Configuration utility to set Emulate Virtual Desktop to on, resolution 640 x 480.
After updating to the latest version, copy over the big "install.exe" from the CDs, and rename them "StarCraft.mpq" and "BroodWar.mpq" depending on which CD you get them from.
If that does not work, you can still try the old method:
First, put the CD in!
If you've already installed it, great. If not, go do that.
Then, do this on the command line:
dd if=/dev/cdrom of=~/BroodWar.iso
To mount this image of the CD:
sudo mkdir /media/iso0 sudo mount -o loop ~/BroodWar.iso /media/iso0
Using winecfg, add a new drive that points to /media/iso0, and give it the type CD-ROM.
Finally, run StarCraft.exe in your program files and you're done! Whenever you want to mount it again, just do:
sudo mount -o loop ~/BroodWar.iso /media/iso0
When you're done and don't feel like keeping it mounted, just do:
sudo umount /media/iso0
If you have any issues still with StarCraft complaining about no CD
being inserted, make sure the iso mount point you made is configured as
a CD-ROM device in winecfg, and make sure you have already mounted it
The following comments are owned by whoever posted them. WineHQ is not responsible for what they say.
cure for slowness on intel hardware
by JoSch on Saturday December 7th 2013, 2:01
For me, starcraft was always playable on my intel graphics systems without problems with speed. This changed after wine version 1.3.27 (which was still working) and specifically with commit 94ae743e (see bug#35032). This commit changed the default renderer from gdi to opengl. In contrast to the suggestion that is made in the description above, the cure for slowness for me is not to use the opengl renderer (which is now the default) but the gdi renderer instead. So in HKEY_CURRENT_USER\Software\Wine\Direct3D set "DirectDrawRenderer"="gdi"
This issue seems to be only present on intel graphics hardware. Using latest mesa from git (10.0+ at the time) did not fix this issue of slowness with the opengl renderer.
Also note that some versions after 1.3.27 have problems with the gdi renderer. For example with 1.5.7 (specifically after commit befdbbd9) starcraft crashes when the gdi renderer is used. This is fixed in 1.5.12. Later, with 1.7.2 (specifically after commit 6325f3dd) the starcraft window will only be a black rectangle when the gdi renderer is used. This issue is not yet fixed but there exists a patch by Henri Verbeet fixing this problem with the gdi renderer in bug#35032 called "gdi fix".
It loads the starcraft.exe into memory, disables the CDROM-checking code and then passes control to the process.
Some kernels might have enabled ptrace protection, which causes the toxicLoAdEr.exe to fail with cryptic message "error writing to process memory" and following message in /var/log/kern.log:
ptrace of non-child was attempted by: wineserver
You can read more about the ptrace protection over here:
To disable the ptrace protection use following command:
sudo echo 0 > /proc/sys/kernel/yama/ptrace_scope
This information is relevant for me (and probably to other players as well). Please leave the comment.
by Nil Choudhury on Monday May 6th 2013, 15:13
There is no Direct3d directory as directed by that "Cure for slowness" section of this page. It seems that the tips given at the top of this page don't reflect the newer versions of Wine. I am using 1.5.29 right now, game has become choppy (offline) and I am unable to play online due to a graphics bug (the same bug causes the game to freeze up when I try to take a screenshot. I have to do a hard restart of the computer afterwards).