Comments

LivingTheDream wrote on 8/2/2011, 5:54 PM
"I don't know, but it's 19 days and counting. ;-( "


My guess is you have 10 more days to go. . .



Steve
TomG wrote on 8/3/2011, 5:47 AM
My daycount is now up to 14 with no response.

This was the first time I posted a question in the 8 years I have been using Vegas and I'm just very disappointed that whiel Sony indicates that they will help, the only place many requests go seems to be the bit bucket...

TomG
TomG wrote on 8/11/2011, 6:23 PM
Well, no response whatsoever to the problem I posted to Sony's support site on 7/19 even though I updated it 3 times and posted a .jpg with the problem visualized. This is the first time I ever tried using this service and will probably be the last.

I hope others have had better luck using this service than I did.....

TomG
Steve Mann wrote on 8/11/2011, 8:11 PM
I know you hate to hear this again, but 0x80 errors are WINDOWS errors. Specifically .net errors.

Here's something I gleaned from another forum:

1. Uninstall the DVD Architect Studio 5.0 application by navigating to your Windows 7 Control Panel
2. Download and Install the following .NET framework update directly from Microsoft: http://support.microsoft.com/kb/2468871
3. Reinstall the DVD Architect Studio 5.0 application

TomG wrote on 8/12/2011, 6:04 AM
Thanks, Steve

But my problem is with Vegas 10e. Will installing DVDA, replacing the .Net framework, and reinstalling DVDA help with that?

TomG
Steve Mann wrote on 8/12/2011, 1:08 PM
The OP was asking about errors while running DVDA.

But try the same sequence: Remove Vegas 10e, reinstall .net then reinstall Vegas 10e.

TomG wrote on 8/12/2011, 1:12 PM
OK, Steve

I'll try that but that still doesn't absolve Sony for their "no response" posture.

TomG
drmathprog wrote on 8/18/2011, 8:44 AM
Yeah, I finally got a response today, 1 month to the day after the original tech support request date.

It turns out to be a known Vegas issue currently being worked on by the Sony developement team (not a Microsoft or Windows issue, Steve Mann, but I do apprecaite your efforts).

Unhappily, the response goes on to say there is a possible work around, but instead of telling me the work around, it explains how to take and send to them a screen shot of the windows paging file size settings window. '-(

So apparently the work around involves a possible modification of the windows paging file size, in a manner yet to be revealed to me. Hopefully, the response to me screen shot will occur in less than a month. ;-)
TomG wrote on 8/18/2011, 3:48 PM
Well, Drmathprog, today was my lucky day also

Just one day from 1 month I did get a reply today. (Maybe Sony does read the Forum?) It didn't solve the problem but they did ask 3 more questions. I guess if you are not in a hurry and your business does not depend on a reply, you may eventually get some help???

TomG
drmathprog wrote on 8/18/2011, 5:41 PM
I'm just a hobbyist, so I have nothing at stake except patience. However, their response times seem much slower than most licensed software I use.
Steve Mann wrote on 8/18/2011, 8:08 PM
"So apparently the work around involves a possible modification of the windows paging file size, in a manner yet to be revealed to me."


From Windows Help:
"If you receive warnings that your virtual memory is low, you'll need to increase the minimum size of your paging file. Windows sets the initial minimum size of the paging file equal to the amount of random access memory (RAM) installed on your computer plus 300 megabytes (MB), and the maximum size equal to three times the amount of RAM installed on your computer. If you see warnings at these recommended levels, then increase the minimum and maximum sizes."

What Windows Help doesn't tell you is how to make the paging file fixed, static, unchanging. The solution is simply to open the Control Panel.

From Control Panel, Advanced Systems Settings, Advanced tab, Settings, another Advanced tab, Click on the "Change" button for Virtual Memory.
Next, Un-check the "Automatically manage Pagefiles on all drives..." box, then click on "Custom Size" and set the minimum and maximum size the same.
note, the largest pagefile size in Windows is 4095Mb.

Then "OK" your way back out. You may likely need to restart to make the changes take effect.

Windows supports up to 16 paging files, but each must be on a separate volume, so if you have more than one internal disk drive you could try enabling a Paging File on your second hard-disk. DO NOT put a paging file on an external drive because if it's not present when Windows boots, then Windows will crash.

For more information, see http://support.microsoft.com/kb/237740

Let me repeat for emphasis: The largest paging file that you can select in Windows is 4,095 megabytes (ref: kb2267427), though nothing in the Virtual Memory setup window will tell you that, or even stop you from entering a ridiculously large pagefile size. I suspect that if you make an 8Gb pagefile, and Windows tries to write more than 4Gb of data, you will likely crash with an Access Violation error.
drmathprog wrote on 8/19/2011, 4:13 AM
Thanks for the information; I'll have to give this a try. I haven't tweaked anything (with 8GB RAM I assumed there ought to be plenty to go around), so I don't know my current settings.