From: Ronald <look@reply.to>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [WIN32] tftp issue
Date: Sat, 09 Oct 2004 21:55:28 +0200 [thread overview]
Message-ID: <pan.2004.10.09.19.55.22.273939@reply.to> (raw)
In-Reply-To: 1097351147.15742.23.camel@kubu.opensource.se
Le Sat, 09 Oct 2004 21:45:47 +0200, Magnus Damm a écrit :
> On Sat, 2004-10-09 at 01:07, Ronald wrote:
>> Hi all,
>
> Hi!
>
>> tonight I decided to give a try to tftp transfert between a windows 98
>> host and linux guest.
>> First thing I had to deal with was how to pass the tftp_prefix, I
>> figured out that omiting the drive letter and his preceding slash is the
>> right way (ie exporting C:\temp to guest consist in passing -tftp /temp
>> to qemu). The issue I had next was with file transfert, I can get some
>> files completely and only the first bytes for some others. I don't know
>> already on what it depends (size, file type ...?), but I thought I
>> should let you know that.
>
> Thank you for the report.
>
> Please specify the version of QEMU and the name and version of the TFTP
> client used by the guest. Or even better, provide a link to a precompiled
> win32 snapshot of QEMU that behaves like you describe together with a
> pointer to a bootable image if available on the net.
>
Qemu version is yesterday cvs, tftp is netkit-tftp-0.17 from slackware 8.
Binary for windows is avaible at
ftp://ftp.freeoszoo.org/qemu/win32/daily/QemuInstall-20041008.exe.
Image is not online, that's a minimal slackware 8 install from cdrom.
> Thanks!
>
> / magnus
next prev parent reply other threads:[~2004-10-09 20:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-08 23:07 [Qemu-devel] [WIN32] tftp issue Ronald
2004-10-09 19:45 ` Magnus Damm
2004-10-09 19:55 ` Ronald [this message]
2004-10-09 21:13 ` [Qemu-devel] " Ronald
2004-10-09 22:07 ` Magnus Damm
2004-10-09 22:26 ` Johannes Schindelin
2004-10-09 22:38 ` [Qemu-devel] " Ronald
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=pan.2004.10.09.19.55.22.273939@reply.to \
--to=look@reply.to \
--cc=daimon55@free.fr \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).