X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
NNTP-Posting-Date: Sat, 18 Jul 2009 21:49:38 -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>
Subject: Re: strange problem with disk operations
Date: Sat, 18 Jul 2009 21:49:19 -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: <dpKdnQ6cP5VeFP_XnZ2dnUVZ_hKdnZ2d@earthlink.com>
Lines: 21
X-Usenet-Provider: http://www.giganews.com
NNTP-Posting-Host: 64.91.192.48
X-Trace: sv3-64Aj1/+T3lfzgRevUts0+zMp1YET82oupQ6TxTqBLi+RnGvKX+fny4U3LzJ0Yt+kOo1Bvg5Usm5bbm+!aUYQ04LQjU45FQojIUXk1lP070+UeaBCSTe6mzKxlhMGaG+/0r3w3fg0rl0hkjb/cFsnMNjKx330!FK+wC+w6AM75FhMOOK11S0NkO7OMyBc=
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
X-Original-Bytes: 2308
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com


"paravashu" <paravashu 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.  You 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.