Re: [Simh] Moved my vaxuser to new standalone system and ...

2018-07-02 Thread Mark Pizzolato
On Sunday, July 1, 2018 at 7:07 PM, James Laferriere wrote:
>   Hello All ,  Found the entry in the .ini file that was causing the 
> problem
> ...
> 
>   SET CPU MODEL=VAXStation
> 
>   I'll try tomorrow
> 
>   SET QVSS ENABLE
> 
>   To see if there is a difference .

There won't be a difference.  These are effectively equivalent. Statements.

When asking for help it is most valuable for you to provide the configuration 
file which you are using that creates the problem.  Merely displaying what the 
simulator looks like after the problem has occurred is not sufficient input.
Meanwhile, you can invoke a configuration file from the "sim>" prompt with the 
-v switch (sim> do -v config-file.ini) which will display each command as it is 
processed and if there are errors the specific command(s) which produced the 
errors will be more obvious.  If you're using the default configuration file 
name (i.e. simulator-name.ini), then you can invoke the simulator with the -V 
switch which will display the default file as it is being processed (i.e. vax 
-V).

Meanwhile, back to your problem.  I installed Slackware 14.2, upgraded 
EVERYTHING and installed SDL2 and ultimately got a clean vax simulator build 
after upgrading everything again.  Once I got a clean build, I was able to:

MicroVAX 3900 simulator V4.0-0 Currentgit commit id: 8c0439fe
sim> set cpu model=vaxstation
QVSS Display Created.  Uncaptured Input Mode
sim> set qvss enable
sim> show version
VAXStation 3900 (KA655) simulator V4.0-0 Current
Simulator Framework Capabilities:
64b data
64b addresses
Threaded Ethernet Packet transports:PCAP:TAP:NAT:UDP
Idle/Throttling support is available
Virtual Hard Disk (VHD) support
RAW disk and CD/DVD ROM support
Asynchronous I/O support (Lock free asynchronous event queue)
Asynchronous Clock support
FrontPanel API Version 12
Host Platform:
Compiler: GCC 5.3.0
Simulator Compiled as C arch: x64 (Release Build) on Jul  2 
2018 at 03:39:26
Memory Access: Little Endian
Memory Pointer Size: 64 bits
Large File (>2GB) support
SDL Video support: SDL Version 2.0.8
PCRE RegEx (Version 8.39 2016-06-14) support for EXPECT commands
OS clock resolution: 1ms
Time taken by msleep(1): 1ms
OS: Linux slackware-14 4.4.14 #2 SMP Fri Jun 24 13:38:27 CDT 
2016 x86_64 Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz GenuineIntel GNU/Linux
git commit id: 8c0439fe
git commit time: 2018-06-24T03:21:22-0700
sim>

The SET CPU MODEL=VAXSTATION command created the video window as expected.

You are not working with the latest simh code.  Please pick up the latest code 
from the master branch at https://github.com/simh/simh If your problem 
persists, please create an issue at https://github.com/simh/simh/issues to 
further track this to ground.

FYI, the build on my test slackware environment looks like:

bash-4.3# make vax
lib paths are: /lib64/ /usr/lib64/ /usr/lib64/seamonkey/
include paths are:  /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/include 
/usr/local/include /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/include-fixed 
/usr/include
using libm: /usr/lib64/libm.so
using librt: /usr/lib64/librt.so
using libpthread: /usr/lib64/libpthread.so /usr/include/pthread.h
using libpcreposix: /usr/lib64/libpcreposix.so /usr/lib64/libpcre.so 
/usr/include/pcreposix.h /usr/include/pcre.h
using semaphore: /usr/include/semaphore.h
using libdl: /usr/lib64/libdl.so /usr/include/dlfcn.h
using libpng: /usr/lib64/libpng.so /usr/include/png.h
using mman: /usr/include/sys/mman.h
using libSDL2: /usr/include/SDL2/SDL.h
using libpcap: /usr/include/pcap.h
*** Info ***
*** Info *** vax Simulator are being built with
*** Info *** minimal libpcap networking support
*** Info ***
*** Info ***
*** Info *** Simulators on your Linux platform can also be built with
*** Info *** extended LAN Ethernet networking support by using VDE 
Ethernet.
*** Info ***
*** Info *** To build simulator(s) with extended networking support you
*** Info *** should read 0readme_ethernet.txt and follow the 
instructions
*** Info *** regarding the needed libvdeplug components for your Linux
*** Info *** platform
*** Info ***
***
*** vax Simulator being built with:
*** - compiler optimizations and no debugging support. GCC Version: 
5.3.0.
*** - dynamic networking support using Linux provided libpcap 
components.
*** - Local LAN packet

Re: [Simh] Moved my vaxuser to new standalone system and ...

2018-07-02 Thread Matt Burke
On 26/06/2018 23:24, James W. Laferriere wrote:
>
> With the above I am getting 
>
> sim> boot cpu
> No protocol specified
> No protocol specified
> xcb_connection_has_error() returned true
> No protocol specified
> xcb_connection_has_error() returned true
> No protocol specified
> QVSS: Error Creating Video Window: No available video device
>
> File open error, PC:  (HALT)
>
>
This looks like SDL is having problems connecting to the X server. Is
the DISPLAY environment variable set and are you able to run other
Xwindows applications from the command line? Perhaps try xdpyinfo.

It could also be an X11 access control problem. A quick search online
for X11 "no protocol specified" showed a few people having problems
running X11 applications as root (and I noticed you are running simh as
root). The problem was due to a missing .Xauthority file for the root
user. Check the environment variable XAUTHORITY.

Matt
___
Simh mailing list
Simh@trailing-edge.com
http://mailman.trailing-edge.com/mailman/listinfo/simh

Re: [Simh] Moved my vaxuser to new standalone system and ...

2018-07-02 Thread James W. Laferriere

Hello Matt ,

On Mon, 2 Jul 2018, Matt Burke wrote:

On 26/06/2018 23:24, James W. Laferriere wrote:


With the above I am getting 

sim> boot cpu
No protocol specified
No protocol specified
xcb_connection_has_error() returned true
No protocol specified
xcb_connection_has_error() returned true
No protocol specified
QVSS: Error Creating Video Window: No available video device

File open error, PC:  (HALT)



This looks like SDL is having problems connecting to the X server. Is
the DISPLAY environment variable set and are you able to run other
Xwindows applications from the command line? Perhaps try xdpyinfo.

It could also be an X11 access control problem. A quick search online
for X11 "no protocol specified" showed a few people having problems
running X11 applications as root (and I noticed you are running simh as
root). The problem was due to a missing .Xauthority file for the root
user. Check the environment variable XAUTHORITY.
Matt


	The difficulty was exactly running as root and doing a "su - vaxuser" 
and expecting X to function under roots window control .


SET CPU TYPE=VAXStation
Works fine .

	(Poorly) In my defense I had been regularly doing that on the 
previous remote session .  Bad habits die hard .


	So now I have a qvss window but have been wondering why after 
executing the 'boot cpu' sequence that the output/input isn't transfered to 
the qvss window ?  Just a wondering not a difficulty I'll try the VMS instance I 
have and see if it'll populate that window .


Thanks goes to both ,  Mark Pizzolato & Matt Burke .

Hopefully there'll be less noise from me from now on ;-)

Twyl ,  JimL
--
+--+
| James   W.   Laferriere | SystemTechniques | Give me VMS |
| Network&System Engineer | 3237 Holden Road |  Give me Linux  |
| bab...@baby-dragons.com | Fairbanks, AK. 99709 |   only  on  AXP |
+--+
___
Simh mailing list
Simh@trailing-edge.com
http://mailman.trailing-edge.com/mailman/listinfo/simh