CosmosEx – v2 – quickstart, by tIn.

What you should know before you start

This quickstart tutorial is aimed to help get your stock CosmosEx v2 device up and running. It’s split in three difficulty levels: beginner, intermediate and expert.

If your CosmosEx v2 is a SCSI version, please be advised that it is configured to act as a SCSI device by factory. You have to open up your device and remove two resistor arrays and add a jumper to switch to ACSI mode. See for a walkthrough with pictures. You can’t sitch the modes just by switching cables!

The ACSI only version of CosmosEx v2 is… well, ACSI only.


Please be also advised that your CosmosEx is not working well as an internal Harrdrive in a Mega STE – this is due to Ataris ACSI/SCSI bridge card, which unfortunately only supports one SCSI ID. For full operation you need at least two.


The CosmosEx (or “CE”) is easiest to operate by users that have the following basic knowledge:

  • TCP/IP Networks (e.g. IP adresses and basic DHCP usage)
  • ACSI/SCSI ID allocation

To complete this quickstart tutorial, you need all of the following:

  • an Atari ST/STe/TT or Falcon 030 system
  • a CosmosEx Device (v2 for ACSI/SCSI)
  • an ethernet cable
  • a DHCP server (e.g. router)
  • ACSI or SCSI Cable (ACSI cable is provided with your CE)


For beginners:

  • a HDMI cable
  • a HDMI capable monitor/TV
  • an USB keyboard



  • a Raspberry PI compatible WLAN adapter


The Steps

  1. Start your CE
  2. Access the device
  3. Update the device
  4. Configure the device
  5. Get access to the CE from your Atari
  6. Bliss

Optional: Prepare WIFI

Insert your Raspberry Pi compatible WIFI Dongle into CEs USB port.

Start your CE (beginner)

Connect the HDMI cable to the HDMI port of your CE and to your monitor/TV. Connect the USB keyboard to the CE. Connect the ethernet cable to your CE. Make sure the ethernet cable is connected to the internet (double check e.g via a laptop).

Turn your CE on. The CE boots and in that process, a lot of textual information will show on the connected HDMI device. A boot screen (“Yocto”) displaying a progress bar will show inbetween. Wait until the CE finished booting.

You will see the follwing at the bottom of the screen:

login as:

Start your CE and get access to the CE web interface (intermediate)

Connect the ethernet cable to your CE. Make sure the ethernet cable is connected to the internet.

Turn your CE on. Let the CE boot for about 30 seconds. The blue HD light should flicker a first time and after a few seconds a second time.

The CE should be booted now. Check on your DHCP server/router which IP has been assigned to your CE.

Open your browser and enter your CEs IP. You should see the CEs web interface. Navigate to “Config”.


Skip “Access the device” and proceed with “Update the device”.


Start your CE (expert)

Connect the ethernet cable to your CE. Make sure the ethernet cable is connected to the internet.

Turn your CE on. Let the CE boot for about 30 seconds. The blue HD light should flicker a first time and after a few seconds a second time.

The CE should be booted now. Check on your DHCP server/router which IP has been assigned to your CE.

Open an ssh terminal to your CEs IP.

Access the device

Login to your device using as user “root” with the password “ce”. You should get a command line prompt like this:


Now enter the following:

cd /ce

Now the “Main Menu” should appear on your console. This is the same configuration utility you will be able to access from your Atari later on.

Update the device

Your CE can be easily updated via Internet. Your CE checks on Jookies Website which software versions are the most current. Don’t worry, no data is transmitted except your devices software version numbers – also it only checks the version when you tell it to do so by entering the “Software update” screen.

Then you can decide to update or not. In most cases it is wise to update, as the software is actively being developed with bugs being fixed and feature requests being added.

The configs “Main menu” screen lets you navigate the menu options via cursor keys. Select “Update software”.

CE is build out of several components, which have different version numbers – don’t worry about that, you’ll just update your CE as a whole.

Select “From web”. Given a working internet connection, you should see your current software status vs the newest one on Jookies website. Give it a few seconds.

