Discussion:
Hercules Emulation of OSA Devices
(too old to reply)
Aaron Finerman arfinerman@gmail.com [hercules-390]
2018-01-21 21:28:40 UTC
Permalink
This maybe a dumb question, but why can't Hercules emulate OSA devices the
same way that zPDT does ?

Hercules Version 4: TCP/IP networking with Hercules

This page describes how to set up TCP/IP connectivity between a Hercules
machine and the outside world.
Since Hercules runs as a user process under the control of a driving system
(usually Linux/x86 or Windows), it does not have direct access to the
driving system's network adapter. This presents a problem in establishing
connectivity between the network and the TCP/IP stack of an operating
system running under Hercules.
Ivan Warren ivan@vmfacility.fr [hercules-390]
2018-01-21 21:46:16 UTC
Permalink
Post by Aaron Finerman ***@gmail.com [hercules-390]
This maybe a dumb question, but why can't Hercules emulate OSA
devices the same way that zPDT does ?
Hercules Version 4: TCP/IP networking with Hercules
This page describes how to set up TCP/IP connectivity between a
Hercules machine and the outside world.
Since Hercules runs as a user process under the control of a driving
system (usually Linux/x86 or Windows), it does not have direct access
to the driving system's network adapter. This presents a problem in
establishing connectivity between the network and the TCP/IP stack of
an operating system running under Hercules.
Aaron,

Hercules 4 emulates QETH/QDIO/OSA Adapters very well, thank you !

(Care to specify what "this page" is ? And what you show doesn't specify
that there cannot be any OSA emulation)

--Ivan



[Non-text portions of this message have been removed]
Aaron Finerman arfinerman@gmail.com [hercules-390]
2018-01-21 22:15:29 UTC
Permalink
This page is referenced in the official Hercules 390 web page. My
understanding is that this support needs CTCI-WIN and TUN/TAP software,
thru CTCI enulation. Best regards,

http://www.hercules-390.eu/hercconf.html

*CTCI* (Channel to Channel link to TCP/IP stack)

A point-to-point IP connection with the TCP/IP stack of the driving system
on which Hercules is running. See the Hercules TCP/IP
<http://www.hercules-390.eu/herctcp.html> page for details.

http://hercules-390.github.io/html/herctcp.html
Post by Ivan Warren ***@vmfacility.fr [hercules-390]
Post by Aaron Finerman ***@gmail.com [hercules-390]
This maybe a dumb question, but why can't Hercules emulate OSA
devices the same way that zPDT does ?
Hercules Version 4: TCP/IP networking with Hercules
This page describes how to set up TCP/IP connectivity between a
Hercules machine and the outside world.
Since Hercules runs as a user process under the control of a driving
system (usually Linux/x86 or Windows), it does not have direct access
to the driving system's network adapter. This presents a problem in
establishing connectivity between the network and the TCP/IP stack of
an operating system running under Hercules.
Aaron,
Hercules 4 emulates QETH/QDIO/OSA Adapters very well, thank you !
(Care to specify what "this page" is ? And what you show doesn't specify
that there cannot be any OSA emulation)
--Ivan
[Non-text portions of this message have been removed]
Ivan Warren ivan@vmfacility.fr [hercules-390]
2018-01-21 22:22:16 UTC
Permalink
Post by Aaron Finerman ***@gmail.com [hercules-390]
This page is referenced in the official Hercules 390 web page. My
understanding is that this support needs CTCI-WIN and TUN/TAP
software, thru CTCI enulation. Best regards,
Aaron,

Your understanding is wrong... TCP/IP connection (and even Ethernet L2)
can be achieved using the LCS and QETH emulations.

--Ivan


[Non-text portions of this message have been removed]
Aaron Finerman arfinerman@gmail.com [hercules-390]
2018-01-22 00:34:18 UTC
Permalink
Hi Ivan,

I have a simple statement to define an OSA adapter, and it fails on
Hyperion, because it is can't find fishlib64.dll. It does appear to have
some dependencies on other software. What am I doing wrong ?

Best regards,

0100.2 LCS 192.168.1.6

