Re: DOS networking: How to use MSclient for DOS machine controllers

>
> Ahha version 3.x won't even work with networking enabled. I've had

some

> success with version 4.x, but you might consider the risk of

problems to be

> a bit too great. You could use a dual boot setup like Boot Magic or

System

> Commander to connect with the network to be on the safe side.
>
> -Bob

Well, here we are at the threshold of understanding. The debate
between DOS, Windows and Linux Controllers rages on. The arguments
remain the same; few minds get changed.

Even though I spent years struggling with making DOS machines work on
a network with Russian Roulete IRQ's, I spent money on a DOS based
solution for my first CNC project (duh). I QUICKLY remembered why I
disdain the OS. I got tired of the floppy-swap, short cryptic file
names, lack of ability to quickly edit and modify the original file
in a CAM program, etc, etc.

I ditched my paid-for (groan) DOS Controller Application and matching
driver card and loaded up several demo Windows Controller programs.
I sent my money to Art for Master5. I spent less than 300 bucks to
upgrade my Controller PC to a 900MHZ AMD card with more ram and now I
can run my CAD, CAM and controller programs in one spot. 1024 X 768
in living color! A network card took all of 10 minutes to install and
get working back to my internal network and out to the Internet. Now
I am looking at using a USB wireless game controller to be a portable
console so I can stand in front of my machine and use the joystick
control to make jog moves and start my cut files.

Could I have spent the time to get my DOS machine on the network?
Sure. I spend 10 hours a day dealing with technology challenges so
when I want to work on my hobby I want to make CHIPS!

Come over to the dark side Bob. Try a taste of the forbidden Windows
fruit. There are a lot of us lurking in the shadows!