I cant seem to open any OpenGL software - gpu

I recently reinstalled windows in my computer and cant seem to run any open source software that requires use of my GPU (Nvidia 1060) this includes Paraview/MeshLab/CloudCompare. According to windows everything seems to be okay as it regards to the drivers.Anyone has any idea on what the problems might be ?
Thank you in advance

Related

Issue Installing Elastix 4.0 via Bootable USB - CentOS7 Error

Goal
I was attempting to install Elastix 4.0 on a home PC via a Bootable USB, but never had any luck getting it to install past the CentOS7 part (it kept giving me a "Warning: /dev/root does not exist" error).
What I've Tried
My main PC is Windows 10 Pro, so after downloading the latest Elastix 4.0 .iso from "http://www.elastix.com/en/downloads/" (Elastix-4.0.74-Stable-x86_64-bin-10Feb2016.iso) I used UNetbootin to create my Bootable USB for Elastix 4.0. I put the now Bootable USB into the PC I want to put Elastix 4.0 on and started it up.
It gave me the "Install Elastix 4" menu, so I hit enter and waited. Then the install proceeded to do its checks for CentOS7, but ended up getting stuck and gave me an error message "dracut-initqueue[580]: Warning: Could not boot." and "Warning: /dev/root does not exist".
This is where I am stuck and cannot proceed.
EDIT #1: I signed up for the Elastix forms, and someone else also had this issue. They said they downloaded the .iso and used Rufus to make a Bootable USB, and then booted the installation using the Troubleshooting -> Install CentOS 7 using Basic Graphics ... but according to them, that apparently corrupted something else and then they opted to just use a DVD.
EDIT #2: I tested this, and making a Bootable DVD of the .iso does work great for local machines. Installing it via a VM also seems to work without hassle. As a personal goal, I would like to get this working via a Bootable USB.
Research
I did some research but a lot of the solutions I've noticed are using the dd command in Linux to make a Bootable USB for just CentOS7 because it is (was?) known that UNetbootin did not properly make a Bootable USB for CentOS7, and I can't seem to find anything that would assist in making the Elastix 4.0 .iso work properly via a Bootable USB. I did try other tools such as Rufus 2.7, Win32 Disk Imager, ISO2USB, and dd for Windows, though most rendered my USB not bootable at all (Rufus worked OK, but still got stuck at the CentOS7 part). Also, installing via a CD/DVD is not ideal, as I have no CD/DVD drive (and I want to see if I can get this working via a Bootable USB drive).
There seem to be a few guides out there for trying to create a Bootable USB for Elastix 2.x, but nothing for Elastix 4.0. Reviewing those, it looks like the guides reference some files that do not exist in the new .iso (ex: ks_default.cfg). Still, my issue pertains mainly to the CentOS7 error I'm getting so I don't think this is related.
Any assistance with this is appreciated, and if you require more information from my end just let me know. I'm willing to try / re-try anything.
Thank you in advance.
http://henrysittechblog.blogspot.ru/2014/01/install-elastix-from-usb-step-by-step.html
Look for this line, but it may change:
append initrd=initrd.img inst.stage2=hd:LABEL=CentOS\x207\x20x86_64 inst.ks=cdrom:/dev/cdrom:/ks/anaconda-ks.cfg quiet
Change it to:
append initrd=initrd.img inst.stage2=hd:LABEL=CentOS\x207\x20x86_64 inst.ks=sdb1:/dev/sdb1:/ks/anaconda-ks.cfg quiet
Hi there i solve this problem 80%.
i did some manual change at line:
inst.ks=cdrom:/dev/cdrom:/ks/anaconda-ks.cfg quiet
Mine:
inst.ks=scsi:/dev/sdb1:/ks/anaconda-ks.cfg quiet
hd is not recogniced by Centos7.
made my usb bootable with rufus 2.9
then open isolinux.cfg with notepad++
just change the line
inst.ks=hd:sdb1:/ks/anaconda-ks.cfg quiet
where sdb1 used to say cdrom

CoreAVC 3.0.1 can't register on Win8.1 64bit

I installed CoreAVC 3.0.1 on my Windows 8.1 64bit, and want to use its decoder in MPC-HC. 32bit versions of CoreAVC and MPC-HC on Win8.1 64bit worked well. But when it turns to 64bit, MPC-HC can't find CoreAVC, and re-register CoreAVCDecoder64.ax fails with "A dynamic link library (DLL) initialization routine failed" error. I have already re-installed CoreAVC for many times. Can somebody help me with this? Thanks!
Since nobody ever seems to have answered this...CoreAVC is simply not supported under Windows 8/8.1/10. It has not been updated in quite some time and appears as though it will not be in the near future. Best bet is to try the CCCP for MPC-HC.
If you want to run HD video with CoreAVC, you'd better just go back to Windows 7.

