X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
NNTP-Posting-Date: Mon, 20 Jul 2009 23:07:45 -0500
From: "Charles Sandmann" <cwsdpmi AT earthlink DOT net>
Newsgroups: comp.os.msdos.djgpp
References: <86e53db7-9815-42a4-a7bc-bcf5276da9a4 AT p18g2000pra DOT googlegroups DOT com> <h2cevu$jbj$1 AT aioe DOT org> <03ff1567-e4b6-4aaf-b218-d290ebb892d9 AT o9g2000prg DOT googlegroups DOT com> <f081b534-3e0f-4152-b289-f2e9773e1d4a AT k26g2000vbp DOT googlegroups DOT com> <57d4080b-ed46-4df6-887c-ac4ff099938f AT m18g2000vbi DOT googlegroups DOT com> <09d1167e-2bae-4774-ba28-23b332e1ca41 AT d9g2000prh DOT googlegroups DOT com> <dpKdnQ6cP5VeFP_XnZ2dnUVZ_hKdnZ2d AT earthlink DOT com> <491c4a4f-ece6-4528-b992-6d26572cf38c AT l35g2000pra DOT googlegroups DOT com>
Subject: Re: strange problem with disk operations
Date: Mon, 20 Jul 2009 23:07:43 -0500
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5512
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-RFC2646: Format=Flowed; Original
Message-ID: <w56dneSgFu-MovjXnZ2dnUVZ_j6dnZ2d@earthlink.com>
Lines: 21
X-Usenet-Provider: http://www.giganews.com
NNTP-Posting-Host: 64.91.192.48
X-Trace: sv3-gcppk0tNf5jEDqLBy8bAIUDj20b5RJ5aoh0Xqd68gLoTdxDafcxt05rI3sib2X9V/WNPrkWwKYBiten!jyjcIIW2SG+o7LIhy27VvYQJS4SUi6B8VVbcZ/T3EMpEE+jvJTuRw6YfBad7m0sUsqOcRULz8xIa!MUGlRyM5tlUvkTat06CLDM2nTsJ62q8=
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.39
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

>but this way it takes lot of time about 1 hour...
>so without using BIOS how can we program our USB for better
>performance on these
>kind of slow devices...do we have to write our own USB stack for
>this ....if it is then
>how can we go about it.....

You might be able to get better performance by writing a certain
number of bytes at once.  But the only guaranteed way would be
to bypass the BIOS and write directly to the hardware.  This is
very time consuming and error prone - you would need to identify
the type of hardware available, use your own drivers when
possible, then fall back to Int13 when you don't recognize it.

Linux drivers are a good source of information for the low
level details.  But you can easily fall behind trying to support
lots of hardware.  That would suggest some sort of "loadable"
driver method, so you could quickly update your working
program with a small update.