C475141@umcvmb.missouri.edu (BRIAN WHITMAN) (10/16/89)
A short brief history of how I got myself into this fix. While I was attempting to download some of the neptune pics, using vt100 v2.6 (I think) my disk ran into a read/write error (it was one of those .69 doods from NEI). I said continue a couple times only to get the same requester so I said poooeee with it and hit the close gadget in the upper left hand corner. upon doing this I found myself looking into the white box of a Disk Validator error. Well it ended up that it crashed my WB1.3 and my telecommunications disk before hitting the on off switch. After making a temp WB1.3 and getting booted up, I obtained DiskSalv from a friend I decided to read the docs and attempt to recover the disk. (side note prior to using disksalv I attempted to use our beloved DiskDoctor). I issued the command DiskSalv df0: df1: and take all the other defaults. By the time I rebooted my machine 7 times or so I was issueing the command whithseveral of the options. During these times of starting it I noticed thing that didn't agree. For the mountlist entry the demo in the doc gave a value of 3 for MEMTYPE. When DiskSalv printed my mountlist it gave a value of 2 for MEMTYPE. Will that make a difference? Should I change my MountList entry? What if anything is the difference? HERE IS WHAT THE PROBLEM WAS Error: out of memory continuously flashing up the screen with no ^c, escape, or anything doing any good. I then started limiting the number of blocks. I had noticed that it made it to 8000 ok so did a diskSalv df0: df1: start 0 stop +700 that ran fine no probs. So then I decided to continue with 8000 to 1100 and ended up with the same result a locked task scrolling Error out of memory up my screen. Is there still hope for my disks? Anybody with any answers I would appreciate. appreciate it. Thanks Brian E Whitman Please send mail to UC475141&@UMCVMB.Bitnet or UC475141@UMCVMB>Missouri.edu