HDTenEightyP/NetNews huggingface dataset:
From: paulonis@kodak.com (Mike Paulonis)
Newsgroups: comp.os.vms
Subject: Changing default fonts in DECterm?
Date: 14 Apr 92 16:38:21 GMT
Organization: Eastman Chemical Co., Kingsport, TN

I just switched from a VAXstation 3100/76 to a 4000/60.  The 4000 has a 100 dpi
graphics interface and monitor.  The 3100 had 75 dpi.  The problem is that the
default DECterm fonts are too big on the 4000.  It seems like they could be
changed by putting something into the DECW$TERMINAL.DAT file, but I don't know
exactly what that would be.  I tried something like

DECW$TERMINAL.main.terminal.fontUsed: -Misc-Fixed-Medium-R-Normal--15 ...etc

but to no avail.  I haven't been able to find any clues in the VMS or MOTIF
manuals that I have.

Can anyone provide the proper way to change the fonts?  I would also be
interested in a reference to information about what can be specified in
DECW$*.DAT files in regards to DECterm.
From: weikl@ILT.FHG.DE (weikl@ilt.fhg.de)
Newsgroups: comp.os.vms
Subject: Re: 3rd party DSSI drives, are they any good?
Date: 16 Apr 92 12:29:03 GMT
Distribution: world
Organization: The Internet

In article <1190.29e9bd16@mbcl.rutgers.edu>, imran@mbcl.rutgers.edu writes:
|>
|>Hi,
|>
|>I'm considering purchasing 3rd party (Enterprise Digital) DSSI (RF72, RF73) 
|>compatible drives.  The prices I've seen are unbeatable.  They leave DEC in 
|>the dust, as usual :-)  However, I'm worried about performance and 
|>reliability.  Is there any experience out there with these or other 3rd party
|>drives?  Any war or horror stories?
|>
|>If you post replies to me I'll summarize to the net.
|>
|>Thanks in Advance,
|>
|>Shahid.
|>
|>------------------------------------------------------------------------------
|>Shahid N. Imran, Systems Programmer      || Phone:    (908) 932-4864
|>Molecular Biology Computing Laboratory   ||
|>Waksman Institute/CABM                   || BITNET:   imran@mbcl
|>P.O. Box 759, Rutgers University         || Internet: imran@mbcl.rutgers.edu
|>Piscataway, NJ 08855-0759 * USA          ||
|>------------------------------------------------------------------------------
|>
We have some experience with Emulex DSSI-Drives DM4160. We ordered 13, 4 didn't 
work. (We are still waiting for one - since last December.) Even worse: This 
disks didn't work as system disk on a boot node. After clusterconfig a booting 
satellite created the following error message:
%NONAME-E-SYSERROR, system service error
-SYSTEM-F-NOSUCHNODE, remote node is unknown
This could be traced down to an identification problem with the disk.

$ show dev /fu $3$dia4
...
Disk $3$DIA4:, device type RF71, is online, member of shadow set DSA4:, served
    to cluster via MSCP Server, error logging is enabled.

    Error count                    0    Shadow member operation count      5478
    Host name               "DSSI04"    Host type, avail     !!!!->   MD30, yes
    Alternate host name     "EE4BS2"    Alt. type, avail      VAX 4000-300, yes
    Allocation class               3

The disk identifies as MD30 which should read RF71.

You will have this problem, when yoou have the ROM-Version G229B, it is fixed with G229D.

Bruno
=====================================================
# Dr. Bruno Weikl                                   #
# Lehrstuhl f|r Lasertechnik, RWTH Aachen           #
# Fraunhofer-Gesellschaft Institut f|r Lasertechnik #
# Steinbachstr. 15, D-5100 Aachen, Germany          #
# InterNet     : weikl@ilt.fhg.de                   #
# Bitnet       : weikl@dacth51                      #
# x400         : C=DE;A=DBP;P=FHG;O=ILT;S=weikl     #
# P.S.I.       : PSI%45050212501::weikl             #
# HEPNET       : 13533::52714::weikl                #
# Phone        : +49/241/8906-134, -0,              #
# Fax          : +49/241/8906-121                   #
# Telex        : 832267 fhilt d                     #
====================================================#
From: ABPATEL@SCUACC.SCU.EDU (Mickey Patel)
Newsgroups: comp.os.vms
Subject: Re: New Zip and UnZip for VMS soon....
Date: 15 Apr 92 12:05:00 GMT
Distribution: world
Organization: The Internet


	Can anyone tell  me as to when is the New ZIP and UNZIP is to be
