PCBUILD Archives

Personal Computer Hardware discussion List

PCBUILD@LISTSERV.ICORS.ORG

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Tom Turak <[log in to unmask]>
Reply To:
PCBUILD - Personal Computer Hardware discussion List <[log in to unmask]>
Date:
Thu, 29 Mar 2001 18:50:27 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (62 lines)
I am curious as to what you are doing, but an explanation is not necessary.
Instead, here's some advice.  Don't trust the error message.  It may not be
generated by win.ini.  It could be a missing line in config.sys or
autoexec.bat
or system.ini, to name a few.  it could be that the file is not missing from
the 2nd computer, or the loading sequence for the culprit programs is
correct
on one and incorrect on the other.  Several widely distributed TSR's were
actually
several programs that needed to be loaded into memory in the correct
sequence.
What is a TSR?  The most common one still in wide use even with Win9x is
probably MSCDEX.EXE.  Most people associate them with hot-keys, but what
they
really do is chain themselves to standard routines that are associated with
an
event.  When the event occurs, they wake up and run first, then decide
whether
the standard routine should also be run, before returning the pc to the
state
it was in just before the event. The event doesn't have to be user
interaction,
although the best known examples are programs that responded to pressing
certain key combinations, or hot-keys, like shortcut keys in windows.  32
bit
programming pretty much put a stop to any of the big uses for TSRs, which
were
extending DOS (mscdex), task switching (popup windows), background
processing(print spoolers),
and transparancy ( a lot of tsr effort went toward convincing programs that
were hardcoded to only deal with the bios or hardware that they were calling

standard routines when in fact they were interacting with user written
routines.)
In the 16 bit microsoft windows 3.1, these could be loaded from win.ini or
system.ini,
as well as config.sys or autoexec.bat.  Some soundcards and modems would put
statements
in all four.
Tom Turak

-----Original Message-----
From: Carl Barnhart [mailto:[log in to unmask]]
Sent: Wednesday, March 28, 2001 8:14 PM

When windows 98 is loading, right before the network login window appears,
an
error is brought up that says "Missing TSR File, please check win.ini". As
strange as it may sound this is the desired effect at the moment. However, I
don't know what a TSR file is. I want to get the same error to occur on
another computer (the exact same computer in everyway) in the same network
so
I copied the win.ini file of the computer that has the error, to the
computer
I want the missing TSR file error to appear. That did not change a thing and
I failed to get the missing TSR file error. Any help or understanding what a
TSR file is would be greatly appreciated.

            Do you want to signoff PCBUILD or just change to
                    Digest mode - visit our web site:
                   http://freepctech.com/pcbuild.shtml

ATOM RSS1 RSS2