Ayer me encontré con esto:
Windows loads your program into RAM lazily, on-demand. When it loses the connection to the network drive, and your application tries to load a page that wasn't already in RAM, Windows has no choice but to throw an exception. Note that Windows also discards pages that haven't been touched recently if you're above your minimum working set size.
To force an image launched from across the network to be loaded into RAM before being executed, pass the /SWAPRUN:NET option to the linker
Lo activé en el vs2008, recompilé y ya he puesto la nueva versión. Espero que ya no haya tortazos similares.
No hay comentarios:
Publicar un comentario