Duke Wiki  logo
Child pages
  • Launching
Skip to end of metadata
Go to start of metadata

Launching Cobalt


To start Cobalt follow the procedure that applies to your computer's operating system.

For Windows:

  1. Unzip the Cobalt zip file.
  2. Open the folder "cobalt-base-current-build-<year-month-day>"  (for example "cobalt-base-current-build-20090113").
  3. Double-click the "Cobalt.bat" file. A black screen will open. (Note: You may see a pop up window with the message "There is a newer version of Cobalt available (20090407). Would you like to download it?" Just ignore this popup and proceed to the next step.)
  4. To launch the Cobalt 3D environment: Drag the blue Cobalt icon located in the lower left side of the screen toward the middle of the screen.

For Macs:

  1. Unzip the Cobalt zip file.
  2. Open the "Cobalt" folder.
  3. Double click the blue Cobalt icon. If you don't see the blue icon look instead for a yellow icon with gear teeth (Note: You may see a pop up window with the message "There is a newer version of Cobalt available (20090407). Would you like to download it?" Just ignore this popup and proceed to the next step.)
  4. To launch the Cobalt 3D environment: Drag the blue Cobalt icon located in the lower left side of the screen toward the middle of the screen. (See screenshot above.)

For Linux:

  1. Unzip the Cobalt zip file.
  2. Open the "Cobalt" folder.
  3. Double-click the "Cobalt.sh" file. (Note: You may see a pop up window with the message "There is a newer version of Cobalt available (20090407). Would you like to download it?" Just ignore this popup and proceed to the next step.)
  4. To launch the Cobalt 3D environment: Drag the blue Cobalt icon located in the lower left side of the screen toward the middle of the screen. (See screenshot above.)
  • No labels

2 Comments

  1. There is a potential problem with NVIDIA video drivers where if the "Threaded Optimization" setting is turned on it could crash Cobalt.  The solution is to adjust the driver settings to to turn this off.

  2. If the browser/viewer should fail to start up after the blue ball is dragged out, the problem is most likely a dispatcher configuration issue.

    I really should document this more, but it's still changing.   There is a file named cobalt-router.conf.   It is read in at viewer startup time and is used to configure the router, dispatcher and the authentication services. It's just a file of Smalltalk code that returns a configuration object as this was the easiest way I could think of to get it working.

    There are 2 stanzas/blocks that matter at for this case, the first is a block that will return a dispatcher configuration and the second is to set up the auth services. In the shipped config, the dispatcher block is setup to configure a Universal Plug and Play firewall hole (if one is available) using the TUpnpDispatcherConfig. The other options are a LAN only config (TLanOnlyDispatcherConfig) and a fully manual config (TManualDiapatcherConfig).  These all can be sent the routerClass: method to set up the kind of router that get spawned on connection. I expect we won't be changing this much but it's been useful for testing. There is also a localAddressString: method they all understand. There are example configuration files illustrating these options in the example-config directory in the Open Cobalt installation.

    The Squeak TCP/IP interface has some problems and doesn't really understand having multiple active TCP/IP interfaces....they seem to have made an assumption that there is only one interface active as would be common in a workstation.  Servers, or a workstation running VMware or Parallels will often have more than one active interface. If you ask for the local interface address, it will give back it's best guess....which is often wrong if you have multiple interfaces.  The localAddressString: method is there to specify the interface we want to advertise, in the cases where the automatic approach is giving us wrong answers.  In the shipped configuration file I have the localAddressString: send commented out, but if Cobalt Master isn't starting up properly try uncommenting it and setting the address string to the IP address you want to use, usually the default interface.  In testing 127.0.0.1 has worked, it just won't let anyone else get a reasonable address to connect to you.

    For the TLanOnlyDispatcherConfig there are no other options.  For theTManualDispatcherConfig there are a bunch of options so you can specify the address on the other side of the firewall and the port numbers.

    The auth services stanza I'm going to leave for later, except to note that the auth service named Local is special and is the service used if a service is not otherwise specified when the controller tries to log in.

    There is also a commentBlock: stanza that does nothing and is useful for commenting out old configurations and putting in inline string comments.