Subj : "stuck" open files To : Rich Wonneberger From : Mike Luther Date : Mon Aug 15 2005 10:51 pm Rich .. This reply is being written remotedly on a FP17 box. The file is: 10-10-03 3:57p 137469 0 DOSCALL1.DLL But watch out! Here is a perfect example of how things move forward in this critical world. On the R40 with the brand new install of the MCP2 latest and Fix Pack XRC_-05 that is on it you find: 12-29-04 11:15a 137601 0 DOSCALL1.DLL Now what you have to understand is that all this does tie together to applicable kernel levels, as produced in installs and Fix Packs. It also can be involved in further kernel development after the latest Fix Pack. There is a discussion now going on more or less in the forums about additional failures in the DLL, even now. Form memory here remotely, that issue is of focus on the latest Mozilla 1.1.8-10-11 operations. I've got a pile of failures with even this .DLL in research work on the MOZ stuff here. And if my memory is correct, though I personally don't know this for sure. There are at least sixteen internally merged DLL's in PMMERGE.DLL, which is closely related to all this too! Even, as I recall this remotely, People running the latest XRC_05 on MCP2 are seeing related failures that may involve DOSCALL1.DLL and it has been advocated by some, that you may need to retro the latest PMMERGE.DLL to stop some of this instability! 7-16-03 6:51p 1269677 49 PMMERGE.DLL That's the file on the FP17 box this is being written on. Note that on the installed XRC-05 R40 debug box it is: 12-29-04 7:33p 1270499 49 PMMERGE.DLL See the probme as all this comes to focus? And .. If you want to see the retrograde PMMERGE.DLL, you'll have to wait until I can get to stabilized XRC-05 boexes in the relay rack pile of big hardware boxes to show you the comparison between the variations there! Does any of this help? Mike - Remotely from Mssr. Picollo via comm port to 1:117/3001 --- Maximus/2 3.01 * Origin: Ziplog Public Port (1:117/3001) .