Microsoft Windows* 8.x

Oh, snap! Windows* 8.1 Release Preview, XAML Content, and Window Resize

Windows* 8 had a visual state known as the “snap view.”  This was a fixed window width that an app could reside in when snapped.  The window is fixed at 320 pixels so the user run two applications at the same time.  Windows 8.1 Release Preview changed the behavior of snap view.  When a window is snapped, the minimum width is 500 pixels.  The width can be modified in the project manifest file. Up to four apps can be snapped concurrently, enhancing the multitasking experience when compared to Windows 8.

CoArray I/O, Windows Instruction File, and Setting Max Images

How is I/O handeled with CoArrays on Windows. I know that WRITE(* goes to all images and READ(* is set to Image 1, but if I have an input file assigned to unit 17 and all the images open the file will there be read input errors? Say I have IUNIT=17 and I open the file with all the images OPEN(UNIT=IUNIT,FILE='INPUT.txt') would they be synconized on the read statements (READ(IUNIT,*) X,Y,Z)  or each over there only location within the file?

Inspector XE question about memory leak

I am new at using the Intel Inspector. It is telling me there is a memory leak at the following line

What would make it think there is a memory leak?
I am confident these variables have not already been allocated.

The derived data type is defined in a module file as follows:
! VAL = Complex Eigenvalue,
! VEC = Complex Eigenvector.

System.EntryPointNotFoundException: No se puede encontrar el punto de entrada denominado 'TSAT11' en el archivo DLL 'calc.dll'.

Hello. I'm working with SharpDevelop and I get is this error. I am calling a dll from Fortran.

System.EntryPointNotFoundException: Can not find entry point named 'TSAT11' in DLL 'calc.dll'.

Thanks for the help.


I am having problems with an error 157 (Access Violation), but can't seem to make any headway.

The biggest challenge facing me now is that the code does not always crash at the same point. The code is structured such that many iterative calls to the same routines are performed. Each time they are in theory using the same memory over and over again.

I have been studying Steve Lionel's article "Don't Touch Me There" and I believe I have ruled out the common sources:

Assine o Microsoft Windows* 8.x