Activity for Archivist_Goals
-
Archivist_Goals modified a comment on discussion Help
Hi there - though some time has passed since this. I wanted to circle back and provide an update. I did manage to successfully automate VVV via PowerShell scripting to have it iterate through all drives and maintains a json file to track progress. All scheduled via Task Scheduler in Windows. This produces daily "snapshots" with timestamped files/folders. Works pretty well. Cheers!
-
Hi there - though some time has passed since this. I wanted to circle back and provide an update. I did manage to successfully automate VVV via PowerShell scripting to have it iterate through all drives and maintains a json file to track progress. All scheduled via Task Scheduler in Windows. This produces daily "snapshots" with timestamped files/folders. Works pretty well. Cheers!
-
Thanks again for your patience, yes, I sent you an email tonight with a screen recording of some new behavior/errors. -Nick
-
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
-
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...
-
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"...
-
Hey there - did you have a chance to look at this further? Thanks.
-
No worries. Please let me know what you find out. Thanks!
-
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.
-
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
-
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...
1
