This isn't really about any "problems;" just informational...
With the right settings, you can choose your own minimum and maximum sizes for the disk cache, for example.
KB articles Q140678 and the revised Q108079 say that the following is valid for win95 at least:
If not present, create the file "system.ini" (yes, win95 still recognizes it. It didn't die with 3.x) in your windows directory.
Create a section [vcache] if it's not already there, and add the following entries:
Reboot, and that's it.
You can use System Monitor to verify that the new settings are working.
You must run NTFS to have ACLs, or anything beyond the simple R/O, hidden, archive, and system attributes.
No NTFS, no filesystem security. And here's the fun part: even so-called MS "experts" frequently recommend that NT be installed that way to ease emergency recovery from a DOS boot.
And then there are network "holes" like the following:
How about the port 80 hole; telnet to port 80 and type: get ../..
or the samba hole; send the following message to the SMB server on the remote NT box: DIR..\
Or how about this one:
Telnet to port 135 or 1031, after you get the confirmation you conected to the port send several lines of text and disconnect. (many ports on NT are vulnerable to this little one). The CPU of the target machine will reach max utilization QUICKLY!