| T O P I C R E V I E W |
| Benno |
Posted - 28 Mar 2009 : 21:15:16
Hi All,
On support Technical I see support for Windows Vista. Does this include Vista 64Bits?
I use V12.x of EasyPC. I plan to buy a new PC and am thinking on going 64 bits and a lot of Ram.
Thanks
Benno
|
| 6 L A T E S T R E P L I E S (Newest First) |
| DavidM |
Posted - 14 Apr 2009 : 18:01:20
Although its not a direct 'fix' for your problems installing msflxgrd.ocx, we have verified that one of our test machines with Vista64 has the ocx in the same SysWOW64 folder you describe, and Easy-PC component editing works fine.
However, as this machine has been set up and running for a while now, I can't be sure how this file got set up the first place.
Back to your initial question, we don't currently list XP64 and Vista64 as supported platforms, but I am expecting these to be added to the list at the next release of Easy-PC in the summer. |
| apemberton |
Posted - 14 Apr 2009 : 16:27:05
Thanks for the response.
I agree with you about Symantec but I don't want to change all my systems right now.
I had backed up all my library files to my sharing server before removing all the EPC progs etc from the 32bit Vista machine. It seems that some of my missing library items were old, pre version12 designs but I doubt that is an issue. I suspect the problem is self-inflicted in that I probably did not save each item to my libraries. The more recent entries seem to be OK.
The worst item I lost was a TO252-5 footprint and a P & N channel MOSFET schematic in the same package (FDD8424) and it was quite instructive re-creating the design. There was a checkbox or summat (I forget which) I should have used to ensure the correct files got saved where they should be.
Ça va!
Tony Pemberton
|
| Peter Johnson |
Posted - 14 Apr 2009 : 14:51:16
Most of the library issues can be avoided by initially using a custom installation (which allows the user to choose the installation path)and avoiding the program files tree.
If you do have a backup copy of the damaged/missing library files, they just need to be copied into the appropriate place. If the backup's damaged, you don't need to rebuild from scratch, as you can scavenge symbols and components from existing designs.
Regarding Symantec. In my years on the support desk, I've found Symantec to be at least an order of magnitude more likely to cause problems than ANY other anti-virus software. Additionally, their detection scores in anti-virus reviews are rarely above the mediocre. I'm convinced that it's a classic case of advertising triumphing over proper research. On the basis of my experience with it, I would recommend pretty well anything except Symantec/Norton, with the possible exception of Avast. That doesn't interfere, but they too have consistently low detection scores (unless they've improved very recently)! |
| apemberton |
Posted - 11 Apr 2009 : 16:15:51
Well I have progressed to the point that EPC doesn't hang the machine while handling libraries.
It seems that msflxgrd.ocx is a VB6 file which is no longer supported by MS and certainly not in 64bit Vista. However I found the instructions for installing on a page here but they will not work on Vista64. The msflxgrd.ocx file is actually located in folder c:\windows\SysWOW64 .
Otherwise the procedure works (though I havn't performed a cold start so I don't know whether the installation of msflxgrd.ocx is permanent or i have to go through the fiddle-faddle of going into the administrator session every time (though I guess if I do I will have to set up a startup script).
Nevertheless, i have lost some of my custom libraries (which are backed up) especially pcb footprints for devices not in the Prolib. That means that I have to do some serious reworking to get back to the status quo before I can progress back to my principal design work.
Incidentally, I have found the Symantec Norton 360 V3 considers EPC and a lot of associated .dll's to be untrustworthy as it cannot validate their certificates and may consider these files to be viral. I can't yet see a way of making them trustworthy at the machine level but in any event EPC will run.
I hope there will be an update that eliminates these problems, especially as it seems that Vista will be consigned to second string / history before too much longer.
Tony Pemberton
|
| apemberton |
Posted - 10 Apr 2009 : 16:14:23
I have had an issue with EasyPC after installing Symantec N360 V3.0 antivirus software on my 3 Y.O. Vista 32 bit machine which locks up that machine. Previously to installing N360 V3 I had been running fine with N360 V2.0 and EPC V12 apart from the library duplicate problems. The PC effectively locks up and I had to use the Widows Task Manager to kill the process thread. With N360 V3 I can see no way of recovering the situation and the PC is a bit dated anyway. Eventually I have uninstalled EPC on that machine to allow me to get on with other things.
Taking a radical approach, I have re-installed EPC V12 on a brand new Vista 64bit with N360 V3.0 and most things seem to work (and indeed looks good on a 1920x1080 screen - lots of screen 'real-estate' for schematics etc.). However, there is a library issue still in that the 32bit applications install in the C:\Program Files (x86)\Number One Systems\Easy-PC\Library folder. I also have a C:\Program Files\Number One Systems\Easy-PC\Library folder too. When I try to open a library item I get a Windows message that states that there is an OCX problem and I should contact my software provider.
Copying across my old libraries to the new machine has been performed but I'm not sure where they should go at this time.
I admit I havn't called support yet. I shall try a few things before doing so but if anyone has any tips, i would be grateful.
|
| Peter Johnson |
Posted - 31 Mar 2009 : 19:03:02
As far as we're aware there shouldn't be any major problems. It's not been fully checked on 64 bit machines, but is certainly running successfully on an XP 64 installation. Vista 64 bit hasn't been formally verified, but we haven't seen lots of support issues arising either.
I'm sorry that I can't just give you a resounding OK, but I'd rather you were properly informed. |
