• don't write specs. Users should consider themselves lucky to get any programs at all and take what they get.
• don't comment their code. If it was hard to write, it should be hard to read.
• don't write application programs, they pro- gram right down on the bare metal. Application programming is for feebs who can't do systems programming.
• don't eat quiche. Real programmers don't even know how to spell quiche. They eat Twinkies, Coke and palate-scorching Szechwan food.
• don't draw flowcharts. Flowcharts are, after all, the illiterate's form of documentation. Cavemen drew flowcharts; look how much it did for them.
• don't read manuals. Reliance on a reference is a hallmark of the novice and the coward.
• programs never work right the first time. But if you throw them on the machine they can be patched into working in only a few 30-hours debugging sessions.
• don't use Fortran. Fortran is for wimpy engineers who wear white socks, pipe stress freaks, and crystallography weenies. They get excited over finite state analysis and nuclear reactor simulation.
• don't use COBOL. COBOL is for wimpy application programmers.
• never work 9 to 5. If any real programmers are around at 9 am, it's because they were up all night.
• don't write in BASIC. Actually, no programmers write in BASIC, after the age of 12.
• don't document. Documentation is for simps who can't read the listings or the object deck.
• don't write in Pascal, or Bliss, or Ada, or any of those pinko computer science languages. Strong typing is for people with weak memories.
• know better than the users what they need.
• think structured programming is a communist plot.
• don't use schedules. Schedules are for manager's toadies. Real programmers like to keep their manager in suspense.
• think better when playing adventure.
• don't use PL/I. PL/I is for insecure momma's boys who can't choose between COBOL and Fortran.
• don't use APL, unless the whole program can be written on one line.
• don't use LISP. Only effeminate programmers use more parentheses than actual code.
• disdain structured programming. Structured programming is for compulsive, prematurely toilet-trained neurotics who wear neckties and carefully line up sharpened pencils on an otherwise uncluttered desk.
• don't like the team programming concept. Unless, of course, they are the Chief Programmer.
• have no use for managers. Managers are a necessary evil. Managers are for dealing with personnel bozos, bean counters, senior planners and other mental defectives.
• scorn floating point arithmetic. The decimal point was invented for pansy bedwetters who are unable to 'think big.'
• don't drive clapped-out Mavericks. They prefer BMWs, Lincolns or pick-up trucks with floor shifts. Fast motorcycles are highly regarded.
• don't believe in schedules. Planners make up schedules. Managers 'firm up' schedules. Frightened coders strive to meet schedules. Real programmers ignore schedules.
• like vending machine popcorn. Coders pop it in the microwave oven. Real programmers use the heat given off by the cpu. They can tell what job is running just by listening to the rate of popping.
• know every nuance of every instruction and use them all in every real program. Puppy architects won't allow execute instructions to address another execute as the target instruction. Real programmers despise such petty restrictions.
• don't bring brown bag lunches to work. If the vending machine sells it, they eat it. If the vending machine doesn't sell it, they don't eat it. Vending machines don't sell quiche.

MOVE.L  #1000,A0       ;bring address in A0          
MOVE    #1,(A0)        ;write 1 into this address

RECORD: 
  DC.W 2                ;number of entries -1                  
  DC.W 1,2,3            ;elements of list

CLR.L   D0            ;erase D0 completely                   
MOVE.L  #RECORD,A0    ;address of list in A0                   
MOVE    (A0),D0       ;number of elements -1 in D0                   
MOVE    1(A0,D0),D1   ;last element in D1                   ...           
RECORD: DC.W 2                ;number of entries -1                   
DC.W 1,2,3            ;elements of list



