BOUNTY for Taito G-Net CF Conversions.

I am fully down the G-Net rabbit hole at this point...

GarNET Launcher POC.

You'll be able to compile your own libraries or just download an img that is already built. Looking into exiting back to the menu by holding start, that kind of stuff. 8GB could definitely hold the full existing library, but some of the new Q-Sound/Yamaha/Namco conversions are a lot bigger.

Need to do a bit of work to get the existing conversions going.

https://photos.app.goo.gl/8uRupoQcgQnDjbSf7
What extra would be needed to run this besides a big enough card?
 
What extra would be needed to run this besides a big enough card?
Just a big card, nothing else needed. I'm working on an initial public testing build that includes all G-Net games and current conversions; I think the first build will require a 2GB card. I'd recommend a working 8GB card though considering upcoming Namco System 10/11/12 conversions and PSX conversions.
 
Just a big card, nothing else needed. I'm working on an initial public testing build that includes all G-Net games and current conversions; I think the first build will require a 2GB card. I'd recommend a working 8GB card though considering upcoming Namco System 10/11/12 conversions and PSX conversions.
Is it possible to increase compatibility with various CF cards by creating a new ModBIOS?
 
I have tested various games using CF and identified several titles that exhibit issues. I would like to share information regarding these problematic games here.

For the tests, I used ROM data compatible with the latest version of MAME, along with a 64MB CompactFlash (CF) card manufactured by SanDisk.

• Zoku Otenamihaiken (V2.05J 2003/05/12 18:00) [The system enters a reset loop once the game finishes loading.]

• Shikigami no Shiro - internal build (V1.02J 2001/09/27 18:45) [The system enters a reset loop once the game finishes loading.]

• Mawasunda!! (V2.08J 2000/02/01 11:02:54) [The system enters a reset loop once the game finishes loading.]

• Chaos Heat (V2.08J 1998/09/25 17:00) [The demo sequence and in-game loading are extremely slow; the game resets after a short while.]

• Tondemo Crisis! [The game reset suddenly during play—specifically, during the pole-crossing scene.]

I am not certain whether these issues are specific to my own setup, but I hope this information proves useful to others.
 

Attachments

  • IMG_9124.jpeg
    IMG_9124.jpeg
    354.2 KB · Views: 2
Last edited:
I have tested various games using CF and identified several titles that exhibit issues. I would like to share information regarding these problematic games here.

For the tests, I used ROM data compatible with the latest version of MAME, along with a 64MB CompactFlash (CF) card manufactured by SanDisk.

• Zoku Otenamihaiken (V2.05J 2003/05/12 18:00) [The system enters a reset loop once the game finishes loading.]

• Shikigami no Shiro - internal build (V1.02J 2001/09/27 18:45) [The system enters a reset loop once the game finishes loading.]

• Mawasunda!! (V2.08J 2000/02/01 11:02:54) [The system enters a reset loop once the game finishes loading.]

• Chaos Heat (V2.08J 1998/09/25 17:00) [The demo sequence and in-game loading are extremely slow; the game resets after a short while.]

• Tondemo Crisis! [The game reset suddenly during play—specifically, during the pole-crossing scene.]

I am not certain whether these issues are specific to my own setup, but I hope this information proves useful to others.
It could also be your GNET board ! Do you have a different card - like SANDISK ULTRA II ?
also goto 5.1V on 5V line (AT THE PCB CONNECTOR)
 
Is it possible to increase compatibility with various CF cards by creating a new ModBIOS?
It was aje_fr :) who dumped and released the ModBIOS arcade BIOS back in the day.

Having all the games on one card is a great idea. Not only is it a convenient solution, but you also avoid the risk of damaging the pcmcia pcb socket through intense use and frequent game changes.
Also, I'm not sure if you're aware, but flashing the Flash memory chips on the Taito G-NET board reduces their lifespan.
At some point, you won't be able to install games on them anymore.

We have no idea how many times they were flashed during commercial operation before ending up in our hands.
Plus, the write cycles listed in the manufacturers' datasheets are mostly approximate and marketing figures.
I've already had to replace all the Flash chips on one of my three motherboards.
 
GarNET is coming along nicely. Within the next couple of days I'm hoping to be able to release a build for everyone to try out. I've spent the time I've had in the last day or so making the older G-Net games/conversions compatible with GarNET because they work differently than the way I did my conversions, as previously discussed. This is mostly complete.

What is left to do:

Must have:
-Test each "legacy" game to make sure they load and work within GarNET (I'll do some surface testing before release but will need everyone's help with this)
-Figure out one stickler (Space Invaders) that I couldn't make GarNET-compatible as easily as the others

Want to have:
-Service menu settings for each game should persist after power off
-Add a universal reset button back to the GarNET menu

Nice to have:
-A much simpler way for people to compile their own GarNET game libraries (throw the games in a folder, click a file)

But at a very basic level, I am probably around 24-48 hours away from having a build of GarNET that will launch and play the full G-Net library and all current conversions.

Also, I was testing Aqua Rush and Tenkomori Shooting before bed last night and they are both ready to rock, I'll upload them after work.
 
Back
Top