Hi all. I have just found a script on the web that gets my winmodem to autoload. What I did, was copy the script into /etc/init.d. Now, if i run "/etc/init.d/slmodemd start" from a terminal, then it works. Then what I did was linked it to rc5.d for startup at boot and rc6.d for stopping at shutdown. Now if I run "/etc/rc5.d/S98slmodemd start" then once again it starts without any problems. If I dont add the "start" argument then nothing happens. So I try it when rebooting and nothing shows up on the screen as the machine boots, and of course when I try wvdial it tells me, cant find the modem device,( cause it wasnt run at bootup.) So is there anything, anyone can think of that is stopping the script from being run when the machine boots and shuts down?

Though that I had better add, that this script has come from a latter version of the modem driver and then been adapted for debian. Have just been reading the policy manual and its saying something about when the program is configured/compiled that there configure scripts should use the rc.d update program instead of manually putting links in or something to that eefect. So do I need to run update rc.d and if I do, then is there something else I need to do before that.

9.3.3.1 Managing the links

The program update-rc.d is provided for package maintainers to arrange for the proper creation and removal of /etc/rcn.d symbolic links, or their functional equivalent if another method is being used. This may be used by maintainers in their packages' postinst and postrm scripts.

You must not include any /etc/rcn.d symbolic links in the actual archive or manually create or remove the symbolic links in maintainer scripts; you must use the update-rc.d program instead. (The former will fail if an alternative method of maintaining runlevel information is being used.) You must not include the /etc/rcn.d directories themselves in the archive either. (Only the sysvinit package may do so.)

Surely there is a way to get this to work manually?

A little more reading and suprise surprise, its all there in the documentation. Just had to run rcd-update and all problems fixed.