IMPORTANT UPDATE!!After you have stuck your now properly imaged SD card into your Pi, plug the Pi into an available ethernet port on your router and power the Pi up.

Give it a minute to understand that it is alive before you try to log into it through Windows.
It takes a few minutes for it to boot up and for the rest of your network to recognize it is there.
If you open an Explorer window on the PC you should be able to type this in and actually get somewhere.

It will take time even if it is working properly so be patient.
If your PC can't find it then it will say so and you have a network issue to address that I probably can't help you with.
This is the folder into which you want to copy your taboo game info elements.
Don't ask, don't tell.
For the rest of our network enabled adjustments the rest is VERY important.
The following bit is the code that someone FAR smarter than me came up with to add somewhere in the Pi- and it actually works.
If the person who wrote this is reading here please message me and I'll send you something mea culpa style for listing your work unacknowledged!
Do the copy and paste thing with the following mouse additions in the manner I set forth in the following if you want to not agonize over this for (at least) weeks like I did.
IMPORTANT UPDATE!!The file that needs to be amended to make your controls all work properly is /home/pi/.advance/advmame.rc and it is VERY important to note that it is a HIDDEN FILE!
There is another advmame.rc file (the one I have been trying to adjust throughout this torture) but it will do NOTHING to get things to work properly.
You can adjust the VMMenu files that are located within the same /advancemame directory that the rom folder resides in above but ONLY changing the advmame.rc configuration file noted in the /home/pi/.advance folder will get your controls to work!!
Here is the final thing I came up with that makes this all work.
device_mouse raw
device_raw_mousedev[0] /dev/input/mouse0
device_raw_mousedev[1] /dev/input/mouse1
device_raw_mousedev[2] /dev/input/mouse2
device_raw_mousedev[3] /dev/input/mouse3
device_raw_mousetype[0] ps2
device_raw_mousetype[1] ps2
device_raw_mousetype[2] ps2
device_raw_mousetype[3] ps2
input_map[p1_trackballx] mouse[0,x] mouse[1,x] mouse[2,x] mouse[3,x]
input_map[p1_trackbally] mouse[0,y] mouse[1,y] mouse[2,y] mouse[3,y]
input_map[p1_dialx] mouse[0,x] mouse[1,x] mouse[2,x] mouse[3,x]
input_map[p1_dialy] mouse[0,y] mouse[1,y] mouse[2,y] mouse[3,y]
input_map[p1_paddlex] mouse[0,x] mouse[1,x] mouse[2,x] mouse[3,x]
input_map[p1_paddley] mouse[0,y] mouse[1,y] mouse[2,y] mouse[3,y]
Easy, NOW, ain't it?!
The last time I did this I actually needed to make all these adjustments driectly within the PI GUI as I think the file permissions for accessing a hidden (protected?) file on the Pi through Windows wasn't happening for me.
YMMV
Dig in and get that addition/alteration made to the
/home/pi/.advance/advmame.rc file however you can pull it off.
I also removed the other P1 references to dial, trackball, and paddle that were in that config file as I was adding the new lines in.
As far as things to alter in your code via PC/network connection, that is it.
Save your changes.
Done.
Things to note as you continue:
*I have had ZERO success using a wireless keyboard/mouse combination device in configuring the Pi once in the cabinet.
Do yourself a favor here and just use a plain old corded keyboard for controller configuration.
*I have NO idea if AdvanceMame fails to launch without having an audio device connected (the way
MAME has failed for me in the past) so do yourself a favor here also and just have something plugged into the Pi that will make some noise. The Pi4 has a 3.5mm stereo jack but from the Pi5 on it appears not.
It also helps because you can hear Chad's menu wake up when it starts and hear keystroke and spinner/joystick indications as you navigate and exit too.
*You MUST have a display (in addition to the vector CRT you have hopefully already acquired or built and is connected to your USB-DVG) plugged into HDMI port 0 on the Pi while finishing up or you simply can't do it.
Unlike any other
MAME build I/you may have attempted, NOTHING will show up on the CRT except what the vectormenu or game are doing.
When it comes to getting AdvanceMame to register your control panel inputs (via the 'Tab' key while in a game- or to adjust things later on) the secondary display is imperative.
Ok-
Now that you have your Pi all set up the next thing is to take care of your controls.
You can be cheap if you want to and try to use something else (and a properly configured Arduino board will suffice here of course- but I am not that smart yet PL1 !) however the following detail is written in reference to an I-PAC and a SpinTrak because I can attest that the following just simply works.
Andy at Ultimarc offers top notch customer service and quickly replied when I asked about what my build was gagging on so that I could fix it.
I've been buying stuff from him for years and he always helps.
I have also bought really nice parts from Randy at groovygamegear (whose support is equal to Andy's) and I am sure that he has a board and Twist that will do exactly the same, although the configuration process will probably differ slightly.
If I can get the time to buy stuff from Randy also I'll test that out too and add notes here if anyone would like.
So, before you fire up the machine with the Pi connected and have fits like I did, let's get your control interface set up properly.
One of the cool things about the I-PAC is that there is are a number of utilities to get your board to act the way you need it to.
If you head to Andy's website you will see a few downloads available for I-PAC boards.
https://www.ultimarc.com/control-interfaces/i-pacs/i-pac2/Andy's app and directions are very straightforward so I won't bore you with reiterating.
After a lot of patience from Andy with his replies and trying EVERYthing here it turns out that the "Keyboard Only" firmware that his boards ship with is the version to use.
There is a header on the I-PAC to plug both the SpinTrak AND trackball (I have a regular old Happ here) into at the SAME time- and they both work.
This is absolutley awesome from my seat since it allows me to play Cosmic Chasm, Tempest, Tac/Scan with this panel and also Quantum with a panel swap.
Love this.
For the sake of being thorough, this particular cabinet was built solely as a vertical game unit.
X Y monitors don't care about orientation really as they are deflecting from center so you can always be smarter than me and just build a wider cabinet with a 25" tube horizontally oriented and be able to play EVERYthing in one cabinet reasonably well as long as you get per-game configuration proper and have the right controls.
I need to revisit the vertical vector game possibilities here.