Jetbrains IDE(s) failures

First my specs are an Intel i7 toshiba laptop with 8gigs of RAM running windows 8.1 with all the latest updates. When I first launch any of Jetbrains IDEs after install, it would ask me for my workspace location and then it would proceed to do nothing after than, but it stays in memory and slows down my entire system for about a minute, after that, the computer stops being slow and returns to normal but the program still does nothing (no GUI) but still remains in memory, what is going on??? Thanks in advance.
It's hard giving a definite answer to your question. But it sounds to me like you have a problem with your Java. Make sure you have it installed and at the latest version.
Also, try looking for matching bugs in the JetBrains bug tracker.
Replacing the jre folder within the IDE folder (pycharm,intelliJ,etc.) with one from an updated JDK install not JRE install.
ex:
JDK/jre7 copy over Jetbrains/IDE/jre
fixes the issue

Powerbuilder 10 Windows 8 compatibility

Does anyone know if Powerbuilder 10 is compatible with Windows 8 (Both the IDE and the runtime module)?
It seems like 11.5 is officially supported, but I couldn't find any info on PB 10's compatibility on Windows 8.
If it isn't, any tips on the migration process from 10->Further version? (Anything particular we have to watch out for?)
You should have no problem with running PB10 applications on Windows 8, appart perhaps not being not fully compliant with Win8 standards (concerning the placement of application data files, access rights on files, and so on mostly related to UAC file virtualization).
Neither you should have big problems with running the IDE, but maybe some minor issues (I think about an issue on the retrieval argument editor on PB11.5 that could also address PB10).
This is one of those things where you just have to try it yourself. The number of PowerBuilder developers with Windows 8 is likely very small.
I am supposed to be getting a Surface Pro 2 when they come out Oct 22nd which will run Windows 8.1. Hopefully there won't be any issues.
I am not sure about PB10 but I have used PB 10.5 in Win8 with no problem.
We have serious issues with running a PB10 application on Windows 8 computers.
Application runs fine until user enters text in datawindow fields, the application "stopped working". The problem is that it happens randomly, 10 fields can be entered without a problem but at the next field the "stopped working" pops up en the application is closed the next time it might happen after entering 2 fields.
The same application runs already for years on many computers unders XP, Vista, Windows 7 without any issue.
Until now we still have no clou what is causing it. Also we have no idea where to start searching.
The application is developed andf deployed under XP.
Next week we are going to setup a development environment under Windows, hopefully this will give us some more light on the issue.
Two things you need to realize:
PB10 was built (and support development stopped) before before Win8 was conceived, so obviously Sybase couldn't do anything in PB to help with Win8 compatibility. You're relying on MS's ability to maintain a backward compatible environment. IME, they do a pretty good job (better than my experience upgrading in the Unix world, but I'd imagine YMMV), but it's never perfect.
PowerBuilder is powerful enough to allow you to build an application that will break under any operating system. PB10 may have been supported on XP, but I guarantee you that I could have written something that violated an XP rule, or corrupted memory, or whatever, and would have been broken under XP. (I've seen memory corruptions that didn't manifest themselves until after an OS upgrade or some other change; so "broken" may not even manifest symptoms yet.) Is that Sybase's fault? I don't think so. They're the rope manufacturer; if you hang yourself....
Bottom line is what's already been said: no matter what the manufacturer or anyone else says, the only answer worth anything is the results of your own testing. My "Hello World" app may run in Win8 just fine, but your app that taps into the TCP/IP stack, leverage protected mode calls, sending printing language codes directly to the point-of-sale bar code printer, etc....
Good luck,
Terry.

Does mono on Linux require X?

With C#, you can create console apps. Well, do they run in Mono without X?
I know, this might be a dumb "Dude, just try it"-question, but the point is that I can't. I don't have any Linux installation right now, I'm going to use Mono to make a Raspberry Pi I'll order of use. Since the Pi's not here yet, I can't really try by myself.
Yes, you can definitely run console apps on Mono on the Raspberry Pi. That's what I use mine for, mostly :)
As an aside, I'd suggest installing the Arch distribution; at least when I installed mine, it had the most stable build of Mono under that environment. See my Google+ post for a few more details and some other handy tips from folks.