Sorry,no go.vtpup,
Thanks for trying the mwave dotpet. I did not understand that it takes so much customizing to get it to work. But I can explain why you don't see anything happening.
With Puppy 4.1 the module loading technique changed so that simply using modprobe does not activate the firmware that does some of the magic. But there is a way to overcome that. Use the BootManager to force loading of mwaved with all its parameters. That will trigger the modem init script, which should handle the rest -- I think. (If it doesn't, we could make it so.)
Richard
EDIT: I read this last post first, then noticed your previous ones. So I may be addressing the wrong problem.
But first, I think we should go back to your other thread so that we don't hijack this one, which is for offering fixes. Could you move this dialog back there and reduce the size of your above posts? I think everyone would appreciate that.
Anyway, once you reboot after installing the dotpet, mwaved should get loaded automatically. We need to get that far first, maybe without your mods to the BIOS, considering that you have upgraded it. But I yield to your knowledge on that.
A-hah! The driver is not loading because of another change in module loading for 4.1. But I have made a dotpet to correct that, earlier in this thread, here:
http://www.murga-linux.com/puppy/viewto ... 797#266797
Richard
There was an error expanding package modem%2Bcardbus_fix-4.1.3.tar.gz.
Either the file is corrupted, or has not expanded into its own directory with
name of modem%2Bcardbus_fix-4.1.3/ (which is how most packages expand).
You will have to go into /root/.packages/ directory and manually clean it up.
This script will now exit...