| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1508.1 | More info... | JGL::JLENIHAN | Byte Twiddler | Mon Oct 02 1989 08:40 | 21 |
| 1508.2 | | SITBUL::KLEINSORGE | So sue me. | Mon Oct 02 1989 14:04 | 19 |
|
Hmmm. Check for the existance and the correct protection (W:RE) for
the file:
SYS$SHARE:DECW$SERVER_DDX_GV.EXE
The next lines in the error log should have been:
VWS/DECwindows
VWS: VMFB loaded
These lines are output as the first thing that the GV server does. It
makes me think that the DIX layer was unable to find the image - or
that the image was incompatable (are you *sure* that you don't have the
V2.0 server? and are you sure you installed the vwsdec010.a, .b, .c
from VWSENG:: and not the old one from BULOVA?)
_Fred
|
| 1508.3 | Protection OK... | JGL::JLENIHAN | Byte Twiddler | Mon Oct 02 1989 14:51 | 17 |
| 1508.4 | Same | CRACKR::SYSTEM | | Mon Oct 02 1989 17:34 | 6 |
| Same as .3
Same protection.
Same Server kit location.
I installed DECWINDOWS with VMS052 from MPGS::SYS$KITS:[VMS052].
|
| 1508.5 | | SITBUL::KLEINSORGE | So sue me. | Mon Oct 02 1989 19:02 | 12 |
|
Do an anal/image on the DECW$SERVER_MAIN.EXE in SYS$SYSTEM: and on
DECW$SERVER_DIX.EXE in SYS$SHARE: and tell me what the image IDs are.
Also, if you have a MODPARAMS.DAT, rename it to FOO.DAT and re-do the
AUTOGEN.
You also should see a GVA0: loaded when you show devices.
|
| 1508.6 | Data..Data! | JGL::JLENIHAN | Byte Twiddler | Tue Oct 03 1989 06:36 | 39 |
| 1508.7 | Still no cigar! | JGL::JLENIHAN | Byte Twiddler | Tue Oct 03 1989 07:33 | 10 |
| 1508.8 | more info | JUPITR::RITZ | | Tue Oct 03 1989 13:10 | 165 |
| ================================================================================
SYS$SYSTEM:DECW$SERVER_MAIN.EXE
Image Identification Information
image name: "DECW$SERVER_MAIN"
image file identification: "DECWINDOWS V5.2"
link date/time: 23-APR-1989 16:40:16.60
linker identification: "05-05"
SYS$SHARE:DECW$SERVER_DIX.EXE
Image Identification Information
image name: "DECW$SERVER_DIX"
image file identification: "DECWINDOWS V5.2"
link date/time: 23-APR-1989 16:35:49.12
linker identification: "05-05"
================================================================================
Device GVA0: is online, record-oriented device, carriage control, shareable.
Error count 0 Operations completed 0
Owner process "" Owner UIC [SYSTEM]
Owner process ID 00000000 Dev Prot S:RWLP,O:RWLP,G:RWLP,W:RWLP
Reference count 0 Default buffer size 80
GVA0: Online 0
GVA1: Online 0
GVA2: Online 0
================================================================================
$ sh proc/all/id=174
3-OCT-1989 10:27:53.54 User: SYSTEM Process ID: 00000174
Process name: "DECW$SERVER_0"
Terminal:
User Identifier: [SYSTEM]
Base priority: 6
Default file spec: Not available
Devices allocated: NET3357:
Process Quotas:
Account name: SYSTEM
CPU limit: Infinite Direct I/O limit: 100
Buffered I/O byte count quota: 47200 Buffered I/O limit: 60
Timer queue entry quota: 7 Open file quota: 87
Paging file quota: 22483 Subprocess quota: 8
Default page fault cluster: 16 AST quota: 595
Enqueue quota: 30 Shared file limit: 0
Max detached processes: 0 Max active jobs: 0
Accounting information:
Buffered I/O count: 280 Peak working set size: 789
Direct I/O count: 279 Peak virtual size: 4240
Page faults: 480 Mounted volumes: 0
Images activated: 0
Elapsed CPU time: 0 00:00:11.23
Connect time: 0 00:00:32.21
Process privileges:
CMKRNL may change mode to kernel
SYSNAM may insert in system logical name table
PRMMBX may create permanent mailbox
WORLD may affect other processes in the world
NETMBX may create network device
PRMGBL may create permanent global sections
SYSGBL may create system wide global sections
PFNMAP may map to specific physical pages
SYSPRV may access objects via system protection
There is 1 process in this job:
DECW$SERVER_0 (*)
================================================================================
$ sh proc/all/id=139
3-OCT-1989 10:23:51.32 User: SYSTEM Process ID: 00000139
Process name: "_WSA2:"
Terminal:
User Identifier: [SYSTEM]
Base priority: 4
Default file spec: Not available
Process Quotas:
Account name: <start>
CPU limit: Infinite Direct I/O limit: 100
Buffered I/O byte count quota: 32448 Buffered I/O limit: 40
Timer queue entry quota: 8 Open file quota: 11
Paging file quota: 5387 Subprocess quota: 8
Default page fault cluster: 16 AST quota: 599
Enqueue quota: 30 Shared file limit: 0
Max detached processes: 0 Max active jobs: 0
Accounting information:
Buffered I/O count: 23 Peak working set size: 500
Direct I/O count: 21 Peak virtual size: 5814
Page faults: 675 Mounted volumes: 0
Images activated: 0
Elapsed CPU time: 0 00:00:02.85
Connect time: 0 00:00:16.90
Process privileges:
SETPRV may set any privilege bit
TMPMBX may create temporary mailbox
NETMBX may create network device
There is 1 process in this job:
_WSA2: (*)
================================================================================
$ sh proc/all/id=177
3-OCT-1989 10:25:10.22 User: SYSTEM Process ID: 00000177
Process name: ""
Terminal:
User Identifier: [SYSTEM]
Base priority: 4
Default file spec: Not available
Process Quotas:
Account name: <start>
CPU limit: Infinite Direct I/O limit: 100
Buffered I/O byte count quota: 32448 Buffered I/O limit: 40
Timer queue entry quota: 8 Open file quota: 11
Paging file quota: 5387 Subprocess quota: 8
Default page fault cluster: 16 AST quota: 599
Enqueue quota: 30 Shared file limit: 0
Max detached processes: 0 Max active jobs: 0
Accounting information:
Buffered I/O count: 23 Peak working set size: 500
Direct I/O count: 12 Peak virtual size: 5814
Page faults: 692 Mounted volumes: 0
Images activated: 0
Elapsed CPU time: 0 00:00:02.78
Connect time: 0 00:00:07.32
Process privileges:
SETPRV may set any privilege bit
TMPMBX may create temporary mailbox
NETMBX may create network device
There is 1 process in this job:
(PID 00000177) (*)
================================================================================
I tried
Autogen
Reinstalling VWSDECW
|
| 1508.9 | Any resolution? | PEACHS::BELDIN | | Fri Nov 10 1989 11:50 | 7 |
|
Has there been any resolution to this problem? We have
a mixed cluster running 5.2 and 5.1 and vws 4.2. All of
the systems running 5.2 can't run VD, while the 5.1 systems
(which may be running 4.1, I don't know) can...
Rick
|
| 1508.10 | AND HERE IT IS! | FK::FRED | So sue me. | Tue Nov 14 1989 02:18 | 23 |
| ** YES ** YES ** YES ** YES ** YES ** YES ** YES ** YES ** YES ** YES **
Well, during a one-week period where my mind was forced into idle and
my feet used instead (i.e. DECUS :-) I had the chance to install the
V4.2/V5.2 stuff.
The server is getting a ACCVIO from UIS. Don't ask me what the hell
it's doing, but I tracked it down that far without the VWS symbol
tables handy.
And now, what you've been waiting for: The WORKAROUND...
The kit consists of three savesets: VWSDECW010.A, .B, .C
on VMS V5.2 systems obtain the second saveset (.B) and do the
following:
$ backup vwsdecw010.B/save/sel=([*...]decw$server_ddx_gv.exe) []/lo
$ copy decw$server_ddx_gv.exe sys$share:/prot=w:re/lo
This will install the V5.1 image - which *will* work. I will track
down the actual problem in my spare (gag) time.
** YES ** YES ** YES ** YES ** YES ** YES ** YES ** YES ** YES ** YES **
|
| 1508.11 | Time stands still for no man...VMS 5.3? | JGL::JLENIHAN | Byte Twiddler | Tue Nov 14 1989 07:41 | 11 |
| 1508.12 | | LESLIE::LESLIE | | Tue Nov 14 1989 09:47 | 5 |
| 1508.13 | | FK::FRED | So sue me. | Tue Nov 14 1989 13:16 | 8 |
|
This has been answered before. No V2 support yet. I have to get the
V2 server result and make whatever changes that may be required.
This *should* happen sometime between now and December.
_Fred
|