On Wed, 11 Jun 2014, Hans Vlems wrote:
What is the value for intstackpages? May be as low as 4 and must be at least 6 (iirc)
25.
Also: progress:
MOIRA::CSMELOSKY$ type sys$manager:DECW$SERVER_0_ERROR.LOG
11-JUN-2014 05:35:07.0 Hello, this is the X server
This is the DECwindows X11 display server for OpenVMS VAX V7.1-010215
compiled on Feb 15 2001 at 08:53:03
Dixmain address=00019c58
Server is running in bug-compatible mode
Now attach all known txport images
Can't start transports
Yet:
$ decw$device == "GAA0,GAB0,WSA1,WSA2,WSA3,WSA4,WSA4"
$ ! decw$default_keyboard_map == "US_LK401AA"
$ decw$server_transports == "DECNET,LOCAL,TCPIP"
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
What is the value for intstackpages? May be as low as 4 and must be at least 6 (iirc)
Verzonden vanaf mijn BlackBerry 10-smartphone.
Origineel bericht
Van: Brian Schenkenberger, VAXman-
Verzonden: woensdag 11 juni 2014 03:12
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Latest version of VWS
Cory Smelosky <b4 at gewt.net> writes:
On Tue, 10 Jun 2014, Brian Schenkenberger, VAXman- wrote:
8192. Looks like SET FILE/ATTRIB=LRL:8192 EWS012.A allowed BACKUP/LIST
EWS012.A/SAVE to succeed.
VMS DUMP the first block. You should see the BACKUP command in the ASCII
translation. If there's a /BLOCK listed, use that value; otherwise, there
are defaults as you have discovered.
Didn't even need to DUMP it. VMSINSTAL didn't complain.
Don't feel bad, I've been dealing with this for 20 years when trying to get
VMS crash dump files from customers sent to me in tact via the internet. ;)
I'm impressed I figured out that LRL was the value I wanted. ;)
Luck. ;)
Yup. ;)
Next battle: anything graphical logs this:
%%%%%%%%%%% OPCOM 10-JUN-2014 19:25:19.33 %%%%%%%%%%%
Message from user AUDIT$SERVER on MOIRA
Security alarm (SECURITY) and security audit (SECURITY) on MOIRA, system
id: 9217
Auditable event: Detached process login failure
Event time: 10-JUN-2014 19:25:19.32
PID: 20200149
Process name: _WSA3:
Username: SYSTEM
Process owner: [SYSTEM]
Image name: MOIRA$DKA0:[SYS0.SYSCOMMON.][SYSEXE]LOGINOUT.EXE
Status: %DECW-F-NOMSG, Message number 02DB8204
Which makes no sense.
$ SET MESSAGE SYS$MESSAGE:DECW$XLIBMSG.EXE
$ EXIT %X02DB8204
%XLIB-F-CANTOPEN, cannot open display
Do you, indeed, have the DECWindows server started?
Is there a Gxx0: device? Configured? Channels assigned?
Try setting SYSGEN parameter STARTUP_P2 to "VDC" in a conversational boot
and then continue. You will find a STARTUP.LOG file in SYS$SYSTEM which
might hold some clues. ;)
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
I speak to machines with the voice of humanity.
On Tue, 10 Jun 2014, Cory Smelosky wrote:
I put the graphics board in the VS4000/60 (boot node)
Device GFA0:, device type DECwindows output device, is online, enabled as
operator terminal.
Error count 0 Operations completed 4
Owner process "" Owner UIC [SYSTEM]
Owner process ID 00000000 Dev Prot S:RWPL,O:RWPL,G:RWPL,W:RWPL
Reference count 0 Default buffer size 80
MOIRA::CSMELOSKY$
%%%%%%%%%%% OPCOM 11-JUN-2014 03:19:42.61 %%%%%%%%%%%
Message from user AUDIT$SERVER on MOIRA
Security alarm (SECURITY) and security audit (SECURITY) on MOIRA, system id: 9217
Auditable event: Detached process login failure
Event time: 11-JUN-2014 03:19:42.60
PID: 20200127
Username: SYSTEM
Process owner: [SYSTEM]
Image name: MOIRA$DKA0:[SYS0.SYSCOMMON.][SYSEXE]LOGINOUT.EXE
Status: %DECW-F-NOMSG, Message number 02DB8204
No change. Other ideas? ;)
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
On 06/10/2014 10:39 PM, Lee Gleason wrote:
I'd do the same...except the cable doesn't provide an internal SCSI
port...does it? I don't have any cables spare that would work I don't
think.
You'd need the expansion plate, I believe, because it provided the
interface
to the external disk and the rudimentary SCSI for the TK50Z.
Connection-wise, all it takes is a 50 pin cable from the 50 pin IDC
connector on the motherboard to a 50 pin narrow SCSI disk. I bolted the
disk into the compartment in the unit where the RD54 was (used rubber
spacers under it to suppress the noise even more).
...but it still goes "rrrrRRRRRRRRRRRRRR!" when it loads heads! ;)
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
I'd do the same...except the cable doesn't provide an internal SCSI
port...does it? I don't have any cables spare that would work I don't
think.
You'd need the expansion plate, I believe, because it provided the interface
to the external disk and the rudimentary SCSI for the TK50Z.
Connection-wise, all it takes is a 50 pin cable from the 50 pin IDC connector on the motherboard to a 50 pin narrow SCSI disk. I bolted the disk into the compartment in the unit where the RD54 was (used rubber spacers under it to suppress the noise even more).
--
Lee K. Gleason N5ZMR
Control-G Consultants
lee.gleason at comcast.net
For the two or three people that may care, I ported the latest version of
the HECnet bridge to Windows. This isn't a MinGW or Cygwin port, but a
native Win32 console version.
I've been able to use it with Windows NT 4.0 Terminal Server, and binding
Pathworks 7 on a loopback interface, and then using HECnetNT to bridge it to
a Linux box with HECnet, that had a SIMH VAX. Memory and CPU utilization
seems to be pretty small.
As an added bonus I added support for Ethernet_II so you can build NetWare
networks, and added in LZSS if desired to make compressed bridges. However
it'll parse original configurations, and operate in a normal uncompressed
manner by default.
I uploaded it to sourceforge here:
http://sourceforge.net/projects/hecnetnt/
Thanks!
Jason
On Tue, 10 Jun 2014, Cory Smelosky wrote:
Doesn't make sense.
MOIRA::CSMELOSKY$ @sys$startup:decw$startup
%DECW-W-NODEVICE, No graphics device found on this system
-DECW-I-NODECW, DECwindows graphics drivers will not be loaded
MOIRA::CSMELOSKY$
MOIRA::CSMELOSKY$ @sys$startup:ews$startup
MOIRA::CSMELOSKY$
%%%%%%%%%%% OPCOM 10-JUN-2014 20:06:57.19 %%%%%%%%%%%
Message from user DECNET on MOIRA
DECnet event 0.3, automatic line service
On Tue, 10 Jun 2014, Brian Schenkenberger, VAXman- wrote:
$ SET MESSAGE SYS$MESSAGE:DECW$XLIBMSG.EXE
$ EXIT %X02DB8204
%XLIB-F-CANTOPEN, cannot open display
Do you, indeed, have the DECWindows server started?
Is there a Gxx0: device? Configured? Channels assigned?
DECWindows is started and I do NOT have a Gxx0: device.
Try setting SYSGEN parameter STARTUP_P2 to "VDC" in a conversational boot
and then continue. You will find a STARTUP.LOG file in SYS$SYSTEM which
might hold some clues. ;)
I would...except the error is generated from VAXELN. ;)
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
Cory Smelosky <b4 at gewt.net> writes:
On Tue, 10 Jun 2014, Brian Schenkenberger, VAXman- wrote:
8192. Looks like SET FILE/ATTRIB=LRL:8192 EWS012.A allowed BACKUP/LIST
EWS012.A/SAVE to succeed.
VMS DUMP the first block. You should see the BACKUP command in the ASCII
translation. If there's a /BLOCK listed, use that value; otherwise, there
are defaults as you have discovered.
Didn't even need to DUMP it. VMSINSTAL didn't complain.
Don't feel bad, I've been dealing with this for 20 years when trying to get
VMS crash dump files from customers sent to me in tact via the internet. ;)
I'm impressed I figured out that LRL was the value I wanted. ;)
Luck. ;)
Yup. ;)
Next battle: anything graphical logs this:
%%%%%%%%%%% OPCOM 10-JUN-2014 19:25:19.33 %%%%%%%%%%%
Message from user AUDIT$SERVER on MOIRA
Security alarm (SECURITY) and security audit (SECURITY) on MOIRA, system
id: 9217
Auditable event: Detached process login failure
Event time: 10-JUN-2014 19:25:19.32
PID: 20200149
Process name: _WSA3:
Username: SYSTEM
Process owner: [SYSTEM]
Image name: MOIRA$DKA0:[SYS0.SYSCOMMON.][SYSEXE]LOGINOUT.EXE
Status: %DECW-F-NOMSG, Message number 02DB8204
Which makes no sense.
$ SET MESSAGE SYS$MESSAGE:DECW$XLIBMSG.EXE
$ EXIT %X02DB8204
%XLIB-F-CANTOPEN, cannot open display
Do you, indeed, have the DECWindows server started?
Is there a Gxx0: device? Configured? Channels assigned?
Try setting SYSGEN parameter STARTUP_P2 to "VDC" in a conversational boot
and then continue. You will find a STARTUP.LOG file in SYS$SYSTEM which
might hold some clues. ;)
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
I speak to machines with the voice of humanity.
On Tue, 10 Jun 2014, Brian Schenkenberger, VAXman- wrote:
8192. Looks like SET FILE/ATTRIB=LRL:8192 EWS012.A allowed BACKUP/LIST
EWS012.A/SAVE to succeed.
VMS DUMP the first block. You should see the BACKUP command in the ASCII
translation. If there's a /BLOCK listed, use that value; otherwise, there
are defaults as you have discovered.
Didn't even need to DUMP it. VMSINSTAL didn't complain.
Don't feel bad, I've been dealing with this for 20 years when trying to get
VMS crash dump files from customers sent to me in tact via the internet. ;)
I'm impressed I figured out that LRL was the value I wanted. ;)
Luck. ;)
Yup. ;)
Next battle: anything graphical logs this:
%%%%%%%%%%% OPCOM 10-JUN-2014 19:25:19.33 %%%%%%%%%%%
Message from user AUDIT$SERVER on MOIRA
Security alarm (SECURITY) and security audit (SECURITY) on MOIRA, system id: 9217
Auditable event: Detached process login failure
Event time: 10-JUN-2014 19:25:19.32
PID: 20200149
Process name: _WSA3:
Username: SYSTEM
Process owner: [SYSTEM]
Image name: MOIRA$DKA0:[SYS0.SYSCOMMON.][SYSEXE]LOGINOUT.EXE
Status: %DECW-F-NOMSG, Message number 02DB8204
Which makes no sense.
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects