nanochess

Gulkave was misplaced alphabetically. Updated games from Good Deal Games: Search for the Stolen Crown Jewels 2 now is sold out and there is only 1 remaining copy of Cye. Included limit date for BATCH of Team Pixelboy games.

Check my Colecovision Homebrew Availability list right here http://www.atariage.com/forums/topic/206287-colecovision-homebrew-availability-list/ Indeed there are a few copies of Pooyan available through Good Deal Games.

I'm so glad that I ordered my SGM just on time

Just I've found a video of hands on Princess Quest by manoau2002

From its statistics it says 3754 software titles

I've asked same some time ago. It looks like that list doesn't exit. You can check http://www.generation-msx.nl it indexes most of old MSX games

It would take one or two hours as you don't know the maps, supposing your little agent can stay alive for enough time as I've distributed zombies generously over the map Yes, the maps are the same. I suggest you to map it as you progress. There are no hidden tricks, in fact the game is so compressed that there was no space for tricks at all. Several people has asked for cooperative mode, but currently there is none.

Maybe the thread could be renamed top 5 pure Colecovision games of 2012 and another thread could be started for top 5 pure SGM games

I've used a trick in Princess Quest, as originally it was developed for MSX it used the powerful basses from AY-3-8910. As I've complete control over the game, the music was developed with bass using channel B. On porting to SN76489, I used a trick first discovered by Daniel Bienvenu, the noise channel can be programmed to a fixed envelope instead of noise, it divides the frequency by 15. You program the channel 3 (noise) for fixed envelope and variable frequency (uses channel 2 that you should mute) and you put in channel 2 frequency the original data value divided by 15. It sounds like a harmonic but does the trick and Princess Quest have its basses , I've done same for upcoming Mecha-8.

Right

The working games are all 16K, the others are mixed 24K / 32K.

The AtariMax SD Cart cleans up memory RAM and VRAM, so some bugs can go unnoticed until final PCB. Early after mounting first PCB, Pixelboy discovered a bug in Princess Quest that fortunately was solved in time, it was VRAM not cleaned fully at start so appeared a fast-flashing letter in a corner during game. So J-F, you've to clean memory completely (RAM and VRAM,) and also to check that all the program uses the same zone of RAM ($7000-$73ff)

Thanks! that means I did something right

For me is only a hobby to have the games that somehow I like and some CIB just for the pleasure of having them, so far I've 40 different cartridges and some CIB. My definition of a serious collector is the guy that manages to have every cartridge available Besides he has two copies of each game (one CIB carefully guarded and one loose cartridge for playing) He has played each game, even those that aren't worth playing. He knows every possible label variation and edition, he knows where the cartridges used to be sold and the original price, he knows the inner details of game companies. He is a great merchant, getting the most rare cartridges at an amazing value. And someday he will complete his collection and it will appear at eBay saying something like "all the Atari games" for mere 1 million dollars or so.

I was serious . But anyway 10 weirdo points for you, no good collector would leave his dog to enter the place of his sacred collection It's more probable that someone needs a replacement box just because he sat down over it

By the way, I had an idea when the pre-order date finishes. You could sell the extra boxes. I'm thinking that someone with a lot of extra space (I'm not that guy, unfortunately) could mount a kind of exhibitor in his basement with all these boxes neatly organized. You know, pyramids and some other shapes like in commercial centers.

There is a rumour that the Z800 was so powerful that the USA military took it for its missiles. Anyway Zilog finally released it in 1989 as the Z280, it provided protected memory, bank switching and a lot of other things. It could have been very good for a 16-bits UNIX like the one in PDP-11 or even Minix, but unfortunately it was too late. Finally the Z280 was discontinued my middle 1990's and completely erasen from Zilog history (now it's very hard to find any info) I've saw also a Z380 that had 32 bits registers, it doesn't had success and also was wiped out.

I've played a lot of Burger Time and never have seen the bug.

It remembers me when I was a kid, I used to read Compute! magazines. Always I was wondering why the screenshots were looking like drawings done by hand. Later I was running my own contest for myself: is real this screenshot or not? I took it very seriously. Besides I slowly became disappointed when I was able to read the descriptions and discovered that the game descriptions were way too good versus the real game.

It is mainly to simplify things. Anything declared in .h would make many eyebrows raised. Just is the way that C programmers have evolved. There is nothing written about it. Yes, you can use the 'extern' keyboard all over your enemies.h file. And include it in your enemies.c, the C language automatically will "fuse" the declarations and there are no conflicts. So you can do this: enemies.h (to be included everywhere it is needed) struct enemy { }; extern struct enemy enemies[40]; extern void new_enemy(int); enemies.c #include "enemies.h" struct enemy enemies[40]; /* The real declaration */ void new_enemy(int type) { ... }

Yep, there is some kind of magic of getting a cart out of its box. I've bought a Zaxxon CIB for CV somewhat damaged and it had some yellow particles glued to front manual that I've removed. At some point I hope really that it was only old glue and at some point I really don't want to know what it was originally

You're missing prototypes in header files. By example, if you have a 'movement.c' file containing a function void move_enemy(int which), then you should have a prototype in 'movement.h' looking like this 'void move_enemy(int);' so other modules can call it. Also if you're referencing variables from other modules you should use things like 'extern int var;' in the module or in a header. The rule is 'int var;' only appears in one module, and every other module or header refers to it via 'extern'.