Space Exploration Dev 7 (Default branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News Space Exploration Dev 7 (Default branch)
# 1  
Old 09-18-2008
Space Exploration Dev 7 (Default branch)

ImageSpace exploration is a work in progress RPG. In SE, you are tasked with charting the long-abandoned Serpens Sector, a region of space reached through a wormhole near Earth. Each star system you visit brings you an encounter with something: ancient ruins, other humans, and many dangers. The map and encounters are chosen at random for each game, which means that each game plays out differently. The intention is to release the base game for free, and create expansion packs for sale.License: FreewareChanges:
This release adds nebulae and a fuel limit, and has new encounters and many bugfixes.Image

Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

6 More Discussions You Might Find Interesting

1. AIX

How to increase space /dev/hd4?

A check disk space and find /dev/hd4 used 99%. How to increase space. Thank you for advice. /home/tecsys > df Filesystem 512-blocks Free %Used Iused %Iused Mounted on /dev/hd4 1048576 20624 99% 5977 68% / /dev/hd2 6815744 653032 91% 59194 ... (4 Replies)
Discussion started by: yapcs88
4 Replies

2. What is on Your Mind?

Is Unix/Linux used in space exploration?

I was looking at some Wikipedia articles on spacecrafts and robotic probes and found a reference of an OS named "VxWorks" which I have never heard of before; according to the article this OS has been used in a few NASA projects. So now I'm wondering what OS flavor or branch all those amazing... (8 Replies)
Discussion started by: verdepollo
8 Replies

3. SCO

Insuficient space on /dev SCO 5.5

Unix SCO 5.5 Insuficient space on /dev - when I run df I get /dev 99% usage. I have a large number of users (most of them are not with the company since Cretacic) and I want to delete them to make more space. When I run rmuser I get rmuser: not found if I type su root rmuser rmuser: The... (6 Replies)
Discussion started by: tzveistein
6 Replies

4. SCO

No space on /dev/hd 1/42

No one is able to log in. What can I try? Help!:( (1 Reply)
Discussion started by: ibqti
1 Replies

5. UNIX for Advanced & Expert Users

NOTICE: HTFS: No space on dev hd (1/42)

If somebody solve this error please help me! Thanks in advance! :confused: (7 Replies)
Discussion started by: FCollet
7 Replies

6. SCO

No space on dev HD (1/42)

Good Evening to all, I am having a problem with our unix server, I give you a little history. last we the logins started getting slower and slower, when we tried to print nothing came out on the network printer, the system had an error ("printer file close error unit=0). Checking... (3 Replies)
Discussion started by: berkmillionare
3 Replies
Login or Register to Ask a Question
emulate_branch(3)					     Library Functions Manual						 emulate_branch(3)

Name
       emulate_branch, execute_branch - branch emulation

Syntax
       #include <signal.h>

       emulate_branch(scp, branch_instruction)
       struct sigcontext *scp;
       unsigned long branch_instruction;

       execute_branch(branch_instruction)
       unsigned long branch_instruction;

Description
       The  function  is  passed  a signal context structure and a branch instruction.	It emulates the branch based on the register values in the
       signal context structure.  It modifies the value of the program counter in the signal context  structure  (sc_pc)  to  the  target  of  the
       branch_instruction.   The program counter must initially be pointing at the branch and the register values must be those at the time of the
       branch.	If the branch is not taken the program counter is advanced to point to the instruction after the delay slot (sc_pc += 8).

       If the branch instruction is a `branch on coprocessor 2' or `branch on coprocessor 3' instruction, calls to  execute  the  branch  in  data
       space to determine if it is taken or not.

Return Values
       The  function returns a 0 if the branch was emulated successfully.  A non-zero value indicates the value passed as a branch instruction was
       not a branch instruction.

       The function returns non-zero on taken branches and zero on non-taken branches.

Restrictions
       Since is only intended to be used by it does not check its parameter to see if in fact it is a branch instruction.  It is really a stop gap
       in case a coprocessor is added without the kernel fully supporting it (which is unlikely).

See Also
       cacheflush(2), sigvec(2), signal(3)

								       RISC							 emulate_branch(3)