HHC00161E Function LoadLibraryEx(TunTap64.dll) failed: [126] The specified
module could not be found.
HHC00161E Function LoadLibraryEx(TunTap64.dll) failed: [126] The specified
module could not be found.
HHC00137E Error opening TUN/TAP device 00-00-5E-80-00-00: No such file or
directory
HHC00900E 0:0100 LCS: Error in function TUNTAP_CreateInterface:
HHC01463E 0:0101 device initialization failed
Post by Ivan Warren ***@vmfacility.fr [hercules-390]
Post by Aaron Finerman ***@gmail.com [hercules-390]
This page is referenced in the official Hercules 390 web page. My
understanding is that this support needs CTCI-WIN and TUN/TAP
software, thru CTCI enulation. Best regards,
Aaron,
Your understanding is wrong... TCP/IP connection (and even Ethernet L2)
can be achieved using the LCS and QETH emulations.
--Ivan
[Non-text portions of this message have been removed]
Ivan Warren ivan@vmfacility.fr [hercules-390]
2018-01-22 01:00:39 UTC
Permalink
Post by Aaron Finerman ***@gmail.com [hercules-390]
Hi Ivan,
 I have a simple statement to define an OSA adapter, and it fails on
Hyperion, because it is can't find fishlib64.dll. It does appear to
have some dependencies on other software. What am I doing wrong ?
Best regards,
0100.2  LCS     192.168.1.6
HHC00161E Function LoadLibraryEx(TunTap64.dll) failed: [126] The
specified module could not be found.
HHC00161E Function LoadLibraryEx(TunTap64.dll) failed: [126] The
specified module could not be found.
HHC00137E Error opening TUN/TAP device 00-00-5E-80-00-00: No such file
or directory
HHC01463E 0:0101 device initialization failed
Aaron,

LCS is not the same as OSA... But that's not the issue here.

You are obviously running under Windows, and you need to follow the
instruction of Fish's website (www.softdevlabs.com) to determine how to
properly install Fish's TUN/TAP emulation for Windows.

--Ivan


[Non-text portions of this message have been removed]
Aaron Finerman arfinerman@gmail.com [hercules-390]
2018-01-22 01:08:42 UTC
Permalink
Thank you Ivan. I have sent an email to SDL support and will wait for
reply. But Hyperion manual specifically mentions LCS is the emulation of an
IBM OSA. Best regards,

Hercules Emulator V4.00 – User Reference Guide Page 215
6.9.6 LCS (LAN Channel Station)
6.9.6.1 Function
This statement defines an emulated LAN Channel Station adapter. This
emulation mode appears to the
operating system running in the Hercules machine as an IBM 8232 LCS device,
an IBM 2216 router, an
IBM 3172 running ICP (Interconnect Communications Program)
, the LCS3172 driver of an IBM P/390, or an IBM Open Systems Adapter (OSA)
Post by Ivan Warren ***@vmfacility.fr [hercules-390]
Post by Aaron Finerman ***@gmail.com [hercules-390]
Hi Ivan,
I have a simple statement to define an OSA adapter, and it fails on
Hyperion, because it is can't find fishlib64.dll. It does appear to
have some dependencies on other software. What am I doing wrong ?
Best regards,
0100.2 LCS 192.168.1.6
HHC00161E Function LoadLibraryEx(TunTap64.dll) failed: [126] The
specified module could not be found.
HHC00161E Function LoadLibraryEx(TunTap64.dll) failed: [126] The
specified module could not be found.
HHC00137E Error opening TUN/TAP device 00-00-5E-80-00-00: No such file
or directory
HHC01463E 0:0101 device initialization failed
Aaron,
LCS is not the same as OSA... But that's not the issue here.
You are obviously running under Windows, and you need to follow the
instruction of Fish's website (www.softdevlabs.com) to determine how to
properly install Fish's TUN/TAP emulation for Windows.
--Ivan
[Non-text portions of this message have been removed]
Gregg Levine gregg.drwho8@gmail.com [hercules-390]
2018-01-22 02:33:01 UTC
Permalink
Hello!
Best place to ask that question is on this list. The writing fish will
only respond if you are a paying customer of his, and have graced his
fins with appropriate monetary notations. (Money.)

Now what is your configuration? And where do you have the libraries
that make up his amazing networking stack placed? Ideally they should
in your Hercules folder, and not in your Windows ones. And you might
also need his Fish Library if you're using his equally amazing GUI.

