foxpro 2.6 for windows virus 1

[datapak]

After a period of time and after a compile the menu in my
paykwikb.exe program is restricted and will not
display the programs in the pull down menu on each end of the menu.

This bug cannot be found by any of the virus software including Norton 360 and Grisoft.

Backup of the FPW26 files seems to have it go away for a while and it returns later on.

Anyone have this situation or any ideas on how to kill it.

Thanks.

datapak@payfreebie.com

 

[dgrewe]

Hmmm, A virus in a 20 year old software just now being found. ??? Not Likely.

Sounds more like a memory problem in the programming.

David W. Grewe Dave

 

[datapak]

Thank you for your comment, but if it were a memory problem
it would be consistant.
It tends to lie in wait for a month or so and then pop up in a compile.
My menu has 10 pull down columns and when it trikes it will not let the first column pull down dispay the 5-6 programs
in the pull down list.
Using Ad Aware will sometimes find what ever it is an kill it for a period of time, but it always returns.

Very frustrating. It is specific to Foxpro 2.6 for windows, but it may be a by product of worm or spyware.

Appparently only on our computers (8).

Datapak

 

[dgrewe]

Ad Aware cleans up Web related items like Cookies, Spiders, Spyware, Ect. Does your programs from the application access the internet ??


David W. Grewe Dave

 

[JRB-Bldr]

"if it were a memory problem it would be consistant."

Actually, memory problems are not consistent.
Quite the contrary, memory problems often come and go depending on what the individual user has open currently or has recently had open on the workstation. NOTE - Excel is a notorious competitor for workstation memory.

Additionally memory problems can be the result of memory chips responding to getting over-heated due to poor workstation ventilation on the PC or other reasons.

I have seen some workstation-specific memory related issues where the symptoms are as you have described. In these instances, the menu pull-down do not 'appear' to be working, but if the user 'pretends' that the pull-down is working and slowly moves the mouse down where the drop-down options ought to be, the drop-down choices do indeed show up one-by-one on the screen. If your users should see this type of behaviour, then you are indeed looking at a memory problem.

If this program has been working for quite some time, and the variety of commercial virus programs do not identify a newly attached virus to the EXE file itself, then an infected FP program is not a likely cause of your problems.

If your perception is that Lavasoft's AdAware is temporarily clearing up the problem, then you are likely chasing a 'red herring' by looking at the Foxpro program itself.

As Dave says above AdAware only clears up Spyware, Cookies, etc. and those would not directly affect the Foxpro program.

If not directly associated with 'normal' programs such as Excel, etc, then a more likely scenario is that something is launching background tasks in your Windows workstations which might be consuming your workstation's memory resources and, as a consequence, might be 'seen' as problematic behaviour by programs which are heavy memory users such as Foxpro, but the problem isn't in the FP program itself.

Good Luck,


JRB-Bldr
VisionQuest Consulting
Business Analyst & CIO Consulting Services
CIOServices@yahoo.com

 

[datapak]

Thanks for your input. We have experinced this on 7 different computers with different memory, but I agree something could be grabbing memory as you indicate.

 

[keepingbusy]

datapak

There may be lots of issues here with copyright, knowledge, ownership etc as I'm not sure about your software set up or where it came from. Do you have the original code or just the EXE?

If you own it, have you considered using a registered version of something like Refox to decompile the EXE/APP and check the source code or if you have the original source code, can you or someone else check it out?

KB

 

[datapak]

I appreciate all the interest in my situation.
From the questions it is obvious that I did not clearly identify my situation.
We are a software house and I believe the problem
occurs after a new compile of a very large employee
benefit and payroll program (PAYKWIK)
that we have written.
Will load up the memory and do a compile and see
if we can create the problem.

Sure nice to see all this help around on a really old
system. Thanks

Datapak Inc