Original Sender : "DasaMan" <[EMAIL PROTECTED]> --------------------------------- From: Fred Langa <[EMAIL PROTECTED]> > The LangaList > 30-Sept-99 > > A Free Email Newsletter from Fred Langa About BrowserTune, > HotSpots, Columns, Tips & Tricks, and Other Activities > > In This Issue: > Internet Explorer Bugs and Security Problems > What To Do With Your Old PC > Return Of The Amigans! > Part 1: More On Temp File Deletion > Part 2: More On Temp File Deletion > Part 3: More On Temp File Deletion > If Everyone Hates Snoopware, Why Is It In Use? > Some Days, It's a 300 to 1 Ratio! > Cool Software > Just for Grimaces > Just For Grins > More! > > >>>Internet Explorer: Bugs or "Security Vulnerabilities?" > >OK, it's time for semantic clarity: A "bug" is a software >coding error that causes inappropriate or unexpected >behavior, usually of the bad sort (crashes, etc.). > >Analogously, a "bug" in a new car might be a misaligned >wheel, a radio that doesn't work, a tendency to stall; etc. > >A "security problem" isn't necessarily a bug, although it >may be. Using the car analogy, if someone else's keys can >open your car, that's a bug. But if your car is "vulnerable" >to someone getting inside by smashing the windows with a >rock or cutting through the roof with a metal saw, that's >not really a bug--- the problem isn't necessarily in the >design or manufacture of the car, but in the malicious >behavior of others. > >However, with software, all problems often get lumped >together as "bugs," even when they're not really the >vendor's fault. On the flip side, software vendors often >like to speak of "issues" and "vulnerabilities," and hardly >ever just come out and say: "We screwed up. It was a bug." > >Like all software, Microsoft products have bugs. But because >they're in the widest use, Microsoft products also get >attacked and hacked more often than any other products. > >Using the car analogy again: More cars get stolen in cities >than in the country. That doesn't mean that car locks on >urban cars are worse or are more poorly designed than those >on rural cars; it's just that there are more car thieves at >work in the cities. > >I offer this not to make excuses for Microsoft, but to offer >perspective: Every time I report on a problem with a >Microsoft product, I can count on getting mail from some >readers claiming it proves how ratty MS products are. > >Sometimes, they are ratty. But other times, the seemingly >high percentage of Microsoft-related problems stems simply >from the fact that there are far more people trying to make >Microsoft products fail than any others. > >This week's security news from Microsoft shows both side of >the equation: Some of these are bugs; some are problems >caused by the malicious behavior of others. You can decide >for yourself whether it's a sign of Microsoft ineptitude or >of the bad behavior of others. > >>>THE IMPORT/EXPORT FAVORITES PROBLEM > >A malicious person can use Internet Explorer's "Import >Favorites" (that is, bookmarks) option to load bad things on >your PC if you choose to import their Favorites list. Along >with the imported URLs, you may get pointers to malicious >code. > >One solution is simply not to share Favorites with people >you don't know. Or, you can download a patch Microsoft has >posted; the patch also corrects a bug in some ActiveX >controls, so it's a kind of two-in-one deal. > >You'll need different patches depending in which flavor of >IE you're running. Best bet is to click over to a FAQ page >and figure out which patch you specifically need: >http://www.microsoft.com/security/bulletins/MS99-037faq.asp > >>>THE IE5 DOWNLOAD BEHAVIOR PROBLEM > >A clever hacker can use something called a "server-side >redirect" to fool your browser into exposing files on your >system that should not be accessible. BigFix.Com ( >http://www.bigfix.com ) first brought this to light; >Microsoft responded by saying that yes it's true; they're >working on a patch; and for now, the only way to prevent >this problem is to turn off Active Scripting. Yikes--- >that's a draconian measure. > >There's no patch yet, but I'll let you know when it arrives. >Meanwhile, if you're wondering if you should turn off your >active scripting or not, here's a FAQ and info on the >workaround: > >http://www.microsoft.com/security/bulletins/ms99-040faq.asp > > >What To Do With Your Old PC > >This newsletter---and indeed every bit or byte that I send >out via the Internet---gets to you via a fossil, almost- >decade-old PC: a 1991 vintage 486 with just 16MB of RAM. > >I'm not a masochist; it's not the machine I work on. But >that lowly box has ample power to perform the simple task of >Internet connection sharing. I use it as such---as an access >server--- to share a single Internet connection among the 7 >machines here. The PC is set up with a Windows "compact" >installation (so no frills, bells or whistles are loaded) >and essentially runs just one small application: Sygate. > >Sygate lets all the machines on my local network share the >same connection. It's a cable modem in my case, but it could >be any type of connection, including dial-up. It also serves >as a firewall, keeping potential intruders out of my >machines and off my LAN. (BTW, there's a new version of >Sygate out; I'm trying it now and will let you know how it >fares. More info: http://www.sygate.com ) > >The cash value of that 1991 PC is near zero--- some of the >parts could be re-used, but essentially, it's a high-mileage >junker that's unfit for today's mainstream apps. Yet, I'm >getting great ongoing service out of it by using it as an >access server. > >That's just one of the dozen different ways I discuss in >"What To Do With Your Old PC;" the column (and discussion >area) that's live right now at >http://www.winmag.com/columns/fred/1999/0927.htm > >Come get all the details, and then join in the discussion! > > >Return Of The Amigans! > >Last week, I wrote about how Gateway 2000 was tap-dancing >about the future of the Amiga--- a storied machine that >generates such fierce loyalty that some Amigans can make >MacFanatics or rabid Linuxen look positively tame. > >Gateway bought rights to the Amiga a couple years ago, and >not much happened until this last summer. But just as it >appeared Amiga was going to rise from the grave (OK, it >never really died; but it was awfully close) Gateway >announced that the Amiga "wasn't really about a box." > >Instead, Gateway issued a statement that Amiga was simply >about "a better way" and that some kind of reconstituted >Amiga---one that wasn't exactly hardware and wasn't exactly >software---would be everywhere; on every OS and platform. >Huh? > >I was deeply dubious, and said so in this month's Byte >column. It seemed to me that Gateway had chickened out about >actually building new Amiga boxes and was trying to weasel >out of its past promises by redefining what was an Amiga >into something so vague and nebulous they could claim to >have shipped "an Amiga" by shipping almost any piece of >hardware or software. > >A lot---and I mean a *lot*---of Amigans felt likewise. The >column was picked up by Amiga organizations worldwide, and >Amigans have flooded Byte's discussion areas. > >It's fascinating reading: Come get the full story at >http://www.byte.com/column/BYT19990922S0004 and then join in >the discussions, which are available two ways: > >The best way (in my opinion) is to use your newsgroup or >Usenet reader (Outlook, Free Agent, etc.) and click on over >to news://news.cmpnet.com/cmpnet.byte.monitor > >Or, you can join in via a standard web browser at >http://www.byte.com/nntp/monitor . > >I prefer the newsgroup version because I find that newsgroup >readers do a better job of displaying the threads; plus, if >you post a message, your email client will handle the >posting for you, and that usually means you have the benefit >of a spell checker and such--- notably absent in the web >interface. > >But either way, join in and see what's up among the >vociferous and worldwide Amigan community! > > >More On Temp File Deletion, Part 1 > >In the last issue, I told you about a little batch file I >use to clean up the TEMP directory, which can get quite >large if left unattended. (See >http://www.langa.com/newsletters/sept-27-99.htm#temp ) > >Several readers had questions or even better ideas. Here are >three example letters: > >Reader Don Graves writes: > Hello Mr. Langa: > I followed your instructions but, my > Prompt is " C:\Windows> " and typing > 'cleanup' indicates a bad command.... > >Type whatever directory the file is in in front of the file >name: For example, if you put the file "Cleanup.bat" in the >c:\ directory, just type c:\cleanup.bat . > > >More On Temp File Deletion, Part 2 > >Reader Michael Murphy suggests an alternative Cleanup.bat >that will work no matter where your TEMP directory is >located. (The default is c:\windows\temp, and that's what I >used in my example. But it can be located elsewhere; and >some systems also have a TMP directory, which is simply an >alternate name for TEMP.) > > I just got your LangaList & read the article about > the temp cleanup batch file. We've encountered > this a few times at work & I thought I'd suggest > an alternative. > > c:\windows\command\deltree /y %temp%\*.* > c:\windows\command\deltree /y %tmp%\*.* > del %temp%\*.zip > del %tmp%\*.zip > del %temp%\*.exe > del %tmp%\*.exe > > It's arguable really since most people will be > pointing to the directory that you reference, > however, I've got my temp directory on a different > drive & thought you might find this an interesting > alternative. The newsletter is great & I look > forward to reading it. Keep up the good work. Have > a great day! ---Michael Murphy > > >More On Temp File Deletion, Part 3 > >Anthony Cassinelli suggests this automated method of >cleanup: > > In your LangaList 27-Sep-99 under the "cleaning Up > Temp Files" I was faced with the same problem. > Problem for me was I would sometimes forget to > cleanup the temp files area. Came up with a few > lines that I inserted into my AUTOEXEC.BAT file. > This way I am reminded every time I start or > reboot my system & if I'm not around it will > automatically bypass the delete. Obviously I could > add more DELTREE lines (if needed) or make this a > separate file & use a @CALL function. > I placed these lines at the bottom of my > AUTOEXEC.BAT file. Hope it helps. ---Anthony > > @ECHO OFF > CLS > CHOICE /T:N,10 Remove files from temp folder > (D:\TEMP\*.*) [Default = N] > if errorlevel=2 GOTO NO > if errorlevel=1 GOTO YES > :NO > REM - Proceed to END without processing > goto END > :YES > ECHO "Deleting all files in TEMP folder..." > DELTREE /Y D:\TEMP\*.* >NUL > goto END > :END > >Yet another automation method is to use Windows Task >Scheduler, and tell Windows to run Cleanup.bat at some point >when you're absolutely, positively certain there will be no >apps, open files or installs that may be using the TEMP >directories---say Monday mornings at 2AM, or some equally >gawdawful time. 8-) > >Thanks to all who wrote in! > > >If Everyone Hates Snoopware, Why Is It In Use? > >Most people posting in the discussion on Snoopware--- >applications that monitor your actions on a PC or LAN---seem >to hate that kind of software. But it's still in use all >over the place. Some of this software runs invisibly; you >may be being monitored even down to the level of your >individual keystrokes and not even know it! For lots more >information on this contentious issue, check out the column >and then join the lively discussion >http://www.informationweek.com/langaletter ! > > >Cool Software > >I've been test driving "ShutDown Plus," a nice app from WM >Software ( http://www.wmsoftware.com/ ). It can run whatever >programs you want at shutdown, and run them either at every >shutdown, or once a day at shutdown, or on an arbitrary >schedule (say, once a week at shutdown). It's actually a >nice way to perform some maintenance tasks, including >periodic wiping of the TEMP files. (See discussion above.) > >But there are freeware apps that run programs at shutdown. >ShutDown Plus's, er, plus is that it also can automatically >shutdown/restart your PC at preset times. I use it in conjunction >with a pile of normal weekly maintenance chores that automatically >run late Sunday night and into Monday morning: My system wipes out >its TEMP and similar files, runs ScanDisk, Aligns and then >Defrags everything. Then, Shutdown Plus reboots the system >so when I sit down to work Monday morning, the system is >solid, clean, and probably readier for the workweek than I >am! 8-) > >You can try ShutDown Plus free for 30 days via the above >link; if you like it, it costs $35. > > >Just for Grimaces > >Thanks to the many readers who wrote to tell me that last >week's "Humanity, I weep for thee" item in Just For Grins >was (ahem) appropriated without attribution by the reader >who sent it to me. The original source appears to have been >none other than Scott Adams (of Dilbert fame; >http://www.comiczone.com/comics/dilbert/ ). > >I love the Dilbert strips; and I despise plagiarism. My >apologies to Scott Adams. And please: If you're going to >send me a bit of humor and have lifted it from another >source, please let me know where it came from. Thnx! > > >Just For Grins > >Several people sent me versions of this "Decoding Windows >Error Messages." If anyone can tell me the original author, >I'd be happy to offer attribution... 8-) > > WinErr: 000 Not Errors found [Retry] [Reboot] > WinErr: 001 Windows loaded - System in danger > WinErr: 002 No Error - Yet > WinErr: 003 Dynamic linking error - Your mistake > is now in every file > WinErr: 004 Erroneous error - Nothing is wrong > WinErr: 005 Multitasking attempted - System > confused > WinErr: 006 Malicious error - OS/2 found on drive > WinErr: 007 System price error - Not enough money > spent on hardware > WinErr: 008 Broken window - Watch out for glass > fragments > WinErr: 009 Horrible bug encountered - God knows > what has happened > WinErr: 00A Promotional literature overflow - > Mailbox full > WinErr: 00B Inadequate disk space - Free at least 80MB > WinErr: 00C Memory hog error - More RAM needed. More! More! More! > WinErr: 00D Window closed - Do not look outside > WinErr: 00E Window open - Do not look inside > WinErr: 00F Unexplained error - Please tell us how this happened > WinErr: 010 Reserved for future mistakes by our developers > WinErr: 011 Window open - Do not look outside > WinErr: 012 Window closed - Do not look inside > WinErr: 013 Unexpected error - Huh ? > WinErr: 014 Keyboard locked - Try anything you can think of. > WinErr: 016 Unable to exit Windows. Try door ! > WinErr: 018 Unrecoverable error - System has been > destroyed. Buy a new one. Old windows license is not valid anymore. > WinErr: 019 User error - Not our fault. Is Not! Is Not! > WinErr: 01A Operating system overwritten - Please > reinstall all your software. We are terribly sorry. > WinErr: 01B Illegal error - You are not allowed to > get this error. Next time you will get a penalty for that. > WinErr: 01C Uncertainty error - Uncertainty may be > inadequate. > WinErr: 01D System crash - We are unable to figure > out our own code. > WinErr: 01E Timing error - Please wait. And wait. > And wait. And wait. > WinErr: 020 Error recording error codes - Remaining errors will be lost. > WinErr: 021 Error displaying error message. You > cannot see this error. > WinErr: 026 Error - Your computer is too fast for > Windows. Decrease the speed of your computer. > WinErr: 042 Virus error - A virus has been activated in a DOS-box. The > virus, however, requires Windows. All tasks will automatically > be closed and the virus will be activated again. > WinErr: 049 Cannot open Windows - Bugs will come in. > WinErr: 055 Hard disk full. Windows cannot write a > swap file. Buy another hard disk. > WinErr: 056 CPU is too tired to continue > WinErr: 057 Processor meltdown. Too hot inside a computer. > WinErr: 077 Joystick not found. Please click joystick button 1 to continue > WinErr: 078 Keyboard not found. Please press F1 to continue > WinErr: 079 Mouse not found - A mouse driver has > not been installed. Please click the left mouse button to continue. > WinErr: 678 This will end your Windows session. Do > you want to play another game? > WinErr: 683 Time out error - Operator fell asleep > while waiting for the system to complete boot procedure. > WinErr: 703 Error exiting Windows. System does not > fit through that window. A window with a size 169 Mb is needed. > WinErr: 815 Insufficient Memory - Only 64,312,583 Bytes available > WinErr: FFF Error buffer full - Windows cannot > display any more error messages. > >See you next issue! > >Best, > >Fred > >([EMAIL PROTECTED]) > >Disclaimer regarding the suitability-to-task of the advice in the newsletter: 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 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 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, 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 and is Copyright � 1999 Langa Consulting. All rights reserved. Zerosig ---------------------------------------------------------------- Compu-Mania MailingList is provided by PT Centrin Utama Maintained by : [EMAIL PROTECTED] To Post a msg : Send mail to [EMAIL PROTECTED] To Unsubscribe : Mail to [EMAIL PROTECTED] BODY : unsubscribe Compu-Mania For more information, send mail to [EMAIL PROTECTED] with "HELP" in the BODY of your mail (without quote). ----------------------------------------------------------------
