Main eSignal window vs Primary Monitor

[shaeffer]

My new computer arrives this weekend, so I'll finally be able to leave 8.0. Before I install eSignal on this new computer, is there a 'preference' within the eSignal program that the main eSignal window be located in the primary monitor of a multi-monitor system?

Right now, I have two rows of three monitors. The bottom-middle monitor is my primary monitor and the main eSignal window is the top left monitor. In this setup, there are two glitches (that may no longer exist in 10.x?).

1. My EFS Performance Monitor window always opens in the bottom middle (my primary) monitor. If I close it from that location, next time it opens in the ether somewhere (I think in the right side of a non-existant third row of monitors, i.e with a one row down and one monitor shift right offset). But, after opening the EFS PM window, if I then move it to the top left monitor (main eSignal window) and close it, then it will open next time in the bottom-middle monitor again (the same offset mentioned above).

2. If I resize say a 2"x4" floating window (outside the main eSignal window), then later redock it, it redocks with a size of about 12"x18". It seems as if the right side of the window stays anchored at its original location, and only the top left corner of that window moves back to the main eSignal window. It then takes three or four resizes to get back to the original size (a minor annoyance).

I've mentioned both these issues before. Will this still occur in 10.x? Or to prevent this (or for any other reason), do I need to place the main eSignal window in my primary monitor? It is my preference not to make them the same.

Since this new computer will be primarily used to run eSignal, any suggestions on the setup (i,e, separate partitions for the OS and eSignal)? I'll be running an i7 CPU with 6GB tri-channel memory and Vista Premium 64 bit if that matters

Thanks
shaeffer

[eSignal_AveryH]

Shaeffer,

Let me investigate these issues and talk with the Product Manager. Once I have more information I'll post back.

AveryH
eSignal Support

[shaeffer]

Thanks Avery,

A search of my name in the forum would provide details from the past discussion on these two issues, if that woud help.

Regards
shaeffer

[eSignal_AveryH]

Shaeffer,

First off congratulations on the new computer, the Vista 64 should work well. I've installed eSignal on my Vista 64 laptop and haven't had a problem yet. The most important thing to remember with Vista is the Virtual Store, this is where your items (EFS Files, Pages, etc.) for program files will be stored.


Please see answers below regarding your questions.

1. My EFS Performance Monitor window always opens in the bottom middle (my primary) monitor. If I close it from that location, next time it opens in the ether somewhere (I think in the right side of a non-existant third row of monitors, i.e with a one row down and one monitor shift right offset). But, after opening the EFS PM window, if I then move it to the top left monitor (main eSignal window) and close it, then it will open next time in the bottom-middle monitor again (the same offset mentioned above).

The EFS Perf Mon window continues to associate itself with the assumption that eSignal is on the primary monitor. So yes you'll still experience it diagonally moving to the next row of monitors if you do not close it within the same monitor as the eSignal.

2. If I resize say a 2"x4" floating window (outside the main eSignal window), then later redock it, it redocks with a size of about 12"x18". It seems as if the right side of the window stays anchored at its original location, and only the top left corner of that window moves back to the main eSignal window. It then takes three or four resizes to get back to the original size (a minor annoyance).

Window size for floating and docked windows is one you don't have to worry about. The windows sizing was corrected in the latest release of eSignal 10.5. What it will do is remember what the size of the chart was when it was last saved within the eSignal frame or if it's a new chart that has not yet been save it will take on the size of a new default chart when it's docked back inside of eSignal.

Please let us know if we can answer any other questions or concerns.

[shaeffer]

Hi Avery,

