IMHO, the problem is neither related to the CB nor MinGW, because it points out directly to the Windows System files that some of the functions( LdrLoadAlternateResourceModuleEx ) residing in the ntdll.dll was causing the problem. >BTW: CodeBlocks currently ships with TDM GCC 4.7.1 so you must have a pretty old version of CodeBlocks anyway.)No, I made sure that I downloaded the latest version of the MinGW and pointed out exactly to that directory where latest files of Mingw reside, but that didn't help, too. It is not working at all, double clicking, trying to execute it during program run or debug, Dr MinGW never pops up, I have the Win7, probably its been targeted for to the different OS. > b) It is working, but it does not provide more information than > a) You still have not managed to get Dr Mingw to work, or Thank you all for your suggestions and sorry for the tardy response, Unfortunately, I know nothing about Fortran (or Code Blocks). I'm using the Code Blocks which intrisically comes with MinGW > It seems that there is completely malfunctioning with dynamically However, is it that:Ī) You still have not managed to get Dr Mingw to work, orī) It is working, but it does not provide more information than mingw/dllcrt1.c: No such file or directory. > In ntdll!LdrLoadAlternateResourceModuleEx () (C:\Windows\system32\ntdll.dll) > rogram received signal SIGSEGV, Segmentation fault. > complaining for the no such file or directory, is it normal ? > Although I'm still puzzled with why the compiler or linker says and Can that be a reason for that discrepancy? I'm using the Code Blocks which intrisically comes with MinGW 3.4.1. mingw/dllcrt1.c:145 Debugger finished with status 0Īnother thing that I'm experiencing and observed so far is even if I have the very simple dynamic array the the watches that I set at debugging time doesn't shows the correct result.It seems that there is completely malfunctioning with dynamically assigned arrays with MingW Fortran compiler. In ntdll!LdrLoadAlternateResourceModuleEx () (C:\Windows\system32\ntdll.dll)ġ45. > I did not have to do this on Windows XP, which I was using theĪlthough I'm still puzzled with why the compiler or linker says and complaining for the no such file or directory, is it normal ?rogram received signal SIGSEGV, Segmentation fault. > Change Action Center Settings -> Scroll to "Related Settings" > Control Panel -> (Search for Action Center) -> Action Center -> > Windows Problem Reporing in Action Center. Disable this " security certificate" check in remote login (best solution)Ģ.> You are right. This must be a PC to PC handshake that we never see.ġ. Sadly CORD (my preferred client) is still NOT working, but now we know WHY! Win 10 looks for this " security certificate " and if it doesnt find it Win10 will REFUSE the connection. I said Yes, and boom! remote desktop ed in perfectly! and as soon as i tried to remote into my Win10 box, a message come up about generating a security certificate for this user. So following the advice above i downloaded MICROSOFTS's remote desktop. I can remote desktop in from a PC but not from CORD on my Mac.
Well as said above, that was short lived with the next update CORD stopped working again.
and after some update CORD finaly started working. So i HAVE been using CORD to log into my PCs from OSX.
I have been fighting this since first installing windows 10 on one of my test systems.i FINALY have the solution. If your server administrator does not know how or, worse still, won't do this for you, then you have far deeper problems that go well beyond OS X in particular and IT as a whole in general. On further prompts make sure you select 'Always Trust'.
cer file and when prompted install it as a system keychain.
They should know how to do this? Once exported save it to a memory stick, insert it into your mac, double click on the. He/she has to export this using the built-in tools. You begin to solve the problem by asking your server administrator for the server's root certificate. By default a mac will not have server-client trust certificates installed simply because the exchange won't happen transparently between an MS based server and non MS-OS such as OS X. I doubt you'd be aware of any of this as generally server administrators won't necessarily discuss them. However your problem may be with your understanding of the secure remote connections requirements between your server and remote connections.
Questions about RDC for Mac should be put on the relevant Microsoft forum rather than here. I doubt this a 'problem' with the mac as such nor does it have anything to do with Remote Desktop for Mac which is an entirely different product and for which this forum is for.