Subj : Bug related to Bullseye bulletin board?
To   : Karloch
From : Digital Man
Date : Tue Nov 04 2008 03:07 pm

  Re: Bug related to Bullseye bulletin board?
  By: Karloch to Digital Man on Tue Nov 04 2008 12:12 am

 >   Re: Bug related to Bullseye bulletin board?
 >   By: Digital Man to Karloch on Sun Nov 02 2008 21:48:16
 >
 >  > Hm... What's the length of the file (in bytes)? I didn't receive the
 >  > e-mail.
 >
 > I tried to email the file to you, but your mail server keeps rejecting my
 > messaage (I was using your address at www.synchro.net).
 >
 > Anyway, I solved the mistery. It turned out to not be a bug, I'll
 > explain...
 >
 >  > 4 bytes per character? No, it's ASCII - one byte per character, so after
 >  > reading 3<CR><LF>, the file position should be 3. Unless you converted
 >  > it to UTF-32?
 >
 > You're absolutely right: it's 1 byte/char. I was afraid my text editor
 > switched the format from ANSI to UTF-8, but that was not the case. The
 > <CR><LF> you put turned on my alarms.
 >
 > Last summer I migrated my BBS from Synchronet/Linux to Synchronet/Win32.
 > The process was smooth, but some things remain in Unix format. The
 > bullseye.cfg was ANSI Unix, using just <LF> as endline char, not the
 > <CR><LF> from DOS. This was the thing confusing the program. As soon as I
 > converted the file to DOS format the bulletin started working again.

Ah, that makes sense. It was probably reading the entire file in that first
file.readln() call then.

 > A question about Unix->Win32 migration, is it necessary to switch the path
 > backslash from "/" to "\" in every path specified at the SCFG utility? What
 > about configuration files?

No, forward slash works fine on Win32.

                                       digital man (xbox-live: digitlman)

Snapple "Real Fact" #14:
Camel's milk does not curdle.
Norco, CA WX: 63.6øF, 65% humidity, 0 mph ENE wind, 0.00 inches rain/24hrs

.