davidg@uns-helios.nevada.edu (Davig Gonzales) (10/19/89)
--------------------- Hello, I am having a bit of a problem understanding the use of Speed Disk (SD) under Norton Utilities 4.5. I can use the program without too much trouble but my hard disk is slowly being filled with files that cannot be moved (the X's in SD disk map). My question is, what can cause the creation of these files and how does one get rid of them? The manual made mention of copyprotected software but I am running only non-copyprotected software or programs that were developed elsewhere. Thanx, David A. Gonzales -----------------------------
jwbirdsa@phoenix.Princeton.EDU (James Webster Birdsall) (10/19/89)
In article <927@unsvax.NEVADA.EDU> davidg@uns-helios.uucp (Davig Gonzales) writes: > I am having a bit of a problem understanding the use of Speed Disk >(SD) under Norton Utilities 4.5. I can use the program without too much >trouble but my hard disk is slowly being filled with files that cannot be >moved (the X's in SD disk map). My question is, what can cause the creation >of these files and how does one get rid of them? > David A. Gonzales I had a problem very much like this; on one of my disks, a huge hunk of space was marked unmovable despite the fact that it wasn't a bootable disk, nor was I using any copy-protected software. After a couple of weeks of looking at this off and on and vaguely wondering what was going on, I realized that it was a huge file that I'd made hidden in order to keep it from appearing in DIR. I changed the attribute back to visible and the X's disappeared. Apparently SD assumes that any file or directory with odd attributes probably should be left alone (which isn't a really unreasonable assumption). It sounds like some program you have is creating hidden files. Hope this helps. -- James W. Birdsall jwbirdsa@phoenix.Princeton.EDU jwbirdsa@pucc.BITNET ...allegra!princeton!phoenix!jwbirdsa Compu$erve: 71261,1731 "For it is the doom of men that they forget." -- Merlin
kens@hplsla.HP.COM (Ken Snyder) (10/20/89)
I've noticed that my system also developed unmovable files but on closer examination they all turned out to be the data/log files for some of the games I had on my system. I have no idea why they were marked as non- movable but I reset them using SD and let them be moved and everything still seemed to work. I think some software simply marks files incorrectly. Ken
austin@bucsf.bu.edu (Austin Ziegler) (10/20/89)
>>>>> On 19 Oct 89 17:39:25 GMT, kens@hplsla.HP.COM (Ken Snyder) said:
Ken> I've noticed that my system also developed unmovable files but on
Ken> closer examination they all turned out to be the data/log files for
Ken> some of the games I had on my system. I have no idea why they were
Ken> marked as non- movable but I reset them using SD and let them be moved
Ken> and everything still seemed to work. I think some software simply
Ken> marks files incorrectly.
I just realized the difference of what everyone is saying. An Unmovable
file is a file that CAN be moved but you are telling SD *not* to move. A
static file is a hidden, read-only, or system file or directory. That
might clear some of the confusion. You can clear the Unmovable files, but
the Static files have to have the hrs bits removed.
Ken> Ken
Elminster, the Sage of Shadowdale (austin@bucsf.bu.edu)
700 Commonwealth Box 2094, Boston, MA 02215
"S.F.'S NO GOOD!!" They bellow till we're deaf.
"But this looks good." "WELL THEN IT'S NOT S.F.!!"
-- Kingsley Amis