Windows

[bob@dsl.cis.upenn.edu (Bob Applegate)]

I've got a rather primitive version of a KISS driver, an AX.25 driver, and
a simple terminal emulator running under Win3.  We were *hoping* to eventually
get an IP implementation, but it made sense to start from the bottom and work
our way up.  The current system is not acceptable for radio use, although it
generally works between two hardwired systems.

Why did it stop here?  WINDOWS IS THE MOST RIDICULOUS ENVIRONMENT TO DEVELOP
PROGRAMS FOR!  I enjoyed low-level X-windows more than this.  There are way
too many calls, lots of bizarre little rules, and MicroSoft forgot about one
tiny little feature that a few programmers have been known to use from
time-to-time: REAL IPC!  IPC is slow and cumbersome.  The Clipboard and DDE
are provided, but the original SDK had nothing to help programmers use them
properly.  IPC, in Billy-Boy's eyes, consists of happy Excel users pasting
financial charts into their Word docs.  A good thing to have, yes, but why
stop there?

Sorry, I'm rambling.  The point is, if we want to run "NOS" (generic term
for an IP system), then take an off the shelf commercial package and work
together to write a decent AX.25 transport layer that can work with that
package.

I'd rather pay $300 for a Windws program than pay a small portion of the
developer's psychiatric bill.

Flames to /dev/null

Bob, wa2zzx