Xref:	news2.mv.net comp.os.msdos.djgpp:1507
From:	76633 DOT 47 AT compuserve DOT com (W.Jackson)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Finding which files are opened
Date:	Wed, 28 Feb 1996 08:07:31 GMT
Organization:	CompuServe Incorporated
Lines:	23
Message-ID:	<4h13nn$8bu@dub-news-svc-3.compuserve.com>
References:	<377F1BB6C2A AT fs2 DOT mt DOT umist DOT ac DOT uk>
NNTP-Posting-Host:	dd73-024.compuserve.com
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

"A.Appleyard" <A DOT APPLEYARD AT fs2 DOT mt DOT umist DOT ac DOT uk> 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
>and find what my Windoze or whatever has been so busy reading.

Might try a simpler solution. At prompt load Windows with     

C:\>WIN /B

This causes Windows to create a boot log (text file) listing exactly
which files its loading while coming up.  Its MUCH easier than
reverting to interrupt hooks.

- Raw text -