Couple of minor hints that might help. One. Check out FreeRam XP Pro (http://www.yourwaresolutions.com). It can be configured to clean up all the leftover memory spaces not cleaned up when you exit various programs. Free.
Two. Check your processes using Task Manager (ctrl-alt-del). Delete immediately AcroRd32.exe, my worst enemy. That's Adobe Reader left over from reading a PDF file on the Internet. Most of the time it won't go away automatically and if left sitting in memory will be guaranteed to lock you up at some point. Main reason I switched to FoxIt Reader. My laptop at work (Win2000) always loads up with pctspk.exe, a utility to add voice messages for various functions. Can't stop it from loading at startup so I kill whenever I boot up in the morning. It then gets immediately replaced by ReaderSL.exe, a speed loader for Adobe! Kill that too. I'm using an SDR1000/FA66 and running WinXP Home Media Edition, 968 Mb ram, 2.2 GHZ processor, about five years old. Computer usage with MixW and PowerSDR running is between 30 and 40%, but I watch what else I run when PowerSDR is running. As they say on the Red Green Show, we're all in this together. 73, Carl WC0V Brian Lloyd wrote: >> I've solved problems like this in the past. Without getting into war >> stories, I worked with a client once who had an imaging device that >> could tolerate no more than 1ms latency. That, folks, is a LOT of >> latency. However, their device (controlled by a complex embedded >> Windows system) when working in production environments (not their >> lab, >> unfortunately) encountered a problem about once a day, always at a >> different time. Turned out, the problem was caused by combined >> interrupt and DPC latency created by a combination of their net card >> and >> the IDE controller handling a paging operation. In other words, it >> had >> nothing to do with their device or any of their image processing >> threads. We locked (pinned) their code in memory (making it >> non-pagable) and... the problem was solved. > > So, not being One With The Microsoft Gestalt I would need help to > learn how I would ensure that all the tasks (the things that gets > scheduled to run by the process/task scheduler in the kernel) > associated with PowerSDR, VAC, and MixW are locked in core and cannot > be swapped? That seems like a very sensible thing to do anyway. > > -- > > 73 de Brian, WB6RQN > Brian Lloyd - brian HYPHEN wb6rqn AT lloyd DOT com > > > > > _______________________________________________ > FlexRadio Systems Mailing List > FlexRadio@flex-radio.biz > http://mail.flex-radio.biz/mailman/listinfo/flexradio_flex-radio.biz > Archives: http://www.mail-archive.com/flexradio%40flex-radio.biz/ > Knowledge Base: http://kb.flex-radio.com/ Homepage: > http://www.flex-radio.com/ > > _______________________________________________ FlexRadio Systems Mailing List FlexRadio@flex-radio.biz http://mail.flex-radio.biz/mailman/listinfo/flexradio_flex-radio.biz Archives: http://www.mail-archive.com/flexradio%40flex-radio.biz/ Knowledge Base: http://kb.flex-radio.com/ Homepage: http://www.flex-radio.com/
