Comments

Former user wrote on 5/30/2020, 1:35 PM

Are you trying to install it on the V drive?

digilyd wrote on 5/30/2020, 2:44 PM

NO! - I have my videofiles on the V-drive on all pc's because then projects are easy to move. I have the software on the C-drive in default folders. And the drive is is present and not asleep.

j-v wrote on 5/30/2020, 3:01 PM

Maybe in this case it is better not to upgrade a former build but deïnstall the program first, restart and than install the new build fresh.

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W10 home version 2004 build 19041.264, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti.
Laptop  :Asus ROG GL753VD, W10 home version 2004 build 19041.264, CPU i7 7700HQ, 8 GB RAM, GeF. GTX 1050 (2 GB) + Int. HD Graphics 630(2GB).VP 16,17 and VMS PL 16,17 are installed, all latest builds
Both Nvidia GPU's have driver version 451.48 Studio Driver, desktop the Studio DHC driver
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEMCELL DONOR !!!

digilyd wrote on 5/30/2020, 4:29 PM

This type of upgrade has always worked flawlessly. There have been one previous install oddity with an accompanying program, but only in the first build of 17. And it is not the softwares business whether a datadrive is present -  nor whether it is in-box, external or network - usually faster than external - it can always ask after the upgrade if in doubt. It is nowadays better to use a network-drive than to run simultaneous read and write on the same drive and it is twice as fast to use a network drive than to use a USB3 drive. When working with 4k it is a lost cause to try to keep all datafiles in the box, storage has to be flexible and structured. And the new build is complaining that a drive that IS available "does not exist".

 

 

digilyd wrote on 5/31/2020, 2:30 AM

Thank you, interesting story of quirks. It does however not seem to be to the point, build 421 is installed on this box and running and works fine, which it wouldn't if any of those causes applied. Also the box is only a few months old and capable and well working. 

Checked to be overcomplete .net is activated. SMB1 was not, a known quirk that is sensible, but impractical with an xp-box still in use, fixed that, nice that it could be done without registry editing.

john_dennis wrote on 5/31/2020, 2:29 PM

@digilyd

[Techno-Philosophical Nonsense of the Day]

SMB is a double-bind for Microsoft. If they disable it by default some old organization like a financial institution, poorly funded healthcare or law enforcement organization will have antiquated "mission critical" applications that won't work after an upgrade. If the leave it on by default, every user in the known universe is exposed to exploitation even though few people absolutely, positively must use it.

[/Techno-Philosophical Nonsense of the Day]

Tried to fix @ targeting. Let's see what happens.

digilyd wrote on 6/1/2020, 12:20 AM

True, on my previous day job I would have loved the disabling of it just to get a lower risk, but with windows breaking my preferred audio software I keep my xp-box runnable and I also need to have my NAS-drives mountable. However, let us not derail this …. I checked if there could be any pointer to drive V: in the current setup of 17 and I can not find any.

