Read JPEG File.vi creates temporary files?

[Premise03]

Forum,&nbsp;I am using LV 8.5 and I have discovered that the &quot;Read JPEG File.vi&quot; creates temporary files when reading a JPEG file.&nbsp; With a built EXE, the files are created in the root of the C: drive.&nbsp; While running the same code in the LabVIEW IDE the files are created on my H: drive which is for my personal network storage.&nbsp; The filename is formatted as &quot;tXXX.X&quot; where X is a random set of ASCII characters.&nbsp; For example, the file is currently named &quot;t53s.b&quot; and the next time I call &quot;Read JPEG File.vi&quot; it will be &quot;t53s.c&quot;.&nbsp;I discovered this fact using Process Monitor v 1.37 from <a href="http://www.sysinternals.com/" target="_blank">www.sysinternals.com</a>&nbsp; and filtering for the creation of these files. &nbsp;The problem is not the creation of the files, rather in the location they are created.&nbsp;&nbsp;A customer running our app&nbsp;does not allow files to be created off of the root of C: when the user is not an Admin.&nbsp; If I could find a way to tell &quot;Read JPEG File.vi&quot; to create these temporary files somewhere else, that would be sufficient to resolve the issue.&nbsp;Thanks,Chris Roth

[smercurio_fc]

Fascinating. I never noticed that before. On my system the files are created directly in C:\ while running from the development environment. Doesn't seem to follow any of the paths that can be set in the LabVIEW options. Wonder if the path is determined in the function or whether it uses some other (unknown) key in the LabVIEW.ini file.

[Brian_A]

Hi Chris,&nbsp;Certainly is an interesting one. &nbsp; I'll look into this and see what we can come up with.&nbsp; This same question has also come up in our email support, so we've definately got something we need to check out!&nbsp; I'll let you know what we find.&nbsp;Regards,&nbsp;