Qchem

I can echo that recommendation. Since I found it I don't use anything else.

Is it feasible to use a static IP address? I'd at least try setting for a short while to rule out some potential problems.

I'd try making sure it worked via CLI first.

Do you think your wireless access point/router should be giving you an IP address, or do you usually have to set one statically? Make sure the network isn't filtering out your packets by MAC address. Try turning firewalls off to see if that makes any difference. Sorry if some of that seems a bit obvious - just trying to brainstorm.

If that doesn't help, try checking the contents of /etc/resolv.conf both when the connection is working and when it isn't. You can do that with cat /etc/resolv.conf

My first linux was Redhat 7.1 I was using IRIX and TRU64 UNIX on workstations before that though, that's where I caught the *NIX bug.

When the connection is working, check the contents of /etc/resolv.conf. Then when the connection breaks check the contents again to see if they have changed. If they are changing we'll be able to lock the file to stop it.

Welcome to the boards!! It's hard to be 100% sure, but I'd wager that it's the driver ndiswrapper is loading that is causing the lock up. Have you used the ndiswrapper database to search for your card (via the "number" you get from lspci), to check for working drivers?

Welcome to the board. Unfortunately I don't really know what to suggest as your comments are a little vague - what kind of parameters did it ask for? Network address details?

As it's not your machine, you might not want to - but I'd be tempted to simply remove the hard drive and install it into your new machine - extract the data you want, then put it back.

I don't really know what you mean by it being a problem with linux, the problem could be caused by the Mandriva kernel doing something different to what the instructions were written for I suppose. TBH, it might be worth looking at getting a combined ADSL modem/router that connects via ethernet.

They very well could be. It would be best to choose a single method and stick to it.

I've never really seen that before, I suppose you could try using dhclient instead.

Why is it called br2684.txt? I thought it was a binary file? It's probably easier to rename it to br2684 rather than change everything in the scripts.

That's a shame as it's a fairly good app under windows. IMO it's not as good as freehand or illustrator but it should suffice for most SVG work.

I downloaded the source the other day, but it needed an rc of a lib so I didn't get round to installing it. They're hoping to work with the inkscape people - here's hoping for good results.

Yes.

If this is from your arch install the fonts may not be located there - I'm currently on a SuSE box and the fonts are in /usr/X11R6/lib/X11/fonts/ - I can't remember where Mandriva hold them.

You could try this: cp xorg.conf xorg.conf.broken.bak cp xorg.conf.old xorg.conf startx to see if the old config works. If not it's probably best to: cp xorg.conf.broken.bak xorg.conf

You may be having problems because of the [1] at the end of the filename. [ and ] are special characters in the linux shell (command line) and it tends to do all kinds of weird things. It's probably worth renaming the file to firmware-extractor. Secondly: You've named the file firmware-extractor[1].txt (are you sure it's a txt? It should be a binary file not that it really matters) and then tried to open it as firmware-extractor[1] It might be better to do this in two steps, assuming you've changed the name to firmware-extractor: chmod +x firmware-extractor ./firmware-extractor ZZZL_3.012

OK, it seems that eth2 is your wireless card, it might be best to try and configure it manually rather than using mcc. To configure it manually: iwconfig eth2 mode Managed iwconfig eth2 key restricted "YOUR_KEY" iwconfig eth2 essid "YOUR_ESSID" dhcpcd eth2 where "YOUR_KEY" and "YOUR_ESSID" should be replaced with the correct values. If there's any problems then please post back. If it now works, we can make these changes permenant by adjusting the startup script. The file you should be looking at is: /etc/sysconfig/network-scripts/ifcfg-eth2 or something very similar. Open this file as root in a text editor (try kwrite if you don't have any other preference), and ensure it looks something like the following: DEVICE=eth2 BOOTPROTO=dhcp ONBOOT=yes ESSID="YOUR_ESSID" MODE=Managed KEY="YOUR_KEY" Where obviously YOUR_ESSID and YOUR_KEY are set to the correct values. Note, this key refers to the WEP key, not WPA. It may be an idea to turn the encryption off for a short while whilst you're testing. Hope this helps.

eth0 is probably your (ethernet) network card, if it's not plugged into anything then this is nothing to worry about.

Could you provide the output of /sbin/ifconfig and /sbin/iwconfig ??

So, as a recap - you have the firmware files (not for the silver version) in the speedtouch directory, still zipped. Is that correct? What happens when you run the speedtouchconf script? To find what type of modem you have, I'd probably try this first: grep -i alcatel /proc/bus/usb/devices You may be able to find some information on the modem with /usr/sbin/lsusb -v When you can't execute a command, can you try and paste the error for us - that way we can probably figure out what's going wrong.

Which directory did you put the firmware file in? It should be in the same dir as your speedtouchconf files. The post you mentions says that the firmware file is a .zip (which I don't think you need to unpack). It's the speedtouchconf that comes as a tar.gz You should probably check that the mandriva speedtouch rpm isn't installed, with: rpm -qa | grep -i speedtouch