Date:	Fri, 23 Feb 1996 13:16:25 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To:	"A.Appleyard" <A DOT APPLEYARD AT fs2 DOT mt DOT umist DOT ac DOT uk>
Cc:	DJGPP AT sun DOT soe DOT clarkson DOT edu
Subject:	Re: Finding which files are opened
In-Reply-To:	<377F1BB6C2A@fs2.mt.umist.ac.uk>
Message-Id:	<Pine.SUN.3.91.960223130915.2693I-100000@is>
Mime-Version:	1.0

On Fri, 23 Feb 1996, A.Appleyard wrote:

>   Related to interrupts if not directly to djgpp. My Windows for Workgroups
> takes an excessive time loading and starting, with long continuous C: hard
> disk access noise. None of this is reading or writing the Windows swop file
> (386spart.par), which is now on my D: hard disk, and I can distinguish D: hard
> disk accesses by the different noise (probably caused by the acoustics of the
> inside of my PC's casing).
>   So, to help in this and likely in much other debugging: Please has anyone
> out there got a program that will drop a TSR that hooks the open-a-file
> interrupt so that all file openings after that are recorded on a log file? Or
> what do I need to write one for myself? That way I can refer to it afterwards

Be warned that if WfW is using the 32-bit File Access (check it in the 
Control Panel / Virtual Memory), then DOS is bypassed almost completely 
in everything that involves file operations, so writing a DOS TSR to 
catch file I/O will be a useless exercise: it won't catch anything 
interesting.

I'd advise to check these:

	1) You use 32-bit File Access, but didn't set the disk cache to a 
proper size (also from the Control Panel).  If you have a lot of memory, 
make it larger, if you have less then 8 MB of memory, make it smaller.  
(You will also need a permanent swap file for 32-bit File Access.)

	2) You DON'T use 32-bit File Access, and you don't have any disk 
cache installed.

	3) You have a resident antivirus which checks every DLL Windows 
loads.

- Raw text -