Can anyone reproduce the following?
In MMA 8.04 in Windows Vista or Windows 7, right-clicking on
an animation while it is running crashes the entire Mathematica
session (kernel and front-end).
Related
I have following problem: Sometimes, when I debug a C++ project in VS 2013, my complete Windows freezes! This means:
GUI is updated (i.e. previous opened Task Manager is updating values)
Can not close VisualStudio
Can not close any program (i.e. firefox, the program which is been debugged, outlook, ...)
killing any process via Task Manager not working
Klicking Windows start button not working
Hitting Strg+Alt+Del not working
The only thing I can do is press and holding the I/O Hardware button at my Laptop
The system is a Windows 7 Enterprise x64 with SSD, 16GB RAM and i7 CPU. Symantec Endpoint Protection is installed from our IT. Some of my collegues have the same problem. We think, that this problem only occures if mixed-Debugging with Managed-Code, Unmanged-Code and COM in code is used.
Thanks for your Help!
My laptop computer is MacBook Pro 13" 2010-mid with nVIDIA 320M GPU. My OS is Windows 10 x64 ver 1607. The nVIDIA driver version is 341.98.
I meet a broken GUI rendering problem. See the screenshot of Visual Studio 2017 RC GUI:
You can see the Solution Explorer pane in the left shows a broken rendering.
Actually, there are not only Visual Studio GUI, but also many application GUIs have the same broken rendering problem, for example, JabRef, Atlassian SourceTree, ...
And, there are not only Windows 10 but also Windows 8 having the same problem. Does anyone have a solution or workaround?
I find workarounds for several my frequently-used apps. These workarounds show the problem comes from the GPU hardware acceleration. Disable the acceleration for working around the broken rendering problem.
For Java apps (e.g., JabRef), the workaround is to set environment variable J2D_D3D to false. See:
Swing rendering appears broken in JDK 1.8, correct in JDK 1.7
For Windows Presentation Foundation (WPF) apps (e.g., SourceTree and Visual Studio 2017 RC), the workaround is to disable WPF acceleration by adding a registry value:
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Avalon.Graphics\DisableHWAcceleration
with data "1." See:
How does one disable hardware acceleration in wpf?
i had many problems with windows 10 on MBP Pro mid2010, i resolved all my problems by installing the upgrade to Build 1909 by downloading the upgrade utility:
https://www.microsoft.com/en-us/software-download/windows10
after that i installed BootCamp4.0.4033 and by magic all works fine.
We are migrating our applications from windows xp to windows 7. One of the application is window and mouse hook. same code is working fine in windows xp but it is not working in windows 7 target machine(windows 7 installed with our own software platform).
One important thing is its working fine in my personal laptop which is having windows 7 os
i dont know what is happening...
please help me to resolve this...
There are increased security features in Windows 7, and that's probably what you're running into. Try running your app as administrator on your target machine (right click, run as admin).
I haven't tried such a hook in Win7 myself, but I saw this happen from XP to a Vista box.
I have found the answer. actually our application does hook every process we create. i have created 32bit dll. target machine is 64 bit so every process is 64bit right. so it tried to load my hook dll(32bit) into 64bit processes. we cannot load 32bit dll into 64bit exe...... :)
When i try to launch Windows Phone 7 Emulator directly it is toggling on/off 2-3 times (can see it for like 2-4 sec),
then stopping without giving any error message.
There is only
"Windows Phone Emulator is doing a complete OS Boot"
somewhere in the middle of appearance.
When i launch it from Expression Blend 4 it is also toggling on/off,
but less frequently and in the middle there is progress bar window stuck always at same place about connecting eventually giving this
error: http://img94.imageshack.us/img94/7025/errorqu.png
The issue is on:
Asus 1005PXD (2 weeks old) with Windows 7 SP1 64 bit
Installed my software in that order:
VS10 Ultimate
VS10 SP1
WP7 SDK
Expression 4 Ultimate (incl. Blend)
Found the issue, Intel GMA 3150 which i have in 1005PXD does not support XNA, after installing WP7.1 SDK it was showing proper information.
But still i don't know why i cannot run emulator at all, but it still should be possible to run non-XNA applications.
Has anyone got hardware breakpoints to work on 64bit XP and if so how?
We have an application that uses hardware breakpoints this has worked on 32 bit XP and 32 bit Vista operating systems for sometime now. However having ported our code to 64 bit we get a crash when the app is run on 64 bit XP but not when run on 64 bit Vista. The app is compiled and built on XP.
We have isolated this down to thread resumption after setting a breakpoint (DR7=1). The crash occurs if we raise a file dialog box and the GUI controls on forms are rather flaky. Strangely, if after setting the breakpoint and observe the flaky GUI, we then disable the breakpoint (DR7=0) the GUI starts behaving normally again and raising the file dialog does not cause a crash.
We have replaced our breakpoint setting code with other example breakpoint setting code and each example has the same problem.
Has anyone got hardware breakpoints to work on 64bit XP and if so how?
I guess that's a no then!
You can create a simple MFC application in Visual Studio and set a hardware breakpoint, e.g. a data breakpoint, in the debugger and the application will demonstrate the same behaviour as you're describing.
XP x64 does seem to be messed up sometimes when compared with the Vista/7 codebase. Therefore, it probably comes as no surprise that Microsoft aren't supporting XP x64 at all for some of its newer products, including Office 2010.
There is an interesting project on Codeproject : "Toggle hardware data/read/execute breakpoints programmatically"
Visual Studio has Data Breakpoints. You can set the debugger to stop on write to a specific memory address.
http://msdn.microsoft.com/en-us/library/350dyxd0.aspx