VVV (Virtual Volumes View) Activity
Brought to you by:
fsenore
Activity for VVV (Virtual Volumes View)
-
Fulvio Senore committed [r478] on Code
Added png icons that can be used to create a Linux launcher.
-
Add icons to the Linux distribution archive
-
Add icons to the Linux distribution archive
-
Sorry for the delay. I have looked at the source code and the program already ignores symlinks: they are stored as 0-byte files. I made that change in 2008 with revision 262: "Now the program stores symlinks to files or folders as zero length files, instead of deferencing the link.". Since you wrote in an email that you have experience working with C toolchains maybe building the program and debugging it with the volume that causes problems might be a good solution. Please let me know if you need...
-
Changes to the InnoSetup script.
-
Changed version to 1.5.0.3. This Windows version is built with wxWidgets 3.2.2.1.
-
Fix to compile with wxWidgets 3.2.
-
Changes to the InnoSetup script because I am using a new code signing certificate.
-
Archivist_Goals posted a comment on discussion Help
Thanks again for your patience, yes, I sent you an email tonight with a screen recording of some new behavior/errors. -Nick
-
Hello Nick, did you receive the email that I sent you on May 13?
-
Changed version to 1.5.0.2.
-
Added checks for command line correctness.
-
Hmm, interesting. Sure, I'd be happy to help test a new release. If you want, you can email me: archivist.goals@gmail.com Thanks for taking an interest in this! -Nick
-
Looking at your last screenshots I noticed that now the error message is different: it is about a missing catalog name and not a missing file. Looking at the source code, that error should happen if the program has not received a catalog name. That does not make sense so maybe there is a problem with parsing the command line. I might prepare a new version with better handling of the command line parsing, just to see if there are problems. Are you interested in testing it?
-
fsenore: Any further thoughts or suggestions?
-
Yes, I tried just now. New CMD instance running as administrator. Still the same error. See screenshot. Also including screenshot of the VVV catalog. As you see, I have C , then the other drives. Only C and Drive D are internal. The others were external drives. I'm running Windows 11 Pro. Again, running this command works and opens up the GUI: "C:\Program Files (x86)\VVV (Virtual Volumes View)\vvv.exe" "C:\VVVCatalogs.vvv" The other one, even with CMD in Admin mode, fails. Strange, indeed. If you...
-
Yes, I tried just now. New CMD instance running as administrator. Still the same error. See screenshot. Also including screenshot of the VVV catalog. As you see, I have C , then the other drives. Only C and Drive D are internal. The others were external drives. I'm running Windows 11 Pro. Again, running this command works and opens up the GUI: "C:\Program Files (x86)\VVV (Virtual Volumes View)\vvv.exe" "C:\VVVCatalogs.vvv" Other one one, even with CMD in Admin mode, fails. Strange, indeed. If you...
-
Yes, I tried just now. New CMD instance running as administrator. Still the same error. See screenshot. Also including screenshot of the VVV catalog. As you see, I have C , then the other drives. Only C and Drive D are internal. The others were external drives. Again, running this command works and opens up the GUI: "C:\Program Files (x86)\VVV (Virtual Volumes View)\vvv.exe" "C:\VVVCatalogs.vvv" Other one one, even with CMD in Admin mode, fails. Strange, indeed. If you want, I can do a Zoom screenshare...
-
Yes, I tried just now. New CMD instance running as administrator. Still the same error. See screenshot. Also including screenshot of the VVV catalog. As you see, I have C , then the other drives. Only C and Drive D are internal. The others were external drives. Again, running this command works and opens up the GUI: "C:\Program Files (x86)\VVV (Virtual Volumes View)\vvv.exe" "C:\VVVCatalogs.vvv" Other one one, even with CMD in Admin mode, fails. Strange, indeed. If you want, I can do a Zoom screenshare...
-
This is really strange. Have you tried running the command prompt as an administrator? https://www.howtogeek.com/194041/how-to-open-the-command-prompt-as-administrator-in-windows-10/
-
I recently did a clean install of Windows. And this time around chose a more suitable user name without special characters. Testing everything again, with the following catalog location and argument did work and opened the catalog GUI, yes: C:\VVVCatalogs.vvv And with this argument: "C:\Program Files (x86)\VVV (Virtual Volumes View)\vvv.exe" "C:\VVVCatalogs.vvv" However, I can not get the argument for updating a volume to work, using this: "C:\Program Files (x86)\VVV (Virtual Volumes View)\vvv.exe"...
-
I recently did a clean install of Windows. And this time around chose a more suitable user name without special characters. Testing everything again, with the following catalog location and argument did work and opened the catalog GUI, yes: C:\VVVCatalogs.vvv And with this argument: "C:\Program Files (x86)\VVV (Virtual Volumes View)\vvv.exe" "C:\VVVCatalogs.vvv" However, I can not get the argument for updating a volume to work, using this: "C:\Program Files (x86)\VVV (Virtual Volumes View)\vvv.exe"...
-
I was just looking at your problem. I checked and everything worked well: I was able to update a volume from the command line. I was able to get the same error message as yours when I forgot to close VVV: it was in execution as a GUI program. VVV locks the catalog file so if you try to open the same catalog with another instance of the program you get a "catalog not found error". That error is a generic I/O error: it is usually caused by a wrong filename but it can also be caused by a permission...
-
Hey there - did you have a chance to look at this further? Thanks.
-
Updated the copyright year to 2024.
-
Changed version to 1.5.0.1.
-
Fixed: when adding the same physical folders to different virtual folders the virtual folders structure could be corrupted.
-
Updated the Portuguese translation.
-
No worries. Please let me know what you find out. Thanks!
-
I am leaving for holidays and I will be back on April 8. Then I will make some tests.
-
Thanks - I thought about that with the # character (poor choice during initial Windows setup) Giving it full access in C:\ requires having full ownership of C:\ and, from what I understand, might cause system instability. So, rather not do that. I also have Drive D. Placing the catalog, DriveD.vvv in D:\ is still not recognized, same error. Not sure what else to try.
-
Thanks - I thought about that with the # character (poor choice during initial Windows setup) Giving it full access in C:\ requires having full ownership of C:\ and, from what I understand, might cause system instability. So, rather not doing that. I also have Drive D. Placing the catalog, DriveD.vvv in D:\ is still not recognized, same error. Not sure what else to try.
-
Maybe the problem is in the "#" character in the database path. I would try putting the database in a simpler path like "C:\VVVCatalogs" and giving it full access rights, just to see if it works. Fulvio
-
Hey Fulvio, thank you. I ran the the first command you suggested and the file name is, indeed, correct. Without any errors. Running the second command you suggested, I still receive the following error, "Catalog not found" Not sure why this happens. In the catalog file. I have multiple drives listed, including Drive C. So, not sure why this error persists. -Nick
-
Hey Fulvio, thank you. I ran the the first command you suggested and the file name is, indeed, correct. Without any errors. Running the second command you suggested, I still receive the following error, "Catalog not found" Not sure why this happens. In the catalog file. I have multiple drives listed, including Drive C. So, not sure why this error persists. -Nick
-
Hey Fulvio, thank you. I ran the the first command you suggested and the file name is, indeed, correct. Without any errors. Running the second command you suggested, I still receive the following error, "The catalog name is missing" Not sure why this happens. In the catalog file. I have multiple drives listed, including Drive C. So, not sure why this error persists. -Nick
-
You can check that the file name is correct by entering the following line in a command prompt: dir "C:\" "C:\Users\Nick-PC#2\Desktop\VVVCatalogDatabase.vvv" and checking for errors. Another possibility is that the executable, when ran from the task scheduler, does not have access to the catalog file. May you try using the command line "C:\Program Files (x86)\VVV (Virtual Volumes View)\vvv.exe" -u -v "C" -vp "C:\" "C:\Users\Nick-PC#2\Desktop\VVVCatalogDatabase.vvv" to see if it works? Fulvio
-
This is directed at Fulvio: Hi there - I am trying to automate VVV so that I can use Windows' built in Task Scheduler to open a script periodically and have that update Cataloged volume files. Basically, I am looking for a way to use VVV to update snapshots of already-cataloged volumes (Drives). So, for Drive C, run a VVV command and update that volume with any new changes made to the Drive (entire C:\ directory) since the last run of VVV. I keep running into, "This catalog file does not exist" even...
-
tommie de pommie posted a comment on discussion Help
Thank You Fulvio. That was the solution. Great program BTW.
-
The configuration file is named ".VVV" and it is located in the user's home directory. It is a hidden file. You can open it with a text editor: look at the "Settings/DatabaseServer" section and change ConnectToServer=0 Fulvio
-
Hello, I have installed VVV catalog on Linux Mint and it was working fine. I installed Firebird on my Qnap but after activating the server connection, I can't go back. When I open ./vvv-start.sh I get an SQL error. I can only open vvv-start.sh as root. REmoved the complete directory and reinstalled VVV but still the same. Can you tell me where the VVV config file on Linux is located so I can start from scratch? Thank you. Tom
-
hmijail posted a comment on discussion Open Discussion
When searching for (e.g.) "this is a test", the search results include every file with "this" in the title, OR "is" in the title, OR "a" in the title, etc. This makes it very difficult to search for anything more complex than a single word. It would be great if the search could be made to use the full string at once, for example by using a quoted string (just like e.g. Google does). Or it could be using syntax like "this AND is AND a AND test" (again like Google)
-
Hi there. As mentioned by email a few weeks ago (sorry for the delay!), I tried cataloging an external HD, and it ended with errors "(error 2: No such file or directory)". All the files mentioned in the errors are broken symlinks. At the end of the scan, the folder information for the root of the catalog says it contains 1500 GB, but the OS says that the disk contains 1800 GB. So I suspect that the errors caused the catalog to be incomplete. So it would be great to have an option so that VVV would...
-
Not at the moment. It would require a large amount of work and I am not sure that MySql has an embedded version to ship with the program.
-
Mateus Machado modified a comment on a blog post
Thank you so much. I aprreciate this software. Could you add MySQl suport for it?
-
Thansk you so much. I aprreciate this software. Could you add MySQl suport for it?
-
Kempelen posted a comment on a blog post
I use VVV every day, so it's wonderful to see an update! Thank you!
-
Dan French posted a comment on a blog post
wow - thanx a lot - really good news Stefano! great!
-
ARtEcnico posted a comment on a blog post
Great news this program is still maintained! Thanks for the new release!
-
Updated the website.
-
Virtual Volumes View 1.5 released
-
VVV (Virtual Volumes View) released /VVV/1.5/VVV-1.5-x86_64.dmg
-
-
-
-
Updated the OSX installation script.
-
Updated the Linux distribution creation script.
-
Updated the InnoSetup script with new version number.
-
Changed version number to 1.5.
-
Updates to handle the Chines translation, credit to translators.
-
Updated the Italian translation.
-
Update CMakeList.txt to correctly handle the Traditional Chinese language.
-
Updated some translations.
-
Added an empty Swedish translation.
-
Added to the translation files new strings to be translated.
-
It will take some time before an official release, so I can give you a test version if you want. Which operating system are you using?
-
Error opening a file under Linux
-
It looks like this problem has been fixed in the latest version of wxWidgets.
-
Updated the Russian translation. Thanks to Vyacheslav Dikonov.
-
Hello, and sorry for the delay. I am working again at VVV and I will be glad to add your translation to the next version. Fulvio
-
Open with default program
-
Show total files number
-
Store the unused space in volumes
-
Fixed in revision 455.
-
seg fault when using a existing name in the catalog dialog
-
Open-Button in Catalog Dialog
-
merging
-
Importing catalog
-
Firebird 4 or 5
-
Fixed: the program crashed if the user cataloged a volume using an existing name.
-
Updated copyright and web link in the About dialog.
-
Changes to the web pages to use Google AdSense.
-
John modified a comment on discussion Open Discussion
Since there is no way to comment in a closed ticket, I report this in here. #84 and #90 are now implemented in the latest source thanks to the developer. I tried to build the latest trunk code. but it seems I failed in preparing taglib. tagd.lib under lib was not made. Because of that or not, vvv failed to be compiled. I will wait for the official binary to come! Thank you.
-
Since there is no way to comment in a closed ticket, I report this in here. #84 and #90 are now implemented in the latest source thanks to the developer. I tried to build the latest trunk code. but it seems I failed in preparing taglib. tagd.lib under lib was not made. Because of that or not, vvv failed to be compiled. I will wait for the official binary! Thank you.
-
VVV almost exclusively runs firebird in embedded mode: there is no firebird installed in the computer and VVV runs firebird from a set of local libraries. Updating the firebird engine to a newer version means that users could not read their catalogs any more unless some conversion is made. Clearly this is not an option. You ought to be able to upgrade a database by making a backup from VVV and restoring it in a newer version of firebird.
-
Copyable object names
-
Fixed in revision 450. Now it is possible to copy info from the "File information" window.
-
Copy path
-
Fixed in revision 450. Now it is possible to copy info from the "File information" window.
-
Copy Text From Object Information
-
Fixed in revision 450.
-
copy file name etc
-
Fixed in revision 450. Now it is possible to copy info from the "File information" window.
-
Save search settings
-
Fixed in revision 452.
-
Now the program remembers a search setting between "All physical volumes" and "Selected physical folder. It does not remember the "Selected virtual folder" setting because at startup there is no selected virtual folder.
-
Removed the "New root folder" context menu from the left pane in virtual mode. It is rarely used and it is still available from the main menu.
-
Now in the "File Information" dialog it is possible to copy data to the clipboard with a context menu or by typing Ctrl+C.
-
Murphy91 created ticket #93
Firebird 4 or 5
-
md5sum
1 >