> However, the problem is that this is impossible to accomplish in the real > world.
Sorry, Ray. I have to disagree with you. If this were true, nobody would ever get a system to accomplish ANYthing. Now, you ARE right about several things: Numerous parts of the system change from installation to installation, user to user. And Flex doesn't control everything. But, none of us controls EVERYthing, right? But you CAN control LOTS of things... and I postulate that you can control enough things to make the MOST of the glitches we see go away. You can employ engineering methods, and specialized knowledge, to address many problems. Of course, if you don't KNOW about these mechanisms, you can't use them. So, for example: What -- specifically -- is being done in the DRIVER to mitigate these problems? What devices/drivers CAUSE problems in FlexRadio environments? What Windows services? For another example: How does PowerSDR organize its processing? How is work divided into threads? Are processor affinities used and when? Does PowerSDR use the Windows Multimedia Class Scheduler Service (which was implemented in Vista to mitigate EXACTLY the kinds of glitches we see in PowerSDR)? If not, why not? When you look at a system end-to-end I think you'll find many things in that chain that you CAN control. I reject the idea that "every system is different, so it has to be up to every individual to make their own system work." This only becomes true once a systems approach has been applied to the problem, and all system-wide remedies have been applied. THEN, sure.... maybe there are systems that are "outliers" that don’t work properly. And even in that case, we should be able to provide some guidelines about good and bad configuration practices. Peter K1PGV _______________________________________________ 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.
