Thanks for the information Ed.

I will give this a try on some machines and see if the problem goes away....



>-snip-
>
>>So far, I have not found much, but I am leaning toward some problem with the configuration of temp files in the workstations.
>>
>>Here are some examples of configuration files I am using:
>>
>>Config.sys
>> device=c:\windows\himem.sys
>> device=c:\windows\emm386.exe noems novcpi
>> dos=high,umb
>> files=255
>> buffers=32,0
>> numlock=on
>
>In Win95, you're really hurting yourself badly trying to use CONFIG.SYS to control your memory environment. My advice here would be to cut your CONFIG.SYS down to:
>
> files=255
> numlock=on
>
>and then let Win95 make decisions about EMS and VCPI allocations. You can control the availability of EMS and VCPI memory for DOS-based applications from the Property sheet of the MS-DOS prompt or shortcut used to fire a DOS program. By default, Win95 will load HIMEM.SYS and will make EMS/XMS/VCPI memory available to DOS programs as needed - the need to allocate space for UMBs in memory for TSRs and working buffers, which you're trying to do with EMM386, really isn't necessary unless you run into a conventional memory ceiling running specific DOS apps. Don't bother specifying buffers, either - it's only significant when loading Win95, and if the number is tool large for the DOS version, will grab memory from the HMA, where DOS would otherwise relocate other things, and as a result will decrease available conventional memory. Unless you have hard drives running in DOS compatibility, the DOS VM talks to a protected mode driver anyway.
>
>-snip-
>
>hth,
>
>Ed