Home of Alex Thissen

Programming tutorial: Part 1–Getting Started

Alex Thissen — Thu, 05 Apr 2012 22:02:48 GMT

Atari Lynx programming tutorial series:

Part 1: Getting started

So, you want to develop a game or program for the Atari Lynx, right? Well, join me on my journey to learn how to program for this game console. This tutorial series will be expanded and updated as my knowledge of the platform grows, when feedback from the community is given. Some things in this tutorial might be wrong. Let me know and help grow this tutorial, so people can benefit from it.

I will write this so others can also start developing games. At this point in time I think I will use a set of helloworld-ish samples to explain concepts, but also build a real game to explore the various aspects of Lynx game development. This means that I am not sure how the tutorials will be structured. I anticipate that they will be like living documents that grow and get better content over time.

The ingredients for a game

These are the things you will need to build, test and run your game for the Atari Lynx:

The actual hardware of an Atari Lynx device
A programmable cartridge onto which you can transfer the game and test it in the real Lynx
An emulator to make dry runs without needing the hardware and the time to transfer and test a cartridge
A development environment that can produce the correct 65SC02 code that the Lynx console can run
The idea for a game
Basic understanding of programming
Dedication, patience and perseverance

Let’s briefly look at each one of these.

Actual Atari Lynx device

You probably have one already. Why else would you want to write a game for this device? If not, there are plenty of Lynx console to be bought in your neighborhood or on the Internet. Ebay is probably a good place to start if no one around you has one for you.

There is no particular preference for the Atari Lynx Mark I (Classic) or II model. The games should run on both. The most noticeable difference in the hardware is the support for stereo in the Lynx II, where the Lynx I only has mono sound. The form factors are different as well. Here, there is a slight bias towards the Lynx II, because it has an open cartridge slot that allows for easy insertion of odd-shaped cartridges. This will help with the flashable cartridges as well (see later).

A programmable cartridge

There are a couple of ways to get a game binary image onto a cartridge. One of them is an EEPROM-burner. I have seen these out there. Or you can use the Flashcart by Karri Kaksonen. My personal favorite is the FlashCard by Lynxman. I own one and have used it extensively to try my games on a real Lynx device. Works like a charm and it is highly recommended. It’s affordable. Check with Lynxman for availability and pricing. Make sure you have a Lynx II or are willing to remove the cartridge bay door of your Lynx I.

Emulator to quickly test a game

There are two main emulators out there:

Handy (with incarnations for about every platform and device)
Mednafen (Multi-system emulator based of Handy source code with improvements)

I have always used Handy, but recently found that Mednafen has flawless sound support. It is a bit trickier to use (command-line based), but is well worth checking out.
When you choose Handy, do pick the Developer version, as it includes debugging support and has more features. Pick up the source code for the emulator as well, which is for the developer version. I have written a blog article on how to compile the source for Handy on Visual Studio 2010.

Development environment for building 65SC02 code

In my book a development environment encompasses everything that you need to build games. This ranges from your operating system, to tooling and documentation.

You have got the operating system taken care of already. How else would you be browsing this page? I cannot judge whether this will be the OS for game development of your choice. I know that it is possible to get a working and productive environment for Windows and Linux and not so sure for MacOS. Everything else will have slimmer chances. If you use one of the first two then your in luck. Otherwise you might need to switch. My operating system is Windows, and have nothing against the others. However, I do focus on Windows and Microsoft technology. I will not compare this with other operating systems and manufacturers thereof. You be the judge of what is better.

My list of things for the Atari Lynx development environment:

Documentation

Epyx developer documentation for Lynx.
Available online from Bastian Schick’s website or as a set of scanned TIFF images from Atari Age at the Lynx Archive.
Atari Age Atari Lynx programming forum

Tooling

Compiler, assembler and linker for 65SC02 source code
Text editor and/or GUI for source code and resource files
Framework specifically for creating Atari Lynx games

We’ll get into each of the tooling later on.

The idea for a game

Surely, to develop a game you will need to have an idea of what the game is like. That is not what this tutorial is about. It is meant to give you the knowledge on how to use the platform, hardware, tooling and programming environment to accomplish writing a game. As far as the game is concerned: that is your idea mixed with the things in this tutorial.

Basic understanding of programming

There are so many books, internet sites, people, training companies and schools out there that can teach you how to program, it’s not even funny anymore. If you are not comfortable writing code and haven’t got your head around it yet, this tutorial might not be for you. I do assume you have programming experience and skills. Then again, reading this might help you learn more about programming. You’ll notice if it can help you develop your skills. For me, it has been very educational to program in a low level way, instead of the high level languages and frameworks that I use every day.

Dedication, patience and perseverance

Being a developer of software can be a very rewarding task. Whether it is monetary gain, or personal satisfaction of solving a problem or completing a game, for everyone there is something to be had from developing. If there isn’t you should really reconsider starting development or being a developer.

But, the other side of the medal is that there will almost certainly be moments where things get tough. You might not get the results you want, or not as quickly as you’d like. There will be bugs in your code that you need to hunt down and fix. There is not as much documentation as you will need and the developer community is small to say the least. You have been warned and should be prepared to deal with this. On the upside, take a look at the fun games that the homebrew community of the Atari Lynx has developed the past couple of years. And I must say after having spent a couple of evenings experimenting: it is really fun to program for the Lynx. Amazing what this little console can do. Little code, big results. I am enthusiastic. I hope you are too.

From this point on

This first part has not a whole lot to do with programming yet. But we’ll take it step by step. The next part will cover the various tools that you will need and could use. We’ll discuss the compilers, editors and frameworks. So, stay tuned for more on the Atari Lynx programming tutorial.

Working from Visual Studio 2010 for Vectrex programs

Alex Thissen — Thu, 23 Feb 2012 06:10:28 GMT

For many years I’ve been working with Visual Studio as my main development IDE. I’ve seen many incarnations, since Visual C++ 2.0, through VC++ 2.1, 2.2, 4.0-4.2 and from there also Visual Basic 5.0, 6.0, and Visual Studio.NET, 2003, Visual Studio 2005, 2008 and now Visual Studio 2010 with “Dev11” gleaning at the horizon. Knowing your development thoroughly is a great advantage. I ‘d rather not go back to other editors and/or environments.

That’s why I have created a Makefile project for Visual C++ and hooked up the AS09 compiler for 6809 code.

Preparing the project

You will need to download Visual C++ 2010 Express to do this. If you’re spoiled like me, you might just have a paid version of Visual Studio 2010, which should include Visual C++.

After choosing the Makefile project you can choose a filename for your project. I have named it HelloWorld

A wizard will start that allows you to enter lots of information. Simply press Finish, as you can set this up in another dialog (with some more space for editing).

At the Solution Explorer, you will see the new HelloWorld project. Right-click it and choose Properties.

Go to the Configuration Properties, NMake at the left tree and fill the three command-lines with the following:

"C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\nmake.exe" /f hello.mak BUILD=Debug all
"C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\nmake.exe" /f hello.mak BUILD=Debug all
"C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\nmake.exe" /f hello.mak BUILD=Debug clean

This means that we will have a hello.mak NMAKE file for our compiler to use. There will be two configurations for building, rebuilding (the same for now) and cleaning.

Set the Output to hello.bin. That is the name of the file that we will be producing.

Add a new text file “hello.mak” to the project. You will also need to include the hello.asm file in the root of the project. The result looks like this:

Editing the make file

Open the hello.mak file and copy the following text in it:

.SOURCE :  
.SUFFIXES : .asm .bin
 
AS="C:\Program Files (x86)\AS09\AS09.exe"
ASFLAGS=-cgiv -h0
 
target = hello.bin
objects = hello.bin
 
.asm.bin:
	$(AS) $(ASFLAGS) -l$(BUILD)\$*.lst -o$(BUILD)\$@ $<
 
all: $(objects)
 
clean:
	del $(BUILD)\*.lst
	del $(BUILD)\*.dbg
	del $(BUILD)\$(target)

Explaining the contents of the make file

Let’s take a short look at the individual elements.

.SOURCE is not used, but indicates subdirectories where source code might be located. .SUFFIXES lists the extensions of files that while be recognized.

AS is a shorthand macro for the compiler and the ASFLAGS for the compiler flags.

The -cgiv flags means that the compiler will:

output cycles counts per instruction (c flag, which is relevant in combination with the l flag)
generate debug information (in a separate .dbg file)
be case-insensitive
be verbose in its output

The flag –h0 indicates infinite page length for the generated listing file hello.lst.

Next are the target and objects, which indicate the thing we will produce (target) and which things (objects) are needed to create the target. In this simple case this is the same. More complex scenarios might have other objects accumulating into the target.

The line .asm.bin: and the line after that is a inference rule that tells NMake how to create a .bin file from a .asm file. In this case it is accomplished by:

$(AS) construct the compiler command
$(ASFLAGS) adds the flags to the command
with a listing flag –l at the location $(BUILD)\$*.lst
The last part will expand to something like DEBUG\hello.lst, because the macro BUILD holds the current build configuration (DEBUG or RELEASE) and $* is the current file (from the rule) without an extension (so hello.asm becomes simple).
at the output $(BUILD)\$@ as specified by the –o flag
This will expand to DEBUG\hello.bin, because $@ is the target of the rule (in this case the .bin that needs to be created)
with input file $< that holds the complete filename that is the lefthand side of the rule (hello.asm)

The final sections indicate the all and clean configurations. All is the build configuration that is used for both a normal Build and the Build All. Since we have only one project the two use the same “all” configuration. It will build all objects are indicated by the objects= line. The clean configuration will run three delete commands that get rid of all .lst, .dbg files and the target.

Building the solution

You can now build the project from the Build menu, Build Solution (shortcut is Ctrl+Shift+B). The makefile project will run the NMake utility and feed it the hello.mak file. plus the value “all” to build. The result should be something like this in the Output window:

