>>OK. On a more posotove note, how can you post a useful message about YAC0000005E (Yet Another C0000005 Error)? The most important things to know are:
>>
>>(1) What's your environment. Operating system (include patch levels if you know them), memory, disk video. If it happens during print-related operations, the print drive would be useful. Network environment is useful. If IE4 is present, is Active Desktop enabled? Any truly bizarre third-party add ons?
>>
>My machine is an Intel 233 w/64 Meg RAM, 1 H-P 1Gig System Disk, 1 Seagate 2Gig D-Drive, Virge S3 Video Adapter. No Network, however a network card is present but not installed. OS is WinNT AND Win98 but I develop in Win98. The NT system is there for one client who has an ongoing VFP5 project he wants developed on NT. The Win98 installation is the first release of the english version in Thailand w/IE4 that came with it.
>** I am going to try swapping out the video card since this has been mentioned before as a possible issue with VFP6 and C***5 errors. **

If you don't have a known, stable card on hand, try switching to the Standard SuperVGA driver in place of the S3 Virge driver - it's stable, and should work with the S3 stuff in general. I've had the fewest problems with Matrox boards and drivers; relatively few problems with ATI except for early releases of the RAGE PRO chipset driver, and the Riva TNT stuff from both Diamond and STB have not been good. The single most stable card/driver combination for me under 98 has been the Matrox Millenium or Mystique 220 PCI cards with Matrox's current driver set.

>
>>(2) How's VFP6 installed? Has VS6 SP1 been installed? Have any updates (like the Setup Wizard update) been applied?
>
>The VFP6 is part of VS6 and all of the MSDN libraries are installed. No service pack is installed. The download takes forever here. No updates.
>** This may be fixed with SP1, I don't know if SP1 addresses these types of problems. **

SP1 addresses some runtime components common to VS, but AFAIK, nothing specific to VFP6 is in the SP1 release. there are significant updates to VFP6 available for download; the Setup Wizard patch at a minimum I would consider mandatory if you use Setup Wizard for all or part of your distribution.

>
>>
>>(3) What makes the error occur? It helps if a specific set of steps causes the error to occur consistently in your environment. Without this, it's like calling your family physician and saying "Doc, it hurts. Please make it stop." without saying where it hurts or how you hurt it.
>
>The error occurs immediatly upon execution of the .exe anytime outside the VFP runtime environment. ie. as an .app or with set step on, no error. The error is not application specific. It happens even when trying to execute an exe built with the application wizard, in other words, it isn't related to something in my framework.
>

OK, then it isn't a generic Win98 problem, since I can run VS6 compiled .EXEs under the VFP debugger on my Win98 box here. My Win98 is updated to reasonably current levels through Windows Update, and includes all patches except for Windows Critical Update facility as of last weekend. I also have IE4 4.72.3110 with the 128 bit cipher support, SP1a and patch 3172 installed.

Base environment: PII/333, 128MB, Adaptec SCSI, 2 4GB Quantum drives, JAZ, ATI All In Wonder PRO AGP w/8MB, CL64 sound, 3C905B/TX NIC on an NT Server domain.

Software: Win98 4.10.1998, updated through MS Windows Update last Sunday.
IE 4 as noted, Active Desktop is running
McAffee VShield
Office 97
Studio 6, SP1
More cr@p than should be running on a development box otherwise


>>
>>Thanks for putting up with an unnecessary screed on my part
>
>Mai Bpen Rai (No problem, Never mind, Forget)
>
>Eric K.