Mail Archives: djgpp/1997/11/22/10:00:18
From: | Ed Leiby <eiby AT frontiernet DOT net>
|
Newsgroups: | comp.os.msdos.djgpp
|
Subject: | Intermittent Run-Time of DJGPP App under Win95
|
Date: | 22 Nov 1997 14:09:07 GMT
|
Organization: | Frontier Internet Rochester N.Y. (716)-777-SURF
|
Lines: | 35
|
Message-ID: | <3476E722.74E0@frontiernet.net>
|
Reply-To: | eiby AT frontiernet DOT net
|
NNTP-Posting-Host: | srv-13-35.roc.ny.frontiernet.net
|
Mime-Version: | 1.0
|
To: | djgpp AT delorie DOT com
|
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp
|
I am a new user of DJGPP, and so far have been incredibly impressed by
the package, the environment and the price!
However, I have recently been hacking around w/ a DSP simulation
compiled under gcc ( rev 2.7.2.1 ) using rhide ( rev 1.3 ) inside a
win95 dos box on a Pentium Pro 200Mhz machine. I had previously been
using Borland 5.01 set for a win95 console app, but had not been using
any win32 specific anything. Well, the app compiled like a dream under
gcc and ran right off, even reproducing results obtained under Borland.
The problem is that it seems to run at two different speeds: As fast as
Borland, and 2-3 times slower than Borland. I have tried using
cwsdpmi,cwsdpr0 (rev 0.90+) and win95 DPMI server. However, to date I
have not been able to correlate any action on my part or setup of the PC
to the different execution speeds. I thought for a while that it had to
do with invoking rhide right before I ran the app or maybe the win95 dos
box DPMI size setting, but results did not track anything conclusively.
When I say 2-3 times slower I am talking about the difference between 10
minutes and 20-30 minutes, so startup times should be swamped out. The
app is doing minimal disk/screen i/o so I don't think I can blame
real/protected switches.
.
Of course there is always the possibility that the problem lies within
my app, but it seems to be very well behaved ( consistent results, no
gpf's etc.)
Any ideas ????
Thanks in advance,
Ed Leiby
- Raw text -