Network issue
-
I am not sure if this is the correct form, but as I think the problem is a result of something in .NET I am posting here. Running a program (written in C# and using .NET 2.0) on a local machine. Using that program to access a file on a network drive, working on the file (the file is a SEGY file, like a JPEG, and lines are overlaid on the file, information about the lines get saved while the SEGY file is unchanged), and saving the work as a text file. It appears, depending on the size of the file trying to be written, the program hangs. A file of 900K can be written successfully, but when the program hangs it stops with about 230K written (working on a local machine only the save which hangs on a network drive works fine). Adding a flush after each write 'appears' to solve the problem (appearing to solve the problem isn't good enough). The writes are in a for loop, running in debug and adding a break point inside the loop, the break point is not tripped. Has anyone had any experience with this or can they point me where I may be able to find an answer?
this thing looks like it was written by an epileptic ferret Dave Kreskowiak
-
I am not sure if this is the correct form, but as I think the problem is a result of something in .NET I am posting here. Running a program (written in C# and using .NET 2.0) on a local machine. Using that program to access a file on a network drive, working on the file (the file is a SEGY file, like a JPEG, and lines are overlaid on the file, information about the lines get saved while the SEGY file is unchanged), and saving the work as a text file. It appears, depending on the size of the file trying to be written, the program hangs. A file of 900K can be written successfully, but when the program hangs it stops with about 230K written (working on a local machine only the save which hangs on a network drive works fine). Adding a flush after each write 'appears' to solve the problem (appearing to solve the problem isn't good enough). The writes are in a for loop, running in debug and adding a break point inside the loop, the break point is not tripped. Has anyone had any experience with this or can they point me where I may be able to find an answer?
this thing looks like it was written by an epileptic ferret Dave Kreskowiak