Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Fpw26 runs slow in windows 2000
Message
From
16/12/2001 21:27:38
 
 
To
14/12/2001 15:32:57
General information
Forum:
Visual FoxPro
Category:
FoxPro 2.x
Miscellaneous
Thread ID:
00541470
Message ID:
00594983
Views:
56
I presume this was meant for Chris , so I'm simply reposting.
I'm not surprised by the anti-virus problems.
Has anyone ever worked out that the time you spend updating virus checkers, checking disks, running with a slow system and the occasional virus checker bug may actually be worse in the long run than putting up with the viruses? :-0


>I recently resolved ONE speed problem on Win2K and FPW 2.6:
>
>1. This client runs my application on a Win2K network (workstations and server). First user goes in quite fast, but the subsequent users take a LONG time before even getting to the login screen. I followed the program excecutions with a debugger, and noticed that it was very slow opening files. Once files were open, it moved quite fast. I modified the CONFIG.FPW settings for my app(see below), set the app executable to run as a separate task on the workstation, but nothing seemed to help. Then I disabled Norton Antivirus autoscan (check files for viruses before opening or using them), and the system sped up dramatically. It used to take 40 seconds to get to my app's login screen, now it took only 5.
>
>The strange thing about this is that Norton slowed it down even I excluded the DBF, FPT and CDX file extensions from the scan. It seems to STILL examine these files, included or not!
>
>So, you can speed startup and operation tremendously by turning off Norton autoscan. This problem seems to affect ONLY Win2K and possibly XP computers. On Win98 SE the program runs fast no matter what norton is doing.
>
>The modified/added settings in CONFIG.FPW -file in the my app's folder:
>MEMLIMIT=0,8000,48000
>TMPFILES=C:\TEMP
>RESOURCE=OFF
>
>NOTE: You can substitute C:\TEMP to any other existing local folder.
>
>2. Another culprit for slow speed seems to be compression. In Win2K you can set up disk compression, which slows the application down considerably, and may even lead to random index file corruption (even with VFP7!). So, make sure compression is not turned on.
>
>3. Try installing W2K SP2 from Microsoft. This service pack fixes a number of problems with W2K. My client was running SP1, at least on the workstations, though.
>
>4. Open taskmanager and end non-critical tasks one by one, then run your app. Some background programs might interfere with the program, just like Norton Antivirus did, and this is a good way to find out what they may be.
>
>
>Hey, at least it is SOMETHING to try, no?
>
>Pertti
Previous
Reply
Map
View

Click here to load this message in the networking platform