Path: news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: candycanearter07 <candycanearter07@candycanearter07.nomail.afraid>
Newsgroups: comp.sys.ibm.pc.games.action
Subject: Re: AMD weighs in on HD versus 4K
Date: Sat, 7 Jun 2025 16:00:12 -0000 (UTC)
Organization: the-candyden-of-code
Lines: 46
Message-ID: <slrn1048o9d.3kmfh.candycanearter07@candydeb.host.invalid>
References: <19nb3k5q4pho824jtoqf3kbrsned4n7db6@4ax.com>
 <1017fgv$3b9h2$2@dont-email.me>
 <h1te3ktmvsv3ks2v4rfp92vqpver9dlqci@4ax.com>
 <jtug3kttldgbgaed3f8f8an3sm8ilfubjr@4ax.com> <101ajb2$2g3v$2@dont-email.me>
 <gcgj3k5k47etj99qvrenppgrt9h11gnijk@4ax.com>
 <ptsj3kditgsrhmphalfrqckqh5teu675v5@4ax.com>
 <6a4n3kh00c561t89cal2fe8s5f8ha21n6p@4ax.com>
 <q02u3k1poiokn9gbniakuapfga72t4nahe@4ax.com>
 <s0014k1ptkn5129jffvu79i01l3062btv7@4ax.com>
Injection-Date: Sat, 07 Jun 2025 18:00:12 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="4fad18b6c2c47606a131893d05d25cde";
	logging-data="3326911"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/7tWtOIteNOXcqpfWrR/TfctHqMMR2UiMM8haSc4C4vA=="
User-Agent: slrn/1.0.3 (Linux)
Cancel-Lock: sha1:mg13QcAQPqWlAX4MbcJLRCOvZvE=
X-Face: b{dPmN&%4|lEo,wUO\"KLEOu5N_br(N2Yuc5/qcR5i>9-!^e\.Tw9?/m0}/~:UOM:Zf]%
 b+ V4R8q|QiU/R8\|G\WpC`-s?=)\fbtNc&=/a3a)r7xbRI]Vl)r<%PTriJ3pGpl_/B6!8pe\btzx
 `~R! r3.0#lHRE+^Gro0[cjsban'vZ#j7,?I/tHk{s=TFJ:H?~=]`O*~3ZX`qik`b:.gVIc-[$t/e
 ZrQsWJ >|l^I_[pbsIqwoz.WGA]<D

Zaghadka <zaghadka@hotmail.com> wrote at 17:24 this Wednesday (GMT):
> On Tue, 03 Jun 2025 10:49:45 -0400, in comp.sys.ibm.pc.games.action,
> Spalls Hurgenson wrote: 
>
>>On Sat, 31 May 2025 19:38:39 -0400, Spalls Hurgenson
>><spallshurgenson@gmail.com> wrote:
>>
>>
>>>I'm not sure I'd recommend a Creative card, though. I suspect my
>>>current issue is with the card itself, and not some Windows thing. I
>>>had a similar problem with another Soundblaster; it just stopped
>>>outputting from one of its ports (fortunately, my motherboard on that
>>>computer supported 5.1 so it wasn't really an issue). I think there
>>>are some real issues with the quality of the components on Creative's
>>>offerings.
>>
>>Update:
>>
>>Fortunately, it turns out to be 'just some Windows thing', in that it
>>was software that caused the problem and not a hardware failure. It
>>turns out there are /at least/ three places you have to enable 5.1
>>speakers to get it to work in a game:
>>
>>     1) in the Soundblaster driver software app
>>     2) in the Windows "sound settings" applet
>>     3) in the game itself.
>>
>>I'd configured the latter two, but had forgotten the first even
>>existed, and for some reason it had toggled itself to 2.1 mode for
>>some reason. 
>>
>>Computers. Go figure.
>>
> These days, it's almost always a software problem, simply due to the
> odds. There are just so goddamn many bugs. QC is a lost art, as is clean
> code.
>
> I'm surprised when I diagnose a hardware error in this era. It happens,
> but I always exhaust all software options before I start running hardware
> diagnostics, and rarely get to the point where I have to run it.*


"Software advancements have done wonders to offset how much Hardware has
improved"
-- 
user <candycane> is generated from /dev/urandom