Dave, Unfortunately, we have *zero *ability to directly fix the IEEE-1394 FireWire driver issues since we do not own nor do we have access to driver source code. The "raspy audio" issue has been escalated to TC Tecnnologies our FireWire chip vendor and they are working directly with Microsoft to resolve the issue. We are pushing to get a resolution.
PC systems that do not have excessive DPCs do not appear to have the problem. This has been discussed extensively here so I will not repeat that discussion. Gerald Gerald Youngblood, K5SDR President and CEO FlexRadio Systems(TM) 13091 Pond Springs Road, #250 Austin, TX 78729 Phone: 512-535-4713 Ext. 202 Email: [email protected] Web: www.flex-radio.com Tune In Excitement (TM) PowerSDR(TM) is a trademark of FlexRadio Systems On Sun, Apr 25, 2010 at 5:37 PM, Dave Gomberg <[email protected]> wrote: > I post this to FlexEdge (instead of FlexRadio, where it belongs) because I > want to > give everyone a chance to comment and Flex a chance to respond before the > issue is made public.... > > > Drax Felton wrote: >> >>> I disagree with this statement. It's not a waste of development to make >>> the >>> Flex software deal with this issue smoothly. >>> >> > I second this statement, it is not a waste of development to make Flex > software > deal with ALL issues smoothly. It is what we professionals used to call > "Professional > Grade Software". It should take whatever abuse you throw at it and do > just about > as good a job as a person could in figuring out what is wrong and getting > past it. It > is cheaper to write the code that to figure out what the user (or your sw) > did wrong, > then figure out a bypass, then document and publish it, and then deal with > all the users > who did not/would not read the doc. > > It turns out that professional quality software costs about double, to read > the code while > you still understand it and ask: What could go wrong, what would I want to > do about it? > Then you write two or three lines of "no-brainer" code to handle the > situation and issue > a diagnostic about what was wrong (bad data, bad branch, bad whatever). Do > not do > what MS does and issue a blue screen of death, unless you have already > written > comprehensive data to the error log. > > I think Flex has not yet learned this lesson, their sw (except the initial > stages of PSDR) > just screws up, with no error log entry or diagnostic message. BTW, if you > write a > diagnostic message, be sure to include the offending data in the message: > > Connot use SWR in sanity test in PSDR1013 because SWR < 1 (-3.456) > > You have no idea what use can be made of that errant value when debugging > code later. > Also, professional quality sw is LOTS easier to debug later when a user > finds a problem. > > Any more tips I can offer??? > > > > -- > Dave Gomberg, San Francisco NE5EE Programming since 1959 > All addresses, phones, etc. at http://www.wcf.com/ham/info.html > ----------------------------------------------------------------- > > _______________________________________________ > Flexedge mailing list > [email protected] > http://mail.flex-radio.biz/mailman/listinfo/flexedge_flex-radio.biz > This is the FlexRadio Systems e-mail Reflector called FlexEdge. It is used > for posting topics related to SDR software development and experimentalist > who are using alpha and beta versions of the software. > _______________________________________________ Flexedge mailing list [email protected] http://mail.flex-radio.biz/mailman/listinfo/flexedge_flex-radio.biz This is the FlexRadio Systems e-mail Reflector called FlexEdge. It is used for posting topics related to SDR software development and experimentalist who are using alpha and beta versions of the software.
