CompuServe Thread

#New VD0: Problem

6 messages in this thread
#10694From: Steven D. KapplinJul 28, 1989 7:03 PM
I have recently switched from old VD0: to the new one recently posted. I have experienced some problems with the new VD0:. After installation and re-booting I experienced the following: 1. When copying files to VD0: chip ram was used instead of fast ram even though fast ram was designated in the mountlist. 2. When executing CleanRamDisk I get a requestor that states that it cannot find "Vdisk.device". In fact the device that has been mounted is "asdg.vdisk.device". Renaming to "Vdisk.device" and modifying mountlist accordingly does not resolve the problem, in fact VD0: will not mount when the driver has been renamed. Replacing the new VD0: with the old VD0: disposes of the above problems. I have to use the old CleanRamDisk, however, with the old VD0:. My installation is an A1000 with 2.5 megs including an outboard Amega 1 meg board, an Insider with KwikStart, and a hard drive running the Cltd SCSI interface. VD0: is mounted after the RAD: device per the documentation. My VD0: has 128 cylinders allocated. Would appreciate learning if I have done something wrong, or if the new VD0: has a bug. Steve
#10704From: Jul 29, 1989 12:43 PM
Steve, Strange with these problems people are having with the new VD0:. I just replaced the devicehandler with the new one and was up and running again as usual. My configuration is A1000, 2.5 MB RAM (TechniSoft RAM-BOard, 2 MB). I wonder, what is causing this for some people and not for others. My Mountlist is: VD0: Device = asdg.vdisk.device Unit = 1 Priority = 5 Surfaces = 1 Flags = 0 BlocksPerTrack = 16 Reserved = 2 Interleave = 0 LowCyl = 0 HighCyl = 191 Buffers = 5 BufMemType = 5 Mount = 1 Regards, J0RGEN
#10705From: Roy S. LauferJul 29, 1989 1:51 PM
Steve, I noticed the same problem. What I did was used the new "asdg.vdisk.device" and the old versions of DeleteRamDisk and CleanRamDisk. It works for me. (I don't know why Perry didn't catch this problem with CleanRamDisk?) -RSL-
#10706From: ASDGJul 29, 1989 2:14 PM
Because Perry didn't put together the arc file that contains two different versions of ram disk software. I trusted some elses's compilation of programs. The problem is that cleanramdisk and deleteramdisk are opening a differently named ram disk device. Sorry…I'll do something about it. pk
#10716From: Fred MurrayJul 29, 1989 10:48 PM
I'm using a 500 with 1 meg and had been using the older VD0. I downloaded the newer VD0 and now it appears to mount (if I try to remount it I get a VD0 is already mounted msg. If I try to CD VD0: I get "Cannot find VD0:" A DIR VD0: returns "Could not get information for VD0:" I've tried bufmemtype set to 3 and 5 and other than that my mountlist is the same. any ideas???
#10717From: ASDGJul 29, 1989 11:32 PM
If you downloaded a zoo file containing several programs plus the ram disk then the person who made the compilation put together things from much different versions. I'll have to take a look.