SweetLow Posted August 20 Author Posted August 20 On 8/18/2024 at 1:22 PM, schwups said: No problems so far, also with swap file set to max size. Thank for testing. Looks like some subtle bug exists in Windows 98/SE: too early shutting down the drive with swap file and probably it is masked by the fact that usual drives much slower than RAM drives.
schwups Posted August 20 Posted August 20 (edited) I had installed 8GB, too. In this case the size of the swap file RAMDrive remains at 1.99 FAT without setting anything. Is this correct? Edited August 20 by schwups
SweetLow Posted August 20 Author Posted August 20 21 minutes ago, schwups said: In this case the size of the swap file remains at 1.99 FAT without setting anything. It is not correct question precisely. Under Windows ME on RAM drive you should get FAT32 volume (not FAT16) by default with size ~4.5 GiB on 8 GiB RAM. 2GiB swap file is just maximal size of swap file under Windows 9x AFAIK, but to get such size you have to set it directly, by default swap file has volatile size and is less than 2GiB.
schwups Posted August 20 Posted August 20 4 hours ago, SweetLow said: Under Windows ME on RAM drive you should get FAT32 volume (not FAT16) by default with size ~4.5 GiB on 8 GiB RAM. Sorry, of course I mean RAMDrive and not swap file. It is to be assumed that the drive should grow accordingly with size of RAM and switch to FAT32 by default. The question is why this didn't happen here.
SweetLow Posted August 20 Author Posted August 20 4 hours ago, schwups said: The question is why this didn't happen here. Yes, it is NOT normal. It shoud be FAT32 and grow as RAM added. Ok, try to setup this registry file, it is forcibly enable FAT32: REGEDIT4 [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\RAMDRV4M] "Config"="Home.Default" [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\RAMDRV4M\Home.Default] "UseFAT16"=hex:00
schwups Posted August 21 Posted August 21 It was a bit strange with the reg file. It was allegedly successfully merged into the registry, but "UseFAT16"=hex:00 was missing. So I merged it manually. Now I have indeed 3.99GB FAT32! Thanks.
SweetLow Posted August 21 Author Posted August 21 https://github.com/LordOfMice/Tools/blob/master/ramdrv4m.zip On 8/20/2024 at 2:13 PM, schwups said: RAMDrive remains at 1.99 FAT without setting anything Fixed bug in detection of FAT32 support.
defuser Posted August 21 Posted August 21 7 hours ago, schwups said: It was a bit strange with the reg file. It was allegedly successfully merged into the registry, but "UseFAT16"=hex:00 was missing. So I merged it manually. Now I have indeed 3.99GB FAT32! Thanks. Most likely, some volume is reserved by the built-in graphics. This value can usually be changed in the BIOS. I also have 8GB, but the ramdisk size is different: However, no values in the registry had to be changed. It immediately took up all the available space and was automatically formatted in FAT32. Perhaps, in your case, the crucial role was played by changing the amount of RAM from 6GB to 8GB.
defuser Posted August 21 Posted August 21 (edited) SweetLow, hi, do you know where Windows gets the ramdisk mapping from to the disk name "MS-RAMDRIVE"? With a different name, as shown in the screenshots above, the disk is defined as "Type: Local Disk" and assigned an icon corresponding to the local disk. If you enter the name "MS-RAMDRIVE", the icon changes to microchip and the type changes to "Type: RAM Disk". When it is RAM Disk in "My Computer" it is easy to immediately distinguish it by another icon. And so (By default), it merges with other (Regular) disks, without being distinguished in any way. It would be possible to leave the name "MS-RAMDRIVE", but as I wrote earlier, it is too long and does not fit completely. I would like to make the name "RAMDRIVE" by default and that it would be defined by the system as "MS-RAMDRIVE", assigning it the correct type and icon. Edited August 21 by defuser
SweetLow Posted August 21 Author Posted August 21 5 minutes ago, defuser said: SweetLow, hi, do you know where Windows gets the ramdisk mapping from to the disk name "MS-RAMDRIVE"? No. Try to search yourself and don't forget that VMM32.VXD is actually packed collection of system VXDs 1
schwups Posted August 21 Posted August 21 (edited) Tested and confirmed FAT32 detection by default - without registry entry! 1 hour ago, defuser said: Most likely, some volume is reserved by the built-in graphics. This value can usually be changed in the BIOS. I also have 8GB, but the ramdisk size is different: P965 hasn't built-in graphics, but yes the reserved size is different for each board. POST gives 7104MB here, what is quite little. Edited August 21 by schwups
defuser Posted August 21 Posted August 21 1 hour ago, SweetLow said: No. Try to search yourself and don't forget that VMM32.VXD is actually packed collection of system VXDs I was able to find out that "MS-RAMDRIVE" is located in "KERNEL32.DLL". I just changed it to "MS-ROMDRIVE", replacing one letter ("A" with "O") and it worked! In other words, the name is mapped exactly from there. The question now is, is there any way to cut off "MS-" painlessly so that it doesn't affect everything else? Simply deleting these three characters is not an option - the code will shift and the OS will not boot. Is it obvious that some other approach is needed here, or does this issue not have a simple solution?
SweetLow Posted August 21 Author Posted August 21 2 hours ago, defuser said: The question now is, is there any way to cut off "MS-" painlessly so that it doesn't affect everything else? Do not delete anything. Set the name you wish from begin of "MS-RAMDRIVE" and add spaces to get string with 11 characters (exactly the "MS-RAMDRIVE" and DOS file record name length). I.e. replace "MS-RAMDRIVE" to "RAMDRIVE ".
defuser Posted August 22 Posted August 22 (edited) 11 hours ago, SweetLow said: Do not delete anything. Set the name you wish from begin of "MS-RAMDRIVE" and add spaces to get string with 11 characters (exactly the "MS-RAMDRIVE" and DOS file record name length). I.e. replace "MS-RAMDRIVE" to "RAMDRIVE ". Yes, I already tried this, but it didn't work. You tried it and it worked (By the way, this applies to any disk under 98\98SE, but it doesn't work at all in WinME. Just in case I'm doing something wrong)? The options I've already checked are "RAMDRIVE[Three spaces]", "RAMDRIVE[HEX: 00 00 00]", "RAMDRIVE[HEX: FF FF FF]". In the first case, Windows cuts off the last three spaces. It doesn't matter if you do this via the command line ("LABEL M: RAMDRIVE ") or via the disk properties - the result is the same: just "RAMDRIVE" remains and nothing changes. With the second two options, the result is identical (Nothing changes: the disk type and icon remain the same, corresponding to the local disk, but not ramdisk). Edited August 22 by defuser
defuser Posted August 22 Posted August 22 And another question - is it possible to get access to the ramdisk ALREADY placed in memory under WinXP? During the XP session, after 98, the information is securely stored there and does not disappear when you return to 98 (I checked). Question - is it possible to reach it directly under WinXP (Read\Write)?
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now