Just for info:
The removal of the border color changes is part of the patch "AH" for the C65 ROM.
So if you already use the patch "AH" there is no need for another patch.
The removal of the border color changes is part of the patch "AH" for the C65 ROM.
ah, I didn't know that... only slowly getting my bearings, and the border annoyed me 
and the border annoyed me
Me too!
Because it was not intended to be in the final ROM, I think, it's our "moral right" to remove it! 
By the way, I'm thinking to (optionally) put a patcher into Xemu for ROM (first it would be checked if it's that version - by checksum or so, for the whole ROM -, of course, which can be patched). The reason, that C65 ROM must be supplied by the user. It's a pain enough for many people, if we say, let's patch it first yourself, then it would be even more pain. So I thought it would be a nice idea. So the user still needs to supply the C65 ROM as their own, but at least no need to patch themselves. I wouldn't think it's a legal problem (like including the ROM would be ..) since it's just few bytes, etc, not even the original content, but the modified bytes ...
What do you think, guys?
So the user still needs to supply the C65 ROM as their own, but at least no need to patch themselves.
That's the way I use in the Xemu live system. Selecting the C65 ROM from stick/sdcard/whatever and after loading it, it will automatically be patched for the use in Xemu.
Putting a patcher into Xemu would be a good idea, but you only have to patch the ROM once. Then you can use this patched ROM as long as you want. So I would not spent too much time for a patcher, because you don't need it very often.
An automatically patcher will only be a legal problem, if the included patch file would be under copyright.
Actually I would patch on load-time, and even then optionally can be turned on/off. It's easier than writing routines to write back patched ROM etc, just patch on loading. If it's set to always patch on-load anyway, it virtually "feels" as being a permanent patch, but easy to turn off, instead of writing the file again to "revert back": just do not patch it on-load in the future ...
Hi LGB-Z,
we have bspatch and bsdiff built into the m65connect tool already, together with the BIT -> COR and BIT -> MCS converter.
These tools work even without a MEGA65 connected.
We hope, that in the future more people will experiment with the ROM that's why we thought, we support this from the beginning.
For me i.e. i have several patches always available, like Snoopy s Internal Drive ID changer, German Umlauts, Border fix.
So i can easily patch together whatever i need
Display MoreHi LGB-Z,
we have bspatch and bsdiff built into the m65connect tool already, together with the BIT -> COR and BIT -> MCS converter.
These tools work even without a MEGA65 connected.
We hope, that in the future more people will experiment with the ROM that's why we thought, we support this from the beginning.
For me i.e. i have several patches always available, like Snoopy s Internal Drive ID changer, German Umlauts, Border fix.
So i can easily patch together whatever i need
Yes I see the point, however for a regular emulator user who find it "difficult" to even provide a single ROM image to be start the "show" may found interesting for better integration without the need to use any external tool. Surely there are many people here who wouldn't find this a problem AT ALL 
