On May 14, 2010, at 17:06:46, Tom wrote: > Setting the port to inactive is a workaround...buts its only a > workaround...not a fix. To think that its a viable permanent solution > wouldn't be reasonable if this was software we were paying for. That would > never fly with commercial product. I'm no developer, but I'd be willing to > bet good money that there is a software solution to this issue.
Even if there is such a solution, it's probably not in HardwareGrowler, since the problem is probably not in HardwareGrowler. We're doing the same thing we've always been doing, and it works just fine on all hardware except the newest. So, the problem is most likely either in that new hardware or in some new OS component on that new hardware. That would make it Apple's problem to fix. We can't determine exactly what the problem is, and fix it if it's ours, if we can't reproduce the problem. I can't, on my (aging) hardware. So, if it's a bug in HardwareGrowler, it will take someone who has the new hardware to find and fix it. If it's a bug in the OS, it will take someone who has the new hardware to find it and report it to Apple. Until a person who can do either of those emerges, all anyone can provide is workarounds. -- You received this message because you are subscribed to the Google Groups "Growl Discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/growldiscuss?hl=en.
