From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1GPPoF-0000bV-W5
	for qemu-devel@nongnu.org; Mon, 18 Sep 2006 16:33:44 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1GPPoE-0000ab-HA
	for qemu-devel@nongnu.org; Mon, 18 Sep 2006 16:33:43 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1GPPoE-0000aY-9H
	for qemu-devel@nongnu.org; Mon, 18 Sep 2006 16:33:42 -0400
Received: from [64.233.162.202] (helo=nz-out-0102.google.com)
	by monty-python.gnu.org with esmtp (Exim 4.52) id 1GPPr8-0007od-Hi
	for qemu-devel@nongnu.org; Mon, 18 Sep 2006 16:36:42 -0400
Received: by nz-out-0102.google.com with SMTP id n29so1722765nzf
	for <qemu-devel@nongnu.org>; Mon, 18 Sep 2006 13:33:39 -0700 (PDT)
Message-ID: <7fac565a0609181333v1245e714u827e2e8b4bdce696@mail.gmail.com>
Date: Mon, 18 Sep 2006 22:33:38 +0200
From: "Alexey Eremenko" <al4321@gmail.com>
Subject: Re: [Qemu-devel] Poor Qemu documentation for Windows host
In-Reply-To: <7fac565a0609181217m47ce48bbw94eb4944b67e6c19@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <7fac565a0609172005w355fd473p4ecc3183390bc212@mail.gmail.com>
	<1158549358.4008.1.camel@vaio>
	<7fac565a0609181217m47ce48bbw94eb4944b67e6c19@mail.gmail.com>
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

> But unfortunately, it comes separately from Qemu package, inside
> "OpenVPN" software.
>
> So my recommendation is to:
> 1) "get" the TAP driver out of "OpenVPN" package, and
> 2) put it into Qemu setup, and
> 3) update user docs with that.
>
> I dunno if I will succeed in getting the driver out of OpenVPN, it
> really depends how far it integrates into Windows... especially if it
> integrates very deeply into registry this will be mission-impossible.

OK, I have succeeded in retrieving the driver from OpenVPN package,
because it didn't have registry entries at all.

Now, I have built a separate setup package, that can be used
independedly from OpenVPN.

Here is the "setup-virtual-ethernet-tap.exe":
http://download.yousendit.com/E73E60032A75C3DF

NOTE: This download location is temporarily and will expire soon, by
then I hope to move else, to normal HTTP server.

Next step, I can build an integrated Qemu setup package for Windows,
that has TAP-Win32 drivers in it. (that way I will follow the standard
rule of Windows to depend *just* on the OS itself)
But I will only do this setup, if you agree to list it on Qemu homesite.

As for docs, I should note that this driver requires Win NT 5.0 and up
(2000 and XP), so if users wanna run Qemu on Win98, they won't have
this functionality.