From: Will Styles <stashelp@yahoo.com>
To: Justin Zygmont <jzygmont@solarflow.dyndns.org>
Cc: linux-msdos@vger.kernel.org
Subject: Re: some problems (1.1.5 and 1.1.4)
Date: Tue, 1 Jul 2003 03:19:41 -0700 (PDT) [thread overview]
Message-ID: <20030701101941.48416.qmail@web20204.mail.yahoo.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0306301336450.22740-100000@solarflow.dyndns.org>
hello.
--- Justin Zygmont <jzygmont@solarflow.dyndns.org> wrote:
> i'll try. however when I managed to try again with 1.1.4, the problem was
> there, just not quite as bad.
well the patchset number is really critical here...
> So I don't know if it'll make much
> difference if it was like that all along.
>
i'm not concerned with persistent problems.
i'm more concerned about this: if the situation gets *drastically* worse from
1.1.4.9 to 1.1.4.10, i know what the problem is. so i am most interested in
these 2 revisions.
btw, out of curiousity, are you running this on pentium 2?
-wst
>
> On Mon, 30 Jun 2003, Will Styles wrote:
>
> > On Thu, 26 Jun 2003 07:11 am, Justin Zygmont wrote:
> > > ok, i'm going to try with ALSA, some of the games
> > > that run improperly are:
> > > jill2,3, kiloblaster1,2,3, and most of my other dos
> > > games. What usually happens is each time there is
> > > a sound effect, the game gets sluggish pausing for
> > > about 1/2 second, and the musical soundtrack
> > > doesn't play for any game. I remember now with
> > > 1.1.4, this problem existed, but just not
> > > quite as badly.
> > >
> > hmm, i think i know what the problem is but i'd rather
> > not say what it is yet. could you please try the
> > following versions:
> >
> > 1.1.4.9 (or <=)
> > 1.1.4.10
> > 1.1.4.13 (or >=)
> >
> > if you don't have time, please just try 1.1.4.9.
> > i don't think stas will be happy though.... :-)
> >
>
__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com
next prev parent reply other threads:[~2003-07-01 10:19 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-30 11:51 some problems (1.1.5 and 1.1.4) Will Styles
2003-06-30 17:39 ` Justin Zygmont
2003-07-01 10:19 ` Will Styles [this message]
2003-07-01 11:16 ` Bart Oldeman
2003-07-01 22:49 ` Justin Zygmont
2003-07-04 3:32 ` Justin Zygmont
2003-07-04 18:10 ` (unknown) Darryl Perry
2003-07-04 18:21 ` your mail Ged Haywood
2003-07-05 14:48 ` Jim Hartley
2003-07-05 14:53 ` Ged Haywood
[not found] ` <1057435822.2023.49.camel@tamriel.terranforge.com>
2003-07-06 4:06 ` Jim Hartley
2003-07-06 11:20 ` Jochen Reinwand
2003-07-06 11:56 ` Ged Haywood
2003-07-06 16:26 ` Jochen Reinwand
2003-07-06 19:03 ` Eemeli Kantola
2003-07-06 23:10 ` Jochen Reinwand
-- strict thread matches above, loose matches on Subject: below --
2003-07-01 11:26 some problems (1.1.5 and 1.1.4) Will Styles
2003-07-01 11:06 Bart Oldeman
2003-06-25 17:39 Stas Sergeev
2003-06-25 21:11 ` Justin Zygmont
2003-07-04 5:26 ` Justin Zygmont
2003-06-25 17:30 Stas Sergeev
2003-06-26 1:27 ` Ryan Underwood
2003-06-15 12:48 Stas Sergeev
2003-06-24 23:21 ` Ryan Underwood
2003-06-25 0:50 ` Justin Zygmont
2003-06-14 10:09 Jan Willem Stumpel
2003-06-14 10:36 ` Bart Oldeman
2003-06-14 23:58 ` Ryan Underwood
2003-06-14 17:17 ` Justin Zygmont
2003-06-14 19:42 ` Jan Willem Stumpel
2003-06-14 23:57 ` Ryan Underwood
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=20030701101941.48416.qmail@web20204.mail.yahoo.com \
--to=stashelp@yahoo.com \
--cc=jzygmont@solarflow.dyndns.org \
--cc=linux-msdos@vger.kernel.org \
/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