|
Please note: Older issues may contain information that is now out of date. How To Subscribe
and Unsubscribe is at the end of this note. Mailing List Trouble? See http://www.langa.com/help.txt Want an easier-to read formatted HTML version? See http://www.langa.com/whats_new.htm (The HTML version of each issue normally is available by 9AM EST [GMT-5] of the issue date.) Please recommend the LangaList to a friend! (And maybe win a Palm III !) The LangaList11-Oct-99 In This Issue:
Fred Does DOSQuick recap of what's transpired so far: Last week, I casually mentioned a few DOS commands that could cleanup some of the garbage files that Windows sometimes won't delete on its own, even if you use the Cleanup Wizard and such. (See http://www.langa.com/newsletters/sept-27-99.htm#temp , http://www.langa.com/newsletters/sept-30-99.htm and http://www.langa.com/newsletters/oct-4-99.htm#wow ) The reader response was very, very eye opening. A significant number of readers had never before booted their system directly to DOS or run their PCs without the graphical interface. I'm probably showing my age (ahem) but it simply hadn't occurred to me that DOS would be so alien to so many people. It's mostly a good thing: a sign that Windows has matured. And don't get me wrong--- I'm glad DOS is essentially dead. But some command-line knowledge is a good thing and can help you get the most from a Windows PC. So, from time to time, Ill devote a column to some DOS-style tips and tricks. If youre an old hand at DOS, I invite your comments, suggestions, and amplifications in the discussion area; if youre new to DOS, I invite your questions. In this way, DOS experts can share their knowledge, and DOS newbies can learn. Done right, we'll all get something out of it! Well start with a look at Autoexec.bat and Config.sys. But to understand them, we need to step back and look at how your PC starts up. (See next item, below.) --------------( Please Visit This LangaList Sponsor!) ------------
--------------(
the above is a paid advertisement )-------------- All personal computers start in
stages: There's just enough special, low-level code permanently stored in the
system BIOS and inside the CPU itself to get the machine going to the point
where the CPU can talk to the hard drive, monitor, etc. Once this tiny amount of
initial code has run, the system then looks on your floppy or hard drive for the
most basic components of an operating system. If it finds them, it loads and
runs them. These core operating system components contain the instructions the
system needs to load the rest of the operating system and to complete the
start-up process. In this piece-by-piece way, your computer self-starts. Computers didn't always start
this way, and a computer that could "pull itself up by its own
bootstraps" was once a novel idea. In fact, when this system of
self-starting was first invented, it was called "bootstrapping," which
later got shortened to "booting." (And that's where that familiar bit
of computer jargon comes from.) Some computers need special
configuration files to boot properly. Different operating systems call them
different names, but the idea is the same: Once the core operating system is
running, but before the full-blown OS starts, it looks for these special files
to see what hardware drivers, software settings, and so on, are needed by the
machine. These special files transform the generic, low-level operating system
into a version that's specific for the machine it's running on. On PCs, two of these
configuration files are called "Config.sys" and
"Autoexec.bat." The former is a text file that can tell the OS what
low-level memory managers, hardware drivers (etc.) to run. The latter is a
series or "batch" of commands that run automatically at startup.
Together, these two files create the software foundation for everything a PC can
do. In the Dark Old Days Of DOS, "power users" often would spend hours
honing and perfecting these files to wring out every last iota of memory and
performance from their PCs. (continued in next item...) Today, some Windows system ship
with no Autoexec or Config file at all. Others ship with a vestigial file thats
either just an empty placeholder, or that contains just a few simple
commands. If you only run Windows applications, that may be fine. But
chances are, even if you think you run only Windows apps, you actually do run
DOS apps from time to time. For example, I use PartitionMagic
and Drive Image to manage disk space and create super-fast-loading backups of my
Windows PCs. Although PartitionMagic and Drive Image have Windows front ends,
they do their real work from DOS! Likewise, some utilities such as
ScanDisk or Norton Disk Doctor sometimes do their work from DOS! And many games still run in DOS,
even if you launch them from inside Windows. What's more, Windows 3x and 9x
are still rooted in DOS: Although many of the OS functions (especially in 9x)
happen "above" the layers controlled by DOS, the old DOS foundation
still is there, and can materially affect how your system behaves. More specifically: The
presence or absence of a properly-done Config.sys and Autoexec.bat can greatly
affect how your OS and apps like these run. And, alas, the generic settings
Windows provides for DOS usually aren't as good as what you can do on your own. In this week's WinMag column,
I'll post specific cut-and-paste examples of ways to set up your Config and
Autoexec files. Because they'll be on web pages, you'll see the examples in the
correct format, and without the weirdness and errors that text-wrapping email
applications may introduce. (I learned my lesson about sending format-sensitive
examples by plain email <grin> See http://www.langa.com/newsletters/oct-7-99.htm#email
) By posting the examples on a web
page, you'll be able to simply copy the properly-formatted content right from
your browser, and paste it into the proper files on your system (I'll tell you
how). Chances are you'll see an instant benefit! What benefit? On a test system
here, my little cut-and-paste trick freed up 11% more "low" DOS memory
than Windows could on its own! This was memory that was totally going to waste!
This low memory is the foundation for all your Win9x and DOS software: DOS apps
usually live entirely inside low memory, and Windows' deepest roots are anchored
there. Making the most of your "low" memory isn't an idle exercise,
and may improve the way your machine runs. So if you want to gain more
"low" memory for free or just learn more about Autoexec and Config
files, click on over to the WinMag site for more info and fully-formatted,
cut-and-paste ready samples. If you're a DOS Expert, please join in to share
your best DOS tips, tricks, batch files, and tweaks. If you're a DOS Novice,
please read the column and then post your questions and comments. Let's help
each other! The column should be live by the
end of business (EDT; GMT-5) on Monday Oct 11th. Look for the link via the
WinMag front page at http://content.techweb.com/winmag/
! Everyone knows what a
"yuk" computer experience is: when a system is frustratingly slow and
seems unable to get out of low gear. But have you ever had a real,
rock-you-back-on-your-heels, Wow moment with a PC? You know, when you saw
something so unexpected or fast or dazzling that you were literally astonished? Readers are sharing their
observations on "wow," "yuk" and the happy middle ground in
between in this week's InformationWeek column and online discussion: Whats
your take? If youre replacing a PC, whats the minimum step up it
takes to feel that you're getting something better? How do you determine the
tradeoff between purely technical needs and the slippery realm of user
satisfaction? Does the Wow effect matter? At what point do you declare old
machines obsolete? What standards do you use for specing new hardware? Join in
the discussion at http://www.informationweek.com/langaletter
! Here, in Microsoft's own words,
is the scoop: "IE 5 includes a
feature called "download behavior" that allows web page authors to
download files for use in client-side script. By design, a web site should only
be able to download files that reside in its domain; this prevents client-side
code from exposing files on the user's machine or local intranet to the web
site. However, a server-side redirect can be used to bypass this restriction,
thereby enabling a malicious web site operator to read files on the user's
machine or the user's local intranet." When this problem first came to
light, the only solution was to turn off all scripting--- a draconian solution.
But now Microsoft has released a patch. It's at http://www.microsoft.com/msdownload/iebuild/dlbhav/en/dlbhav.htm and soon should be available via
the Windows Update site as well: http://windowsupdate.microsoft.com If you'd like more info, see http://www.microsoft.com/security/bulletins/MS99-040faq.asp But in general, if you're running
IE5, I recommend you grab this patch ASAP. -------------(
Please Visit This LangaList Sponsor!) ------------
--------------(
the above is an advertisement )-------------- All Bill had to do was recommend
the LangaList to a friend using the form at http://www.langa.com/recommend.htm#2
Once a month or so, I draw one
name, at random, from among those who have used the recommendation form, and
award a prize. (Note that this isn't some big-company sweepstakes: It's just my
informal way of saying thanks for your help in spreading the word about this
newsletter.)
Of course, if you don't want a
shot at winning a book, you can try for a Palm III organizer via this link
instead: http://www.langa.com/recommend.htm#1
(Full details on both giveaways
are available via the links.)
If you think the LangaList is a
worthwhile read, just use the link above to recommend the LangaList to a friend.
Your friend just may find a new source of useful information; I just may gain a
new subscriber; and you just may win a prize! Either way, thank you, and good
luck! Last week's newsletter that
listing a wide range of files that usually are safe to delete (see http://www.langa.com/newsletters/oct-7-99.htm#more
) generated lots of mail. Much of it was in the form of "I have a group of
files [name of file type here]; is it safe to delete them?" Here's how you can find out on your own if a file (or files) is safe to
delete--- and this actually is a method we've discussed in past
newsletters: One way is simply to make a full
backup before you do any serious pruning of your files. If it turns out you
deleted something you need, restore the needed file from the backup. Simple! Or: Change the name of the
suspect file to something obvious and memorable, and run your system for a
while. For example, say you have a file somewhere on your system called "importantlooking.dll"
and you'd like to know if you can delete it: Rename the file to something like
"importantlooking.test" and run your PC for a while. If you have
problems or get a message that says something like "File missing" or
"cannot find importantlooking.dll" then you know the file actually is
useful. Rename it back to "importantlooking.dll" and move on. But after a while, if nothing bad
happens, just delete "importantlooking.test" and you're done. Easy! The LangaList has readers
worldwide. Nico van Tonder from Zaire sent in this piece of prose, which he
points outs is spelled perfectly: Eye halve a spelling
chequer
--------------( the above is an advertisement )-------------- See you next issue!
Best, (Please recommend the LangaList to a friend! (And maybe win a Palm III) An easier-to read formatted HTML version is available in the "what's new" section of http://www.langa.com. (The HTML version of each issue normally is available by 9AM EST [GMT-5] of the issue date.) All past LangaList issues are also available via the same link.
Why are you getting this newsletter? There are only two ways to get on the list (direct email request or via the WinMag mail list signup page) so if you're getting this newsletter; your name came to me through one of those channels. SUBSCRIBE (it's free!):
Send email to subscribe-langalist@lyris.dundee.net About the advertisers: Each item marked "the above is a paid advertisement" is just that: a paid ad. Although Langa Consulting LLC will never knowingly accept advertising for a fraudulent product, company or service, Langa Consulting LLC makes no implied or explicit warranty, recommendation or endorsement of or for the products, companies or services mentioned in the ads. Treat these ads as you would any other ad in any other medium. Disclaimer: The tips and other information given in the newsletter are researched and are as accurate as possible. However, due to the many variables of hardware and software brand, size, type, age and configuration, plus the vagaries of user knowledge, skill level and usage accuracy, Langa Consulting LLC makes no assertion, warranty or guarantee that all the information here will work on all systems and for all users, all the time. If you're not sure of the applicability or suitability-to-task of any advice, tips, etc. given here, or are uncertain of your own ability to perform a described task, seek additional help or information before proceeding. In any case, all information herein is offered as-is and without warranty of any kind; neither Langa Consulting LLC, nor its employees nor contributors are responsible for any loss, injury, or damage, direct or consequential, resulting from application of any information presented here. This newsletter is a free service of Langa Consulting LLC and is Copyright © 1999 Langa Consulting LLC. All rights reserved. |
|
Please note: Older issues may contain information that is now out of date. |