On 17.1.2012 20:16, Pinocchio wrote:
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
Behalf Of Kari Uusimaki
Sent: Tuesday, January 17, 2012 9:56 AM
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Is Pathworks32 server CTerm part exists?
On 16.1.2012 20:43, Pinocchio wrote:
P.S. Do anyone have DOS version of Pathworks in archives?
I might have PW for DOS V5 or V6 (or maybe both) someplace. Which one
do you prefer?
Kari
What a luck! Please, upload both!
Thank you!
P.S. I am not part of HECnet yet, so please upload it on some free hosting
like http://www.mediafire.com/
P.P.S. It's my secondary reply to your message. For unknown to me reason
first post seems is lost in eternity :-) (I did not receive it via mail list
for about half hour). So I performing repost now. And to be on the safe side
I am sorry for double posting in case first reply finally would find it
destination sometime.
.
Pinocchio,
It takes a while for me to find the Pathworks CD's. I have an unsorted collection of hundreds of DEC software CD's and I have to dig into the boxes and go through them to pick the right ones.
Please have patience.
When I have the CD's available, I prefer to upload them to my own VMS machine for your pick up. I'll tell you about the locations when everything is ready.
Kari
2012/1/17 Kari Uusim ki <uusimaki at exdecfinland.org>:
On 16.1.2012 20:43, Pinocchio wrote:
Thank you all, for useful information on CTERM subject!
While playing with Pathworks32 v7.4 I did found and fixed one bug, which
can
in some cases prevent successful installation of Pathworks32 at least on
W2K/W2K3 platforms. If network card service registry path (mine is
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\e1yexpress) last
component (e1yexpress) longer than 8 characters - network card would never
be listed on last installation step. So you would be unable to bind DECnet
to network interface. Of course there is always way to manually bind them
via editing registry at
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DECNDIS\Linkage\Bind,
but this way is not very convenient. Buggy component responsible for this
activity is w2k\pwbind.exe executable on installation CD. If anyone would
interested in - I can post patched binary (24k) or binary diff description
here.
P.S. Do anyone have DOS version of Pathworks in archives?
.
I might have PW for DOS V5 or V6 (or maybe both) someplace. Which one do you
prefer?
Kari
Hello!
I don't know, you pick. Now as for accessing the location, that'll be
a problem because I only have normal (What's that?) Internet access
here.
Basically either version will work for me. If you want to make both
ones available, then that's okay as well.
-----
Gregg C Levine gregg.drwho8 at gmail.com
"This signature fought the Time Wars, time and again."
On 16.1.2012 20:43, Pinocchio wrote:
Thank you all, for useful information on CTERM subject!
While playing with Pathworks32 v7.4 I did found and fixed one bug, which can
in some cases prevent successful installation of Pathworks32 at least on
W2K/W2K3 platforms. If network card service registry path (mine is
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\e1yexpress) last
component (e1yexpress) longer than 8 characters - network card would never
be listed on last installation step. So you would be unable to bind DECnet
to network interface. Of course there is always way to manually bind them
via editing registry at
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DECNDIS\Linkage\Bind,
but this way is not very convenient. Buggy component responsible for this
activity is w2k\pwbind.exe executable on installation CD. If anyone would
interested in - I can post patched binary (24k) or binary diff description
here.
P.S. Do anyone have DOS version of Pathworks in archives?
.
I might have PW for DOS V5 or V6 (or maybe both) someplace. Which one do you prefer?
Kari
On 16 Jan 2012, at 13:43, Brian Hechinger <wonko at 4amlunch.net> wrote:
2008 adds PowerShell and exposes a lot more admin features to the cli. I've never used it but I hear you can do anything in the cli you can do in the GUI.
That came in with Vista/Server 2008/Win7 so it's not really greatly applicable to PATHWORKS. I haven't used Powershell yet either but I have heard its very comprehensive.
Mark,
The cmd environment is useful, like turning off a pc, say, to make your daughter go to bed. ..
I will admit it does have uses. I was thinking along the lines of rebooting IIS every time it dies, memory leaks or stops working for other random reasons ;)
When the unix tools kit is installed a lot more functionality is available. May be I'm too fond of ascii user interfaces...
You and me both :)
--
Mark Benson
http://markbenson.org/bloghttp://twitter.com/MDBenson
2008 adds PowerShell and exposes a lot more admin features to the cli. I've never used it but I hear you can do anything in the cli you can do in the GUI.
-brian
On Jan 16, 2012, at 8:12, hvlems at zonnet.nl wrote:
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/bloghttp://twitter.com/MDBenson
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/bloghttp://twitter.com/MDBenson
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/bloghttp://twitter.com/MDBenson
Not every Windows kit contains a telnet server. XP professional does have one. It uses NTLM authentication by default. Access via say VMS requires that you switch it off. Once done it is rather useful. The commandline interface is accessible while you're far away from the Windows system. Which is not a bad thing per se ;-)
Hans
On 2012-01-16 06.16, Pinocchio wrote:
On 2012-01-15 22.15, Pinocchio wrote:
Hi guys!
Do Pathworks32 includes server part of CTerm protocol?
I mean I can setup Pathworks32 to be a file server for sharing files to
other DECnet clients.
Is such capability exists for CTerm protocol? Documentation do not
mention such function,
but I see one interesting message "TNET0005N: Pwtelnt loaded
successfully" in Pathworks32 event log.
So I am wonder, is it sign of server part of CTerm protocol presence?
You are confused. :-)
CTERM is an interactive terminal protocol. It is not used to transfer
files.
What you need is a FAL listener. And yes, I think that Pathworks 32 do
include that.
Johnny
Sorry for confusing manner of asking questions! :-)
My question is exactly about CTERM terminal protocol.
Is server part of CTERM present in pathworks32?
Ah. Now, that was a different question. :-)
(The first one was like "how do I setup telnet to share files".)
I don't think that a CTERM listener exists for Pathworks32. 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 machines are meant to be used locally, using the graphical interface. Not remotely using a plain terminal.
Johnny
On 2012-01-15 22.15, Pinocchio wrote:
Hi guys!
Do Pathworks32 includes server part of CTerm protocol?
I mean I can setup Pathworks32 to be a file server for sharing files to
other DECnet clients.
Is such capability exists for CTerm protocol? Documentation do not
mention such function,
but I see one interesting message TNET0005N: Pwtelnt loaded
successfully in Pathworks32 event log.
So I am wonder, is it sign of server part of CTerm protocol presence?
You are confused. :-)
CTERM is an interactive terminal protocol. It is not used to transfer files.
What you need is a FAL listener. And yes, I think that Pathworks 32 do include that.
Johnny
