martouf

MediaCoder 0.5.1build2720 http://mediacoder.sourceforge.net

those things are found in the /proc filesystem and are adjusted using echo NewValue > parameter_name .. however, you should have very little need to make any adjustments at all. you should find all of the defaults are perfectly suitable for most every terrestrial configuration.

copy the directory with the .inf files -and- all subdirectories (if any) or associated files in the same directory to any convenient place in the linux filesystem. Then run the install utility again.

that is easy to fix: do not use ports 6800 to 6999 reconfigure your client appropriately. i use verizon and have never experienced a "slow down" for any reason other than link congestion (or service interruption).

i think you are simply saturating your upload/return bandwidth. you should set a reasonable upload rate cap in your p2p app or use NetLimiter to enforce one. "reasonable" == 80% of the maximum tested upload rate. if you do not know your max upload rate, then you may use a link test site like http://broadbandreports.com/stest or http://testmy.net/u_load.php

you'd have to run "lspci -v" to be able to tell which device has that PCI address. it may or may not be related to your situation. just because you allocated a disk in vmware, it doesn't mean Knoppix will know what to do with it. (unless of course you've also created a filesystem on the 'disk') i don't recall that Knoppix automounts disks even when they contain filesystems it knows how to mount.

what you can expect depends on your proclivities and interests. what real-world experiences have you collected for yourself in the field of InfoSys ? consider offering yourself as an intern (unpaid) to the 'dream company' you may already have in mind.

family emergency?

audacity.sourceforge.net has nearly reached the level of sophistication equivalent to CoolEdit Pro

read Samba-3 by Example ( <-- click me! ) i'm sure you'll find a section addressing a situation similar to yours. in other words: yes, you can do what you are describing with Samba.

http://www.samag.com/documents/sam0414e/ http://www.wlug.org.nz/ActiveDirectorySamba and http://us3.samba.org/samba/docs/man/Samba-HOWTO-Collection/ServerType.html#id2540088 Hope that helps!

you should need no driver other than the generic usbstorage module you already have. have you run 'fdisk /dev/sda' to have a look at the device's partition table ? (don't make any changes!) .. in case it's like a zip drive which puts the vfat filesystem on /dev/sda4 ?

hmm.. i think the /dev/midi interface is a holdover from the days of the OSS sound driver. perhaps you haven't enabled the oss compatibility part of ALSA?

if you're setting up to use TKIP then you're not using WEP, you're using WPA and you're going to need to get and build the wpa_supplicant ..

tested with tux racer (accel required) with simplymepis.

experiment with acpi and apm kernel parameters.

yes. even accelerated using the xorg radeon driver. no need to use the ati drivers if you don't want to.. tested with ubuntu, knoppix, suse livecd, and simplymepis. it's important to manually select your screen resolution from the boot menu. i have a latitude d600.

maybe (as root) try: $ touch > /.forcefsck $ shutdown -r now ?? (that's from memory - it -is- .forcefsck isn't it?) isn't there also an lsattr command so you can check for any extended permissions in /usr/share/wallpapers ?

it looks like you've got everything installed properly, but for some reason the ndiswrapper kernel module is throwing errors. and perhaps just plain crapping out on you. is there a newer ndiswrapper available for your distro or are you ready to build a newer ndiswrapper kernel module yourself? ps: what you posted isn't all that long.. you were right to put it all in. I couldn't have been able to figure out what is going on otherwise.

what does [size:4][tt],, /usr/sbin/ndiswrapper -l ,,[/tt][/color] show? what does [size:4][tt],, grep ndis /var/log/messages ,,[/tt][/color] show?

First, umount the CD and turn off the 'install VM Tools' mode for that VM. I expect you'll need to restart Fedora (run "shutdown -h now" as root) in the VM. Reboot your system (the host OS not the guest). Next, restart the Fedora VM. Once restarted, turn the install VM Tools mode back on and mount the 'CD drive' (it's virtual). If the rpm on the 'CD' gives you any trouble, then just use the src tar instead. don't forget to umount and turn the VM Tools mode back off. good luck!

the letter you need to use (in ITU phonetics) is "Lima" Alpha == A Bravo == B Charlie == C Delta == D Echo == E . . and so on.. . . Lima == L nolapic ::= Nancy Oscar Lima Alpha Papa India Charlie ok?

huh.. really? here's what I've got on my test system: [size:4][tt]$ dmesg | grep ndis ndiswrapper version 0.6+CVS loaded[/tt][/color] (second command run as root, many distros don't allow regular users to read /var/log/messages) [size:4][tt]# grep ndis /var/log/messages Apr 21 14:58:33 testsys kernel: ndiswrapper version 0.6+CVS loaded[/tt][/color] Ok, no accelerated display driver. confirmed. good - it had the potential to be the source of the problem. unlikely, but potential. the swap config looks OK. Nothing looks bad there. the one big difference between your system and mine is the really large number of LOC interrupts. Mine is 0. Even after millions and millions of timer interrupts. it's the local interrupt counter in the APIC. your APIC must be on. hmmm.. have you (or would you) try booting with "noapic" ? booting with both "noapic" and "nolapic" ?

oh, about the lack of display driver hooked to an interrupt: it means you're not using an accelerated driver.

you ought to find the ndiswrapper version information in the output of [size:4][tt]dmesg[/tt][/color]. try: [size:4][tt]dmesg | grep ndis[/tt][/color] for memory config, there's [size:4][tt]free[/tt][/color] and [size:4][tt]procinfo[/tt][/color]. procinfo gives a nicely concise memory and interrupt report. free gives just the memory report. ( raw data may be obtained using: [size:4][tt]cat /proc/interrupts cat /proc/meminfo[/tt][/color] )