Anyway, just checked whether going via a new install download as if with a first time install would update properly, nah … same errornumber, -21 ….. a negative number to me suggests a numeric overflow. since it says it can  not find an  actually existing drive via its letter it seems to a an untrapped (do'h!) division by zero. It could have been a different install flow, but wasn't.

Hey MAAaAgIIIIIIixX … are you listening??? - seems like ya made a 4 am error! - checked whether the download was copied correctly to the magix downloads folder by the installer, no, it is not there. And that folder is in the My Documents folder, a relocateable systemfolder with a system variable pointing at it. And it is on drive V: because it is a mirrored drive in my local cloudserver. So now I know what is broken  ….. btw. the error message refers to drive V: as drive V:\ - now that way of writing it refers not to the drive, but to the root directory of the drive …. ???

Leading to the question of whether the relocation string from the OS for the localized folder name "Dokumenter" is parsed incorrectly? - the answer is YES. Temporarily relocating the "My Documents" folder to default location fixed it. That makes it the second time I have found an OS stringparsing error in Vegas 17's install routine, there was also one - regarding Boris - in the initial release.

digilyd wrote on 6/1/2020, 1:06 AM

Note what is broken seems to be the move of the downloaded file to storage in the magix install folder in the My Documents folder, so it is the install that is broken also this time, someones understanding of windows needs enhancing, also the software testers so that they find such a fault.

NickHope wrote on 6/1/2020, 1:42 AM

If you still didn't get updated, you can do it with this installer instead of the automated process: http://dl04.magix.net/2019/VEGASPro17/VEGAS_POST_17.0.0.452_DE-EN-FR-ES.exe

digilyd wrote on 6/1/2020, 1:51 AM

Thank you Nick, it was the folder relocation that broke the move of the downloaded file by the installer to magix installs folder in My Documents as explained above, otherwise that file would have been needed, thoughtful of you!

 

john_dennis wrote on 6/1/2020, 1:52 AM

[Second Techno-Philosophical Nonsense of the Day]

'splane to me again why we need a download manager.

[Second Techno-Philosophical Nonsense of the Day]

digilyd wrote on 6/1/2020, 2:29 AM

The concept came into being because browsers used to be unable to resume a download if interrupted, I think it remained popular because it allows a fast initial download.

michael-harrison wrote on 6/1/2020, 3:08 AM

I don't understand the fix as you describe it.

Did you have a bad installer or did you 'fix' the problem by moving the installer to a different folder?

 

digilyd wrote on 6/1/2020, 5:42 PM

The windows operating system allows you to move the system folders, all of them actually as far as I know, including the My Documents folder to any folder with any name. This is because there is a system variable that points to the location you specify. The install program does not parse these system variables correct and thus having a relocated My Documents folder broke the install because the first thing the install program does after downloading is to move the file to install to a subfolder in the My Documents folder. Windows is a lot better and a lot more capable and a lot more configurable and much documented than many understand. All you need to pass a certification test is in the OS helpfiles. It is strongly adviced to simply read them. They are the user manual.

fifonik wrote on 6/1/2020, 8:21 PM

I'd say moving such folders is a bad idea. If you really need to release some space on your system drive and would like to move the content of such molders somewhere, you should use junctions instead.

Camcorder: Panasonic X920

Desktop: MB: MSI B450M MORTAR TITANIUM, CPU: AMD Ryzen 3700X (not OC), RAM: G'Skill 16 GB DDR4@3200 (not OC), Graphics card: MSI RX580 8GB (factory OC), SSD: Samsung 970 Evo+ NVMe 500MB (OS), HDDs: Seagate & Toshiba 2TB, OS: Windows 10 Pro 1909

NLE: Vegas Pro [Edit] 11, 12, 13, 15, 17

NickHope wrote on 6/2/2020, 12:42 AM

My Windows Documents, Downloads, Music, Pictures & Videos folders have not been in the default location on my desktop or laptop PCs for many years. In fact I moved them the other day to be within my Dropbox folder, since I subscribed to the 2TB version of Dropbox. It's never been a problem but obviously they need moving via the right procedure.

On the occasions that I have installed a VEGAS product using a VEGAS "dlm" download manager, the installation has dealt fine with my Documents folder being at, for example, D:\Documents.

digilyd wrote on 6/2/2020, 11:59 AM

I'd say moving such folders is a bad idea. If you really need to release some space on your system drive and would like to move the content of such molders somewhere, you should use junctions instead.


As MCSE I disagree, the folder relocation is an essential part of the OS being network focused, to the local cloud they go so that the workstation can be freely replaced and formatted. As Nick says, it is usually unproblematic, with V17 installs, this is the second time it is has shown itself to be A problem, not for Vegas, but for the installation program.

 

john_dennis wrote on 6/2/2020, 2:32 PM

On two systems that I "share" with my wife, I relocate the Desktop, Documents, etc. to another local disk. Doing so allows me to swap the boot systems without worrying about deleting any of her "stuff". Recently, I chose to undo that configuration long enough to build a VMWare virtual machine of our "office" PC, but put it back when I had a good VM. Some day, the system will break and it's so old the hardware won't be available. On editing machines, I leave user folders on C: but don't use them for anything. I've looked at junctions, but I have so many system images that implementing junctions would be more trouble than it's worth for a single user workstation. I find relocating these user folders useful for family members who perceive of me as their personal on-call hardware/software tech support person.

When a new release of Magix software is available, I usually download the full installation package without using download manager. if possible. If I have to use download manager, I watch where it downloads and move the installation file before I attempt to install Vegas.

Check this Out!

fifonik wrote on 6/2/2020, 7:04 PM

As Nick says, it is usually unproblematic

Keyword is usually :)

I faced too many issues caused by folder relocation in my career.

Sure, in business environment when programs set is limited and mostly it is MS products or major brands products are user -- this works fine OK.

Camcorder: Panasonic X920

Desktop: MB: MSI B450M MORTAR TITANIUM, CPU: AMD Ryzen 3700X (not OC), RAM: G'Skill 16 GB DDR4@3200 (not OC), Graphics card: MSI RX580 8GB (factory OC), SSD: Samsung 970 Evo+ NVMe 500MB (OS), HDDs: Seagate & Toshiba 2TB, OS: Windows 10 Pro 1909

NLE: Vegas Pro [Edit] 11, 12, 13, 15, 17

digilyd wrote on 6/3/2020, 2:14 PM

I'd say moving such folders is a bad idea. If you really need to release some space on your system drive and would like to move the content of such molders somewhere, you should use junctions instead.

I do not want user data on the drive windows is on. I want to be able to format it with no data loss. Also, since this is the real world, this quite new box has windows on a SSD, at 1 terabyte it is way too small to have user data on anywat,  so even IF they were not on my own local cloud, they would be relocated and it would be proper windows practice to so do. And this is a production computer, it is reasonably lean, it is not a "do all" box. Seems to me that you focus on my using the properties of the OS instead of on the documented error in the install program.

Musicvid wrote on 6/4/2020, 10:50 AM

The error number you posted is known. Type it in a forum Search box.

digilyd wrote on 6/5/2020, 6:44 AM

Thank you, the requester also said it in plain text, but nice to know another time, very useful, thank you! - The error was that there was no error handler displaying a requester saying that "i can't find your My Documents folder, where do you want the install archive placed?" - the underlying issue being that someone had not considered that a user might right click on the My Documents folder and ask for it to move somewhere more sensible than the drive with the OS on it. not even an advanced relocation via Active Directory. And it is 20 years ago that technology was implemented, so even that should be well known by now. Things happen, and it is NOT a Vegas error, it is an install program error.