martouf

DDan: it isn't a 'having or not having' Audigy problem. it's an ALSA driver and system configuration problem. beej: be root and use 'alsactl store' so save a config (levels, too) you are happy with... read all about it here and here.

did you by any chance simply "su" before attempting to install the rpms? if so, try again, but this time "su - root". "id -a" will help explain the difference between the two methods of becoming root, as will "printenv". But given your error message, "id -a" will explain more.

you mean this document is written in a forgotten language? 8) Check the list at the bottom to see if you have one of the affected LG drives. If you need further assistance, let us know.

you want to be sure you're choosing the NDIS 5.1 driver (.inf + .sys) to use with ndiswrapper. Quote: wlan0 warning: using NO encryption ERROR: command 'iwconfig wlan0 key off' returned Error for wireless request "Set Encode" (8B2A) : SET failed on device wlan0 ; Operation not permitted. means the command "iwconfig wlan0 key off" was issued at some point, and the error message is from ndiswrapper. I don't recall any such command in the list of commands from OldSpiceAP's "How To" message. In any case, it's just a warning. (you know you should be using 128bit WEP and MAC filtering, yes?)

are there any other scripts you can check the configuration/associations of to see how to set yours up?

maybe the localization data is incomplete for the locale you've chosen? can you choose another locale to see if that's the problem?

in the document I pointed you to in an earlier message has a "Links and information" section which will point you to the iptables.org project. If a kernel uses the iptables interface, then that's what it uses. The interface is the change, not the kernel. iptables code will do what you want on any system with iptables.

exact string substitution - everything else in the line remains exactly as you found it. substitute the chars "noauto,rw,users" where the chars "defaults" appear. leave the rest as you found it. In Perl string substitution code: s/defaults/noauto,rw,users/; not to overthink this .. just _do_. (yes, the "0 0" remains)

Step 0 (as root): "/sbin/modprobe ndiswrapper" check ndiswrapper module load status with "dmesg | tail -8"

I think res0r9lm hit the nail on the head and drove it all the way home in a single stroke. If you blinked at the moment of impact, you missed the show. Whiskers: edit your fstab file and replace "defaults" with "noauto,rw,users" for each of the usbX disks.

