New RespwQt Fork

[ebiguy]

About the idea of running a CAR/ROM file from RespeQt:

 

The scope of this feature would be limited to 8K/16K non bank switched cartridges.

And many of them contain code to write on the ROM area so that the program is destroyed if in RAM.

So if we remove the cartridges using bank switching and the cartridges having a protection, how many cartridges still remains?

 

We could also add a patch database in RespeQt so that the cartridge is patched on the fly to remove the protection (the write instructions).

These patches have already been done when the cartridges were converted to files.

But maybe a huge work for not so many titles...

 

Any comments?

Edited March 10, 2020 by ebiguy

[DjayBee]

I guess that for every cart which could be handled this way, there are already two XEXs doing exactly the same. 

[ebiguy]

41 minutes ago, DjayBee said:

I guess that for every cart which could be handled this way, there are already two XEXs doing exactly the same

Yes, that's why I ask if it is really useful to add such a feature. I guess not.

Big dev for games that are already available as XEX...

[+Philsan]

There are some games that in CAR version work on 64K machines and in XEX version need memory expansion.

 

But if this feature would be limited to 8K/16K non bank switched cartridges then yes, I think it would be not so useful.

[ebiguy]

TO RESPEQT USERS: This thread contains deprecated RespeQt versions.

The latest stable release is at https://github.com/RespeQt/RespeQt/releases

 

TO CONTRIBUTORS: The official repository is now https://github.com/RespeQt/RespeQt.git

The ebiguy repository won't be updated anymore.