INFO-VAX Fri, 07 Jan 2005 Volume 2005 : Issue 14 Contents: Re: 'Security log is full' Basic virtual memory question Re: DCPS and Kyocera FS-6020 printer DECterminal: scroll bar width ? Re: DECterminal: scroll bar width ? Re: Help - SYSUAF and $SETUAI on UAI$_USER_DATA field Re: Help - SYSUAF and $SETUAI on UAI$_USER_DATA field Re: HPLJ tray selection problem from OVMS V7.3-1 Re: HPLJ tray selection problem from OVMS V7.3-1 Re: Mark Gorham interview in Interex's HP World Magazine Re: Mark Gorham interview in Interex's HP World Magazine New Mozilla security issues/vulnerabilities Samsung! Re: Simple EDT or TPU init file Re: Simple EDT or TPU init file Re: Simple EDT or TPU init file Re: Simple EDT or TPU init file Re: Simple EDT or TPU init file Re: Simple EDT or TPU init file Re: VAXstation 3100: supported under VMS 7.3? Re: VMS ready laser printer? ---------------------------------------------------------------------- Date: Fri, 7 Jan 2005 13:09:21 -0500 From: "PEN" Subject: Re: 'Security log is full' Message-ID: Hi Michael, "Michael Clark" wrote in message news:A2A28DB6D52E084783ACD6E6C6F5D7900274F9BC@EMAILSERVER2.nemschoff.com... >I keep getting a netsend message to the administrator account on my domain > from our OpenVMS machine saying "The Security log is full". > I have gone into pathworks are cleared the log histoy, that doesnt seem to > make a difference. Any ideas what I should be looking at? > This is quite annoying. Which log did you clear? The security log can be cleared by doing: $ admin clear event/type=security HTH, Paul ------------------------------ Date: Fri, 07 Jan 2005 13:41:12 -0500 From: JF Mezei Subject: Basic virtual memory question Message-ID: <1105122665.245feb03fda7a96ead9c9055ba54b402@teranews> OK, I browsed through the VAX/VMS internals book. But I couldn't find an easy answer to an age long question I have had about VMS. On a conventional MAC, one had a very simple memory management config: You told the MAC how much virtual memory it should have, and it would create a page file that big. Then, with each imager file (application), you configured how much virtual memory it was allowed to take. On VMS, the way I understand it, a process can allocate memory until it has used up all its pagefile quota and its working can't be grown anymore. Is that correct ? Lets take the example of a *theoretical* all mighty Microvax II with a whopping 16 megabytes of physical RAM, but with a 100 megabytes page file. At the VMS level, are there SYSGEN parameters to tell the OS that it has over 100 megs of virtual address space ? (100 megs page file + however physical memory can be used as VIRTUALPAGES). Or does VMS create a virtual memory page table for each process based on how much pagfilquo and wsextent the process can potentially have ? From what I can gather, the SYSGEN parameters seem to split physical memory between non pageable memory and pageable memory (NPAGEDYN and VIRTUALPAGES), with soem other parameters probably taking up some physical memory apart from NPAGEDYN and VIRTUALPAGES (such as SPTREQ I think). Is there a simple list of SYSGEN parameters that, when added up, equal to the physical memory on that machine ? ------------------------------ Date: Fri, 07 Jan 2005 15:59:37 GMT From: Paul Anderson Subject: Re: DCPS and Kyocera FS-6020 printer Message-ID: <070120051045004645%paul.anderson@hp.com> In article , Fred Zwarts wrote: > If I specify the product name as anything the symbiont complains when > the first print job is started that it does not recognize the product > name and it assumes Unrecognized, but it prints correctly. This > contradicts the documentation, which says that for unsupported > printers the definition of the product name logical is not needed. I've duplicated this here and it sure looks like a bug. It is not our intention to require a product name logical name for all LPD queues. Paul -- Paul Anderson OpenVMS Engineering Hewlett-Packard Company ------------------------------ Date: Fri, 07 Jan 2005 02:24:05 -0500 From: JF Mezei Subject: DECterminal: scroll bar width ? Message-ID: <1105081997.f6849de65446fb7e81069abf979ef07c@teranews> Does anyone know if one can specify some resource to make the vertical scroll bar in DECterminal (DECW$TERMINAL) more narrow ? I tried *XmScrollBar*width: 18 but that didn't seem to make a difference (I just edited the resource file and from an existing decw$terminal, used the "restore named optiosn" to get it to reload the optiosn file). Turned scrolled bar off and back on again, but no changes were seen. ------------------------------ Date: 7 Jan 2005 01:41:41 -0800 From: martinkirby12@yahoo.co.uk Subject: Re: DECterminal: scroll bar width ? Message-ID: <1105090901.544224.59250@z14g2000cwz.googlegroups.com> JF Mezei wrote: > Does anyone know if one can specify some resource to make the vertical scroll > bar in DECterminal (DECW$TERMINAL) more narrow ? > > I tried *XmScrollBar*width: 18 but that didn't seem to make a difference > > (I just edited the resource file and from an existing decw$terminal, used the > "restore named optiosn" to get it to reload the optiosn file). Turned scrolled > bar off and back on again, but no changes were seen. I looked at the code. It appears the width is hard-coded. However, as far as I can tell it is set to 17 any way! Martin ------------------------------ Date: 7 Jan 2005 07:46:23 GMT From: "Dave Weatherall" Subject: Re: Help - SYSUAF and $SETUAI on UAI$_USER_DATA field Message-ID: On Thu, 6 Jan 2005 13:56:05 UTC, briggs@encompasserve.org wrote: > > o If the file name has the syntax: name (devoid of ':', '.', ';', etc) > > e.g. SYSUAF > > Logical name resolution is attempted on the name (SYSUAF) > > o Otherwise (name has multiple components, but no leading device or nodename) > > e.g. SYSUAF.DAT > > Logical name resolution is not attempted > Spot on John. Brain-fade on my behalf had inverted my memory. I really must set up a hobbyist system at home so I can check before I type. -- Cheers - Dave W. ------------------------------ Date: 7 Jan 2005 07:53:06 -0600 From: briggs@encompasserve.org Subject: Re: Help - SYSUAF and $SETUAI on UAI$_USER_DATA field Message-ID: In article , Lorin Ricker writes: > Re: opening SYSUAF in Pascal (or Fortran, etc) -- my utility does not open > SYSUAF directly at all -- SETUAI doesn't have a single OPEN statement in it; > open/closing SYSUAF is handled by the $GET/SETUAI interface. My question about > logicals was "Do these RTLs open by logical name, or by using a full > path/filespec?" > > I suspected that they'd honor the "SYSUAF" logical name, and John's advice to > "Define your SYSUAF logical and use AUTHORIZE to see if you can read/write it. > It uses the same interfaces." reminds me that this is true, which is easily > verified. When flailing, I don't always think to clearly! ;-) Testing reveals that AUTHORIZE does NOT use the same interface as $GET/SETUAI. The AUTHORIZE utility respects process and outer mode logical names. The $GET/SETUAI routines respect only trustworthy logical names. That is to say, AUTHORIZE behaves like a Pascal (or Fortran, etc) program opening SYSUAF with a default file specification of SYS$DISK:[].DAT But $GET/SETUAI behaves like SYS$SYSTEM:LOGINOUT.EXE, opening SYSUAF with a default file specification of SYS$SYSTEM:.DAT and specifying the use of trusted logical names. John Briggs ------------------------------ Date: 7 Jan 2005 07:43:36 -0800 From: "denny" Subject: Re: HPLJ tray selection problem from OVMS V7.3-1 Message-ID: <1105112616.440491.27580@f14g2000cwb.googlegroups.com> Hmmmm.....I inadvertently pointed to the solution in the first posting......the dreaded "piece of COBOL". After much hair-pulling, i dumped (/byte/ascii) one of the generated bar code files and found a reset in the first line. The sequence is: Ec%-12345X. This probably defaulted the tray selection to 3. This sequence was embedded in the document, so it arrived after my forms modules, and promptly undid my careful tray selection. We had the application writer take out his reset. Tray selection now works for this "COBOL" application, and my print form, of course, does the reset itself. Denny ------------------------------ Date: 7 Jan 2005 09:55:10 -0800 From: jordan@ccs4vms.com Subject: Re: HPLJ tray selection problem from OVMS V7.3-1 Message-ID: <1105120510.881976.20470@z14g2000cwz.googlegroups.com> That sequence is the 'Universal Exit Language' command; normally it is used to switch into PJL mode so that printer job control language commands can be sent. By itself it is supposed to signal the end of a job. If the printer 'resets' between jobs, then if it interpreted the UEL you were sending as an end of job, that would explain the problem you had, but I don't see the UEL defined as performing a reset on its own. The manual I have is a little confusing, but there should be a 'start' UEL and an 'end' UEL, with PJL encapsulated between them (and the first PJL command should immediately follow the initial UEL, f.e.: %-12345X@PJL COMMENT Change Defaults @PJL DEFAULT PAPER=LETTER %-12345X Rich ------------------------------ Date: Fri, 07 Jan 2005 08:48:11 -0800 From: David Mathog Subject: Re: Mark Gorham interview in Interex's HP World Magazine Message-ID: John Smith wrote: > Barratt, Chris (FMC) wrote: > >>What is the ".NET integration technology" that is being brought to the >>OpenVMS platform ? >> > > Effectively NT Affinity renamed :-( > > Management has to do something to stamp out those four quarters of OpenVMS growth. Regards, David Mathog mathog@caltech.edu ------------------------------ Date: Fri, 7 Jan 2005 11:58:02 -0500 From: "John Smith" Subject: Re: Mark Gorham interview in Interex's HP World Magazine Message-ID: David Mathog wrote: > John Smith wrote: >> Barratt, Chris (FMC) wrote: >> >>> What is the ".NET integration technology" that is being brought to >>> the OpenVMS platform ? >>> >> >> Effectively NT Affinity renamed :-( >> >> > > Management has to do something to stamp out those > four quarters of OpenVMS growth. ROTFLMHO ------------------------------ Date: 7 Jan 2005 10:02:54 -0800 From: jordan@ccs4vms.com Subject: New Mozilla security issues/vulnerabilities Message-ID: <1105120974.201140.31600@f14g2000cwb.googlegroups.com> http://www.securityfocus.com/archive/1/386070/2005-01-04/2005-01-10/0 "A remote attacker could craft a malicious NNTP link and entice a user to click it, potentially resulting in the execution of arbitrary code with the rights of the user running the browser. A local attacker could leverage the temporary file vulnerability to read the contents of another user's attachments or downloads. A remote attacker could also design a malicious web page that would allow to spoof filenames if the user uses the "Open with..." function in Firefox, or retrieve information on the presence of specific files in the local filesystem." ------------------------------ Date: Fri, 7 Jan 2005 12:41:08 +0100 From: "GWDVMS::MOELLER" Subject: Samsung! Message-ID: <6280994@MVB.SAIC.COM> Seen on Korean (english language) TV : In Tuesday's new report, they had a VERY LOW KEY ANNOUNCEMENT of Samsung, the world's leading chipmaker, which mentioned a company named INTEL. [Since I happened to look elsewhere, I did not get the full text.] Do I remember correctly that these folks are free to build Alphas? Busy lately with Korean Wave Fever ... Wolfgang J. Moeller, Tel. +49 551 201-1516/-1510, moeller@gwdvms.dnet.gwdg.de GWDG, D-37077 Goettingen, F.R.Germany | Disclaimer: No claim intended! http://www.gwdg.de/~moeller/ ---- ---- ------------------------------ Date: 7 Jan 2005 04:14:43 -0800 From: "Big John" Subject: Re: Simple EDT or TPU init file Message-ID: <1105100083.002942.32550@f14g2000cwb.googlegroups.com> Over the holiday period, I was thinking about TPU (well, what else is there to do?), and I thought about some possible solutions to your problems.. > First, using SHOW TERMINAL/FULL I find the keypad is usually > in numeric mode by default to start with. It needs to be in > application mode before you call SIMPLE or else the keypad > doesn't work and you can't get out except with a CONTROL-Y. Since we can't 'fix' this (as we don't know how your emulator is working - clearly it's not a perfect emulation of a VT300), there is a nice simple workaround for it. And this is to define any '1' key, the keypad 1, plus any other key that sends '1' to the system, to all do the same thing that kp1 does. Similarly for the other defined kp keys, 2, 4, 6 and 8. Thus we have 2 define_key commands for each command, e.g. define_key ("message(ascii(27)+'[?25h');QUIT (OFF,1)", kp1, the_key_map); define_key ("message(ascii(27)+'[?25h');QUIT (OFF,1)", KEY_NAME ("1"), the_key_map); - so that whatever your keypad 1 key sends, it will be interpreted by the TPU file as you intend. Your other problem sounds trickier to work around.. > Second, if you type enough of the undefined keys, there is a > buffer that gets full somewhere and the terminal beeps and > nothing happens each time you hit another key, even a legit > key. This requires me to clear the communications on my > VT300 X-window on my PC via the Commands pulldown menu, and > that causes the cursor to show up again. Perhaps the > type-ahead buffer needs to be zero?? Something needs to be > done to throw those keys away properly and to make sure they > do not pile up. One idea that occurs to me is to set the undefined-key command to be an ABORT, not a RETURN. If the system is having trouble processing the undefined keys quickly enough, this may help, as it does not waste time trying to recover from an error, it just throws the key away. Here is the helptext from the ABORT command in the TPU manual: --- The ABORT procedure stops any executing procedures and causes DECTPU to wait for the next key press. ABORT returns control to DECTPU's main control loop. It causes an immediate exit from all invoked procedures. --- This should be quicker, and prevent your buffer filling, though it is not guaranteed. See if it works. So attached below is another version of SIMPLE.TPU with these changes. Good luck. - John SIMPLE.TPU follows.. input_file := GET_INFO (COMMAND_LINE, "file_name"); main_buffer:= CREATE_BUFFER ("main", input_file); window_size := GET_INFO(screen,"length"); position (BEGINNING_OF (main_buffer)); main_window := create_window(1,window_size,off); the_key_map := create_key_map ("user_keys"); the_key_map_list := create_key_map_list ("keylist", the_key_map); set (UNDEFINED_KEY, the_key_map_list, "abort"); set (KEY_MAP_LIST, the_key_map_list, main_buffer); set (SELF_INSERT, the_key_map_list, OFF); MAP (main_window,main_buffer); message (ascii(27)+"[?25l"); ! define_key ("message(ascii(27)+'[?25h');QUIT (OFF,1)", kp1, the_key_map); define_key ("message(ascii(27)+'[?25h');QUIT (OFF,1)", KEY_NAME ("1"), the_key_map); define_key ("scroll (current_window, 1)", kp2, the_key_map); define_key ("scroll (current_window, 1)", KEY_NAME ("2"), the_key_map); define_key ("scroll (current_window, -1)", kp8, the_key_map); define_key ("scroll (current_window, -1)", KEY_NAME ("8"), the_key_map); define_key ("scroll (current_window, window_size-1)", kp6, the_key_map); define_key ("scroll (current_window, window_size-1)", KEY_NAME ("6"), the_key_map); define_key ("scroll (current_window, -window_size+1)", kp4, the_key_map); define_key ("scroll (current_window, -window_size+1)", KEY_NAME ("4"), the_key_map); define_key ("scroll (current_window, 1)", down, the_key_map); define_key ("scroll (current_window, -1)", up, the_key_map); ! Fred Bach wrote: > Big John, > > Thank you for your TPU insight. I don't do much TPU. > > I copied your code directly into SIMPLE.TPU in my login > directory. Right now my SIMPLE symbol is: > > SIMPLE == "edit/tpu/read/command=SYS$LOGIN:SIMPLE.TPU/noinit/nosection/nojournal" > > There are a couple of problems. > > First, using SHOW TERMINAL/FULL I find the keypad is usually > in numeric mode by default to start with. It needs to be in > application mode before you call SIMPLE or else the keypad > doesn't work and you can't get out except with a CONTROL-Y. > > Second, if you type enough of the undefined keys, there is a > buffer that gets full somewhere and the terminal beeps and > nothing happens each time you hit another key, even a legit > key. This requires me to clear the communications on my > VT300 X-window on my PC via the Commands pulldown menu, and > that causes the cursor to show up again. Perhaps the > type-ahead buffer needs to be zero?? Something needs to be > done to throw those keys away properly and to make sure they > do not pile up. > > Unlike the original request, it would be nice if SIMPLE could > fill the existing screen whatever length / width it is. We > should pick the screen lengths and widths from the existing DCL > window size before SIMPLE is called. It would still work for > the size of screen originally specified by the original poster. > > Clearly we need to put the necessary DCL setup commands into > a tidy foolproof little .COM file, SIMPLE.COM . What setup > commands do you advise? And if one has to change something > at the DCL level, perhaps one should put it back after SIMPLE > has finished. > > Thanks in advance. > > .. fred bach .. music@triumf.ca > > > Big John wrote: > > > Peter Weaver wrote > > > > > >>Mike Buchanan wrote: > >> > >>>... > >>>1) Can I make the cursor invisible? > >>>... > >> > >>The only way I can think of doing this depends on how good your > > > > terminal > > > >>emulator is; > >> > >>$ esc[0,8]=27 > >>$ write sys$output "''esc'[?25l" > >>$ assign sys$command sys$input/user_mode > >>$ edit/tpu/nosec/comm=sys$login:simple.tpu 'P1 > >>$ write sys$output "''esc'[?25h" > >> > >>-- > > > > > > This is fine, but you can do it very simply, entirely within the TPU > > command. This would make it much easier to set up if you do decide > > to use the callable TPU directly, instead of spawning out. There > > are two ways to do it. The 'proper' way would be to set the window > > not to translate escape sequences, but put them straight out, with a > > command like: > > set (TEXT, main_window, NO_TRANSLATE) > > - then copy_text the escape sequence, and update the window. > > > > However here, there is a simpler solution. Since we are not trapping > > messages, but splashing them unaltered straight on to the screen, we > > can output the escape sequences with a couple of MESSAGE commands. > > > > (There, I believe I said before that it was a much better idea to > > start from scratch and build, instead of stripping down the EVE > > section :-). > > > > So all you need to do, after you have mapped the window to the > > buffer is to add the line.. > > message (ascii(27)+"[?25l"); > > .. and change the kp1 key to execute the 2-command sequence.. > > message(ascii(27)+'[?25h');QUIT (OFF,1) > > .. to switch the cursor back on when exiting. > > > > > > One other point worth mentioning.. > > > > If you don't care about the cursor position, then you can move the > > screen about more simply with the SCROLL command instead of the > > MOVE_VERTICAL command. SCROLL changes the editing point by leaving > > the cursor position unchanged on the screen and adjusting the file > > window display. This is exactly what you want here, and you do not > > need to adjust the cursor to the top/bottom before moving up/down > > a line, making the whole thing simpler. > > > > Also, SCROLL does not report an error if you scroll too far. > > (Instead it returns a value of the amount actually scrolled, if you > > need it. It's a shame, I think, that MOVE_VERTICAL does not do the > > same). Thus, you will not need any on_error processing, so you can > > simplify it further by removing the SIMPLE_MOVE procedure. > > > > > > So here is a really cool stripped down version of SIMPLE.TPU that > > displays the file, moves the display, and hides the cursor.. > > > > > > input_file := GET_INFO (COMMAND_LINE, "file_name"); > > main_buffer:= CREATE_BUFFER ("main", input_file); > > > > position (BEGINNING_OF (main_buffer)); > > main_window := create_window(1,21,off); > > > > the_key_map := create_key_map ("user_keys"); > > the_key_map_list := create_key_map_list ("the_keylist", the_key_map); > > > > set (UNDEFINED_KEY, the_key_map_list, "return"); > > set (KEY_MAP_LIST, the_key_map_list, main_buffer); > > set (SELF_INSERT, the_key_map_list, OFF); > > > > MAP (main_window,main_buffer); > > message (ascii(27)+"[?25l"); > > > > ! > > define_key ("message(ascii(27)+'[?25h');QUIT (OFF,1)", kp1, > > the_key_map); > > define_key ("scroll (current_window, 1)", kp2, the_key_map); > > define_key ("scroll (current_window, -1)", kp8, the_key_map); > > define_key ("scroll (current_window, 20)", kp6, the_key_map); > > define_key ("scroll (current_window, -20)",kp4, the_key_map); > > define_key ("scroll (current_window, 1)", down, the_key_map); > > define_key ("scroll (current_window, -1)", up, the_key_map); > > ! > > > > Cheers, John -- > > ------------------------------ Date: Fri, 7 Jan 2005 07:39:07 -0500 From: "Neil Rieck" Subject: Re: Simple EDT or TPU init file Message-ID: <_pvDd.29822$7n1.1162660@news20.bellglobal.com> "Big John" wrote in message news:1105100083.002942.32550@f14g2000cwb.googlegroups.com... > [...snip...] > You've created some pretty cool extensions to TPU but I wonder how many people in this thread know about this simple one? $ cre sys$library EVE$INIT_NEIL.EVE set key edt (hit In article <_pvDd.29822$7n1.1162660@news20.bellglobal.com>, "Neil Rieck" writes: > You've created some pretty cool extensions to TPU but I wonder how many > people in this thread know about this simple one? > > $ cre sys$library EVE$INIT_NEIL.EVE > set key edt > (hit $ set/file/prot=(s:rwed,o:rwed,g:re,w:re) EVE$INIT_NEIL.EVE > $ EVE == "EDIT/TPU/INIT=sys$library:EVE$INIT_NEIL.EVE > > Now TPU will come up with most EDT commands in place. Why not just put the "set keyboard edt" in eve$init ? ------------------------------ Date: 7 Jan 2005 07:06:43 -0800 From: "AEF" Subject: Re: Simple EDT or TPU init file Message-ID: <1105110403.178446.188470@z14g2000cwz.googlegroups.com> Neil Rieck wrote: > "Big John" wrote in message > news:1105100083.002942.32550@f14g2000cwb.googlegroups.com... > > > [...snip...] > > > You've created some pretty cool extensions to TPU but I wonder how many > people in this thread know about this simple one? > > $ cre sys$library EVE$INIT_NEIL.EVE > set key edt > (hit $ set/file/prot=(s:rwed,o:rwed,g:re,w:re) EVE$INIT_NEIL.EVE > $ EVE == "EDIT/TPU/INIT=sys$library:EVE$INIT_NEIL.EVE > > Now TPU will come up with most EDT commands in place. I don't think any of the EDT commands will be in place. The EDT KEYPAD -- now that's a different story! The EDT keypad will be emulated, but no EDT commands will work, AFAIK. If they have been added at some point, I'd sure like to know about it! > > Neil Rieck > Kitchener/Waterloo/Cambridge, > Ontario, Canada. > http://www3.sympatico.ca/n.rieck/links/cool_openvms.html ------------------------------ Date: Fri, 7 Jan 2005 16:20:48 +0000 (UTC) From: peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER) Subject: Re: Simple EDT or TPU init file Message-ID: In article , koehler@eisner.nospam.encompasserve.org (Bob Koehler) writes: >In article <_pvDd.29822$7n1.1162660@news20.bellglobal.com>, "Neil Rieck" writes: > >> You've created some pretty cool extensions to TPU but I wonder how many >> people in this thread know about this simple one? >> >> $ cre sys$library EVE$INIT_NEIL.EVE >> set key edt >> (hit > $ set/file/prot=(s:rwed,o:rwed,g:re,w:re) EVE$INIT_NEIL.EVE >> $ EVE == "EDIT/TPU/INIT=sys$library:EVE$INIT_NEIL.EVE >> >> Now TPU will come up with most EDT commands in place. > > Why not just put the "set keyboard edt" in eve$init ? Or better a "$ DEFINE/SYSTEM EVE$KEYPAD EDT" in SYS$MANAGER:SYLOGICALS.COM -- Peter "EPLAN" LANGSTOEGER Network and OpenVMS system specialist E-mail peter@langstoeger.at A-1030 VIENNA AUSTRIA I'm not a pessimist, I'm a realist ------------------------------ Date: Fri, 7 Jan 2005 16:19:15 +0000 (UTC) From: peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER) Subject: Re: Simple EDT or TPU init file Message-ID: In article <_pvDd.29822$7n1.1162660@news20.bellglobal.com>, "Neil Rieck" writes: >You've created some pretty cool extensions to TPU but I wonder how many >people in this thread know about this simple one? > >$ cre sys$library EVE$INIT_NEIL.EVE That should be a colon and not a whitespace (sys$library:EVE$INIT_NEIL.EVE) >set key edt >(hit $ set/file/prot=(s:rwed,o:rwed,g:re,w:re) EVE$INIT_NEIL.EVE >$ EVE == "EDIT/TPU/INIT=sys$library:EVE$INIT_NEIL.EVE > >Now TPU will come up with most EDT commands in place. If "SET KEY EDT" is the only command in the EVE initialization file, then a "$ DEFINE EVE$KEYPAD EDT" in Neil's LOGIN.COM is much easier. OTOH, my SYS$SHARE:EVE$INIT.EVE looks somehow like this TPU IF GET_INFO (SCREEN, "MOTIF") THEN SET (MOUSE,ON) ELSE SET (MOUSE,OFF) ENDIF DEF KEY=CONTROL-B SET WIDTH 132 DEF KEY=CONTROL-N SET WIDTH 80 DEF KEY=F8 QUIT DEF KEY=GOLD-E EXIT DEF KEY=GOLD-Q QUIT DEF KEY=GOLD-X TPU WRITE_FILE (SELECT_RANGE,"TMP.TMP") DEF KEY=GOLD-LEFT "SHIFT LEFT 8" DEF KEY=GOLD-RIGHT "SHIFT RIGHT 8" SET CURSOR BOUND SET NOEXIT ATTRIBUTE CHECK SET SCROLL MARGIN 7 7 SET NOWRAP and I think some lines (1,8-10,12-13) are important to get a EDT feeling in EVE YMMV -- Peter "EPLAN" LANGSTOEGER Network and OpenVMS system specialist E-mail peter@langstoeger.at A-1030 VIENNA AUSTRIA I'm not a pessimist, I'm a realist ------------------------------ Date: 7 Jan 2005 07:46:27 GMT From: "Dave Weatherall" Subject: Re: VAXstation 3100: supported under VMS 7.3? Message-ID: On Thu, 6 Jan 2005 15:00:31 UTC, Kilgallen@SpamCop.net (Larry Kilgallen) wrote: > The only people running systems as old as the ones you describe > are likely to be VMS hobbyists, who do not buy support contracts > anyway, so whether a given box is supported or not is immaterial. > > * If there is some customer who wants to buy lots of support contracts > for a particular older system, I suppose the management at VMS Development > might be influenced. But it is more expensive for VMS Development to > support older systems than newer systems, since running a particular > test suite is going to take longer on an older system. So the contract > you are willing to sign for support should be for a _large_ number of > that older system model. There's a VaxStation 3100/M76 on my desk and I use it every day I'm at work. It runs under VMS 6.2. I confess that these days it's mainly a 'DecTerm screen'. It's been a while since I used it to test the VAX/VMS version of my VAX/ELN systems, or other Decnet Server processes. If it has to be replaced when we move to VMS 7.3(-1) I'll try and collar an AlphaStation 255. I've been told I can bring the VaxStation home. -- Cheers - Dave W. ------------------------------ Date: Fri, 07 Jan 2005 02:58:12 -0500 From: Dave Froble Subject: Re: VMS ready laser printer? Message-ID: <41DE4114.6040302@tsoft-inc.com> Bob Kaplow wrote: > I'm looking for an INEXPENSIVE b/w laser printer for connecting to my home > office network. Everything in the mass market stores these days seems to be > PC/USB only unless you buy an adapter. I want something that my VMS systems > can use. Something that understands PCL and maybe even PostScript? Something > with an ethernet port included. > > What's the current equivalent of the old standard Laserjet III / IV with > built in JetDirect? And it doesn't have to be from HP! > > BTW, has VMS integrated HP Laserjet support yet so you don't have to roll > your own forms libraries for "standard" HP printers? > > > Bob Kaplow NAR # 18L TRA # "Impeach the TRA BoD" > >>> To reply, remove the TRABoD! <<< > Kaplow Klips & Baffle: http://nira-rocketry.org/LeadingEdge/Phantom4000.pdf > www.encompasserve.org/~kaplow_r/ www.nira-rocketry.org www.nar.org > > Homeland Security Administration: The Gestapo of the 21st Century > Well, you can't always have everything. :-) I recently bought a Brother MultiFunction system (print/copy/fax) from Staples. It's a re-conditioned unit. Has the same 1 year warranty. Price begins at $200, then there is a $50 rebate until sometime in February, and there was another $20 off for something. $129 + sales tax. That's less than the cost of a replacement drum. Was cheaper than getting my old printer fixed. Parallel and USB ports, no ethernet port. Not too bad for $129. Dave ------------------------------ End of INFO-VAX 2005.014 ************************