ksherlock

I might be biased but it looks good to me. The vmnet_common stuff should probably be in a namespace. bootp/dhcp translation shouldn't be that hard and would be handy.

Interesting. VMNET_BRIDGED_MODE didn't exist when I originally wrote the helper. I'll try to play with it this weekend.

For bridged mode, we need to specify the interface that is bridged, eg: ``` xpc_dictionary_set_uint64(dict, vmnet_operation_mode_key, VMNET_BRIDGED_MODE); xpc_dictionary_set_string(dict, vmnet_shared_interface_name_key, "en1"); ``` `vmnet_start_interface` return NULL if there's an error, which it...

That is a big list. The UI is driven by config files ([example](https://github.com/ksherlock/ample/blob/master/Ample/Resources/macse.plist)) which are pre-generated from the `mame -listxml` output because `-listxml` is often inconsistent and lies about some...

Do any of them work? Most are flagged as `MACHINE_NOT_WORKING` or `MACHINE_IS_SKELETON`.

[Here](https://github.com/ksherlock/ample/releases/tag/mainframe-1) is a version of Ample Lite with most of the machines above. You'll need to bring your own MAME.

Thanks for the testing and feedback. Ample tries to keep the previous selection for slots of the same name when the machine changes. For Apple II and Mac I think...

The embedded/mame64 and embedded/mame-data.tgz are from this fork/branch of mame - https://github.com/ksherlock/mame/tree/ample-261-u2 . make -f make-ample mame-data.tgz will create it (or make -f make-ample release for both).

I've rewritten it to move all the registers into discrete fields and split the sockets into a separate device to simplify their registers and tcp/udp support. The w5100s support was...

Pathname conversion also handles mpw-style environmental variable substitution so you could do something like: `mpw -DPWD="$PWD" mwc68k -v {PWD}:test.c`