I was about to install node.js on a brand new Windows 7 64bit system. But during the installation I get a bluescreen. It happens while "copying new files". I tried node.js 8.9.4 and 9.5.0, both in 64 bit. Any idea what's wrong?
edit: I now enabled virtual memory and the message has changed. Now I get
The driver is attempting to access memory beyond the end of the allocation.
And here the current screenshot of the dump:
Honestly, these problems seem absolutely weird... I have never before had such issues with the installation of nodejs. And I'm doing it on a new machine which is up-to-date.
I've figured out what the issue was. It had to do with Comodo Programs Manager. After having deinstalled the program, everything worked fine again. But on my old machine I used to run Comodo Programs Manager as well. So it remains strange why it now caused such issues.
Related
I have Imagemagick running on a remote server and have had it running on a local server successfully for many years, but recently I have had need to reinstall on a new machine and can't for the life of me figure out what i'm doing wrong, It's probably really simple and I'm hoping someone can point me in the right direction.
Scenario
WIN 10 running iis as localhost
Successfully installed Imagemagick 32 and 64 bit so they run on the local machine, however when try to access the localhost web page requiring Imagemagic I'm receiving the following message
Microsoft VBScript runtime error '800a01ad'
ActiveX component can't create object: 'ImageMagickObject.MagickImage.1'
my app pool is current set to allow 32bt application and as far as I am aware all permissions are correct, although I do believe this may be the issue somewhere.
Can anyone help to shed some light on this issue.
Thanks :-)
Resolved.. It turns out the latest version of Imagemagick 7.1.x does not ship with ImagemagickObject.dll, fortunately, I had a saved download .exe for an earlier version 7.0.8 which still had the .dll, once install I could copy imageMagickObject.dll to the system32 folder, after that everything worked as expected. Not sure what would replace this in my code if I have to ever user a newer version, if someone knows please add to the post.
I was trying to install SDK and Emulator without the Andriod studio on Ubuntu 20.04.
But got stuck at this error.
E0520 11:06:29.866803544 5261 socket_utils_common_posix.cc:201] check for SO_REUSEPORT: {"created":"#1589952989.866791260","description":"SO_REUSEPORT unavailable on compiling system","file":"/mnt/tmpfs/src/android/emu-master-dev/external/grpc/src/core/lib/iomgr/socket_utils_common_posix.cc","file_line":169}
checkValid: hw configs not eq
I got the solution from this article:
So in order to fix this, I just disabled the Camera by switching the option from Emulated to None and that was all.
Don't ask why this works, but it seemed to solve it for me.
Install Android SDK Platform tools. if already exist uninstall and install Android SDK Platform tool in ubuntu 20.04
Seems a GPU issue, try :
sudo ubuntu-drivers autoinstall
Or (or both) change graphic emulated performance to software if your emulated device allow it.
Had same issue with linux mint android studio ..
Hope it will help.
Though not directly affected by the error you described, when stuck at this point (namely, when supposed to be connecting back to the ADB server, but can't), this can be a result of a corrupted quick-boot snapshot.
What worked for me is to hard-delete the existing quick-boot snapshot, and have the emulator regenerate it on the next run.
To delete the snapshots:
rm -fr ~/.android/avd/<AVD name>/snapshots/default_boot
To regenerate the next snapshot, rerun the emulator as you normally would, then kill it after if full loads. But first, make sure that it is configured for saving a quick-boot snapshot on exit:
Edit quickbootChoice.ini, for example:
vi ~/.android/avd/<AVD name>/quickbootChoice.ini
The only line there should be:
saveOnExit = true
If you wish to see whether any of this is likely to help you before making any changes, run the emulator with the -no-snapshot argument applied, beforehand. For example:
$ANDROID_SDK_ROOT/emulator/emulator -no-snapshot #Pixel_API_29 &
(Or find a way to do this through Android Studio)
A note regarding other answers here that advised configuring the camera differently (which seems unrelated): It is very likely that changing the camera setting, for the Emulator, is considered a configuration change - which ends up in forcing a cold-boot (i.e. skipping usage of the quick-boot snapshot), which can explain why it works (but with no voodoo involved).
I am trying to install Oracle 12c client on my development box running Windows 10 and it doesn't even start.
I downloaded the files from Oracle download web site, ran setup.exe and it flashes briefly and nothing happens. I made sure latest JRE and JDK are installed.
I have spent most of the day googling but most deal with errors that occur during installation whereas I can't even start the installation! No errors, no messages. Checked GAC on off chance DLLs might be there but they are not.
I have used the same set of files on other machines and servers (Windows 2008r2 and 2012r2) without any issues but can seem to be able to troubleshoot this one. Any ideas to put me on the right path is appreciated.
After spending a couple of days trying to figure out the issue, uninstalling/reinstalling JRE and JDK and all that, the issue turned out to be the hard drive size. Apparently max dive size where you install the client is 2TB and mine was 3TB. I had to shrink the drive and it worked after that. Hopefully it saves someone some pain.
A couple of links for more info.
Installing on large disk
Oracle Universal Installer
I am running MARS 4.5 on Linux Mint with OpenJDK 8 and the program starts up fine and I can create a file. However, if I try to save or open another file, the program freezes and I have to kill the process.
The strange thing is that it worked one time, but after restarting the program, it was back to freezing whenever trying to access the filesystem.
I apologize if this is the wrong place for this kind of question, but I'm not sure where else to post it. If this is the wrong place, let me know and I will remove the question. Thanks for any help.
Switching to the official jdk from Oracle seems to have fixed the problem. I followed these instructions to uninstall OpenJDK and install the official one.
I've just downloaded Eclipse on elementary OS and attempted to launch it. After doing so, I saw the loading screen for a few seconds before it disappeared and left me with the desktop. Since then, my computer (an old Dell with 4GB of RAM and an Intel Core Duo) has been very unresponsive and the disk activity indicator is almost constantly lit up. I've been looking at the desktop for around 30 minutes now! How can I solve this problem and launch Eclipse?
EDIT: Running eclipse -clean from the command line produces the following error: The org.eclipse.m2e.logback.configuration bundle was activated before the state location was initialized. Will retry after the state location is initialized.
First, you might review your installation steps. If nothing is obviously wrong, check the following:
check for any error logs
check that you're using the proper Java version
make sure that there's enough memory allocated for Eclipse (see the eclipse.ini file)
as a last resort, try reinstalling it
See also the following guide for installing on Elementary OS: how to install
If that's not working submit more details of your specific problems.
NOTE: You may have to find the right Java and install it "by hand" rather than relying upon the distribution's package manager. You can "point" Eclipse at the right Java by editing the .ini file.
Some related links are as follows:
a similar symptom related to multiple screens and/or corrupt workspace
General trouble-shooting related to your issue and symptoms