Updating Vivaldi on a small sized RAM disk



  • I have Vivaldi standalone installation on a 1Gb RAM disk. Normally it has 15% of free space. So when I start the update installer to install the new snapshot it stops because I guess there is not enough space on the RAM disk for installation.
    So what I do is install Vivaldi standalone somewhere on a hard drive first.
    My question is - will the update be done correctly if I delete the Application folder from the RAM disk and then copy the new Application folder to the RAM disk, leaving the old User Data as it was to keep all the old garbage? :)
    In other words, are all the changes for the new version contained in the Application folder, and nothing in the User Data folder needs updating so it's OK to just keep the old one?
    Thanks



  • @svguss Your assumption is correct - all your user data is kept separately from the application folder. you can safely delete that and install the new version in its place.

    A RAM disk sounds interesting - what software do you use to manage that?


  • Moderator

    @svguss It might be a bit safer to move the entire Vivaldi folder off of the RAM disk, update it, and then move it back. The reasoning here is that (very rarely) the data structure of the User Data folder does change.



  • @lonm I use Radeon RAMDISK, the free version is fine for me. Never had any problems with it. Now that Vivaldi has synchronization, a sudden loss of power is not a concern (I didn't want to lose my History file, mainly). I find that with a fresh install Vivaldy runs similarly quickly on an SSD and RAM, but after some time the browser on SSD gets slower and on RAM it never does.

    @Ayespy OK, I'll do it that way then. Thank you!



  • I’ve used procmon to see what the installer does and may have found a workaround.

    The 50MB installer first copies a VIVALDI.PACKED.7Z archive in the (hard disk) %TEMP% folder, then unpacks this to a 200MB vivaldi.7z file in a Temp folder next to the Vivaldi Application folder (so on your RAM drive), before updating the installation from this.

    You can move that second 200MB file on your hard disk also, by creating a junction point beforehand; e.g. by running this from the Vivaldi folder (the parent of both Application and User Data):

    mkdir %temp%\Vivaldi-Temp
    mklink /j Temp %temp%\Vivaldi-Temp
    

    The installer will even clean this up at the end (so repeat the last command before each update).



  • I use the spartan ImDisk RAM drive.



  • @dantesoft man, it's almost Greek to me. I know there is the Terminal (is it called Command line?), but how do I start it from the Vivaldi folder and when?... could you please describe it in steps for computer illiterate like me? Say the temp folder is where it is always, on C: and the Ram Disk is R:
    I'd appreciate it greatly



  • @svguss In Vivaldi, go to the Help menu and select About, and copy the Profile Path to the clipboard, to be used below (it will be something like R:\Vivaldi-Folder\User Data\Default).

    Start a command prompt (by running cmd.exe) and run in order these 4 commands (pressing Enter after each one), only instead of typing R:\Vivaldi-Folder\User Data\Default just paste the path you copied from Vivaldi (by right-clicking the black command window):

    mkdir c:\Vivaldi-Temp
    cd /d R:\Vivaldi-Folder\User Data\Default
    cd ..\..
    mklink /j Temp c:\Vivaldi-Temp
    


  • @dantesoft Thank you! I'll try it when the next snapshot comes out.
    PS Will I have to do it once, or every time I update Vivaldi?



  • You will need to do it every time, because the Vivaldi installer doesn’t know/care about this workaround, and at the end it deletes all temporary files (including the temporary folder on the hard drive).



  • @dantesoft I realized I don't understand one more thing - when do I run the installer, before this Command Prompt procedure or after?



  • I have no idea why installer doesn't check available disk space before extracting data but it stops with "extracting error" instead.
    This is totally user-unfriendly...



  • @svguss Run the Vivaldi installer after the executing the Prompt commands.



  • @rotfl Agreed. Should we flip a coin on who to write up a bug report? :)

    On the other hand, unpacking the new files on the same drive as the installation minimizes the time it takes to install (as it’s now a Move File operation instead of a potential Copy File).



  • @dantesoft said in Updating Vivaldi on a small sized RAM disk:

    Should we flip a coin on who to write up a bug report? :)

    As You wish...
    But I think that priority of this issue will be low, so consider for example adding it to "Feature requests"...



  • @dantesoft said in Updating Vivaldi on a small sized RAM disk:

    @svguss Run the Vivaldi installer after the executing the Prompt commands.

    Thanks!



  • @rotfl said

    As You wish...

    I rolled a 4 on my first visit to https://www.random.org/dice/?num=1
    Unless you get a 5 or a 6, you should write it up :p


Log in to reply
 

Looks like your connection to Vivaldi Forum was lost, please wait while we try to reconnect.