1> Microsoft (R) Program Maintenance Utility Version 10.00.30319.01
1> Copyright (C) Microsoft Corporation. All rights reserved.
1>
1> "C:\Program Files (x86)\AS09\AS09.exe" -cgiv -h0 -lDebug\hello.lst -oDebug\hello.bin hello.asm
1> AS09 Assembler for M6809 [1.42]. Copyright 1994-2007, Frank A. Kingswood
1>
1> Optimization enabled.
1> Pass 1.
1> 20 lines read, no errors in pass 1.
1> Pass 2.
1> No errors in pass 2.
1> Checking binary file boundaries.
1> Writing binary file "Debug\hello.bin".
1> Wrote binary from address $0000 through $0022.
1> Total size 35 bytes.
1>
1> Reading from file "hello.asm"
1>
1> Reading from file "hello.asm"
========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========

Clicking the Show All Files button at the top of the Solution Explorer reveals the contents of the Debug folder:

where all output is located. Running Clean solution from the Build menu will get rid of the output of the build proces.

More information can be found at the MSDN website.

Hello World with 6809 assembler language

Alex Thissen — Wed, 22 Feb 2012 17:25:00 GMT

The first thing I did after finding the developer information is skim through the Introductionary Tutorial by Christopher L. Tumbler. I want to get a feel for the assembly language, and the way the games for the Vectrex are created. At first glance the code for the 6809 seems reasonably close to the 6502. There are 16-bit registers and instructions that make use of those. Branching is possible with the relative short jump (plus or minus 127 offsets), but also long jumps which take an additional byte.

The code for a typical Hello World program looks like this:

ORG $0000

; Magic Init Block
FCB $67,$20
FCC "GCE XXXX"
FCB $80
FDB music
FDB $f850
FDB $30b8
FCC "SIMPLE"
FCB $80,$0

start:
bra start

music:
FDB $fee8
FDB $feb6
FCB $0,$80
FCB $0,$80

Notice the magic initialization block that is needed for a Vectrex program. The program loops infinitely and plays no music.

I want to get this simple program to compile. So, I started searching for compilers:

AS09 at http://www.kingswood-consulting.co.uk/assemblers/
GCC6809 (C compiler for 6809, so not useful for this code fragment)

I unpacked the AS09 1.42 compiler and copied the Simple.asm file (with the contents above) to the directory.
Compile the source with:

as09.exe simple.asm

As it seems the compiler has some issues with upper case mnemonics. Normally the –i switch should make the compiler case-insensitive, but this doesn’t seem to happen. I’ve contacted Frank Kingswood about this. Changing the ORG, FCB, FCC and FDB to lower-case does the trick for now.

The result of the compilation is a simple.bin binary file that you can run on an emulator like MESS. The syntax for running this is:

mess64.exe vectrex –cart roms\vectrex\simple.bin

where I have run this command from the command-line at the MESS root directory. My roms are stored in the subdirectory roms\vectrex. The required boot rom for Vectrex is also located in that folder.

I have also stumbled on the source code for VecThrust at the website of Ville. This will be interesting later on.

Scavenging the internet for Vectrex information

Alex Thissen — Mon, 20 Feb 2012 15:37:58 GMT

These are the first interesting links that I found roaming the Internet:

http://en.wikipedia.org/wiki/Vectrex
The Wikipedia page for the Vectrex. Has some history and tells about the working of the device and the 3D imager and light pen.
http://www.vectrex.biz/
Richard created the VecMulti and VecFlash cartridges. The first one seems to be able to host different kinds of cartridges, as it mentions 64K bank-switched games. Uses a Micro-SD card as the backing store.

The VecFlash is discontinued and seems a precursor to the VecMulti.
http://www.vectrex.co.uk/
Has information on the VecDev developer cartridge and some modifications like the resetting after uploading a game to the cartridge. Cartridge is supposed to be available from Vectrex.biz but it is not mentioned there I think.
Also, under Documents/Data sheets it has a lot of technical information on the electronics inside the Vectrex. Most importantly I found the Vectrex FAQ here, plus the programming manuals and a tutorial.
Vectrex museum http://www.vectrexmuseum.com/
Complete overview of the original, prototype and homebrew games. Interesting news section. Also has a section with programming documentation.

A new thing

Alex Thissen — Sun, 19 Feb 2012 20:11:19 GMT

Time to try something new. I want to see if I can commit to write blog posts and keep some form of diary as I go about creating a blog on building a Vectrex emulator and maybe a game in the process. Usually I try to find out things on some topic and explore everything, but never get around to writing about it. I will try to do it the other way around. It’s an experiment, but it’s worth a shot.

Initial goal formulation:

Create a modern Vectrex emulator for the managed .NET platform

So, with that said, time to do some initial high-level planning (aka lying) and summarize some things that need to be done.

Find general information on the Vectrex
Find technical and developer information
Find out what the technical components of the Vectrex are
Understand the way the Vectrex works
Understand the programming language for the CPU
Understand the boot process
Emulate CPU, memory and electronics for video
Try to get visuals from the vector graphics
Do the audio, controls and other hardware
… (we’ll see where we stand when we get here)

To make this work I will try to brain dump instead of going for complete, error-free, correct, article-like writing. That means it will be a diary of progressing insights. You’ve been warned.

On with the experiment.

Revelations on Windows 8

Alex Thissen — Wed, 14 Sep 2011 18:32:13 GMT

Today the //BUILD/Windows conference started with a day full of main sessions. A two and a half hour keynote followed by three “Big Picture” sessions after lunch introduced all present to the new Windows 8 OS and platform. Personally, I am still catching my breath over the amazing amount of information that was given to us. Lots of people have asked me since then what I thought of the first day. I have told them: “Fantastic”. Here’s why, in my words and with a personal interpretation of the information that is available to everyone.

Merging the web with Windows

What I saw Microsoft present today is the new vision for the Windows 8 operating system. Windows 8 merges with the web in terms of devices and applications. It also brings together all your devices and makes them a mesh that is constantly in sync with one another. This mainly goes for data, be it application data, application settings or identities. The Cloud (Windows Live in particular, complemented by Windows Azure) acts as the conduit to flow and store information across devices and online storage.

Web of applications

Equally important is the fact that all applications are not only interconnected with the OS and the cloud, but also with one another. Searching and exchanging data has become a smooth continuum across OS and applications alike. I like to think of it as a new opportunity to create Windows-based mashups, just like it has become common place for Web 2.0 applications. This style of creating applications will now come to native Windows applications. The possibilities will be endless. All you need to do is reimagine your apps, just like Microsoft has reimagined Windows.

A new family of applications

Windows 8 distinguishes two types of applications: Desktop apps and Metro style apps. The Desktop apps are best described as the applications that will run on earlier versions of Windows (7, Vista, …). The Desktop can be built using the well known variety of APIs, ranging from native Win32 in C/C++, to .NET or Silverlight with C# or VB and HTML with JavaScript for Internet Explorer hosted web applications. Metro style applications are easily identified from their styling. Behind that new appearance there is a whole new stack of frameworks and APIs to build and run applications. The Metro applications can interconnect with each other and the OS. There is deep integration through the new API.

Metro, great for users and developers

Metro applications use a new application model at system service level. This is the layer that runs on top of the Windows kernel. The application model also represents the way a Metro application lives in its eco-system, hooks into the operating system with its own execution environment and how it is packaged and deployed. On top of the app model you can build Metro apps with three new APIs: Data and Communication, Graphics and Media, Devices and Printers. You can choose from any kind programming interface, just like with the Desktop apps, boiling down to C++, managed languages and JavaScript. The first two use XAML to create the view layer. XAML has become a native part of the operating system.

Whether you are going for the XAML or HTML5 approach, Metro apps have the same distinct look and feel, backed up with styling guidelines. The Visual Studio 2011 development environment embraces Metro and offers a whole slew of templates to facilitate in creating the right Metro views for your app.

The Metro style will help users get a consistent feel across devices (desktop PC, tablet or phone) and form factors (small, medium, large). Whether they pick up a phone with WP7.5 or a tablet with Windows 8, it all looks and feels the same. For now, Metro style applications are built targeted at either Windows 8 or Phone 7.5

Opportunities for everyone

With all of this come great opportunities for everyone: users, designers, developers, architects and business, you name it. Since this is a developer conference, I would like to point out that the next couple of years will be very, very interesting for developers. The shift in programming paradigm from rich-client, high-end client applications to interconnected, cloud- and os-integrated applications are a new ball-game and a game changer to boot. This will give lots of change, chance and learning for all to enjoy.

The extra gift

As if all of this goodness and announcements weren’t enough there was the unexpected gift. Secretly anticipated and living up to speculation all attendees of //BUILD/Windows were giving a new Developer Preview Tablet: a Samsung tablet with amazing specs. The line for picking it up was unbelievable. I chose to wait until tomorrow to pick it up. I still need to do so. Everybody is excited about it. Check the specs to see why.

Getting ready to unwrap the big picture at BUILD

Alex Thissen — Tue, 13 Sep 2011 05:47:11 GMT

Tomorrow is the first day of the //BUILD/Windows conference. BUILD is a highly anticipated conference and expectations are equally high. I thought it would be good to put some of my thoughts on my blog before the conference actually started. You see, BUILD is special in a way that most conference of the past years have not been: we know nothing about the announcements. Sure, there will most likely be information on Windows 8, HTML 5 and JavaScript, the developer roadmap and so on. But then again, this is only high over. Nobody knows anything about what will be announced, not even the average Microsoft employee.

