Message Area
Casually read the BBS message area using an easy to use interface. Messages are categorized exactly like they are on the BBS. You may post new messages or reply to existing messages!

You are not logged in. Login here for full access privileges.

Previous Message | Next Message | Back to NOSTALGIA  <--  <--- Return to Home Page
   Networked Database  NOSTALGIA   [734 / 900] RSS
 From   To   Subject   Date/Time 
Message   mark lewis    JOE MACKEY   Detours   June 28, 2019
 6:00 PM *  

 On 2019 Jun 28 06:37:12, you wrote to NANCY BACKUS:

 JM>   The interstate between here and Charleston (the capitol and about 50
 JM> miles away) seems to be accident alley.  There seems to be at least one on
 JM> a daily basis.  And even for something minor like a fender bender the
whole
 JM> section is shut down for miles with t

the above paragraph was just cut off right there...

 JM>   I used the booking.com app on the phone sometimes (when I could get a
 JM> free wifi signal) for upcoming big towns and check room rates, location,
 JM> etc. I found I could book a room in less than 30 minutes before a planned
 JM> check in. Smaller places I just took th

this one was cut off right there... this seems to be a common occurance with
your posts... i've not said anything until now... i have my suspicions as to
where the problem is but i won't voice them here right now... i don't know what
 to suggest other than writing more and thusly shorter paragraphs... i can't
tell if it is a line/paragraph length problem on the BBS you are uploading to
or what...

to try to explain that: today's systems use one long line per paragraph instead
 of numerous lines of specific lengths like we used to do in days past... if
lines are longer than the buffers allocated to them, they get truncated and the
 additional characters are lost... we mainly saw this when quoting but in some
cases, it happens on import...

it is a bug or design flaw in the software accepting the postings... they
should be checking the length of the input data against the size of the buffer
and processing in chunks until all the data is handled... for some reason,
they're filling the buffer and then stuffing it into another shorter buffer
without length checks and so the tail ends of some of your paragraphs are being
 cut off...

if you reread your messages on the system you are uploading them to, you should
 see the problem and be able to report it to your operator so they can report
it to the software maintainer... if you are using news to read and write your
messages, you may want to download your messages from the server again so you
can see them and not your local copy if there is one...

i tried to not be too technical but i don't know if i was successful or not :(

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it
wrong...
... I plead "Premature Senility"
---
 * Origin:  (1:3634/12.73)
  Show ANSI Codes | Hide BBCodes | Show Color Codes | Hide Encoding | Hide HTML Tags | Show Routing
Previous Message | Next Message | Back to NOSTALGIA  <--  <--- Return to Home Page

VADV-PHP
Execution Time: 0.1289 seconds

If you experience any problems with this website or need help, contact the webmaster.
VADV-PHP Copyright © 2002-2024 Steve Winn, Aspect Technologies. All Rights Reserved.
Virtual Advanced Copyright © 1995-1997 Roland De Graaf.
v2.0.140505

Warning: Unknown: open(c:\Sessions\sess_dck6kajhhjk79rveg3jfalk3q6, O_RDWR) failed: No such file or directory (2) in Unknown on line 0 Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (c:\Sessions) in Unknown on line 0 PHP Warning: session_start(): open(c:\Sessions\sess_dck6kajhhjk79rveg3jfalk3q6, O_RDWR) failed: No such file or directory (2) in D:\wc5\http\public\VADV\include\common.inc.php on line 45 PHP Warning: Unknown: open(c:\Sessions\sess_dck6kajhhjk79rveg3jfalk3q6, O_RDWR) failed: No such file or directory (2) in Unknown on line 0 PHP Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (c:\Sessions) in Unknown on line 0