released? I heard that it was supposed to be released in Mid_April.
If someone has already got it could you let me know as to how?
Thanks!
Mike
From: DWING@UH01.Colorado.EDU (Dan Wing)
Newsgroups: comp.os.vms
Subject: Re: Total number of files on a volume
Date: 16 Apr 92 14:48:30 GMT
Organization: The Internet

>What is the maximum number of files on a volume?  I had a problem creating any
>more files on a disk.

Nick De Smith has an excellent article about this very problem in the most 
recent issue of VAX Professional.  You probably ran out of available file 
headers in INDEXF.SYS.  Quick fix is to delete files to free up headers, 
long term fix is to defragment your disk (using BACKUP/IMAGE), and the best
fix is described in Nick's article.

>Also is there anyway to change the number of legal subdirectories (I can only
>access 8)?  Can you go deeper?

No.  The 'workaround' is to create a rooted logical, like:

   $ DEFINE ROOTED_LOGICAL $n$DUAn:[DIR1.DIR2.DIR3.DIR4.] -
       /TRANSLATION=CONCEALED

Then reference the rooted logical, like:

   $ CREATE/DIRECTORY ROOTED_LOGICAL:[DIR5.DIR6.DIR7.DIR8.DIR9.DIR10.DIR11]

BACKUP can get upset about this, by the way, as it can't traverse deep
directories without /IMAGE or /PHYSICAL (i.e. /SINCE backups may not work).

-Dan Wing, DWING@UH01.Colorado.EDU  (or WING_D@UCOLMCC.BITNET)
 Systems Programmer, University Hospital, Denver
Organisation: European Space Technology Centre (E.S.T.E.C)
Date: Wednesday, 15 Apr 1992 11:26:30 CET
From: Hugh D.R. Evans <HEVANS@ESTEC.BITNET>
Newsgroups: comp.os.vms
Subject:    file compression utility


Can anyone out there provide me with a file compression utility
similar to PKZIP/ZOO...?

Many thanks.

Hugh Evans

Internet: hevans@estec.esa.nl      hevans@29.623.decnet.cern.ch
Bitnet:   hevans@ESTEC             SPAN:     ESTCS1::HEvans
From: DWING@UH01.Colorado.EDU (Dan Wing)
Newsgroups: comp.os.vms
Subject: Diskeeper V5.0 - Control Master file corruption
Date: 9 Apr 92 16:29:50 GMT
Article-I.D.: VAXF.01GIMZWJZMDE00005N
Organization: The Internet

I'm running Diskeeper V5.0, and have had on and off problems with Control 
Master  messing up its control files:

  SYS$SYSDEVICE:[SPICM]CONTROL_MASTER_JOBS_QUEUE.UH01
  SYS$SYSDEVICE:[SPICM]CONTROL_MASTER_NODE_LISTS.UH01

This problem does *NOT* indicate a data integrity problem with Diskeeper's
file movement, but rather with how Control Master (the new Diskeeper V5.0
process controlling scheduling and other parameters) manipulates these files.

