This is the same question as on turn off FTH but on Windows8 so maybe there's a different answer. I have tried ALL the suggestions there and it still won't go away. I'm trying to debug a 32 bit program on 64 bit Windows Pro 8. I've tried setting all the registry entries (and rebooting); these normally only exist in the 64 bit part but I added them to the 32 bit part as well. I've tried renaming the acxtrnal.dll file (both 32 & 64 bit versions). I've tried running the rundll32 suggestion given. None of these have stopped FTH running and destroying my program performance - an operation which took 5 seconds is now taking several minutes.
The only way I have found to get around it is to rename both the visual studio and my program executables - which I will have to do again when it next starts crashing (which it will - I'm doing development!!).
Any ideas?
To disable it for a single application
Go to the HKEY_LOCAL_MACHINE and HKEY_CURRENT_USER versions of
Software\Microsoft\Windows
NT\CurrentVersion\AppCompatFlags\Layers\your_application.exe and
delete the FaultTolerantHeap entry.
or visit this link
Here
Related
Im using widows 7 on my working PC and i know i should update (i have win10 on my common pc)
but i still need to finish some important art projects and updating my system now would cause me a lot of compatibility trouble with some wierd and old programs i use so im stuck with win7 until im done with theses projects.
However, last night i had an update (i thought there was no more updates wor win7 Oo')
and since then, my mouse software wont work anymore !
the software is called "Steelseries Engine"
i worked until late and the software was working, but today, it wont start.
i tried to restart, update, and reinstalling but the problem seems to come from some missing dll.
when i go into the install folder and launch it from there, it gives me the following error :
the program cant start because "api-ms-win-core-winrt-string-l1-1-0.dll" is missing.
Anyone could tell me how to repair that ? is it something related to visual c++ or something ?
I really need help, because i have to finish my project fast and witout my mouse setup/macros its going to take ages.
art
Thanks a lot.
I have got the same problem from yesterday, now.
Same message, same circonstances, "steel series" connected + windows 7, and i see no reason why it started. i reinstalled the steelseries engine exe i kept from my personal depository file, and it worked, then today i rebooted the PC and the dll message came back. Very strange. Stranger is that the steel series engine exe for the mouse and Co is not available for windows 7 anymore ont the steelseries website, it is written "For windows 8 and upper versions."
edit: i fixed the .ddl missing trouble, even though i don't know how it started. Thanks to CCLEANER, i found in the start list a long command line stating that the .dll will be deleted by a steel series operator. Delete this useless line (i don't know where it suddenly came from, may be a corrupted auto upgrade by SSeries) and reinstall steelseriesengine. I'm pretty sure this problem had nothing to do with W7. Enjoy.
Since upgrading from Domino 9 to 11 some LS-Agents crash the server on calls to C API functions.
We're running Domino 11.0.1 64 bit on AIX 7.2
First we thought about a change in handle sizes and switching from 32 bit to 64 bit fixed some calls. But other calls needed a switch from 32 bit to 16 bit to work. Strange! (In fact the declared size should make no difference, as long as its big enough for the actual value, because all arguments are passed as 64 bit on 64 bit machines - at least in this case)
I've tested the calls from Java using JNA - everything works as expected with 32 bit handles. So C API seems to be OK, but LS C callout seems broken.
Does anyone else notice this behaviour? Or is it just us?
Just in case anyone else runs into this issue:
SPR #ASHEBSVQ72 (not online visible by now)
It's a regression bug with C callouts from LS on AIX. Has been there since Domino 10. Strange thing nobody but us ran into this problem.
No easy workaround known. Wait for a fix or use JNA in Java for callouts.
I’m using VB 2019 with the latest updates on 64-bit Windows 10 with the same. In the past few days I’ve started having a 30-40 second delay when loading my code in debug mode. Up until a couple of days ago this only took about 5 seconds. Any ideas what might have happened and/or how I can reduce this delay starting up my code every time I make a change to it?
Windows updated a couple of items each of the last couple of nights, I wonder if any of these have triggered the new behavior.
The reason may be that many files are created during compilation, and the anti-virus tool provided by Microsoft will scan the created files, so the compilation speed is reduced.
You can set a folder whitelist in the Windows Security Center, which is Windows Defender. Files in this folder will not be scanned. Putting my own code warehouse, I will put all my code in a folder, add this folder to the whitelist, it will not be scanned during compilation, which can speed up the compilation speed.
This problem is pretty self explanatory. Here are the details: I'm trying to include freeglut and glew in Visual Studio 2012 on Windows 8. I'm on a 64 bit system, so I thought I needed to put glew32.dll in my 64 bit system folder. I tried that and receive the following error:
"The application was unable to start correctly (0xc000007b). Click OK to close the application."
Which I've interpreted as I'm trying to put a 32 bit dll in the 64 bit folder or vice-versa.
Just for laughs, I tried putting the file in System32, but of course, it just told me the file wasn't on my computer. Any suggestions?
EDIT* May I also add that some of the set up for this was NOT the same as it would have been on Windows 7 or Visual Studio 2010 or earlier. I may have missed something because I kind of winged it using the search function combined with some documentation I found on various websites. (i.e the lib and include folders are no longer in the same place)
EDIT2* I'm sure this can probably be derived, but I want to add it anyway for clarity: If I removed the dependency for glew32.lib and comment out any code using glew.h, the window forms as it should. I don't think my source code is needed seeing as I'm 99% sure this is not a code issue, but if anyone wants to see it, let me know and I'll attach it.
I'm shocked that this hasn't been asked yet - but I can't install VS 2008 sp1 because my c: (%SYSTEMDRIVE%) has around 1.6 G free...
How in the world can I get sp1 to install?
Thanks
UPDATE:
I had the C++ bits installed - and I wasn't using them... Once I removed the C++ bits the installer stopped complaining.
ALSO - FYI - my %tmp% and %temp% already pointed to a different disk - but the installer isn't smart enough to figure that out i guess...
I've had similar problems with other installations. Re-setting TMP and/or TEMP to a partition with more space seems to have worked.
Per the system requirements from the release notes from Visual Studio 2008 SP1:
"3.8 GB available on the system drive, plus 600 MB on the drive on which Visual Studio is installed. Note: You can use the Disk Cleanup utility to remove temporary files." One option that could help you is to turn off system restore, restart, install, then turn system restore back on. Risky, but it may allow the install if you are absolutely desperate.
You're going to need more hard drive space. The VS installer will be doing a lot of downloading, uncompressing, and copying. So most of the 4gb is used for swap space, not necessarily for final installation.
It's also possible to turn of the swap space of Windows. Only do that when you've got plenty of RAM. Swap space can be found in My Computer/properties/Advanced/Performance/Advanced/Virtual Memory.
If you also wish to defrag at some point, do it when the disk is as empty as possible otherwise defrag (which can improve performance) will not work all that well, if at all.
Don't forget to activate swap space again afterwards.
sadly i had to remove c++ ( see my update in the question ) and that 'fixed' it...