It seems notepad.exe is doing the right thing - it tells you
that you do not have CRLFs at the end of your line. The
issue is with your code, and how "\n\n" is compiled
under SP3. I recommend you repost your item in a
newsgroup that focuses on the compiler you use.
"Nagesh" <(E-Mail Removed)> wrote in message
news:095601c36b03$63d7b220$(E-Mail Removed)...
> Hi,
>
> Thanks for your reply. I have used a binary lister and
> noticed that when I have the Win2000 SP2 in place I see a
> CR and LF (0D 0A) at the end of the line and when I have
> SP3, I see a 0A 0A. I see this difference for the same
> piece of code where I have used "\n\n".
>
> Nagesh.
> >-----Original Message-----
> >
> >"Nagesh" <(E-Mail Removed)> wrote in message
> >news:06f101c36ae4$7c6e7f90$(E-Mail Removed)...
> >> Hi All,
> >>
> >> From my C++ application I was generating a report and
> >> have "\n" for having new lines in to the report. When I
> >> make a txt file of this report, I used to get the new
> >> lines properly when I view the report in the notepad.
> >> After I have installed SP3 of Win2000, I start seeing a
> >> square in place of newline when I open the txt file in
> the
> >> notepad, but I don't see these squares when I open the
> >> file in Wordpad. Is there any thing done like this in
> the
> >> SP3 of Win2000?
> >>
> >> Please reply to this query
> >> Thanks
> >> Nagesh.
> >>
> >
> >Rather than using notepad or wordpad to investigate
> >this issue, you should use a binary lister. The good
> >old list.com is an example, or debug.exe if you do
> >not have anything else. Under Microsoft OSs, each
> >line in a text file is terminated by one CR plus one
> >LF (or $0d + $0a in hex). What do you see?
> >
> >
> >.
> >
|
Similar Threads
