[Important Note: You are now at the download section of the Squeak Swiki, the primary source for information about Squeak]
The latest stable Squeak version is: Squeak 3.5
For previous versions see here: (3.4),(3.2),(3.0).
How to read the following table:
The table is organized by major platforms and provides entries for particular items on each platform. If there is an entry for "full" then this is all you need to download to get going. If not, you need to download both, the "image" and the "stable VM" package.
The columns in the table mean:
info is a link to more information about this port, typically hosted by the primary developer of this port. For more specific information about Squeak downloads see below.
stable: The latest stable Squeak version known and tested for this platform.
full: A package containing "everything you need to run Squeak". If a full package is available for your platform, you don't need anything else.
image: A package containing the image, changes, and sources file. These files are cross-platform but require an appropriate platform specific virtual machine; see the next column.
stable VM: A package containing the latest stable virtual machine for this platform and Squeak version.
VM source code: A package containing the source code to (re)compile the virtual machine. The latest VM code can be obtained by going to the VMMaker page.
The info in front of each row is a link to more information about this port, typically hosted by the primary developer of this port. For more specific information about Squeak downloads see below.
Scroll right, or resize your browser, to see the entire table.
No matter what system you are on you will need to end up with these four files to run Squeak X.Y:
SqueakX.Y.image
SqueakX.Y.changes
SqueakVX.sources
Squeak VM for your system
The first three files are platform-independent. The fourth file is the interpreter, or virtual machine (VM), and you must get one that is intended for your particular computer. For Acorn, Macs, Windows, and some Unix systems there are full packages containing all necessary files above.
If you need to download individual files or older versions of Squeak, see one of the following sites:
If you have trouble starting Squeak for the first time, try the following:
By far the most common problem is that the files were downloaded in "text mode". The symptom is that a compressed ".sit", ".zip", "tar.gz" or similar file can't be decompressed. This is because add of the linefeeds have been turned in to carriage returns. The downloading program is trying to do too many favors for you. Another symptom is that Squeak runs, but the source code of every method is gibberish. This means the file SqueakV3.sources had linefeeds inserted into it.
In both your fetching utility, and your decompressing program, set the preference to "binary" instead of "text" mode.
Download a complete set of all files you need. Make sure these files are OK and are not touched by any download problems. I recommend downloading a Stuffit, Zip, or Tar file (depending on your preferred platform) since the compressed files usually have checksums. Uncompressed files are sometime modified by helpful OSs, and this corrupts it for Squeak. If you download stuff from the web you should always do binary download. If you don't know how to do this, use Fetch, or another FTP program.
Decompress the files in a single folder. There should be four files now: SqueakX.Y.image, SqueakX.Y.changes, SqueakVX.sources (the "X.Y" stands for the version) and the Squeak program itself (named differently because of platform specifics, e.g. Squeak.exe on Windows).
Assuming you're using a Windows or Mac like UI, drag the file "SqueakX.Y.image" onto the Squeak VM itself. You probably already know about starting programs on your machine.
Look what's happening. If you get messages such "Squeak could not find the file xxxxxx" then you haven't put all of the files in the right folder. In general, you should not get such a message. If you do, something is wrong.
If the system seems to to start up with a blank screen showing only a complaint about not finding the source file, check that the SqueakVX.sources file is in the same folder as the VM.
If the system seems to to start up with a blank screen showing only a complaint about not finding the changes file, check that the SqueakX.Y.changes file is in the same folder as the SqueakX.Y.image file.
If you use the Squeak Class Browser and the bottom pane is blank, it often means that Squeak cannot find the SqueakVX.sources file. Perhaps it is not in the same folder as the virtual machine.
Try the graphics/sound examples in the "Welcome to Squeak" Window. If they work, things should be fine. If they don't it's time to ask for help.
