> I.E the SIMPLE STATUS is a great example, of all the people that us SB stuff > how many do you actually hook direct to a PC? I personally have MAYBE 5--10% > that I do that way so this software would possible work but to me its a > bandaid I hook most my installs to a router which this software is useless > because the radio is before the router so how is a customer PC supposed to > see the radio other then giving the radio a public IP which would be a > waste.
Ok, showing my ignorance here, but could someone point me to a radio that will allow someone to access it from the LAN port of a router where the radio is plugged into the WAN port of the router? Proxim??? Orinoco??? Canopy??? I guess I'm missing something here. Every radio that I can think of off the top of my head requires you to connect directly to the ether port to configure/monitor it (over the ether port side anyway). Many radios can be monitors over the wireless side of things. > Its little things like that if you pass if before a few people to critique > first then you don't spin your wheels developing something that maybe 5% of > us will ever use. You could have them spend more of their time developing a > more useful feature like having this feature (watchdog reboot) built INTO > the radio which would have been more useful?? The above comment doesn't make sense at all. You appear to be indicating that sB doesn't do Beta testing. (at least that's what I read into your comment. sB does have an extensive Beta program in place. > Believe me I bet I have just as much R & D time as they do working with > engineers and beta testing stuff trying to find the bugs that was part of my > job for 7 + years. So as you can see I have an eye for these things and it > seems a few other people do as well and we have said we would donate our > time to help but it seems like they just go ahead and do what they want and > maybe put a feature or two in that is actually good. Even with the experience you mention, it's not just having "an eye" the makes for a good quality assurance inspector. I guess you have already asked sB to be a Beta tester and have not heard back or were not selected. Just because you were not selected, you should take offense to that nor indicate that they are not doing field beta. Your non-selection could be totally based on something as simple as by the time you request beta status, they already had 2000 other people before you ask for the same thing. > I would like to see this stuff work like it did 6 months ago and I know it > can and like you said it does not seem fast enough. Personally I would have > recalled ALL the product back from the DIST and NOT sent it back until they > knew for sure it was good if thats not what they have done already. You've said that 10 times already and we all agree with you. > I think everyone is just venting me included since I have not been doing as > many installs due to equipment that keeps failing and I am not going to > order anymore till this corrected I have been sitting here looking at all > the features and or bugs same as everyone else. I know and understand. I'm in the same boat as everyone else and yes I have thrown a fit (in private) after having to send a tech back to the same house for the fifth time in two weeks. If you really want to help the situation, make better reports to sB on the exact circumstances. The better we write our discovery of problems, the better they can try to duplicate them in a lab. It's the quality of the report that will help solve the problem not the quantity of the reports. My2cents Michael The PART-15.ORG smartBridges Discussion List To Join: mailto:[EMAIL PROTECTED] (in the body type subscribe smartBridges <yournickname> To Remove: mailto:[EMAIL PROTECTED] (in the body type unsubscribe smartBridges) Archives: http://archives.part-15.org
