From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1DDTlo-0000Lq-6b
	for qemu-devel@nongnu.org; Mon, 21 Mar 2005 15:45:06 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1DDTld-0000Gg-Au
	for qemu-devel@nongnu.org; Mon, 21 Mar 2005 15:44:57 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1DDTld-0000Cg-5y
	for qemu-devel@nongnu.org; Mon, 21 Mar 2005 15:44:53 -0500
Received: from [128.8.10.162] (helo=po0.wam.umd.edu)
	by monty-python.gnu.org with esmtp (Exim 4.34) id 1DDTPw-0007fv-DT
	for qemu-devel@nongnu.org; Mon, 21 Mar 2005 15:22:28 -0500
Received: from jbrown.mylinuxbox.org (jma-box.student.umd.edu [129.2.237.180])
	by po0.wam.umd.edu (8.12.10/8.12.10) with ESMTP id j2LKMRNa021176
	for <qemu-devel@nongnu.org>; Mon, 21 Mar 2005 15:22:27 -0500 (EST)
Date: Mon, 21 Mar 2005 15:22:26 -0500
From: "Jim C. Brown" <jma5@umd.edu>
Subject: Re: [Qemu-devel] MS-DOS Network Client
Message-ID: <20050321202226.GA4182@jbrown.mylinuxbox.org>
References: <000e01c52b21$92fa00a0$6401a8c0@geodb.org>
	<200503212034.19569.Andreas.Krause@web.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200503212034.19569.Andreas.Krause@web.de>
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

On Mon, Mar 21, 2005 at 08:34:19PM +0100, Andreas Krause wrote:
> I finally ran out of ideas.
> 
> All I wanted to do is:
> 
> Host OS: XP
> Guest OS: DOS
> boot some DOS
> setup Network (Lan Manager with TCP/IP transport)
> login to some Windows NT4.0 domain
> mount a share
> run an install.bat located on this share
> 
> I tried almost every combination of the following variables:
> 
> MS-DOS, DR-DOS, FreeDOS
> NE2000/ISA, RTL8029/PCI
> user-net, tap
> different BIOSses
> different qemu-releases (0.6.0, 0.6.1, daily builds)
> different network stacks (MS Network Client, WatTCP)
> DHCP, fixed IP (10.0.2.x in user mode, 192.168.0.x in tap mode)
> 
> Completely no success.
> 

I use Linux as the host OS, and I also have never been able to get MSDOS to
use the network in qemu.

I just tried and same problem as last - hardware seems to be detected and work,
but no packets can be seen.

I use qemu's own BIOS and have had this problem since 0.5.5

> In other OSs than DOS (Knoppix, NT4.0) networking works perfectly in almost 
> every combination without any effort.
> 
> In DOS, I could load both, ne2000.dos and pcind.dos, by using a current bochs 
> BIOS - but not a single packet seems to be transmitted in any configuration. 
> In Linux and NT4.0 networking work's perfectly with the same parameters.
> 
> Any clue? Did anyone run MS-DOS LAN Manager ind qemu successfully? Please, if 
> any of the developers could try this combination and anlyaze somehow deeper 
> than I am able to do? All I can do is try & error all day...
> 
> Thanks in advance
> 
> CU - nak
> 
> 
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
> 

-- 
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.