delorie.com/archives/browse.cgi | search |
X-Authentication-Warning: | delorie.com: mail set sender to djgpp-bounces using -f |
From: | paravashu <paravashu AT gmail DOT com> |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: strange problem with disk operations |
Date: | Mon, 20 Jul 2009 05:40:43 -0700 (PDT) |
Organization: | http://groups.google.com |
Lines: | 28 |
Message-ID: | <491c4a4f-ece6-4528-b992-6d26572cf38c@l35g2000pra.googlegroups.com> |
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> | |
NNTP-Posting-Host: | 210.118.108.254 |
Mime-Version: | 1.0 |
X-Trace: | posting.google.com 1248093644 1010 127.0.0.1 (20 Jul 2009 12:40:44 GMT) |
X-Complaints-To: | groups-abuse AT google DOT com |
NNTP-Posting-Date: | Mon, 20 Jul 2009 12:40:44 +0000 (UTC) |
Complaints-To: | groups-abuse AT google DOT com |
Injection-Info: | l35g2000pra.googlegroups.com; posting-host=210.118.108.254; |
posting-account=nZZF7goAAAABsnWP2j-BAdZkVZvGqieS | |
User-Agent: | G2/1.0 |
X-HTTP-UserAgent: | Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; |
Trident/4.0; .NET CLR 2.0.50727),gzip(gfe),gzip(gfe) | |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
Reply-To: | djgpp AT delorie DOT com |
On Jul 19, 7:49=A0am, "Charles Sandmann" <cwsd DOT DOT DOT AT earthlink DOT net> wrote: > "paravashu" <parava DOT DOT DOT AT gmail DOT com> wrote in message > > news:09d1167e-2bae-4774-ba28-23b332e1ca41 AT d9g2000prh DOT googlegroups DOT com... > > >I have tried with the bigstack cswdpmi.exe provided in the above link > >http://clio.rice.edu/djgpp/bigstack.zip > >when i dont combine this exe with my utility, the application works > >fine without any hanging problem. > > When CWSDSTUB.EXE is combined with the executable, it will > be used as the DPMI provider and not call CWSPMI.EXE, so > this seems to have confirmed the problem. > > You might try the stacksize version, which will print out the amount > of stack required. =A0You can then allocate a real mode stack in the > 1MB region and specify this in the DPMI interrupt call to avoid > the problem. > > So this seems to confirm the BIOS is poorly written for USB > disk interrupts on this one machine. Yep thanks a lot for the info... 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.....
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |