• Seethings
• Contacts
• pictures
• Videos
• Areas
• Team

• ASPECT: Team 
• - [coding] XYZ
• - [graphician] XYZ   

• ASPECT: Photos
• - [photos:dev] yxcyxcv
• - [photos:team] sadf 

• 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
•  

• 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.

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.

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

• Default Inser-Line (L)
• Commands (K) - Commands : Shift-Function > The command
• Graphics (G) - Create the char with graphics (First Shift Graphics > Shift Key)

• Tilebase is simple to use. Create the tiles and just say here is TileA, titleB.
• Tilebase save space (######) - important in the beginning
• Tilebased could be used for creating games (Labyrinths) with Sprites in front
• You can create very fast new levels
• The hardware has often tilebased background support 
• Seamless tiles create very fast interesting backgrounds and foregrounds … 

• We have people, who worked (appropriation) in those days >1960 with Computers 
• We have people, who are working today with old hard-, software and games (Shared memories). 
• We have people, who work today with old hard-, software and games from scratch (emulation included).
• We have people, who create today with old hardware new software and games. 
• We have people, who create today hard-, software, pictures, films and games in the style of yesterday.
• We have people, who are working with fantasy computers & consoles today. 

Apples erste Mac-Generation nutzte ihn. Der Amiga wurde von ihm inspiriert und um ihn entwickelt, wie auch der Atari ST. Der MC68000-Prozessor von Motorola wurde der Standard für die Homecomputer-Nachfolge der legendären 8-Bitterund zeitweise eine ernstzunehmender Alternative zu IBM-PCs.

"Motorola's Advanced Computer System on Silicon" war der sperrige Name, unter dem 1976 die Entwicklung des MC68000 und damit der Ursprung der 68k-Generation begann. Motorola orientierte sich beim Architekturdesign an den legendären IBM360-Mainframes, allerdings mit linearen Adressbereich; die Entwickler scherten sich auch sonst nicht um alte Zöpfe der frühen CPU-Entwicklung, sondern schnitten sie einfach ab.

• Snake
• Music Programm
• Question: Gaming at EPFL?
• Answer: Learning Coding
• Animation (Future of video?
• Hand-Punchard System
• Multimedia-Hardware

• 2 modes - text and graphic mode
• difficult ram organisation for graphic mode
• difficult to paint text (no routine)