Subj : DOS BBS in Win2000
To   : Chris Cranford
From : Craig Healy
Date : Mon Jul 10 2000 02:12 am

-> -> I have had problems with DOS apps and COM ports under NT.  It was
-> -> always an IRQ or address conflict.
->
-> The problems with NT is how Microsoft developed the software.  Window
-> 95 and 98 didn't care, if an application wanted to get down and dirty
-> with the hardware, it didn't stop it...
->
-> But in Windows NT and 2000 (since built on NT technology), Windows
-> does not permit an application to get down and dirty with the
-> hardware devices.

I understand the underlying principles of NT protecting resources.
But most DOS apps still have worked fine for me under NT.

-> So therefore, you will experience problems with
-> certain applications if not a lot of them running in DOS windows
-> under Windows which tries to talk directly to the hardware instead
-> of going through Windows.  That is why it is probably important that
-> the WinFossil be there because it will talk to windows who talks to
-> the hardware.

The FOSSIL issue is the only one I've had real problems with.  I was
working on it late on a Friday afternoon before I went on vacation.
I'm back this morning, and can find some time to experiment.  I wasn't
using WinFossil, but will try it.

My goal was to get a Wildcat 4.20 node to run using NetModem for
telnet access.  The virtual modem that NetModem created is the rub.
But, I can work on it.

Heck, I even run a 1990 DOS Risk game.  It doesn't shut down properly
as it wants to reboot the computer.  Task Manager kills it..

All my VBDOS 1 compiled programs work fine.  Even every DOS based
BBS door program has worked in local mode.  It's not been a problem
for me.

-c-

--- ViaMAIL!/WC v1.60d
 * Origin: Chowdanet! (401-331-5587) telnet://chowdanet.com  (1:323/120)

.