Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!bu.edu!rpi!zaphod.mps.ohio-state.edu!samsung!cs.utexas.edu!rutgers!njin!limonce From: limonce@pilot.njin.net (Tom Limoncelli) Newsgroups: comp.sys.amiga.tech Subject: Re: HD validation error (possible cause?) Message-ID: Date: 16 Jan 91 17:29:20 GMT References: <1991Jan16.040022.22135@eecs.wsu.edu> Organization: Drew University/NJIN Lines: 22 In article <1991Jan16.040022.22135@eecs.wsu.edu> rnelson@eecs.wsu.edu (Roger Nelson - Grad Student) writes: > Is it not the responsibility of the File System to manage the HD resource? > If the File System is reliable against large numbers of simultaneous > operations, then there must be some flaw in the HD, the controller, or the > HD driver software? I don't know if this is what happens with LHARC, but it is a simple counter example to what you suggest: The FS can only protect you to a certain (excuse the pun) extent. What if a utility needs to create a temporary file. It creates it as T:lharc.tmp every time. Running the utility multiple times will cause problems. This is the kind of thing I would expect from a program ported from the PC. I didn't like the one I found in Manx 3.6 so I wrote my own. I believe AmigaDOS 2.0 has a "create unique file name" system call. -- tlimonce@drew.edu Tom Limoncelli "Flash! Flash! I love you! tlimonce@drew.bitnet +1 201 408 5389 ...but we only have fourteen tlimonce@drew.uucp limonce@pilot.njin.net hours to save the earth!"