From: Pete Zaitcev <zaitcev@redhat.com>
To: Martin Maurer <martinmaurer@gmx.at>
Cc: stern@rowland.harvard.edu, martin.maurer@email.de, akpm@osdl.org,
linux-kernel@vger.kernel.org,
linux-usb-devel@lists.sourceforge.net, zaitcev@redhat.com
Subject: Re: Fw: Re: Elitegroup K7S5A + usb_storage problem
Date: Sun, 7 Aug 2005 14:00:38 -0700 [thread overview]
Message-ID: <20050807140038.29e3d4e3.zaitcev@redhat.com> (raw)
In-Reply-To: <200508072247.43916.martinmaurer@gmx.at>
On Sun, 7 Aug 2005 22:47:40 +0200, Martin Maurer <martinmaurer@gmx.at> wrote:
> > Just out of curiosity, if you plug the player into a Windows system
> > without installing any special drivers first, will Windows be able to read
> > and write files okay? If it can, a USB packet trace may give Pete a clue
> > as to where to look.
> as far as i recall i didnt install any special drivers for my win 2k and win
> xp systems. (i got this mp3 player quite a while now...)
> How would I do such an packet trace ?
I have never run Snoopy on Windows myself and I did not want to subject
you to it. Let's try my delay patch first. If that fails, I guess we
have to get instructions from someone who knows how to run Snoopy.
Maybe Windows issues some cache synchronization command when it
commits FAT. Then the packet trace should show it.
-- Pete
next prev parent reply other threads:[~2005-08-07 21:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-07 15:32 martin.maurer
2005-08-07 18:08 ` Alan Stern
2005-08-07 20:47 ` Martin Maurer
2005-08-07 21:00 ` Pete Zaitcev [this message]
[not found] <20050805151820.3f8f9e85.akpm@osdl.org>
[not found] ` <Pine.LNX.4.44L0.0508061137180.1168-100000@netrider.rowland.org>
2005-08-06 20:02 ` Pete Zaitcev
2005-08-07 0:22 ` Martin Maurer
2005-08-07 1:06 ` Pete Zaitcev
2005-08-07 15:14 ` Alan Stern
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=20050807140038.29e3d4e3.zaitcev@redhat.com \
--to=zaitcev@redhat.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=martin.maurer@email.de \
--cc=martinmaurer@gmx.at \
--cc=stern@rowland.harvard.edu \
/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
all inboxes | Powered by JetHome®