Announcement

Collapse
No announcement yet.

OSFMount create RAMDisk from console(Disk in Explorer is not displayed)

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • OSFMount create RAMDisk from console(Disk in Explorer is not displayed)

    Hey.
    If I use GUI when creating RAMDISK, then disks are created and the system sees them (disks are displayed in my computer folder)
    If I use the console, the command:

    Code:
    OSFMount.com -a -t vm -s 512M -o format:fat32:"RamDisk",logical,rw -m V:
    Creating device...
    Created device 6: V: -> VM image
    Formatting drive with volume label RamDisk
    Done

    I see that drives are created, I see it in the application OSFMount.exe and in the console using the commands:

    Code:
    wmic logicaldisk get description,name
    Description       Name
    Local Fixed Disk  C:
    Local Fixed Disk  D:
    Local Fixed Disk  E:
    Local Fixed Disk  F:
    Local Fixed Disk  G:
    CD-ROM Disc       H:
    Local Fixed Disk  I:
    Local Fixed Disk  N:
    Local Fixed Disk  O:
    Local Fixed Disk  V:  //<--- its RAMDisk

    But in the explorer and in the folder of my computer, I do not see the drives. even if you use the F5 key, discs are not displayed.

    OS: Windows 7 SP1 x64

    Code:
    OSFMount.com --version
    PassMark OSFMount Command Line Interface.
    Version V3.0 (Build 1005) - (Compiled May 31 2019)
    How i can fix it?

  • #2
    What happens if you type in the drive letter into Windows Explorer in the navigation bar?
    We've seen cases where Windows Explorer doesn't update its display, but it can still access the drive if you type in the path.

    Comment


    • #3
      No, Explorer reports that this is not a valid drive name or path.
      But I can go to this drive from the console and create files or directories there.

      I think this is a banal regression!
      I installed the version osfmount_x64_v2.0.1001

      And using the following command:
      Code:
      ./osfmount.com -a -t vm -s 512M -o format:fat32:"RamDisk",rw -m V:
      Creating device...
      Created device 0: V: -> VM image
      Formatting drive with volume label fat32:RamDi
      Notifying applications...
      Done.
      I got the result I need. The disk is created and the Windows Explorer sees and displays it.

      As I understand it, in the new version there is an error in registering a new disk in the system.

      A new version (v3.0.1005):
      Code:
       ./osfmount.com -a -t vm -s 512M -o format:fat32:"RamDisk",rw -m V:
      Creating device...
      Created device 0: V: -> VM image
      Formatting drive with volume label RamDisk
      Done.
      Old version (v2.0.1001):
      Code:
      ./osfmount.com -a -t vm -s 512M -o format:fat32:"RamDisk",rw -m V:
      Creating device...
      Created device 0: V: -> VM image
      Formatting drive with volume label fat32:RamDi
      Notifying applications...  //This message is not in the new version!
      Done.
      I can’t say for sure which version it happened in, because I don’t know where to download them. I have only version v2.0.1001 and v3.0.1005

      Comment


      • #4
        I see version 3.0.1006 on the download page. I downloaded it and now I can create RAM disks from cmd.
        Is this an official release?
        it’s just that you did not answer in this topic and on the download page in the section what's new, there is no information about version 6.
        But there are duplicates for version 5. Perhaps a web page error.

        Comment


        • #5
          Originally posted by IgorIvanov View Post
          I see version 3.0.1006 on the download page. I downloaded it and now I can create RAM disks from cmd.
          Is this an official release?
          Yes, we made a new release of OSFMount (V3.0.1006) few days ago. This includes addressing the issue from your original post. Good to hear the problem seems to be resolved.

          Originally posted by IgorIvanov View Post
          But there are duplicates for version 5. Perhaps a web page error.
          Thanks for pointing out the error. We have added the change list for V3.0.1006

          Comment

          Working...
          X