Announcement

Collapse
No announcement yet.

Error when mounting ramdisk with command line 1.5.1014

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

  • jslegers
    replied
    The -o rw option does the trick thanks for the tip.

    Leave a comment:


  • keith
    replied
    Originally posted by jslegers View Post
    Hello,

    I have discovered an other bug. When I create a ramdisk with the command line the ramdisk is readonly. When i create it with the gui it is read/write.

    See below :

    [ATTACH=CONFIG]75[/ATTACH]

    R: is command line
    F: is with gui
    It looks like the default is set to read-only, which is OK for files but unreasonable for empty ram disks. We will change the default for empty ram disks to read/write for the next build. For now, you can specify "-o rw" to set the permissions to read/write.

    Leave a comment:


  • jslegers
    replied
    Hello,

    I have discovered an other bug. When I create a ramdisk with the command line the ramdisk is readonly. When i create it with the gui it is read/write.

    See below :

    Click image for larger version

Name:	8clbGwp.jpg
Views:	1
Size:	20.6 KB
ID:	34850

    R: is command line
    F: is with gui

    Leave a comment:


  • keith
    replied
    Originally posted by jslegers View Post
    Hello,

    I use a command line to create a ramdisk. This has always worked with the previous versions. But with version 1014 it misses something :

    [ATTACH=CONFIG]73[/ATTACH]
    Is this a bug?
    I'm using Windows 8.1 64 Bit
    The command is correct, and it looks as though the RAM disk was successfully created.

    Please ignore the error output as this is a bug. This will be removed from the next build.

    Leave a comment:


  • Error when mounting ramdisk with command line 1.5.1014

    Hello,

    I use a command line to create a ramdisk. This has always worked with the previous versions. But with version 1014 it misses something :

    Click image for larger version

Name:	rQlOL4C.png
Views:	1
Size:	17.2 KB
ID:	35102
    Is this a bug?
    I'm using Windows 8.1 64 Bit
Working...
X