FW: Windows 7 compatibility issue

Mon Oct 7 08:04:27 PDT 2013

Top Post:

What is the path to  the fp directory (folder)?  

Has the hardware vendor run any applications that look for rootkits on the server or other workstations connected to the network?

One of my client's recently had a virus attack on their server.  Their filepro applications is buried 3 folders down on that server and was not affected by the attack.  (N:\company\filepro\fp56\fp) .  I was not told what virus was attacking their server but apparently whatever it was did not search that deeply.

Richard Kreiss
GCC Consulting

Office: 410-653-2813

> -----Original Message-----
> From: filepro-list-bounces+rkreiss=verizon.net at lists.celestial.com
> [mailto:filepro-list-bounces+rkreiss=verizon.net at lists.celestial.com] On
> Behalf Of Coleman, Don
> Sent: Monday, October 07, 2013 8:49 AM
> To: filePro Mailing List
> Subject: Re: FW: Windows 7 compatibility issue
> 
> Walter:
> 
> Below is the entire post.
> 
> Long-time client with relatively new fP user suddenly cannot start her fP
> application.  When starting either my app. directly or even P.EXE, Windows 7
> issues the following error:
> 
> "This program or feature cannot start or run due to incompatibility with 64-bit
> versions of Windows"
> 
> I configured this work station for fP myself last year when it was replaced by
> their I.T. vendor (formerly an XP machine).  It has run fP w/o issue until today.
> Client is not aware of any changes made to this machine since she last used
> her fP application (this past Friday).  Any idea what may have changed or been
> changed to suddenly cause this?  To avoid possible changes made to the
> shortcut, I had her try starting the fP app. directly from her network drive
> (bypassing the shortcut) and starting P.EXE directly, both now cause the
> incompatibility error.  At the moment I cannot confirm the version of fP since I
> cannot start fP, but know it is either v4.8 or v5.0 because I use the
> PFPOSTPRINT feature in conjunction with PrintWizard.
> 
> 
> To update this issue, the Windows 7 compatibility error was being caused by
> an apparent malware infection found on the server.  I am waiting for their
> hardware consultant to provide details (name, etc.) on it.  Every hour on the
> hour, the fP executables are modified by this apparent threat, increasing in
> size.  If I restore the executables, my fP app once again works fine, until the
> top of the hour.  There are postings similar to this noted on both
> microsoft.com and google searches, but nothing that I have seen referencing
> it happening on the hour.  The client's hardware vendor has told me they
> have reviewed the scheduled tasks and services running on the server, but
> have found nothing they believe causing this.  Their initial Norton EndPoint
> search did find 8 occurrences of a virus in various public document folders on
> the server and said they removed them.  They have not updated me as to the
> results of a full scan of the server.  To temporarily resolve my portion of this is
> sue, I moved my app from the server to a local work station where it has been
> functioning fine.  For data backup purposes, I have the client copy the filePro
> folder from the local machine to the server each time they use my app,
> usually several times per week.
> 
> I have been out of town unexpectantly for the past 10 days, and need to get
> an update from both the client and hardware vendor today.  I will advise if I
> receive any additional details.
> 
> Don Coleman
> Donald G. Coleman, Consultant
> 402 Andrew Circle
> Indiana, PA 15701
> (724) 349-6302
> (412) 849-2589 (cell)
> 
> ---------- Original Message ----------------------------------
> From: "Walter D Vaughan Jr" <wvaughan at steelerubber.com>
> Date:  Sun, 6 Oct 2013 15:32:41 -0400
> 
> >
> >
> >-----Original Message-----
> >From:
> >filepro-list-bounces+wvaughan=steelerubber.com at lists.celestial.com
> >[mailto:filepro-list-bounces+wvaughan=steelerubber.com at lists.celestial.
> >com]
> >On Behalf Of Kenneth Brody
> >Sent: Wednesday, September 04, 2013 10:31 AM
> >To: dcoleman at dgcreact.com
> >Cc: filepro-list at lists.celestial.com
> >Subject: Re: Windows 7 compatibility issue
> >
> >On 9/3/2013 2:36 PM, Coleman, Don wrote:
> >> Long-time client with relatively new fP user suddenly cannot start
> >> her fP application.  When starting either my app. directly or even
> >> P.EXE, Windows 7 issues the following error:
> >>
> >> "This program or feature cannot start or run due to incompatibility
> >> with 64-bit versions of Windows"
> >>
> >> I configured this work station for fP myself last year when it was
> >> replaced by their I.T. vendor (formerly an XP machine).  It has run
> >> fP w/o issue until today.  Client is not aware of any changes made to
> >> this machine since she last used her fP application (this past
> >> Friday).  Any idea what may have changed or been changed to suddenly
> >> cause this?  To avoid possible changes made to the shortcut, I had
> >> her try starting the fP app. directly from her network drive
> >> (bypassing the shortcut) and starting P.EXE directly, both now cause
> >> the incompatibility error.  At the moment I cannot confirm the
> >> version of fP since I cannot start fP, but know it is either v4.8 or
> >> v5.0 because I use the PFPOSTPRINT feature in conjunction with
> PrintWizard.
> >
> >Is there more to that message?
> >
> >If you are trying to run an ancient MS-DOS version of p.exe for some
> >reason (still supported by 32-bit Windows, but not supported by 64-bit
> >Windows), then you would get a popup with something like this:
> >
> >==========
> >
> >---------------------------
> >Unsupported 16-Bit Application
> >---------------------------
> >The program or feature "\??\c:\appl\fp.old\P.EXE" cannot start or run
> >due to incompatibity with 64-bit versions of Windows. Please contact
> >the software vendor to ask if a 64-bit Windows compatible version is
> available.
> >
> >---------------------------
> >OK
> >---------------------------
> >
> >==========
> >
> >Now, as to why it would have worked and now doesn't, perhaps you have
> >two copies of p.exe on your system, and something changed to cause
> >Windows to now run the "wrong" version.  I have heard of some
> >anti-virus programs picking up p.exe as "infected" for some reason, and
> >silently deleting/quarantining it.
> >
> >
> >--
> >Kenneth Brody
> >_______________________________________________
> >Filepro-list mailing list
> >Filepro-list at lists.celestial.com
> >Subscribe/Unsubscribe/Subscription Changes
> >http://mailman.celestial.com/mailman/listinfo/filepro-list
> >
> >_______________________________________________
> >Filepro-list mailing list
> >Filepro-list at lists.celestial.com
> >Subscribe/Unsubscribe/Subscription Changes
> >http://mailman.celestial.com/mailman/listinfo/filepro-list
> >
> 
> 
> 
> 
> 
> ____________________________________________________________
> ____
> Sent via the WebMail system at mail.dgcreact.com
> 
> 
> 
> 
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> Subscribe/Unsubscribe/Subscription Changes
> http://mailman.celestial.com/mailman/listinfo/filepro-list