Hi.

The result would only partly be the same. One of the goals of this project (has anyone actually started programming it?) is to get IP-only functionality (esp. FTP/HTTP) to a MkI. The MkI does not have any Ethernet port, so the only way to get IP to it is via PPP (wether over serial or USB is only a matter of speed) or through the emulation of a USB-to-Ethernet adapter on the empeg's side.
In other words, the goal is to get Windows (and possibly even Linux) to think that the empeg is actually a USB-to-Ethernet adapter that is in turn connected to the ethernet port of an empeg (even though the MkI doesn't actually have an Ethernet port).
A more complex, but even better solution would be to have the empeg emulate a USB hub which is connected to an empeg (for "classic" emptool/emplode USB connections) as well as to a USB-to-Ethernet adapter (for pseudo-Ethernet connections to the empeg). Using ASCII graphics to illustrate it, it would basically look like this:

                             +----------------------+       

                             | +-----+  +---------+ |       

                             | |     |--| USB2Net |*|

 +----+                      | | USB |  +---------+ |

 | PC |--- USB connection ---+-| HUB |              |       

 +----+                      | |     |  +---------+ |       

                             | |     |  | empeg   | |       

                             | |     |--| USB     |*|       

                             | +-----+  +---------+ |       

                             +----------------------+       

                                                            

where the big right box depicts the empeg, the boxes        

inside it only show "virtual" devices the PC sees. The

"*" characters stand for Linux device nodes (one serial

device, one ethernet device).

Yes, that would be my ideal solution for this project, but it is well beyond my abilities to implement that.

cu,
sven