Adobe Air 2/Flash CS5 on Win.
I must finish 2 little desktop projects in the client office right now. I have 6 hours to do it.
I did develop and test both apps at my studio and everything was OK. Even the installer generation. The client did test the beta installers in his computer.
Now I cant preview (ctrl+enter) them in my client computer, so I can't finish the projects and I'm 3 hours far away from home.
Any idea?
UPDATE:
I did change the name of the files and..., voilà, it worked!
Weird situation this one!
Resolved:
I did change the name of both files and..., voilà, they came back to live!
Weird situation this one!
Related
While developing a Cocoa sandboxed application, I discovered that if I switched it to non sandboxed, in all the Open Panels of the application, the right click commands (Duplicate, move to trash etc.) do not work any more. I am certain they did work no more than two weeks ago, but I have reverted the project to old commits and the misbehaviour is still there. I tried everything, until I realised that this misbehaviour now appears in all my projects, if I switch them to non-sandboxed. This makes me think it may be some kind of bug introduced in 10.14.2 or something similar. I hope somebody else has experienced the same issue so that we can understand better what is going on. Thanks
P.S. I am using the latest Xcode 10.1 (10B61) and tried on several machines. It is the same misbehaviour.
The OS might be confused by having some contradicting leftover knowledge about sandboxed and non-sandboxed versions of the app with the same version / bundle ID / signature.
Some things to try:
Test the app on a fresh user account.
Delete the app sandbox container from your Home Folder > Library > Containers.
Temporarily change app bundle ID to something new to see if it’s still affected.
I have come across this particular problem several times across several versions of the IAR embedded workbench (EW430 5.40.7 [EW 6.0], EW430 5.51.2 [EW 6.4], EW430 6.20.1 [EW 7.0]), but each time only after a long period of having no problems. The problem doesn't seem to have affected the other firmware developers in the office, so no help can be offered there. I'm currently on Windows 10, but the problems first occurred when I was on Windows 8.1 (same PC.)
The problem is that, for no obvious trigger, the IAR ide will start to hang until terminated (or it will just crash on one of the EW versions) on any attempt to change the active build configuration in MSP430 projects using the emulator.
From my testing, it appears to be directly related to something the IDE is doing with the emulator, as when the build configuration is changed, I can see the emulator menu in the menu bar disappear, then the hang happens. Under normal circumstances, the menu will disappear, but then reappear once the other debug configuration is completely loaded.
I have tried the default project "flashing the LED" to see if it was only my project - but if I select the msp430x4xx (C) - Debug, right click it and select "Set as Active" from the context menu, to make this the active project, the IDE also hung. I then reopened the EW IDE, and opened the LED flashing project again. The original 1xx asm project was the active project.
I then changed the settings of the 4xx (C) Debug project (without making it the active project) from the emulator to the simulator, and clicked OK. The program did NOT crash.
I then set the 4xx (C) Debug project as the active project and it did NOT crash. The simulator even runs without problems.
The version of the FET firmware didn't change from when the IDE worked correctly to when it didn't, and the FET is not even used at this point. It can be completely disconnected and the same results will occur.
I have tried the following, without success:
erasing the files in my project folder's settings subfolder
erasing the *.dep files in the project folder.
deleting the IarIdePm.ini file from AppData\Roaming\IAR Embedded Workbench
making sure none of the project files are read-only
reinstalling the program to the same location
removing and reinstalling the program to the same location.
What does solve the problem (until it reoccurs) is to reinstall the program, but to a different directory (for e.g., the default directory will be in program files (x86)\IAR Systems\Embedded Workbench x.x. Installing again into program files (x86)\IAR Systems\EWx (just so it is different) allowed that installation to work, but the old installation continued to fail.
Best advice so far (from our support person) has been to do the above, install to another directory and live with it, as it doesn't happen often.
Since it has happened to me on 3 occasions with 3 different versions of the program, I would like to know how to fix or prevent it! If anyone could offer anything to try (or even better, a straight solution :)) that would be greatly appreciated!
Cheers!
Since newer versions and updates on W10, it seems that old compatibilities are being removed from this OS. I have no direct solution for this problem since Microsoft does not promise support for old software and hardware. Even I tried to find a solution for that problem, and I found on the IAR website a list of IDE's and their compatible versions. (remember, old versions are not compatible)
( https://www.iar.com/knowledge/support/technical-notes/ide/windows-10-and-iar-embedded-workbench/ )
You will need to update your IDE and program version to a newer version if you plan to continue to use this IDE natively on Windows 10 or you may use Virtual machines with an old operational system (like Windows 7) to compile your program on old IDE.
P.S.1 I manually uninstalled KB4592449 recently updated and the program return to work natively. Probably it will continue working until this update (or other similar) being installed again on the computer, but probably there is any vulnerability that the computer will be exposed to, and in this case, I'm paying the price.
P.S.2 KB4580325 promotes the same behavior in IAR 5.11 on windows 10. Both KB's implement securities about the flash player - that I Don't use - then, I can securely uninstall it.
P.S.3 Since I updated my windows up to Windows 10 version 21H1 (compilation 19043.1165) AND I configured Windows defender to not be monitoring IAR IDE (IarIdePM.exe) disabling all protections available, everything works fine. But Remember: my program is original, not cracked or altered by anything, then I am secure to do what I did.
It is a 'natural' that software problem. Not found way of fixing it. The solution temporary is modify manually the file .eww for change of project active. The ultimate solution is to use another development environment.
So I made a few gamemaker games about 11 years ago and tried to run the exe file.
When I run the exe file, nothing really happens just an error box pops up saying you can find out more here. And it points to 3 .tmp files located in the Temp folder on my computer.
Anyone know how to get these exe files working again?
The older versions of game maker games use an old runner that does not work with the newer versions of window (from Vista and up).
Using compatibilty mode does not fix this.
There is however a fix available that replaces the runner in the EXE with an updated one.
The tool was posted by Mark Overmars (the original creator of Game Maker) but the link in his topic is no longer active (the .zip does download but its an HTML page, not the actual tool).
http://gmc.yoyogames.com/index.php?showtopic=299895&p=2116603
It did work for me and using this program I was able to run a lot of older gm4 + games that I have played before on windows XP.
If its a must - you can always try to run it on an XP machine.
TL;DR:
There is a tool to make them work, I will upload it tonight.
EDIT: Turns out YoYoGames has the tool posted themselves;
http://help.yoyogames.com/attachments/token/lsj0pmbzqeu64hf/?name=GM_Convert_Game.zip
More information: http://help.yoyogames.com/hc/en-us/articles/216753218-Troubleshooting-Legacy-GameMaker
You can extract all the files to a directory, then drag your old .exe file onto the converter exe. It will then create a game_old.exe and game.exe and then you should be able to run the game.exe one.
My temporary developer license (using Visual Studio 2011 Beta and Windows 8 Consumer Preview) expired and a popup asked me to aply for a new one. This all seemed to work, but when I build and deploy to the local machine it takes me to the app store and tells me that the developer license has expired.
I've tried:
Unistalling my app from the home screen
Cleaning my project solution
Removing my developer license using powershell command Unregister-WindowsDeveloperLicense and getting new license again
Restarting machine
I can create new projects that build and deploy fine, but my existing project is stuffed. Is the old licence cached somewhere and how can I get it to forget about it.
There is this similar quesion on MSDN. Someone managed to solve it, but there solution has not worked for me and there are other people saying it hasn't worked for them.
The first month this happened to me, a reboot solved it. The second time it didn't. I went into my package manifest and changed the package ID. It looked like a GUID and I just put kmg on the end. Then everything worked fine. Later I tried changing it back but it failed again so I guess my package ID ends in kmg now :-)
I believe it's because you're trying to overwrite a package that was shipped by a "different developer". They're going to have to fix that somehow but hey, this is what betas ^H^H^H^H^H previews are for, right?
I have recently put together a new development machine and loaded Windows 7 64 bit and VS2010.
I copied over all my projects (VB) from the old machine which was Windows 7 x86 and VS2008.
After following the conversion wizard in VS2010 and installing a third-party component I had forgotten about, my solutions opened and executed fine on the new machine.
Then I tried to work on one of my projects via RDP from a Windows XP machine (something I have done many, many times with the old machine) and the project crashes when run. I get the "no source availiable" tab and an AccessViolationException as soon as the splash screen has loaded. Going back to local operation, the project runs fine.
I've Googled this one to death and I can't find anything that relates to this problem at all. Any sugggestions would be gratefully received.
Thanks.
I do have multiple monitors but have never had a problem before with RDP. Anyways, I found other problems when opening other, older, projects in VS2010 so I uninstalled and reverted to VS2008. All OK now. Thanks for your help.
I was having an issue running Visual Studio 2010 via RDP where the IDE contents except the Solution Explorer wouldn't render. I went to Options->Environment->General->Visual experience and turned off the the "rich client visual experience" options. I suspect turning off "Use hardware graphics acceleration if available" did the trick.
I had also problem with RDP working in "windows 10"
My connection other computers always run successful, but closing after 5-15 second. I very long try fix this error. And I open this exception in VS2015 and read full excaption:
Unhandled exception at 0x00007FFBE35A8283 (ntdll.dll) in mstsc.exe: 0xC0000374: Куча была повреждена (parameters: 0x00007FFBE35FF6B0).
At first I thinked my PC have truble with RAM memory, but I decide change RDP settings and it began work without problem.
I changed the picture quality and uncheck using printer in other window.
My rdp workin very nice now.
I tried many fixes
From the microsoftware, with updates and system files, but nothing helped. I am writing now if someone with the same collision can solve temporarily the problem by lowering the quality of the picture. On a remote computer, it may be very important to simply connect, especially if it is a server.