ATTENTION: if the driver compiles but the script just wont work for you.
Here are the bare minimum steps to get your modem to work.

0. log in as root.
1. insmod -f Intel536.o (Intel536.ko for kernel 2.6)
2. you can start "hamregistry &" at this point if you wish.
3. rm /dev/536ep
4. mknod /dev/536ep c 240 1 (note "240" is the default, if it does not
work see what /proc/devices says 536ep's major number is)
5. ln -s /dev/536ep /dev/modem
6. start a comm application like minicom and use the modem.

Error: Could not open /dev/nvidiactl because the permissions
are too restrictive. Please see the FREQUENTLY ASKED QUESTIONS
section of /usr/share/doc/NVIDIA_GLX-1.0/README for steps
to correct.

A: It is likely that a security module for the PAM system may be
changing the permissions on the NVIDIA device files. In most cases
this security system works, but it can get confused. To correct this
problem it is recommended that you disable this security feature.
Different Linux distributions have different files to control this;
please consult with your distributor for the correct method of
disabling this security feature. As an example, if your system has
the file
/etc/security/console.perms
then you should edit the file and remove the line that starts with
"<dri>" (we have also received reports that additional references to
<dri> in console.perms must be removed, but this has not been verified
by NVIDIA). If instead your system has the file
/etc/logindevperms
then you should edit the file and remove the line that lists
/dev/nvidiactl. The above steps will prevent the PAM security system
from modifying the permissions on the NVIDIA device files. Next,
you will need to reset the permissions on the device files back
to their original permissions and owner. You can do that with the
following commands:
chmod 0666 /dev/nvidia* chown root /dev/nvidia*