terrypin wrote:No. I had no idea what versions of the many scripts were installed. From the illustration below you can see the current status. When I upgraded from v3 to v4, I thought I was making a smart move by copying across all the scripts I could find. Clearly not! But shouldn't the v4 install have handled the scripts too?
terrypin wrote:I must have screwed up my script files or their location in some way.
Well, older versions (especially
some whole number jumps) can turn out to not work or be unstable. Also, simply copying over stuff from one regular install to another
isn't a great idea (unless you know what you're doing, not saying you don't, but...). Copying over stuff from one to the other works better/is safer/easier with the portable install.
terrypin wrote:Meanwhile any insights into which VBS file I'm seeking, its correct folder, and how my mistake could cause such a catastrophic loss would be appreciated please.
You could try renaming that old Backup script and there are other things you could do, but honestly, I would just try to correct all the copying over of the old stuff.
In other words, open MM to see if you can uninstall any suspect scripts from the GUI first (like backup) > shutdown/restart > see if problem persists.
If it does persist > get back to me (keep it in the forum if you can, but PM me if you feel the need).
terrypin wrote:OK, I'll see what happens after I've tracked down and installed Backup 6. Doesn't the installation program do any legwork on updating scripts
Do the above suggestion first.
terrypin wrote:Many thanks for the prompt reply and the hand-holding on this topic, something of a black art to me!
No problem, I'm always learning myself!
[EDIT]Just saw this:
terrypin wrote:Edit: Installed Backup v6. Maybe I'm being over picky, but wouldn't it be sensible to give scripts meaningful names, such as backup-6.vbs instead of the ambiguous backup.vbs ?
Did it improve anything?
[quote="terrypin"]No. I had no idea what versions of the many scripts were installed. From the illustration below you can see the current status. When I upgraded from v3 to v4, I thought I was making a smart move by copying across all the scripts I could find. Clearly not! But shouldn't the v4 install have handled the scripts too?[/quote]
[quote="terrypin"]I must have screwed up my script files or their location in some way.[/quote]
Well, older versions (especially [i]some[/i] whole number jumps) can turn out to not work or be unstable. Also, simply copying over stuff from one regular install to another
isn't a great idea (unless you know what you're doing, not saying you don't, but...). Copying over stuff from one to the other works better/is safer/easier with the portable install.
[quote="terrypin"]Meanwhile any insights into which VBS file I'm seeking, its correct folder, and how my mistake could cause such a catastrophic loss would be appreciated please.[/quote]
You could try renaming that old Backup script and there are other things you could do, but honestly, I would just try to correct all the copying over of the old stuff.
In other words, open MM to see if you can uninstall any suspect scripts from the GUI first (like backup) > shutdown/restart > see if problem persists.
If it does persist > get back to me (keep it in the forum if you can, but PM me if you feel the need).
[quote="terrypin"]OK, I'll see what happens after I've tracked down and installed Backup 6. Doesn't the installation program do any legwork on updating scripts[/quote]
Do the above suggestion first.
[quote="terrypin"]Many thanks for the prompt reply and the hand-holding on this topic, something of a black art to me![/quote]
No problem, I'm always learning myself!
[EDIT]Just saw this:
[quote="terrypin"]Edit: Installed Backup v6. Maybe I'm being over picky, but wouldn't it be sensible to give scripts meaningful names, such as backup-6.vbs instead of the ambiguous backup.vbs ?[/quote]
Did it improve anything?
