Hi,

On Mon, Sep 14, 2015 at 7:54 AM, soko.tica <soko.t...@gmail.com> wrote:
>
> I have installed freedos on qemu (both x86_64 and i386), but cannot start
> the networking.

Which version(s)? 0.13.50? 2.4.0?

> Since this is installed on Qemu, which is an emulator, I don't know where to
> find the appropriate driver, or how to configure it properly. I could not
> find the answer in the chapter Packet driver installation
>
> Please advise. Where to find the appropriate driver for a virtual device?

First of all, if you're using mTCP, it uses its own mtcp.cfg and env.
var., so it's not directly compatible with Watt-32 apps. So be sure
you know what you're trying to run (e.g. Ftp, Wget, Links2). Upstream
only recommends latest mTCP version for latest bugfixes:

http://www.brutman.com/mTCP/

Secondly, depending on how old your QEMU build is, you'll have to use
a different network card for each. QEMU hasn't always had decent
support for Windows, so you'll still find some old builds out there
(e.g. ReactOS bundles 0.13). However, these days we do have some
current builds (e.g. 2.4.0) that work okay, see
http://qemu.weilnetz.de . (In other words, older 0.13 seems to need
"ne2k_isa", but newer can work with "pcnet".)

I don't recommend Realtek 8139 for various reasons. But, for
completeness, here's their latest build (AFAIK):

http://www.realtek.com/Downloads/downloadsView.aspx?Langid=1&PNid=14&PFid=6&Level=5&Conn=4&DownTypeID=3&GetDown=false#3

P.S. Once again, this could've been more directly solved with my
MetaDOS 0.2 (which does all of this), but I still am undecided whether
to just upload it "as is" or keep improving it. If you want me to
email you the floppy .img (600 kb .ZIP) and sources (3 MB .7z), that
would be the simplest solution to your problem (no fiddling required).

------------------------------------------------------------------------------
_______________________________________________
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Reply via email to