INFO-VAX Thu, 31 May 2007 Volume 2007 : Issue 295 Contents: Re: DS10L ATI 7500 PCI Graphics Problems Re: DS10L ATI 7500 PCI Graphics Problems GRUB master boot record Re: GRUB master boot record Re: HP wasting millions of dollars on itanium! Re: HP wasting millions of dollars on itanium! Re: HP wasting millions of dollars on itanium! Re: HP wasting millions of dollars on itanium! Re: Looking for a H7868 power supply OpenVMS on AlphaPC Re: OpenVMS on AlphaPC Re: OpenVMS on AlphaPC Re: PCSI, disk space, UNDO, unseen dangers etc Re: PCSI, disk space, UNDO, unseen dangers etc Re: PCSI, disk space, UNDO, unseen dangers etc Re: PCSI, disk space, UNDO, unseen dangers etc Re: RDB Tutorial Remote Shadow... Re: Remote Shadow... Re: SSH port scanners Re: SSH port scanners Upgrade to Vista from XP ? Yes or No Re: Upgrade to Vista from XP ? Yes or No Re: Upgrade to Vista from XP ? Yes or No VMS L&T Distribution [OT] (kinda) HP, parts ain't parts; KVM internal power supply Re: [OT] (kinda) HP, parts ain't parts; KVM internal power supply ---------------------------------------------------------------------- Date: Wed, 30 May 2007 19:46:30 -0500 From: "Craig A. Berry" Subject: Re: DS10L ATI 7500 PCI Graphics Problems Message-ID: In article , "FredK" wrote: > "Vance Haemmerle" wrote in message > news:465B95CF.5040500@toyvax.Glendale.CA.US... > > FredK wrote: > > > > > All of Apple's Cinema Display 20" and iMac 20" and last 17" PowerBook G4 > > and 17" MacBook Pros are 1680x1050. > > Consumer electronics, odd numbers. > > In any case, the VMS tabled are setup for 1600x1200 > > If you can pass me along the modeline from a Linux/xFree86 system for the > panels, I'll look at adding them. > > I can generate a modeline like: > > "1600x1050_60.00" 139.83 1600 1704 1872 2144 1050 1051 1054 1087 -HSync > +Vsync > or > > "1680x1050_60.00" 147.14 1680 1784 1968 2256 1050 1051 1054 1087 -HSync > +Vsync > > But those are just CVT suggested timings. > > I am considering adding a mechanism to allow a user to load a custom entry > (that is, the modeline idea from xFree86) - but with a big warning that you > can fry your monitor by plugging in bogus values. The one at gives me: Modeline "1680x1050@60" 154.20 1680 1712 2296 2328 1050 1071 1081 1103 and the one at gives me: # V-freq: 60.00 Hz // h-freq: 65.35 KHz Modeline "1680x1050" 149.00 1680 1760 1944 2280 1050 1050 1052 1089 and the one at gives me: ModeLine "1680x1050" 199.18 1680 1752 2112 2256 1050 1052 1064 1090 #81Hz I speciified 60Hz where that option was available. I will try it with a Linux system tomorrow. -- Posted via a free Usenet account from http://www.teranews.com ------------------------------ Date: Wed, 30 May 2007 21:20:43 -0400 From: "FredK" Subject: Re: DS10L ATI 7500 PCI Graphics Problems Message-ID: "Craig A. Berry" wrote in message news:craigberry-7E7F32.19463030052007@free.teranews.com... > In article , > "FredK" wrote: > >> "Vance Haemmerle" wrote in message >> news:465B95CF.5040500@toyvax.Glendale.CA.US... >> > FredK wrote: >> >> > >> > All of Apple's Cinema Display 20" and iMac 20" and last 17" PowerBook >> > G4 >> > and 17" MacBook Pros are 1680x1050. >> >> Consumer electronics, odd numbers. >> >> In any case, the VMS tabled are setup for 1600x1200 >> >> If you can pass me along the modeline from a Linux/xFree86 system for the >> panels, I'll look at adding them. >> >> I can generate a modeline like: >> >> "1600x1050_60.00" 139.83 1600 1704 1872 2144 1050 1051 1054 1087 -HSync >> +Vsync >> or >> >> "1680x1050_60.00" 147.14 1680 1784 1968 2256 1050 1051 1054 1087 -HSync >> +Vsync >> >> But those are just CVT suggested timings. >> >> I am considering adding a mechanism to allow a user to load a custom >> entry >> (that is, the modeline idea from xFree86) - but with a big warning that >> you >> can fry your monitor by plugging in bogus values. > > The one at gives me: > > Modeline "1680x1050@60" 154.20 1680 1712 2296 2328 1050 1071 1081 1103 > > and the one at gives me: > > > # V-freq: 60.00 Hz // h-freq: 65.35 KHz > Modeline "1680x1050" 149.00 1680 1760 1944 2280 1050 1050 1052 1089 > > and the one at gives > me: > > ModeLine "1680x1050" 199.18 1680 1752 2112 2256 1050 1052 1064 1090 #81Hz > > I speciified 60Hz where that option was available. I will try it with a > Linux system tomorrow. > Right. That is why I asked. The numbers I showed was from GTF.C from sourceforge. Timing parameters can vary quite a bit depending on the "other" parameters like sync timing and margins. On flat panels you don't need as much sync (front and back porch etc) time. So often you will find a timing that someone has worked out "just" for the specific monitor that works the best. 1680x1050 isn't a standard VESA resolution - so CVT, GTF, or or other timing generators come up with different computed values. ------------------------------ Date: 30 May 2007 13:46:27 -0700 From: Navid Shakibapour Subject: GRUB master boot record Message-ID: <1180557987.689064.223370@p47g2000hsd.googlegroups.com> Like the Boot Records of an OS, the first three bytes could be called the Jump Instruction. But only the first two bytes are being used to form the actual JMP (Jump) instruction to the rest of the executable code; the third byte (90h) is just a NOP instruction ('No Op' do nothing). So the execution jumps over the 71 next bytes which can be thought of as a BIOS Parameter Block (or BPB); BIOS parameter block (BPB) is a description of the physical medium (hard disk or floppy) that might be stored in a file system=E2=80=99s Volume Boot Record. File systems with a BIOS parameter block include FAT16, FAT32, HPFS, and NTFS. ECMA-107 or ISO/IEC 9293 (which describes FAT as for flexible/floppy and optic distal disk cartridges) also describes this as an FDC Descriptor or an FDC Extended Descriptor. 00000000 EB48 jmp short 0x4a 00000002 90 nop Jump to the start of the program at 0x7c00 and is jumped to with CS:IP 0:0x7c00. Jump over BPB data area to main body of code. This BPB Data Area (BIOS Parameter Block) is filled with useful data for any program examining it as a normal Volume Boot Record. The BYTES in the BPB which are referenced in the code below are: [00000005] -> 8E D0 BC 00 B0 B8 00 00 8E D8 8E C0 FB BE ("Disk Address Packet" for LBA mode.) [00000040] -> 80 ("Boot Drive") NOTE: For those of you with multi- OS booting systems, if your Linux installation with GRUB's remaining software (stage2, menu file, etc.) is located somewhere other than on the Primary Master drive, this value will be 81, 82, etc. depending upon which drive that Linux OS's /boot/grub directory is located. [00000041] -> 00 ("Force LBA mode byte") [00000042] -> 00 80 (8000h) Memory location where GRUB stores the next stage of the code to execute. [00000044] -> Note: A very important location for anyone using GRUB! This (4-byte) Quad-Word contains the location of GRUB's stage2 file in sectors! You will always see the bytes 01 00 00 00 in this location whenever GRUB has been installed in the first track (Sectors 1 ff.) of an HDD; immediately following the GRUB MBR in Absolute Sector 0. [00000048] -> 00 08 (800h) [Don't confuse this with the 8000 at 00000042.] 00000003 10 00000004 8E 00000005 D0 00000006 BC 00000007 00 00000008 B0 00000009 B8 0000000A 00 0000000B 00 0000000C 8E 0000000D D8 0000000E 8E 0000000F C0 00000010 FB 00000011 BE 00000012 00 00000013 7C 00000014 BF 00000015 00 00000016 06 00000017 B9 00000018 00 00000019 02 0000001A F3 0000001B A4 0000001C EA 0000001D 21 0000001E 06 0000001F 00 00000020 00 00000021 BE 00000022 BE 00000023 07 00000024 38 00000025 04 00000026 75 00000027 0B 00000028 83 00000029 C6 0000002A 10 0000002B 81 0000002C FE 0000002D FE 0000002E 07 0000002F 75 00000030 F3 00000031 EB 00000032 16 00000033 B4 00000034 02 00000035 B0 00000036 01 00000037 BB 00000038 00 00000039 7C 0000003A B2 0000003B 80 0000003C 8A 0000003D 74 0000003E 03 0000003F 02 00000040 80 00000041 00 00000042 00 00000043 80 00000044 8B 00000045 82 00000046 00 00000047 00 00000048 00 00000049 08 General setup: 0000004A FA cli This line will Clear Interrupt Flag This is a workaround for buggy BIOSes which don't pass boot drive correctly. If GRUB is installed into a HDD, check if DL is masked correctly. If not, assume that the BIOS passed a bogus value and set DL to 0x80, since this is the only possible boot drive. If GRUB is installed into a floppy, this does nothing (only jump). 0000004B EA507C0000 jmp 0x0:0x7c50 Long Jump to the next instruction because some bogus BIOSes jump to 07C0:0000 instead of 0000:7C00. 00000050 31C0 xor ax,ax 00000052 8ED8 mov ds,ax 00000054 8ED0 mov ss,ax set up %ds and %ss as offset from 0 00000056 BC0020 mov sp,0x2000 set up the REAL stack 00000059 FB sti Set Interrupt Flag This instruction sets the interrupt flag (IF) in the EFLAGS register. After the IF flag is set, the processor begins responding to external, mask able interrupts after the next instruction is executed. 0000005A A0407C mov al,[0x7c40] <<<<<<<< Boot Drive Check if we have a forced disk reference here 0000005D 3CFF cmp al,0xff Compare GRUB_INVALID_DRIVE and al 0000005F 7402 jz 0x63 jump to the next instruction because some bogus BIOSes jump to 07C0:0000 instead of 0000:7C00. 00000061 88C2 mov dl,al 00000063 52 push dx Save drive reference first thing! 00000064 BE767D mov si,0x7d76 00000067 E83401 call 0x19e Print a notification message on the screen. The first line =E2=80=9C0x7d76=E2=80=9D is the place of the string =E2=80= =9CGRUB=E2=80=9D on memory. =E2=80=9C0x19e=E2=80=9D is the place of the function that print the message= on screen that have the following code in GRUB stage1.s code: lodsb cmpb $0, %al jne 1b /* if not end of string, jmp to display */ ret 0000006A F6C280 test dl,0x80 do not probe LBA if the drive is a floppy 0x80 is STAGE1_BIOS_HD_FLAG that explained before. 0000006D 7454 jz 0xc3 Jump to the =E2=80=9C0xc3=E2=80=9D on the memory if zero flag is set and th= at named =E2=80=9Cchs_mode=E2=80=9D and it determine the hard disk geometry from th= e BIOS! If it happened first, so that LS-120 IDE floppies work correctly. 0000006F B441 mov ah,0x41 Function 41h of INT13 00000071 BBAA55 mov bx,0x55aa 00000074 CD13 int 0x13 Test for INT13 Extensions Check if LBA is supported %dl may have been clobbered by INT 13, AH=3D41H. This happens, for example, with AST BIOS 1.04. 00000076 5A pop dx 00000077 52 push dx 00000078 7249 jc 0xc3 0000007A 81FB55AA cmp bx,0xaa55 0000007E 7543 jnz 0xc3 Use CHS if fails =E2=80=9C0xc3=E2=80=9D is the place of memory whit label =E2=80=9Cchs_mode= =E2=80=9D that I explained before and will explain more in end of this paper. 00000080 A0417C mov al,[0x7c41] <<<< Force LBA mode byte 00000083 84C0 test al,al check if AH=3D0x42 is supported if FORCE_LBA is zero 00000085 7505 jnz 0x8c Jump if =E2=80=9Clba_mode=E2=80=9D 00000087 83E101 and cx,byte +0x1 0000008A 7437 jz 0xc3 0000008C 668B4C10 mov ecx,[si+0x10] Save the total number of sectors 00000090 BE057C mov si,0x7c05 Set %si to the disk address packet 00000093 C644FF01 mov byte [si-0x1],0x1 Set the mode to non-zero 00000097 668B1E447C mov ebx,[0x7c44] 0000009C C7041000 mov word [si],0x10 The size and the reserved byte 000000A0 C744020100 mov word [si+0x2],0x1 The blocks 000000A5 66895C08 mov [si+0x8],ebx The absolute address (low 32 bits) 000000A9 C744060070 mov word [si+0x6],0x7000 =E2=80=9C0x7000=E2=80=9D is the segment of buffer address 000000AE 6631C0 xor eax,eax 000000B1 894404 mov [si+0x4],ax 000000B4 6689440C mov [si+0xc],eax 000000B8 B442 mov ah,0x42 000000BA CD13 int 0x13 BIOS call "INT 0x13 Function 0x42" to read sectors from disk into memory Call with %ah =3D 0x42 %dl =3D drive number %ds:%si =3D segment : offset of disk address packet Return: %al =3D 0x0 on success; err code on failure 000000BC 7205 jc 0xc3 LBA read is not supported, so fallback to CHS. 000000BE BB0070 mov bx,0x7000 =E2=80=9C0x7000=E2=80=9D is STAGE1_BUFFERSEG 000000C1 EB7D jmp short 0x140 =E2=80=9C0x140=E2=80=9D is copy_buffer The code below is =E2=80=9Cchs_mode=E2=80=9D that I explained a little befo= re. Determine the hard disk geometry from the BIOS! We do this first, so that LS-120 IDE floppies work correctly. 000000C3 B408 mov ah,0x8 Function 08 of INT13 000000C5 CD13 int 0x13 Get Drive Parameters 000000C7 730A jnc 0xd3 The call failed, so maybe use the floppy probe instead. =E2=80=9C0xd3=E2=80=9D is the place of label final_init The call failed, so maybe use the floppy probe instead. 000000C9 F6C280 test dl,0x80 =E2=80=9C0x80=E2=80=9D is a value of STAGE1_BIOS_HD_FLAG 000000CC 0F84F300 jz near 0x1c3 =E2=80=9C0x1c3=E2=80=9D is a label whit name: floppy_probe that I will show= the implantation further. Nope, we definitely have a hard disk, and we're screwed. 000000D0 E98D00 jmp 0x160 Hard disk error =EF=83=A0 hd_probe_error 000000D3 BE057C mov si,0x7c05 000000D6 C644FF00 mov byte [si-0x1],0x0 set the mode to zero 000000DA 6631C0 xor eax,eax 000000DD 88F0 mov al,dh save number of heads the following code is for final initialize: 000000DF 40 inc ax 000000E0 66894404 mov [si+0x4],eax save number of cylinders 000000E4 31D2 xor dx,dx 000000E6 88CA mov dl,cl 000000E8 C1E202 shl dx,0x2 000000EB 88E8 mov al,ch 000000ED 88F4 mov ah,dh 000000EF 40 inc ax 000000F0 894408 mov [si+0x8],ax 000000F3 31C0 xor ax,ax 000000F5 88D0 mov al,dl 000000F7 C0E802 shr al,0x2 000000FA 668904 mov [si],eax save number of sectors the following code is for setup sectors: 000000FD 66A1447C mov eax,[0x7c44] load logical sector start (bottom half) 00000101 6631D2 xor edx,edx zero %edx 00000104 66F734 div dword [si] divide by number of sectors 00000107 88540A mov [si+0xa],dl save sector start 0000010A 6631D2 xor edx,edx Zero %edx 0000010D 66F77404 div dword [si+0x4] divide by number of heads 00000111 88540B mov [si+0xb],dl save head start 00000114 89440C mov [si+0xc],ax save cylinder start 00000117 3B4408 cmp ax,[si+0x8] 0000011A 7D3C jnl 0x158 =E2=80=9C0x158=E2=80=9D is a label with this name geometry_error do we need too many cylinders? This is the loop for taking care of BIOS geometry translation (ugh!) 0000011C 8A540D mov dl,[si+0xd] get high bits of cylinder 0000011F C0E206 shl dl,0x6 shift left by 6 bits 00000122 8A4C0A mov cl,[si+0xa] get sector 00000125 FEC1 inc cl normalize sector (sectors go from 1-N, not 0-(N-1) ) 00000127 08D1 or cl,dl composite together 00000129 8A6C0C mov ch,[si+0xc] sector+hcyl in cl, cylinder in ch 0000012C 5A pop dx restore %dx 0000012D 8A740B mov dh,[si+0xb] Head number BIOS call "INT 0x13 Function 0x2" to read sectors from disk into memory Call with %ah =3D 0x2 %al =3D number of sectors %ch =3D cylinder %cl =3D sector (bits 6-7 are high bits of "cylinder") %dh =3D head %dl =3D drive (0x80 for hard disk, 0x0 for floppy disk) %es:%bx =3D segment:offset of buffer Return: %al =3D 0x0 on success; err code on failure 00000130 BB0070 mov bx,0x7000 =E2=80=9C0x7000=E2=80=9D is STAGE1_BUFFERSEG 00000133 8EC3 mov es,bx load %es segment with disk buffer 00000135 31DB xor bx,bx %bx =3D 0, put it at 0 in the segment 00000137 B80102 mov ax,0x201 0000013A CD13 int 0x13 function 2 of int13 0000013C 722A jc 0x168 =E2=80=9C0x168=E2=80=9D is labeb with this name: read_error 0000013E 8CC3 mov bx,es The following code is for copy buffer: 00000140 8E06487C mov es,[0x7c48] We need to save %cx and %si because the startup code in stage2 uses them without initializing them. 00000144 60 pusha 00000145 1E push ds 00000146 B90001 mov cx,0x100 00000149 8EDB mov ds,bx 0000014B 31F6 xor si,si 0000014D 31FF xor di,di 0000014F FC cld 00000150 F3A5 rep movsw 00000152 1F pop ds 00000153 61 popa 00000154 FF26427C jmp near [0x7c42] WORD <<< 8000 hex. boot stage2 This is where we jump to the next stage of the code which GRUB loaded from the HDD into Memory locations 0000:8000 hex and following: END OF MAIN LOOP Section for Displaying Error Messages: BIOS Geometry translation error (past the end of the disk geometry!). The following code is for geometry_error: 00000158 BE7C7D mov si,0x7d7c --"Geom Error" 0000015B E84000 call 0x19e -- Display it on screen. 0000015E EB0E jmp short 0x16e -- Finish it and 'lock- up' Jump to the label =E2=80=9Cgeneral_error=E2=80=9D The following code is for hd_probe_error: Disk probe failure 00000160 BE817D mov si,0x7d81 -- "Hard Disk Error" 00000163 E83800 call 0x19e -- Display it on screen. 00000166 EB06 jmp short 0x16e -- Finish it and 'lock-up' Read error on the disk: read_error: 00000168 BE8B7D mov si,0x7d8b -- "Read Error" 0000016B E83000 call 0x19e -- Display it on screen general_error: 0000016E BE907D mov si,0x7d90 -- (For displaying " Error") 00000171 E82A00 call 0x19e -- Display it on screen stop: 00000174 EBFE jmp short 0x174 go here when you need to stop the machine hard after an error condition Location of the GRUB ID String Define string =E2=80=9CGRUB =E2=80=9D : 00000176 47 00000177 52 00000178 55 00000179 42 0000017A 20 0000017B 00 Define string =E2=80=9CGeom=E2=80=9D : 0000017C 47 0000017D 65 0000017E 6F 0000017F 6D 00000180 00 Define string =E2=80=9CHard Disk=E2=80=9D: 00000181 48 00000182 61 00000183 72 00000184 64 00000185 20 00000186 44 00000187 69 00000188 73 00000189 6B 0000018A 00 Define string =E2=80=9CRead=E2=80=9D: 0000018B 52 0000018C 65 0000018D 61 0000018E 64 0000018F 00 Define string =E2=80=9C Error=E2=80=9D: 00000190 20 00000191 45 00000192 72 00000193 72 00000194 6F 00000195 72 00000196 00 Display Character Subroutine: 00000197 BB0100 mov bx,0x1 0000019A B40E mov ah,0xe Function 0Eh of INT10 0000019C CD10 int 0x10 Display the character 0000019E AC lodsb 0000019F 3C00 cmp al,0x0 000001A1 75F4 jnz 0x197 if not end of string, jmp to display 000001A3 C3 ret 000001A4 00 000001A5 00 000001A6 00 000001A7 00 000001A8 00 000001A9 00 000001AA 00 000001A8 00 000001AC 00 000001AD 00 000001AE 00 000001AF 00 000001B0 00 000001B1 00 000001B2 00 000001B3 00 000001B4 00 000001B5 00 000001B6 00 000001B7 00 Finally, GRUB makes sure not to use any of the bytes between offsets 1B8h and 1BBh because they're used by Microsoft=C2=AE Windows=E2=84=A2 NT/2= 000/XP/ 2003 as the NT Drive Serial Number; which in our example above is the four-byte WORD 00000000h. 000001B8 00 000001B9 00 000001BA 00 000001BB 00 000001BC 00 000001BD 00 Partition Table in Memory: Although GRUB is a Boot Manager, its stage1 code follows the structure of all MBRs by placing the standard four-entry Partition Table in its agreed upon location (offsets 01BEh through 01FDh) which is followed by the standard Word-sized signature ID of AA55h. 000001BE 80 000001BF 01 000001C0 01 000001C1 00 000001C2 83 000001C3 FE 000001C4 3F 000001C5 0C 000001C6 3F 000001C7 00 000001C8 00 000001C9 00 000001CA 8E 000001CB 2F 000001CC 03 000001CD 00 000001CE 00 000001CF 00 000001D0 01 000001D1 0D 000001D2 83 000001D3 FE 000001D4 BF 000001D5 DE 000001D6 CD 000001D7 2F 000001D8 03 000001D9 00 000001DA 52 000001DB FC 000001DC B0 000001Dd 00 000001DE 00 000001DF 00 000001E0 81 000001E1 DF 000001E2 82 000001E3 FE 000001E4 FF 000001E5 0E 000001E6 1F 000001E7 2C 000001E8 B4 000001E9 00 000001EA 30 000001EB C4 000001EC 0B 000001ED 00 000001EE 00 000001EF 00 000001F0 00 000001E1 00 000001F2 00 000001F3 00 000001F4 00 000001F5 00 000001F6 00 000001F7 00 000001F8 00 000001F9 00 000001FA 00 000001FB 00 000001FC 00 000001FD 00 000001FE 55 000001FF AA ------------------------------ Date: Wed, 30 May 2007 21:30:04 -0400 From: "FredK" Subject: Re: GRUB master boot record Message-ID: Ah... what the heck is this talking about? Did you post this to the wrong newsgroup? "Navid Shakibapour" wrote in message news:1180557987.689064.223370@p47g2000hsd.googlegroups.com... Like the Boot Records of an OS, the first three bytes could be called the Jump Instruction. But only the first two bytes are being used to form the actual JMP (Jump) ... ------------------------------ Date: Wed, 30 May 2007 14:48:09 -0400 From: JF Mezei Subject: Re: HP wasting millions of dollars on itanium! Message-ID: <1e709$465dc710$cef8887a$31489@TEKSAVVY.COM> Bob Koehler wrote: > > "immediately shift to EV8"? How do you "immediately" shift to > something that doesn't exist? OK, for the sake of discussion, lets assume both HP and Intel admitted today that IA64 was a mistake. Both decide to focus on Alpha and HP gives Intel the rights to build and improve/designs new alphas. How long would it take to take current EV7 and produce a new EV7 made with smaller process and higher speed ? (same logic inside) and perhaps larger cache ? With Intel's resources, would it be months, a year ? 2 years ? Couldn't they give EV7 a speed boost each year until Intel then comes up with EV9 (lets skip EV8 and go to EV9 with whatever techniques have been learned/developped since 2001). (I realise that from a political point of view, this is unfortunatly ot likely to happen, but from a technical point of view, couldn't they ramp up EV7 production and EV7 speed bumps rather quickly ? ------------------------------ Date: Wed, 30 May 2007 13:52:30 -0500 From: Ron Johnson Subject: Re: HP wasting millions of dollars on itanium! Message-ID: On 05/30/07 13:48, JF Mezei wrote: > Bob Koehler wrote: >> >> "immediately shift to EV8"? How do you "immediately" shift to >> something that doesn't exist? > > > OK, for the sake of discussion, lets assume both HP and Intel admitted > today that IA64 was a mistake. Both decide to focus on Alpha and HP > gives Intel the rights to build and improve/designs new alphas. > > How long would it take to take current EV7 and produce a new EV7 made > with smaller process and higher speed ? (same logic inside) and perhaps > larger cache ? > > With Intel's resources, would it be months, a year ? 2 years ? > Couldn't they give EV7 a speed boost each year until Intel then comes up > with EV9 (lets skip EV8 and go to EV9 with whatever techniques have been > learned/developped since 2001). *Would* Intel even do it? They've now got Core2 Duo, Penryn, etc. -- Ron Johnson, Jr. Jefferson LA USA Give a man a fish, and he eats for a day. Hit him with a fish, and he goes away for good! ------------------------------ Date: 30 May 2007 11:57:40 -0700 From: ultradwc@gmail.com Subject: Re: HP wasting millions of dollars on itanium! Message-ID: <1180551460.372506.269550@g4g2000hsf.googlegroups.com> On May 30, 11:47 am, p...@langstoeger.at (Peter 'EPLAN' LANGSTOeGER) wrote: > In article <1180534238.711964.84...@p77g2000hsh.googlegroups.com>, ultra...@gmail.com writes: > >which will never catch power. when it still has alpha and can immediately > >shift to EV8 and get back on the right track ... where are the shareholders > >at? They should be steaming! > > Come on Bob, you know that the engineer left some years ago. So "immediately" > isn't in the game now (and they would also need years to complete EV8 then) > > Yes, the shareholders should have been in action (but for a long time now). > And, alas, they are not, so the train will continue heading the wall... > > Sigh > (and repeating the obvious doesn't make us less sorrow/angry) > > -- > Peter "EPLAN" LANGSTOEGER > Network and OpenVMS system specialist > E-mail p...@langstoeger.at > A-1030 VIENNA AUSTRIA I'm not a pessimist, I'm a realist hire them back! ------------------------------ Date: 30 May 2007 13:06:19 -0700 From: Doug Phillips Subject: Re: HP wasting millions of dollars on itanium! Message-ID: <1180555579.601438.66630@g4g2000hsf.googlegroups.com> On May 30, 1:52 pm, Ron Johnson wrote: > On 05/30/07 13:48, JF Mezei wrote: > > Bob Koehler wrote: > >> "immediately shift to EV8"? How do you "immediately" shift to > >> something that doesn't exist? > > > With Intel's resources, would it be months, a year ? 2 years ? > > Couldn't they give EV7 a speed boost each year until Intel then comes up > > with EV9 (lets skip EV8 and go to EV9 with whatever techniques have been > > learned/developped since 2001). > > *Would* Intel even do it? They've now got Core2 Duo, Penryn, etc. > Right. Why would they even consider it? The Penryn road map shows 45nm 2007, 32nm 2009 and 22nm 2011. The scuttlebutt about the Larrabee many-core project seems to point to IA with x86 (but I'd like to know if Bill Todd and our other chip gurus have heard more.) Looks like Larrabee will be released as a GPU first, but apparently many variations are planned for different applications. IBM is teamed with AMD on the x86 front, and you can bet that team isn't exactly standing still, either. High-End products are often used as proving grounds for new technology. If that paradigm continues, we can expect to see new high- end designs (like Power & IA) as long as there's someone willing to buy them. ------------------------------ Date: Wed, 30 May 2007 12:57:13 -0500 From: "P. Thompson" Subject: Re: Looking for a H7868 power supply Message-ID: This is used in BA215 QBUS style boxes. MicroVAX 3x00, DECsystem 5400, DECserver 5x0, R215F DSSI pedestal, et al On Wed, 30 May 2007, David Turner, Island Computers wrote: > What is this used in? > Vax something or other? > > DT > wrote in message > news:1180340609.043141.142600@n15g2000prd.googlegroups.com... >> If anybody has a spare laying around and wants to sell the item let me >> know. >> tks >> phil >> ------------------------------ Date: Thu, 31 May 2007 00:43:55 +0200 From: |a|i|e|i|e| Subject: OpenVMS on AlphaPC Message-ID: <465dfe1b$0$17947$4fafbaef@reader1.news.tin.it> Hi all, I have an AlphaPC, and i would install openvms. I installed SRM 5.8 I think that the first problem is the scsi adapter (adaptec now, not supported), and i don't know if the qlogic 1020/1040 is ok. The video card a Diamond FireGL So, can i hope to install vms on it? Any suggest? thanks for all. (I can continue using vms on my 4000vlc) ------------------------------ Date: Wed, 30 May 2007 19:02:52 -0500 (CDT) From: sms@antinode.org (Steven M. Schweda) Subject: Re: OpenVMS on AlphaPC Message-ID: <07053019025190_202002DA@antinode.org> From: |a|i|e|i|e| > I have an AlphaPC, and i would install openvms. I know approximately nothing about an AlphaPC. > I installed SRM 5.8 Sounds like a good start. > I think that the first problem is the scsi adapter (adaptec now, not > supported), and i don't know if the qlogic 1020/1040 is ok. Should be. I've used a generic Qlogic card with an ISP1040B chip in my AlphaStation 200 4/233 (and probably in my Digital Personal Workstation 500a[u]), but if you can find one which says "Digital Equipment Corp. KZPBA-CX" on the back, you might be safer. > The video card a Diamond FireGL Probably won't work for DECwindows. > So, can i hope to install vms on it? You may need a SCSI CD-ROM drive. (I assume that you were planning on a SCSI system disk.) ------------------------------------------------------------------------ Steven M. Schweda sms@antinode-org 382 South Warwick Street (+1) 651-699-9818 Saint Paul MN 55105-2547 ------------------------------ Date: Wed, 30 May 2007 20:54:11 -0400 From: "Richard B. Gilbert" Subject: Re: OpenVMS on AlphaPC Message-ID: <465E1CB3.4000707@comcast.net> |a|i|e|i|e| wrote: > Hi all, > > I have an AlphaPC, and i would install openvms. > I installed SRM 5.8 > > I think that the first problem is the scsi adapter (adaptec now, not > supported), and i don't know if the qlogic 1020/1040 is ok. > The video card a Diamond FireGL > > So, can i hope to install vms on it? > > Any suggest? > > thanks for all. > > > (I can continue using vms on my 4000vlc) > The fastest way to get an answer may be to try it. Qlogic SCSI may make several 1020/1040 SCSI HBA's. You may need to be sure you get the ones with DEC firmware. IF the SPD for the version of VMS you intend to install doesn't list something as "supported" you are on your own; it may work or it may not and, if it doesn't work you'll find sympathy in the dictionary. ------------------------------ Date: 30 May 2007 11:28:12 -0700 From: "george.pagliarulo@hp.com" Subject: Re: PCSI, disk space, UNDO, unseen dangers etc Message-ID: <1180549692.337203.57560@i13g2000prf.googlegroups.com> On May 29, 5:21 am, hel...@astro.multiCLOTHESvax.de (Phillip Helbig--- remove CLOTHES to reply) wrote: > In article <1180429907.973154.94...@k79g2000hse.googlegroups.com>, > > IanMiller writes: > > See > > $ HELP PRODUCT DELETE RECOVERY_DATA > > That's it, thanks. What is the relation between patches and the > PCSI$UNDO directories? It's not one-to-one since my patch action > yesterday modified some older directories. (I don't know what it's > doing under the hood.) In other words, does a "recovery-data set" refer > to a patch or to a PCSI$UNDO directory? Each time you install a patch kit (patch, not product) PCSI creates an UNDO directory for that kit. The UNDO directory for the latest patch kit installed is always number one. Therefore, everytime you install a patch kit PCSI has to go through and re-number all the existing UNDO directories to make room for the newest one. George Pagliarulo ECO Release Process OpenVMS Sustaining Engineering ------------------------------ Date: Wed, 30 May 2007 22:16:26 +0000 (UTC) From: helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply) Subject: Re: PCSI, disk space, UNDO, unseen dangers etc Message-ID: In article <1180549692.337203.57560@i13g2000prf.googlegroups.com>, "george.pagliarulo@hp.com" writes: > Each time you install a patch kit (patch, not product) PCSI creates an > UNDO directory for that kit. The UNDO directory for the latest patch > kit installed is always number one. Therefore, everytime you install > a patch kit PCSI has to go through and re-number all the existing UNDO > directories to make room for the newest one. OK. Isn't renaming directories officially unsupported, though? :-) ------------------------------ Date: Wed, 30 May 2007 22:19:51 +0000 (UTC) From: helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply) Subject: Re: PCSI, disk space, UNDO, unseen dangers etc Message-ID: In article <1180549692.337203.57560@i13g2000prf.googlegroups.com>, "george.pagliarulo@hp.com" writes: > Each time you install a patch kit (patch, not product) PCSI creates an > UNDO directory for that kit. The UNDO directory for the latest patch > kit installed is always number one. Therefore, everytime you install > a patch kit PCSI has to go through and re-number all the existing UNDO > directories to make room for the newest one. /BEFORE /BEFORE=time Selects patch recovery data sets created before the specified date and time. You can specify time as an absolute time, as a combination of absolute and delta times, or as one of the following keywords: TODAY (default) TOMORROW YESTERDAY Is BOOT now included here as well? For me, /BEFORE=BOOT would actually be interesting. I normally do a shutdown to break the system-disk shadow set, then reboot with a single-member system-disk shadow set, then install patches. I want to keep the new stuff around, i.e. those installed since boot, and get rid of the older ones. ------------------------------ Date: Wed, 30 May 2007 20:48:51 -0400 From: "Richard B. Gilbert" Subject: Re: PCSI, disk space, UNDO, unseen dangers etc Message-ID: <465E1B73.5090900@comcast.net> Phillip Helbig---remove CLOTHES to reply wrote: > In article <1180549692.337203.57560@i13g2000prf.googlegroups.com>, > "george.pagliarulo@hp.com" writes: > > >>Each time you install a patch kit (patch, not product) PCSI creates an >>UNDO directory for that kit. The UNDO directory for the latest patch >>kit installed is always number one. Therefore, everytime you install >>a patch kit PCSI has to go through and re-number all the existing UNDO >>directories to make room for the newest one. > > > OK. > > Isn't renaming directories officially unsupported, though? :-) > I don't recall if it's supported or not. ISTR that there is, or can be, a problem with some BACKUP commands if a directory has been renamed. If you MUST rename a directory, get an IMAGE backup ASAP. IIRC, some backups do either too little or too much if a directory is renamed. ------------------------------ Date: 30 May 2007 19:47:33 -0700 From: yyyc186@hughes.net Subject: Re: RDB Tutorial Message-ID: <1180579653.396082.145230@p47g2000hsd.googlegroups.com> On May 29, 7:28 am, "Ruslan R. Laishev" wrote: > Hello, Dr. Dweeb! > > > > Dr. Dweeb wrote: > > Ruslan R. Laishev wrote: > >> Hello, All! > > >> I looking for RDB tutorial "for beginners". > > >> Thanks for any pointers. > > > Do you mean OracleRdb as a specific product, or "rdb" as a generic reference > > to relational databases. > > > Read Chris Date's book for the latter and I guess the Hobbs book for the > > former. > > Amazon search is your friend here. > > I looking for any guide which describe for beginners several ways for > developing/programming apps under/on RDB: > > - SQL Mods > - SQL Preprocs > - Stored Procedures, Packages (?) > - Creating and using constants in the stored procedures/packages (as is it in > the ORACLE PL/SQL stuff). > > > > > Dweeb > Well, at the risk of this being an advertisement, you might want to visit http://www.theminimumyouneedtoknow.com and take a look at "The Minimum You Need to Know to Be an OpenVMS Application Developer". I'm the author, so my opinion is skewed. ------------------------------ Date: Wed, 30 May 2007 15:55:34 -0400 From: "Hal Kuff" Subject: Remote Shadow... Message-ID: Any current users using this product at 40 to 50ms latency? ------------------------------ Date: Wed, 30 May 2007 15:58:14 -0400 From: "Hal Kuff" Subject: Re: Remote Shadow... Message-ID: Thats remote shadow the non-HP product... http://www.advsyscon.com/products/rso/ "Hal Kuff" wrote in message news:XEk7i.16603$7T.2371@newsfe18.lga... > Any current users using this product at 40 to 50ms latency? > ------------------------------ Date: Wed, 30 May 2007 22:58:50 +0300 From: =?ISO-8859-15?Q?Uusim=E4ki?= Subject: Re: SSH port scanners Message-ID: <465dd70d$0$8371$9b536df3@news.fv.fi> My VMS machine was also attacked by some SSH port cracking attempts. When the SSH session limit was at default value (10000) the repeating attempts did consume a lot of memory and the machine became really slow. As a countermeasure I limited sessions to 20 and after that it wasn't that bad anymore, but they still kept coming. One day I got really mad at the crackers and changed the SSH port number to a nonstandard one and after that day I haven't had a single attempt. I can recommend it as a solution for a known user community, but if your machines are public servers, it might be a problem, though. IMHO the default limit is unnecessary high. There aren't very many Alphas which can handle 5000 interactive sessions. I think the vast majority of AlphaServers running VMS host less that 1000 simultaneous SSH sessions. Large clusters and the biggest GS series AlphaServers might have more than that. Tom Linden wrote: > These guys are a nuisance, what are others doing, if anything about > these. > ------------------------------ Date: Wed, 30 May 2007 20:32:25 -0500 From: Ron Johnson Subject: Re: SSH port scanners Message-ID: On 05/30/07 14:58, Uusimäki wrote: > > My VMS machine was also attacked by some SSH port cracking attempts. > When the SSH session limit was at default value (10000) the repeating > attempts did consume a lot of memory and the machine became really slow. > As a countermeasure I limited sessions to 20 and after that it wasn't > that bad anymore, but they still kept coming. One day I got really mad > at the crackers and changed the SSH port number to a nonstandard one and > after that day I haven't had a single attempt. I can recommend it as a > solution for a known user community, but if your machines are public > servers, it might be a problem, though. > > IMHO the default limit is unnecessary high. There aren't very many > Alphas which can handle 5000 interactive sessions. I think the vast > majority of AlphaServers running VMS host less that 1000 simultaneous > SSH sessions. Large clusters and the biggest GS series AlphaServers > might have more than that. How many "enterprise" Alphas host thousands of meat-bag connections anymore? Isn't it all pooled client-server connections, etc? > Tom Linden wrote: >> These guys are a nuisance, what are others doing, if anything about >> these. >> -- Ron Johnson, Jr. Jefferson LA USA Give a man a fish, and he eats for a day. Hit him with a fish, and he goes away for good! ------------------------------ Date: 30 May 2007 11:52:19 -0700 From: Katie Tam Subject: Upgrade to Vista from XP ? Yes or No Message-ID: <1180551139.432014.273620@j4g2000prf.googlegroups.com> Should I upgrade my laptop to Vista ? Good or Bad? Please advise Katie Tam Network Administrator http://www.linkwaves.com/main.asp http://www.linkwaves.com/ ------------------------------ Date: Wed, 30 May 2007 15:50:38 -0400 From: "Richard B. Gilbert" Subject: Re: Upgrade to Vista from XP ? Yes or No Message-ID: <465DD58E.2050806@comcast.net> Katie Tam wrote: > Should I upgrade my laptop to Vista ? Good or Bad? > > Please advise > > Katie Tam > Network Administrator > http://www.linkwaves.com/main.asp > http://www.linkwaves.com/ > This is really the wrong forum for this question. Having said that, why would you want to upgrade? Does whatever you're running work? Does it do what you need it to do? My computer is eligible for a "free upgrade" but I wouldn't dream of touching it. It works very well as is! ------------------------------ Date: Wed, 30 May 2007 15:51:24 -0400 From: sol gongola Subject: Re: Upgrade to Vista from XP ? Yes or No Message-ID: Katie Tam wrote: > Should I upgrade my laptop to Vista ? Good or Bad? > > Please advise > > Katie Tam > Network Administrator > http://www.linkwaves.com/main.asp > http://www.linkwaves.com/ > should be OT. Ask yourself the following: Is there something that stopped working on XP that vista will fix? Is there something you want to do for which vista is necessary? Do you know for sure that everything you are using will work under vista or will you have to upgrade your applications? What is the cost and time spent upgrading worth compared to just getting a new preinstalled laptop. They aren't that expensive anymore and a new machine will be faster and have more memory/storage. ------------------------------ Date: Wed, 30 May 2007 15:56:14 -0400 From: "Hal Kuff" Subject: VMS L&T Distribution Message-ID: Hi, looking for someone to get the latest distribution from... can anyone provide us with a copy? ------------------------------ Date: 30 May 2007 15:55:10 -0700 From: Rich Jordan Subject: [OT] (kinda) HP, parts ain't parts; KVM internal power supply Message-ID: <1180565710.892717.25200@h2g2000hsg.googlegroups.com> We've got an HP KVM switch, 336044-B21. Its just out of warranty, and not under contract. Power supply went all microsoft on us (low output, capacitors oozing, no worky). HP does not provide service parts, and cannot tell us where to get same, though they'd be happy to sell us a new unit. Aside from being very difficult to understand, the parts person was pleasant and tried to help but apparently something on his screen said "can't help, no info, make the caller go away and move on to the next one". Its kind of on topic because we do have a DS10 and an MV3100-30 connected to it; its currently running with an old PC-AT power supply jury-rigged up to it. Its a small open frame, made by DVE, model number DSO-142L (may be DS0). The number comes up on a couple of chinese websites, but doesn't seem to be a 'normal' replacement at the usual places (Digikey, Jacobs, etc). Any ideas where we could get one, or a compatible enough to fit inside the case unit? 4.6" x 1.4" x 1" high, output +5.1/2.4A and -5V/0.5A, mounts on and grounds through little metal pedestals inside the KVM case. Thanks ------------------------------ Date: Wed, 30 May 2007 21:33:02 -0400 From: "FredK" Subject: Re: [OT] (kinda) HP, parts ain't parts; KVM internal power supply Message-ID: "Rich Jordan" wrote in message news:1180565710.892717.25200@h2g2000hsg.googlegroups.com... > We've got an HP KVM switch, 336044-B21. Its just out of warranty, and > not under contract. Power supply went all microsoft on us (low > output, capacitors oozing, no worky). > > HP does not provide service parts, and cannot tell us where to get > same, though they'd be happy to sell us a new unit. Aside from being > very difficult to understand, the parts person was pleasant and tried > to help but apparently something on his screen said "can't help, no > info, make the caller go away and move on to the next one". > Probably because the unit itself is the FRU (field replaceable unit) and there are no orderable "parts" to fix it. Many things are this way because it makes no sense to stock low volume or low cost subcomponents - especially when the unit is probably made by someone else and sold with a HP logo. ------------------------------ End of INFO-VAX 2007.295 ************************