I could search out what this Virtual Store is all about (I've never heard of it before), but if you happen to have a link handy I'd appreciate it. It sounds like I better know that before installing the program.

I think that EFS Perf Mon window location should be considerd a glitch, since if one forgets to relocate the window before closing it, the window becomes 'lost' and then takes finding some config file somewhere and erasing the x,y coordinates to make it viewable again. In my setup, the Edit Alerts window always opens in the primary eSignal window - can't the location coding for that be copied into the EFS PM window?

Good news that the window sizing when redocking is saved now.

Supposedly a quad core i7 CPU shows four CPU Usage windows in Task Mgr - it will be interesting to see how the load is handled. I think it is not until the next release though that eSignal is multi-threaded?

Regards
shaeffer

[jgr]

On this Virtual Store.

I run Vista 64 at SP 2 level on two machines and there is nothing called Virtual Store. I read and write files to the esignal pages etc in the Program Files (X86) directory just fine. I may have at some time ago added my personal read/write rights to everything in Program Files (x86) but I am not sure.

[eSignal_AveryH]

I could search out what this Virtual Store is all about (I've never heard of it before), but if you happen to have a link handy I'd appreciate it. It sounds like I better know that before installing the program.

The VirtualStore is created when UAC (User Account Controls) are turned on. The VirtualStore is in a hidden directory in the C:\User folder. The path to the virtualStore is %userprofile%\appdata\local\virtualStore and if you look in the program files it will show what application run there, eSignal actually run in the Program Files (x86) which is an indications that Windows labels it as a 32bit application.

I think that EFS Perf Mon window location should be considered a glitch, since if one forgets to relocate the window before closing it, the window becomes 'lost' and then takes finding some config file somewhere and erasing the x,y coordinates to make it viewable again. In my setup, the Edit Alerts window always opens in the primary eSignal window - can't the location coding for that be copied into the EFS PM window?

I'm pretty sure that when the new framework of eSignal comes this will be address. I'll follow up with and email to Product Management just to make sure.

Supposedly a quad core i7 CPU shows four CPU Usage windows in Task Mgr - it will be interesting to see how the load is handled. I think it is not until the next release though that eSignal is multi-threaded?

The i7 should be a pretty awesome processor; we haven't gotten much feedback from folks at have it now. I think now that we have multi-threaded EFS that should lighten the load from some of the eSignal. Hopefully early next year we'll a new eSignal that you'll be able to start working the other three processors.

AveryH

[shaeffer]

Originally posted by eSignal_AveryH
The VirtualStore is created when UAC (User Account Controls) are turned on. The VirtualStore is in a hidden directory in the C:\User folder. The path to the virtualStore is %userprofile%\appdata\local\virtualStore and if you look in the program files it will show what application run there, eSignal actually run in the Program Files (x86) which is an indications that Windows labels it as a 32bit application.
AveryH

Thanks for the reply Avery, but I'm still not clear. Because I have a 64 bit OS, do I have to install eSignal differently, i.e., do I need to create this Virtual Store by turning on this UAC at some point in the installation process?

Before you said "The most important thing to remember with Vista is the Virtual Store, this is where your items (EFS Files, Pages, etc.) for program files will be stored." After installing eSignal, do I need to move all the EFS's I use into this Virtual Store directory, and then reload them into each chart with the new directory path? I don't use Pages, but does this apply to layout files as well? Or is all this done automatically during the installation?

Regards
Shaeffer

[eSignal_AveryH]

Shaeffer,

Sorry I was not being clearer before; you don't have to do anything. The operating system will take care of everything for you.

The VirtualStore comes in to play when it comes time to moving and or saving your EFS studies, Pages and Layouts. A perfect example in your case will be; Once you’ve installed eSignal and you’ve move your layouts and windows into the C:\Program Files(x86)\eSignal directory. Later, when you go back to this same directory to edit or delete one of the layouts, Vista will have moved all those files from the System Directory (C:\Program Files(x86)\eSignal) to the VirtualStore (%userprofile%\appdata\local\virtualStore) for you.
Not to worry though, the eSignal Technical Support Staff is well versed in helping you with any issues you run into with Vista.

AveryH

[shaeffer]

Thanks Avery, I've got it now.
Have a good weekend!
Shaeffer

[eSignal_AveryH]

No problem, please let us know how the new machine works out for you.

[shaeffer]

Originally posted by eSignal_AveryH
No problem, please let us know how the new machine works out for you.

Hi Avery,
The graphic below tells the story. Even with an i7 processor and 6GB of tri-channel memory my computer will often hesitate (running just eSignal and IB).

I understand the brand new eSignal (I forget the new name) is due the end of March, and will be multi-thread designed. I'm looking forward to it.

Regards
shaeffer

[eSignal_AveryH]

Thanks for the information, has this been the typical performance of this machine or has it been a slow decline?

[shaeffer]

Hi Avery,

The performance has slowly declined. It started out much better than my previous P4 dual-core computer. But then I started loading up more charts and efs's. I try to clean out old trend lines fairly often, so I don't think that's contributing to the slowdown. And I try to optimize my efs's, but I've learned that just because they appear to work doesn't mean there is not an inefficiency problem.

I have a Win 7 upgrade disk, but have been reluctant so far to make the switch from Vista (not that I like Vista in particular).

The morning today was very active, so the hesitations were much more noticeable than usual. Your question suggests you might have an idea about the slowdown?

Regards
shaeffer

[jgr]

shaeffer,

I too had serious performance problems with my Core 2 Duo machine. I built an ASUS with I7-860 and 8 Gbyte RAM and that helped a lot. I don't see slowdowns except for very short times. But the volume has been lower in the recent months. It is times of high tick rate that the system bogs down and their main processing engine only uses one core regardless of how many there are.

I did upgrade to Windows 7, 64 bit and that is what stimulated my hardware upgrade as W7 is actually slower than Vista 64 I had before. Apparently MS did two things in W7 that slow it down. One is to devote more CPU cycles to the OS interface which makes W7 respond better to users but process applications slower. The other was to put back in some 16 bit application support because of all the old applications around with DOS and Windows 95 code still in them. This also slows down the computer as 16 bit is an emulation layer on top of 32 bit which is itself an emulation layer on top of the native 64 bit base.

MS has not been very successful in getting developers to write for 64 bit. My understanding is that the new Esignal will be 32 bit as will the new application from Schwab.

Interesting that Apple has taken the bold step and their newest most powerful machines run 64 bit applications ONLY.