is that visiting somebody?
i have an (two) extra for you.
i took the heavy load to prepare all (ALL! i own roundabout 240) for the use in MAME though they will be displayed properly as available in the MAME UI.
the problem is stll the rotten memory mapping needed for the inty (and other old junk).
instead to depend on a config file (which would exceed it if you guess how many machines mame emulates now) or to load the whole image and to depend on a own config table (presets for the common mappings) it's now done like before in MESS and the cartridge images must be split into the proper sections according to the memory mapping to load the section in the proper memory bank.
for bin's (the image must be in .bin .int .itv format for this) up to 16Kb they can be simply zipped and the zip file must be named exactly as required by MAME (hashtable intv.xml in directory "hash", this will also tell you how the images have to be split if at all), while the content of the zip file, the binary, can be named however MAME identifies binaries by their unique checksum and not by their name. we humans need names and a certain naming convention is obvious for us we can't read differ checksums so well.
unlike before the files must nest in a given directory structure to be shown as available. if you like to store your cartridge images in the default roms directory you have to extract the zip's "intv" and "intvecs" (these are the two intv systems seperated by MAME, intvecs has also an own hash table) to the directories "intv" and "intvecs".
unfortunately if you place the rom packs inside the system zip's they won't be recognized as available
create a directory in it named i.e. "carts", it doesn't matters what name this directory has and you could even place the rom packs directly into "intv" or "intvecs", but it's certainly neater if you create a subdirectory. if everything is proper they will apear now as available in the MAME UI.
alternatively you can create a directory in "MAME" home dir named "whatever" and add the path of "whatever" to the mame.ini and the respective machines ini's. i.e.
rompath roms;whatever;whatever\tard
path's are seperated with a semicolon.
the folder for the software must be named equal to the system it should run in, e.g. "intv", likewise the zip or folder for the system roms is named.
SAY IT LOUD: THAT IS A COMLICATED TARD TO RUN A GAME IN MAME
and worst of all it's not even reliable, games which certainly run on any real intellivision, soccer - all of them, fail in mame. and who knows which game will even fail - you have to play them and not only watch if the title screen loads to be sure it runs as expected and pardon me a standard intellivision game like soccer will tell me a lot if it didn't runs.
but i guess it was never the goal MESS/MAME is an usable machines archive, a sort of museum and not a specialised emulator to run a game in best possible manner.
still i'm sad about the joining MESS was more this museum type and MAME concentrated on arcade machines which was done very well in this project, due to the joining, even if MAME was always a derivate of MESS it has getting worse in my opinion.
still you can load a rom (.rom in this case) with the file requester, but that's far from being comfortable, but a safe method to run a intellivision game in MAME.
however, like i said i took the heavy load to prepare all games for MAME, now i can't share all even if i would like to because i'm aware not everybody likes to fumble around with a hex editor and feels joy doing it.
but i can share some, everything which is legal (and a little bit more).
what i can't share are of course the system roms and the official released intellivision games, for this buy please a "Lives!" or "Rocks" CD ROM - even if it takes years until you do so (like in my own case, but i can still say "hey that's now my fourth intellivision console, i'm allowed to").
but still including the IntyBASIC "tard" (which are worth to have a look at) you receive roundabout 100 games with this pack which will be recognized and run in MAME.
box arts and overlays (sometimes very artificial) for almost all 240 games i listed in intv.xml and intvecs.xml, means your inty will appear very neat and cool in MAME.
includes a readme which explains the system how MAME recognizes cartridges and together with the roms and hash table examples enough how to split the roms for MAME.
NOTE:
all standard (excluding homebrews or IntyBASIC) images up to 16Kb doesn't have to be split, if their checksum is recognized they will appear as available if the pack (.zip) is named proper and rests in the proper directory.
as a little extra it includes the complete "RCA Studio II" (except system images, but they are free i can upload them) including the homebrews which was made for its 35th anniversary. complete with "box art".
"only for scientific interest"
MAME intv.zip
i know i should have made screenshots (can't do that on the mac - or maybe, i will see), it's really neat together with the boxes and overlays.
the only thing is....
MAME fails often, it doesn't runs "Soccer", it fails at "D.K. Arcade" it fails at "Ms. Pac-Man", it fails, it fails, it fails i don't know where else.
it was a brainfucker to get some games running in mame and i really had to manually hack some roms to make them work, since MAME "stupidly" only accepts "legal" memory addresses like "5000" or "4800" (imagic) or "A000" but no specific addresses like "C100" (words apropos).
i managed it to get "Quest" running until the game should start, the title and game setup loads now when the scene should change it halts. it's a complete shit if a game uses RAM especially if it's in a non standard way and bankswitching like it's needed for "quest" isn't proper supportet in MAME (how can i preload? and so on).
because this is so frustrating (i have to peep in that "launch box" once ) i put a second set together, it's an jzInzv pack containing "weeds" jzintv launcher which is quite neat if you have everything like box art, overlays and manuals ready.
the launcher is a little obsolate but still works well with the recent jzintv releases, in case you are not satisfied with the three presets for the screen res. (which i assume) you still can edit the "launcher.ini" and manually enter any desired resolution, i.e. -z1024x768.
again i put that all together with some free roms which work with the handed out "miniexec.bin", box art, manuals (.txt) and overlays for the complete set named after "goodintv" or kept the conventions for newer games (which are most of the handed out games).
with this pack you can start rightaway to play an emulated inty and won't need anything else as to set it up for the directory you placed it in.
of course many games won't run with the miniexec (even some IntyBASIC fail), but i won't hand out the system roms, else i could put all together and never mind about, but neither it makes sense to include games which won't run with the miniexec even if a few pearls are between them, like the latest release of "Deep Zone".
jzIntv includes all the developing tools from "sdk-1600", which means for you it's easy as 1,2,3 to convert .bin's in the safe to read .rom format.
to get all the flags for jzIntv displayed add --help to the command line, unlike stated you can redirect the output to a file like: jzintv --help >usage.txt
it's cool if all is ready (and i do would like to share every tidbit)
only of entertaining interest:
jzIntv Launcher Pack.zip
however if you dislike the "launcher" you can still use the set of box fronts and overlays of either pack i linked (as .png for MAME named to its conventions and as .jpg for "jzintv launcher"). you still will find this or that interesting game in either pack (while due to the splitting many games for MAME intv won't have a use outside of MAME).