emulator

Pick a game, write a server emulator for it. This is a great way to use all your skills up to this point.

So to be selfish: Instead of adding a terminal emulator, I want my Chrome from 2 years ago back, which was fast, bug free and did not hang.

The emulator's performance is so bad it's unusable. The tablet section of the market is empty of real tablet apps.

Putty is a well known SSH client and terminal emulator. On seeing the name WebPutty I'd believed Putty had been ported to a web interface.

I'm pretty scared of Eclipse and the slow-as-hell emulator doesn't sound fun, but coding layouts that don't involve lots of "how tall is this text for this given width?" calculations is a welcome addition.

Shameless plug below: Last year, inspired by Bellard's jslinux, I too wrote an emulator that can run Linux on the browser. Only I was lazy and emulated the vastly easier LatticeMico32 processor.

I package this enyo app in a second's time and it's up running the same code on the device or emulator, and it all feels native to the OS. As long as the code is the same, I don't care if you package it in a cup cake. Enyo is actually a very good idea.

Nowadays, when I teach I meet kids who know python/html/php, fiddle with minecraft mods, jailbreak their android tablet so they can run a GBA emulator, etc. all the time.

All of the in circuit emulators up to the 386 had a 'bond out' version in the emulator pod that gave you access to internal state of the chip. Others have pointed out the key for loading replacement microcode, another 'feature' to fix bugs in the field and do diagnostics.

The Android emulator fought me a little so I started just debugging on my actual device. Debugging certain problems can be difficult, Eclipse can cause headaches and throw random nonexistent exceptions, etc.

I spend some long, late evenings with the in-circuit emulator and the logic analyzer, trying to figure out what the hell was going on. Eventually, I was able to determine that it only happened if the signal was delivered while the system was trying to return from handling a page fault for the process that was receiving the signal.

The emulators were created with code that was stolen. Google is simply cracking down on licensing violations. They're not taking a stance against emulation in general, or anything like that. I'm sure that if you submitted an emulator that you actually wrote, rather than stealing, and sold it, it would stay up just fine.

Taking the time to isolate the problem and repair the crystal on a 30-year-old computer, when you could as easily have used an emulator or picked up another one on eBay, just because it's more fun to fix it yourself - that's pretty much the definition of a hacker, right there.

I wrote a NES emulator for ExciteBike 64, so that the original 8-bit ExciteBike could be played as an unlockable level. The hardest part was getting the audio to sound approximately right! Fun fact: NES Excitebike supported saving and loading your custom tracks to the Famicom Data Recorder. The USA version of the FDR was never released, but the USA version of NES Excitebike still had all the save/load code+functionality built in. When you tried to save a track it would just hang for a while before returning to the menu. After figuring out where the save/load routines were, and where the track was stored in RAM, we were able to put hooks in the emulator to save the tracks to the N64 cart.