The almost complete silence and accompanying secrecy is not what we have seen in the past couple of years. Microsoft has always been very open in its directions. The product teams have engaged with the community early on and gotten feedback from the developers, architects and so on. Now, we have heard nothing up front. And this leads to a lot of speculation, criticism, fear and doubt. People complain about this approach. Apple and Google have been working this way for a long time now. The big announcements and revelations are made on an important conference. So, how bad is it that Microsoft has taken the same path?

Taking a step back I feel spoiled. All these years we have had the luxury of knowing all upfront. It is like Christmas time (or Sinterklaas if you are Dutch), where you sent out a wish list to Santa Claus. Santa would tell you exactly what you would get. The unwrapping of the presents was fun to do, but there were hardly any surprises. This time is different. Tomorrow we will be given a lot of presents and we do not know what is in the boxes. Everyone will be thrilled to receive the gifts and find out what is inside. Best of all, there might even be presents that we hadn’t wished for. I am enjoying every moment of it. Because once the unwrapping is done, the nervousness and anxiety goes away and is replaced with the fun of playing with the new stuff. Still good, but different. Who knows how long it will be before we will have the experience of not knowing again?

The registration today went very smooth. It was not busy (yet). The self-service terminals made it easy to register. The badge, wristband (for the party on Wednesday) and booklet were all the things we got. There were no details on the sessions, other than that the first day will be general sessions only. These general sessions are called “Big picture” in the booklet. Sort of indicates what we will getting from those. The breakout sessions are from Wednesday till Friday. It will be four fantastic days without a doubt. I am looking forward to it!

Dracula the Undead walkthrough

Alex Thissen — Tue, 19 Jul 2011 06:50:00 GMT

Below follows the complete solution to the graphical adventure on your Lynx, Dracula – The Undead.

