Qchem

If you look at the search results, you'll find those numbers are more than a little misleading. Backdoor.Win32.Biomac.c doesn't actually affect the Mac, but the search result includes it. Try searching for OS X, you'll get three windows viruses and a single Mac one (which doesn't even self propogate).

I use this box as a scientific workstation, mainly running very heavy quantum chemistry calculations and in the meantime I'm doing some coding (shell scripting, C and Fortran) for related utilities. Whilst I'm at work I also use it for general internet duties and preparing journal articles. The box is a dual EM64T Xeon 3.2 GHz with 4 GB RAM and over 500 GB of hdd space.

There's a topic on compiling with gcc in our FAQ section.

I guess we need to start looking at things like firewall, routing table, resolv.conf, IPv6

What does iwconfig say about your card? Do the details look right?

Is it possible to turn the hardware detection service off in mcc - I'm not at a mandriva box right now but I thought there was something like this.

tar cvzf - * | split -b 512k nameoftar

Try looking at the k flag, I remember using that on old-school unix. EDIT - it appears this does something different in GNU tar - sorry! You'll probably be better off piping it through split.

Yes, otherwise you may get more conflicts. You might want to check the pinned thread on ndiswrapper at the top of this forum.

I would assume that Mandriva has tried to autodetect the card and has added it as sl0 - causing you conflicts. If you have a look at lsmod (lists all the loaded kernel modules) you may be able to see two wireless card entries (or paste them here at get us to look :D ).

This is a bit but the plural of virus is viruses, not virii.

your iwconfig output is telling you that the interface is called ra0

It probably just means that was the version the person used at the time. I would expect it to work with all later versions.

OK, I've found that chipset on the ndiswrapper database, someone has got it working with ndiswrapper 0.9 and the RT2500 drivers for XP (the .inf and .sys) from ftp://ftp.a-link.com/wl54h/WL54driver2.2.6.0.zip Someone else with the same chipset mentions that the win2k drivers from the same zip are more stable.

Could you do an lspci -n and paste the line here that contains 05:00.0

I would probably blame lisa first, try turning the individual things on and off to see what triggers it.

Why alas? At least the Linux world doesn't have the travesty that exists in Mac OS X - several well known AV manufacturers sell products to protect the Mac which also has no virus problem, and many people buy them.

Not sure regarding the KDE part (I'm a gnome abuser) but for the cups uri you have to use exactly the name that the printer is shared as, you can check that from a linux box with: smbclient -U username -L dd-win2k replacing username with your windows username (it'll ask for that users windows password).

If you've decided that you need to use ndiswrapper to get your wireless networking card going, there's a couple of places you should check if you have problems: Carefully read the tips and tricks thread on this board (perhaps a little out of date, but still good advice). If you're having trouble make sure you get the latest version of ndiswrapper from their website to replace the mandrive supplied version. You'll need the kernel-source rpm that matches your running kernel (check this kernel version with uname -a) - use Easy-urpmi to help install this if need be. Check the list of wireless cards to see if anyone has had success with your card. If you've read all these documents and are still having problems - then please start a new topic and people will try their best to help.

I'm not sure ClamAV or similar would actually help if there was a sudden outbreak of a Linux virus anyway - surely you'd need some kind of definition file first. I don't forward mail attachments and I don't run an email server, windows users can look after there own machines from my perspective.

When you're adding the printer cups throws up a dialog box for a password - that should be the root account on the linux box. For the windows domain password you need to change the printer URI to something like: smb://username:pass@HOME/dd-win2k/HP where you replace username and pass with your windows username and password and I'm assuming that HOME is your workgroup, dd-win2k is the host machine and HP is the name of the printer share. HTH

If the machine is at a remote site ssh would seriously be my first option for this.

The number you need appears in the first column of that output - it's not in the ndiswrapper wiki list. Try manually loading the win drivers from the CD, the worst that can happen is the kernel crashes and you'll need to reboot - hardly the end of the world.

Try doing lspci -vv which should give extra info on your card (you're looking for serial numbers etc), search through the wiki again with these codes.

You can check if cups is running in the services section of mcc. IIRC (not at a mandriva box ATM) you can also do service cupsd status from CLI to check if it's running.