first off (since you didn't say so): are you certain sound is working on your local system? I also see there's someone at linuxquestions.org with the same problem. If they respond with a solution, please be sure to post a pointer to it here. Does the Win2003 server have a sound card? This message indicates a problem in such a case. Another message indicates a problem with the timing of audio. One other message I've just found indicates audio problems when high screen resolutions are used. You might try 800x600 64k color (or less).

you apparently have XFree86 4.3 and the fglrx driver meant for 4.3, and there's already a libGL.so.1.2 installed. I'd try "--force"ing the rpm install. rpm --force -Uhv fglrx-4.3...etc....rpm doesn't the fglrx installation instructions say something about this? or am I mistakenly recalling seeing something about this in the ATI FAQs/Support? enjoy!

motaguense: OldSpiceAP provided a bunch of commands, and not exactly in the right order. try this: 1. configure the wlan radio (pick one of the following) $ iwconfig wlan0 essid any (assumes you're not using any encryption) $ iwconfig wlan0 essid SSIDname mode managed key [1] xxxxxxxxxxxx (if you're using WEP with a hexchar key) 2. confirm your radio has successfully linked to the AP radio $ iwconfig wlan0 (make sure the AP addr isn't all zeroes) 3. obtain an IP addr (pick one of the following) $ pump -i wlan0 & (if your distro has pump) $ dhcpcd wlan0 & (if ...) $ dhclient wlan0 & (DHCP provides an IP addr and DNS config) 4. confirm your interface has an IP addr $ ifconfig wlan0 (make sure the interface is UP and has an IP addr) 5. confirm your system has a default route $ netstat -r (make sure there is a 'default' route to the AP IP addr) 6. confirm your system has a DNS configuration $ cat /etc/resolv.conf 7. enjoy!

all: I'm quite certain CONFIG_NET_RADIO has already been set in the Red Hat 9 and Mandrake 10 kernels. don't worry about that part of the instructions - especially if you find the config var set in your /boot/config-X.Y.Z file. another hint the config var is set is when your distro includes 'wireless-tools'... w-l-c: if you install the 'kernel-sources' package, then you'll have a /usr/src/linux dir.

does the dplay project have a mailing list? you might have better luck there reaching the author or someone who's been waiting to revive the project. meanwhile, take a day to go through the source and take extra time looking at each call to an ipchains function in dplay. As you find each ipchains call, find the corresponding iptables function. With the original dplay source safely tucked away elsewhere, edit the source and add the corresponding iptables function call in a comment (delimited with /* and */ chars). Where variables need new datatypes, add those definitions /* within comment blocks */ if after about a day's worth of this workload research the time-to-complete estimate doesn't look awful, then announce the good news here there and everywhere. you may find this document helpful.

allow 140W for the CRT and another 100W for the system. like I said, don't base your sizing on the wattage of the power supply. many PCs only draw 40W and that's mostly for the spinning disk drives. I think you'll see what size you really need if you figure your system is a 250W load. have a look at the BackUPS LS BP700UC aka "Back-UPS LS 700" and price it via pricegrabber.com .. the BackUPS RS 1500 will run for nearly half an hour.. you're paying for the battery capacity, you know. The BackUPS ES 725 looks like a good choice, too. If you need extra runtime to ensure nobody misses an episode of SpongeBob, then have a look at Smart-UPS XL 750VA.

if you [size:4][tt]cat /etc/mtab[/tt][/color] and your filesystem is jfs|reiser|ext3 then you're using a journalled filesystem. don't just select VA capacity based on how many watts your power supply is.. do you need your system to keep running for a very long time after the power goes, or is it enough to do an orderly shutdown? "orderly" meaning: you have time to finish your thought, save the file, do a quick online weather report check, and announce to your pet/child/spouse "system shutting down in 3 minutes". or orderly meaning: lights go out, and you've got 3 or 4 minutes before the screen goes dark. are you planning to plug your aquarium pump into the UPS? (don't even think about the heaters!) do you have a CRT or LCD monitor? (and don't plug your laser printer into the UPS!) would you be able to borrow someone else's APC SmartUPS long enough to use it to measure the actual AC mains load for your system? or do you have a trueRMS multimeter available? the APC sizing chart is a guide, not a cookbook.

the installation disc should offer a 'safe mode' or 'failsafe mode' bootloader selection very early on in the install process. select it. you probably need the 'noapic apm=off acpi=off' kernel parameters.

hmm. interesting. (words you never want to hear from a Doctor) just humor me and run through your setup again, but this time: [size:4][tt]ifconfig eth0 192.168.1.12 netmask 255.255.0.0[/tt][/color] (oh, and you can skip the 'metric' when you add the default route, but you might want to add '-net' before 'default') [ see 'route --help --inet' ] if you get the same arp and ping results, then: are you sure you haven't plugged your cable into a 'straight-through' port instead of a crossover ('X') port? are you sure you haven't grabbed a crossover cable when you meant to grab a straight-through cable?

ulikeit: yeah, your instructions would be great if jarves wanted to share from Linux to WinXP. But what jarves was asking about is sharing from WinXP to Linux. :x

BTW, if you're using a journalled file system, a sudden crash halt isn't really so terrible. The hold-up time of your power supply is enough to get the journal entries written in most cases (something less than fully saturated disk I/O). Still, it is nice to finish your Slashdot post by the glow of your screen while the rest of the neighborhood is in complete darkness. 8)

I'm a APC customer - ever since the first UPS I bought. If you choose one of their SmartUPS products, you'll have your choice of USB, ethernet or serial link to the UPS. Also, you may either use the PowerChute for Linux software from APC, or use apcupsd. Read this article - start at the "Support" section and read to the end.

no, I'm pretty sure I'm not missing the point. The 'free'-ness of your ESP isn't at issue here. What is at issue is in this brave new SPF and 'Sender ID' world, how is it this ESP intends to stay alive without offering its users a complete mail service? I'm very sorry, but at the moment, I'm quite reluctant to offer much help in this area unless I feel assured the knowledge I might share won't be used to no good purpose. I'll gladly explain my concerns, if you don't already apprehend the basis of my reluctance.

GNU/Linux is both ingénue and mature. It is mature in process isolation and system security (SELinux being the ultimate). Mature, as in: a mature technological base and design. It is mature in international standards compliance. It is immature in that it persists in expanding the universe of hardware with which it works, despite the lack of effort on a manufacturer's part to provide support for their products. It is immature in that it is a platform for software innovation. You may choose to do business with vendors who stand behind their products and labor. If you do so, then you'll live in your familiar "everything works" world. A wise person once said: Unix not user friendly? It's very user friendly! It's just picky about who its friends are.. Linux is an inheritor of a design philosophy and tradition which pre-dates Microsoft. (interesting wordplay if the hypen is removed.. hmm.) If you do not feel up to the task of learning a different way of doing things, then stay in your comfort zone. Not everyone has the talent to work with nitromethane fueled racing machines. Heck, some folks are dangerous operating a bicycle.

we apologize for the inconvenience. your answer is 42. sorry. the question? 8) you may want to seriously consider adding a 2.2 kernel and only those modules you really need to run the game in multiplayer mode. an alternative could be to offer yourself up to the author of dplay to help the porting effort. You're clearly quite motivated, and some projects die only for lack of motivated participants. how much time and effort are you willing to give the "dplay porting project"?