I have a modem with an Intel 536ep chipset: this is a winmodem, but a driver exists and I have used it without any trouble before. However, while installing it on my new distribution (Mandrake 9.0, kernel 2.4.19), I ran into trouble. The installation script compiles the driver binary ok, and installs the required files ok. But it exits with the message "Could not remove /dev/536ep: operation not permitted". I have looked at the script and figured out that it creates a new device, /dev/536ep, on boot and symlinks it to /dev/modem. But everytime it boots, it is supposed to delete /dev/536ep and create it all over again, and since this isn't working, neither is my modem. On my old installation, the script worked all right. But even though I compiled and installed this as root, it won't work now. Even if I log in as root and try to remove /dev/536ep manually, I get the same error message. Does anyone have any ideas?

try
ls -l /dev/536ep
to find out who owns the device
then
su
su - owner
rm -r /dev/536ep
at least it will be removed then and might be created correctly on boot
hope that helps - maybe someone has a better idea
cheers, jens

the ls -l command will show u the group of the device, maybe u don't belong to that group?

Thanks, I finally figured out that I had to delete the devices in the right order. Dumb mistake, I know, but using the long listing format helped me figure it out. I'll try fiddling around with the settings again and see if I can get it to work.

Hey, I've got the samer modem and problem what you had here!
The owner and Group is root and even as the root it won't allow me to delete the 536ep files in /dev/
With windows the only time it doesn't allow you to delete is if it's being used by another program.
How did you solve this problem
Cheers
Dave

Well, despite the problems here It did start to work like someone else has commented after saying the modem is not responding.
Great now lets not be stupid and reinstall XP

Only joking

ok, well after someone else said when you get the modem to ring out it comes at first "modem not responding" then try it again and it works fine.

I think the file that "links" the 536ep file is hamregistry that uses the file.