OK, I'm back with more test results...
It looks like the problem is related to cnet.device (or my network card using it). I have to admit that I didn't try to ping the A1200 with cnet.device. After everything successfully worked with my WLAN card, I just checked if uIP also came up correctly with cnet.device -which was the case- and assumed the rest would work also. I didn't try any further because I had no network cable where my A1200 sits. No QA as it should be, I have to admit - shame on me...
Today, I network cabled the A1200 with cnet.device, fired up uIP, tried to ping it and voila: it has the same problem as the A600, it just keeps responding to ff-ff-ff-ff-ff-ff. :roll:
I can't check prism2.device on the A600, because it requires at least OS 3.0... Don't think I haven't tried it nevertheless... I usually don't trust READMEs :-D
But no luck, SetPrism2Defaults crashes the A600.
Trev wrote:
Does uIP continue to receive data after the "sending..." message, or does it hang? Does it respond to CTRL+C? If it responds to CTRL+C, then SANA-II I/O is hung. If it doesn't repond to CTRL+C, then uIP (or the system itself, if nothing responds) is hung.
It keeps receiving & responding, you can close it with CTRL+C, fire it up again, no problem. It just keeps replying to ff-ff-ff-ff-ff-ff... I can dump the traffic with tcpdump or something when I have time. Maybe some other user can check uIP with cnet.device in the meantime to verify if the problem is related to my card.