| Newsgroups |
gmane.comp.emulators.hercules390.general |
| Message-ID |
<[email protected]> |
Hi Joe
while I don't want to exclude anything currently, I nonetheless think that this is a completely different beast.
Cheers
Jürgen
---In [email protected], <joemonk64@...> wrote :
This is probably related to this reported issue...
https://github.com/hercules-390/hyperion/issues/231 https://github.com/hercules-390/hyperion/issues/231
Joe
On Sun, Jun 23, 2019 at 10:46 AM kerravon86@... mailto:kerravon86@... [hercules-390] <[email protected] mailto:[email protected]> wrote:
---In [email protected] mailto:[email protected], <kerravon86@...> wrote :
>>> (c) The binaries with the kludge
>> Here is the result from the first run of this:
> The first 3 runs were similar. But the 4th run
> gave me this on my screen:
I have completed the 10 runs, and the results
were like this:
c) juergen2: BBBCB BBCBB
A crash on the 8th run, with a bit different verbiage
on my screen:
name '0:0680 communication thread' ended
HHC00101I Thread id 00004f9c, prio 4, name '0:0681 communication thread' ended
***************
* OOPS! *
***************
HHC00101I Thread id 00006f84, prio 4, name '0:0682 communication thread' ended
Hercules has crashed!
HHC00101I Thread id 00007388, prio 4, name '0:0683 communication thread' ended
(you may or may not need to press ENTER if no 'oops!' dialog-box appears)
HHC00101I Thread id 000072b4, prio 4, name '0:0688 communication thread' ended
C:\scratch\juergen2>
BFN. Paul.