Win 7 64bit Disguises filepro errors

Kenneth Brody kenbrody at spamcop.net
Fri Nov 15 12:23:55 PST 2013


On 11/15/2013 12:58 PM, Jerry Crespi wrote:
> Hi,
> This is a heads up:
>
> I have a client who has recently moved from Win XP  to Win 7 64
> bit.  Their filepro app is a large and complex program that helps
> them do fiberglass fabrication.  It also handles invoicing,
> inventory, PO's and a host of other office functions.  They only have
> 6 users and are on 5.7 with a runtime system and only one development system.
>
> For the first time since their move, they used a part of the program
> on Win 7.  It produced errors that stated that rclerk was no longer
> working with the following error message:
>
> Exception error 3221225477 (0xc0000005) in process failed 0(0x00000000)
> comspec="Y:\fp\rclerk fabricate -s1
[...]
> The moral of the story? Don't believe what you see or anything that
> anyone tells you.
>
> Windows 7 64bit may not report 32 bit program errors correctly.

It's probably reporting it just fine.  That error is very similar to a 
"segmentation violation" on *nix.

I have seen such errors on Windows systems with faulty network hardware.  I 
am going on the assumption that "y:" is a network drive?

Check the system's event logs, and see if there are any other error logged 
at that time.

As a test, copy "y:\fp" to "c:\fp", point PFPROG to "C:", and try it again 
on that same system.  If it starts working, there's your answer.

-- 
Kenneth Brody


More information about the Filepro-list mailing list