So neosdconv dissapeared

[sasja-san]

The Github repository on the page for neosdconv was deleted. I happened to have the code saved, so here's the repo (it's under MIT License):

neosdconv.tar.gz

I asked the clanker (Claude) to create me a single file python equivalent:

neosdconv.py

Here are its comments:

I’ve ported the whole project to one Python file, neosdconv.py. It needs only the standard library and Python 3.8 or newer. I haven’t run it against real ROM files.

It keeps the same command-line flags, including -# for the NGH number and -d to dump a .neo header. The output layout is the same too: a 4096-byte header followed by the P, S, M, V and C data.

I kept the file-name matching, the interleaving of the C ROMs and the swapping of the two megabytes in a 2 MiB P ROM as they were. I left the debug print calls in.

I did make two changes:

NGH in -d output: the original TypeScript printed each byte as hex without zero-padding, so a value like 0x1005 would have shown as 105. Python now prints it as a proper hex number.
No async waits: the wait(1) calls only existed to avoid “browser is busy” warnings, so I dropped them.
One quirk is still there on purpose. For the v1/v2 style of V ROM, the original matching pattern needs a digit after v1 and v2, so a file named like x-v1.v1 is not picked up by those checks. Games with a single V ROM still work because they use the plain v pattern. If you have a v1/v2 game, such as League Bowling, tell me and I’ll change the matching.

I don't know about licenses and LLM-generated code, but if it's within my rights to licence it, it's under MIT.

@dciabrin this has a place in tools/?

[sasja-san]

lol nevermind

I just found romtool.py and saw that it did just this. I hadn't looked at it before because it wasn't in any of the makefiles of the example I'm working from 🙃