Control Master, on occasion, refuses to startup (after a system reboot or 
other Diskeeper shutdown) until these files are deleted.  Of course, you must 
then re-enter all the parameters, sheduling, device lists, etc.  (the files
are re-created during Control-Master startup if they don't exist).

Has anyone experienced problems similar to this?

-Dan Wing, DWING@UH01.Colorado.EDU  (or WING_D@UCOLMCC.BITNET)
 Systems Programmer, University Hospital, Denver
From: marten@ilt.fhg.de (Lutz Marten)
Newsgroups: comp.os.vms
Subject: Document interchange MAC - VAX (DECwrite)
Date: 10 Apr 92 07:36:58 GMT
Distribution: world
Organization: The Internet

Hi, who knows how we can interchange Documents between MACintosh MS WORD and VAX/VMS 
DECwrite. The connection is not the problem, PathWorks or IBM floppies, but which format? 
MS Word for MAC's seems not to support DCA.

# Lutz Marten Postmaster and general dogsbody        #
# Fraunhofer-Gesellschaft Institut fuer Lasertechnik #
# BITNET       : MARTEN@DACTH51, KQ040MA@DACTH11     #
# InterNet     : marten@ilt.fhg.de                   #
# HEPNET       : 13533::52714::MARTEN                #
# Phone        : +49/241/8906-112, -0, office        #
From: imhw400@indyvax.iupui.edu
Newsgroups: comp.os.vms
Subject: Re: Problem with sub-proc writing to SYS$OUTPUT
Date: 14 Apr 92 10:17:59 -0500

A1 probably pulls the same trick that WPS-Plus does:  when you "spawn" out, the
subprocess' SYS$INPUT is piped (well, mailboxed :-) through WPS, which handles
every character looking for a blank line.  The blank line means, nuke the
subprocess and go back to doing WPS things.  I think it is a bit sleazy, but it
is probably there for compatibility with WS78 WPS or some such.

Anyway, the point is that spawning out of WPS (and presumably A1) does not give
you the same process-permanent file environment as spawning out of anything
else, so this may be why the behavior is different.  Explicitly opening TT: and
WRITEing it sounds like your only hope.
-- 
Mark H. Wood, Lead Analyst/Programmer    +1 317 274 0749   [@disclaimer@]
Internet:  IMHW400@INDYVAX.IUPUI.EDU     BITNET:  IMHW400@INDYVAX
Celebrate freedom:  read a banned newsgroup.
From: Chris_F_Chiesa@cup.portal.com
Newsgroups: comp.os.vms
Subject: XImage display problem
Date: 10 Apr 92 02:47:44 GMT
Organization: The Portal System (TM)

Hello all...

   My company is evaluating a VAXstation 4000 model 60 for possible use
as a color graphics workstation.  One absolute requirement is the ability
to display full-color 24-bit images, in a DECwindows/Motif window if possible
(but on the bare hardware if necessary - ouch!).   

   24-bit hardware has been installed, along with the drivers and supporting
software to let DECwindows talk to it.  The Xlib server-query routines in-
form me that the resulting combination appears to an application as having
a visual class of "TrueColor" and a depth of 24 bitplanes -- as expected.
So far, so good.

   After two days of racking my brains I've managed to write an application
that reads a high-resolution 24-bit image, samples it down to "display 
resolution," places the resulting data in a ZPixmap-type Ximage, and 
XPutImage()-es it to a window.  Alas, after trying every conceivable 
combination of arguments to XCreateImage() and XPutImage(), the best I
have been able to achieve is a horizontally-"sliced-and-shuffled"-looking
attempt at the desired image.  I.e. I can see that the image is THERE,
but the scanlines seem to be interleaved AND the first dozen or so don't
appear AT ALL -- just solid background-pixel where those lines ought to
be.  24-bit COLOR seems to be working -- the sliced images have the right
colors in the right general areas -- but I've been racking my brains and 
can't get the STRUCTURE together.

   It's highly possible that with the right manuals I could work this out,
but we don't have any DECwindows programming documentation (to say nothing
of Motif, another animal about which I/we know even LESS) and no budget
to even consider ordering same.  I don't have C so am writing in Macro
assembly against the "VAX bindings."  Nonetheless, based on a combination
of C source code (from this Net and elsewhere), SYS$SHARE:DECW$*.MAR files,
a terse "Xwindows Programming Reference" book, and notes from Digital's
own DECwindows Programming courses (I and II) which I took in 1990, I've
managed to cobble together a few feeble (but working) DECwindows applica-
tions.  What I LACK is mostly the "big picture," of how it all fits to-
gether.  I've got a book that lists all the routines and their arguments, 
but nothing that says what those routines DO and what the arguments (data
structures and their fields, e.g.) MEAN, and how they all INTERACT.  I've
really shaken the bushes just to get this far.

   I'd appreciate any input from anyone familiar with the behavior of 
