temu-vsb
TEMU ("Tandy Emulator") and VSB ("Virtual Sound Blaster"), two nifty MS-DOS TSR utilities originally developed by Andrew Zabolotny (Андрей Заболотный). (by volkertb)
gb-test-roms
Collection of Game Boy test roms. (by retrio)
| temu-vsb | gb-test-roms | |
|---|---|---|
| 3 | 17 | |
| 60 | 512 | |
| - | 6.3% | |
| 0.0 | 0.0 | |
| about 3 years ago | almost 10 years ago | |
| Assembly | Assembly | |
| GNU General Public License v3.0 or later | - |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
temu-vsb
Posts with mentions or reviews of temu-vsb.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-12-03.
-
Janet Jackson music video declared a cybersecurity exploit
I could have sworn it was named "Sound Blister" or some other hideous pun, but I can't find any trace of that name on the Internet now. I did find VSB (Virtual Sound Blaster) which looks right and was out around the same time period, so it's possible I'm just misremembering the name.
- What's everyone currently working on?
-
8086 emulator part II. Now with Tandy graphics and sound!!
Cool, thanks for the links. Yep Adlib/OPL will probably be next. I have already hardcoded basic SoundBlaster PCM playback (Sending samples with https://github.com/volkertb/temu-vsb/blob/main/sbemu/sbdma.pas), though not using interrupts/full DMA yet.
gb-test-roms
Posts with mentions or reviews of gb-test-roms.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-06-08.
-
What's everyone working on?
Make sure you incorporate testing your implementation with test roms: https://github.com/retrio/gb-test-roms Do this as early in the project as possible. This will save you a huge migraine later on.
-
Some GameBoy games running at half speed
Have you tested your emulator against blargg's instruction timing test ROM? I believe this one only checks cycle counts, not memory timings: https://github.com/retrio/gb-test-roms/tree/master/instr_timing
- Need some help on how to progress with my gameboy emulator after opcodes.
- Getting weird desync on Super Mario Land (GB) between the attract mode and real gameplay. Any ideas?
-
Me again... Blarg's Gameboy test ROM
Yeah the source for cpu_instrs is in github. https://github.com/retrio/gb-test-roms/tree/master/cpu_instrs/source
-
What memory address do I load Blaargs test ROMs into? Is it 0x0100?
I actually have a question about this. I've been building a Gameboy emulator, the CPU works but when it runs the RET instruction the PC jumps to some really high address like 0x2000 or something when it's meant to jump to somewhere around 0x400 instead (after comparing it with another GB emulator). I think the RET address is meant to be read from HRAM, where the stack is stored, but when I look there it is the value around 0x2000 like I mentioned earlier. Are there any special quirks with this section of memory that I might not have implemented? I'm pretty much just reading and writing from an array for HRAM at the moment. I'm having the issue on one of blarggs cpu-instrs test roms https://github.com/retrio/gb-test-roms/blob/master/cpu_instrs/cpu_instrs.gb
-
Best documentation for the details?
So just start with implementing the CPU's fetch/decode/execute loop and a rudimentary memory bus, so that you can run simple test ROMs. You don't even need a display for many test ROMs (like Blargg's well-known test suite, which writes the results to the serial port as well as the display). After that you can do test-driven development (in a way) and focus on making more and more tests pass. Don't worry about details until you need to.
-
Gameboy emulator blargg test 02 EI failed #2
It looks like the test enables interrupts and then invokes the timer interrupt.
- Gameboy Blargg test 03 - Infinite loop
- [GameBoy] Problem with CD instruction.
What are some alternatives?
When comparing temu-vsb and gb-test-roms you can also consider the following projects:
DK86PC - A WIP Intel 8086 and IBM PC 5150 emulator.
jitboy - A Game Boy emulator with dynamic recompilation (JIT)
rust64 - Commodore 64 emulator written in Rust
mooneye-gb - A Game Boy research project and emulator written in Rust
gba-tests - A collection of Game Boy Advance tests.