Now you can decide to “Update” – this process basicly restarts your CE, so don’t worry if you won’t see anything on the screen for a few seconds, it will come back.

After update the “on web” column should show “the same” on all rows. You are ready to configure your device.

Configure the device

ATTENTION: This step is essential to get your CE up and running. Your Atari can’t see your CE until you have completed this step successfully!

First, press return on “ACSI IDs config” (or SCSI depending on your device). The easiest configuration here is:

ID off sd raw ce_dd


You can navigate with the cursor keys to enter this configuration. Press return on “Save” when done.

This configuration means the following:

Every device connected to your Ataris ACSI/SCSI port needs an ID to be able to communicate – to be called by name, so to speak.

Every ID that is “off” in this configuration can be used by other devices other than your CE (see 1). The other IDs are used by your CE, and yes, here it emulates 3 devices in total.

Your Atari normally boots only one device – so if the SD-Card is bootable, the boot process won’t check the following devices. First is the SD card slot (the slot in front of your CE). This will be accessed first and checked for a bootable Atari formatted SD card. Second, there is “raw” – this is used for Atari-formatted USB sticks NOT for DOS/Windows formatted ones.

The third device (ce_dd) is used to autoboot the CE_DD driver. You need this driver to access “translated drives”, drives like Windows formatted USB sticks or Shared Folders.

The Files on these Drivers are basically read by your CE and emulated into an Atari readable device by this driver.

Now your CE knows how to answer when your Atari tries to start a conversation.

Optional: Configure WIFI (expert)

Go to “Network settings” and enter your Wifi-SSID in “WPA SSID” and your WPA2-Password into “WPA PSK”.

You probably should leave “DHCP” checked, but you can enter a fixed IP if necessary.

After saving, the setting should be active after a few seconds. Ping your CEs Wifi IP to check if everything is OK.

Get access to the CE from your Atari

Now power OFF your CE – you shouldn’t connect any device to your ST while that device is powered on.

You can now disconnect HDMI and keyboard again – you shouldn’t need these for the next step. But you might keep them nearby, for troubleshooting purposes.

Connect the SCSI or ACSI cable between your Atari and your CE. Remove any SD card you might have inserted in the front SD slot. Also remove any disks you might have in your foppy drives.

Make sure that only one device (that being your CE) is connected to your ACSI/SCSI port. We don’t want to complicate things just now.

Turn on your CE.

Wait for about 30 seconds for the CE to boot – the HD led should flash a first time and then, after a few seconds, a second time.

Turn on your Atari.

Now the Atari should boot the CE DD driver. This may take a while, because first your Atari might try to access the empty floppy drive.

When booted, your Atari should show you a desktop with the drives A,B and O. Open the drive O.

This drive should contain a set of CE-specific tools. Congratulations, your CE is configured correctly!


Now you can insert a SD card and format it from your ST. Or you can mount a network drive. Or insert an USB stick with software. Or use the web interface. Or connect the floppy emulator. Well, you know, all that.


  • if, for any reason, your CE isn’t booting, download the CE configuration tool from Start this on your Atari and see if it does see your CE. If it doesn’t, re-check your configuration.
  • if the config tool sees your CE, but doesn’t boot, check your SD card
  • if your SD card seems OK, try to configure CE_DD on a lower ID. It should boot first – just to be sure any device boots at all.
  • if none of this is working, try to load a harddisk driver (e.g. ICD,HDDRIVER,PPera driver) from floppy and see if it’s recognizing our CE. Make sure an SD card is inserted.
  • try to change the SD card – not all SD cards are working properly, beware of the cheap ones. Kingston proved to be very reliable so far.
  • if, for any reason, the CE can’t be accessed via network, access it via USB keyboard and HDMI display. Check through ifconfig etc. if the network is up and running.
  • access the web interface and access the debug information page (via the link on the first page). Download the app log. See if anything out of the ordinary is in there.

(1) There are known incidents where CE did not work with other ACSI devices in a chain:

Comments are closed.