Helen,

The only time that I had major Windows errors with SBT Pro 5 was relating to video cards. I did alot of playing around with removing hardware video acceloration, etc but the only thing that fixed them completely was to replace the video cards with more compatible ones. I had a client with 10 brand new PC's and they all had the same video card and they had similar errors except one computer that was older and a different brand. It never crashed.

Bill

>Hello Al,
>thank you very much for your reply. I tried to check all step by step and what I have is:
>
>Both VFP500.DLL and VFP5ENU.DLL are 5.0.0.415 and they are in C:\Windows\System32.
>No duplicates, no older versions on this computer.
>
>We use FPROT antivirus on all our computers, not doing manual scan and do not have any problems with it.
>
>Motherboard BIOS and all drivers are Up-to-date.
>We do not use AIO printers.
>
>I was able to reproduce the problem on my dev machine just once with the same pure information.
>All other tries did not give me a crush.
>
>The user who has the problems has her own computer which is brand new.
>She is the user who mostly works with AR part of SBT.
>All other parts of SBT like IC, SO, PO work pretty well for different users on different computers
>
>Problem machine is basic and does not have any add-on hardware.
>
>We do not use OmniPage at all.
>
>The fault address I gave in my posting is just an example, it's not every time the same.
>I have 0x002bc2e1 (faulting module vfp500.dll), 0x00011d8f (faulting module ntdll.dll),
>0x00011e58 (faulting module ntdll.dll), but mostly 0x000109f9 (faulting module ntdll.dll).
>
>Best regards,
>
>Helen