I have been going round and round with Evo on my Win7-64 machine. Finally had it going good and solid for several months and then did the 7/5 update and it's broke again. Actually, it worked fine the first day of the update, including starting and quitting Evo several times and at least one system reboot in there. Then the next day, bang! You're dead.
 
I'm wondering how much of the problem might be Win7 vs 64-bit. Anyone have any words of wisdom or testimonials? BTW, DBA Classic works fine on here, if a bit slow.

Quote from RPCAdmin on 08/03/10 at 12:40:04:

 
Yes, I did that. I also had to use UNC drive mapping. I thought I (well, with Malcolm's help) had it fixed...  

I have noticed in Win7 that sometimes in File>Open or File>SaveAs dialogs that it will show that drives are not connected (red "x" on them). However, I just tried Evo with a Win Explorer window open to both the applications and data folders; no luck...

EvoERPSetup.exe shows the correct UNC drive mapping.
 
Here is a sequence of what happens:
 
(first of all, I have to run Evo as administrator, so I have to say "yes, I really want to do this)
 
I get the logon window, then:
 
FILE OPEN ERROR
Error number 12
File was not found
File name: BKSYMSTR
Program name: \\SBSR2\APPS\DBAMFG\EOVOERMENU.RWN
EXE path: C:\ISTS\
This program will now end.
 
After I close that, I get a message about opening a file that doesn't exist, or something like that on BKSY.COMP.NAME, and then what looks like the Evo window but with no buttons on it.
 
UPDATE:
 
Just for the fun of it, I decided to uncheck "Run as Administrator", and now it works  
 
Edit:
Ooops. Spoke too soon. Evo opens, but many programs won't open - it just goes into "not responding" mode. Maintain Database works, TAS-G works. It seems that T7 programs work, but so far not a single BK or T6 one. And although T7SOA opened it hung when I did a lookup.
 
Something obviously is still wrong...

T6 and BK programs load a second instance of the EXE.  Add TP7RUNTIME.EXE to your DEP exceptions and see if that helps.

The difference between the T7 programs (that work) and the T6 & BK (that don't) is that the T6 & BK chain to a new instance of the TP7RUNTIME.EXE so somehow your workstation isn't liking that but I don't know why if it is not the DEP.

This is a wired network.
 
Running AVG 9.0 (paid version).
 
I ran the ping test, and after 15 or 20 minutes all the ones I've seen have been <1ms except when I first fired up Evo it dropped to 9 & 10ms. Not a single time out.
 
So far I have not been able to get a red X in Explorer.
 
However one thing you said makes me curious.
Quote:

 
I don't get a tp7runtime showing in Task Manager even when Evo starts all the way up, not even on a good fully-working workstation... Should I be?
 
EDIT: just realized that Ctrl+Break shows the packet data. So far, sent 1139 packets, received 1139 packets. 0 lost.

We have a similar problem.
 
if we try to use the shortcut with "C:\ISTS\evoerp.exe C:\ISTS" target
we get the following error: Data dictionary file could not be opened:F:\DBAMFG\FILELOC.DBF
 
But
 
If you go to start  then run and then open F:\DBAMFG\evoerp.exe
 
It works ok
 
???
 
 
 
Kelloggs

No, I'm sorry for the confusion.  I didn't mean it quite like that.  
 
When you run Evo (if it's set up right) it should start EVOERP.EXE.  While it Evo, running one of the menu programs can start TP7RUNTIME.EXE.  
 
I was trying to say that on the chance that you got far enough to start it, kill it.  What I didn't say was that we need to do it anyway, no matter how it was started, because it keeps us from chasing a whole array of phantom symptoms.
 
Well at this point, you have a decision to make.  if you want to take the wreckless approach (like I would), wipe and reinstall Windows.  If given the option, limit what it installs to just the Operating System.  Then install Pervasive's 32bit client, run the Evo workstation setup - USING THE UNC with the server's IP address instead of it's name - and run it.
 
In your email to me, you asked if you should go back to 32bit.  I say 'no'.  First, because I'm running 64bit Ultimate and LOVE IT!!!!!  Second, and probably more important, because I've seen this happen on 32bit Vista and Win7 too, so in this case I'd say there's no benefit.  
 
But if you want to take the safe route and troubleshoot the problem then it's time to start removing some variables.  First I'd run System Restore and go back to the oldest point possible.  Then I'd uninstall your AntiViirus, all the software and hardware you don't 'need' and using MSCONFIG, take all things 'not Microsoft' out of your startup. You'll also need to uninstall Evo, the same way you did last time, and all things Pervasive.  Then turn of the UAC and Reboot a few times. Reinstall the 32bit Pervasive client and Evo - USING THE UNC with the server's IP address instead of it's name.  If that doesn't work, then I'd have to see it.  
 
Of course, the downside to 'the safe approach' is that you run the risk of screwing up your system anyway with all the uninstalling and Shrug and Pray's (Plug and Play) attempts to reinstall stuff.  That's why I'd just reinstall in the first place.  Faster and much less thinking!  Plus I get the benefit of a clean slate!

Quote from David Waldmann on 08/04/10 at 12:02:39:

 
Definitely proves that the problem is local BUT I wouldn't run it like that for any length of time.  EVOERP.EXE 'wants' to be run from the local ISTS folder.  

Quote from skyywalker on 08/04/10 at 11:57:16:

 
I'm unfamiliar with that format. Would it be 111.222.333.444\drive?
 
Quote from skyywalker on 08/04/10 at 11:57:16:

 
That's the answer I was expecting, but thanks.
 
Quote from skyywalker on 08/04/10 at 11:57:16:

 
I think that's probably what I'll do.
 
Yes, I am running 2000i SP3. I had bought v10 a couple years ago when we got a new server and couldn't get it to run (can't remember why?) so I got rid of it. Maybe I should re-visit that, but DBA Classic runs flawlessly on Win7-64...

I forgot to mention that our server is Windows 2003 and only the Workstations are Windows 7 - 64
 
 
Quote from Kelloggs on 08/04/10 at 11:31:31:

Quote from Kelloggs on 08/04/10 at 11:31:31:

 
Do you get an error number too?

Quote from Kelloggs on 08/05/10 at 07:26:07:

 
UGH - that's a tuff one.  if it's just the one workstation i'd probably start by uninstalling and reinstalling the pervasive and evo clients.  but if that doesn't work - or if you already did that - I'd say either work thru it with Lynn's support group or reinstall Windows...  ...And my vote's for the latter!
 
======
I've got a sneaking suspicion that if i took the time to collect data on this issue, I'd find that it's more common from a particular oem or two....but if i'm right, reinstalling <i>shouuuuld</i> take care of it since the hdd image probably isn't the same as the image from the restore dvd...  
 
just a thought!

Quote from lesleys on 08/26/10 at 06:42:03:

 
Can you elaborate?  We need Windows/DBA/Pervasive version numbers...both before and after the 'install'.  
 
If you have more than one workstation, do you see the problem on other workstations?

When installing the Pervasive client on the Win 7 machine, make sure to right click and install as admin
 
When in doubt, reinstall the client
 
The same when running Evo the first time from the server. Navigate to the EVERP or DBAMFG folder on the server and right click on evoerp.exe and run as admin.
 
You should also make sure that your anti virus software is not checking everything that runs from the EVOERP/DBAMFG folder.
 
My Win7 installation now runs Evo at the same speed in ran under XP

Interesting tidbit about the network drives - happens here frequently and is mildly annoying.....One question however - what if you don't have a domain and only have the network set up as a workgroup?