From 266ff48b684b420ebe670aea1819ee78c514155d Mon Sep 17 00:00:00 2001 From: tomcw Date: Tue, 19 Dec 2017 00:19:26 +0000 Subject: [PATCH] Help doc: add Uthernet WiFi workaround. (Fixes #376) --- help/Table of Contents.hhc | 7 +++++ help/uthernet-wifi-workaround.html | 48 ++++++++++++++++++++++++++++++ help/uthernet.html | 6 ++-- 3 files changed, 58 insertions(+), 3 deletions(-) create mode 100644 help/uthernet-wifi-workaround.html diff --git a/help/Table of Contents.hhc b/help/Table of Contents.hhc index 1c7b3d03..727bd493 100644 --- a/help/Table of Contents.hhc +++ b/help/Table of Contents.hhc @@ -89,7 +89,14 @@
  • + +
  • diff --git a/help/uthernet-wifi-workaround.html b/help/uthernet-wifi-workaround.html new file mode 100644 index 00000000..00ff6d79 --- /dev/null +++ b/help/uthernet-wifi-workaround.html @@ -0,0 +1,48 @@ + + + + WiFi workaround + + + +

    WiFi workaround

    +
    +

    Overview: +

    +

    A (heavyweight) workaround for the WiFi issue.

    + +

    Details: +

    +

    Installing a virtualization solution like the (free) VMware +Workstation Player provides a virtual ethernet card. Then installing +WinPcap inside the virtual machine allows access to the internet via +WiFi from AppleWin.

    + +

    VMware allows you to configure the virtual ethernet card in two ways:

    +
      +
    • Bridged, this means that the virtual Uthernet card becomes visible +with its MAC address in the WiFi net and that an Apple II DHCP client +gets its address from the usual DHCP server (typically a WAN router). +
    • NAT, this means that the virtual Uthernet card is part of a virtual +network with three participants: +
        +
      • A virtual Ethernet card added by VMware to the "outside" (aka host) Windows. +
      • The virtual Ethernet card used by the "inside" (aka guest) Windows. +
      • The virtual Uthernet card. +
      +
      + That virtual network has its own IP address range and has its own DHCP +server (being part of VMware). An Apple II DHCP client gets its +address from that DHCP server. +
    + +

    Another positive aspect of that "emulation inside vitualization" +approach is that the "inside" (aka guest) Windows always has just one +single network interface: that virtual ethernet card mentioned above. +And that interface has always the same name (even when switching +between Bridged and NAT) so one never has to fiddle with network +setting of the emulators using WinPcap.

    + + + diff --git a/help/uthernet.html b/help/uthernet.html index 5076acb5..373245be 100644 --- a/help/uthernet.html +++ b/help/uthernet.html @@ -1,7 +1,7 @@ - Save-State Files + Uthernet network card Acknowledgment:

    Uthernet (TFE) support in Applewin was made possible by implementing the GPL - source written by Spiro Trikaliotis for the Vice emulator - - http://www.viceteam.org/

    + source written by Spiro Trikaliotis for the Vice emulator - + http://vice-emu.sourceforge.net/index.html#developers

    Details:

    To enable Ethernet support in AppleWin you must first download and install