PCBOARD 15.4 - NATIVE 32bit and 64bit 🖥️

[ONiX]

(C) 2026 by Brain Patchwork DX, LLC.

ezgif-399533416722811f.png (48.71 KiB) Viewed 67839 times

[ONiX]

Every single official emoji exists in UTF-8. UTF-8 is not a collection of characters, but rather a variable-width encoding system capable of translating all 3,953 emojis pcboard 15.4 with native utf8 built in

Auto detect of caller supports UTF-8 using a technique perfected by Dr Ozz Nixon.

Native telnet server - supporting thousands of concurrent users from a single native binary.

[ONiX]

Code: Select all

 .--------------------------------------------------------------------------.
 | DOOR32 Revision 1 Specifications                 Updated: Feb 23rd, 2001 |
 `--------------------------------------------------------------------------'

  What is Door32?
  ---------------

  Door32 is a standard text-based drop file designed to take advantage of
  32-bit operating systems.  Supporting handle inheritance, it will allow
  for doors to work under multiple platforms and over both serial and
  socket (telnet) connections.

  Programming Door32 Doors
  ------------------------
  There are several freeware door libraries which support Door32 although
  most if not all of them are for Pascal at this time.  These libraries are
  able to compile doors for DOS, Windows, OS/2, and Linux.

  I personally suggest the D32 library which is freeware and comes with
  source code.  It can compile doors for DOS, Windows, OS/2 and Linux using
  various Pascal compilers.  There are other great door libraries as well,
  so give them all a try!

  Testing Door32 Support in BBS Software
  --------------------------------------
  Included in the Door32 specification archive is a Win32 executable by the
  name of SAMPLE.EXE.  This is a very simple Door32 compatible door compiled
  with the Pascal library mentioned above.  BBS authors may find this
  program useful for testing their Door32 support.

  Notes about Door32 Programming
  ------------------------------
  At this point, there seems to be two things which need to be kept
  in mind when doing Door32 programming:

     1. Under Linux or any operating system with case sensitive file names,
        the Door32 drop file (DOOR32.SYS) will be created with all lower
        cased lettering. IE:  door32.sys

     2. There appears to be a bug in the Win32 programming API (ie, a bug in
        Windows) which prevents Door32 programs from running from a batch
        file.  This means that the doors have to be executed directly from
        the software.  Instead of running MYDOOR.BAT which eventually
        executes MYDOOR.EXE, you must run MYDOOR.EXE directly.  This problem
        has said to have been fixed in Windows NT, but still exists under
        the Windows 9x platforms.

        What does this mean to BBS authors?  Not much.

        What does this mean to DOOR authors?  Maybe some changes...

        Because Door32 doors must be executed directly, there is a good
        chance that the current directory will NOT be the directory that
        your door executable is stored.  When porting an old DOS door,
        the door might assume that the system is in the same directory
        as the .EXE when loading data files.  Because of this, it is
        recommended that you have your Door switch to the directory where
        the door .EXE is located, or read that directory and use it when
        accessing door related files.  In Pascal, this is a sample of
        getting the directory where the door .EXE is found:

        Function ProgPath : String;
        Var
          Dir  : DirStr;
          Name : NameStr;
          Ext  : ExtStr;
        Begin
          FSplit (ParamStr(0), Dir, Name, Ext);
          ProgPath := Dir + '\';
        End;

        The above example will return the path where your door is located.
        Some door libraries might already switch to the directory of the
        executable, so you may not have to worry about it.

  The DOOR32.SYS Drop file
  ------------------------

  Below is the final Revision 1 version of DOOR32.SYS.  It is a straight
  DOS-style text file in all lower cased letters under operating systems
  with case sensitive file systems:

[cut here]-------------------------------------------------------------------
                                     
0                            Line 1 : Comm type (0=local, 1=serial, 2=telnet)
0                            Line 2 : Comm or socket handle
38400                        Line 3 : Baud rate
Mystic 1.07                  Line 4 : BBSID (software name and version)
1                            Line 5 : User record position (1-based)
James Coyle                  Line 6 : User's real name
g00r00                       Line 7 : User's handle/alias
255                          Line 8 : User's security level
58                           Line 9 : User's time left (in minutes)
1                            Line 10: Emulation *See Below
1                            Line 11: Current node number

[cut here]-------------------------------------------------------------------

 * The following are values we've predefined for the emulation:

 0 = Ascii
 1 = Ansi
 2 = Avatar
 3 = RIP
 4 = Max Graphics

 Avatar, RIP, and Max Graphics all have ANSI fallback support, so most door
 libraries that don't support those emulations can just use ANSI if emulation
 2, 3, or 4 is encountered.

 Conclusion
 ----------

 Thats it for the Revision 1 specifications of DOOR32.SYS.  You can find the
 latest information at the official Door32 web page:

    http://www.mysticbbs.com/door32

 You can e-mail mysticbbs@geocities.com for any questions or suggestions
 relating to Door32 or post a message in the FidoNet DOORGAMES echo
                                     

[ONiX]

A glaring question/obvious answer

Since PCBoard 15.4 is a single instance, multi-user server ~ it runs in "Headless" mode. Meaning, Sysop screen does not show the users screen.

As a single screen could not denote 2+ user screens concurrently. We did experiment, with a GUI front end, that would spawn a new CRT/Screen per connection. Real quickly the sysop's desktop became a jumbled mess of DOS-like screens scattered across the desktop.

* So, unless you NEED to see what the users are seeing, you won't ~ BUT we do offer a PCBoard SHADOW utility. It acts like a small proxy that you can wedge on a specific port parallel to the BBS. So you see everything in real-time (or you can put PCBoard Shadow into Hex Debug mode and see the characters that are being sent and received in NRT (Near-Real-Time)).

[ONiX]

New Splash Screen

(C) 2026 by Brain Patchwork DX, LLC.

ChatGPT Image Aug 5, 2026, 07_25_26 PM.png (1.95 MiB) Viewed 66787 times

[ONiX]

(C) 2026 by Brain Patchwork DX, LLC.

PCB154_LOGIN.png (7.01 KiB) Viewed 65613 times

Theme inspired by "Essential" ANSIGarden ~ hand-built. And my variants will be the Defacto ANSi ART for the BBS.