1 INFO-VAX	Mon, 21 Nov 2005	Volume 2005 : Issue 649       Contents:	 Boot disk 
 Re: Boot disk 
 Re: Boot disk  Re: Configure tips Re: No more SETI on VMS ? ) Re: Setting Terminal Line Charcateristics ) Re: Setting Terminal Line Charcateristics ) Re: Setting Terminal Line Charcateristics   F ----------------------------------------------------------------------    Date: 20 Nov 2005 13:11:38 -0800$ From: "Oblix" <oba_baby@hotmail.com> Subject: Boot diskC Message-ID: <1132521098.276654.269570@f14g2000cwb.googlegroups.com>   C My knowledge with OpenVMS is not that good so bare with me please..   C I now managed to make format and restore on a Conner 2.4GB new hard $ disk on my MicroVAX 3100/95 station., The hard disk takes DKA0 on the workstation.+ How can I change it to be DKA300 or DKA200? 7 Is there a way to remove the bad blocks on a hard disk? A I have alot of parity errors on the original hard disk. how can I  remove them?D I don't think formatting will help. Is there anything that I can do?  E Another thing, I tried to make a backup copy of another HD. It take a   long time and it never finishes.F I am afraid that if i do Analyze disk it will damage some files that I1 don't have a backup copy of. Can you help please?    Thank    ------------------------------  + Date: Sun, 20 Nov 2005 22:06:19 +0000 (UTC) < From: gartmann@non.immunbio.mpg.de.sens (Christoph Gartmann) Subject: Re: Boot disk) Message-ID: <dlqs0r$7nv$1@news.BelWue.DE>   j In article <1132521098.276654.269570@f14g2000cwb.googlegroups.com>, "Oblix" <oba_baby@hotmail.com> writes:D >My knowledge with OpenVMS is not that good so bare with me please.. > D >I now managed to make format and restore on a Conner 2.4GB new hard% >disk on my MicroVAX 3100/95 station. - >The hard disk takes DKA0 on the workstation. , >How can I change it to be DKA300 or DKA200?  ) Change the SCSI-ID of the disk to 3 or 2.   8 >Is there a way to remove the bad blocks on a hard disk?  ' Yes, you have to do a low-level format.   B >I have alot of parity errors on the original hard disk. how can I
 >remove them?   
 See above.  E >I don't think formatting will help. Is there anything that I can do?   < Formatting will help, provided it is a low-level formatting.H Unfortunately I don't remember how to perform a low-level SCSI-format on' a MicroVAX but there is a way to do it.   F >Another thing, I tried to make a backup copy of another HD. It take a! >long time and it never finishes. G >I am afraid that if i do Analyze disk it will damage some files that I 2 >don't have a backup copy of. Can you help please?  L ANALYZE/DISK/READ/REPAIR will not do any harm to your files. Instead it will3 try to map the bad blocks out and recover any data.    Regards,    Christoph Gartmann    --  E  Max-Planck-Institut fuer      Phone   : +49-761-5108-464   Fax: -452   ImmunbiologieI  Postfach 1169                 Internet: gartmann@immunbio dot mpg dot de   D-79011  Freiburg, Germany 9                http://www.immunbio.mpg.de/home/menue.html    ------------------------------  % Date: Sun, 20 Nov 2005 17:10:53 -0500 - From: JF Mezei <jfmezei.spamnot@teksavvy.com>  Subject: Re: Boot disk, Message-ID: <4380F46C.DF22F2DB@teksavvy.com>   Oblix wrote:. > The hard disk takes DKA0 on the workstation.- > How can I change it to be DKA300 or DKA200?   E YOu may wish to check its SCSI ID to make sure there is no conflict.  T YOu shoudln't use 0 or 7 as SCSI ID since this is often used by the SCSI controller.  9 > Is there a way to remove the bad blocks on a hard disk?   F YOU need very very small tweezers to remove the bad magnetic particles and deposit new ones. :-)     G If you did a low level format, it would automatically detect bad blocks * and revector them with spare good blocks.   C > I have alot of parity errors on the original hard disk. how can I  > remove them?  G Make sure the disk is properly configured. If it is properly configured : and you still get parity errors, then the disk is no good.  H > I am afraid that if i do Analyze disk it will damage some files that I3 > don't have a backup copy of. Can you help please?   E ANA/DISK/REPAIR does not damage the disk. It works at the file system G level.  There are other qualifiers that will actually exercise the disk U surface either in a destructive mode. HELP ANA/DISK will give you a good description.    ------------------------------  % Date: Sun, 20 Nov 2005 22:30:47 +0100 8 From: Martin Borgman <martin.borgman@oooovms.dyndns.org> Subject: Re: Configure tips 6 Message-ID: <4380eb07$0$11062$e4fe514c@news.xs4all.nl>   Hi John,  H you're missing one of the most important options in "UNIX" porting. The F CRTL feature switches. With these feature switches you can change the / CRTL's behavior to a more "UNIX" like behavior. H And since you mention getopt, yes you can change getopts behavior to be 8 case sensitive. The way "UNIX" programs expect it to be.A Just look at the GNV sources and particularly at vms_crtl_init.c. D For a short introduction of how this works, please read the porting 4 guide at <http://www.oooovms.dyndns.org/reference/>.   Martin Borgman, ( OpenOffice.org On OpenVMS porting group.  <http://www.oooovms.dyndns.org/>   John Malmberg wrote: > Martin Vorlaender wrote: >>H >> And talking about environments, the number of projects I see that useK >> autoconf/automake grows. And adapting those config.h.in files for VMS is 2 >> sometimes just as bad as tweaking the makefile. >>4 >> So, a unixy make is just one piece of the puzzle. > G > The main piece of the puzzle for GNV to generate a config.h for many  2 > projects is getting a current config.guess file. > - > $search config.guess "ia64","vms"/match=and  > J > If you do not see any matches, the config.guess for that package is out K > of date.  Someone seems to have been updating the config.guess files for  G > several of the GNU packages though.  What is curious is that some of  > > them have been updated to know about "alpha-hp-vms" but not < > "ia64-hp-vms".  In most cases, I am seeing "ia64-dec-vms". > B > autoconf requires changes to Perl on VMS so that Perl can spawn J > multi-line bash commands.  Currently Perl on VMS will try to issue them  > as DCL commands. > K > Configure scripts may hang under GNV Bash because they are sending files  J > to the sed editor that are larger than what can be stored completely in H > an OpenVMS MAILBOX.  In some cases this only shows up after the first H > run of Configure because it is validating the config.status file.  In J > that case deleting the config.status file allow the Configure script to L > be re-run.  In other cases, the Configure script will need to be modified. > M > I am anticipating this issue will be fixed in an future version of GNV. :-)  > J > Configure scripts also generally require the following line just before K > they are run to prevent their tests from being attempted as DCL commands.  > ) > bash$ export GNV_DISABLE_DCL_FALLBACK=1  > K > The use of --disable-dependency-tracking as a parameter to the Configure  K > command may also be required for proper generation of the Makefile.  You  K > may also need to use other Configure options to override tests.  Run the  I > Configure script with the "--help" option to get a list of the options. D > Some options are controlled by the export of shell symbols before  > running the script.  > I > Also, the CC/GCC program in GNV will use the current setting of the CC  H > symbol.  The CC symbol may need to be modified so that the C compiler % > will behave more like UNIX expects.  > # > cc :== cc/names=(shortened,as_is)  > K > For simple projects, you can add a "/FIRST_INCLUDE=path:vms_inc_first.h"  K > to that symbol which will allow you to add OpenVMS specific hacks to the  H > programs.  This does not always work, because when the CC/GCC wrapper @ > program gets too complex of a command, it can append it's own  > /FIRST_INCLUDE qualifier.  > : > In the vms_inc_first.h file, you can put such things as: > #define _POSIX_EXIT 1 - > #define _USE_STD_STAT 1 /* V8.2 or later */  > #define _LARGEFILE > C > If you want to use the GNU getopt instead of the one in the CRTL:  >  > /* Hide DECC getopt */G > #include <unistd.h> /* Process the header for the prefixed symbols */  > #define getopt gnu_getopt  > #define optarg gnu_optarg  > #define optopt gnu_optopt  > #define optind gnu_optind  > #define opterr gnu_opterr  > : > #include <string.h> /* Missing from some gnu getopt.c */ >  > E > Unless a UNIX program was written to specifically use OpenVMS exit  J > codes, the _POSIX_EXIT macro should probably be defined.  Bash and some F > newer versions of Perl need this in order to properly interpret the + > non-zero exit codes of spawned processes.  > J > Any program that actually uses "st_ino" values will either need OpenVMS I > specific modifications for before V8.2 or for V8.2 and later will need  E > the _USE_STD_STAT.  _USE_STD_STAT also will set _LARGEFILE.  These  E > macros need to be defined before any standard headers are included.  > J > If the project needs the alloca() function, then in the vms_inc_first.h C > the following is needed for Configure and the program to find it.  >  > #include <builtins.h> # > #define alloca(__x) __alloca(__x)  > I > GCC typically ignores this warning, so unless it is suppressed, it can   > make the builds quite noisy. > & > #pragma message disable ptrmismatch1 > H > And the Configure step may need a different first include header file  > than the build step. > J > If you do not have C++ installed on your system, A configure script may E > be fooled by the C++/G++/CXX programs on your system and insist on  K > trying to use them.  In this case, you may need to rename those programs   > or install the C++ compiler. > K > While this is not a complete answer, hopefully this will help in getting   > some things ported.  >  >  > -John # > malmberg@dskwld.zko.hp.compaq.dec  > Personal Opinion Only    ------------------------------  % Date: Sun, 20 Nov 2005 23:58:10 -0600 / From: Chris Scheers <chris@applied-synergy.com> " Subject: Re: No more SETI on VMS ?2 Message-ID: <438161F2.8020906@applied-synergy.com>   Robert Alan Byer wrote:  > B > I'm currently going over the source code for BOINC and hopefully& > soon will have an OpenVMS port done.  E The BOINC source is available so this is a possibility, but if there  I isn't a SETI client (or some other BOINC client) for VMS, it won't be of  	 much use.   6 Is anyone working on any BOINC project client for VMS?   --  G ----------------------------------------------------------------------- $ Chris Scheers, Applied Synergy, Inc.  B Voice: 817-237-3360            Internet: chris@applied-synergy.com    Fax: 817-237-3074   ------------------------------  % Date: Sun, 20 Nov 2005 14:55:56 -0500 , From: Forrest Kenney <Forrest.Kenney@hp.com>2 Subject: Re: Setting Terminal Line Charcateristics& Message-ID: <4380D4CC.2209043F@hp.com>  D     A couple of things 100 baud is not a legal value for any of the G RS232 controllers on the VAX.  First the possible legal baud rates for   VMS are:   	BAUD_50 	BAUD_75	 	BAUD_110 	 	BAUD_134 	 	BAUD_150 	 	BAUD_300 	 	BAUD_600 
 	BAUD_1200
 	BAUD_1800
 	BAUD_2000
 	BAUD_2400
 	BAUD_3600
 	BAUD_4800
 	BAUD_7200
 	BAUD_9600 	BAUD_19200  	BAUD_38400  	BAUD_57600  	BAUD_76800  	BAUD_115200  7 	Not all serial line controller supported all of these  > speeds.  Also note that in many cases you can ask for one and > not get an error.  The terminal hardware driver knows what is @ legal and all that I know about will silently refuse an illegal @ speed.  The only way to know is to a set and a show to make sure it was accepted.  9 	If you want to force two stop bits you are going to have @ to write a small program to set that.  There is no provision in B set terminal to set the number of stop bits.  Also understand thatA in some cases if you ask for 2 the hardware will not obey that.   C The case that comes to mind is if the character data bits is 5 two  ? stop bits will made into 1.5 by the hardware on some or all of   the controllers.     Forrest Kenney OpenVMS group     ) John.Martin_At_Home@BTInternet.com wrote:  > H > I wish to connect a terminal line from my MicroVax3100 (VMS 7.2) to myH > PDP8i computer its terminal port runs at 100 baud with 2 stop bits. ToI > change the PDP8i to 1 stop bit requires hardware changes which I do not H > want to do as I also use it with a ASR33 Teletype which requires the 2D > stop bits.  I have built an interface that converts the PDP8i 20mAI > current loop to/from RS232. I know my interface is good as it all works G > connected to a PC where it is a simple matter to specify 2 stop bits.  > F > The Set Terminal command will let me set the baud speed but how do IH > set the 2 Stop Bits. I have successfully connected my PDP8e to the Vax > but this expects 1 stop bit. >   > Any help would be appreciated. >  > John   ------------------------------  % Date: Sun, 20 Nov 2005 17:06:07 -0500  From: Bob Hassinger <x@y.z> 2 Subject: Re: Setting Terminal Line Charcateristics" Message-ID: <4380F34F.5090804@y.z>  ) John.Martin_At_Home@BTInternet.com wrote:   H > I wish to connect a terminal line from my MicroVax3100 (VMS 7.2) to my3 > PDP8i computer its terminal port runs at 100 baud   I The standard PDP-8/I current loop interface ran/runs at 110 baud.  If it  G is the standard hardware, and if it is operating with a standard ASR33  9 then it is highly likely you are looking at the 110 baud.      with 2 stop bits. ToI > change the PDP8i to 1 stop bit requires hardware changes which I do not H > want to do as I also use it with a ASR33 Teletype which requires the 2D > stop bits.  I have built an interface that converts the PDP8i 20mA > current loop to/from RS232.    I built one too - in 1968.  + I know my interface is good as it all works G > connected to a PC where it is a simple matter to specify 2 stop bits.  > F > The Set Terminal command will let me set the baud speed but how do IH > set the 2 Stop Bits. I have successfully connected my PDP8e to the Vax > but this expects 1 stop bit. >   > Any help would be appreciated.  H Are you sure you need to worry about the two stop bits?  The VAX is not E going to care that you are sending two stop bits toward it (there is  2 just a bit time of no data between each character.  H Have you determined that is does not work if you only send one stop bit D towards the 8/I?  Its been more than 35 years since I looked at the F schematic for that interface, but there is a good it may be satisfied  with one stop bit too.    
 Bob Hassinger    >  > John >    ------------------------------  # Date: Mon, 21 Nov 2005 03:19:27 GMT   From: John Santos <john@egh.com>2 Subject: Re: Setting Terminal Line Charcateristics) Message-ID: <31bgf.3072$Vu2.624@trnddc06>    Bob Hassinger wrote:+ > John.Martin_At_Home@BTInternet.com wrote:  > I >> I wish to connect a terminal line from my MicroVax3100 (VMS 7.2) to my 4 >> PDP8i computer its terminal port runs at 100 baud >  > K > The standard PDP-8/I current loop interface ran/runs at 110 baud.  If it  I > is the standard hardware, and if it is operating with a standard ASR33  ; > then it is highly likely you are looking at the 110 baud.  >  >  with 2 stop bits. To  > J >> change the PDP8i to 1 stop bit requires hardware changes which I do notI >> want to do as I also use it with a ASR33 Teletype which requires the 2 E >> stop bits.  I have built an interface that converts the PDP8i 20mA  >> current loop to/from RS232.   >  >  > I built one too - in 1968. > - > I know my interface is good as it all works  > H >> connected to a PC where it is a simple matter to specify 2 stop bits. >>G >> The Set Terminal command will let me set the baud speed but how do I I >> set the 2 Stop Bits. I have successfully connected my PDP8e to the Vax  >> but this expects 1 stop bit.  >>! >> Any help would be appreciated.  >  > J > Are you sure you need to worry about the two stop bits?  The VAX is not G > going to care that you are sending two stop bits toward it (there is  4 > just a bit time of no data between each character. > J > Have you determined that is does not work if you only send one stop bit F > towards the 8/I?  Its been more than 35 years since I looked at the H > schematic for that interface, but there is a good it may be satisfied  > with one stop bit too.  F It might be possible to play games with the character size.  IIRC, theH line idles a 1, and the start and stop bits are 0's.  (Could easily haveF that backwards.)  To get 2 stop bits, it may be possible to either setG the character size 1 bit larger (8 bits, no parity) and always send a 0 G as the eighth bit, or set it 7 bits, space parity.  If the stop bit has D to be a 1, then 7 bits, mark parity, or 8 bits and filter the outputD to force the 8th bit to a 1.  C-Kermit can do this (according to itsF help), though I don't know if it works on VMS.  See SET PARITY and SET SERIAL in C-Kermit.   A IIRC, the standard teletype setting was 7 bits, no parity, 2 stop B bits.  The low bit is sent first.  So the PDP-8 should see the 8thF data bit (or the parity bit if parity is enabled, when it is expectingB the 1st stop bit, so all you need to do to fake it out is send theB right bit (0 or 1, depending on what stop bits are supposed to be)@ as the parity bit (i.e. Space parity) or as the eighth data bit.  B It is also possible you don't need to do anything at all....  I'veD seen many terminals and terminal interfaces that automatically set 2G stop bits if the baud rate is 110 or below (and 1.5 stop bits for 150?) > Maybe VMS does this and it has been lost in the mists of time.     > Bob Hassinger  >  >> >> John  >>     --   John Santos  Evans Griffiths & Hart, Inc. 781-861-0670 ext 539   ------------------------------   End of INFO-VAX 2005.649 ************************