Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!brutus.cs.uiuc.edu!ux1.cso.uiuc.edu!ux1.cso.uiuc.edu!uxa.cso.uiuc.edu!sfn20715
From: sfn20715@uxa.cso.uiuc.edu
Newsgroups: comp.sys.ibm.pc
Subject: RamdiskQ
Message-ID: <111700179@uxa.cso.uiuc.edu>
Date: 12 Dec 89 10:39:14 GMT
Lines: 17
Nf-ID: #N:uxa.cso.uiuc.edu:111700179:000:789
Nf-From: uxa.cso.uiuc.edu!sfn20715    Dec 11 22:40:00 1989


I have several questions about ramdisks.  
 1) When I execute a program from a ramdisk, the OS copies the code from
 some area of ram allocated to the ramdisk into some area of ram not
 allocated and sets the program counter at the beginning of this new
 area, right?
 2) Wouldn't it be a lot better if a ramdisk were to use the OS's "Load but
 dont execute" function to load executables onto a ramdisk?
 That way, when the user wants to execute it, the ramdisk controller
 executes an "execute already loaded program", saving duplicating the
 program and all of the time requried in doing such, etc etc.
 When the program is to be deleted, just use the "unlink already loaded
 program" function.
 Data and/or nonexecutables could be kept in the usual ramdisk fashion.


 Would this work?