Ben, I think the point I'm trying to make is that even if Apple is causing the problem, others have managed to work around it.
In any kind of computing project, sometimes you have to "fix" things that you aren't responsible for. I write web pages. Half my day is spent working around bugs created by browser manufacturers. Even though those bugs aren't my problem, my pages have to accomodate them. Why? Because the end user browsing my pages doesn't care whether it's my fault or Netscape's fault that the page doesn't work right. It becomes my fault, and if I don't fix it, my users will find another site that does. --- Ben Reser <[EMAIL PROTECTED]> wrote: > No it's not a lame copout. The DHCP clients work > for everyone *BUT* > you (I'd say Airport users but I don't recall anyone > else having this > issue). These are the same daemons that x86 uses. > So if > there's a problem with them it would have been > discovered by now. So > that tells me Apple isn't following the standard in > some way. __________________________________________________ Do You Yahoo!? Yahoo! Tax Center - online filing with TurboTax http://taxes.yahoo.com/
