Two birds in one commit: with the introduction of shared secrets,
there is a practically-infinite amount of local switches that can be
used, by merely editing the shared secret string. As such, support
for old switch groups has been removed.
In addition to this, the multicast address for local switch has been
altered to 239.255.80.86. This ensures a hard compatibility break
with the previous code and old (albeit interim) builds of 86Box would
not attempt to receive packets with shared secrets.
This allows for a “shared secret” to be entered for a network switch,
segmenting traffic so that multiple people could use the feature
simultaneously without accidentally entering into or interfering with
each other's networks.
Takes a string specified in the configuration file (using the
net_%02i_secret key) and hashes it through SHA3-256 to prepend to each
data packet. This hash is used to compare packets on reception and
allow or discard them.
1. See above.
2. Reuse the 4k ROM with proper loading mechanism so that extended ATI modes can be used with the ATI 8514 Ultra 4k ROM (add-on).
3. Disable excess logging.
4. Apparently 8514/A bresenham line must always draw the last pixel unlike the vector lines, fixes missing pixels in some programs e.g.: calculator on Windows 3.x using 8514/A drivers.
Since the default 10.0.2.0/24 (or 10.0.3.0... etc) address can
conflict with a LAN (as it does in my case), this feature now adds the
ability to set custom network prefixes in the configuration file. I
believe this is an “advanced” usage feature (like port forwarding) and
should not be exposed in the GUI, therefore no GUI changes have been
made.
In the `[Network]` section of 86box.cfg, each of the four NICs can be
set to have a custom address like such:
```
net_01_addr = 10.80.88.0
net_02_addr = 10.82.86.0
net_03_addr = 10.84.86.0
net_04_addr = 10.85.86.0
```
The last octet of the address is effectively ignored and always set to
0 again when the configuration file is saved. Only a /24 CIDR
(netmask 255.255.255.0) is supported. IPv4 has three local-scope
ranges: 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0. Finding a network
prefix within these that do not conflict with your real LAN should not
pose a problem.
Previously, we determined the UI font from a predefined set of fonts
each mapped to a language. This works well if the user doesn't change
their Windows UI font, but if one does, they will get the default UI
font associated with their language instead of the one the set.
This commit replaces ProgSettings::getFontName with
ProgSettings::getUIFont, which uses the SystemParametersInfo API to
query the message font from the system, which will allow users to have a
custom font. It will also not interfere with different languages, as the
message font will be appropriately set by default there.
