Slashdot Mirror

Seems like one of those "wink wink nudge nudge" statement I make about *trying* games out on my GBA emulator.

That may be true for you, but it isn't true for everyone. I've actually written several programs for the Game Boy Color using emulators and the Bung XChanger and flash carts. I also wrote my own assembler and linker for the GBC.

Just because tools can be used for piracy doesn't mean everyone uses them that way. Writing programs and development tools for limited consoles can be a lot of fun and a great learning experience.

Seems like one of those "wink wink nudge nudge" statement I make about *trying* games out on my GBA emulator.

That may be true for you, but it isn't true for everyone. I've actually written several programs for the Game Boy Color using emulators and the Bung XChanger and flash carts. I also wrote my own assembler and linker for the GBC.

Just because tools can be used for piracy doesn't mean everyone uses them that way. Writing programs and development tools for limited consoles can be a lot of fun and a great learning experience.

Seems like one of those "wink wink nudge nudge" statement I make about *trying* games out on my GBA emulator.

That may be true for you, but it isn't true for everyone. I've actually written several programs for the Game Boy Color using emulators and the Bung XChanger and flash carts. I also wrote my own assembler and linker for the GBC.

Just because tools can be used for piracy doesn't mean everyone uses them that way. Writing programs and development tools for limited consoles can be a lot of fun and a great learning experience.

Seems like one of those "wink wink nudge nudge" statement I make about *trying* games out on my GBA emulator.

That may be true for you, but it isn't true for everyone. I've actually written several programs for the Game Boy Color using emulators and the Bung XChanger and flash carts. I also wrote my own assembler and linker for the GBC.

Just because tools can be used for piracy doesn't mean everyone uses them that way. Writing programs and development tools for limited consoles can be a lot of fun and a great learning experience.

Look What I Did To The Bitch!

started working on a new key server..will probably implement it into waste sometime.

just an add/delete feature at the moment:

http://waste.acz.org/keys.php

http://waste.acz.org is waste mirror.

started working on a new key server..will probably implement it into waste sometime.

just an add/delete feature at the moment:

http://waste.acz.org/keys.php

http://waste.acz.org is waste mirror.

A Link if you want one in that format.

Actually, one of my friends started that about three years ago. See my other post about it or grab it here: http://david.acz.org/duke/

About three years ago, a friend of mine, Rusty Wagner, decided it would be cool to have a version of Duke 3D that worked in Windows. Rusty already had a game engine that he'd been writing, so he modified it to load the Duke 3D maps. He also added menus, a console and some other cool stuff. The result is actually quite good. Duke 3D maps look very nice when rendered using OpenGL or Direct3D.

You can grab the source code with precompiled duke.exe or view some screen shots.

Someone at his school found the source and ported it to SDL: http://openduke.sourceforge.net/

Unfortunately, the project never went anywhere, but there is still a lot of useful code there.

About three years ago, a friend of mine, Rusty Wagner, decided it would be cool to have a version of Duke 3D that worked in Windows. Rusty already had a game engine that he'd been writing, so he modified it to load the Duke 3D maps. He also added menus, a console and some other cool stuff. The result is actually quite good. Duke 3D maps look very nice when rendered using OpenGL or Direct3D.

You can grab the source code with precompiled duke.exe or view some screen shots.

Someone at his school found the source and ported it to SDL: http://openduke.sourceforge.net/

Unfortunately, the project never went anywhere, but there is still a lot of useful code there.

About three years ago, a friend of mine, Rusty Wagner, decided it would be cool to have a version of Duke 3D that worked in Windows. Rusty already had a game engine that he'd been writing, so he modified it to load the Duke 3D maps. He also added menus, a console and some other cool stuff. The result is actually quite good. Duke 3D maps look very nice when rendered using OpenGL or Direct3D.

You can grab the source code with precompiled duke.exe or view some screen shots.

Someone at his school found the source and ported it to SDL: http://openduke.sourceforge.net/

Unfortunately, the project never went anywhere, but there is still a lot of useful code there.