XCreateImage() (aka X$CREATE_IMAGE), particularly the "pad" and "quantum"
arguments, and with XPutImage(), and with DECwindows/Motif behavior 
with a "TrueColor" visual class.  Post and/or mail, I read this group 
religiously!

  Thanks very much in advance,

    Chris Chiesa
      Chris_F_Chiesa@cup.portal.com
Newsgroups: comp.os.vms
From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick)
Subject: Re: SUMMARY: How to SET FORWARD to multiple users
Reply-To: carl@SOL1.GPS.CALTECH.EDU
Organization: HST Wide Field/Planetary Camera
Date: Tue, 14 Apr 1992 23:02:39 GMT

In article <KENW.92Apr13161603@skyler.arc.ab.ca>, kenw@skyler.arc.ab.ca (Ken Wallewein) writes:
>
>  It boils down to this: DEC removed that capability from VMS Mail in V5.0,
>apparently because they were worried about mail loops.  I thought it was a
>bad decision then, and I still do.

No, not because of mail loops.  Because the MAIL-11 protocol allows you only to
figure out whether the message was or was not delivered successfully by the
remote node.  In particular, if there's a remote mailing list, and the remote
machine can't deliver to mail to one of the addressees, you have no way of
telling to which addressees the mail was delivered and to which it wasn't.
--------------------------------------------------------------------------------
Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL

Disclaimer:  Hey, I understand VAXes and VMS.  That's what I get paid for.  My
understanding of astronomy is purely at the amateur level (or below).  So
unless what I'm saying is directly related to VAX/VMS, don't hold me or my
organization responsible for it.  If it IS related to VAX/VMS, you can try to
hold me responsible for it, but my organization had nothing to do with it.
From: zampetti@eniac.seas.upenn.edu (Mr. M.)
Newsgroups: comp.os.vms
Subject: VAX C SYS$MOUNT Question
Date: 7 Apr 92 17:04:25 GMT
Organization: University of Pennsylvania


Xref: sparky comp.os.vms:8161 vmsnet.networks.tcp-ip.multinet:1227 vmsnet.networks.tcp-ip.wintcp:101
From: joel@eco.twg.com (Joel Stevick)
Newsgroups: comp.os.vms,vmsnet.networks.tcp-ip,vmsnet.networks.tcp-ip.multinet,vmsnet.networks.tcp-ip.wintcp
Subject: Re: TGV MultiNet vs. WIN/TCP NFS Client
Keywords: WIN/TCP, TGV, NFS Client, VMS
Date: 8 Apr 92 18:56:13 GMT
Reply-To: joel@eco.twg.com (Joel Stevick)
Organization: The Wollongong Group (East Coast Operations)


David:

	You mentioned in your recent response to Reece Pollack's
	article (concerning the differences between our NFS client
	implementations) that you have integrated calls to the
	the NFS Lock Manager.

	This is an important issue that I feel warrants a seperate
	series of postings.

	In your response to Reece Pollack's article concerning the
	overall difference between our NFS Client implementations
	you write:

>
>TGV NFS Client also uses the NFS Lock Manager to allow for file locking
>in an NFS environment.  The ability to open a file and restrict access to
>others while the file is being manipulated is an important VMS feature that
>also maps into the NFS world.  It is amusing to have one VAX do the following:
>	$ OPEN/WRITE FOO "FOO.DAT"
>On an NFS volume and have another VAX 3,000 miles away do the following:
>	$ DELETE FOO.DAT;
>And have the 2nd VAX get a "file locked by another user" message.
>

I agree that this is amusing.  I am assuming that what you have done is to 
emulate the Access Arbitration Lock using the services of the NFS lock manager.
I would like to point out that this is NOT "RMS record locking."  It is 
important to make this distinction since customers may otherwise (incorrectly) 
trust that distributed applications which depend on this feature will be 
synchronized.

The PRIMARY need for file synchronization in a distributed VMS environment 
happens when two applications access files opened for shared-write access, 
and perform record-level locking (via RMS).  In this case, the file lock would 
not provide any relevant synchronization.

If you have found a way to integrate the NFS lock manager with RMS record
level locking, I salute you.

