Archived

This topic is now archived and is closed to further replies.

bobbyjack

EditVoicePack 4 Error

Recommended Posts

Hello everyone,Everytime I try to update the FSX Voicepack using EVP 4 CTP 2, I get this error:Error updating voicepack file:Access to the path 'C:Program Files (x86)Microsoft GamesMicrosoft Flight Simulator XSoundATCEvpAccelerating.tmp' is denied.Why is this, and how can I fix it?Thanks,

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

Hello BoeingGuy!EVP4 does not work on Vista. Are you running Vista?Sincerely,Dennis D. Mullert

Share this post


Link to post
Share on other sites

Hi Dennis,Oh, I think that's it. Bummer. Thanks anyways! Does this mean I can't use custom airlines?Thanks,

Share this post


Link to post
Share on other sites

That's what it means. I think parts of it work. But it is more that it is not finished for FSX yet, than a Vista problem. I have my own airlines and airports that I dearly wish atc could call, but no go.Bob

Share this post


Link to post
Share on other sites

Try using EVP3 on Vista. See if that works. Do you know if EVP3 works in Vista?I still use EVP3 on WinXP, with FSX. I have plenty of custom callsigns and ICAO's in my FSX because of this.RhettAMD 3700+ (@2585 mhz), eVGA 7800GT 256 (Guru3D 93.71), ASUS A8N-E, PC Power 510 SLI, 2gb Corsair XMS 3-3-3-8 (1T), WD 150 gig 10000rpm Raptor, WD 250gig 7200rpm SATA2, Seagate 120gb 5400 rpm external HD, CoolerMaster Praetorian

Share this post


Link to post
Share on other sites

As I understand it, FS9 can use more than one voicepak(or somthing like that). I believe you can create your custom voicepak in EVP3, than import it into FSX, so that you can have custom callsigns, but then you have to delete the original FSX pak because FSX will read only one or the other. I believe that means callsigns for new airports(new in FSX) and any new atc (if there is any ) will be gone. That's the last I heard ,anyway. I think I'd rather wait for something FSX compliant. I hear of too many problems porting FS9 things into FSX.Bob

Share this post


Link to post
Share on other sites

Lars is quite correct. All you need to do is "give yourself permission in Vista" to use your own bloody system......now you can understand WHY I believe it's a "Bad Idea" to install FS(any version) to the default path on a Vista machine. :)

Share this post


Link to post
Share on other sites

But all you have to do is turn off UAC and everything works fine. EVP4 is not a complete program. What is there works fine in Vista. Bob

Share this post


Link to post
Share on other sites

>But all you have to do is turn off UAC and everything works>fine. EVP4 is not a complete program. What is there works fine>in Vista. Isnt' that just what I said, more or less? You have to "give yourself permission to use your own bloody system!" :)Of course EVP4 works with Vista. I've been using it since it was first put up for evaluation.

Share this post


Link to post
Share on other sites

YES! That was it! Thanks everyone! I just had to give myself permission, then use the right-click and Run as Administrator option. Geez, this is so irritating. Why make Vista so secure to the point of obnoxiousness?Thanks everyone!

Share this post


Link to post
Share on other sites

I do agree with you. Kind of like all the passwords I have to put in to use my " own bloody system" :-)Bob

Share this post


Link to post
Share on other sites