Actually, remapping the keys for use in the normal calculator modes is not a very simple thing to do on the TI calcs. You'd have to register an interrupt handler, and I think the only free memory the calc won't shuffle around is the memory used for the graphics screen. So, while you had the buttons remapped, you couldn't graph.

Right, the 82 and 85 did not have assembly support built in, so interrupt handlers are more trouble. Though quite possible. One of the shells with interrupt support comes with a demo that leaves a grayscale background while in the TI-OS.

However, I was talking about the TI-86, which does have assembly support and has a lot of built in hooks (such as the [sqrt] programs). I did a lot of programming in assembly for that calculator and if you look on ticalc.org, you will find a lot of demos that show you how to do things like that in the TI-OS. A good one to look at is Kirk Meyer's April Fools program. It completely rearranges the keyboard. A good joke to play on someone :)

The hooks for the 86 let you do a lot of stuff. You can remap the keyboard, modify system menus, modify the parser, change output, hook into the grapher, run programs at startup, etc. Pretty much anything you want to do is possible if you're willing to do some digging in the ROM. The hardest part is keeping the TI-OS from crashing when you modify things that you shouldn't.

If you're interested, take a look at this set of hook demos by Clem Vasseur. It's a good example of what can be done and if you actually want to write a hook, then most of the hard work is done for you:

http://david.acz.org/hooks.zip

The TI-83 line has built in assembly support, but it is not as good as the 86's, and those calculators suck anyway, so do not consider buying them. The 86 is the best calc overall, especially if you want to have fun programming. The 89 and 92 are ok, have more RAM and a faster CPU (68k instead of z80), but aren't as "clean". The 86 lets you do cool grayscale and has a lot of free RAM to play with. The 83 line can't really do grayscale, don't have much RAM and the screen is smaller (96x64 vs 128x64). The 86 is a fun device to progam.

While TI graphing calculators don't have the hex buttons where you want them, they are very programmable. The TI-86 is reasonably priced and very programmable. You could write yourself a simple conversion app with remapped buttons in TI-BASIC, or go all out and integrate it into the TI-OS using an assembly language program. There are many sites with resources to help you and assembly language mailing lists to get help on. You can do so many cool things with these calculators. Remapping the keys and writing a simple conversion app would be simple.

While TI graphing calculators don't have the hex buttons where you want them, they are very programmable. The TI-86 is reasonably priced and very programmable. You could write yourself a simple conversion app with remapped buttons in TI-BASIC, or go all out and integrate it into the TI-OS using an assembly language program. There are many sites with resources to help you and assembly language mailing lists to get help on. You can do so many cool things with these calculators. Remapping the keys and writing a simple conversion app would be simple.

While TI graphing calculators don't have the hex buttons where you want them, they are very programmable. The TI-86 is reasonably priced and very programmable. You could write yourself a simple conversion app with remapped buttons in TI-BASIC, or go all out and integrate it into the TI-OS using an assembly language program. There are many sites with resources to help you and assembly language mailing lists to get help on. You can do so many cool things with these calculators. Remapping the keys and writing a simple conversion app would be simple.

This is better. This type of thing was known to crash Windows 95/98 machines.

Hah, I have no clue is this is off topic or not...mainly because my eyes are shooting hooks between the eyelids in order to shut themsevles, and it is only 7:30...but you want something to do with AOL CDs?! Try, creating a full setup of hub caps for a car, along with an antenna decor an hood ornament...and then the next night...take the other 1/1000th of your stash of millions(that you took from the stupid aol/walmart cd campaign) and create a birthday gift-wrapped door on the apartment door (well, i actually didn't know this person at all, but i knew it was their birthday, so of course I had to help out)... AolCar AolDoor

Hah, I have no clue is this is off topic or not...mainly because my eyes are shooting hooks between the eyelids in order to shut themsevles, and it is only 7:30...but you want something to do with AOL CDs?! Try, creating a full setup of hub caps for a car, along with an antenna decor an hood ornament...and then the next night...take the other 1/1000th of your stash of millions(that you took from the stupid aol/walmart cd campaign) and create a birthday gift-wrapped door on the apartment door (well, i actually didn't know this person at all, but i knew it was their birthday, so of course I had to help out)... AolCar AolDoor