Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!dsinc!netnews.upenn.edu!vax1.cc.lehigh.edu!cert.sei.cmu.edu!krvw From: korpela@stew.ssl.berkeley.edu (Eric J. Korpela) Newsgroups: comp.virus Subject: Re: Norton sd says *NonMovable Blk* (was Curse.exe virus) (PC) Message-ID: <0010.9011081406.AA17159@ubu.cert.sei.cmu.edu> Date: 7 Nov 90 22:58:05 GMT Sender: Virus Discussion List Lines: 29 Approved: krvw@sei.cmu.edu rzi@philpav.tds.philips.se (Roman Zielinski) writes: >I looked a little in my 386-system and noticed that Nortons *sd* reported >a number of areas marked by X, *NonMovableBlks*! > ... >1 was msdos.exe (i localized it to \windows directory (its the *old* > win 2.x-like executive) > ... >The only strange thing is why msdos.exe is nonmovable? The reason that MSDOS.EXE was listed as unmovable is because of a "feature" of Norton's SD that lets you specify files which will not be moved. MSDOS.EXE is, by default, specified to be unmovable. Apparently Norton wanted to be sure that no one has renamed their MSDOS.COM system file to MSDOS.EXE. (Or perhaps he was afraid that future versions of MSDOS would use system files in EXE format). To allow MSDOS.EXE to be moved you must do (from SD) 1) Set Options 2) Unmovable files 3) Remove the stupid filenames It's as easy as that. Removing a file name from the list of unmovable files will not change the file attributes nor will it make system files movable. /\ korpela@sunspot.ssl.berkeley.edu Internet /__\ rioch BKYAST::KORPELA 42215::KORPELA DecNet / \ of Chaos korpela%bkyast@ucbjade Bitnet (_____________________