I was playing with the simulator that comes with VS 2012 and decided to crank up the resolution to see if my app would look well in high resolutions. Little did I realize how much that would demand from my machine. The simulator crashed and I haven't been able to use it since. I can start it outside of visual studio but as soon as I click anything it freezes and starts to lock up my machine. I'm running Windows 8 in a virtual machine so it's already a bit resource limited.
Is there a way (either through the registry or some other means) to reset the simulator settings? I need to turn the resolution back down so I can actually use it to test my apps.
This is definitely less than optimal, but I found a solution if you are desperate. I decided to repair VS 2012 to solve some other things and it seems to have reset the simulator settings.
This just further confirms that there has to be a simple way to do this because the installer probably just copied default registry settings in place with fresh copies of the files. Therefore I'm not going to accept this answer for at time so that others can see this and hopefully offer a better answer.
Related
I'm on a VB.Net Winform project and I have encountered a strange problem with my IDE Visual Studio 2019.
When I double click in the solution explorer to open the form in visual editing mode, it shows up but with a wrong resolution, the form and everything in it becomes far bigger than it should be. But when I run the project in debug mode, the runtime resolution is normal.
I do have two monitors but I never had this issue before, it would be great if someone knows why and has a solution for it.
Problem was solved after a reboot. I think it was a pending windows update who caused this . Very often, a pending windows 10 update causes a problem, I've experienced the blue screen, wifi connection failure, and this time a resolution problem. Intentionally or not, it forces users to restart the computer to apply the update. Hope this can serve other people.
I have a radio button that is represented as a pbdatawindow, when I run setcelldata to pick an option it works fine on my laptop but fails on my colleagues laptop. If we try the run the command again on my colleagues laptop we get a fatal error from UFT.
The only difference between my UFT install and my colleagues is that my colleagues version is installed in French. Has anyone seen a similar issue?
PbWindow().PbDataWindow().SetCellData 1,1,""
Few things to try:
What version of uft are you using? - perhaps check for newer of see if there is a patch available?
Jump onto the microfocus knowledge base and see if there is anything around power builder.
You say the machines are the same but does that include every application too? In the past I've known that if you install applications after uft it can break its references. Try uninstalling and reinstalling uft. There is a repair option but uninstall/reinstall is normally more thorough.
Try and clear out all your temp and user settings.
In your user profile backup then remove all folders with mercury, hp, Hewlett-Packard and microfocus.
-The go to %temp% and clear evetything.
Try and pin down the problem - Has your colleague tried the English version or uft? - if that works, is it an option? (everyone use the same version)
If it doesn't work it suggests it's your colleague's machine as opposed to uft.
Is evetything such as the resolution and browser/application versions the same? Or simply try another French localised machine?
What's the fatal error? Does it provide any clues on why it failed?
Finally, You're paying a lot for commercial software. Don't suffer in silence :-)
Log a support call with microfocus. It's a bit long winded but Back in the day they used to be pretty good at helping. They'll ask you for logs and knowing how to get that is good to know.
There's more to try - let me know how you get on.
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.
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.