CONFIG.SYS Absent (AREV Specific)
At 04 MAR 1998 11:09:44AM Victor Engel wrote:
I've seen the recommendation to set FILES=100 in the config.sys. What happens if the CONFIG.SYS file is absent completely? Does one need to be set up, or does Windows 95 handle this situation on an as-needed basis?
At 04 MAR 1998 11:16AM Victor Engel wrote:
Whoops! I meant 200.
At 04 MAR 1998 12:08PM John Duquette wrote:
Victor,
It is my understanding that Win95 allocates ~60 files by default. So you should make one. You also need to add himem.sys and emm386.exe to allow for EMS support.
John Revelation
At 04 MAR 1998 12:35PM Victor Engel wrote:
EMS Support is an interesting thing. It seems that EMS support is provided automatically on Windows 95 for some workstations with no CONFIG.SYS file. Other workstations, however, don't provide EMS support automatically (I can't think of an example at the moment, but I feel sure we've encountered this). Is there some other setting besides PIF settings and CONFIG.SYS that would determine if expanded memory managment is used? Is this provided automatically only on certain Win95 versions?
At 04 MAR 1998 12:56PM Steve Smith wrote:
Victor,
Win 95 handles (!) the memory differently depending on the
build/version. I know that some versions require EMM386
in config.sys while others do not. It was recently
discussed among the PC Magazine beta testing panel in
their forum.
Basically, DOS defaults to 20 files, and opens 5 itself (CON,AUX,PRN,etc.). There is a maximum of 250 (as handles are only ever 8 bits in a standard DOS open call, and DOS uses 5).
Network handles (Novell 4+) in NET.CFG subtract from
the 255 DOS can use. Not sure about NT.
Windows 95 uses its own opening strategy for DOS boxes,
which seems to be around 50. In Windows 32 itself,
using API opens, there seems to be no file resource
restriction.
Hope this helps,
Steve
stsm@ozemail.com.au