On Sun, Mar 13, 2022 at 10:50 AM Eric Auer <e.a...@jpberlin.de> wrote:
>
> > RDRVSX32: FAT32 RAM drive for HimemSX (Announce)
> >
> > posted by jadoxa, Queensland, Australia, 13.03.2022, 13:58
> >
> > I had a request (via email) to create a RAM drive greater than 4GiB.
> > It sort of works (works on his and mine 8GiB AMD, but has issues with
> > his 32GiB Intel) so if anyone has the time and inclination to test,
> > that'd be great. You will need more than 4GiB RAM (in order to access
> > super-extended memory), preferably more than 8GiB (in order to test
> > accessing beyond 4GiB). Our testing has been simple so far: just copy
> > large files (he was able to create a 28GiB RAM drive, copy hundreds
> > of 64MiB files, but it fails copying a 1GiB file).

I haven't read through the entire thread, but I am curious about why
the person whose email request was referenced *wanted* a RAMdrive for
DOS targer than 8GB.

On bare metal DOS back in the PC XT days, Ihad an AST 7-Pak card that
added an extra megabyte of RAM, with software that could use it to
create a RAMdrive and/or a disk cache.  I did both, with a 512KB
RAMdrive sees as Z:\. and  256KB disk cache.  My AUTOEXEC.BAT file
copied frequently used utilities likew Vern Buerg's LIST and my
texteditor to the RAMdrive, and various things that could be told
where to create temp file like PKZIP used the RAMdrive when they
created them.  Z:\.was the first entry in my DOS %PATH%.  That and the
disk cache sped things up a treat.

I still use a RAMdrive under Win10 Pro. I found an open source 64bit
Windows RAMdrive driver that would allocate arbitrary amounts of
physical RAM to one or more RAMdrives. Here, I hafe 20GB RAM, and
512MB is allocated to Z:], a RAMdrive used for browser cache.
(Firefox makes that easy.  Chrome requires serious hacking.)  I don't
do development on this machine. If I did, I'd likely find other uses
for the RAM. On my prior desktop running Win7, I had Firefox set up to
run entirely from the RAMdrive, with the profile iyt used stored tehre
too.  The currrent machine boots of a 256GB SSD, and testing revealed
no observable speedup from rthe profile on the RAMdrive vs having it
on SSD, so I didn't bother recreating the previous setup.

With a big enough RAMdrive, you could create it on startup and copy
*everything* you used to it and run entirely off the RAMdrive.  I
could do something like thet with the Win64 RAMdrive.  You can define
an image file to be loaded to it after it is instantiated, and I could
theoretically load everything I use to it, but the benefits don't
justify the effort. .
______
Dennis


_______________________________________________
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Reply via email to