From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] r6677 broke access to physical FDD on Win32
Date: Fri, 20 Mar 2009 20:56:14 -0500 [thread overview]
Message-ID: <49C4493E.9050701@codemonkey.ws> (raw)
In-Reply-To: <68676e00903201620n1ac29c01g9e3d7172f9bc69a4@mail.gmail.com>
Luca Tettamanti wrote:
> On Sat, Mar 21, 2009 at 12:02 AM, Anthony Liguori <anthony@codemonkey.ws> wrote:
>
>> Is "a:" a valid filename in Windows?
>>
>
> No, ":" is not a valid char for a file name.
>
>
>> Is there a way in Windows to detect
>> that a given file is actually a physical device?
>>
>
> : is used for delimiting the mount point; actually the internals are a
> bit more complicated (see [1]), stuff like A: or C: are reserved
> special names, the "real" device names are \\.\A: or \\.\C: (where
> \\.\ is the namespace used for devices).
>
Looks like the code is doing the right thing. Someone running windows
is going to have to debug this because a: should be transformed to
\\.\a: as far as I can read the code.
Regards,
Anthony Liguori
> Luca
> http://msdn.microsoft.com/en-us/library/aa365247.aspx#path_names_and_namespaces
>
>
>
next prev parent reply other threads:[~2009-03-21 1:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-18 21:53 [Qemu-devel] r6677 broke access to physical FDD on Win32 Robert Riebisch
2009-03-20 22:01 ` Anthony Liguori
2009-03-20 22:23 ` Robert Riebisch
2009-03-20 23:02 ` Anthony Liguori
2009-03-20 23:20 ` Luca Tettamanti
2009-03-21 1:56 ` Anthony Liguori [this message]
2009-03-22 20:49 ` Robert Riebisch
2009-03-23 2:20 ` Anthony Liguori
2009-03-23 12:31 ` Luca Tettamanti
2009-03-24 8:20 ` Japheth
2009-03-30 19:59 ` Robert Riebisch
2009-03-21 22:07 ` Luca Tettamanti
2009-04-07 1:46 ` Anthony Liguori
2009-04-07 11:45 ` Luca Tettamanti
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=49C4493E.9050701@codemonkey.ws \
--to=anthony@codemonkey.ws \
--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).