lah@raybed2.UUCP (LANCE HOLMES) (07/15/88)
I read in the May issue of Amiga world that the recoverable Ram disk which is planned for the next release of the O. S. will be simular to the ASDG RRD. Does this mean that it will be of a fixed length that is defined in the mountlist or will it be a virtual ram disk simular to VDK. I'd also like to hear some pro's or con's with respect to the two different techniques. Personally I like the virtual method better. Lance Holmes p.s. (Notice I said the next release not V1.3 which is going to be out RSN)
sirius@cup.portal.com (07/17/88)
In article: <1194@raybed2.UUCP> Lance Holmes writes: >I read in the May issue of Amiga world that the recoverable Ram disk >which is planned for the next release of the O. S. will be simular to >the ASDG RRD. Does this mean that it will be of a fixed length that is >defined in the mountlist or will it be a virtual ram disk simular to >VDK. >I'd also like to hear some pro's or con's with respect to the two different >techniques. Personally I like the virtual method better. It is like ASDG's, it uses a fixed number of tracks (As of yet I can't get it to make a disk bigger than 80 tracks. It comes back with "handler not found" when I do). In this case it's nic,e because KS1.3 allows you to boot Workbench from it, so it has to be the same as any other amigados disk (except for the highest track). personally I like the ASDG method of pre-allocating the maximum size of the disk. Nothing more annoying than having you RRD chew up all your ram, and sometimes MORE than you have, because you weren't keeping a close enough eye on how much free RAM you have. I don't mind it for smaller or temporary storage, but for heavy use like VD0: and CARD: (I killed my ASDG entry and renamed CARD: to VD0:) I'd definately prefer pre-allocating as opposed to v virtually allocating it on the fly. ___ ___ ___ _________________________ / \ | | \ | | | / \ | | \___ | |___/ | | | \___ | "Jes cuz um uh Mo-Ron | \ | | \ | | | \ | Don't meen um Stu-Pid" | \___/ | | \ | \_/| \___/ |_________________________| {ucbvax!sun,uunet!portal}!cup.portal.com!sirius BITNET: sirius%cup.portal.com@sun.com
david@ms.uky.edu (David Herron -- One of the vertebrae) (07/17/88)
In article <1194@raybed2.UUCP> lah@raybed2.UUCP (LANCE HOLMES) writes: >p.s. >(Notice I said the next release not V1.3 which is going to be out RSN) The RRD *is* in 1.3. It *is* of fixed size specified in the MountList just like the ASDG RRD. -- <---- David Herron -- The E-Mail guy <david@ms.uky.edu> <---- ska: David le casse\*' {rutgers,uunet}!ukma!david, david@UKMA.BITNET <---- What is this wet ... *stuff* ....... falling from the sky? <---- It stirs a vague memory of ... *something* ... but of what I do not know.
fgd3@jc3b21.UUCP (Fabbian G. Dufoe) (07/19/88)
On the other hand, the virtual technique allows you to get more memory by deleting some files from RAM:. The pre-allocation technique won't cut you any slack that way. --Fabbian Dufoe 350 Ling-A-Mor Terrace South St. Petersburg, Florida 33705 813-823-2350 UUCP: ...gatech!codas!usfvax2!jc3b21!fgd3
andy@cbmvax.UUCP (Andy Finkel) (07/19/88)
In article <7415@cup.portal.com> sirius@cup.portal.com writes: it uses a fixed number of tracks (As of yet I can't get >it to make a disk bigger than 80 tracks. It comes back with "handler not >found" when I do). In this case it's nic,e because KS1.3 allows you to RAD wants contigious memory. This may be what is happening. Also, RAD does not want (or need) to be formatted when used with the old file system. -- andy finkel {uunet|rutgers|amiga}!cbmvax!andy Commodore-Amiga, Inc. "It is sad, but all too often, the source code to an assembly language program and an uncommented disassembly of that program are identical." Any expressed opinions are mine; but feel free to share. I disclaim all responsibilities, all shapes, all sizes, all colors.
sneakers@heimat.UUCP (Dan "Sneakers" Schein) (07/20/88)
In Message <7415@cup.portal.com>, sirius@cup.portal.com writes: >In article: <1194@raybed2.UUCP> Lance Holmes writes: >>I read in the May issue of Amiga world that the recoverable Ram disk >>which is planned for the next release of the O. S. will be simular to >>the ASDG RRD. Does this mean that it will be of a fixed length that is >>defined in the mountlist or will it be a virtual ram disk simular to >>VDK. > >>I'd also like to hear some pro's or con's with respect to the two different >>techniques. Personally I like the virtual method better. > >It is like ASDG's, it uses a fixed number of tracks (As of yet I can't get >it to make a disk bigger than 80 tracks. It comes back with "handler not >found" when I do). In this case it's nic,e because KS1.3 allows you to >boot Workbench from it, so it has to be the same as any other amigados >disk (except for the highest track). > Hmmm this is odd, its been awile since I used CBM's RRD - but I thought it went bigger than 80 tracks. Carolyn - Andy? >personally I like the ASDG method of pre-allocating the maximum size of the >disk. Nothing more annoying than having you RRD chew up all your ram, >and sometimes MORE than you have, because you weren't keeping a close enough >eye on how much free RAM you have. I don't mind it for smaller or temporary >storage, but for heavy use like VD0: and CARD: (I killed my ASDG entry and >renamed CARD: to VD0:) I'd definately prefer pre-allocating as opposed to v >virtually allocating it on the fly. > Well im just the opposite - I like my ram disk to grow on the fly :-) This way if im doing alot of C code - compiling - downloading from Berks Amiga BBS - ect. I don't have to worry about running into the max size of my RRD. Also if I want to fool around with Psound and my digitizer (to do something important like Roger Rabbit) and need the ram for a large size sample, having a allocate as you go RRD gives me memory that otherwise would have been alocated to the RRD. I have the 1.3 RRD and ASDG's VD0: but I use (and prefer for the reasons above) the one by Neil Katin called VDK: also known as Survivor. (VDK: is a commercial product - not PD or ShareWare) -- Dan "Sneakers" Schein {ihnp4|allegra|burdvax|rutgers}!cbmvax!heimat!sneakers Sneakers Computing 2455 McKinley Ave West Lawn PA 19609 Call: BERKS AMIGA BBS 24 Hrs - 3/12/2400 Baud Disclaimer: Any opinions expressed are 40 Meg -=- 215/678-7691 those of Sneakers Computing Of course heimat is an Amiga, doesn't everyone run UUCP & UseNet on an Amiga?
Skywalker@cup.portal.com (07/21/88)
It sounds like you people haven't used ASDG's VD0:, because its "size" is only a *maximum* size -- it does actually allocate and free memory from your available system RAM on an ongoing basis (and I've watched it do it, too! -- it's just a little slow about releasing the memory- read the docs, it's well explained.) (.signature files only waste bandwidth) skywalker@cup.portal.com
conn@panda.gatech.edu (Avery Shealey) (07/22/88)
In article <1504.AA1504@heimat> sneakers@heimat.UUCP (Dan "Sneakers" Schein) writes: > I have the 1.3 RRD and ASDG's VD0: but I use (and prefer for the reasons above) > the one by Neil Katin called VDK: also known as Survivor. (VDK: is a commercial > product - not PD or ShareWare) > >-- > Dan "Sneakers" Schein {ihnp4|allegra|burdvax|rutgers}!cbmvax!heimat!sneakers > Sneakers Computing > 2455 McKinley Ave > West Lawn PA 19609 Call: BERKS AMIGA BBS > 24 Hrs - 3/12/2400 Baud > Disclaimer: Any opinions expressed are 40 Meg -=- 215/678-7691 > those of Sneakers Computing > > Of course heimat is an Amiga, doesn't everyone run UUCP & UseNet on an Amiga? Anyone know how to get vdk? thanks /avery Avery Shealey School of Information & Computer Science, Georgia Tech, Atlanta GA 30332 Internet: conn@boa.gatech.edu CSNet: conn%boa@gatech UUCP: ...!{akgua,allegra,amd,hplabs,seismo,ihnp4}!gatech!boa!conn Avery Shealey School of Information & Computer Science, Georgia Tech, Atlanta GA 30332 Internet: conn@boa.gatech.edu CSNet: conn%boa@gatech
filip@alberta.UUCP (Don Filipchuk) (07/22/88)
In article <17311@gatech.edu> conn@panda.UUCP (Avery Shealey) writes: >In article <1504.AA1504@heimat> sneakers@heimat.UUCP (Dan "Sneakers" Schein) writes: >> I have the 1.3 RRD and ASDG's VD0: but I use (and prefer for the reasons above) >> the one by Neil Katin called VDK: also known as Survivor. (VDK: is a commercial >> product - not PD or ShareWare) >> Dan "Sneakers" Schein {ihnp4|allegra|burdvax|rutgers}!cbmvax!heimat!sneakers Does anybody know if the new 1.3 release will have the old RAM: device? Or does the new 1.3 RRD **REPLACE** the RAM: disk. It's just that I find the old, unrestrained RAM: disk so useful when starting some quick and dirty operation that might eat up huge chunks of memory, and I don't want to trash my VD0:.... Second question : To send Perry (at ADSG) a shareware donation for his spiffy VD0: do I just send it to him c/o ADSG? I know that some ADSG people read the news here sometimes, and I'd like to send it but I want to make sure that it gets to it's intended recipient... Don -------------------------------------------------------------------------- | Don Filipchuk | "... with human females, I must | | | restrain myself too much. They are | | University of Alberta | quite fragile." | | Edmonton, Alberta | | | Canada | - Lt. Worf -- | --------------------------------------------------------------------------
jdow@gryphon.CTS.COM (J. Dow) (07/25/88)
In article <308@cadomin.UUCP> filip@cadomin.UUCP (Don Filipchuk) writes: >In article <17311@gatech.edu> conn@panda.UUCP (Avery Shealey) writes: >>In article <1504.AA1504@heimat> sneakers@heimat.UUCP (Dan "Sneakers" Schein) writes: >>> I have the 1.3 RRD and ASDG's VD0: but I use (and prefer for the reasons above) >>> the one by Neil Katin called VDK: also known as Survivor. (VDK: is a commercial >>> product - not PD or ShareWare) >>> Dan "Sneakers" Schein {ihnp4|allegra|burdvax|rutgers}!cbmvax!heimat!sneakers > > > Does anybody know if the new 1.3 release will have the > old RAM: device? Or does the new 1.3 RRD **REPLACE** the > RAM: disk. It's just that I find the old, unrestrained > RAM: disk so useful when starting some quick and dirty > operation that might eat up huge chunks of memory, and > I don't want to trash my VD0:.... The old ram: handler will remain in place. It DOES have its uses. The sadest thing about RAD: is it only marginally works on my machine. At DevCon I won one of the 1Meg AGNUS chips. That blows the OS mind so that a sanity check in it decides things are corrupt and it has to recold boot. Byebye rad:. Carolyn has generated a little utility called "saverad" that helps. But nothing we can do really makes it survive a GURU very well. Thank heavens for the recovery speed I get with the HardFrame prototype I have been working on and debuggin. At least a boot from HD is much better than from floppy! (And the HD is now much faster than rad:. It boots up with ffs!) >-------------------------------------------------------------------------- >| Don Filipchuk | "... with human females, I must | >| | restrain myself too much. They are | >| University of Alberta | quite fragile." | >| Edmonton, Alberta | | >| Canada | - Lt. Worf -- | >-------------------------------------------------------------------------- Gee, Worf, ya cudda fooled me? You're really awfully cuddly you know! <deep throated growl!> YUMMY YUMMY! <unsane giggle> -- Sometimes a bird in the hand leaves a sticky deposit. Perhaps it were best it remain there in the bush with the other one. {@_@} jdow@bix (where else?) Sometimes the dragon wins. Sometimes jdow@gryphon.CTS.COM the knight. Does the fair maiden ever {backbone}!gryphon!jdow win? Surely both the knight and dragon stink both stink to high heaven.