- Joel 
Xref: sparky comp.os.vms:8242 comp.sys.dec:2537
From: vossj@topaz.ucq.edu.au
Newsgroups: comp.os.vms,comp.sys.dec
Subject: Problems with REGIS graphics under DECterm
Date: 13 Apr 92 10:31:12 AET
Organization: University of Central Queensland, Australia

We have an application that has been running on old GIGI terminals using 
REGIS graphics. This application draws a graph on the top 18 lines of the
screen and asks tutorial type questions about the graph in the bottom 6 lines
on the screen. Now recently I've been trying to get this application to work
using a DECterm window(which is set to VT300 mode) on PC's running DECwindows
but I've ran into a couple of differences.

(1) There seems to be difference in colours.
        green (Gigi) appears as magenta (DECterm)
        yellow (Gigi) appears as white (DECterm)

(2) When running the application in a DECterm window, it occassionaly rolls the
    graph up the screen about 2 lines. This consistently happens at the same
    places.

Is anyone aware of any differences with REGIS graphics on a GIGI and a DEC's
DECterm or how to fix the above problems? My last resort will be to carefully
examine the escape sequences that are sent by the application. 

Thanks,

John 
-- 

--------------------------------------------------------------------------------
U U  CC  QQ  John D. Voss                Internet: J.Voss@ucq.edu.au    _--_|\
U U C   Q  Q Computing Services             Phone: (+)61 79 309804    -/------*-
U U C   Q  Q University of Central Queensland Fax: (+)61 79 361361     \_.--._/
UUU  CC  QQ\ Rockhampton,  Queensland  4702   AUSTRALIA                      v
--------------------------------------------------------------------------------
Newsgroups: comp.os.misc
From: woodman@bnr.ca (Dave Woodman)
Subject: Re: QL serial lines (was Re: Microdrive problems...)
Keywords: QL QDos
Organization: BNR Europe Ltd, Maidenhead
Date: Thu, 09 Apr 1992 16:44:08 GMT

In article <1992Apr9.132304.16484@klaava.Helsinki.FI> torvalds@klaava.Helsinki.FI (Linus Benedict Torvalds) writes:
>
>              ...  There was no unix available for the QL when I last
>looked, and although QDOS does multitask, unix is still nicer.  (and no,
>I didn't feel like writing my own unix for the QL - it was hard enough
>for a 386, which supports it better :^)
>

  Well (and Linus, you might not want to hear this, given your recent 
efforts), there is Minix available for QDOS...

  Most of your other problems have since been fixed, including the problem
with lack of power, and further developments are close. The only thing
left is the problem of the RS232 interface giving problems. For a clue to
this, watch the handshake used on receive:- this is not held steady, even
on an idle line.
        
               Cheers,

			Dave.      


-- 
==============================================================================
=  My e-mail address might be woodman@bnr.ca, but Maidenhead is definitely   =
=  in Britain... My employer is entitled to disagree with anything but this! =
==============================================================================
From: ryan@phi.cs.fsu.edu (John Ryan)
Newsgroups: comp.os.misc
Subject: Need Amoeba OS info
Date: 7 Apr 92 22:30:11 GMT
Reply-To: ryan@nu.cs.fsu.edu
Organization: Florida State University Computer Science Department



Does anyone know where I can get information on the Amoeba
Operating System??


ryan@nu.cs.fsu.edu
From: hansi@abalon.se (Hansi Tesarz)
Newsgroups: comp.os.misc
Subject: Whitechapel MG1
Date: 7 Apr 92 09:35:12 GMT
Organization: Abalon AB, Stockholm, Sweden


Hi 

Anyone out there running a MG1 unix machine from Whitechapel?


What is the status of MG1?


Is it posible to get an update for the OS? The OS i use is 42UNIX

Is there a port for GCC on the MG1
Is there a port for X11 on the MG1


 - Hansi


Hansi Tesarz	Phone work: +46-8-802320
hansi@abalon.se Fax work: +46-8-806580
Abalon AB, Box 11129, 161 11 Bromma, SWEDEN.
From: ryan@phi.cs.fsu.edu (John Ryan)
Newsgroups: comp.os.misc
Subject: Need Amoeba OS info
Date: 7 Apr 92 22:32:35 GMT
Reply-To: ryan@nu.cs.fsu.edu
Organization: Florida State University Computer Science Department



