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 Windows95  <--  <--- Return to Home Page
   Networked Database  Windows95   [159 / 486] RSS
 From   To   Subject   Date/Time 
Message   Daryl Stout    mark lewis   Re: Old mail and new!   October 22, 2016
 8:31 PM *  

Mark,

 ml@> yo're looking at this too deeply or something... it appears that
 ml@> there's a simple serial number being used... it is incremented each
 ml@> time one is pulled... the problem is that with all your switching back
 ml@> and forth from package to package and reinstalling and such, the
 ml@> counter starts over each time... ask steve where the counter is stored
 ml@> so you can edit it to a higher value and the duplication of serial
 ml@> numbers will be thwarted... i don't know if it is VFIDO that is putting
 ml@> the MSGID into the messages or not... i would think NOT because it
 ml@> wouldn't be able to properly support the REPLY control lines but
 ml@> anyway, just figure out how to change that number and then keep up with
 ml@> that file in case you decide to switch again or have to reinstall VADV
 ml@> again...

  Steve is so busy with other things that I have no idea when I'll get
a reply.

  I really don't want to try to go to another BBS and set up an account
to read echoes...I prefer them on my BBS, but some of the message 
networks I have only offer FTN access, and NOT QWK Networking.

  To make matters worse, the file transfer deal (VXYZ) apparently is
timing out on some transfers. Then, CEXYZ locked on me when I tried to
get this packet, and would not take a test file upload.

  If this wasn't bad enough, my Mom's copy of Windows 7 32-bit that
we bought from Amazon apparently has an invalid key. When we tried
to get support, or contact them...never mind trying to get a new 
copy...we were bombarded with "upgrade to Windows 10". I said "SCREW
THAT!!". So, we went on Amazon, and ordered a new copy, which was $50
more than what we paid when we ordered it earlier this month. I guess
M$ is trying to get rid of all the copies of anything before Windows
10, and FORCE everyone to go to it.

  Then, after the DYN DDoS crash on Friday (thankfully, my Mom and
I were out on errands much of the day), and all this mess...I've
about had it with computers this week.

  I really don't want to change software, and I'd rather drop all of
the message networks, and make it a local board only. No one else
reads the other areas anyway.

Daryl

... A computer's attention span is limited by its power cord.
--- MultiMail/Win32 v0.50
                               
--- Virtual Advanced Ver 2 for DOS 
 * ORIGIN: The Thunderbolt BBS - wx1der.dyndns.org (1:19/33)
  Show ANSI Codes | Hide BBCodes | Show Color Codes | Hide Encoding | Hide HTML Tags | Show Routing
Previous Message | Next Message | Back to Windows95  <--  <--- Return to Home Page

VADV-PHP
Execution Time: 0.0826 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_dk4trt3qlafu659v5eikmk5o42, 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_dk4trt3qlafu659v5eikmk5o42, 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_dk4trt3qlafu659v5eikmk5o42, 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