1 INFO-VAX	Sun, 03 Nov 2002	Volume 2002 : Issue 608       Contents:+ Re: can vms C access the keyboard directly? + Re: can vms C access the keyboard directly? + Re: can vms C access the keyboard directly? + Re: can vms C access the keyboard directly? + Re: can vms C access the keyboard directly?  Re: CHARON-ALPHA - soon ???? OPCOM suggestions  Re: OPCOM suggestions  Re: OPCOM suggestions  Re: OPCOM suggestions  Re: Remote Console access 7 Re: VMS to support KDE over CDE in which future version 7 Re: VMS to support KDE over CDE in which future version 7 Re: VMS to support KDE over CDE in which future version 7 Re: VMS to support KDE over CDE in which future version , [OpenVMS Alpha V7.3, MMOV V2.2] Why ACCVIO ?# Re: [very OT] OS X, the (bad?) turn # Re: [very OT] OS X, the (bad?) turn   F ----------------------------------------------------------------------  % Date: Sat, 02 Nov 2002 22:57:07 -0500 ' From: Howard S Shubs <howard@shubs.net> 4 Subject: Re: can vms C access the keyboard directly?< Message-ID: <howard-5B5F91.22570702112002@enews.newsguy.com>  . In article <us8o5lfggq965@corp.supernews.com>,#  Z  <zarlenga@conan.ids.net> wrote:   , > Paul Sture <p_sture@elias.decus.ch> wrote:I > :> On Unix you set the tt control with ioctl() and then call getchar().  > :> That's hard?  > / > : For someone who hasn't done it before, yes.  > H > : I've just had a swift look at "man ioctl" and while I could probablyF > : figure it out eventually, it would be swifter to scour the net for# > : an example, or ask a newsgroup.  > H > IMO, the following is MUCH easier reading than the 1 or 2 chapters oneM > must read in the I/O User's Guide to properly use $QIO for single-character 	 > input :   0 From memory, I've done this too darn many times:   c  c  INCLUDE files c     include '($iodef)'     include '($ssdef)'    c  c  External functions  c 0    integer*4 sys$assign      !ASSIGN i/o channel2    integer*4 sys$dassgn      !DeASSiGN i/o channel:    integer*4 sys$qiow        !Queue I/O request, with Wait  =    integer*2 channel         !I/O channel to the input device ;    integer*2 iosb(4)         !i/o status block return value 3    integer*4 status          !returned status value <    character c               !place to put the one character   c $ c  Assign a channel to the terminal. c )    status = sys$assign ('TT:', channel,,) '    if (.not. status) call exit (status)    c E c  Get one character into the variable "C".  The character will echo. A c  If you don't want the character to echo, change the expression C c  IO$_READVBLK to IO$_READVBLK + IO$M_NOECHO.  If you're a purist, D c  use .OR. instead of "+", but functionally this won't matter here. c ' c  Here's a more detailed explaination:  c  The call looks like this: c C c  status = sys$qiow ([flag], channel, function, [iosb], [astadr],  C c  1                  [astprm], [p1], [p2], [p3], [p4], [p5], [p6])  c  c  Arg      description H c  flag     event completion flag, not needed since this is being calledD c           synchronously.  For the $QIO call, this would be used toG c           denote the completion of the I/O request, as a number in an ; c           assocated event flag mask, by value.  Optional. @ c  channel  I/O channel to perform the I/O request on, by value.@ c  function I/O function to perform, with any options, by value.D c  iosb     a quadword I/O status block in which the driver depositsI c           completion information.  This is highly device-type-dependant F c           but for a terminal looks like 4 16-bit words.  See the I/OH c           User's Manual for details.  Important part is the first one,C c           which can contain a different return status than the R0 A c           status value.  IIRC, the second word is the number of F c           characters actually transferred during the request.  CouldH c           be fewer than requested if there weren't enough or there wasD c           a timeout period and it expired.  Optional, but strongly c           recommended.? c  astadr   completion AST routine address, by value. Optional. D c  astprm   CALLG-style routine parameter block address, by value.   c           Optional. I c  P1..P6   function-specific arguments.  These are entirely dependant on @ c           what you specified as a function.  For the terminal D c           IO$_READVBLK (READ Virtual BLocK, as opposed to logical G c           block or physical block) as specified below, there are only H c           two actual arguments: the address of the buffer to place theB c           results in is P1, and P2 is the value of the number ofE c           characters to read.  If there was a IO$M_TIMOUT (timeout) G c           option on the function, P3 would be a number in seconds, by I c           value.  If you specified a IO$M_PROMPT, P5 and P6 would be a  I c           pointer to the prompt and a length of the prompt.  Those are  : c           the most popular variations, in my experience. c D c  Now the rest of you can tell me which parameter I forgot.  C'mon, c  there's got to be one...  c D    status = sys$qiow (, %val (channel), %val (io$_readvblk), iosb,,,    1  c, %val(1),,,,) &    if (.not.status) call exit (status)      write (*,10) c . 10 format (' you entered <',a1, '> just now.')   c H c  Clean up time.  Not necessary if your program is about to end anyway,G c  but it's good to be neat and give the image rundown handler less to  C c  do.  And it's appropriate if your program is -not- about to end.  c &    status = sys$dassgn (%val(channel))      call exit (status)     end   --  4 Today, on Paper-view: The World Origami Championship   ------------------------------  % Date: Sun, 03 Nov 2002 19:18:40 +1100 1 From: Paddy O'Brien <paddy.o'brien@tg.nsw.gov.au> 4 Subject: Re: can vms C access the keyboard directly?, Message-ID: <3DC4DBE0.7000306@tg.nsw.gov.au>   JF Mezei wrote:  > Question about $QIO  > K > How do I setup a $QIO to return a single character OR return a multi-byte  > terminator ? > O > If I specify a buffer of 1, it will return every character received, but what & > about a multi character terminator ?  K A couple of days ago, I put up two ancient Fortran programs.  Do they help?    Regards, Paddy      G ***********************************************************************   C "This electronic message and any attachments may contain privileged > and confidential information intended only for the use of the B addressees named above.  If you are not the intended recipient of C this email, please delete the message and any attachment and advise B the sender.  You are hereby notified that any use, dissemination, 7 distribution, reproduction of this email is prohibited.   A If you have received the email in error, please notify TransGrid  A immediately.  Any views expressed in this email are those of the  = individual sender except where the sender expressly and with  C authority states them to be the views of TransGrid.  TransGrid uses > virus scanning software but excludes any liability for viruses contained in any attachment.  < Please note the email address for TransGrid personnel is now$ firstname.lastname@transgrid.com.au"  G ***********************************************************************    ------------------------------  % Date: Sun, 03 Nov 2002 02:45:40 -0500 - From: JF Mezei <jfmezei.spamnot@videotron.ca> 4 Subject: Re: can vms C access the keyboard directly?, Message-ID: <3DC4D41A.2DD8501E@videotron.ca>   Paddy O'Brien wrote:M > A couple of days ago, I put up two ancient Fortran programs.  Do they help?     M In those, you don't make use of the "terminator" capabilities of QIO, instead N you process character by character and assemble the escape sequences manually.   ------------------------------  % Date: Sun, 03 Nov 2002 20:03:04 +1100 1 From: Paddy O'Brien <paddy.o'brien@tg.nsw.gov.au> 4 Subject: Re: can vms C access the keyboard directly?, Message-ID: <3DC4E648.9080906@tg.nsw.gov.au>   JF Mezei wrote:  > Paddy O'Brien wrote: > M >>A couple of days ago, I put up two ancient Fortran programs.  Do they help?  >  >  > O > In those, you don't make use of the "terminator" capabilities of QIO, instead P > you process character by character and assemble the escape sequences manually.  H True.  I forget my rationale now, as I wrote those in the mid-eighties. E   Vaguely I think it gave me easier access to all the keys with less  G code.  I have some code here which a previous employee did write using  A that capability.  Or I did not fully understand QIO at that time.   I I did ask for comments, and thanks.  I'll try to re-understand why I did   what I did.    Regards, Paddy    G P.S.  It suddenly came to mind:  I did not want the calling program to  4 have to know about terminators.  Anyway, I'll check.            G ***********************************************************************   C "This electronic message and any attachments may contain privileged > and confidential information intended only for the use of the B addressees named above.  If you are not the intended recipient of C this email, please delete the message and any attachment and advise B the sender.  You are hereby notified that any use, dissemination, 7 distribution, reproduction of this email is prohibited.   A If you have received the email in error, please notify TransGrid  A immediately.  Any views expressed in this email are those of the  = individual sender except where the sender expressly and with  C authority states them to be the views of TransGrid.  TransGrid uses > virus scanning software but excludes any liability for viruses contained in any attachment.  < Please note the email address for TransGrid personnel is now$ firstname.lastname@transgrid.com.au"  G ***********************************************************************    ------------------------------  % Date: Sun, 03 Nov 2002 10:55:58 -0500 ( From: David Froble <davef@tsoft-inc.com>4 Subject: Re: can vms C access the keyboard directly?, Message-ID: <3DC5470E.5090406@tsoft-inc.com>   Howard S Shubs wrote:     F > c  iosb     a quadword I/O status block in which the driver depositsK > c           completion information.  This is highly device-type-dependant H > c           but for a terminal looks like 4 16-bit words.  See the I/OJ > c           User's Manual for details.  Important part is the first one,E > c           which can contain a different return status than the R0 C > c           status value.  IIRC, the second word is the number of H > c           characters actually transferred during the request.  CouldJ > c           be fewer than requested if there weren't enough or there wasF > c           a timeout period and it expired.  Optional, but strongly > c           recommended.  F > c  Now the rest of you can tell me which parameter I forgot.  C'mon, > c  there's got to be one...     J My only issue is that it's my understanding that there is a status on the P queueing of either a QIOW or a QIO, and for either there is a completion status / of the operation in the first word of the IOSB.   L I don't think that the testing of the completion status is optional, at any K time.  There was just a thread on a piece of freeware, and the problem was  $ sloppy testing of completion status.   It's got to be:   
 1) Successful ) 2) Successful with additional information A 3) Some error condition that you anticipate and have provided for Q 4) An unexpected error, which should be reported, and then you really don't have  # any logical recovery, so, an abort.   F Note, if there was a logical recovery, then that would be condition 3.   Dave   ------------------------------  % Date: Sat, 02 Nov 2002 20:40:34 -0500  From: Everhart <ge@gce.com> % Subject: Re: CHARON-ALPHA - soon ???? + Message-ID: <aq1uqn$8pi$1@bob.news.rcn.net>    Tom Cole wrote: K > I bet as one of the authors of CHARON-VAX, he's not pulling it out of his  > butt... :) > N > If you think about the issues around implementing a CISC instruction set viaK > emulation, each VAX instruction neatly translates into a reasonably small L > but non-zero-sized amount of logic, expressable as a method switch case orK > whatever invocation architecture you choose.  The cost of translating the E > instruction is relatively low compared to the cost of executing it, I > especially since many VAX instructions require *quite* a bit of code to J > implement correctly - for example, D_FLOAT math isn't trivial on an IEEEL > architecture, and EMODD becomes more than a few lines of code to implement > as a result... :)  > L > By comparison, each Alpha instruction is quite a bit more succinct in whatK > it does - the cost of decoding the instruction could easily match or even M > overwhelm the cost of executing the logic associated with that instruction. K > In short, you don't get a pleasing tradeoff between virtual machine speed : > and compiled methods like you do in a CISC architecture. > K > I would love to see an Alpha emulator worth it's salt, and I believe that J > SRI are the folks who can do it, but I do agree that a 1:4 ratio is veryL > unlikely between emulated and physical machine speeds - even with a wickedL > clever instruction decoder, it's hard to imagine anything faster than 1:20G > or something like that, especially given that you pretty much have to M > emulate the virtual memory processing no matter how clever your instruction 2 > decoder is, and that's a bear in it's own right. > H > In short, I don't think that chip complexity is the issue; it's more a) > fundamental aspect of RISC versus CISC.  >  > ; > "Keith A. Lewis" <lewis@mazda.mitre.org> wrote in message * > news:apuc51$9mv$1@newslocal.mitre.org... > @ >>"Robert Boers" <robert.boers@softresint.com> writes in article > F > <3dc24668$1@news.deckpoint.ch> dated Fri, 1 Nov 2002 10:16:21 +0100: > G >>>The ratio of 1.5 GHz to 400 MHz is far too optimistic, and mapping a  >> > 64-bit > F >>>CPU emulator on a 32-bit host system is * very * inefficient. Given >>	 > Alpha's  > K >>>excellent arithmetic units, a reasonable host would be a dual AMD Hammer G >>>system. A dual 2 GHz Hammer system would provide the equivalent of a  >> > 100 -  > $ >>>140 MHz Alpha, not very exciting. >>K >>I agree that Dean's ratio is over-optomistic, and the way he presented it J >>made it sound like he pulled the numbers out of his butt.  Are you doing >  > the  > J >>same thing?  If there are ALU and transistor-count comparisons out there% >>somewhere, I'd like to take a look.  >>- >>--Keith Lewis              klewis$mitre.org @ >>The above may not (yet) represent the opinions of my employer. >  >  > K I would suggest that such an emulator would be most usefully implemented on M a 64 bit machine first. I would suggest using an alpha. Strangely enough this L would not be quite as useless as might first appear: if done right, it wouldK provide a way to emulate privileged code in user mode emulation. However it G certainly is not a trivial task to do all the memory mapping and so on, = though perhaps the presence of PAL code would make it easier.   C I will also remind the crew here that DEC did some part of an alpha J emulator way back when as part of alpha development. I don't know how muchH was there,and it certainly emulated no very current alpha processor, butM was a sort of proof point. Wonder if Mr. Supnick will ever persuade those who Q have it to release it as a starting point? I think it was called Mannequin (which N was then dressed with things like VEST and TIE [never heard of anything called PANTS though ;-) ]).  K I suspect Mannequin may not have been totally complete since its job was to M help with very early development, not to support the mature VMS OS. I believe J it ran on Vax (after all, what else was there back then?)...which leads toM the image of running a VAX emulator on some machine like a PC in order to run J an Alpha emulator on the emulated VAX in order to do something or other...  8 Surely an exercise for those over-endowed with patience.   Glenn Everhart    H BTW found the post with the Cswing fix and am merging with Grant's fixedI up code.  I will experiment to see if the bump of wildcard context can be  now removed.   ------------------------------  % Date: Sun, 03 Nov 2002 05:51:32 -0500 - From: JF Mezei <jfmezei.spamnot@videotron.ca>  Subject: OPCOM suggestions, Message-ID: <3DC4FFB0.7A9D7972@videotron.ca>  E 1- make sure that the OPERATOR.LOG file is written in such a way that  TYPE/TAIL is *always* usable.   L It is a pain to have to use TPU to look at the end of the file. (edt refusesJ to open the file since it is already opened by OPCOM, and TPU takes a long5 time to start since operator.lot is often very large)    ------------------------------  % Date: Sun, 03 Nov 2002 06:01:56 -0500 - From: JF Mezei <jfmezei.spamnot@videotron.ca>  Subject: Re: OPCOM suggestions, Message-ID: <3DC5021F.FBBAECC1@videotron.ca>   Another suggestion:   M REPLY/FLUSH  Causes OPCOM to flush buffers to the logfile so that one can see / uptodate contents when typing/editing the file.       L Also, when REPLY/LOG is issued,  OPCOM does look at OPC$LOGFILE_NAME logicalE name, but the newly created file doesn't reflect current settings for I OPC$LOGFILE_CLASSES. (eg: LOGFILE_CLASSES is probably looked at only when  OPCOM starts).   ------------------------------  * Date: Sun, 3 Nov 2002 13:38:00 +0000 (UTC)+ From: david20@alpha1.mdx.ac.uk (David Webb)  Subject: Re: OPCOM suggestions) Message-ID: <aq38ro$t$1@aquila.mdx.ac.uk>   \ In article <3DC4FFB0.7A9D7972@videotron.ca>, JF Mezei <jfmezei.spamnot@videotron.ca> writes:F >1- make sure that the OPERATOR.LOG file is written in such a way that >TYPE/TAIL is *always* usable. > M >It is a pain to have to use TPU to look at the end of the file. (edt refuses K >to open the file since it is already opened by OPCOM, and TPU takes a long 6 >time to start since operator.lot is often very large)  J There is an old public domain tail program available which works much much better than type/tail.H If you can't get it elsewhere it is available from my anonymous ftp area    ftp://ftp.mdx.ac.uk/vms/tail.zip    
 David Webb VMS and Unix team leader CCSS Middlesex University   ------------------------------  % Date: Sun, 03 Nov 2002 12:17:57 -0600 1 From: "David J. Dachtera" <djesys.nospam@fsi.net>  Subject: Re: OPCOM suggestions' Message-ID: <3DC56855.6D74C061@fsi.net>    JF Mezei wrote:  > G > 1- make sure that the OPERATOR.LOG file is written in such a way that  > TYPE/TAIL is *always* usable.  > N > It is a pain to have to use TPU to look at the end of the file. (edt refusesL > to open the file since it is already opened by OPCOM, and TPU takes a long7 > time to start since operator.lot is often very large)   D For the OPCOM log, I've never found TYPE/TAIL to be all that useful,H since the events I'm usually looking require viewing a considerable timeH period. I find TYPE/OUTPUT much more useful since I can then examine the" output file with EDT, SEARCH, etc.   --   David J. Dachtera  dba DJE Systems  http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/    ------------------------------  % Date: Sun, 03 Nov 2002 09:42:41 +0100 ) From: Bart Zorn <B.Zorn@xs4all.nospam.nl> " Subject: Re: Remote Console access6 Message-ID: <3dc4e182$0$46614$e4fe514c@news.xs4all.nl>   Main, Kerry wrote: > Bart, Robert - > I > ConsoleWorks started as an OpenVMS based product (VAX and Alpha), so it > > is a very good VMS based product for managing many consoles. > J > If Customers or Prod Mgrs :-) decide to implement PC platforms to manageI > important systems, then that is their decision, but it can certainly be  > done in other ways.  >  > Reference:: > http://www.tditx.com/services_support_faqs.html#console  > E > (scroll down and look at the OS listed first under supported server  > OS's)  >  > :-)  > 	 > Regards  >  > Kerry Main > Senior Consultant  > Hewlett-Packard (Canada) Co.# > Consulting & Integration Services  > Voice: 613-592-4660  > Fax   : 613-591-4477 > Email: kerryDOTmain@hpDOTcom/ >     (remove the DOT's and replace with "."'s)   I Fair enough! However, as a consultant who has not been involved with the  E initial configuration of my current client's Wildfire systems, I see  F that they are configured with billyboxes in such a way that those are H definitely a single point of failure with a miserable user interface on C top of it (you can't even use cut and paste in the console window!)   G The only way to make them usable is through the ConsoleWorks client on  E OpenVMS. But there I have not found a way to do something similar as  F Console Manager's CONSOLE CONNECT <node>. You have to do it in a much # more complex way (logging in, e.a.)   	 Bart Zorn    ------------------------------  % Date: Sun, 03 Nov 2002 09:47:18 +0100 ) From: Bart Zorn <B.Zorn@xs4all.nospam.nl> @ Subject: Re: VMS to support KDE over CDE in which future version6 Message-ID: <3dc4e296$0$46611$e4fe514c@news.xs4all.nl>   C.W.Holeman II wrote: E > Anyone have any info on the rumor that a future release of VMS will E > support KDE? I was told by a VMS Ambassador the CDE was going to be  > replaced by KDE. >  > -- > C.W.Holeman II> > cwhii5@Julian5Locals.com                http://also.as/cwhii > remove the fives% > Send spam to junkmail@earthlink.net   H Is KDE something we should be waiting for? The only advantage (IMHO) of C CDE over the classic Motif desktop is the availability of multiple  G workspaces. But you have to take a lot of unixisms to configure things  ( to your taste. And those default colors!  % Will KDE be an improvement over this?   	 Bart Zorn    ------------------------------  % Date: Sun, 03 Nov 2002 04:13:21 -0500 - From: JF Mezei <jfmezei.spamnot@videotron.ca> @ Subject: Re: VMS to support KDE over CDE in which future version, Message-ID: <3DC4E8A1.5D53DBF0@videotron.ca>   Bart Zorn wrote:' > Will KDE be an improvement over this?   A What percentage of VMS-based workstations are VAX versus Alpha ?    < (VAX isn't getting any of thew new goodies such as CDE etc).   ------------------------------  % Date: Sun, 03 Nov 2002 07:41:59 -0600 5 From: Michael Rice <MichaelARice@no-spam.knology.net> @ Subject: Re: VMS to support KDE over CDE in which future version2 Message-ID: <3DC527A7.7030007@no-spam.knology.net>   C.W.Holeman II wrote: E > Anyone have any info on the rumor that a future release of VMS will E > support KDE? I was told by a VMS Ambassador the CDE was going to be  > replaced by KDE. >  > -- > C.W.Holeman II> > cwhii5@Julian5Locals.com                http://also.as/cwhii > remove the fives% > Send spam to junkmail@earthlink.net   H If that's true, then that implies the Trolltech Qt software is going to ' be ported to VMS.  That would be great!    ------------------------------   Date: 3 Nov 2002 10:32:06 -0600 B From: clubley@remove_me.eisner.decus.org-Earth.UFP (Simon Clubley)@ Subject: Re: VMS to support KDE over CDE in which future version3 Message-ID: <JbIOJ1PPYWYr@eisner.encompasserve.org>   r In article <77555df7.0211022058.535989ff@posting.google.com>, cwhii_google_spam@yahoo.com (C.W.Holeman II) writes:E > Anyone have any info on the rumor that a future release of VMS will E > support KDE? I was told by a VMS Ambassador the CDE was going to be  > replaced by KDE. >   : I sincerely hope that it will be GTK/Gnome instead of KDE.  D Amongst other things, GTK has been designed to support many language> bindings from day one, and has a wider range of them than KDE.   Simon.   --  B Simon Clubley, clubley@remove_me.eisner.decus.org-Earth.UFP       & "This is VMS. Viruses are irrelevant."   ------------------------------  # Date: Sun, 03 Nov 2002 09:47:57 GMT . From: peter@langstoeger.at (Peter LANGSTOEGER)5 Subject: [OpenVMS Alpha V7.3, MMOV V2.2] Why ACCVIO ? 4 Message-ID: <hh6x9.94061$aa2.1181427@news.chello.at>  H As you might know, I still run OpenVMS V7.3 (with almost all ECOs) on my> PWS433au with an 3D30 - so no V7.3-1 binary issues apply here.D I also have MMOV V2.2 (and FWIW Open3D V4.9B) installed and started.  N Today, after some months, I tried to play a MPEG file with MPEG3PLAY freeware.: But nothing happened because/and the MMOV_SERVER ACCVIOed.  J I do use MPEG3PLAY occasionally but for years. I didn't have such problemsG before, but I'm not sure if I used MPEG3PLAY already since the last VMS # upgrade (or what ECO installation).     ! $ TYPE SYS$STARTUP:MMOV_ERROR.LOG - Copyright  1993 Compaq Computer Corporation. / mmeserver V2.2 17-APR-2000 23:01:59.15 %%2(1,2)     " $ TYPE SYS$STARTUP:MMOV_SERVER.LOG; %CMA-F-EXCCOP, exception raised; VMS condition code follows P -SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=000000000000& 0004, PC=000000007BCD3758, PS=0000001B    L The exit code of the MMOV_SERVER process is 10408014 which is a threads one.% %CMA-F-NOMSG, Message number 10408014   ) Do you know what CMA error code this is ? < Do you know of any problems with MMOV V2.2 on OpenVMS V7.3 ?( Did you already have the same problems ?  Do you know of an ECO for MMOV ?/ Do you know of problems with the THREADS ECOs ? * Do you know of a solution for my problem ?   Many TIA   -Peter  8 PS: I've the following ECOs installed (if this matters):   	VMS73_ACRTL		2.0  	VMS73_AMACRO		1.0 	VMS73_APB		1.0  	VMS73_BACKUP		1.0 	VMS73_CLIUTL		2.0 	VMS73_CLUSTER		2.0  	VMS73_CPU2308		1.0  	VMS73_DCL		2.0  	VMS73_DDTM		1.0 	VMS73_DECW_XTERM	1.0  	VMS73_DELETE		1.0 	VMS73_DRIVER		3.0 	VMS73_F11X		1.0 	VMS73_FIBRE_SCSI	3.0  	VMS73_GRAPHICS		1.0 	VMS73_INIT		1.0 	VMS73_LAN		3.0  	VMS73_LIBRTL		2.0 	VMS73_LINKER		3.0 	VMS73_LMF		1.0  	VMS73_MANAGE		2.0 	VMS73_MIME		1.0 	VMS73_MONTOR		1.0 	VMS73_PPPD		2.0 	VMS73_PTHREAD		3.0  	VMS73_REGISTRY		1.0 	VMS73_REM		1.0  	VMS73_RMS		4.0  	VMS73_RTPAD		1.0  	VMS73_SHADOWING		2.0  	VMS73_SYS		4.0  	VMS73_SYSINI		1.0 	VMS73_SYSLOA		3.0 	VMS73_UPDATE		1.0 	VMS73_XFC		2.0    --   Peter "EPLAN" LANGSTOEGER % Network and OpenVMS system specialist  E-mail  peter@langstoeger.atF A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist   ------------------------------  % Date: Sun, 03 Nov 2002 02:05:39 -0500 - From: JF Mezei <jfmezei.spamnot@videotron.ca> , Subject: Re: [very OT] OS X, the (bad?) turn, Message-ID: <3DC4CABB.F857B1B9@videotron.ca>  
 -Andy- wrote: , > Selector ? I've been using Macs since 1989  3 I've been using Macs since 1986... beat you to it !   / "Slecteur" in french ---> "Chooser" in english    ------------------------------  % Date: Sun, 03 Nov 2002 00:29:31 -0600 % From: "-Andy-" <acs@fcgnet.works.net> , Subject: Re: [very OT] OS X, the (bad?) turn= Message-ID: <Xns92BBECE89E90acsfcgnetworksnet@216.166.71.232>   = Didier.Morandi.nospam@Free.fr (Didier Morandi) enlightened us  with< news:1fl0gq2.y1a5e41o4iz4cN%Didier.Morandi.nospam@Free.fr on
 02 Nov 2002:    8 > I finally decided to install OS X on my iMac because I< > wanted to try the new Apple iSynch tool (yeah, I know it's; > a beta version and it does not seem to synch anything yet  > :-)   1 There ARE better places to ask these questions...    > Now, I have OS X.  >  > 1. where is the selector? < > I still have the Classic selector access, so I do not need > OS X.   ? Selector ? I've been using Macs since 1989 (Ok... so I started  < with them late)... what do you mean by "selector" ? Finder ?: (it's there) or something else - program selector like the Dock ?   6 > 2. where is the background image customization menu?  > Hmmm.... it's there though it seems to be better in OS X 10.2  than earlier versions of OS X.  9 > I dragged an image into the bg window area, it came too 6 > wide on my screen and no way (found) to change this.  : ?? What version os OS X ?? 10.2 lets you have SOME control over the background image...   . > 3. where is the Remote Access control panel?  ; In System Preferences - Combination of the Network control  0 panel and "Internet Connection" seem to work....     5 > 4. Where is the automatic indexation feature within : > Sherlock? Should I really wait for a new indexation each< > time I open it? Boring. I want my nightly processing back.  3 No idea.... not a feature I've really ever used....    5 > 5. Why does the Classic indexation process not work  > anymore?    
 No idea...     8 I think Mac OS X does very well.... for a Unix disguised> as a Mac. And very stable (usually).... now if only there was < a way to sync my Zarus with it without buying a CF wireless  card.    -Andy-   ------------------------------   End of INFO-VAX 2002.608 ************************                                                                                                                                                                                                                                                                                                                                                                    @    A    B    C    D    E    F    G    H    I    J    K    L    M    N    O    P    Q    R    S    T    U    V    W    X    Y    Z    [    \    ]    ^    _    `    a    b    c    d    e    f    g    h    i    j    k    l    m    n    o    p    q    r    s    t    u    v    w    x    y    z    {    |    }    ~                                                                                                                                                                                                                                                                                ®    î    Į    Ů    Ʈ    Ǯ    Ȯ    ɮ    ʮ    ˮ    ̮    ͮ    ή    Ϯ    Ю    Ѯ    Ү    Ӯ    Ԯ    ծ    ֮    ׮    خ    ٮ    ڮ    ۮ    ܮ    ݮ    ޮ    ߮                                                                                                                                                                         	    
            
                                                                                 !    "    #    $    %    &    '    (    )    *    +    ,    -    .    /    0    1    2    3    4    5    6    7    8    9    :    ;    <    =    >    ?    @    A    B    C    D    E    F    G    H    I    J    K    L    M    N    O    P    Q    R    S    T    U    V    W    X    Y    Z    [    \    ]    ^    _    `    a    b    c    d    e    f    g    h    i    j    k    l    m    n    o    p    q    r    s    t    u    v    w    x    y    z    {    |    }    ~                                                                                                                                                                                                                                                                                ¯    ï    į    ů    Ư    ǯ    ȯ    ɯ    ʯ    ˯    ̯    ͯ    ί    ϯ    Я    ѯ    ү    ӯ    ԯ    կ    ֯    ׯ    د    ٯ    گ    ۯ    ܯ    ݯ    ޯ    ߯                                                                                                                                    