Whatever happened its definitely the fault of a yeti and a man named Dave in PA.
-----
Gregg C Levine ***@gmail.com
"This signature fought the Time Wars, time and again."
Post by Aaron Finerman ***@gmail.com [hercules-390]
Thank you Ivan. I have sent an email to SDL support and will wait for
reply. But Hyperion manual specifically mentions LCS is the emulation of an
IBM OSA. Best regards,
Hercules Emulator V4.00 – User Reference Guide Page 215
6.9.6 LCS (LAN Channel Station)
6.9.6.1 Function
This statement defines an emulated LAN Channel Station adapter. This
emulation mode appears to the
operating system running in the Hercules machine as an IBM 8232 LCS device,
an IBM 2216 router, an
IBM 3172 running ICP (Interconnect Communications Program)
, the LCS3172 driver of an IBM P/390, or an IBM Open Systems Adapter (OSA)
Post by Ivan Warren ***@vmfacility.fr [hercules-390]
Post by Aaron Finerman ***@gmail.com [hercules-390]
Hi Ivan,
I have a simple statement to define an OSA adapter, and it fails on
Hyperion, because it is can't find fishlib64.dll. It does appear to
have some dependencies on other software. What am I doing wrong ?
Best regards,
0100.2 LCS 192.168.1.6
HHC00161E Function LoadLibraryEx(TunTap64.dll) failed: [126] The
specified module could not be found.
HHC00161E Function LoadLibraryEx(TunTap64.dll) failed: [126] The
specified module could not be found.
HHC00137E Error opening TUN/TAP device 00-00-5E-80-00-00: No such file
or directory
HHC01463E 0:0101 device initialization failed
Aaron,
LCS is not the same as OSA... But that's not the issue here.
You are obviously running under Windows, and you need to follow the
instruction of Fish's website (www.softdevlabs.com) to determine how to
properly install Fish's TUN/TAP emulation for Windows.
--Ivan
[Non-text portions of this message have been removed]
Aaron Finerman arfinerman@gmail.com [hercules-390]
2018-01-22 03:09:08 UTC
Permalink
Hi, I'm running 64 bit Windows 7 and my router address is 192.168.1.1 and
my PC IP address is 192.168.1.6. I want to be able to define a OSA
simulated device and my problem is I can't get past a clean startup. I have
downloaded a trial version of CTCI-WIN and will gladly buy a copy if I can
get it to work. Fish has responded with some recommendations. I'm still not
clear if I need to use LCS or CTCI for a simulated OSA.
Best regards,
Post by Gregg Levine ***@gmail.com [hercules-390]
Hello!
Best place to ask that question is on this list. The writing fish will
only respond if you are a paying customer of his, and have graced his
fins with appropriate monetary notations. (Money.)
Now what is your configuration? And where do you have the libraries
that make up his amazing networking stack placed? Ideally they should
in your Hercules folder, and not in your Windows ones. And you might
also need his Fish Library if you're using his equally amazing GUI.
Whatever happened its definitely the fault of a yeti and a man named Dave in PA.
-----
"This signature fought the Time Wars, time and again."
Post by Aaron Finerman ***@gmail.com [hercules-390]
Thank you Ivan. I have sent an email to SDL support and will wait for
reply. But Hyperion manual specifically mentions LCS is the emulation of
an
Post by Aaron Finerman ***@gmail.com [hercules-390]
IBM OSA. Best regards,
Hercules Emulator V4.00 – User Reference Guide Page 215
6.9.6 LCS (LAN Channel Station)
6.9.6.1 Function
This statement defines an emulated LAN Channel Station adapter. This
emulation mode appears to the
operating system running in the Hercules machine as an IBM 8232 LCS
device,
Post by Aaron Finerman ***@gmail.com [hercules-390]
an IBM 2216 router, an
IBM 3172 running ICP (Interconnect Communications Program)
, the LCS3172 driver of an IBM P/390, or an IBM Open Systems Adapter
(OSA)
Post by Aaron Finerman ***@gmail.com [hercules-390]
Post by Ivan Warren ***@vmfacility.fr [hercules-390]
Post by Aaron Finerman ***@gmail.com [hercules-390]
Hi Ivan,
I have a simple statement to define an OSA adapter, and it fails on
Hyperion, because it is can't find fishlib64.dll. It does appear to
have some dependencies on other software. What am I doing wrong ?
Best regards,
0100.2 LCS 192.168.1.6
HHC00161E Function LoadLibraryEx(TunTap64.dll) failed: [126] The
specified module could not be found.
HHC00161E Function LoadLibraryEx(TunTap64.dll) failed: [126] The
specified module could not be found.
HHC00137E Error opening TUN/TAP device 00-00-5E-80-00-00: No such file
or directory
HHC01463E 0:0101 device initialization failed
Aaron,
LCS is not the same as OSA... But that's not the issue here.
You are obviously running under Windows, and you need to follow the
instruction of Fish's website (www.softdevlabs.com) to determine how to
properly install Fish's TUN/TAP emulation for Windows.
--Ivan
[Non-text portions of this message have been removed]
'\'Fish\' (David B. Trout)' david.b.trout@gmail.com [hercules-390]
2018-01-22 05:41:38 UTC
Permalink
Gregg C Levine wrote:

[...]
The writing fish will only respond if you are a paying
customer of his, and have graced his fins with appropriate
monetary notations. (Money.)
Not true!

If someone is trial testing my software before buying it and they cannot get it to work, I will certainly try my best to help them! To not do so would not make good business sense! Why should they PAY for my software if they can't get it to work? OF COURSE I will help someone who has not (yet) paid for my software!!


[...]
Now what is your configuration? And where do you have the
libraries that make up his amazing networking stack placed?
Ideally they should in your Hercules folder, and not in your
Windows ones.
NO! WRONG!

What you said would ONLY be true if they *specifically* chose to override the installer's suggested installation directory (which is normally "C:\Program Files (x86)\SoftDevLabs\CTCI-WIN"). You should install CTCI-WIN using the provided installer which defaults to "C:\Program Files (x86)\SoftDevLabs\CTCI-WIN", which is where you SHOULD normally install into.

You are probably thinking about the "old way" of "manually installing" my software from years ago. TODAY, you run the Windows installer and install it just like you would install any other software product on Windows. All of my software TODAY now comes with an official installer that installs all of the required pieces into their proper place (Visual C++ Runtime and WinPCap and FishLib, etc -- ALL required pieces) AUTOMATICALLY, and updates you PATH variable, etc, so that after installing it, just like any other product, it JUST WORKS.

That's why I wrote the installer: to make it DIRT SIMPLE and hard to get wrong. You run the installer and click, click, click... DONE! Nothing more to do! A child could do it.
And you might also need his Fish Library if you're using
his equally amazing GUI.
The proper version of "FishLib" is automatically installed (into the proper location, etc) by the installer for ALL of my software products. Again, you don't need to mess with gathering all of the pieces from various different places and manually installing anything any longer. All of my products all come with their own official Windows installer that properly installs the product -- including any/ALL pre-requisite components -- so that once the product is installed there's NOTHING MORE you need to do. Nothing. You just start *using* it: Start -> All Programs -> SoftDevLabs -> (product). Voila! The products starts up and just WORKS! (Or at least it *should*!!)



And as far as OSA on Hercules is concerned, Ivan is right: that's the QETH device. The Hercules LCS networking device is not an OSA device despite what the documentation/description says. It's a "LAN Channel Station" device, just like its name suggests.

LCS devices work great and are much better than CTCI devices (which I don't recommend using), but OSA (QETH) device are much better that LCS devices. I highly recommend their use. I've been using them without issue for a couple of years now, on both <mumble-mumble> OS and <mumble-mumble> VM as well (in both Layer 2 and Layer 3 mode). In fact, in my SDL version of Hyperion(*) you can specify "OSA" (or OSD) as your Hercules networking device type instead of "QETH" since that's really what it is.

And my upcoming release of my HercGUI product OSA devices (and CTCE devices too) are now fully supported as a result.


"Manually installing" my products (by manually copying files around into different folders and manually updating your PATH variable and then manually copying yet MORE binaries around and manually installing Visual C++ and WinPCap, etc) is SOOOO passé. F**k that sh*t. That's old school from several years ago.

Now all SoftDevLabs products come with full installers just like any of the thousands of other software products do that you install on Windows. You run the installer and click the 'Next' button a few times and VOILA! You're done and up and running.


-------------------
(*) http://www.softdevlabs.com/hyperion.html
--
"Fish" (David B. Trout)
Software Development Laboratories
http://www.softdevlabs.com
mail: ***@softdevlabs.com
Aaron Finerman arfinerman@gmail.com [hercules-390]
2018-01-23 02:42:37 UTC
Permalink
Hi, Which manual describes the format of the QETH device definition ? I
took the time to go through all the reference guides and could not find
any. There is only mention of it. Best regards

On Mon, Jan 22, 2018 at 12:41 AM, ''Fish' (David B. Trout)'
Post by '\'Fish\' (David B. Trout)' ***@gmail.com [hercules-390]
[...]
The writing fish will only respond if you are a paying
customer of his, and have graced his fins with appropriate
monetary notations. (Money.)
Not true!
If someone is trial testing my software before buying it and they cannot
get it to work, I will certainly try my best to help them! To not do so
would not make good business sense! Why should they PAY for my software if
they can't get it to work? OF COURSE I will help someone who has not (yet)
paid for my software!!
[...]
Now what is your configuration? And where do you have the
libraries that make up his amazing networking stack placed?
Ideally they should in your Hercules folder, and not in your
Windows ones.
NO! WRONG!
What you said would ONLY be true if they *specifically* chose to override
the installer's suggested installation directory (which is normally
"C:\Program Files (x86)\SoftDevLabs\CTCI-WIN"). You should install CTCI-WIN
using the provided installer which defaults to "C:\Program Files
(x86)\SoftDevLabs\CTCI-WIN", which is where you SHOULD normally install
into.
You are probably thinking about the "old way" of "manually installing" my
software from years ago. TODAY, you run the Windows installer and install
it just like you would install any other software product on Windows. All
of my software TODAY now comes with an official installer that installs all
of the required pieces into their proper place (Visual C++ Runtime and
WinPCap and FishLib, etc -- ALL required pieces) AUTOMATICALLY, and updates
you PATH variable, etc, so that after installing it, just like any other
product, it JUST WORKS.
That's why I wrote the installer: to make it DIRT SIMPLE and hard to get
wrong. You run the installer and click, click, click... DONE! Nothing more
to do! A child could do it.
And you might also need his Fish Library if you're using
his equally amazing GUI.
The proper version of "FishLib" is automatically installed (into the
proper location, etc) by the installer for ALL of my software products.
Again, you don't need to mess with gathering all of the pieces from various
different places and manually installing anything any longer. All of my
products all come with their own official Windows installer that properly
installs the product -- including any/ALL pre-requisite components -- so
that once the product is installed there's NOTHING MORE you need to do.
Nothing. You just start *using* it: Start -> All Programs -> SoftDevLabs ->
(product). Voila! The products starts up and just WORKS! (Or at least it
*should*!!)
And as far as OSA on Hercules is concerned, Ivan is right: that's the QETH
device. The Hercules LCS networking device is not an OSA device despite
what the documentation/description says. It's a "LAN Channel Station"
device, just like its name suggests.
LCS devices work great and are much better than CTCI devices (which I
don't recommend using), but OSA (QETH) device are much better that LCS
devices. I highly recommend their use. I've been using them without issue
for a couple of years now, on both <mumble-mumble> OS and <mumble-mumble>
VM as well (in both Layer 2 and Layer 3 mode). In fact, in my SDL version
of Hyperion(*) you can specify "OSA" (or OSD) as your Hercules networking
device type instead of "QETH" since that's really what it is.
And my upcoming release of my HercGUI product OSA devices (and CTCE
devices too) are now fully supported as a result.
"Manually installing" my products (by manually copying files around into
different folders and manually updating your PATH variable and then
manually copying yet MORE binaries around and manually installing Visual
C++ and WinPCap, etc) is SOOOO passé. F**k that sh*t. That's old school
from several years ago.
Now all SoftDevLabs products come with full installers just like any of
the thousands of other software products do that you install on Windows.
You run the installer and click the 'Next' button a few times and VOILA!
You're done and up and running.
-------------------
(*) http://www.softdevlabs.com/hyperion.html
--
"Fish" (David B. Trout)
Software Development Laboratories
http://www.softdevlabs.com
Ivan Warren ivan@vmfacility.fr [hercules-390]
2018-01-23 08:28:25 UTC
Permalink
Post by Aaron Finerman ***@gmail.com [hercules-390]
Hi, Which manual describes the format of the QETH device definition ?
I took the time to go through all the reference guides and could not
find any. There is only mention of it. Best regards
On Mon, Jan 22, 2018 at 12:41 AM, ''Fish' (David B. Trout)'
Aaron,

https://hercules-390.github.io/html/hercconf.html#QETH

--Ivan


[Non-text portions of this message have been removed]
Aaron Finerman arfinerman@gmail.com [hercules-390]
2018-01-23 13:02:54 UTC
Permalink
Thanks so much, Ivan. I was looking into the PDFs. Best regards,
Post by Ivan Warren ***@vmfacility.fr [hercules-390]
Post by Aaron Finerman ***@gmail.com [hercules-390]
Hi, Which manual describes the format of the QETH device definition ?
I took the time to go through all the reference guides and could not
find any. There is only mention of it. Best regards
On Mon, Jan 22, 2018 at 12:41 AM, ''Fish' (David B. Trout)'
Aaron,
https://hercules-390.github.io/html/hercconf.html#QETH
--Ivan
[Non-text portions of this message have been removed]
Gregg Levine gregg.drwho8@gmail.com [hercules-390]
2018-01-23 02:48:12 UTC
Permalink
Hello!
You raise an interesting and compelling point for someone who is not a
member of the marlin family. But don't get your scales in a snit, as
it happens that was one of my many (and typically around here wrong)
opinions.

Just because the few times I've successfully run Hercules on this
laptop, that's the way I've done it. Oddly enough I've even gotten an
early release of Debian through Hercules and your libraries and
everything else involved on a system who was 32 bit and ran Win98SE
but I never got very far with it.

And if our correspondent is successful it will add something else to
the group.
-----
Gregg C Levine ***@gmail.com
"This signature fought the Time Wars, time and again."


On Mon, Jan 22, 2018 at 12:41 AM, ''Fish' (David B. Trout)'
Post by '\'Fish\' (David B. Trout)' ***@gmail.com [hercules-390]
[...]
The writing fish will only respond if you are a paying
customer of his, and have graced his fins with appropriate
monetary notations. (Money.)
Not true!
If someone is trial testing my software before buying it and they cannot get it to work, I will certainly try my best to help them! To not do so would not make good business sense! Why should they PAY for my software if they can't get it to work? OF COURSE I will help someone who has not (yet) paid for my software!!
[...]
Now what is your configuration? And where do you have the
libraries that make up his amazing networking stack placed?
Ideally they should in your Hercules folder, and not in your
Windows ones.
NO! WRONG!
What you said would ONLY be true if they *specifically* chose to override the installer's suggested installation directory (which is normally "C:\Program Files (x86)\SoftDevLabs\CTCI-WIN"). You should install CTCI-WIN using the provided installer which defaults to "C:\Program Files (x86)\SoftDevLabs\CTCI-WIN", which is where you SHOULD normally install into.
You are probably thinking about the "old way" of "manually installing" my software from years ago. TODAY, you run the Windows installer and install it just like you would install any other software product on Windows. All of my software TODAY now comes with an official installer that installs all of the required pieces into their proper place (Visual C++ Runtime and WinPCap and FishLib, etc -- ALL required pieces) AUTOMATICALLY, and updates you PATH variable, etc, so that after installing it, just like any other product, it JUST WORKS.
That's why I wrote the installer: to make it DIRT SIMPLE and hard to get wrong. You run the installer and click, click, click... DONE! Nothing more to do! A child could do it.
And you might also need his Fish Library if you're using
his equally amazing GUI.
The proper version of "FishLib" is automatically installed (into the proper location, etc) by the installer for ALL of my software products. Again, you don't need to mess with gathering all of the pieces from various different places and manually installing anything any longer. All of my products all come with their own official Windows installer that properly installs the product -- including any/ALL pre-requisite components -- so that once the product is installed there's NOTHING MORE you need to do. Nothing. You just start *using* it: Start -> All Programs -> SoftDevLabs -> (product). Voila! The products starts up and just WORKS! (Or at least it *should*!!)
And as far as OSA on Hercules is concerned, Ivan is right: that's the QETH device. The Hercules LCS networking device is not an OSA device despite what the documentation/description says. It's a "LAN Channel Station" device, just like its name suggests.
LCS devices work great and are much better than CTCI devices (which I don't recommend using), but OSA (QETH) device are much better that LCS devices.. I highly recommend their use. I've been using them without issue for a couple of years now, on both <mumble-mumble> OS and <mumble-mumble> VM as well (in both Layer 2 and Layer 3 mode). In fact, in my SDL version of Hyperion(*) you can specify "OSA" (or OSD) as your Hercules networking device type instead of "QETH" since that's really what it is.
And my upcoming release of my HercGUI product OSA devices (and CTCE devices too) are now fully supported as a result.
"Manually installing" my products (by manually copying files around into different folders and manually updating your PATH variable and then manually copying yet MORE binaries around and manually installing Visual C++ and WinPCap, etc) is SOOOO passé. F**k that sh*t. That's old school from several years ago.
Now all SoftDevLabs products come with full installers just like any of the thousands of other software products do that you install on Windows. You run the installer and click the 'Next' button a few times and VOILA! You're done and up and running.
-------------------
(*) http://www.softdevlabs.com/hyperion.html
--
"Fish" (David B. Trout)
Software Development Laboratories
http://www.softdevlabs.com
------------------------------------
------------------------------------
http://groups.yahoo.com/group/hercules-390
http://www.hercules-390.org
------------------------------------
Yahoo Groups Links
' Richard Pinion' rpinion@netscape.com [hercules-390]
2018-01-22 03:37:33 UTC
Permalink
Aaron Finerman arfinerman@gmail.com [hercules-390]
2018-01-22 03:52:27 UTC
Permalink
This is the error I get. Do you have the same version of TunTap64.dll ?
Best Regards,

0100.2 LCS -n 192.168.1.1 192.168.1.6

HHC04100I TunTap64.dll version 3.2.1.160 initiated
HHC00137E Error opening TUN/TAP device 192.168.1.1: No error
HHC00900E 0:0100 LCS: Error in function TUNTAP_CreateInterface:
HHC01463E 0:0101 device initialization failed
HHC00137E Error opening TUN/TAP device 192.168.1.100: No error
I have a similar setup and I use LCS. This from my Hercules config file.
0E20-0E21 LCS -n 192.168.1.92 192.168.1.105
Richard and Vickie Pinion
Subject: Re: [hercules-390] Hercules Emulation of OSA Devices
Date: Sun, 21 Jan 2018 22:09:08 -0500
Hi, I'm running 64 bit Windows 7 and my router address is 192.168.1.1 and
my PC IP address is 192.168.1.6. I want to be able to define a OSA
simulated device and my problem is I can't get past a clean startup. I have
downloaded a trial version of CTCI-WIN and will gladly buy a copy if I can
get it to work. Fish has responded with some recommendations. I'm still not
clear if I need to use LCS or CTCI for a simulated OSA.
Best regards,
Hello!
Best place to ask that question is on this list. The writing fish will
only respond if you are a paying customer of his, and have graced his
fins with appropriate monetary notations. (Money.)
Now what is your configuration? And where do you have the libraries
that make up his amazing networking stack placed? Ideally they should
in your Hercules folder, and not in your Windows ones. And you might
also need his Fish Library if you're using his equally amazing GUI.
Whatever happened its definitely the fault of a yeti and a man named Dave
in PA.
-----
"This signature fought the Time Wars, time and again."
Post by Aaron Finerman ***@gmail.com [hercules-390]
Thank you Ivan. I have sent an email to SDL support and will wait for
reply. But Hyperion manual specifically mentions LCS is the emulation of
an
Post by Aaron Finerman ***@gmail.com [hercules-390]
IBM OSA. Best regards,
Hercules Emulator V4.00 – User Reference Guide Page 215
6.9.6 LCS (LAN Channel Station)
6.9.6.1 Function
This statement defines an emulated LAN Channel Station adapter. This
emulation mode appears to the
operating system running in the Hercules machine as an IBM 8232 LCS
device,
Post by Aaron Finerman ***@gmail.com [hercules-390]
an IBM 2216 router, an
IBM 3172 running ICP (Interconnect Communications Program)
, the LCS3172 driver of an IBM P/390, or an IBM Open Systems Adapter
(OSA)
Post by Aaron Finerman ***@gmail.com [hercules-390]
Post by Ivan Warren ***@vmfacility.fr [hercules-390]
Post by Aaron Finerman ***@gmail.com [hercules-390]
Hi Ivan,
I have a simple statement to define an OSA adapter, and it fails on
Hyperion, because it is can't find fishlib64.dll. It does appear to
have some dependencies on other software. What am I doing wrong ?
Best regards,
0100.2 LCS 192.168.1.6
HHC00161E Function LoadLibraryEx(TunTap64.dll) failed: [126] The
specified module could not be found.
HHC00161E Function LoadLibraryEx(TunTap64.dll) failed: [126] The
specified module could not be found.
HHC00137E Error opening TUN/TAP device 00-00-5E-80-00-00: No such file
or directory
HHC01463E 0:0101 device initialization failed
Aaron,
LCS is not the same as OSA... But that's not the issue here.
You are obviously running under Windows, and you need to follow the
instruction of Fish's website (www.softdevlabs.com) to determine how to
properly install Fish's TUN/TAP emulation for Windows.
--Ivan
[Non-text portions of this message have been removed]
------------------------------
Netscape. Just the Net You Need.
' Richard Pinion' rpinion@netscape.com [hercules-390]
2018-01-22 03:56:27 UTC
Permalink
Aaron Finerman arfinerman@gmail.com [hercules-390]
2018-01-22 04:26:18 UTC
Permalink
Yes. It looks like there are all there. Thank you for your help Since this
seems to be related to Software Development Lab, I'll seek his help off
list. Best regards,
Do you have CTCI-WIN_3.3.3.3285_x64_std_setup, FishLib_2.12.0_x64_min_setup,
and
WinPcap_4_1_3 installed?
Richard and Vickie Pinion
Subject: Re: [hercules-390] Hercules Emulation of OSA Devices
Date: Sun, 21 Jan 2018 22:52:27 -0500
This is the error I get. Do you have the same version of TunTap64.dll ?
Best Regards,
0100.2 LCS -n 192.168.1.1 192.168.1.6
HHC04100I TunTap64.dll version 3.2.1.160 initiated
HHC00137E Error opening TUN/TAP device 192.168.1.1: No error
HHC01463E 0:0101 device initialization failed
HHC00137E Error opening TUN/TAP device 192.168.1.100: No error
I have a similar setup and I use LCS. This from my Hercules config file.
0E20-0E21 LCS -n 192.168.1.92 192.168.1.105
Richard and Vickie Pinion
Subject: Re: [hercules-390] Hercules Emulation of OSA Devices
Date: Sun, 21 Jan 2018 22:09:08 -0500
Hi, I'm running 64 bit Windows 7 and my router address is 192.168.1.1 and
my PC IP address is 192.168.1.6. I want to be able to define a OSA
simulated device and my problem is I can't get past a clean startup. I have
downloaded a trial version of CTCI-WIN and will gladly buy a copy if I can
get it to work. Fish has responded with some recommendations. I'm still not
clear if I need to use LCS or CTCI for a simulated OSA.
Best regards,
Hello!
Best place to ask that question is on this list. The writing fish will
only respond if you are a paying customer of his, and have graced his
fins with appropriate monetary notations. (Money.)
Now what is your configuration? And where do you have the libraries
that make up his amazing networking stack placed? Ideally they should
in your Hercules folder, and not in your Windows ones. And you might
also need his Fish Library if you're using his equally amazing GUI.
Whatever happened its definitely the fault of a yeti and a man named Dave
in PA.
-----
"This signature fought the Time Wars, time and again."
Post by Aaron Finerman ***@gmail.com [hercules-390]
Thank you Ivan. I have sent an email to SDL support and will wait for
reply. But Hyperion manual specifically mentions LCS is the emulation of
an
Post by Aaron Finerman ***@gmail.com [hercules-390]
IBM OSA. Best regards,
Hercules Emulator V4.00 – User Reference Guide Page 215
6.9.6 LCS (LAN Channel Station)
6.9.6.1 Function
This statement defines an emulated LAN Channel Station adapter. This
emulation mode appears to the
operating system running in the Hercules machine as an IBM 8232 LCS
device,
Post by Aaron Finerman ***@gmail.com [hercules-390]
an IBM 2216 router, an
IBM 3172 running ICP (Interconnect Communications Program)
, the LCS3172 driver of an IBM P/390, or an IBM Open Systems Adapter
(OSA)
Post by Aaron Finerman ***@gmail.com [hercules-390]
Post by Ivan Warren ***@vmfacility.fr [hercules-390]
Post by Aaron Finerman ***@gmail.com [hercules-390]
Hi Ivan,
I have a simple statement to define an OSA adapter, and it fails on
Hyperion, because it is can't find fishlib64.dll. It does appear to
have some dependencies on other software. What am I doing wrong ?
Best regards,
0100.2 LCS 192.168.1.6
HHC00161E Function LoadLibraryEx(TunTap64.dll) failed: [126] The
specified module could not be found.
HHC00161E Function LoadLibraryEx(TunTap64.dll) failed: [126] The
specified module could not be found.
HHC00137E Error opening TUN/TAP device 00-00-5E-80-00-00: No such file
or directory
HHC01463E 0:0101 device initialization failed
Aaron,
LCS is not the same as OSA... But that's not the issue here.
You are obviously running under Windows, and you need to follow the
instruction of Fish's website (www.softdevlabs.com) to determine how to
properly install Fish's TUN/TAP emulation for Windows.
--Ivan
[Non-text portions of this message have been removed]
------------------------------
Netscape. Just the Net You Need.
------------------------------
Netscape. Just the Net You Need.
Continue reading on narkive:
Loading...