CMP  #2,D1
CMP   #2,D1      ;comparison,or subtraction
                 BNE   UNEQUAL    ;branch,if not equal(Z flag not set)
                 MOVE  #0,D2      ;otherwise execute D2=0
        
          UNEQUAL:

 T        true,corresponds to BRA
          F        false,never branches
          HI       higher than                   C'* Z'
          LS       lower or same                 C   Z
          CC,HS    carry clear,higher or same    C'
          CS,LO    carry set,lower               C
          NE       not equal                     Z'
          EQ       equal                         Z
          VC       overflow clear                V'
          VS       overflow set                  V
          PL       plus,positive
          MI       minus,negative
          GE       greater or equal              N*V N'*V'
          LT       less than                     N*V' N'*V
          GT       greater than                  N*V*Z' N'*V'*Z'
          LE       less or equal                 Z   N*V'   N'*V

 ---------------------------------------------------
      Bcc     Label         conditional branch,depends on condition
      BRA     Label         unconditional branch(similar to JMP)
      BSR     Label         branch to subprogram.Return address is
                            deposited on stack,RTS causes return to that
                            address.
      CHK     <ea>,Dx       check data register for limits,activate the
                            CHK instruction exception.
      DBcc    Reg,Label     check condition,decrement and branch
      JMP     Label         jump to address(similar to BRA)
      JSR     Label         jump to subroutine.Return address is
                            deposited on stack,RTS causes return to that
                            address.
      NOP                   no operation
      RESET                 reset peripherals(caution!)
      RTE                   return from exception
      RTR                   return with loading of flags
      RTS                   return from subroutine(after BSR and JSR)
      Scc     <ea>          set a byte to -1 when condition is met
      STOP                  stop processing(caution!)
      TRAP #n               jump to an exception
      TRAPV

• most games - you play not act 
• qix no
• pac man - somehow but too hard
• moon lander? no really
• asteroids no
• galaxy - some visual aspect - mukokuseki
• missile command no 
• atari 2600 porno games no
• klax arcade - chain
• frogger
• most shootenup (space invader - war visuals) 
• lemmings? dark behind the nice graphics
• battle chess - reanalog - brutal
• demoscene? biggest part - yes
•  

1. Program/file name: Ideally, all uppercase and followed by one space. Carriage returns are ignored in this file.
2. Version number: In the format "v1.123", followed by a space.
3. ASP number: Only if an actual ASP member, otherwise ignored.
4. Description separator: A single short hyphen "-".
5. Description: The description of the file. The first two lines should be the short summary, as older boards cut off the rest. Anything beyond that should be extended description, for up to eight lines, the official cut-off size. Additional text could be included beyond that but might not be included by the board.

1. as Computers create staff
2. as Consoles
3. you could pirating easily software games included
4. the 16-bit consoles had mouses and guis. easier to use.

Facts

• TTV1 was the first file-based Amiga virus
• Its creation was a fun experiment. It was inspired by the boot block based SCA virus which had reached dubious fame due to its very successful spreading and the flaw of overwriting the boot block. Would it be possible to create a self spreading file, thus breaking out of the boot block dread?
• Development took place between spring and fall 1988.
• The early code name was HOUZ virus.
• Thinking up the name we tried to find something that would sound mean and at the same time on the verge to ridiculous. The final name was inspired by a rap band called The Terrorists.
• The virus does not harm the system. In fact, care was taken to avoid any even unintentional damage.
• Identity of the authors was kept secret for 30 years. It was officially revealed on March 9, 2019 at the Demonights 008 event in Bern Switzerland
• "The names have been changed to protect the innocent" shown in the message was inspired by the song Beat Dis by Bomb the Bass. They have sampled it from the Dragnet radio series.
• The "BGS9" was in fact a clone. Its code is almost identical even including the resident name "TTV1". It got more reach and thus was regarded as the origin.

About the life of the beast

1. TTV1 installs itself as a reset proof resident module (KickTag/ROMTag) named "TTV1"
2. On reset the resident module (virus) is called
3. Execution gets delayed in order to gain disk write access. Therefore Intuition's OpenWindow function is redirected.
4. As soon as the AmigaDOS tries to open the CLI window the OpenWindow gets called the virus looks for the startup-sequence on the booted disk
5. The virus is looking for the first command (A) in the startup-sequence
6. File request windows (e.g. "Disk is write protected") are being temporarily disabled
7. Virus renames A to $a0202020a02020a020a0a0. This is a combination of none breaking spaces and spaces. The idea is that the user will oversee this "invisible" file.
8. Virus writes itself as an executable command with the name of A to the disk
9. Eventually A gets loaded and executed with all its parameters by the virus

Musée Bolo owns one of the most extensive collection of machines and objects related to information technology and its brief history.

• No curriculum there for information technology > ETH Mathe/Physik > Pascal (Mathem. Algorithmen) > Speicherung Lochkarten
• Firma  (Cobol) PDP11
• …

Installation

• Show colors
• Show good graphics
• show a lot of sprites!
• hast do be somehow 3d
• not really graphical design … 

• Tilebased
• Too fast
• not yet solved - TargetFields constantly