Application running from VC++ 6 crashes with "kernelbase.dll module not found" - visual-c++

This happens only in a specific machine.
So it must be VS 6 installation in the machine or the machine itself.
If I run the application in VC++6, I will get a crash with "kernelbase.dll module not found " after a certain operation.
But when executed in standalone, it is running fine.
Has anybody experience this symptom? Do I have to reinstall VC++6 again?

I fixed this problem by reorganizing system path. By some of unnecessary directories from the system path, I could resolve this problem. Hope this will help others with a similar problem.

Related

Imagemagick IIS install issue VBScript error "800a01ad"

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.

node.exe does not return output in case a package is given at the parameters

We are using node to build the LESS files in our .NET application.
To do so, we have prepared some stuff to support that easier for all the developers. In the end we have a node version in the source control.
Everything works fine for everyone except one developer that has joined our team in the last days.
Whenever he tries to run the stuff, the CSS files are just empty.
To find the reason we have tried to skip all the stuff around and call node with the less package directly from console. This is working as expected on my PC but there is no output at the affected developers PC.
Also when we are using a path to not existing package there is no output.
On my PC there is an error logged into the console, the affected developer does not get any output.
The only parameters that seems to work are "-h" and "-v"...
As we could not find any usefull hints in the internet, maybe anyone having an idea what can be reason?
Windows-configurations, ....
Finaly we could solve the problem:
Don't ask why but uninstalling Visual Studio 2019, installing VS 2017 and installing 2019 again solved the issue somehow... everthing works as expected.
Reinstalling VS 2019 alone did not solve the problem before.
Maybe a hint in case someone else comes to this question with the same issue:
The reason for going to VS 2017 where different issues with ReSharper as well. Mainly performance issues of VS when ReSharper was active, but some functional issues too. This issues where gone as well after that.
It seems there was something broken with the VS2019 installation that was not repaired by uninstalling and reinstalling VS2019 but by VS2017...

Too many open files error in Visual Studio Node.js under parallels after upgrade to MacOS Catalina 10.15.7

I just upgraded my Mac to 10.15.7 today. I run Parallels Desktop on the Mac so I can run my Node.js Visual Studio projects. Upon doing this upgrade I can no longer get my project to run. Unfortunately I made a few changes to the code before trying to run but I do not think that is the source of the issue or the log files would be telling me something else. When I run I get hundred/thousands of lines with the "too many open files" error. Below is a sample of one of those lines:
SourceMaps: could not preload for generated script: c:\Users\chris\github\CollegeTennisRanks\CollegeTennisRanks\obj\Release\Package\PackageTmp\node_modules\core-js\library\fn\string\bold.js. Error: Error: EMFILE: too many open files, open 'c:\Users\chris\github\CollegeTennisRanks\CollegeTennisRanks\obj\Release\Package\PackageTmp\node_modules\core-js\library\fn\string\bold.js'
I tried a suggestion I found online to change the settings by going to e terminal window and running the following command:
sudo launchctl limit maxfiles 65536 200000
but that did not change anything, still the same errors when i run the project. The odd thin is that I actually have two projects in the solution and the 2nd one actually runs, but it is a much smaller project and only a console app that dows not start up a web server, etc.
I am assuming that the upgrade to 10.15.7 had something to do with this but no cluee where to go now. Any help would be greatly appreciated.
Well I'll be darned... it was a code change. I copied the project over to a PC and ran and got the same result. Went through last changes one by one undoing them and found that one of my controllers had an issue that for some reason prevented it from running. How to determine that from the log is another question but at least that answers that. Evidently all the "too many open files" messages in debug log are not an issue, which also seems odd.

nodejs bluescreen on install

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.

MARS MIPS Simulator freezes when trying to open a file on Linux

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.

Resources