Included are all the possibilities of exploration available in the game. You need not go through the list of commands given below. Stick to the bold commands and only execute the others if you're interested in seeing what happens. Omitted are the commands that result in remarks like 'there's nothing unusual about it.' or 'I don't think that'll work'. Some are quite interesting (and that's the main reason I included them), since they more or less show the path of exploration you might have followed solving the game yourself. For instance, when you first try and climb out of the window in Jonathan's antechamber he doesn't believe it possible, whereas when he has seen Dracula do it, he does climb out, convinced it can be done.

Use the map in combination with the italic headers. The headers give the name of the location where you should be or move to before trying any of the actions given below them. If you would want to finish the game as quickly as possible, you should only execute the commands printed in bold.

A note of caution: if something happens, like an animation of some sort or a narration by Bram Stoker, and the list prompts you to use notebook, make sure you execute no other command. If you do, you might not be able to finish the game victoriously. Sometimes, however, you might be lucky if you accidently execute a false command, because in some instances you can examine something again and then use the notebook (like at Dracula's coffin or in his study).

On the other hand

Finishing the game in only two days (more like one) after about three go's I really started wondering whether the solution given below is the only one. If you've read the original novel by Bram Stoker (which I can really, really recommend for all you English books readers or students who need a good book for their reading list), you find that the DRACULA - THE UNDEAD only covers about a seventh of the novel. Some arguments to confirm my doubts: in the sewing room where you fall asleep and nearly get killed by the three brides you come across several objects I cannot seem to use in any way. There are more of those unusable objects, by the way. Furthermore, most doors that are locked can be opened later on in the game. Some, however, not. What about the coins you carry, but do not seem to need? Although being warned several times to escape before the brides 'claim you with their voluptuous kisses' I never got killed by them.

I imagine this to be the result of always having broken open the window of Jonathan's bedroom, so I could exit the room later in the game, when the door to the antechamber from the bedroom is locked. Does anybody know if this is really so? And last and certainly not least: if you happen to have GAMEZONE issue four handy, look on page 91, the LYNX previews. You'll notice a picture from the DRACULA game showing Jonathan bending over Dracula in his coffin, stake in hand pointing towards Dracula's chest. The text reads: 'Finding a handy stake he is ready to end Draculas reign of terror.' I certainly did not find this picture anywhere in the game, so where did it go? Cancelled in a later version because Atari ran out of memory on the card, or did I miss out on a part of the game?

Walkthrough (Spoiler alert)

The actual walkthrough is too long for this blog post. I have uploaded it to the Media area of this blog.

You can find the PDF file for the walkthrough here.

Completing Chip’s Challenge game

Alex Thissen — Mon, 18 Jul 2011 14:52:47 GMT

To be honest, I do not remember whether I completed the Atari Lynx game Chip’s Challenge myself back at the time. Anyway, yesterday evening I sat down, looked up the level start code for the final level and gave it a spin. I quickly realized that I either had to use every memory muscle in my brain to finish this level, or make some notes. Well, some notes turned into a complete level map. Here is the layout of the final level:

You start off at the place where Chip is shown. You first need to get the four keys to consecutively open the yellow, blue, red and green door. Then you head into the teleporter and find out you need to shove some bricks/boxes, brown thingies. Easy enough, except: underneath some of the boxes is fire, roasting your fine, nerdy buttocks. By trial and error you can find out which ones are safe to use, which ones are not. You will have to remember those. That’s possible because there is no randomization involved. You will have to try each and every box until you find the exit to finish the game behind one of them.

Spoiler alert!!!

You can save some time looking at the map below. It shows what is beneath a box, if something is there at all. So the fire indicates hotness beyond your ability to handle. The question marks will say: “This spot would be too obvious!”. Finally, the exit is shown to be at the top row, slightly off to the left side of the middle (second block from the middle). Here’s the map with the locations:

Once you reach the exit, you are welcomed by the end sequence. Melissa is hugging you for completing this quest and takes you to the prom “E-prom”.

For your entertainment I also uploaded a speedrun of the level to Youtube.

Speedrun of level 149 “Special” of Atari Lynx game Chip’s Challenge

Have fun!

Using WCF and WIF to perform WS-Trust active claim requests

Alex Thissen — Mon, 18 Jul 2011 14:07:39 GMT

The last week I have been working on a claim-based identity scenario that involves two separate instances of a Active Directory Federation Services (ADFS) 2.0 as Security Token Service (STS). The first STS is an identity provider STS (IP-STS) and the second a resource STS (R-STS) . The R-STS and IP-STS have a trust relationship in that the IP-STS is a trusted identity provider to the R-STS. Typically this setup is used with the passive profile for federation from browser clients. The web application (SharePoint 2010 for our scenario) would require authentication, redirect to the R-STS, which in turn would redirected (after IP selection) to the IP-STS. Here the end-user will authenticate, gets a identity claims from the IP-STS and is redirected back to the R-STS. The resource STS can augment claims from information stored in AD Lightweight Directory Services (AD-LDS) and issue the final claim token to the passively federated web application.

In our case we have a SharePoint 2007 application, which does not have its own STS to initiate the entire process. Also, business requirements demand that

the user interface is completely controlled
no redirects to other pages during authentication
authentication takes place from within a certain screen flow

These requirements made us investigate the active profile flow for the setup. In an active profile flow you will use the web services of ADFS 2.0 to communicate directly to the STS instances. You can use either the WS-Trust or WS-Federation protocol depending on your requirements. WS-Federation allows you to call the R-STS directly with the retrieval of the IP-STS claim performed under the covers. WS-Trust is used for the individuals steps. You can also leverage WS-Trust to take full control of the individual steps. To get acquainted with the entire active scenario we chose to the latter approach. Windows Communication Foundation (WCF) and Windows Identity Foundation (WIF) provide ready-to-use channels for the WS-Trust protocol and WS-Federation protocol. The scenario will take several steps:

Acquire an identity claim from the IP-STS by using username/password authentication to authenticate.
The IP-STS will issue a claim token regarding our identity, sign and encrypt it and send it back to us.
Use the claim token from the IP-STS to authenticate against the R-STS and request a new claim token with additional claims from AD-LDS.
The R-STS will also issue the (augmented) claim, sign and (optionally) encrypt it and send it.
We need to decrypt the token, check its signature and issuer and convert the claim token to a principal object.

Note that we made some design choices, such as using username/password to authenticate against the IP-STS. You could make similar or different choices depending on your particular scenario.

Step 1: Acquiring an identity claims from an active STS

The first part of the process is the acquisition of a claim token from the IP-STS. We need one of the specialized WCF binding for a WS-Trust channel. Because we are using username and password to authenticate, this comes down to UserNameWSTrustBinding. We want to use transport security (an HTTPS connection) with credentials inside of the message (because Message security would mean that we need encryption and certificate exchange for this part). The endpoint at ADFS is https://identityadfs.company.com/services/trust/2005/usernamemixed to reflect our choices. The 2005 endpoint will use the newer WS-Trust 1.3 specification (as opposed to the February 2005 one).

var binding = new UserNameWSTrustBinding(SecurityMode.TransportWithMessageCredential);
var factory = new WSTrustChannelFactory(binding, "https://identityadfs.company.com/adfs/services/trust/13/usernamemixed")
  {
    TrustVersion = TrustVersion.WSTrustFeb2005,
  };
 
factory.Credentials.UserName.UserName = @"youraccount";
factory.Credentials.UserName.Password = @"abc123!";
factory.ConfigureChannelFactory();

We now have a configured channel factory to create an actual WS-Trust channel. Across that channel we want to send a Request Security Token (RST) message.

var rst = new RequestSecurityToken
  {
    RequestType = WSTrust13Constants.RequestTypes.Issue,
    AppliesTo = new EndpointAddress(http://resourceadfs.company.com/adfs/services/trust),
    KeyType = WSTrust13Constants.KeyTypes.Symmetric
  };

var channel = factory.CreateChannel();
return channel.Issue(rst);

As you can see this RST message indicates an issue request for the audience “http://sourceadfs.company.com/adfs/services/trust/active”, which is the identifier of the relying party (the IP-STS) administration in the R-STS . In other words: a identity claim token intended to be shown to the R-STS.

We also ask the IP-STS issuer to encrypt the claim token with a symmetric key. You will see why this is in a moment. In other situations you could have asked for a Bearer (unecnrypted) key type token, which would have allowed you to inspect the token.

Step 2: Issue token from IP-STS

The IP-STS will accept and validate our credentials against the Active Directory Domain Services identity store. When successfully authenticated, ADFS will use its claim rules to extract information from ADDS and build a claim token with the indicated claims. Next it will encrypt this claim token using a certificate with a public key. This public key belongs to a public/private key pair that the R-STS holds. The IP-STS can encrypt the token, where only the R-STS can decrypt it using its private key.

Step 3: Use claim token to authenticate and request augmented claim token

Now, we can use the issued identity claim token to authenticate against the R-STS. We will again use a WS-Trust channel, but now with issued token authentication.

var binding = new IssuedTokenWSTrustBinding();
binding.SecurityMode = SecurityMode.TransportWithMessageCredential;
binding.KeyType = SecurityKeyType.SymmetricKey;
 
var factory = new WSTrustChannelFactory(binding, 
  "https://resourceadfs.company.com/adfs/services/trust/13/issuedtokenmixedsymmetricbasic256");
factory.TrustVersion = TrustVersion.WSTrust13;
factory.Credentials.SupportInteractive = false;
factory.ConfigureChannelFactory();

The configuration of the channel factory is similar to the first step. The key differences are that we now have an IssuedTokenWSTrustBinding and a symmetric key for the issued token. The reason for choosing the symmetric encrypted request in the first step is that the R-STS does not accept Bearer key tokens for authentication. They have to be (a)symmetrically signed for the R-STS to use them as an authentication means. Also, we suppress the Interactive support (meaning InfoCard c.q. CardSpace UI), as we are initiating a service request (hence, no user is available).

Next, we create another RST message and send it out to the R-STS.

var rst = new RequestSecurityToken
  {
    RequestType = RequestTypes.Issue,
    AppliesTo = new EndpointAddress("http://sp2007webapp.company.com"),
    KeyType = KeyTypes.Bearer
  };   var channel = factory.CreateChannelWithIssuedToken(token);
return channel.Issue(rst);

The RST now indicates an audience for the SharePoint 2007 application. Its key type can be Bearer or (A)Symmetric, depending on how you want the token to be transferred. Should you choose the Symmetric or Asymmetric key type, you will need to install a server certificate on the web application’s IIS server, extract the public key and install it on the R-STS server as the encryption certificate for the relying party (i.e. the SharePoint app) trust.

Finally, using an extension method from WIF we create a channel from the factory that can convey the token as an authentication means. Lastly, we send out the RST message and return the token to the caller after step 4 has completed.

Step 4: Issuing an augmented claim

Once the issued token arrives at the R-STS, ADFS will decrypt the token using its public/private keypair. If it is a valid token, the R-STS will believe its trusted IP-STS that the credentials originally provided where correct. According to the configured claim rules the R-STS will create new and/or additional claims (called claim augmentation) to the new claim token. It will include the audience, sign it, encrypt it if you indicated so in the RST, and send out the RST response (RSTR).

Step 5: Check claim token and create principal

The last step is back on the SharePoint application.

GenericXmlSecurityToken augmentedToken = AugmentClaims(issuedToken);
var tokenReader = new StringReader(augmentedToken.TokenXml.OuterXml);
var reader = XmlReader.Create(tokenReader);

The issuedToken variable contains the token received from step 1 and 2. The AugmentClaims method is the implementation shown in step 3. When the R-STS returns the augmented claim, it will surface as a GenericXmlSecurityToken. We set up an XmlReader to start reading the token.

Remember that to read the token we need to decrypt it, check its signature, audience and issuer. This checking is taken care of by a set of token handlers

SecurityTokenHandlerCollection handlers = 
  SecurityTokenHandlerCollection.CreateDefaultSecurityTokenHandlerCollection();

The default security handlers are some eight handlers for various types of tokens. They all use the configuration defined at the SecurityTokenHandlerCollection. First, we will add our public/private keypair as the certificate that the token resolver should use for decryption. The SecurityTokenResolver will use the thumbprint as a reference to the certificate

X509Store store = new X509Store(StoreName.My, StoreLocation.LocalMachine);
store.Open(OpenFlags.ReadOnly);
X509Certificate2Collection certificates = store.Certificates;
X509Certificate2 certificate = certificates.Find(
  X509FindType.FindByThumbprint, 
  "ThumbprintForWebAppPubPrivCertificateAllCapitals", true)[0];
 
List<SecurityToken> serviceTokens = new List<SecurityToken>();
serviceTokens.Add(new X509SecurityToken(certificate));
SecurityTokenResolver serviceResolver = 
  SecurityTokenResolver.CreateDefaultSecurityTokenResolver(
  serviceTokens.AsReadOnly(), false);
handlers.Configuration.ServiceTokenResolver = serviceResolver;

You will only need the code fragment for the token resolver above if you indicated an encrypted token. We did not, so these 8 lines of code are not necessary.

Next, we will add a certificate store for the issuer resolution. The token handlers will look up the issuer’s certificate thumbprint in the Personal certificates store of Local machine (not a user’s store).

SecurityTokenHandlerCollection handlers = 
  SecurityTokenHandlerCollection.CreateDefaultSecurityTokenHandlerCollection();
X509CertificateStoreTokenResolver certificateStoreIssuerResolver = 
  new X509CertificateStoreTokenResolver(StoreName.My, StoreLocation.LocalMachine);
handlers.Configuration.IssuerTokenResolver = certificateStoreIssuerResolver;

var registry = new ConfigurationBasedIssuerNameRegistry();
registry.AddTrustedIssuer("ThumbPrintForResourceADFSPubSigningAllCapitals", 
  http://resourceadfs.company.com/adfs/services/trust);

handlers.Configuration.IssuerNameRegistry = registry;
handlers.Configuration.AudienceRestriction.AllowedAudienceUris.
  Add(new Uri(http://sp2007webapp.company.com));

With all this setup, all that remains it to actually read (decrypt) the token and to check its signature, issuer and audience. The set of identities that is included will contain 1 IClaimsIdentity derived object containing our identity with corresponding claims.

var samlToken = handlers.ReadToken(reader);
IClaimsIdentity identity = handlers.ValidateToken(samlToken)[0];

All done

At this point we have a ClaimsIdentity that we can use to construct a claim principal and start reading claims for authorization inside our application. You might want to have the claims principal set to the current thread Thread.CurrentPrincipal and the HTTP context via HttpContext.Current.User. Inside the identity you can see the initial authentication type (username/password in our case) and for each claim the issuer (R-STS) and the original issuer (IP-STS, only when you passed through the original IP-STS claim as a R-STS claim).

All steps assume a happy flow, but you will need to include the usual exception handling for Timeout-, Communication-, ObjectDisposedException and other exceptions that may occur.

Hope this helps.

Maps of “Todd’s Adventures in Slimeworld”

Alex Thissen — Sun, 10 Jul 2011 19:44:46 GMT

These maps have been in my folder for a very, very long time (around 1992). I thought it would be a shame to see them go to waste.

When I was still in university I had too much time and an Atari Lynx with “Todd’s Adventures in Slimeworld” to boot. A great combination. I drew all maps of the single player adventures by hand and stuck them in a folder. Today, I used my scanner to scan each of them. Then I stitched together the individual pages and came up with the maps you can see here. I hope you enjoy them and find them useful. Pay special attention to the map for adventure 6 (Arcade): it shows the easter egg to the zit-popping game.

Let me know what you think.

Adventure 1: Easy

Adventure 2: Exploration

Adventure 3: Action

Adventure 4: Suspense

Adventure 5: Logic

Adventure 6: Arcade

Legend

Key	Description
Number	Spawn point (see lookup list at right of map for start code)
G	Gem
SG	Super gem
M	Megabomb
V	Snapper
B	Bait
S	Shield
P	Gun powerup
J	Jetpack
C	Cleanser (changes slime pool to water)
R	Mushroom
Blue	Water
Green	Slime
Green (marked M)	Moving slime
Double line	Passway (door or ceiling)
Brown edge	Bouncy slime
Red edge	Sticky slime
Blue edge	Ice

Portable Libraries for Visual Studio 2010 SP1

Alex Thissen — Thu, 07 Jul 2011 21:47:03 GMT

The Microsoft BCL team recently released the RTM version of Portable Libraries (PL). This PowerTool for Visual Studio 2010 SP1 allow you to develop managed assemblies for more than one target .NET framework. It will let you aim your code at both the full .NET Framework, Silverlight, Silverlight for Windows Phone 7 and/or Xbox 360. By using the Portable Libraries you can control which targets you are aiming for and compile a single assembly that will work on all targets you selected.

The Portable Libraries has features that are close to, yet different from another piece of functionality in Visual Studio: multitargeting. It is similar in that it will help you find the allowed subset of functionality in the .NET Framework given the combination of targets you select. It is different, because it will let you have a single project where you would normally have multiple projects for class libraries targeting .NET FX (versions 2.0 to 4.0, with full or client profile) and Silverlight. For Xbox 360 you have the Xbox 360 Game Library which comes close, but is a different thing altogether. PL projects are class libraries which can host reusable managed code over all of the previously mentioned.

You can install the tooling for PL from here. Once you have done that, a new library project is available:

A Portable Library project has its own project template. The main difference from a regular class library is in the AssemblyInfo.cs file. The contents are trimmed, because ComVisibleAttribute and GuidAttribute do not make sense for Silverlight and Xbox and are not allowed. The other difference is an extra tab on the Project Properties page. It allows you to specify the targets for your library.

In the screenshot below you can see a Class Library project converted to a Portable Library. The references to assemblies that are not part of the allowed assemblies for the targets are indicated with exclamation marks, just as when you had selected a not allowed assembly for the .NET Target Framework in a normal Class Library.

The Portable Libraries have a different build target, which further distinguishes them from regular class libraries.

The allowed set of assemblies is listed here, but to give you an idea, it is limited:

mscorlib.dll
System.dll
System.Core.dll
System.Xml.dll
System.ComponentModel.Composition.dll (MEF)
System.Net.dll
System.Runtime.Serialization.dll
System.ServiceModel.dll
System.Xml.Serialization.dll
System.Windows.dll (from Silverlight)

This set is the largest possible if you are only targeting .NET Framework 4. For Silverlight and Phone 7 you cannot use MEF (System.ComponentModel.Composition), and for Xbox 360 you can only use the bold assemblies.

The use of the Portable Class Library project will pay of in finding which classes you can use and which not. If you are in doubt, you can check the MSDN documentation and make sure. Here is an example for the System.Runtime.InteropServices.StructLayoutAttribute class:

In the type’s members you can see whether a particular member is supported (when the type itself is):

The small project icon in the left column means it is supported.

An example scenario

Let’s say you have a piece of C# code that can be reused in an application or game for Windows, Phone and Xbox 360. Normally (without Portable Libraries), you would need to set up several projects:

Each of the ReusableGameCore libraries contain the same code, but have a different target. They are referenced by the corresponding game (or application) version for Windows, Phone and Xbox.

You need to do so, because the build target need to be different for the various consumers of your reusable code. For example, referencing a normal Class Library project in an XNA Game Studio 4.0 project for Xbox 360 will get you compile errors. It will complain about the “wrong” target framework being selected, even though you have changed it to .NET 4 Client Profile (or something else).

As you can see in the screenshot the code in the Silverlight and Xbox360 library projects is linked from the Windows version. You will only have one version of the code, but having three project is not ideal.

The alternative is offered by Portable Libraries. In that case the three libraries can be combined into a single one. Your solution will look like this:

The three other projects each reference the single portable class library. Quicker to set up and easier to maintain. Moreover, you can install additional frameworks, which allows you to target other or more from the same library.

Converting a Class Library to a Portable Class Library

It could very well be that you have a Visual Studio solution that holds class libraries which you would like to be Portable. One option is to create a new Portable Library project and transfer the files from the class library to the new Portable project. This should be the normal way to go. I tried whether it is possible to convert the class library project into a portable one. Turns out that it can be done. Here’s how:

Unload the Class Library project. Right-click the project and select Unload Project from the context menu to do so.
Edit the .csproj or .vbproj file. Pick the option from the context menu.

Add the following fragment to the first <PropertyGroup> under the <Project> root element:

C#:

<ProjectTypeGuids>{786C830F-07A1-408B-BD7F-6EE04809D6DB};{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}</ProjectTypeGuids>
<TargetFrameworkProfile>Profile1</TargetFrameworkProfile>

Visual Basic:

<ProjectTypeGuids>{14182A97-F7F0-4C62-8B27-98AA8AE2109A};{F184B08F-C81C-45F6-A57F-5ABD9991F28F}</ProjectTypeGuids>
<TargetFrameworkProfile>Profile2</TargetFrameworkProfile>

Remove the <ProductVersion> and <SchemaVersion elements:

<ProductVersion>8.0.30703</ProductVersion>
<SchemaVersion>2.0</SchemaVersion>
Change the <Import> element just before the closing tag of the <Project> element to the .

In C# replace

<Import Project="$(MSBuildToolsPath)\Microsoft.CSharp.targets" />

with

<Import Project="$(MSBuildExtensionsPath32)\Microsoft\Portable\$(TargetFrameworkVersion)\Microsoft.Portable.CSharp.targets" />

In Visual Basic replace

<Import Project="$(MSBuildToolsPath)\Microsoft.VisualBasic.targets" />

with

<Import Project="$(MSBuildExtensionsPath32)\Microsoft\Portable\$(TargetFrameworkVersion)\Microsoft.Portable.VisualBasic.targets" />

Remove the following code from AssemblyInfo.cs (or the equivalent from AssemblyInfo.vb)

// Setting ComVisible to false makes the types in this assembly not visible 
// to COM components.  If you need to access a type in this assembly from 
// COM, set the ComVisible attribute to true on that type.
[assembly: ComVisible(false)]
 
// The following GUID is for the ID of the typelib if this project is exposed to COM
[assembly: Guid("1e49a9ca-89db-46d1-9704-b76e10897ffb")]

Reload the project by right-clicking the project and selecting the menu item

Please note that this is not an official and therefore not supported migration. No guarantees and make sure you have backups, checkins et cetera before you undertake this conversion.

Running Atari Lynx emulator on a Windows Phone 7

Alex Thissen — Wed, 06 Jul 2011 20:00:00 GMT

The implementation of the emulator for the Atari Lynx has been progressing steadily. I thought it would be a good time to show a particular point of progress: a working implementation of the emulator running on a Windows Phone 7.

(Please visit the site to view this media)

Update: here is another video of the emulator running in Windows Phone 7 emulator.

(Please visit the site to view this media)

Some details:

The emulator core is used in a XNA Game Studio 4.0 implementation for Windows, Phone 7 and Xbox 360 client. The Windows and Phone 7 implementations work correctly (give and take the remaining bugs and mayor performance issues), but the Xbox 360 variant doesn’t work.

As you can see in the video the framerate is pretty dramatic with an estimate of 2 fps (where 0.2 would probably be more accurate). The Windows version can run at 60 fps, but the Windows Phone 7 doesn’t even come close. The Windows Phone 7 emulator can run most games at 25 fps. This is something that needs to be investigated. There were no performance optimizations made just yet.

You can find the source code for the emulator at lynxemulator.codeplex.com. Suggestions for improvement are very welcome.

Pepijn Sitter helped develop part of this code. He refactored the controller handling implementation and did some first, rough implementation of the gestures for the Phone, so we could at least get past the start screen. (Which didn’t work out as expected). Thanks Pepijn.

Compiling Handy 0.95 for Windows

Alex Thissen — Mon, 20 Jun 2011 08:25:20 GMT

Quick runthrough to get the Handy sources to compile for Windows using Microsoft Visual Studio 2010 (or Microsoft Visual C++ 2010 Express, which is a free download).

Download these first:

Handy source code (Handy-win32src-0.95.zip contains the sources)
Microsoft Visual C++ 2010 Express (in case you do not own a copy of Visual Studio that includes C++)
DirectX 9.0 Software Development Kit Update (August 2005)

Install Visual C++ and the DirectX SDK. Unpack the sources of Handy.

Open the folder of the Handy sources and find the Handy.dsp file. Doubleclick to the open it in Visual C++. It will prompt you to convert the project. Choose Yes in the dialog.

Save the solution. You must specify the location of the .sln solution file. The root of the project will be an appropriate location.

Right-click the Handy project and open the Properties dialog. Go to the C/C++ section and enter a new entry under “Additional Include Directories”. This should be “C:\Program Files (x86)\Microsoft DirectX 9.0 SDK (August 2005)\Include” if you installed the DirectX 9 SDK to the default installation directory.

Next, go to the Linker section and add “C:\Program Files (x86)\Microsoft DirectX 9.0 SDK (August 2005)\Lib\x86” to the “Additional Libraries Directories”.

When you first try to compile the sources you will get a number of errors. Fix each of these, bullet by bullet and recompile in between:

22 errors: error C1083: Cannot open include file: 'strstrea.h': No such file or directory
Apply fix 1.
96 errors: related to endl, ostream&, ostrstream and ostrstream& references and declarations in error.h
Apply fix 2.
43 errors:

error C4430: missing type specifier - int assumed. Note: C++ does not support default-int
error C2664: 'CWnd::OnActivateApp' : cannot convert parameter 2 from 'HTASK' to 'DWORD'
error C2440: 'static_cast' : cannot convert from 'void (__thiscall CLynxWindow::* )(WPARAM,LPARAM)' to 'LRESULT (__thiscall CWnd::* )(WPARAM,LPARAM)'
error C2065: 'loop' : undeclared identifier
error C2065: 'endl' : undeclared identifier

Apply fixes 2 to 6

This is the list of fixes you will need to make to get the sources to compile.

Replace #include “strstrea.h” in error.h with these two lines:

#include <iostream>
#include <strstream>

Prefix ostream&, ostrstream and ostrstream& declarations with:

std::

Change line 1192 in Lynxwin.cpp to

static bool firsttime=0;

Change HTASK hTask in line 2365 of Lynxwin.cpp and line 325 of Lynxwin.h to

DWORD hTask

Comment out the lines 868 and 869 of Lynxwin.cpp. I do not know how to really fix these errors yet.
Add a new line at 1552 in Lynxwin.cpp with:

ULONG loop=0;

Change line 95 of Debuggerwin.cpp to:

for(int loop=0;loop<mWinHeight;loop++) LineOutput("");

Change line 550 of Debuggerwin.cpp to these two:

int loop;
for(loop=0;loop<mLineInput-1;loop++)

Change line 487 of codewin.cpp to these two:

int loop;
for(loop=0;loop<MAX_CPU_BREAKPOINTS;loop++)

After that you should have a Handy C++ project that compiles, links and runs correctly.

For the developer version of Handy you should add a preprocessor definition _LYNXDBG to the project:

The developer version gives you a Code, Debugger and Graphics dump window and ability to debug/step-through the 65SC02 code.

You will also get new compile errors. To fix these, apply fix 7 to 9 to get rid of those.

Run the Handy emulator, find yourself LYNXBOOT.IMG if you have got the boot image and some rom images for (homebrew) games.

For your convenience, you can download the revised sources here: http://www.alexthissen.nl/media/p/22572.aspx

SDN Event June 2011: ASP.NET Web Pages Framework for ASP.NET developers

Alex Thissen — Mon, 20 Jun 2011 05:43:22 GMT

Last Friday saw another edition of a Software Development Network Event. A number of great sessions were on the list. I got to see Marcel de Vries’s session on combined development for Windows Phone 7, Android and iOS. I must say I was impressed with the state of tooling for Mono for Android and MonoTouch (for iOS).

My session for the SDN Event was on the ASP.NET Web Pages Framework. In it I show

what this new framework is,
how it relates to ASP.NET WebForms, MVC and WebMatrix
how to build applications with it
introduction to Razor (see also my DevDays 2011 session on “Introduction to Razor” for more information on Razor)
what the new concepts like “page hierarchies”, UrlData and PageData are
working with models and model state (and how this is different than the model from MVC)
automatic routing
some more

If you couldn’t make it, feel free to take a look at the slides and the demos. Thanks everyone who attended the session. Hopefully you found it useful.

I missed the session of Pepijn Sitter on XNA Game development for the Windows Phone 7, because he shared the timeslot with my own session. Luckily for me I had a chance to meet him before his session. We had a very enthusiastic talk on games, game development, the fun of it all and his Ms. Pacman implementation with XNA for XBox360 and Windows Phone 7. Brilliant stuff.

Come Lynx with me

Alex Thissen — Tue, 31 May 2011 20:03:06 GMT

One of the differentiating features of the Atari Lynx was its ability to link together up to 18 Lynx devices using a set of cables. This allows for multiplayer games,

You need at least two Lynx devices and at least one ComLynx cable to make a connection. For more Lynxes you require an additional ComLynx cable for every extra Lynx. The ComLynx cable has two male connectors at either end. One end has a split cable with a female connector.

The single male side of a new cable can be connected to the female connector and to the next Lynx at the split end. This way you can connect an potentially unlimited chain of Lynxes. The practical limit is around 18 because of communication overhead and something called “pull-ups”.

and so on.

There were several games that used this capability for multiplayer support. Each Lynx will need a separate copy of the game. There is a possibility to game

Title	Players	Title	Players
Awesome Golf	1-4	Pit-Fighter	1-2
Baseball Heroes	1-2	Raiden	1-2
Basketbrawl	1-2	Rampage	1-4
Battlewheels	1-6	Rampart	1-2
Battlezone 2000	1-4	Robo-squash	1-2
Bill and Ted’s Excellent Adventure	1-2	Shanghai	1-2
California Games	1-4	Super Off-Road	1-4
Checkered Flag	1-6	Super Skweek	1-2
Double Dragon	1-2	Todd’s Adventures in Slime World	1-8
European Soccer Challenge	1-2	Tournament Cyberball 2072	1-4
Gauntlet: The Third Encounter	1-4	Turbo Sub	1-2
Hockey	1-2	Warbirds	1-4
Jimmy Connors Tennis	1-4	World Class Soccer	1-2
Joust	1-2	Xenophobe	1-4
Lynx Casino	1-2	Xybots	1-2
Malibu Bikini Volleyball	1-4	Zarlor Mercenary	1-4
NFL Football	1-2

The ComLynx-able games can be recognized by the yellow triangle at the bottom-right corner of the box. This shows that players can “Lynx Up” and the maximum number of players. The game “California Games” is an exception, in that is says “1 To 2 Players” on the box, where a total number of 4 players are possible.

and pay special attention to the corner.

Here is a video that shows two Lynxes connected together:

Atari Lynx version I and version II ComLynxed together

Remarks found all over the Internet:

“The ComLynx does not have any hardware bugs. But the format is pretty much fixed to start bit, 8 data bits, even parity, 1 stop bit. And the only sensible baud rates are 9600 and 62500. The ComLynx has a combined Rx/Tx pin and it can sense if two Lynxes transmit at the same time. … The Lynx has +5V on one pin that is enough to power up the communications cable.” – AtariAge forums
“ComLynx was originally developed to run over infrared links (and was codenamed RedEye).^[4] This was changed to a cable-based networking system before the final release.” – Wikipedia
“UART (for ComLynx) (fixed format 8E1, up to 62500 Bd)” – Wikipedia

Bugs in the ComLynx (from the Lynx development manual):

“A design error causes the power up state of the output to be TTL high, ALL code must set the TXOPEN bit in order to fix this"
"Well, we did screw something up after all. Both the transmit and receive interrupts are 'level' sensitive, rather than 'edge' sensitive"

Links that seemed useful to me:

Here are some observations I made, which I hadn’t read on the Internet anywhere:

Some (maybe all?) ComLynx-able games can connect players while the start-menu/animations is displayed.
In other words: as long as no player has started the game, other players can join by switching their Lynx on. Bear in mind the next observation. I always believed that the Lynxes needed to be powered on at the (near-exact) same time.
When multiple Lynxes are linked together, the outsides of the chain can switch off, without disrupting the other connected Lynxes. The same goes for switching the Lynxes on at a later time (see previous point)
You can disable the cartridge detection of the Lynx. In theory this should allow for multiple Lynxes to connect on one cartridge, provided that the Lynx have detection disabled and that the cartridge is read only at the startup of the game. Did anyone try this?

From the Lynx Frequently Asked Questions:

Q. What does "ComLynx" mean, exactly?
A. Some Lynx games allow multiple players to play together simultaneously. This works when each player has a Lynx game machine, and all of the machines are connected to each other via cables. The connection is the ComLynx port, and the cables are ComLynx cables. Games that support this mutiplayer simultaneous play are usually identified by the phrase "1 to N players Lynx up" on the box, the instruction manual, and/or the game card.

Q. Do all players "Lynxed up" via the ComLynx need a copy of the game being played?
A. Yes. All players need a copy of the game card.

Q. What's the ComLynx port like?
A. There is limit of 18 players via ComLynx. In practice it may be possible to connect more units together, but to operate within specifications, the drivers in the Lynx cannot drive over more than 17 units with pull-ups on the serial ports. ComLynx runs from 300.5 to 62.5K baud. It works on a "listen and send" structure. Data transmission between Lynxes is done in the background, freeing up the CPU to run the game instead of communicating. It's called "RedEye" in-house at Atari, named after an early idea of having Lynxes communicate with infra-red transmissions. It uses a three-wire cable (+5V/Ground/Data) and allows for bi- directional serial communications. The system frames messages in terms of 11-bit words, each consisting of a start bit, eight data bits, a parity bit, and a stop bit. The ComLynx port is used solely for communications; it can't be used to control other aspects of the Lynx, though in theory it can be used to send signals to external devices.

Q. Sometimes a multiplayer ComLynx game will freeze up. Why?
A. A ComLynxed game will freeze if communication between the Lynxes is interrupted. If communications can be restored, the game will continue. The most common cause of this problem is a fray in one of the ComLynx cables, or a loose seating in one of the ComLynx jacks. Communication is broken, and the game "freezes". Jiggling the cable or reseating the jacks may fix the solution temporarily, but the best cure is a new cable.

Q. I hear there's a ComLynx port on the Atari Jaguar. How does that work? Can I connect my Lynx to it? Will there be a Lynx adaptor for the Jaguar?
A. The ComLynx port allows communication between Jaguar units and Lynx units. In theory, it would be possible to daisy-chain multiple units of either machine type for multiplayer games. At the current time, however, no such plans are in the works. Instead, it is seen as allowing Lynxes to be used as peripherals: software can be developed to allow Lynxes to be part of a Jaguar game as controllers. An adaptor to allow the Jaguar to play Lynx games is not currently planned.

Choosing from all the great sessions at the Dutch Developer Days 2011

Alex Thissen — Tue, 19 Apr 2011 05:44:37 GMT

The organization of the Microsoft Developer Days has an outstanding reputation for selecting excellent speakers from abroad and both new and well known speakers in The Netherlands. This year I intend to go see more sessions than in previous years. It is hard to choose from all of the sessions that are listed. Instead of randomly picking from that list, I first came up with a strategy to select them. It turned out to be a criteria list that should help prioritize sessions.

Strategic initiative from Microsoft
If there is a session on Windows Azure, Windows Phone or the next version of some product
Practice over theory
I guess that you can go a long way by following the training kits, blogs and documentation on new platforms, frameworks and technologies. The lessons learned by using these in real-life/business scenarios is a lot harder to come by.
New and broad information over in-depth information (on topics that are known already)
Learning new things gets preference over going deeper into topics I already feel comfortable with
Speaker reputation
Some speakers are a delight to go see. If none of the above make a difference or end in a tie, I will decide based on the speaker. This can be based on entertainment value, technical accuracy or experiences in the past.

Developer Days - 1

9:15 – 10:45	The easiest timeslot to choose a session: the keynote
11:05 – 12:20	What's New in SQL Server "Denali" for Developers?, Paul van Wingerden. New technology and I’m very rusty on the developer side of SQL Server. Catching up required. Windows Phone 7 (title to be disclosed after MIX), Ben Riga: Summary of WP7 as discussed at Mix 2011. Should save a lot of time viewing this session instead of the recorded videos at Channel 9 MVC 3 – 101, Scott Hanselman Guaranteed fun and overview of MVC3 to boot
13:30 – 14:45	Reactive Extensions for .NET for the Rest of Us, Mike Taulty Mike is an excellent speaker with loads of high-speed demos and more information than a human could handle in one hour. Windows Azure AppFabric: Building, Managing, and Connecting High-Density, Multi-Tenant Cloud Applications , Clemens Vasters Clemens is Mr. ServiceBus and the authority on this part of AppFabric. De Locatie Centraal met Windows Phone 7, Marco Wagemakers Lower on the list as Achmea is also using ArcGIS and it should be close to home.
15:05 – 16:20	Produceer Betere Product Kwaliteit door Gebruik te Maken van de Ultimate Test Tools, Marcel de Vries It’s been a long time since I saw Marcel speak. I also need some better overview of the test tooling Taking Control of your World with the .NET Micro Framework, Rob Miles Great speaker who could easily have been standup comedian. I’m curious what the .NET Micro Framework will bring us in the future.
16:30 – 17:45	What's New in Silverlight 5, Jeff Prosise What can I say: Jeff Prosise of Windows and MFC fame to tell us about the new things in SL5. A must see. Visual Studio LightSwitch - Beyond the Basics, Beth Massi I saw a LightSwitch session by Stefan Kamphuis at the Dutch CodeCamp a couple of weeks ago. I looks very promising as a new tool and I want to know more about the developer potential of this tool.

Developer Days - 2

9:15 – 10:30	HTML 5 - That's What You Need to Know Today!, Ingo Rammer Ingo Rammer is famous for his book and knowledge on .NET Remoting. HTML 5 is going to make an impact over the next couple of years. Better not to stay behind. Identity & Access Control in the Cloud, Vittorio Bertocci What can I say: the next generation security combined with the cloud. If it weren’t for my involvement in a project that goes deep into claims and identity, I would go see this one. Improving Legacy .NET Code, Thomas Huijer Something we all have to deal with: legacy code. I wonder what Thomas’s insights are in improving this.
10:50 – 12:05	Demystifying the .NET Asynchronous Programming Landscape, Bart de Smet Bart has been involved in Linq and other language features at the source in Redmond. This will give a great insight into the async options and the upcoming VB and C# support. Real World Architecture with ASP.NET MVC, Hadi Hariri Real World Windows Azure Development: Tips & Tricks, Wade Wegner Hard to choose between number 2 and 3. If it comes down to one of these, I think I’ll toss a coin. (I’ve done so before, ask Dennis)
13:15 – 14:30	Windows Azure AppFabric Access Control Service: Deep Dive, Vittorio Bertocci Advanced Debugging with Visual Studio 2010, Ingo Rammer Just yesterday I did some low level debugging with WinDbg and DotTrace to track down a memory leak in an ASP.NET application. Ingo will be able to tell more on the topic.
14:50 – 16:05	I’ll be at my own session. Come see this if you are interested in finding out more on Razor and the Web Pages framework surrounding it.
16:15 – 17:30	Developing SaaS Solutions with the Windows Azure Platform, Vittorio Bertocci Web Services Interoperability tussen WCF en Java, Edwin van Wijk en Bert Erman WCF Data Services Introductie - De Serverkant, Erno de Weerd At the end of the conference I have no idea what I think is a nice roundup. These three seemed to come to mind. We’ll see.

Hopefully this list or the criteria will help you select from all of the sessions, if you are in doubt. Whichever way, the DevDays 2011 should be a great event. Have fun and see you there!

A new role: Microsoft Regional Director

Alex Thissen — Mon, 04 Apr 2011 20:49:27 GMT

Since early March I have been given a new role as Microsoft Regional Director (RD). In The Netherlands there are two positions for RD, and for the past few years Marcel de Vries and Anko Duizer have fulfilled both. Last year Anko rejoined the ranks of Microsoft and automatically stopped being an RD. August last year I was contacted by Microsoft NL to talk about the RD program. I happily accepted the invitation to become the new RD.

I’ve waited for a good moment to announce my new role and finished some other work, in order to be able to spend more time on the RD program. The appearance of the RD column that Marcel and myself wrote for the the last issue of the Dutch DotNetMagazine seemed like a good time. I am very enthusiastic about the program and the part I can play in it. I really believe that RDs can serve as an intermediate between Microsoft and the community at large (being the .NET community, end users and businesses). Very soon Marcel and myself will start building an “attack plan” to maximize the impact we can make as RDs. Stay tuned.

Next up will be a translation of the RD column in English, because I think that it explains the purpose of the Regional Director program from a different angle. I’ve named it “Regional Directors: the antennas for Microsoft and the community”.

If you are interested to read more on the Regional Director program, you can take a look at the TheRegion.com. Also, there is a nice blog post by Jeffrey Pallermo that has some frequently asked questions on “who are the Regional Directors?”.

Dirty Larry Renegade Cop

Alex Thissen — Mon, 29 Nov 2010 14:20:10 GMT

Some time ago I decided to finish some of the Atari Lynx games that I hadn’t played that much or hadn’t completed. This post is on Dirty Larry Renegade Cop, a nice side-scrolling shooter/bash’m up in the tradition of games like Double Dragon (also a Lynx title). In a future post I will explain how I managed to complete the game.

On a personal note: I pretty much enjoyed the game after some practice, but was glad I could play the game with the Handy emulator to save the game at different points of progress. Especially defeating the first boss (Mr. Snuff) was pretty much impossible without being able to reload the game at level 5. The bullets are your lifeline as much as your health is. No bullets means a certain death. You will (almost) always take damage using your fists. The more difficult villains like the machinegun toting Rastafarian are hard to beat.

For now, here is some information and nowhere to be found screenshots of the game. Enjoy.

Synopsis (spoiler-alert!)

You are a police cop with an attitude and a will of his own. You are just gotten yelled at by your boss and learned that you do not get a car anymore.

Larry’s boss: “And darn it Larry, that’s the third car this week! You need to learn to respect police property! As of this moment, you walk or take the subway! Judge Smite just threw out another case! Get to the Knight Shade Hotel, this time with a proper warrant, and bring in Harold Snuff, A.K.A. Mr. White, an iceman boss. The charge is drug trafficking...”

So, off you go to the Knight Shade Hotel on foot. First you travel to the subway, ride a cart on the sub and deal with a lot of criminals and scoundrels along the way. You face gun and knife wielding gang members, big mommas with chains, biker dudes, baseball club swinging crazies (like in the movie The Warriors) and self-igniting pyromaniac and arrive at the hotel armed with a machine gun you found in the subway. In the meantime someone known as Mr. Big has a conversation with Harold Snuff.

Mr. Big: “Mr. Snuff, I require a favor of you. There is a cop that I need out of the way.”
Mr. Snuff: ”Consider it done, Mr. Big…”

You work your way through three levels of the hotel with assorted baddies and end up in a confrontation with Mr. Snuff/White. After you have defeated him you acquire grenades and head back to the office.

Larry’s boss: “Congratulations, Larry, you finally did something right! Mr. White goes on trial today. We got the address of a warehouse from one of his papers. Check it out and remember, ask questions first!”

So, foot patrol to the warehouse along the sidewalks of Steelburg and through the subway. As you leave the subway there is another conversation, this time between Mr. Big and Dr. Electro.

Mr. Big: “Dr. Electro, it seems that Mr. Snuff was unable to do his duty. Would you mind showing Larry the light?”
Dr. Electro starts blinking with electricity.

You enter a warehouse and get confronted with more villains, including grenade throwing mad scientists. At the far end of the warehouse you discover a trap door and open it to descend into the sewers. Near the end you battle against Dr. Electro. His electrifying rays may hurt you, but he is no match against the awesome power of your grenades and machine gun. You exit the sewers and find you are in… the courthouse of Judge Smite.

Yet another conversation takes place. Mr. Big has a talk with

Mr. Big: “Office Stobbe, one of your detectives has been harassing my men. Could you see that it stops?”
Office Stobbe: “Yes sir, I’ll get a few of my men to have a talk with him…”

Office Stobbe must be a quick guy, because you are faced with a dozen or so corrupt cops that want to have a “talk” with you. They use a lot of bullits to do the talking. Finally, you reach the office room of the courthouse and find that none other than Judge Smite is waiting for you. He starts throwing his wooden hammer at you and hammers the floor to make earthquakes. A big man and hard to defeat. You manage to do so any way.

As it turns out, Judge Smite is actually Mr. Big! Your actions will put Judge Smite behind bars for a long time.

The levels

Level 1 and 6, 2 and 7, 4 and 5 are pretty much the same levels. The levels 5, 9 and 10 have Boss battles with Mr. Snuff, Dr. Electro and Judge Smite. After defeating the corrupt judge you have finished the game and end credits are displayed.

Level 1: The Steelburg Sidewalks

Level 2: The Steelburg Subway

Meanwhile

Level 3: The Knight Shade Hotel Ground Floor

Level 4: The Knight Shade Hotel Second Floor

Level 5: The Knight Shade Hotel 3rd Floor

Back at the office

Level 6: The Steelburg Sidewalks

Level 7: The Steelburg Subway 2

Meanwhile

Level 8: The Warehouse

Level 9: The Sewers

Level 9: Boss battle with Dr. Electro

Meanwhile

Level 10: The courthouse

Level 10: Boss battle with Judge Smite

End credits

Regular villains (in order of appearance)

Vacature “Microsoft Technisch consultant” bij Nokavision

Alex Thissen — Mon, 29 Nov 2010 13:55:26 GMT

Het bedrijf Nokavision uit ‘s-Hertogenbosch heeft een interessante vacature beschikbaar. Ben je op zoek naar een nieuwe uitdaging in het zuidelijke deel van Nederland, lees dan de beschrijving eens door.

Ik ken Nokavision als een bedrijf dat graag bezig is met nieuwe Microsoft technologien. Ze hebben een sterk verleden met document management en document stromen en business process management in organisaties. Om meer te weten te komen over Nokavision, kun je natuurlijk hun website bezoeken. Daar vind je onder andere case studies van eerdere klanten, hun producten (o.a. Skelta, StreamServe en Captaris producten) en de diensten die ze bieden.

Hieronder de vacaturetekst. Ben je geinteresseerd, neem dan contact op met Rob Steenvoorden. De contactgegevens staan onderaan.

Microsoft Technisch consultant

Doel van functie

Als Consultant maak je deel uit van een professioneel team dat als standplaats Den Bosch heeft. Onze werkzaamheden vinden plaats aan oplossingen die als product in de markt worden gezet. Je werkt aan de ontwikkeling, uitbreiding en beheer van Microsoft oplossingen. Je werkt met professionele collega’s met diverse ideeën, achtergronden en werkwijzen. Je wordt aangemoedigd je technische vaardigheden uit te breiden en je thuis te voelen in een “lerende” cultuur.

Verantwoordelijkheden en taken

Je bent verantwoordelijk voor de ontwikkeling, oplevering en onderhoud van nieuwe en bestaande producten op basis van Microsoft technologieën. Je werkt met de modernste Microsoft technologieën waaronder C#, .NET 4, Silverlight 4, WCF RIA Services, Entity Framework, Enterprise Library, SQL Server. Tevens maken we gebruik van Workflow technologie die .NET gerelateerd is.

Ideale profiel

Ervaring met C# en .NET
Junior/Medior software ontwikkelaar
Je bent accuraat en hebt een actieve houding
Belangstelling voor complexe bedrijfskundige en technische omgevingen
Gewend om volgens methodieken te werken

Een pré is:

Kennis van UML & Design Patterns
Kennis van en ervaring met Silverlight en/of WPF

Arbeidsvoorwaarden

Nokavision is een zeer sociaal bedrijf. Nokavision biedt uitstekende primaire/secundaire arbeidsvoorwaarden. De opleidingsmogelijkheden zowel intern als extern zijn uitstekend. Daarnaast besteden wij veel tijd en energie aan persoonlijke groei en ontwikkeling.

Wil je meer weten of reageren: stuur je bericht met CV naar r.steenvoorden@nokavision.com of bel met 073-6408490.

Two exam opportunities

Alex Thissen — Sat, 16 Oct 2010 20:46:48 GMT

Quick post on two beta Microsoft exams that you are allowed to participate in. Gerry o’Brien posted that the exams:

are now available to take. The beauty is that if you manage to pass the qualifying score on the beta exam, you also pass the exam as soon as it is released. Of course, it is also a good challenge for your brain and a test of your knowledge on the topic of the exam. When you’re into the business of training, coaching or other knowledge transfer areas, this is a great opportunity to find out which training, books and e-learning material is needed to prepare for this exam.

The Microsoft Learning website lists extra information on the exams 70-583 and 70-506. The exams seem to be the one exam to pass to acquire either the “MCPD: Windows Azure Developer 4” or “MCTS: Silverlight 4, Development” certifications.

You can take these exams for free if you use the promotion codes AZPRO and SL410 respectively. You need to enter these code at the Payment Information screen.

Time is limited, so be sure to register immediately at Prometric.

Arcade machines converted to Atari Lynx

Alex Thissen — Wed, 22 Sep 2010 10:51:15 GMT

The Atari Times has a really nice article “Arcade to Lynx”. It shows a graphical list of games that once lived as a standalone arcade machine and got converted to a game for the Atari Lynx. I had no idea there were that many arcade games. It is not surprising to see Atari’s own games, such as Xybots and Gauntlet, in the list. These Arcade games were new to me:

A.P.B.
Blockout
Hydra
Pac-Land
Road Riot
Tournament Cyberball
Xenophobe

At least, I had not seen them in the arcade halls (when those were still around).

Here’s is a sample from the site: Ms. Pac-man

Original Ms. Pac-man arcade machine

Atari Lynx conversion of Ms. Pac-man

The beauty of most conversion to the Lynx is the addition of extras. Take Ms. Pac-man again as an example. Besides the original gameplay including the intermissions between different level types, there are also new levels that are larger and landscape oriented instead of the normal portrait ones. Moreover, every round has a new level layout. I found at least 17 unique layouts.

New levels in Lynx version of Ms. Pac-Man

Also, there are cheats and easter eggs all over the place. In the case of Ms. Pac-Man you can get extra lives and lightning speed, plus you can skip levels. Obviously not available in the arcade machine.

For your convenience, here are the actions required to activate the cheats.

5 Extra lives:
PAUSE, OPTION 1, B, B, A, A, OPTION 1
Lightning speed:
PAUSE, OPTION 1, A, and OPTION 1. A lightning bolt will appear. Press B to use it.
Skip levels:
PAUSE, OPTION 1, B, B, B, OPTION 1, PAUSE and skip levels with OPTION 1

TIP: When pausing on the Handy emulator, make sure you use Q to pause instead of F5. “Pause” should appear on-screen.

Architecture of the Atari Lynx

Alex Thissen — Sun, 19 Sep 2010 22:26:00 GMT

The Atari Lynx is a handheld console that has two form factors over its lifetime. The Lynx I and II models have a different casing and internal layout, but hold nearly exact same electronic hardware. The main difference is lower power consumption and stereo sound (but less loud) for the Lynx II incarnation.

Atari Lynx I and II handhelds

This fragment found at Atari Lynx@Everything.com describes the Lynx fairly well:

The Lynx had two 16-bit co-processors running at 16 MHz each, nicknamed Mikey and Suzy. Mikey supported the sound engine and the video driver, the system interrupts routine, ComLynx support, and the system timers. Mikey was also responsible for loading the games with the 512 bytes of ROM it had for that function. Suzy supported the graphics engine and a math co-processor. The Lynx contains half a megabit of ROM. Game cards support up to 2 MB of ROM, but most contain either 128K or 256K, with only 3 games supporting 512K.

The various chips inside the machine are:

U1: (Mikey, see below)
U2: (Suzy, see below)
U3 and U4:
Lynx I – HM-50464-12
Lynx II - HY53C464LS-10 (Two 256 KB DRAM chips (64K X 4 nMOS general purpose Dynamic RAM, page-mode operation DIP-18, 256 cycles/4 msec)
U5: LM386 (Low voltage audio power amplifier)
U6: 4069 (CMOS 16 MHz Square wave oscillator)
U7: 74HC04 (Hex inverter, used multiple times)
U8: 74HC4040 (12-stage binary ripple counter; generates cartridge addresses A0-A10)
U9: 74HC164 (8-bit serial-in, parallel-out shift register; generates cartridge addresses A12-A19)
U10: Unknown
U11: 74HC74 (High Speed CMOS Logic Dual Positive-Edge-Triggered D-Type Flip-Flops with Set and Reset)
U12: LM386 (Low voltage audio power amplifier)

Mikey
16-bit custom CMOS chip running at 16MHz

MOS 65SC02	Processor running at up to 4MHz (~3.6MHz average) 8-bit CPU, 16-bit address space
Sound engine	4 channel sound 8-bit DAC for each channel (4 channels x 8-bits/channel = 32 bits commonly quoted) Lynx II has panning support Atari reports the range is "100Hz to above the range of human hearing"; spectrum analysis shows the range may go as low as 32Hz. Stereo with panning (mono for original Lynx)
Video DMA driver	Video DMA driver for LCD display 4096 color (12-bit) palette 16 simultaneous colors (4 bits) from palette per scanline (more than 16 colors can be displayed by changing palettes after each scanline)
System timers	8 System timers (2 reserved for LCD timing, one for UART)
Interrupt controller
UART (for ComLynx)	Universal Asynchronous Receive/Transmit Fixed framing format 8E1 (meaning an 8-way connection between two “users”) Baud rate up to 62500Bd
512 bytes ROM	Bootstrap and game-card loading ROM

Suzy
16-bit custom CMOS chip running at 16MHz

Blitter unit	Bit-map block transfer unit
Graphics engine	Hardware drawing support Unlimited number of high-speed sprites with collision detection Hardware high-speed sprite scaling, distortion, and tilting effects Hardware decoding of compressed sprite data Hardware clipping and multi-directional scrolling Variable frame rate (up to 75 frames/second) 160 x 102 "triad" standard resolution (16,320 addressable pixels) (A triad is three LCD elements: red, green, and blue) Capability of 480 x 102 artificially high resolution
Math co-processor	Hardware 16-bit multiply and divide 16-bit × 16-bit → 32-bit multiply with optional accumulation; 32-bit ÷ 16-bit → 16-bit divide Parallel processing of CPU and single multiply or divide instruction
Controller Input	Handles input from joypad, pause, option and fire buttons

Parts of the Mikey and Suzy information was taken from the Atari Lynx FAQ, which has more detailed information on all physical aspects of the Atari Lynx.

Bastian Schick has the electronic schematics up on his website (in a single ZIP file, but with two images of board split in left and right side). He also has a file listing the pin layout of the cartridge port.

Another famous Lynx developer Matthias Domin has the Lynx I and Lynx II opened up and describes what part is what.

Game endings at Video Game Museum

Alex Thissen — Sun, 19 Sep 2010 18:35:45 GMT

Some games are just too hard to finish, or take too much time to do so. And if you did, on a device like the Atari Lynx, it is hard to show others what the end scenes and screens of the game look like. The quality of photographs usually don’t show this very well. Thanks to the emulators it is possible to both save games (by storing the entire state of the emulator) and create high quality images of the screens.

Ending for Shadow of the Beast

Apparently over at The Video Game Museum they have been collecting game endings for a number of games. One of the collections is the Atari Lynx game endings. I must say that there is an impressive number of games listed with screenshots showing the last sequences of the game. There are even some games I have never finished, but was curious to see what it would be like.

Ending for Kung Food

Go check it out yourself. Now all I need to find is a website that has the savegames for a decent emulator (like Handy), so I can relive those endings myself. If it is not out there, I guess that I will need to create one myself.

Ending for Viking Child (which I did finish myself)

Google Android versus Atari Lynx’s Gauntlet the Third Encounter

Alex Thissen — Sun, 19 Sep 2010 16:25:01 GMT

Personally, I haven’t played Gauntlet III on the Lynx much. Consequently I hadn’t noticed the similarities between the Android character and the new logo of Google’s mobile operating system.

To wet your Lynx appetite some more, here are some additional screenshots:

Go read the full story here.