> It does(just tried it), because getpwent (or the similar used function, I
> didn't look at the sources) can't get the crypted passwd string from
> /etc/spwd.db, so it gets an '*' instead, from /etc/pwd.db. And the passwd
> you enters, after crypt(), never match '*'. So you get the 'BAD SU' message,
> just as if you entered the wrong passwd.

it looks as if this may be the problem, but unfortunatley, I'm not 
familiar with how to use setuid, anybody have a really brief instruction 
on what to do at the command prompt?