| Newsgroups |
gmane.comp.emulators.hercules390.general |
| Message-ID |
<[email protected]> |
Thanks for the tip. I am now able to run
the "mvs" batch file instead of running
"startmvs2". I get the same result though.
ie no verbiage in the log file after "quit".
BFN. Paul.
---In [email protected], <joemonk64@...> wrote :
If you dont want to run in daemon mode, there is a procedure to disable that in the tk4- user manual. Simply going in rem'ing out the line is shooting yourself in the foot.
Prevent Hercules from starting in daemon mode:
o On a Windows system: Open the tk4-/unattended folder and click (or double click, depending on your settings) the set_console_mode.bat file.
Joe
On Sat, Jun 22, 2019 at 5:52 PM kerravon86@... mailto:kerravon86@... [hercules-390] <[email protected] mailto:[email protected]> wrote:
1. Unzip standard TK4-8
2. Unzip below download
3. Make this change:
C:\scratch\juergen>diff -w mvs.bat startmvs2.bat
17c17
< SET DAEMON=-d
---
> rem SET DAEMON=-d
4. Run startmvs2
5. Wait for IPL to complete
6. Type "quit"
Log file shown below is missing verbiage:
07:44:53 HHC00100I Thread id 00004f3c, prio 5, name 'impl_thread' started
07:44:53 HHC00100I Thread id 00005c48, prio 4, name 'logger_thread' started
07:44:53 HHC01413I Hercules version 4.2.0.9576-SDL-ge3c6c3aa-modified (4.2.0.9576)
....
07:46:34 HHC02264I Script 5: file scripts/tk4-.rc processing ended
07:46:38 HHC01603I quit
07:46:38 HHC01420I Begin Hercules shutdown
07:46:38 HHC00101I Thread id 000045d0, prio 4, name '3705 device(1:066B) thread' ended
07:46:38 HHC00101I Thread id 00005290, prio 4, name '3705 device(1:0662) thread' ended
07:46:38 HHC00101I Thread id 000050bc, prio 4, name '3705 device(1:0661) thread' ended
07:46:38 HHC00101I Thread id 00005070, prio 4, name '3705 device(1:0665) thread' ended
07:46:38 HHC00101I Thread id 00004430, prio 4, name '3705 device(1:0660) thread' ended
07:46:38 HHC00101I Thread id 00005e20, prio 4, name '3705 device(1:0663) thread' ended
07:46:38 HHC00101I Thread id 000066b8, prio 4, name '3705 device(1:0668) thread' ended
07:46:38 HHC00101I Thread id 0000576c, prio 4, name '3705 device(1:066A) thread' ended
07:46:38 HHC00101I Thread id 00005a94, prio 4, name '3705 device(1:0669) thread' ended
07:46:38 HHC00101I Thread id 000067ac, prio 4, name '3705 device(1:0666) thread' ended
07:46:38 HHC00101I Thread id 000057a4, prio 4, name '3705 device(1:0664) thread' ended
07:46:38 HHC00101I Thread id 00003e1c, prio 4, name '3705 device(1:0667) thread' ended
07:46:39 HHC01423I Calling termination routines
07:46:39 HHC00101I Thread id 00005e24, prio 4, name 'socket_thread' ended
07:46:39 HHC00101I Thread id 0000655c, prio 4, name 'http_server' ended
07:46:39 HHC00101I Thread id 0000452c, prio 2, name 'Processor CP00' ended
07:46:39 HHC00101I Thread id 00004600, prio 4, name 'console_connect' ended
07:46:39 HHC00101I Thread id 00002c14, prio 4, name '0:0670 communication thread' ended
07:46:39 HHC00101I Thread id 00004a78, prio 4, name '0:0671 communication thread' ended
07:46:39 HHC00101I Thread id 00004a38, prio 4, name '0:0672 communication thread' ended
07:46:39 HHC00101I Thread id 000051bc, prio 4, name '0:0673 communication thread' ended
07:46:39 HHC00101I Thread id 00005c6c, prio 4, name '0:0680 communication thread' ended
07:46:39 HHC00101I Thread id 0000631c, prio 4, name '0:0681 communication thread' ended
07:46:39 HHC00101I Thread id 000067a0, prio 4, name '0:0682 communication thread' ended
(log file ends here, without verbiage)
BTW, correct spelling for README is "explicitly" not "explicitely".
BFN. Paul.
---In [email protected] mailto:[email protected], <winkelmann@...> wrote :
Hi Paul
SDL Hyperion 4.1 is not supported with TK4-. Please build either using the current SDL Hyperion repository, or use the following to directly update TK4- Update 08 to using SDL Hyperion 4.2: https://polybox.ethz.ch/index.php/s/YZewbh59DZ7cCaE/download https://polybox.ethz.ch/index.php/s/YZewbh59DZ7cCaE/download https://polybox.ethz.ch/index.php/s/YZewbh59DZ7cCaE/download https://polybox.ethz.ch/index.php/s/YZewbh59DZ7cCaE/download . Note that this is very early alpha and as such it is in no way meant to be an official update. And: Do read the README from beginning to end. If you don't, you're guaranteed to fail.
Cheers
Jürgen
---In [email protected] mailto:[email protected], <kerravon86@...> wrote :
---In [email protected] mailto:[email protected] mailto:[email protected] mailto:[email protected], <winkelmann@...> wrote :
> Then, please, provide a complete error report
> describing a reproducible scenario.
It's an intermittent fault, so I can't guarantee
that you can reproduce it.
> it must be reproducable on SDL Hyperion 4.2.0.9576 or later.
I only found downloadables for 4.1. Here's how
to reproduce it on 4.1:
1. Make the following changes:
C:\mvs380>diff mvs.bat startmvs2.bat
17c17
< SET DAEMON=-d
---
> rem SET DAEMON=-d
36c36
< .\hercules\windows\%ARCH%\hercules %DAEMON% -f conf\tk4-.cnf >log/3033.log
---
> hercules %DAEMON% -f conf\tk4-.cnf >log/3033.log
2. Put SDL Hercules 4.1 into the PATH
3. Run startmvs2 and wait for the IPL to complete with this:
05:28:39 HHC02264I Script 5: file scripts/tk4-.rc processing ended
4. Type "quit".
5. See if the tail of 3033.log ends with:
04:26:51 HHC01424I All termination routines complete
04:26:51 HHC02103I Logger: logger thread terminating
If it does, then you *haven't* encountered the problem,
so repeat the exact same process. If you don't get
the problem after 5 runs you can probably assume
the problem is not reproducible in your environment.
Here's the problem I am seeing:
05:27:00 HHC00100I Thread id 00006794, prio 5, name 'impl_thread' started
05:27:00 HHC00100I Thread id 000065d8, prio 4, name 'logger_thread' started
05:27:00 HHC01413I Hercules version 4.1.0.9426-SDL-g42b533fa (4.1.0.9426)
...
05:28:39 HHC02264I Script 5: file scripts/tk4-.rc processing ended
05:28:42 HHC01603I quit
05:28:43 HHC01420I Begin Hercules shutdown
05:28:44 HHC01423I Calling termination routines
05:28:44 HHC00101I Thread id 0000636c, prio 4, name 'socket_thread' ended
05:28:44 HHC00101I Thread id 00006538, prio 4, name 'http_server' ended
05:28:44 HHC00101I Thread id 00006554, prio 2, name 'Processor CP00' ended
05:28:44 HHC00101I Thread id 00006158, prio 4, name 'console_connect' ended
05:28:44 HHC00101I Thread id 000064ac, prio 4, name '0:0670 communication thread' ended
05:28:44 HHC00101I Thread id 00006710, prio 4, name '0:0671 communication thread' ended
05:28:44 HHC00101I Thread id 00005a08, prio 4, name '0:0672 communication thread' ended
(that's it, that's the end of my log file).
BFN. Paul.