Does anyone know where I can get information on the Amoeba
Operating System??


ryan@nu.cs.fsu.edu
From: torvalds@klaava.Helsinki.FI (Linus Benedict Torvalds)
Newsgroups: comp.os.misc
Subject: Minix for the QL (was Re: QL serial lines)
Keywords: QL QDos
Date: 10 Apr 92 22:49:26 GMT
Organization: University of Helsinki

In article <1992Apr09.164408.24670@bnr.uk> woodman@bnr.ca (Dave Woodman) writes:
>
>  Well (and Linus, you might not want to hear this, given your recent 
>efforts), there is Minix available for QDOS...

Oh yes, I'm definitely interested - especially if it is available as
patches against PC-minix (but I assume they started off with a 68k
port?).  Can somebody tell me how they did it? (and who are "they"
anyway?) I know writing a floppy-driver wouldn't be much fun: with no
DMA I had to really optimize things in order to read the programmed IO
for my own driver, and I think I never got it to work from basic ram
(had to use eproms or expansion-ram - the inner loops that read the IO
addresses were really tight: I was unable to use a cmp, had to use a
subq, I think, to save a couple of cycles.  Something like that... 
Debugging was hell :^). 

Or does it all work on top of QDos? Much easier, but not as much fun. 
But it /would/ be fun to refer to the microdrives as /dev/rmt0 :)

Does QL-minix use the QDOS for multitasking too? Or does it use it's own
scheduler within one QL task or what? Running atop QDOS should mean you
can run minix while at the same time using SB and any other QL tasks -
true or false?

>  Most of your other problems have since been fixed, including the problem
>with lack of power, and further developments are close.

Well, there were newer versions of the QL coming out even while I was
still active, so I'm not too surprised - with a reasonably fast 68020 or
better and a better memory subsystem it might be a real pleasure to use. 
I always liked QDos - one of my few gripes with it was the inability to
use the second screen without disabling most of the system software (and
being unable to map all the interrupts - I'd have liked to use the a-
and f-line exceptions and some other things...)

>							  The only thing
>left is the problem of the RS232 interface giving problems. For a clue to
>this, watch the handshake used on receive:- this is not held steady, even
>on an idle line.

If this was in the original specs, it might explain my problems: I never
had access to an oscilloscope to test it all out.  It's a bit ironic
that this would still be a problem - serial lines aren't exactly hard to
handle, and it's a pity the QL didn't use more standard parts for them. 
Some of the hardware solutions in the QL were definitely "interesting" -
I assume it was cheaper that way originally, but it did hurt the
reputation of the machine.

I fixed some of my problems with a better power-supply and regulator
(home-brew, but they seemed to work), as well as additional heat-
dissipation.  A pity really: I shouldn't have needed to, and I had a
number of weird crashes before I got it all together.

		Linus
Organization: Ministry of Education, Computer Center NETNEWS system V2.3
Date: Tuesday, 7 Apr 1992 22:05:24 EST
From: Wu the Supreme <NCKUS178@twnmoe10.edu.tw>
Newsgroups: comp.os.misc
Subject: some problems about ptrace()

I'm just a novice of newsgroups and maybe I don't post my question to
the correct newsgroup, and I don't know too much about the etiquette
of this group. If there are anything improper in this letter, please
tell me anyway, thanks!

Here I faced a lot problems when programming with ptrace() system call. Now
I have only two references: SUN reference manual and a book "The Design
of the UNIX operating systems", wrote by Maurice J. Bach. If anyone who
know the detailed technical data or books discussing ptrace(), Could you
tell me? I'll be very happy because I've "try and error"using ptrace() for
a period of times.....

                                                      Jyh-Shi Wu
                                                         Apr. 7
Xref: sparky comp.os.misc:506 comp.sys.dec:2596 comp.sys.hp:5287 comp.unix.admin:2818 comp.unix.msdos:635 comp.unix.questions:6252 comp.unix.sysv386:8722 comp.unix.xenix.sco:1918 comp.windows.misc:782 comp.windows.x:10098