Tom
Sorry, I didn't get back to you soon. Thanks for the suggestion.
That sure is a lot of work but my client has determined that the
install diskettes were corrupt.
Alleluiah!
Luis
>Luis
>
>You should know the routine by now (said the Drill
>Sargent),
>strip the Config.Sys & Autoexec.Bat (copies) to
>their lowest
>level & start adding lines to them until it
>crashes. I know
>it's a pain in the butt. But you will be
>reasonably sure
>what happened.
>
>Also, sometimes it takes a combo of 2 or 3
>programs to reproduce an error. The one program
>by itself
>(suspected culprit) will not always cause the
>crash -- Ain't
>life interesting!?!?!
>
>Happy Hunting
>Tom
>
>>
>>I have a user running an FP26 .EXE on a 386
>>Windows enhanced
>>with 4 meg RAM. Whenever he runs the EXE, he gets
>>an error
>>"FoxPro has caused a page fault in Module
>>FOXW2600.ESL at
>>0001:05C4".
>>
>>User faxed me a copy of his CONFIG.SYS,
>>AUTOEXEC.BAT, and
>>memory status using MEM /C DOS command. All his
>>TSRs are
>>stored in conventional memory which includes
>>EMM386, win386,
>>RAMBOOST, and DPROTECT. RAMBOOST and DPROTECT are
>>files
>>associated with PCTOOLS software and they are
>>stored
>>respectively on CONFIG.SYS and AUTOEXEC.BAT.
>>
>>I suspect that the PCTOOLS files are causing the
>>error, but
>>I need to verify. A prompt response would be
>>greatly
>>appreciated. Thanx.
>>
>>
>>Luis Antonio
>>julie@isacorp.com
>>
>
Previous
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only