@ChrisXenon: The thread historically had a lot of non-technical users getting thrown at it, because it's the home of the Fonts and the ScreenSavers hack.
To avoid said users shooting themselves in the foot, by design, the USBNetwork docs were done the *nix way: i.e., RTFM, which happens to be a README_FIRST text file *inside* the package.
As you've discovered in said doc, since I'm not a Windows user, and Windows (used to, I'm told since Windows 8 or 8.1 things are better) ships *without* the relevant drivers, well, there was no 'official' documentation.
This was fixed by third-party forum posts, and wiki edits.
Fast-forward to the K4. For technical reasons, K4 packages belong with old, legacy packages, which means that mega-thread.
You'll notice that I had since moved to single dedicated threads, because, yes, that thread is unwieldy as hell (and the spoiler tags serve the specific purpose of making it slightly less so; think of them as collapsible subsections, it's a cheap hierarchy). But, again, historical reasons, can't touch it.
But we do needed a slightly better doc, especially because the K4 JB is so peculiar. The wiki looked good, and had the most succinct & clear instructions, so I went with that, and simply linked to it inside the README, because why the hell c/p stuff that risks getting outdated and that I can't actually verify myself anyway
.
TL;DR: The wiki has the relevant information. The state of the USBNet doc is by design, a prospective USBNet user is *expected* to have basic *nix admin knowledge.
As for Windows, can't write doc for stuff I don't use
. OS X info only appeared in there once I got my hands on an OS X system, for instance.