Yast Forgets Network Configuration

Hi, I've recently upgraded from Suse 10.0 to 10.3. I have a Ralink wireless network card which worked fine with an rt2500 driver under Suse 10.0.

The driver that came with 10.3 didn't work, so I removed it, built and installed a different rt2500 kernel module, configured the card through Yast - and it worked. But whenever I restart Yast and go to network devices, the card is shown as not configured. This doesn't seem to matter until I reboot. Then I have to reconfigure the card again - IP address, network mask, ESSID, WEP key, the whole works. Rather tedious.

If I look in /etc/sysconfig/network I have some ifcfg-* files. None of these gets updated after I've configured my network card through Yast. I have ifcfg-ra0 from the setup with Suse 10.0, but it clearly isn't being written to or read by the 10.3 version of Yast.

The setup in Yast insists on calling the interface ra0. Even so, I've tried copying ifcfg-ra0 to ifcfg-wlan0 and ifcfg-wlan-ra0, but this doesn't work either - restart Yast and the card is still showing up as not configured. When I do configure it through Yast, it tells me it's writing the config file - but where? And why can't it find it next time?

I suspect this may be a Yast issue rather than a network card one. If anyone has any suggestions I'd be grateful.