From owner-freebsd-stable Wed Mar 22 16:43:16 2000 Delivered-To: freebsd-stable@freebsd.org Received: from cx344940-a.meta1.la.home.com (cx344940-a.meta1.la.home.com [24.6.21.74]) by hub.freebsd.org (Postfix) with ESMTP id 4253037B84E for ; Wed, 22 Mar 2000 16:43:11 -0800 (PST) (envelope-from conrads@cx344940-a.meta1.la.home.com) Received: (from conrads@localhost) by cx344940-a.meta1.la.home.com (8.9.3/8.9.3) id SAA77822 for stable@freebsd.org; Wed, 22 Mar 2000 18:43:07 -0600 (CST) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Wed, 22 Mar 2000 18:43:06 -0600 (CST) Organization: @Home Network From: Conrad Sabatier To: stable@freebsd.org Subject: What does "Voxware still supported in 4.0" mean exactly? Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've seen several people state that Voxware is still "supported" under 4.0, and I really have to stop and scratch my head and ask, is this some new definition of the word "supported" I was not previously aware of? Trying to use Voxware under 4.0 is, as I learned the hard and painful way, anything but easy (I've already gone back to 3.4 because of it). In fact, it's damned near impossible with certain PnP hardware, the AWE 64 being one notable example. Without the good ol' pnp commands at boottime, the AWE's wavetable is dead in the water, and if you're unfortunate enough to also have PnP motherboard audio that CANNOT BE DISABLED due to the removal of the pnp commands (my BIOS provides no facility for disabling it either), you wind up with a real mess on your hands. Not to mention that, if you compile Voxware into your kernel, at boot time you're greeted with some rather unfriendly messages chiding you for doing so, and strongly suggesting (coercing?) that you use the new pcm drivers instead. It's rather disturbing to me to think that, as FreeBSD progresses along through this and that version, I'll have no choice but to be left in the dust, or sacrifice certain functionality that I've come to know and love, or (God forbid) migrate to another platform altogether. One really must question what kind of "progress" it is that breaks things that formerly worked (and worked very well at that), and offers no new alternatives. -- Conrad Sabatier http://members.home.net/conrads/ ICQ# 1147270 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message