Path: utzoo!attcan!uunet!wuarchive!zaphod.mps.ohio-state.edu!swrinde!ucsd!ucbvax!bloom-beacon!eru!hagbard!sunic!philpav!rzi From: rzi@philpav.tds.philips.se (Roman Zielinski) Newsgroups: comp.windows.ms Subject: Re: Re;"Curse-virus" orig.article Summary: about non-movable blks Message-ID: <501@philpav.tds.philips.se> Date: 6 Nov 90 08:34:18 GMT References: <90305.084851LK-AP@finou.oulu.fi> <1990Nov3.022808.6903@ivucsb.sba.ca.us> Organization: Philips TDS, Stockholm, Sweden Lines: 36 It has been some discussions about curse.exe. One of them was about the *unmovable* blocks as reported by norton's *sd*. I made some investigations on my 386SX (Award bios) and found that indeed there was four non-movable areas on my disk. - io.sys (the old boot friend) - msdos.sys (one more old boot friend) - \windows\msdos.exe (Why non-movable? Que?) - garbage from crashed win-session (could be removed by *chkdsk /f *) Now something very *funny*: If I rename \windows\msdos.exe to msdos1.exe it ceases to be non movable! When I rename it back to msdos.exe it is non-movable again. I compared the file with the original on distribution disks and did not find any strange things. (NB You must uncompress them by *expand.exe*, also on win3.0 distribution disks). One more strange thing is that my other 386-system (=Philips 3345/100MB+386SX which has almost the same software, but another HW and BIOS did not have the same behaviour (ie on unmovable blks) ****** can someone explain what's going on? ******* Tanks, Roman +-------------------------------------------+ _--~--_ | Roman M. Zielinski | ---- / \ ---- | Philips Tele & Data System AB | ---- ( |^^^| ) ---- | S-115 84 Stockholm, Sweden | ---- \ \ / / --- | tel +46 8 782 1373 | |=====| +-------------------------------------------+ |=====| | NET ADDR: rzi@pav.tds.philips.se | |=====| +-------------------------------------------+ ~~U~~