![]() Maybe the game writes somewhere else (cache?) during load and this is the main factor in loading time? So, instead of moving GameData to RAM I need to place that cache folder there?īut, anyway, what are your loading time, guys? And how much mods do you have? I've mainly wanted to compare against others to see if this is typical or not. You can keep your saves on the physical HDD/SSD and that was actually what I did: I only moved GameData folder on the RAM disk by making a symbolic link to it from the game directory (and maybe that's why I didn't see any major improvement?) because my RAM size is insufficient to move an entire game there while leaving some ram to run it, the OS and other persistent software. This product lets you create any number of virtual RAM disks limited only by the available memory. That right there I think is worth waiting a few minutes more to have it load. They all work in full DOS environment, but hang in DosBox, no matter if I try to use XMS or EMS memory.I think the biggest risk to keeping KSP in a RAM disk is either forgetting to copy your save files over to real storage before rebooting, or losing save progress to a power or system interruption. You can configure as many virtual drives as you have available drive letters and run multiple virtual CDs simultaneously. VirtualDrive Pro lets you create up to 23 virtual CD/DVD-ROM drives and an unlimited number of virtual CDs and DVDs. (Listed all them here in case you’ll want to test them). In Windows Explorer, a virtual disc shows up as a drive letter. – MS Ramdrive from MS-DOS 6.22 (DosBox doesn’t support config.sys commands, but it is possible to load drivers from command line):ġst, you need to add available device letters with “LastDrive” utility: Ģnd, load RAMDRIVE.SYS with “DevLoad” utility: I tried DOS RAM disks from several developers: Since I didn’t give up with that “RAM drive” idea, I decided to mount ordinary ram-disk software, and figured out that all RAM disks hang in DosBox. To make a RAM disk, download Dataram RAMDisk(click Download Software), and follow the instructions below. Played with Magic DosBox little more and found out that it supports up to 512 Mb of EMS memory, cool! – probably will be more compatible with different programs. – probably can be much larger than dos ramdisk – will be available without any memory drivers Unlike with DOS ramdrive.sys, such “real” drive: “rammount d -t hdd -fs fat -size 512,63,16,520 -save /sdcard/images/w95_256mb.img”Ĭreate unformatted disk D, then install Windows, for example, and save ram drive on shutdown. “rammount c -t hdd -fs fat -size 512,63,16,520 -load /sdcard/images/w95_256mb.img -save -”Ĭreate 256 Mb ram drive, load it from image file and don’t save any changes on shutdown (to test some Windows program and leave system untouched). – optionally save data to disk image file on shutdown.Ĭreate floppy drive in RAM on startup, then do what is needed – format it, make bootable or whatever – and, since “-save” is not defined, during shutdown ask to save RAM image to file or not. – optionally load data from *.img files on startup It’s not so important for desktops, but should be useful for mobile devices, as they have much more degradable flash memory.Īnd, if it’s possible, it could be handful to: To make a RAM disk, download Dataram RAMDisk (click Download Software), and follow the instructions below. Similar to how *.img drives are handled, but with data in memory. Install and remove the RAM Disk, configure its size, drive letter and media type, and use the load or save image buttons for persistent storage. Hello, may I add a little suggestion: is it possible to add “physical” drive emulation in RAM?
0 Comments
Leave a Reply. |