[NTLUG:Discuss] Possibly change server solution, instead of client ...

[Bryan J. Smith]

Courtney Grimland
> I don't know enough to know if this is a dosemu problem or a freedos 
> problem or something else entirely.
> I use an old remote access program called HyperAccess5 (HA5) to dial in 
> to machines running OS/2 via modem.  HA5 has a file transfer feature 
> that only half works when I use it under dosemu/freedos.  I can transfer 
> files from the remote machine to my computer just fine, but uploading 
> from my computer to the remote machine doesn't work.  The transfer will 
> get through about halfway and then fail.  The only other environment 
> I've used it in is Windows98, which always worked fine
> Anyone have any ideas on where I might begin to look for a solution?

- Suggestion #1:  Try FreeDOS

FreeDOS is missing a number of capabilities.  Consider DR-DOS
before trying something else.  I can send you an "evaluation" image
Lineo DR-DOS 7.03, or you can buy DR-DOS 8.0 from DeviceLogics.COM.

- Suggestion #2:  Look at server-side, instead of client ...

BTW, I've seen a lot of solutions that attempt to implement a change
in client solution, instead of addressing the server-end.  I know
the instinct is to not touch a working server solution, but sometimes
feasibility of the client becomes an issue.

E.g., a _lot_ of DOS programs are still in use.  A common way to
allow remote, multiple access is to use Concurrent DOS (DR-DOS
Virtual86 DPMS-based) or OS/2 (also DPMI services-based) with
a bank of serial connections / modems.  Then you're stuck with
some convoluted DOS/Win client that expects all sort of features.

Some clients just keep using those clients, as hard as it is to
support.  Others do far worse.  They start running the DOS programs
on Windows 2000 Terminal Server with Citrix MetaFrame XP.  ICA
might be a lean and mean protocol for GUI widgets, but it's a _poor_
solution for pumping DOS screens.

If you're just running DOS programs on Concurrent DOS or OS/2 and
pumping over serial/terminal/modem, I'd setup a Linux system.
Run the DOS sessions under XDOSEmu and then pump the display over
X11 to any X terminal over TCP/IP.  It's just as "clean," but you
can now serve it out _anywhere_ TCP/IP goes.  You can also map
network printers to LPT1:-LPT3: transparently to the DOSEmu session.

I have done this with _numerous_ DOS accounting systems.  Unlike using
Windows to SMB shares, you don't have the oplock/coherency issues
(which is a common issue, unless you setup Samba and turn off oplocks
completely -- which is a performance issue).  And unlike using TS/ICA,
it's a crapload cheaper.

And it's typically a lot cheaper than continuing to support multiple
DOS to serial/terminal/modem connections and forcing some DOS client
down users' throats.


-- 
     Linux Enthusiasts call me anti-Linux.
   Windows Enthusisats call me anti-Microsoft.
 They both must be correct because I have over a
decade of experience with both in mission critical
environments, resulting in a bigotry dedicated to
 mitigating risk and focusing on technologies ...
           not products or vendors
--------------------------------------------------
Bryan J. Smith, E.I.         b.j.smith at ieee.org