Mark, The cmd environment is useful, like turning off a pc, say, to make your daughter go to bed. .. When the unix tools kit is installed a lot more functionality is available. May be I'm too fond of ascii user interfaces... Hans -----Original Message----- From: Mark Benson <md.benson at gmail.com> Sender: owner-hecnet at Update.UU.SE Date: Mon, 16 Jan 2012 12:31:05 To: hecnet at Update.UU.SE<hecnet at Update.UU.SE> Reply-To: hecnet at Update.UU.SESubject: Re: [HECnet] Is Pathworks32 server CTerm part exists? On 16 Jan 2012, at 12:05, Johnny Billquist <bqt at softjar.se> wrote: I don't think that a CTERM listener exists for Pathworks32. I don't think it has one, at least not in 7.4 that I have but I am waiting on getting XP Pro so I can test the server side of PATHWORKS 32 as XP Home doesn't have the user admin tools I need to make it work. Frankly commandline access to Windows NT wouldn't be that useful anyway ;) In general remote login on Windows machines are not that common. Not sure I've ever seen a telnet server either (but I'm sure that DO exist). Windows 2000 has a TELNET server IIRC. Naturally, I turned it off ;) Windows machines are meant to be used locally, using the graphical interface. Not remotely using a plain terminal. Yes, Windows is generally a graphical environment and command terminal access is only usually used for running UNIX-like stuff largely or running batch automation/unattended install scripts and the like. Remote access *is* quite common in Windows environments but it is mostly via Remote Desktop/Terminal Services or something like Citrix handing out remote graphical desktops. Remote command terminal access is very rare. -- Mark Benson http://markbenson.org/blog http://twitter.com/MDBenson