Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!rochester!cornell!batcomputer!braner From: braner@batcomputer.tn.cornell.edu (braner) Newsgroups: comp.sys.atari.st Subject: Re: questions about TOS Message-ID: <1986@batcomputer.tn.cornell.edu> Date: Sun, 11-Jan-87 00:02:35 EST Article-I.D.: batcompu.1986 Posted: Sun Jan 11 00:02:35 1987 Date-Received: Sun, 11-Jan-87 04:36:56 EST Reply-To: braner@batcomputer.UUCP (braner) Organization: Theory Center, Cornell University, Ithaca NY Lines: 28 Summary: Problem, unsolved, further explained [] I'm still stuck on the problems I posted a couple of days ago. Consider a program based on the following idea: Rwabs(READ, buffer, secs-1, 1, A); Rwabs(WRITE,buffer, secs-1, 1, D); where secs=no. of sectors on the disk, and READ, WRITE, A and D are the obvious constants. (D is a RAM disk.) This should copy the complete floppy disk contents to the RAM disk. Note that the boot sector (#0) is NOT overwritten. As long as the two disks have the same LOGICAL structure (bytes per sector, sectors per cluster, sectors per FAT and in the root directory) the copied data should be usable. And it is! I have succesfully copied a single sided disk to a double-sided one this way, AS A DISK (not file-by-file). As a matter of fact, I have a nifty program that (after appropriate safety checks...) allows copy from any drive to any drive, all ready to go, but... The Problem: SOMETIMES (not always!), when copying from a floppy to the RAMdisk, I end up with a strange RAMdisk: all files in the root directory work fine, EXCEPT subdirectories (folders). When clicked, it flickers and stutters and ends up still showing the root directory contents. (From inside micro-C-Shell I get "not found" responses to "ls sub_dir_name".) A check with a RAM editor shows that all the relevant data is present in the RAMdisk area where expected. Can anyone pull me out of THIS ditch? - Moshe Braner