I seem to have put this in the wrong place before, so here it is in the correct area I hope
I have been working on an Air app in cs4. The version of Air is 1.5.
For some of the features in Air that would make things easyer for me, I need to upgrade.
So I downloaded cs6 to test out as it has Air 3.2
Problem I have found is that my project crashes the PC every time the compiler catch's an error. Any error.
I also reinstalled in case it was a bad install.
My system stats are : XP Prp 32bit sp3 with 3GB ram and all the latest updates.
possible problems include,
-having a bad sector on your harddrive- hdds mainly last 3-4 years, past that and they can have gradual minor read failures and become slower etc. and your running a 10+ yr OS so that gives some flags
-since you have reinstalled flash the problem may lie in adobe air, as you compile or publish anything for mobile it uses the air sdk so you may want to update the SDK as well as the air software just incase the flash install doesn't overwrite once installed.
-the problem could be caused from the OS, but theres no way to know without reinstalling windows.
-if you downloaded it online and are reinstalling it from the same download you may want to redownload the original cs6 file. also you could always call your ISP and ask them if you have a high packet loss or google for ways to find out yourself, your internet connection doesn't have to show any signs of problems for you to have a high packet loss, files will still download but tiny fragments will be corrupted in turn not functon correctly
TBH, I do think it is your adobe air install, replace files in your program files/adobe/flashcs6 with the new sdk ones just in case and update air
Firstly I must say that my OS has nothing wrong with it.
I like xpPro as it is the best out there. I will wait and see how win7 and 8 do before deciding to move.
If it is the instilation that might be "worn out", I periodicaly wipe my drive and reinstall so as to have the best setup possible. I also use windows steady state so I know that there will be no bug's lingering after a full boot.
(though I do not do a full boot every time whitch is true).
As for flash, I did download it from the site twice. Once as the "Master Collection" and again as a standalone download to test different instals. They both are the same.
As you sagested, I also re done Air. I un-instaled it first and then downloaded it and re-instaled it. The SDK was current.
On a side note, my flash cs4 has now stopped compiling. It goes through the motions and then nothing. Just a file with nothing in it.
The only thing off the top of my head would be that the Flash compiler is to blame.
I have not tested it with a normal flash doc yet as have only now thought about it while writing this, and if it did not work, would crash this message as well as the pc.
So Will do later though.
ok done a quick test...... only the AIr aps crash the computor, so what is it with Air????
I did think that it might have been depricated functions in Air, but that would not account for the standard errors.
That would only point to it being in the Air compile script.
ok people UPDATE
I have upgraded my PC lately to win7 x64.
I thought that I would test cs6 again on my new comp.
STILL not working in air3.2..... but not crashing the PC though.
Comes up with "Test Movie Launch Failed".
Strang thou that it still works in air2.5 ????
The only thing I can think of is that there are some scripts that might be depricated in 3.2 that might be coasing it as I did writ the program in 1.5 ..... any ideas??
Found the problem I think....
the " *-app.xml " file.
It seems that you must delete the .xml and the .swf file that is with the .fla
For some reson un explainable, flash will not over write an older format file ??????
So now it has created its own NEW ones.... it seems to be working.
Will update if it stops again, but till then, hope this might help others.
Hey Spacebaloon!!!! Thanks for posting your findings. You just saved me HOURS. I had the same issue (on Mac 10.7, Flash cs6), and like you, reinstalled Flash. Strangely, I had been compiling for Android and IOS, both AIR with no problems like this. It was only when I compiled to AIR Desktop that this issue started up - I wanted to leave this finding for others. I was about to explore reinstalling the AIR sdk when I found your post...all I can say, is thank you, SIR.
PS Other facts, using AIR 3.2. 3.4 and 3.7 - issue was the same across the board.