Re: why you can't find ramdrive in your system
The reason you can't 'find' windows:ramdrive.sys active in your operating
system is simply because IT ISN'T. If you read my email carefully you will
notice that I stated that it was used during the INSTALL of the operating
system. It (ramdrive) has to strap itself in as E:, that is why you have
to leave it alone in regards to it picking its drive letter. It erases
itself after it has done its prepatory work (one such necessary thing is
for it to establish HIMEM so that Windows can do its install within it).
It is NOT active once the install is completed; I never said that it was.
By the way, when you said that you built your own ramdrive, do you mean
that you implemented the ramdrive.sys application, or did you really build
a program (as opposed to scripting commands as boot macros)? Pardon me for
being so abrupt, but Building and Using are two different things, and both
are necessary in their place, but this is a programmer's forum, not an
application batching forum. Sorry about the smoke, but at least that is
better than flames.
I do wish to thank you from getting some of us away from the constant
filing of Linux stuff. It is great that porting is taking place, but Kat
at least brings some relief in the form of a different subject. 
Norm
|
Not Categorized, Please Help
|
|
