Syndicate the Cosmos Blog Feed.

Known Bugs and Issues

Milestone 2 user kit issues:

The Milestone 2 user kit contains some issues which are fixed in the dev kit, and will be fixed in Milestone 3 :

  1. Invalid Opcode - On some runs you may receive an invalid opcode after booting Cosmos. Simply rerun again. On slower machines the frequency of this occurrence is quite high, often 75%+ on my 1.2 GHz machine, while it occurs less than 5% of the time on my quad core machine. This has been fixed for Milestone 3. If you wish to develop further, please install the developer kit (our live source) instead of the user kit which also has this fix included.
  2. Vista Users - The current release by default tries to write to the program files directory during build. This fails on Vista. Workarounds:
    1. Change the folder during install and install Cosmos to a writable directory such as a sub folder of the Documents and Settings Folder.
    2. Copy the complete Cosmos directory including all sub directories to a writable directory, and update Cosmos registry key (search)

Switching from user to dev kit:

If you decided to switch from the user kit to the dev kit, it is possible that you experience a issue where the build procedure fails. That's because the build procedure searches for assemblies(which are required for correct building) in the wrong directory.

There is a easy way to fix this problem:

Go to \Users\<Username>\AppData\Roaming\Cosmos and open the file "BuilderConfig.xml". Now search for the BuildPath entry and change it to <dev kit folder>\Build\ . Now, everything should work fine.