>>What SP of W2K are you running? (SP 2 & 3 fixed some IDE caching problems for some people.) Are these files local or on a network? Since .SCT files (half of the Screen file pair) are often targets of viruses / worms, are you running a virus checker? Have you got a copy of these files before they may have been infected?
>
>Rick,
>
>I'm running W2K build 2195 with SP2
>No network is connected.
>I removed McAfee anti-virus software pre-installed with my HP XE Omnibook
>so there is no anti-virus software.
>
>I specify a new file to modify report command so this cannot
>be a screen file corruption.
>
>I use E4M disk in my computer as I: drive.
>
>TEST RESULTS (MODIFY SCREEN NEWFILE) :
>
>1. IF E4M disk is not installed, and FOXPROW startup directory is in C:\
>all is OK.
>
>2. IF E4M disk is installed but FOXPROW default directory is C:\ , sometimes FOXPROW vanishes without error, sometimes illegal operation error occurs:
>
>FOXPROW caused an access violation inntdll at 0x77fcb375
>Click on CLOSE to terminate the application
>Click on IGNORE to continue, you should save your work in a new file.
>
>After clicking Ignore the same message appers again, but
>address is 0x77fcb937
>
>After clicking ignore again, the same message with same location
>0x77fcb937 appers.
>
>After clicking Ignore third time, foxprow vanishes without any message.
>
>Clicking Cancel seems not to cancel application, same message appers again and again.
>
>After running fxoprow again and typing modify screen newfile, foxprow vanishes without any messages.
>
>3. IF E4M disk is installed and FOXPROW default directory is in E4M disk,
>FOXPROW vanishes after MODIFY SCREEN newfile without any message.
>
>However, some time ago this works OK.
>I think there is some setting in W2K which stops FOXPROW from working with E4M but I have no idea what setting.

Rather than use E4M, maybe you could use Windows 2000's native Encrypting File System:
http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B230520