joe@dayton.UUCP (Joseph P. Larson) (09/11/89)
We just upgraded the 500 at work to a 3-meg machine. Does really nice things to the speed of things when you never touch the disk after bootup. Anyways, I wanted to try something -- make a larger RAD:. It complained when I changed the highcyl value to 120 -- "Not a DOS disk". So I changed it back to 79 and created a second RAD: entry, renaming it to RD2:, and tried that. Machine eventually crashed. So -- is there anything I can do to obtain an extra 300K or so of recoverable ramdisk space? I've got memory to burn, you see. I can just use RAM:, but that doesn't survive the occassional crash or necessary reboot terribly well. -Joe -- Life is a cabaret (old chum). UUCP: rutgers!dayton!joe (Picts 1-13 are DHDSC - Joe Larson/MIS 1060 ATT : (612) 375-3537 now ready.) 700 on the Mall, Mpls, Mn. 55402
shadow@pawl.rpi.edu (Deven T. Corzine) (09/13/89)
On 11 Sep 89 14:27:29 GMT, joe@dayton.UUCP (Joseph P. Larson) said: joe> Anyways, I wanted to try something -- make a larger RAD:. It joe> complained when I changed the highcyl value to 120 -- "Not a DOS joe> disk". So I changed it back to 79 and created a second RAD: joe> entry, renaming it to RD2:, and tried that. Machine eventually joe> crashed. I don't know how large you can manage to make RAD:, but whenever you change the size of RAD: while an old one exists (whether mounted yet or not) you will get the "Not a DOS disk" error. You can either do a RemRAD and reboot, and it will recreate it from scratch, or you can simply mount the new sized one and format it. (It's fun to watch RAD: format... it FLIES.) Deven -- Deven T. Corzine Internet: deven@rpi.edu, shadow@pawl.rpi.edu Snail: 2151 12th St. Apt. 4, Troy, NY 12180 Phone: (---) --none-- Bitnet: deven@rpitsmts, userfxb6@rpitsmts UUCP: uunet!rpi!deven Simple things should be simple and complex things should be possible.
fgd3@jc3b21.UUCP (Fabbian G. Dufoe) (09/13/89)
From article <6757@dayton.UUCP>, by joe@dayton.UUCP (Joseph P. Larson): > Anyways, I wanted to try something -- make a larger RAD:. It complained > when I changed the highcyl value to 120 -- "Not a DOS disk". So I changed > it back to 79 and created a second RAD: entry, renaming it to RD2:, and > tried that. Machine eventually crashed. Did you make a renamed copy of your RAD: handler and edit it to have a different name or did you just rename RAD: with a relabel command? I ran a second RAD: for a while and it worked OK. Copy sys:devs/ramdrive.device to sys:devs/ramdriv2.device. The use a disk editor to change "ramdrive" to "ramdriv2" and "RAMB0" to "RAMB1" in ramdriv2.device. Then add a second mountlist entry for RD2:, for example. I hope I have't left out anything. --Fabbian Dufoe 350 Ling-A-Mor Terrace South St. Petersburg, Florida 33705 813-823-2350 UUCP: ...uunet!pdn!jc3b21!fgd3