My upgrade to Windows 10 went very well and only needing a few programs reinstalled. Java was one of those because Eclipse did not start anymore: eclipse 64 bit didn't run but 32 bit did and I am on a 64 bit machine where it used to work. This was easily fixed by uninstalling and reinstalling Java and the JDK. However, one issue still remains.
System.getProperty(" ... ") returns next wrong values:
"os.name" = "Windows 8.1" should say "Windows 10"
"os.version" = "6.3" is this wrong also?
Is this a problem with Java or is this because Windows 10 was done through a system-update and my system is technically still "Windows 8.1"?
It's a problem with current Java.
MS changed some API behavior in Windows 10 and Java doesn't recognise it correctly. See https://bugs.openjdk.java.net/browse/JDK-8059803 for details.
This will be fixed in upcoming jdk8u60. Latest dev version reports next on Windows 10:
os.name = Windows 10
os.version = 10.0
Related
UPDATE*
I made a excell addin (.xll file), with some math functions, compiled in c++, and it works normally in my computer. Well, when i try send to other person, isnt work. Excel's show a message like the file is corrupted, and when we try open it, open a sheet with some codes/words/symbols
I've tried to find a solution, but to no avail. But I found out what's the really problem.
After install Visual Studio (full version) in this machine wasn't working, the xll addin works!
So, I think I have a program, feature, component that I installed together with the visual studio (full version) that made the program run. I tried the SDK but was unsuccessful.
Could you help me please? I attached 3 images, one with the addin working and 2 with erros.
PS: i tried compiling version 32 bits and x64, for both excells, and happens in both excels (32 & 64 bits)
erro 1
erro 2
working
A colleague ask me to uptdate with the results of -dumpbin /dependents Addin.xll
Follow bellow:
File Type: DLL
Image has the following dependencies:
KERNEL32.dll
USER32.dll
MSVCP140D.dll
VCRUNTIME140_1D.dll
VCRUNTIME140D.dll
ucrtbased.dll
Summary
1000 .00cfg
3000 .data
4000 .idata
1000 .msvcjmc
A000 .pdata
29000 .rdata
2000 .reloc
1000 .rsrc
70000 .text
32000 .textbss
1000 .tls
1) Make sure what you send out to other persons are release builds, not debug ones.
2) Users who do not have the VC++ runtimes installed already will need to install the appropriate x86 (32-bit) or x64 (64-bit) redistributables from The latest supported Visual C++ downloads page (where the bitness depends on which x86 vs. x64 version of the XLL you send them, not on the bitness of their Windows installation).
MSVCP140D.dll
VCRUNTIME140_1D.dll
VCRUNTIME140D.dll
ucrtbased.dll
The 'D' suffix in those DLL names stands for "Debug". Those are the debug C/C++ runtime DLLs, which are used by the Configuration = Debug builds, and are installed as part of the Visual Studio setup. They are to be used during development, but not otherwise deployed, per Determining Which DLLs to Redistribute:
Debug versions of applications and the various Visual C++ debug DLLs are not redistributable.
90% of the apps are displaying correctly sharp and clear as it's supposed to be on my uhd laptop screen. My scaling is 150% (as default also) (because of uhd screen in 15.6" laptop, 100% is too inefficient for my eyes.)
But dev c++ and some old softwares are looking blurry.
blurry dev c++
there is a fix on windows 10 settings named "advanced scaling" that is already enabled. is there any way to fix blurry dev c++ or do you recommend better up to date ide for c++ with compiler?
advanced scaling settings windows 10
(eclipse-cpp with mingw is slow,
clion is super but uses visual c++ compiler (i dont know if is there any setting for compiler,
microsoft visual c++ is good but showing some errors for nothing, actually says "no errors" than doesnt compiles for some time)
Right click on the Dev c++
Select “Properties” from the popup menu.
Click on “Compatibility” tab.
making the settings to manually fix fuzzy text in windows 10
Select “Override high DPI scaling behavior.
Select “System (Advanced)” not "System" or "Application" from the options provided in “Scaling performed by” section.
Click on “Apply” button and then on “OK.”
Fixed screenshot
There is a new version of Dev C++ compiled with the latest version of Delphi which supports high-DPI, Unicode, and Windows 10.
https://github.com/Embarcadero/Dev-Cpp/releases
The Android Studio 3.4.1 has many sub-processes (around 100!) as seen by the following screen-cap:
Windows 10 Task Manager Screen Shot - more than 90 sub-processes under process Android Studio, and CPU usage keep 100% for more than 10 hours!
My only question is: how can I solve this CPU 100% problem?
But I would like to use the following questions/answers section to provide more information about the problem!
Qus 1: What am I doing inside Android Studio?
Ans 1: Absolutely nothing, the sub-processes are there even I closed all projects. (But with Android Studio opened)
Qus 2: What is my hardware/software configuration?
Ans 2: CPU: Intel Core i5-6200U 2.3GHz, Ram: 8GB DDR3, Harddisk: 250GB SSD + 1TB Harddisk, OS: Windows 10 Home, verion 1803, Android Studio Version: 3.4.1
Qus 3: How many sub-processes? What are their names?
Ans 3: There are around 45 'Window Command Processor' and another 45 'Console Window Host' sub-processes under the process 'Android Studio'.
Qus 4: What did I do in order to get rid of the cpu-usage problem?
Ans 4.1: Uninstall and Re-install Android Studio
Ans 4.2: Clicked 'Help' -> 'Edit Custom VM-options' and set the following
-Xms2g
-Xmx2g
then restart Android Studio
Ans 4.3: Wait for the sub-processes to complete, but it's been 10 hours.
Ans 4.4: Open a project and set the following in android/gradle.properties:
org.gradle.jvmargs=-Xmx1536M
Ans 4.5: Close all projects. (But with Android Studio opened)
Ans 4.6: Search all stackoverflow and google, for related problems, none of them has this 'Many sub-processes AND 100% cpu-usage' problem.
It's a known issue, maybe you have other problems, but Android Studio 3.2+ is using processor on 100%.
There is no fix for now.
You can do two things:
Remove Android Studio and all related files, then install a fresh version
Check for Windows updates
You can try next:
Close Android Studio
Delete Android Studio folder (in my case C:\Users\Andriy\.AndroidStudio4.0)
It worked for me by lowering the max heap size
Go to Settings->Appearance & Behavior->System Settings->Memory Settings
lower to min values (my PC has 16GB RAM)
I am using Visual Studio 2012 with the Intel Fortran Compiler XE 13.0 (from Parallel Studio 2013) to code in Fortran.
When debugging a project, the "Locals" and "Auto" windows don't show any variable. Similarly, when hovering over a variable name in the code, I don't get any datatip showing its value. Lastly, when trying to evaluate a variable or expression in the Watches I always get an "Unable to evaluate expression". So, as far as I understand, there's some problem involving debugger symbols or something like this.
Here's what I tried:
restarting VS and Windows
creating a new solution with default configuration
checking the Debugging options for any obvious setting which could case this
followed this answer, even if it looks like it's for a slightly different problem (VS recognizes a local variable, but saying it's out of scope)
repairing my Intel Parallel Studio XE 2013 installation
I never enabled optimization. Here's a screenshot so that you can clearly see what it's going on here.
P.S: as a last hint, I found a similar bug affecting VS2010, but 1) yeah, I've got VS2012 and I suppose it should have been fixed 2) it affects C++ (don't know if this matters though) 3) the patch is not directly available online.
I installed Pharo 3.0 on my ASUS Windows 7 laptop and settled in to run through the ProfStef tutorial. But I could not get past the first panel - I could not 'doit'.
I installed Pharo 2.0 on the laptop. Same story. I turned on the touchpad. Nope. I installed Pharo 2.0 and 3.0 on a Windows 7 desktop. No, the mouse right button is not recognized there.
I installed Pharo 2.0 on a Gateway Windows XP and the right-mouse button did not work there either.
Finally, knowing that Pharo is a fork of Squeak, I installed Squeak 4.3 on the original laptop. The right-click is recognized by that package.
Does right-click means something in Pharo other than what I am expecting?
This appears to be a known issue.
Reference here on the Pharo Open Issues area.
I didn't create a user to dig deeper at the link provided there, but you can check it out.
My guess is that, since it's pretty darn important, it will be resolved soon.
This is very likely a VM problem. The latest update on this issue is from February 14 2013, work still in progress.
Pharo and Squeak use different VMs, which explains the different behaviours you're seeing.
To evaluate an expression (i.e. "doit") you don't need the right click. You can simply use ctrl + d (or alt + d, I'm on Mac, so I don't know which one's the command button). So simply select the code you want to evaluate and "doit" and you're good.
If you want feedback, you can also "print it" (ctrl + p), "inspect it" (ctrl + i) or "explore it" (ctrl + shift + i).
I have raised the priority of that issue (case 7545 on FogBugz) so we have a look at it before releasing Pharo3
No, it is not. That's not related: it has something to do with the following of implementors when pressing over a class or a selector. And btw, that issue tracker is not active anymore (that issue is old, more than a year). We should close it, but we let it there for documentation issues. For now, we are using https://pharo.fogbugz.com.
Anyway... about your problem: I couldn't reproduce it. How are you installing your pharo distributions?
I tried two ways:
http://get.pharo.org
(it works in windows if you have a decent shell installed)
and the pharo launcher:
https://ci.inria.fr/pharo-contribution/job/PharoLauncher-Win-Package/lastSuccessfulBuild/artifact/pharo-ci/pharo_installer.exe
Both are "the recommended" ways of installing, even if they are not properly publicised in the pharo web site (something that we should change during the course of the day :) )