Main > Main Forum
A word about LEDBlinky…
Bender:
--- Quote from: Vanguard on May 03, 2010, 03:00:13 pm ---I'm not addressing the legality of selling your software. Yes, you are in the legal clear.
My point to csaun9001 is was that there is significant time/effort by the "free stuff" people inside of LEDBlinky. He made it sounds like "free stuff" is something else entirely.
--- End quote ---
you make it sound as if LEDBlinky is just a bunch of "free stuff" packaged together that Arzoo is trying to now sell
I don't think anything could be further from the truth
The vast majority of the program is is hard work. (Period)
csaun9001:
In case I was misunderstood, my entire point was that ARZOO has worked really hard on LEDBlinky and I am in full support if he now want some compensation for that hard work. Everybody likes to get things for free, sure, but not much in life is free. :dunno
arzoo:
Thanks everyone for the positive feedback :)
Vanguard:
--- Quote from: Bender on May 03, 2010, 03:10:23 pm ---
--- Quote from: Vanguard on May 03, 2010, 03:00:13 pm ---I'm not addressing the legality of selling your software. Yes, you are in the legal clear.
My point to csaun9001 is was that there is significant time/effort by the "free stuff" people inside of LEDBlinky. He made it sounds like "free stuff" is something else entirely.
--- End quote ---
you make it sound as if LEDBlinky is just a bunch of "free stuff" packaged together that Arzoo is trying to now sell
--- End quote ---
No, that's not my intent. I fully understand how much work arzoo has done. Also, I've backed off my original statement. As Cheffo pointed out, not everything is about MAME.
Vanguard:
--- Quote from: arzoo on May 03, 2010, 03:09:37 pm ---As I recall, the ledwiz function library was a ---smurfette--- to get working!
--- End quote ---
Yes it was. There were a bunch of users reporting that the LEDWiz/PowerMAME was either not working for them at all or was very flaky to the point of being mostly useless.
After quite a bit of debugging nothing was determined to be wrong with the driver. After much triage and research into the setups each user was using, it was determined that the users all had one thing in common. They all had systems with an Nvidia Nforce chipset. The ledwiz.dll developer had to acquire a computer system with the same chipset and debug the USB traffic with a sniffer. Once it was determined that packets were getting lost, the developer had to work with some USB experts at another company to determine what was causing the packet loss. To this day it isn't clear whether Nvidia is actually wrong with their USB implementation or whether the LEDWiz was expecting USB protocol to be implemented a certain way. In the end though, it didn't really matter as the problem needed to be fixed in order for the LEDWiz to be a robust product. The problem seemed to be a timing issue and a workaround was eventually found that solves the problem with software and saved the hardware vendor significant expense recalling his product. This was all done without the promise of pay.