Myself curious to write a GB emulator... how do you get images? After a quick search I see a list of "homebrews" on a collection repo on GitHub [0]. Is there a particularly good place to find games? [0] https://github.com/gbdev/awesome-gbdev#homebrews
Gameboy.live: A basic Gameboy emulator with terminal “cloud gaming” support
21–30 of 51 posts
Re: Gameboy.live: A basic Gameboy emulator with terminal “cloud gaming” support
#22Earlier quoted context omitted.
Highly unlikely, given all the other GB emulators that already exist, some of which are far more famous.
Yeah, until you start hosting roms I don't think Nintendo cares (although possibly begrudgingly). Once you do though... bad times. Nintendo has even used existing open source emulators themselves in commercial products.
Source? I'd love to read more about that.
Re: Gameboy.live: A basic Gameboy emulator with terminal “cloud gaming” support
#23Re: Gameboy.live: A basic Gameboy emulator with terminal “cloud gaming” support
#24Earlier quoted context omitted.
Fork it while you can!
It is more important to clone it, so that you have a local copy on your PC forking is just a gesture, especially for obviously hot repos. a takedown of 1 can takedown all the forks
Even as a "backup", it's pointless, because it's all Copy-on-Write, there's no backup.
As if they never learned to use the "Star" button to bookmark...
Personally, I don't fork any repos unless I'm working on a derived program, or working for a patch, even so, I'll delete my forked repos as soon as the patches are accepted (if it's a one-time contribution), so these forked repos won't spam my own list.
Re: Gameboy.live: A basic Gameboy emulator with terminal “cloud gaming” support
#25Earlier quoted context omitted.
Yeah, until you start hosting roms I don't think Nintendo cares (although possibly begrudgingly). Once you do though... bad times. Nintendo has even used existing open source emulators themselves in commercial products.
> Nintendo has even used existing open source emulators themselves in commercial products. Source? I'd love to read more about that.
Re: Gameboy.live: A basic Gameboy emulator with terminal “cloud gaming” support
#26Earlier quoted context omitted.
Yeah, until you start hosting roms I don't think Nintendo cares (although possibly begrudgingly). Once you do though... bad times. Nintendo has even used existing open source emulators themselves in commercial products.
> Nintendo has even used existing open source emulators themselves in commercial products. Source? I'd love to read more about that.
Re: Gameboy.live: A basic Gameboy emulator with terminal “cloud gaming” support
#27Earlier quoted context omitted.
Yeah, until you start hosting roms I don't think Nintendo cares (although possibly begrudgingly). Once you do though... bad times. Nintendo has even used existing open source emulators themselves in commercial products.
> Nintendo has even used existing open source emulators themselves in commercial products. Source? I'd love to read more about that.
https://waxy.org/2004/07/jaleco_borrows/
Nintendo has written or contracted a lot of emulators themselves. The grandparent may be thinking of the pervasive use of the iNES header format, which originated with an unofficial (though not open source) emulator:
Re: Gameboy.live: A basic Gameboy emulator with terminal “cloud gaming” support
#28A sign of the times: the use of the term "cloud gaming" to describe what would once be called "network play". The emulator will firstly break at the ROM entry point 0x0100 in debug mode, which is the entry point of the game program. That start address is the same as in CP/M, and subsequently DOS 16-bit COM-format binaries. I wonder if Nintendo was inspired by that.
The DMG boot ROM fits into the top 0x100 bytes. To protect it from being snooped, the last instruction shuts off the boot ROM by flipping a register that can’t be flipped back, mapping the top 0x100 back to the cartridge (and allowing the cartridges interrupt vectors to be installed.) So, there is no jump to 0x100 at any point; they just fit the DMG boots ROM perfectly into 0x100 bytes and control flow leaves bootstr…
Re: Gameboy.live: A basic Gameboy emulator with terminal “cloud gaming” support
#29Earlier quoted context omitted.
The DMG boot ROM fits into the top 0x100 bytes. To protect it from being snooped, the last instruction shuts off the boot ROM by flipping a register that can’t be flipped back, mapping the top 0x100 back to the cartridge (and allowing the cartridges interrupt vectors to be installed.) So, there is no jump to 0x100 at any point; they just fit the DMG boots ROM perfectly into 0x100 bytes and control flow leaves bootstr…
The fact that it was undumped until recently makes me want to understand this more. Can you ELI5?
Fault injection is a method to cause microprocessors to execute instructions "incorrectly" by manipulating external factors (clock frequency, input power, etc). Getting the CPU to fail to write to a memory address, or flipping the truth of a comparison instruction, and other "glitches" can influence execution of security-sensitive code and ultimately undermine security mechanisms.
The original Gameboy ROM was dumped by physically de-capping the chip and reading out the bits: https://dot-matrix-game.blogspot.com/2014/01/boot-roms.html
Re: Gameboy.live: A basic Gameboy emulator with terminal “cloud gaming” support
#30A sign of the times: the use of the term "cloud gaming" to describe what would once be called "network play". The emulator will firstly break at the ROM entry point 0x0100 in debug mode, which is the entry point of the game program. That start address is the same as in CP/M, and subsequently DOS 16-bit COM-format binaries. I wonder if Nintendo was inspired by that.
Probably because the lower addresses are for the interrupt vector table.