comp.lang.idl-pvwave archive: archive » File pointer problem on PC-IDL

Home » Public Forums » archive » File pointer problem on PC-IDL

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: File pointer problem on PC-IDL [message #14723 is a reply to message #14602]

Thu, 18 March 1999 00:00

landsman
Messages: 93
Registered: August 1991

Member

In article <7cpol7$k4h$1@nnrp1.dejanews.com>, Peter Mason <menakkis@my-dejanews.com> writes...
> landsman@stars.gsfc.nasa.gov (Wayne Landsman) wrote:
> <...>
>> Basically, then internal file position is getting screwed up. I open a
>> binary file, readu 2880 bytes, and find myself located 4095 bytes into the
>> file.
> <...>
>
> Wayne, don't ask me why, but ask your remote user to include the switch
> /NOAUTOMODE in the OPEN call.
>
Peter, thanks for the info. The IDL documentation certainly gives the
impression that the Windows-only /NOAUTOMODE and /BINARY keywords to OPEN
have an effect only when *writing* to a file. I guess my example shows
that one has to be aware of flipping between "text" mode and "binary"
mode, even when reading a existing file opened with OPENR.

--Wayne Landsman landsman@mpb.gsfc.nasa.gov

Report message to a moderator

[Message index]

		File pointer problem on PC-IDL By: landsman on Thu, 11 March 1999 00:00
		Re: File pointer problem on PC-IDL By: menakkis on Thu, 18 March 1999 00:00
		Re: File pointer problem on PC-IDL By: Craig Markwardt on Thu, 18 March 1999 00:00
		Re: File pointer problem on PC-IDL By: landsman on Thu, 18 March 1999 00:00
		Re: File Pointer By: Paul Van Delst[1] on Mon, 06 December 2004 14:50
		Re: File Pointer By: David Fanning on Mon, 06 December 2004 13:28

Previous Topic:	test for ENVI running in IDL code
Next Topic:	9 dimensions arrays

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Sun Oct 12 14:23:26 PDT 2025

Total time taken to generate the page: 0.88183 seconds