I just found this forum...
I've been having problems with high CPU loading since December and never associated it with eSignal. I'd looked for worms, trojans, swapped video cards, etc. and had convinced myself there was something internally at fault in my motherboard. The problem affected all programs (Outlook extremely slow to open e-mail, Excel, etc.) - even immediately following a power-up boot in with nothing else (eSignal) running.
Found the thread about deleting the line tools and did that. My 4 ach files went from around 200KB to about 8-15KB and the high CPU problem is gone!! :-)
The part I found most interesting is that this solved the problem for the other programs too - whether eSignal is running or not. Out of my realm here (not a computer type), but does that mean eSignal was using some portion of memory and not releasing it (I'm using XP Pro)? If so, there may be a lot of folks like me that haven't made the connection and are having similar problems and need to hear about this.
Mark
I've been having problems with high CPU loading since December and never associated it with eSignal. I'd looked for worms, trojans, swapped video cards, etc. and had convinced myself there was something internally at fault in my motherboard. The problem affected all programs (Outlook extremely slow to open e-mail, Excel, etc.) - even immediately following a power-up boot in with nothing else (eSignal) running.
Found the thread about deleting the line tools and did that. My 4 ach files went from around 200KB to about 8-15KB and the high CPU problem is gone!! :-)
The part I found most interesting is that this solved the problem for the other programs too - whether eSignal is running or not. Out of my realm here (not a computer type), but does that mean eSignal was using some portion of memory and not releasing it (I'm using XP Pro)? If so, there may be a lot of folks like me that haven't made the connection and are having similar problems and need to hear about this.
Mark
Comment