The IBM 1130 Computing System, introduced in 1965, was IBM's least expensive computer at that time. A binary 16-bit machine, it was marketed to price-sensitive, computing-intensive technical markets, like education and engineering, succeeding the decimal IBM 1620 in that market segment. Typical installations included a 1 megabyte disk drive that stored the operating system, compilers and object programs, with program source generated and maintained on punched cards. Fortran was the most common programming language used, but several others, including APL, were available.

The 1130 was also used as an intelligent front-end for attaching an IBM 2250 Graphics Display Unit, or as remote job entry (RJE) workstation, connected to a System/360 mainframe.

Description

The total production run of the 1130 has been estimated at 10,000.
The 1130 holds a place in computing history because it (and its non-IBM clones) gave many people their first direct interaction with a computer. Its price-performance ratio was good and it notably included inexpensive, removable disk storage, with reliable, easy-to-use software that could be in several high-level languages. The low price (from around $32,000 or $41,000 with disk drive) and well-balanced feature set enabled interactive "open shop" program development.

The IBM 1130 uses the same electronics packaging, called Solid Logic Technology (SLT), used in System/360. It has a 16-bit binary architecture, as do later minicomputers like the PDP-11 and Data General Nova.

The address space is 15 bits, limiting the 1130 to  words () of memory.  The 1130 uses magnetic-core memory, which the processor addresses on word boundaries, using direct, indirect, and indexed addressing modes.

Models
IBM implemented five models of the 1131 Central Processing Unit, the primary processing component of the IBM 1130. The Model 1 through Model 5 describe the core memory cycle time, as well as the model's ability to have disk storage. A letter A through D appended to the model number indicates the amount of core memory installed.

IBM 1131 Central Processing Unit weighs about 760/1050 lb (345/477 kg).

The Model 4 was a lower-priced product with a 5.6 μs cycle time. Some purchasers of performance upgrades observed that the field adjustment to achieve the improvement was surprisingly trivial.

The IBM 1132 printer relies on the 1130 processor rather than internal logic to determine when to fire the print wheels as they rotated. Printers for the Model 4 run more slowly, but the slower processor still can not keep up with it. The hardware manual discloses that when the Model 4 was servicing the two highest-level interrupts (the level 0 card-reader column interrupt or the level 1 printer interrupt), it ran at the faster 3.6 μs cycle time. Some users of the Model 4 would write a phony printer driver that did not dismiss the printer interrupt, in order to benefit from the higher processor speed. However, lower-level interrupts are disabled during this interval, even the end-of-card interrupt (level 4) from the 1442 card reader.

Follow-on products
The IBM 1800, announced November, 1964, is a predecessor of the IBM 1130 for process control applications. It uses hardware rather than core memory for the three index registers and features two extra instructions (CMP and DCM) plus extra interrupt and I/O capabilities. It is a successor to the IBM 1710, as the IBM 1130 is a successor to the IBM 1620.

The IBM 1500 is a multi-user educational system based around either an IBM 1130 or an IBM 1800. It can connect to up to 32 student work stations, each with a variety of audio-visual capabilities.

Other than these, IBM produced no compatible successor systems to the 1130. The IBM System/7 is a process control and real-time system, and the IBM Series/1 is a general-purpose 16-bit minicomputer, both having different architectures from the 1130, and from each other.

Chronology
February 11, 1965 – IBM introduces the 1130 (Models 1A, 1B, 2A, and 2B). Also announced is the IBM 1132 printer, the lowest cost online computer printer ever announced by IBM at that time.
Fourth quarter 1965 – First customer shipments begin from the San Jose plant.
March 31, 1966 – IBM introduces the IBM 1500 educational system.
April 1966 – IBM 1800 ships.
August 9, 1966 – IBM rolls out the 1130 synchronous communications adapter, which permits the small 1130 system to be connected by regular leased telephone lines to, and function as a communications terminal for, any model of the IBM System/360.
April 17, 1967 – A four-way expansion of the 1130 is announced (Models 2C, 2D, 3B, 3C, and 3D), involving:
Five times the disk storage and four times the core memory;
An additional processing speed almost 40 percent faster than previously available;
More and faster peripheral equipment, including an optical mark reader;
An improved commercial programming package.
January 1968 – First shipments begin of the 1130 Models 2C, 2D, 3B, 3C, and 3D.
July 1968 – The Boca Raton plant begins shipping the 1130.
July 22, 1971 – 1130 Models 4A and 4B are introduced at new levels of economy.
September 1971 – First customer shipments begin of the 1130 Model 4.
May 31, 1972 – Models 1C, 1D, 5B, 5C and 5D are announced.
1973 - The Xerox 530 was marketed as a possible successor to IBM 1130 customers. Orders for the Xerox 530 were deemed "encouraging" as of January 1974.

Software
To maximize speed and conserve space, the operating system and compilers are written entirely in assembly language and employ techniques that are rare today, including intermixing code and data as well as self-modifying code.

Much user programming is done in Fortran. The 1130 Fortran compiler can run on a machine with only 4,096 words of core—though the compiled program might not fit on such a machine. In this multi-pass compiler, each "phase" processes the entire source program and takes it another step toward machine code.  For example, the first phase reads the source statements into memory, discards comment lines, removes spaces except in text literals, concatenates continuation lines and identifies labels. The compiler is available in a disk-resident version as well as on 8-channel punched paper tape or punched cards.

The most widely used operating system for the 1130 is the Disk Monitor System Version 2 (DM2) introduced in 1967. DM2 is a single-task batch-oriented system. It requires a system with at least 4 KB of core memory and one integrated 2310 disk drive for system residence. The Supervisor is tiny by modern standards, containing assorted system details such as first-level interrupt routines, called Interrupt Level Subroutines, plus the disk driver and routines to load the interpreter of job control commands and the card reader driver. Device drivers for other I/O devices required by a job are incorporated as part of the loading of that job, which might also include the replacement of the basic disk driver by a more advanced driver. During the execution of a job, only a resident monitor, called the Skeleton Supervisor, resides in memory. This Supervisor requires just 1020 bytes, so a task's first available memory starts with address /01FE (hexadecimal) or word 510.  When the job ends or is aborted, the supervisor loads the Monitor Control Record Analyzer (MCRA) to read the job control for the next. While the job is running, the Supervisor is inactive. Aside from device drivers and interrupt processing all CPU time is entirely devoted to the job's activities.  Other programs distributed as part of the operating system are a core dump utility, DUMP, and the Disk Utility Program, DUP.

A Card/Paper Tape Programming System was available to support systems without disk.

There is a hierarchy of device drivers: those with names ending in Z are for Fortran, such as DISKZ, while assembler programmers might use DISK0, and DISK1 was even faster at reading multiple disk sectors. But DISKZ starts its sector addressing with the first available unused sector, while the others start with sector zero of the disk, making it possible for a programmer unfamiliar with disk organization to inadvertently overwrite the bootstrap loader.

Other programming languages available on the 1130 include
 APL,
 BASIC,
 COBOL,
 FORTH,
 PL/I (in the form of the SL/1 interpreter), and
 RPG.

There is even a French language ALGOL compiler, in which for example "Debut ...Fin;" take the place of "Begin ... End;".  All its messages are in French, so "Bonne compilation" is the goal.

Eastern Michigan University developed a Fortran IV compiler for the 1130, known as Fortran-EMU, as an alternative to the Fortran IV (subset) compiler provided by IBM.  It adds many Fortran Iv features not supported by the IBM compiler, including the LOGICAL data type, six-letter variable names, and enhanced diagnostics. The Fortran-EMU compiler was distributed as a deck of punched cards in a disk image file format with all the remaining system area deleted, to prevent copying other modules that would normally reside on the same disk, such as the assembler or compilers.

Oklahoma State University developed an ALGOL 68 compiler, written in ANSI Fortran 1966.

A FOCAL interpreter was developed at the University of Michigan.

IBM also distributed a large library of programs, both IBM-supported (Type I and II) and unsupported (Type III and IV).

Since the 1130 was aimed primarily at the scientific market,
scientific and engineering programs predominated:
 Scientific Subroutine Package
 Draw and Plot Subroutines
 Electric Power System Load Flow Program
 Multiple Regression
 Calculation of Electrical Distribution System Fault Currents
 Pipe Analysis
 COGO coordinate geometry
 Continuous System Modeling (CSMP)
 Linear Programming Mathematical optimization Subroutine System
 Structural Engineering System Solver (STRESS)
 Statistical System

The 1130 also occupied a niche as a data processing machine for smaller organizations:
 1130 Commercial Subroutine Package
 Student Information System
 CPM/PERT

There is also special-purpose software:
 Remote Job Entry (RJE)
 Typesetting

Job control
Batch operation of the 1130 is directed by control records in the primary input stream (card or paper tape reader). There are two types of control records, monitor control records and supervisor control records.

Monitor Control Records
Monitor control records are identified by //␢ followed by a "pseudo-operation code" in columns 4–7. "␢" represents a single blank.

The JOB record can have a "T" in column 8 to indicate that any files added to the User Area by this job should be deleted at the end. Columns 11 thru 15 can contain a cartridge label; the system verifies that the specified cartridge is mounted before proceeding.

The XEQ record may contain the name of the program to be run in columns 8 thru 12. If this is omitted, the program currently in Working Storage will be executed. If column 14 contains "L", and the program is in Disk System Format (not core-image) a core map will be printed by the Core Load Builder. If this statement is followed by LOCAL NOCAL, or FILES Supervisor Control Records, columns 16 and 17 contain the count of these records. Column 19 optionally indicated which disk driver routine is to be linked. "0", "1", or "N", request DISK1, DISK2, or DISKN, any other character, including blank, requests DISKZ, the FORTRAN disk routine.

Supervisor Control Records
Supervisor Control records begin with an "*" in column 1, immediately followed by the command pseudo-operation in column 2. They are LOCAL, NOCAL, and FILES for the Core Load Builder. DUP control records have a similar format. These records control program linking, either for the // XEQ statement or the DUP *STORECI command.

Operating procedure

The enduring memories of the IBM 1130 may have resulted from its need for continual human intervention. It was usually occupied running "jobs" specified by a deck of punched cards. The human operator would load jobs into the card reader and separate them back into jobs for return, perhaps along with printed output, to the submitter. The operator would also have to watch the 1130 for evidence of a malfunctioning or stalled job and intervene by pressing the  key on the keyboard to skip ahead to the start of the next job.

Marking the start of a job was a punched card that started with // JOB. Any card that started with // was a command to the Supervisor and could not be used as user program or data. Other commands included // DUP to execute the Disk Utility Program (to delete files or add the file in the temporary area to the file collection) and // XEQ to execute a named program from disk. If a user program tried to read a command card, the standard card reader routine would signal end-of-input to the program and save that card's content for the Supervisor.

Initial Program Load (IPL)
Unlike the IBM 360, where a booting device can be selected from the system console, an IBM 1130 can only be "booted" (IPL'd: Initial Program Load) from an external device: a card reader or a paper tape reader.

The bootstrap procedure reads one card from the card reader.  The boot card contains binary code to read the contents of sector zero of the disk drive, which in turn handles the "operation complete" interrupt from the disk drive and performs additional disk reads to prepare the 1130 for the first punched-card job. The whole process takes about a second to complete.

Recovery procedures
When the IBM 1130 is started, the Supervisor is still in memory and probably intact, as core memory retains its state without power.  If the operator concludes that a user program has stalled, the Supervisor can sense a key press to abort the program and skip ahead to the next // card.  The Supervisor is not protected against modification by a badly written job, a case that might require that the operator reboot the 1130.  Nor was there protection against writing to disk.  If the copy of the system software on disk is modified, it can be restored by reloading it from about 4000 binary-coded punched cards (approximately two boxes).

Disk organization

The IBM 2310 disk drive stores sectors of 320 words (640 bytes) plus a one-word sector address. A cylinder consists of two tracks on the top and bottom surfaces of the 2315, or of one platter on the 1316 disk pack used in the 2311.  Each disk cylinder contains eight sectors. A sector is logically divided by the monitor into sixteen disk blocks of 20 words (40 bytes) each. The disk block is the unit of allocation for files.

The system distinguishes between system cartridges, which contain the monitor and utilities along with user data, and nonsystem cartridges, which contain user data only. All cartridges contain information on cylinder 0, including the defective cylinder table, cartridge id, and a bootstrap program (bootstrap code). On nonsystem cartridges, the bootstrap simply prints an error message and waits if an attempt is made to boot from this cartridge. On a system cartridge this is the cold-start program, followed by a communications area and the resident monitor in sectors one and two.  Sectors three through five contain the System Location Equivalence Table (SLET)—a directory of all phases of all monitor programs.  Other control information fills out the first track.

The system area is present on system cartridges. It contains the Disk Monitor program, and optionally the FORTRAN compiler, the Assembler, and a core image buffer used for linking relocatable programs. It also contains the user file directories— Fixed Location Equivalence Table (FLET), and Location Equivalence Table (LET),

Following the system area, the cartridge contains up to three logical subdivisions: the fixed area, the user area, and working storage. Both the fixed area and user area store non-temporary programs and data. The fixed area size is defined by DUP, and stores data, and programs in core image format only. It is not repacked when files are deleted. The user area stores data and programs in any format. The boundary between the user area and working storage "floats"— the user area expands as files are added and contracts as it is repacked to reclaim space from deleted files. If a file needs to be modified, the usual process is to use // DUP commands to delete it, which moves any subsequent files back to close the gap, and then give that name to the temporary file as the new version of the file. Rarely modified files thus migrate towards the start of the disk as new files or new versions are appended, and frequently modified files are stored towards the end of the disk.

Working storage starts after the last file in the user area and occupies all the remaining space on the cartridge. It may contain one temporary file created by the system or the user, such as the output of a compiler or an application program. This file is subject to possible deletion at the end of the current job, unless saved to the fixed area or the user area.

All disk files are contiguous disk blocks, thus there is no fragmentation. A program can use and modify named files, but can not expand them beyond their created size. A program which creates more than one file must have all but one pre-allocated by a DUP.

With limited disk space, program source files are normally kept as decks of cards. Users having larger requirements may have a disk of their own containing the operating system, but only their files, and would have to replace the "pool" system disk with theirs and restart the system when their programs are to be run. A system with a second disk drive that can be devoted entirely to one user's code and data provides some relief.

A disk pack or cartridge is initialized for use on the 1130 by the Disk Pack Initialization Routine (DIPR). This routine scans the disk, and writes sector addresses on all cylinders, flags defective sectors, and writes a cartridge id on cylinder zero. DIPR is a Standalone program, which is loaded from cards or paper tape, and accepts the cartridge id from the system console.

Disk Utility Program (DUP)
The Disk Utility Program (DUP) provides commands for transferring programs, subroutines and data. It is invoked by the job control  // DUP card, followed by one or more control cards:

Other commands, mainly for use by the system administrator, define or expand the Fixed Area, delete the FORTRAN compiler and/or Assembler from the system, and restore correct sector addresses to Working Storage if they have been modified.

The operands have to be placed into fixed columns.The source device code goes in columns 13 and 14, the destination device in columns 17 and 18. These device codes are:
 UA – User Area
 FX – The fixed area (no "extents" as per the 360; just contiguous space)
 WS – Working Storage
 CD – Punched Card/Principal Input device (could be PT: Paper Tape)
 PR – Printer
Optionally, a program name may be coded in columns 21 thru 25, and a count field in 27 thru 30. The interpretation of these fields depends on the DUP function requested.

Programs can be converted to a faster-loading format with the STORECI command, which invokes Core Image Builder (DM2's counterpart to the 360's Linkage Editor). Alternatively, a program can go through this process each time it is to be run, and for infrequently used programs this is preferred in order to conserve disk space.

The following control card instructs DUP to take the current contents of working storage and move it to the user area naming it PROGM. DUP knows the size of the file in working storage. The size of the user area will be increased by the size of the file, and the size of working storage will be decreased correspondingly.

Peripheral devices

Disk memory is used to store the operating system, object code, and data, but source code is kept on punched cards.

The basic 1130 came with an IBM 2310 voice-coil actuated disk drive, called "Ramkit", from IBM's General Products Division in San Jose. Their pizza-box-sized IBM 2315 single platter cartridges holds 512,000 words or 1,024,000 bytes (less than a 3.5" HD floppy's 1.44MB or even the 5.25" HD floppy's 1.2MB). Transfer rate is 35,000 words per second (70 KB/sec) using cycle stealing.

The IBM 1053 console typewriter uses an IBM Selectric mechanism, which means one could change the typeface or character set by replacing a hollow, golf-ball sized type element. There is a special type element available for APL, a powerful array-oriented programming language using a special symbolic notation. A row of 16 toggle switches on the console typewriter can be individually tested from within programs, using the special Fortran statement IF (SENSE SWITCH i), for example.

Other available peripherals included:
Printers – the IBM 1132 and IBM 1403 line printers
Punched-card – the IBM 1442 card reader/punch and the IBM 2501 card reader
Paper tape – the IBM 1055 paper tape punch, the IBM 1054 paper tape reader, and the IBM 1134 paper tape reader
Disk – the IBM 2311 Disk Drive
Magnetic tape – From 1968, IBM 2415 Magnetic tape data storage drives were available as an RPQ.
Graphics – IBM 2250 Graphic Display Unit.
Color Pen Plotter – IBM 1627 drum plotter.
Optical Mark Reader – IBM 1231 Optical Mark Page Reader
Communications – Synchronous Communications Adapter (SCA).  The IBM 1130 MTCA, for Multiple Terminal Control Adapter, announced in 1970 allowed up to four 2741 terminals to be connected to an IBM 1130, for use with APL.

To simplify the design of peripheral devices, these rely on the processor. The card reader has no memory buffers, but instead gives the CPU a level-zero (highest priority) interrupt after each individual column of the card has been read. If the CPU does not respond and store the twelve bits of data before another such interrupt indicates that the next column has been read, data will be lost. Similarly, the 1132 printer relies on software in the 1130. When a letter such as A comes into position, the CPU has to analyze a buffered line of text and assemble an array of bits that will indicate to the 1132 which print positions should be printed with A. If the CPU can not respond before the A rotates out of position, print speed could be severely degraded.

Other peripherals accept text in a device-specific code convenient for its hardware. The CPU has to translate it to or from the EBCDIC code in which the CPU processes the text.

Instruction set overview
Instructions have short (one-word) and long (two-word) formats.  Most computational, load, and store instructions reference one register (usually ACC) and a memory location.  The memory location is identified, in the short format, by an 8-bit signed displacement from either the current address or one of the index registers; or in the long format, by a full 15-bit address, which can be indexed and specify indirection. Memory is addressed in units of words.

The 1130 supports only single-precision and double-precision binary data natively (16 and 32 bits)  stored in big-endian format. Standard- and extended-precision floating-point (32 and 48 bits) and decimal data are supported through the use of subroutines.

Conditional transfers are based on (a) the current contents of the accumulator, or (b) the carry and overflow indicators set by a preceding operation.  Transfers can be by skip (which assumed that the next instruction was short) or by branch. A skip occurs if any of the specified tests are true. A branch occurs if none of the specified tests were true.

Main Registers:
IAR = Instruction Address Register
ACC = Accumulator
EXT = Extension Register
XRx = Index Registers: x = 1,2,3
      Implemented as memory words 1,2,3, not as hardware registers.

Condition tests:
Z  Accumulator zero
-  Accumulator negative
+  Accumulator positive
E  Accumulator even
C  Carry indicator off
O  Overflow indicator off

1130 Instruction Set Mnemonics:
LD   = Load ACC                   STO  = Store ACC
LDD  = Load Double (ACC & EXT)    STD  = Store Double (ACC & EXT)
LDX  = Load Index                 STX  = Store Index
LDS  = Load Status                STS  = Store Status
A    = Add ACC                    AD   = Add Double
S    = Subtract ACC               SD   = Subtract Double
M    = Multiply                   D    = Divide
AND  = Boolean AND                OR   = Boolean OR
XOR  = Boolean Exclusive OR
SLA  = Shift Left ACC             SLT  = Shift Left ACC & EXT
SLCA = Shift Left and Count ACC   SLC  = Shift Left and Count ACC & EXT
SRA  = Shift Right ACC            SRT  = Shift Right ACC & EXT
RTE  = Rotate Right ACC & EXT
BSC  = Branch or Skip on Condition (Modifier dependent)
       i.e. BP BNP BN BNN BZ BNZ BC BO BOD
BOSC - Branch Out or Skip Conditionally (alternate for BSC with bit 9 set)
       Exits current interrupt level.
BSI  = Branch and Store IAR
MDX  = Modify Index and Skip (Increment IAR one if a sign change or becomes zero)
WAIT = Halt                       NOP  = No Operation (alternate for SLA 0)
XIO  = Execute I/O

1800 Additional Instruction Mnemonics:
CMP  = Compare ACC                DCM  = Double Compare ACC & EXT

Equivalent Mnemonics
The disk assembler introduced several mnemonics equivalent to existing
instructions intended to make the programmer's intent clearer:
SKP - Skip on condition, equivalent to a short BSC
B   - Branch unconditionally, equivalent to BSC with no conditions specified
BP  - Branch Accumulator Positive, equivalent to BSC specifying '+' condition
BNP - Branch Accumulator not Positive
BN  - Branch Accumulator Negative
BNN - Branch Accumulator not Negative
BZ  - Branch Accumulator Zero
BNZ - Branch Accumulator not Zero
BC  - Branch on Carry
BO  - Branch on Overflow
BOD - Branch Accumulator Odd
MDM - Modify Memory, equivalent to unindexed long-format MDX
XCH - Exchange Accumulator and Extension, equivalent to RTE 16

Short instruction format (one 16 bit word):
                       1
Bits    0...45678......5
        OP---FTTDisp----

OP    is Operation
F     is format 0 = Short
TT    is Tag
Disp  is Displacement

Long instruction format (two 16 bit words):
                       1               1
Bits    0...456789.....50..............5
        OP---FTTIMod----Address---------

OP    is Operation
F     is format 1 = Long
TT    is Tag
I     is Indirect bit
Mod   is Modifier

Effective Address Calculation (EA):
          F = 0            | F = 1, I = 0     | F = 1, I = 1
          Direct Addressing| Direct Addressing| Indirect Addressing
-------------------------------------------------------------------
TT = 00 | EA = Displ + IAR | EA = Add         | EA = C/Add
TT = 01 | EA = Displ + XR1 | EA = Add + XR1   | EA = C/Add + XR1
TT = 10 | EA = Displ + XR2 | EA = Add + XR2   | EA = C/Add + XR2
TT = 11 | EA = Displ + XR3 | EA = Add + XR3   | EA = C/Add + XR3
-------------------------------------------------------------------
    Disp = Contents of displacement field
     Add = Contents of address field of instruction
       C = Contents of location specified by Add or Add + XR

Reserved memory
The lowest addresses of core memory have uses dictated either by the hardware or by convention:

Programming

Subprograms
The 1130 has no hardware support for a stack.  Most subprograms are called with the instruction BSI (Branch and Store IAR).  This deposits the value of IAR (the return address) at the destination address and transfers control to destination+1. Subprograms return to wherever they were called on that occasion using an indirect branch through that first word of the subprogram. Placing the return address in-line was a common technique of computers at that time, such as the Hewlett-Packard HP 2100, the DEC PDP-8, and the Scientific Data Systems SDS 920.

So a subprogram named SIMPL might be organized as follows (comments follow the instruction operand):

 SIMPL: DC     *-*    This is the entry point, filled with a zero initially.
        (whatever the routine does)
        B    I SIMPL  Return by an Indirect branch, to the address found in location SIMPL.
        END    SIMPL  Instructs the assembler that the source for routine SIMPLE is complete.

The subprogram would be called as follows:

        BSI  L SIMPL  Call SIMPL. L (Long) is needed if SIMPL is more than -128 or +127 words away.

The pseudo-opcode CALL would typically be used.

As shown, a subprogram's entry point is DC *-*, an assembler pseudo operation that is used to Define a Constant (occupying one word of storage) with the value specified by the expression. The * stands for the current address of the assembly and so *-* results in zero. Writing this rather than 0 provides a visually distinctive note that a meaningful value (the return address) will be placed there at run time. The entry point need not be the first word of the subprogram. Indeed, the preceding word can be the start of a two-word direct branch instruction whose address field is at SIMPL. Then, returns can be effected by one-word branches there: B SIMPL-1

When SIMPL is called, the BSI instruction replaces *-* with the current value of IAR, which is the address just past the BSI instruction.  After SIMPL does whatever it is written to do, B I SIMPL branches not to SIMPL, but indirect through it, thus continuing execution with the instruction following the BSI instruction that called SIMPL.

Without extra arrangements to protect the return address, recursion is impossible:  If SIMPL calls itself, or called a subprogram that called it, its original return address is overwritten.  Re-entrancy is problematic for the same reason:  An interrupt service routine must refrain from calling any subprogram that might have been the code that was interrupted.

The caller of SIMPL might pass it parameters, which might be values or addresses of values.  Parameters might be coded in-line (immediately following the BSI instruction) or might be placed in index registers XR1 and XR2.  If parameters are placed in-line, SIMPL modifies its own return address so its final indirect branch returns beyond the parameters.

Integer functions of a single integer expect the parameter in the accumulator and return their result there. Floating-point functions employ the floating-point accumulator (a two word area set aside by the floating-point library, three words for extended precision), and so on.

The convention of coding 0 as the initial value at the entry point means that if a programming error leads to SIMPL returning before the first time it was ever called, execution would jump to memory location 0.  As mentioned above, it is customary to have location 0 contain a branch to location 0.  The 1130 would be stuck at location 0, and the IAR lights on the console would be entirely dark, making it clear the program had failed.

Linkage to library routines
For subprograms that would be called many times (for example, subprograms for floating-point arithmetic), it is important to reduce the size of each call to one word. Such "library routines" use the LIBF protocol.  It is more complex than the CALL protocol described in the previous section, but LIBF hides the complexity from the writer of the assembly-language program.

Library routines are addressed through index register XR3.  (Fortran subprograms use index register XR1 for the addresses of parameters and the return address, but register XR2 is unused.)  XR3 points to a sequence of three-word transfer vectors such that the first entry is -128 words from XR3's value.  The programmer calls the library routine using the LIBF pseudo-operation, which assembles not a direct BSI to the routine but a one-word indexed branch instruction (BSI 3 disp) whose displacement (-128, -125, and so on) identifies the start of the routine's transfer vector.

The transfer vector is prepared by the linkage loader when it puts together the program.  A transfer vector entry to a library function named SIMPL takes this form:

       DC       *-*            A word into which BSI stores the return address.
       B    L   SIMPL          Branch to the start of the library function.

The way SIMPL knew where its return address was is that, if SIMPL were declared a LIBF routine, the linkage loader would modify the code of SIMPL, placing the address of SIMPL's transfer vector entry at SIMPL+2.  LIBF routines, unlike CALL subprograms, do not start with a DC directive to hold the return address (it is in the transfer vector) but with actual code, as follows:

 SIMPL STX   1  RCVR1+1        Save the caller's value of XR1 at a nearby location.
       LDX  I1  *-*            The linkage loader changes the address word to point to the transfer vector.

Placing the address of SIMPL's transfer vector at SIMPL+2 leaves room for a one-word instruction to save the chosen index register, here XR1. Then the indirect LDX instruction points XR1 not at the transfer vector, but through it to the return address, or to any parameters stored in-line after the BSI.  SIMPL then does whatever it was written to do, gaining access to any in-line parameters through XR1 (in which case it must increment XR1 for the return address), and returns as follows:

       STX   1  RETN+1         Store XR1 to prepare to use it as a return address.
 RCVR1 LDX  L1  *-*            SIMPL's first instruction modified this address.  Now,
 *                              restore the original value of XR1.
 RETN  B    L   *-*            This instruction was modified two instructions ago; return.

Example
Suppose a LIBF-style call to SIMPL were at address 100.  Then the return address would be 101, because BSI 3 disp is a one-word instruction. XR3 points into the group of transfer vectors.  If the transfer vector for SIMPL started at address 2000, then the BSI would be assembled with a disp so that XR3+disp = 2000.  Executing the BSI stores 101 at location 2000 and jumps to location 2001.  At 2001 is a two-word long jump to the entry point of SIMPL, which the linkage loader might have placed at address 300.

The long jump transfers control to SIMPL.  After the instruction at 300 stores XR1, the instruction at 301 is LDX I1 2000, the linkage loader having placed 2000 at location 302.  This does not load 2000 into XR1; it is an indirect instruction, and loads the contents of 2000, which is 101, the return address for that call to SIMPL.

In the return sequence shown above, by the time control reaches RETN, the instruction there is B L 101, which returns to the caller.  (If there is one or more in-line parameters at 101, SIMPL would increment XR1 to point to 102 or beyond, and this would be the destination of the B instruction.)

Variations
If SIMPL took parameters coded in-line following the BSI instruction, SIMPL gains access to them with indexed addressing off XR1.  The first could be obtained by LD 1 0, the second by LD 1 1, and so on. If the second parameter is the address of the actual parameter, then LD I1 1 obtains its value. Before returning, SIMPL increments XR1 past the n parameters with an instruction such as MDX 1 n so as to place the right value at RETN+1.

A LIBF routine that declined to restore the original value of XR1 could omit the above steps and return with a simple B 1 n to skip n in-line parameters.  However, such a routine can not be called by other LIBF routines because it disrupts the caller's use of XR1 for access to its own parameters and return address.

The complexity of LIBF saves memory for subprograms that are frequently called.:  The LIBF linkage requires one word per invocation, plus three words for the transfer vector entry and extra code in the routine itself, whereas the CALL linkage requires two words per invocation because most CALLs will be to an address beyond the -128 to +127 word reach of the one-word opcode.

The register XR3 must point to the transfer vector entries for the library routines rather than a dispatch table of only their addresses, because this latter would require that LIBF routines be called with an indirect BSI instruction.  These instructions are two words long, so such a design would negate the code size savings of LIBF. The eight-bit limit for the disp field of the one-word instruction code limits usage of LIBF routines to no more than 85 distinct entries.

Code modification

The previous sections show that code and data are intermingled.  It is common in 1130 programming to modify the address fields of instructions and, in fact, to modify entire instructions.

By the Fortran compiler
The Fortran compiler produces self-modifying code when generating code for any subprograms (subroutines or functions) that have parameters. The compiler builds a table of every location where the subprogram references one of its parameters, and compiles as the first instruction in the body of the subprogram a call to a subprogram called SUBIN that uses the table to modify the address field of every reference to a parameter to be the actual address of the parameter during the current invocation.  SUBIN makes these patches every time the subprogram is called.

When a Fortran program calls a subprogram, the addresses of any parameters appear in-line following the call.  For example, the Fortran statement CALL SIMPL(X) might compile into:
   BSI L  SIMPL
   DC     X      The address of X, on which SIMPL is to operate

Within the subprogram, parameters could be accessed by indirect indexed addressing as shown above in Variations, so, given that XR1 has been suitably prepared, an integer parameter could be loaded into the accumulator with an instruction like this:
   LD  I1 0      Load the value of the first parameter (offset 0) into the accumulator

The compiler instead used direct addressing.  When SUBIN runs, it obtains the address of X and patches the instruction's address field to become:
   LD  L  X      Load the value of X into the accumulator

The advantages of SUBIN are as follows:
To obtain the operand's address an indirect indexed instruction requires three memory cycles (the index register being in memory) while the direct access instruction require only one.
If SIMPL were to pass one of its parameters to any subprogram that expected to receive the address of its parameter (including all the LIBF routines for floating-point arithmetic), SUBIN is needed to supply the actual address of the original parameter.

The disadvantages of SUBIN are the time it requires to run and the memory required for the table of references.  The size of this table is the sum of 5, the number of parameters, and the number of references; if this sum exceeds 511, compilation will fail.  For subprograms with many references to a parameter, the author of the subprogram might copy the parameter into a local variable.

By the user
Modifying entire instructions was a common technique at the time.  For example, although the 1130 has an OR instruction, the syntax of Fortran provides no way to write it.  An integer function IOR can be defined, enabling logical OR to be part of a Fortran expression such as:
   M = 3*IOR(I,J) + 5
The Fortran compiler places the addresses of I and J in-line and expects the result in the accumulator.  Using IOR(I,J) in a Fortran expression compiles the following four words:

   BSI  L IOR    Two-word jump to the start of the IOR function.
   DC     I      A one-word in-line parameter: The address of I.
   DC     J      A one-word in-line parameter: The address of J.

In fact, the assembler IOR function does not compute I or J at all.  Instead, it replaces the above four words with the following:

   LD   L I      Load accumulator with I (two-word instruction)
   OR   L J      OR accumulator with J   (two-word instruction)

After performing that transformation, it does not return past the end of the four-word block (which it had just modified).  Instead, it branches to the exact address from which it had been called originally.  The BSI instruction is no longer there; what is now there is the two instructions it has just written.  They combine the two integers with the machine-language OR instruction and leave the result in the accumulator, as required.

The call to IOR and the transformation of the four-word block happens at most once per program run.  If the Fortran line illustrated above is executed again, it runs faster than it did the first time. Similar functions could be devised for other useful operations.

A function that self-modifies, as IOR does, can not be used in a Fortran subprogram on any of the parameters to that subprogram (though it could be used to combine local variables) because it is incompatible with the SUBIN subprogram discussed above.  IOR's transformation of its four-word calling sequence, shown above, moves the location of the address of variable I.  On subsequent calls to the Fortran subprogram, the table of references to parameters would be in error and SUBIN would patch the wrong word, in this case placing the new address of I over the OR operation code.

Extended precision
1130 FORTRAN  offers two floating point formats:  a 32-bit "standard precision" format and a 40-bit "extended precision" format.

Standard precision format contains a 24-bit two's complement significand while extended precision utilizes a 32-bit two's complement significand. This format makes full use of the CPU's 32-bit integer operations. The extended format occupies three 16-bit words, with the high-order eight bits of the first word unused. The characteristic in both formats is an 8-bit field containing the power of two biased by 128.  Floating-point arithmetic operations are performed by software.

The *EXTENDED PRECISION compiler option card tells the FORTRAN compiler to use 40 bits instead of 32 bits for all floating point data, there is no provision for mixing formats.

Large Fortran programs
Data to be manipulated and the instructions that manipulate them have to reside together in core memory.  The amount of installed memory (from 4,096 to 32,768 words) is a key limitation.  Fortran provides several techniques to write large programs despite this limitation.

LOCAL subprograms
Fortran let any subprogram be designated as "LOCAL" (Load-on-Call).  Each LOCAL subprogram is an overlay; it is part of the disk-resident executable program but is only loaded into core memory (if not already there) during the time it is called.  So, for example, six LOCAL subprograms would require only as much core memory as the largest, rather than the total amount for all six. However, none of the six can invoke another, either directly or through intermediary subprograms.

Programs in phases
An entire Fortran program can pass control to a subsequent phase, exiting to the Supervisor with an instruction to load the follow-on phase into core memory. A large program might be split into three parts, separately compiled, called PART1, PART2, and PART3.  Execution is started by // XEQ PART1 and at a suitable point, PART1 would execute the Fortran statement CALL LINK(PART2) and so forth.  The name of the successor program in the CALL can not be variable, but program logic can govern whether control is transferred to another phase, and which CALL LINK statement is executed.  As mentioned above, the Fortran compiler itself was written this way, with each phase of compilation achieved by a separate program.

COMMON data storage
Programs, such as Fortran programs, reside at low core memory addresses (just above the Supervisor).  Fortran allocates space at the highest addresses for any variables and arrays declared COMMON.  If a follow-on phase of the program contains a corresponding COMMON declaration, then information in this common area can be shared among phases.  Phases could omit the COMMON declaration without problem, provided those phases were not so large as to have their program code invade the common area.  COMMON storage not only shares data between phases; lower-memory COMMON variables can be used to pass data among a main program and subprograms within a single phase, though the data could be lost on moving to the next phase.

Programming examples
The examples can be executed on the IBM 1130 emulator available at IBM 1130.org.

Sample assembler program deck
The following listing shows a card deck that compiles and runs an assembler program that lists a deck of cards to the line printer.

 // JOB
 // ASM
 *LIST
                     * LCARD.ASM - LIST A DECK OF CARDS TO LINE PRINTER
                     *
                     * PROGRAM
                     *    NEW PAGE ON PRINTER
                     * A  READ A CARD
                     *    CONVERT FORMAT
                     *    PRINT A LINE ON PRINTER
                     *    GOTO A
                     *
                     START LIBF    PRNT1    GOTO NEW PAGE ON 1132
                           DC      /3100    PRINTER CHANNEL 1-NEW PAGE
                     *
                     NEXTC LIBF    CARD0    READ FROM 1442 CARD READER
                           DC      /1000    CONTROL TO READ
                           DC      CBUFF    STORE 80 COLUMNS
                     CINP  LIBF    CARD0
                           DC      0
                           B       CINP     LOOP UNTIL CARD IS READ
                     *
                           LIBF    ZIPCO    CONVERT CARD TO PRINTER
                           DC      /1100    UNPACKED IN, PACKED OUT
                           DC      CBUFF+1  INPUT BUFFER
                           DC      PBUFF+1  OUTPUT BUFFER
                           DC      80       CHARACTER COUNT
                           CALL    HLEBC    HOLLERITH TO EBCDIC
                     *
                           LIBF    PRNT1    PRINT 80 CHARACTERS
                           DC      /2000    CONTROL CODE TO PRINT
                           DC      PBUFF    PRINT BUFFER
                           DC      PERR     PRINT ERROR
                     POUT  LIBF    PRNT1    CHECK FOR PRINT COMPLETE
                           DC      0
                           B       POUT     LOOP UNTIL COMPLETE
                     *
                           B       NEXTC    READ NEXT CARD
                     *
                     * DATA
                     *
                     CBUFF DC      80       80 COLUMNS PER CARD
                           BSS     80
                     *
                     PBUFF DC      40       40 WORDS 80 CHARACTERS
                           BSS     40
                     *
                     PERR  DC      0
                           B    I  PERR     THIS RETURNS TO THE
                     *                       PRINTER ERROR HANDLER
                     *                       WHICH WILL TERMINATE THE PROGRAM
                     *
                           END     START    PROGRAM ENTRY POINT
 // XEQ
 TEST DATA 1
 HELLO WORLD
 TEST DATA 2

In this job, the assembler leaves the result of its assembly in the temporary area of the system disk, and the XEQ command executes the content of the temporary area. The odd-looking END START has two meanings: end of assembler source, and the name of the entry point of the routine, which has the label START.

Assembler source starts with column 21 of the card, not column one. In systems without a disk drive, the assembler would punch code into the start of the card just read (the card reader was actually a reader-punch, with the punch station after the read station) and then read the next card. To handle forward branches and the like, the assembler's second pass literally involved a second pass of the cards through the reader/punch. If source changes were needed the programmer would duplicate the cards to obtain a deck with columns 1-20 blank ready for the next run through the assembler.

By convention, buffers are preceded by a word count.  The DC (Define Constant) assembles a count word and the following BSS (Block Started by Symbol) reserves the required number of words for the buffer. The card buffer requires 80 words, one for each card column.  Driver CARD0 reads each card column literally, using 12 of the 16 bits in the buffer word, with a bit set to on for each hole punched in the corresponding row for that column.  The pattern of punches typically describes a text character using the Hollerith code.  The console keyboard also gives input to the program in the Hollerith code, the only case of two devices using the same character encoding.

The printer routine, however, works with text in 8-bit EBCDIC with two characters per word, requiring a 40-word buffer.  The program uses library routine ZIPCO to perform the conversion. Despite appearances, the statement CALL HLEBC is not executed because HLEBC is not a subroutine but an IBM-supplied Hollerith-to-EBCDIC conversion table.  The CALL statement provides the address of the table to ZIPCO and ensures that the linking loader includes the table in the program, thus it is the fifth parameter to ZIPCO, though one occupying two words of storage: the BSI operation code word for the CALL is unused and thus usually wasted, but the second word of the expansion of CALL HLEBC is the address of the HLEBC table needed by ZIPCO. After the conversion, the program sends the converted output, now in buffer PBUFF, to the printer through driver PRNT1.  Again, the program loops until the printer driver reports completion, then the program reads the next card.

This example contains no code to decide when to stop.  A more complete program would check for cards that begin with //, which denotes the start of the next job. To stop the card reader as soon as possible, a program could check for the Hollerith code of / before even converting the card to EBCDIC.

Asynchronous I/O and performance
The call to CARD0 to read a card initiates that operation and immediately returns to the caller, which could proceed with other activity. However, the example program makes no attempt to overlap input and output using buffers even though it has two separate work areas; it simply loops back to CIMP to test afresh. After CARD0 has sensed the card reader's operation-complete interrupt, it returns one word further on, thus skipping the jump back to CIMP and leaving the loop.

The example routines do not run the I/O devices at top speed. Notably, the card reader, only a few milliseconds after reporting completion on reading a card, will commence its stop sequence, after which a new read command will have to wait to initiate another read cycle. The IBM 1442 reader could read 400 cards/minute at full speed, but just a little hesitancy in the read commands would halve its throughput or worse. A Fortran program could not complete even the simplest input processing in time, and so could not read cards at full speed. One common Fortran DO loop to read cards made the motor stop and start so frequently as to accelerate wear.  With buffering, the card reader control could be overlapped with processing, and the reader could be run at full speed through large data decks, but memory for the more complex program and for buffers was often at a premium.

Even with assembler and double buffering, a program to list a deck of cards from the IBM 2501 reader (1,000 cards/minute) on the line printer could not keep up, as the translation from card hole patterns to EBCDIC for the printer as done by EBPRT was too slow; the more complex ZIPCO and HLEBC were needed instead, as in the example.

Sample APL\1130 session
The following image shows a simple APL \ 1130 session.   This session was performed via the 1130 simulator available from IBM 1130.org

The above session shows a signon, addition of the integers 1 to 100, generation of an addition table for the integers 1..5 and a sign off.

Competing systems
In the same year as the 1130's introduction, Digital Equipment Corporation introduced the smaller, cheaper, and better-selling 12-bit PDP-8, recognized as the first successful minicomputer.

Influence of the 1130

Brian Utley was the 1130s project manager during its development and introduction. Brian said at the third 11/30 party that before IBM Marketing named the 1130 it was known as the Small Engineering Computer System or SECS.  The initial architecture was 18 bits but was changed to 16 bits due to the influence of the System/360 development.  The full dialogue of his 2005 presentation is available at IBM1130.org.
Notable software designer Grady Booch got his first exposure to programming on an IBM 1130:
... I pounded the doors at the local IBM sales office until a salesman took pity on me. After we chatted for a while, he handed me a Fortran [manual]. I'm sure he gave it to me thinking, "I'll never hear from this kid again." I returned the following week saying, "This is really cool. I've read the whole thing and have written a small program. Where can I find a computer?" The fellow, to my delight, found me programming time on an IBM 1130 on weekends and late-evening hours. That was my first programming experience, and I must thank that anonymous IBM salesman for launching my career. Thank you, IBM.
LISP guru Guy Steele wrote a LISP interpreter for the IBM 1130 when he was in high school (Boston Latin School, which had an IBM 1130 for student use).  His code and documentation for LISP 1.6, along with a summary of current work in getting it to run under simulation, is available at IBM1130.org.
Chuck Moore wanted to call his new language "Fourth" but the IBM 1130 operating system was limited to five-character names, so it wound up being called FORTH.
Dan Bricklin, creator of the VisiCalc program, got his start in programming when he learned and used the IBM 1130 as part of the National Science Foundation Computer/Math Summer Project for high school students, given at the University of Pennsylvania in 1966.
An IBM 1130 with 8 kilowords of core was used for the world's first full-time Search for Extraterrestrial Intelligence research at The Ohio State University Radio Observatory. This equipment detected the Wow! signal.
Charles Goldfarb, the father of SGML, describes a job installing a typesetting system based on an IBM 1130 that "eventually changed my career", driving him towards generic markup:
The system was an IBM 1130 computer, a machine the size of a desk with 8 KB of main memory, a 512 KB disk drive, a Teletype CX paper tape reader and BRPE paper tape punch, and a Photon 713 photomechanical typesetter. The assignment was my first experience with managing a machine-readable document database: I learned to roll the punched paper tape carefully so that it could be stored neatly in cylindrical waste paper baskets.In the meantime, though I didn't know about it, the roots of generalized markup were being planted. Historically, electronic manuscripts contained control codes or macros that caused the document to be formatted in a particular way ("specific coding"). In contrast, generic coding, which began in the late 1960s, uses descriptive tags (for example, "heading", rather than "format-17").
 Alan Kay used the IBM 1130 in early GUI work for his Ph.D. thesis in 1969.
Hutchinson Central Technical High School ("Hutch Tech") in Buffalo, NY used the IBM 1130 in the nation's first four-year high school computer science curriculum in 1969. Robert Santuci was the computer science program head and taught classes in programming and inductive logic.
 An engineer from IBM was hired by Signetics and incorporated a number of architectural features from the IBM 1130 into the Signetics 2650 single-chip processor.

1130s today
Out of an estimated 10,000 systems produced, the following are known to exist as of :
 ACONIT in Grenoble, France has a complete 1130 system.
 The Computer History Museum (Mountain View, California) has an 1130 system.
 COSECANS (Basel, Switzerland).
 The National Museum of Computing (TNMOC) (Bletchley Park, United Kingdom) has a complete 1130 system.
 The University of Stuttgart (Germany) has a functional 1130 system.
 Carl Claunch is currently restoring an 1130 system.

Apocrypha
Speculation on why the product was given the number 1130 centered on the following possibilities:
That, since the 1130 was a small scientific machine, the number was chosen by multiplying 360 (as in IBM 360) by π.
That 11:30 was the time of day that product planners reached an impasse regarding what to call the product.
That the 1130 was IBM's 11th Computer Design, and it had 30 instructions.

Others have speculated that the existence of the IBM 1130 explains why no computer designated "11/30" ever appeared in the PDP-11 family of machines.

See also
IBM mainframe
List of IBM products

Notes

References

External links

IBM Archive: IBM 1130 press releases, chronology, photos, facts folder.
IBM 1130.org Norm Aleks and Brian Knittel site which has significant information about the 1130 and a downloadable simulator that supports the DMS R2V12 and APL environments.
www.ibm1130.net is Howard Shubs' site dedicated to the 1130.
Arnold Reinhold's personal account of the 1130. Text from here has been incorporated into this article with permission
A set of PDFs made up of scanned IBM 1130 manuals
Kym Farnik's page on Retro Computing specifically the 1130
A discussion about the (then) Angle Park computing centre which was equipped with IBM 1130's
Bob Rosenbloom's IBM 1130 Photos
IBM 1130 material at Columbia University, Computing History site.
A Flickr collection of detail photos taken by Peter Vaughan of an IBM 1130 at The National Museum of Computing

1130
Magnetic-core memory computers
16-bit computers
IBM 1130

IBM 1130


Paul Christophe est un nom de personne assez fréquent en Belgique et dans le nord de la France ; il peut désigner notamment :

 Paul Christophe (1870-1957), ingénieur belge ;
 le père Paul Christophe (1932-2016), professeur honoraire à l'Université catholique de Lille ;
 Paul Christophe (né en 1971), homme politique français, député maire de Zuydcoote.

Paul Christophe


Die Samuel Holbrook Ltd. (anfänglich: Holbrook & Taylors Ltd.) war ein britischer Hersteller von Automobilkarosserien.

Unternehmensgeschichte

Namensgeber des Unternehmens war Samuel Holbrook. Holbrook war Verkaufsleiter bei Austin gewesen, bevor er sich Anfang 1930 selbständig machte und sich bei der L. & L. Taylor Ltd., einem Spezialisten für Nutzfahrzeugaufbauten in Wolverhampton, einkaufte. Das Unternehmen wurde als Holbrook & Taylors Ltd. reorganisiert. Trotz anfänglicher Ankündigung, im Nutzfahrzeugbereich tätig zu bleiben, stellte die Firma bereits im gleichen Jahr Sonderaufbauten für PKW auf der Olympia Motor Show in London vor: eine Cabrio-Limousine (All-Wheather Saloon) für Hillman und eine Sportsman's Saloon genannte Sportlimousine für Invicta. Bis 1937 präsentierte die Firma regelmäßig ihre Karosserien an den Londoner Automobilausstellungen im Olympia respektive Earls Court.

1933 zog sich die Familie Taylor aus der Firma zurück. Es folgte eine Reorganisation unter dem Namen Samuel Holbrook Ltd. mit neuen Teilhabern. In den folgenden Jahren baute Holbrook eine Reihe weiterer All-Wheather Saloons für Hillman und konnte mit Alvis zusammenarbeiten. Für eine Reihe von Modellen dieser Marke entstanden attraktive Limousinen. Holbrook nannte das Design Dorchester und verkaufte Varianten davon auch an Crossley, Lanchester, Singer, Standard und Wolseley; bei Vauxhall wurde es als Suffolk und bei BSA als Varsity geführt.

Holbrook bemühte sich um eine Ausweitung des Geschäftsfelds und begann ab etwa 1935 Sonderkarosserien für Luxusautomobile herzustellen. Die Firma schaffte es, in den Kreis der von Rolls-Royce empfohlenen Karossiers aufgenommen zu werden, woraus sich dauerhaft jedoch auch nicht genügend Aufträge ergaben. Nachdem ein letzter Versuch mit Karosserien für Linien- und Reisebusse, unter anderem in Kooperation mit dem Motorradhersteller A.J.S., gescheitert war, blieb nur der Weg in die Insolvenz. Samuel Holbrook Ltd. schloss ihre Tore 1938.

Literatur
 Walker, Nick: A–Z of British Coachbuilders, 1919–1960; Bay View Books, Bideford, Devon, UK (1997), ISBN 1-870979-93-1 (englisch)

Weblinks

Einzelnachweise

Ehemaliger Karosseriehersteller
Ehemaliges Unternehmen (West Midlands, Metropolitan County)
Jaguar Cars
Gegründet 1933
Aufgelöst 1938

Samuel Holbrook Ltd.


is a Japanese voice actor and singer affiliated with Arts Vision.  Some of his major anime roles include Son Goku in Saiyuki, Kira Yamato alongside Rei Tanaka and Akira Ishida, in Gundam Seed, Gundam Seed Destiny & Mobile Sute Gundam Seed Freedom 2024 alongside Rei Tanaka and Akira Ishida, Kazuki Fuuchouin in GetBackers, Masaru Daimon in Digimon Savers, Kaoru Hanabishi in Ai Yori Aoshi, and Tomoki Sakurai in Heaven's Lost Property. In video game franchises he voices Sanada Yukimura in Sengoku Basara, Keiichi Maebara in Higurashi When They Cry, Kilik in Soulcalibur, and various characters in Haruka: Beyond the Stream of Time. He partially voices Shirogane Takeru in the Muv-Luv series. Hoshi was also known for his voice roles of villains as Goro Akechi from Persona 5, Death Gun from Sword Art Online, and Lio Shirazumi in The Garden of Sinners  & Sentarō Miya in Kono Oto Tomare! Sounds of Life.

For his work, Hoshi has been awarded the voice acting award in the Anime Grand Prix in both 2005 and 2006. Additionally, in the 2007 Seiyu Awards,  Hoshi was a nominee in the category "Best Actors in supporting roles" for his portrayal as Kira Yamato in the Mobile Suit Gundam SEED Destiny.

Filmography

Anime

Film

Video games

Tokusatsu

Drama CD

Dubbing

Discography

Albums

References

External links

 Sōichirō Hoshi at GamePlaza-Haruka Voice Acting Database
 Sōichirō Hoshi at the Seiyuu.info database

1972 births
Living people
Male voice actors from Fukushima Prefecture
Japanese male video game actors
Japanese male voice actors
Japanese male pop singers
King Records (Japan) artists
Singers from Fukushima Prefecture
20th-century Japanese male actors
21st-century Japanese male actors
21st-century Japanese singers
21st-century Japanese male singers
Arts Vision voice actors
People from Aizuwakamatsu

Sōichirō Hoshi


Herne, Almanya'nın kuzeybatısında, Kuzey Ren-Vestfalya eyaletinde Arnsberg ili'ne bağlı bir kent. Kent Ruhr sanayi havzasında Bochum ile Gelsenkirchen arasında konumlanmıştır.

Konum
Ruhr sanayi bölgesinde, Dortmund'un yaklaşık 16 km batısındadır; Ren-Herne ve Dortmund-Ems kanallarının kesiştiği noktada yer alır. Nüfusu, (31 Aralık 2010 itibarıyla) 164,762 kisidir.

Tarihçe
10. yüzyılda Haranni adıyla bilinen yerleşim, 19. yüzyılda yörede kömür yatakları bulunana değin küçük bir köy olarak kaldı. 1897'de tüzel kimlik kazanan kent bugün kömür madenleri, dökümhaneleri ve tekstil fabrikalarıyla bir sanayi merkezi durumundadır. 1975'te, bitişiğindeki Wanne-Eickel (1926'da Wanne ve Eickel kentlerinin birleştirilmesiyle kuruldu) kenti ile birleştirilmiştir.

Ekonomi
Ruhr bölgesinde önemli bir ulaşım merkezi olan kentte kömür madenciliği, demir işleri, biracılık ve kimya sanayileri vardır.

Herne'de faaliyet gösteren önemli kuruluşlar
 UPS
 Phönix AG
 Schwing AG
 Sasol
 Degussa AG
 Von der Linde

Kardeş şehirler
Herne kentinin şu kentlerle resmi kardeş şehir bağlantıları bulunmaktadır:

Resimler

Notlar

Dış bağlantılar

 Herne Belediyesi resmi websitesi
 Herne Turizm Sitesi

Kuzey Ren-Vestfalya'daki şehirler
Kuzey Ren-Vestfalya'daki belediyeler

Herne, Kuzey Ren-Vestfalya


Die Grohmannhütte () ist eine Schutzhütte im Südtiroler Teil der Stubaier Alpen.

Lage und Umgebung

Die Grohmannhütte befindet sich auf  Höhe im oberen Ridnauntal nahe der österreichisch-italienischen Staatsgrenze auf dem Gebiet der Gemeinde Ratschings. Die nächstgelegenen Ortschaften sind Maiern und Ridnaun.

Der einfachste Anstieg zur Hütte erfolgt durch das Ridnauntal. Zu den von hier aus erreichbaren Berggipfeln zählen unter anderen Agglsspitze, Feuerstein, Schneespitze, Wilder Freiger, Wilder Pfaff, Sonklarspitze und Botzer. Etwas nordwestlich liegen die Teplitzer Hütte, das Becherhaus und die Müllerhütte. In nordöstliche Richtung ist ein Übergang zur Magdeburger Hütte im Pflerschtal möglich. Von der Grohmannhütte aus dem Weg nach Süden folgend überschreitet man das Egeltjoch und kommt zum ehemaligen Bergbaugebiet Schneeberg.

Geschichte

Die Hütte wurde 1887 von der Sektion Teplitz des DuÖAV als Teplitzer Hütte erbaut und am 27. August eröffnet. Im Winter 1887/88 wurde die Hütte durch einen Sturm vollständig zerstört. Daraufhin finanzierte der böhmische Großindustrielle Theodor Grohmann für 1.534 Florin einen Neubau, der nach ihm benannt wurde. Die neue, wenn auch kleinere Hütte, eröffnete am 14. August 1889. Nach dem Ersten Weltkrieg wurde die Hütte vom italienischen Staat enteignet und der CAI-Sektion Sterzing übergeben. Nachdem sie einige Jahre leer gestanden hatte und zu Teilen verfallen war, erfolgte in den Jahren von 1998 bis 2000 eine Komplettsanierung.

Zusammen mit 24 weiteren vom Staat enteigneten Schutzhütten ging die Grohmannhütte 1999 in das Eigentum der Autonomen Provinz Bozen – Südtirol über; mit Jahresende 2010 lief die Konzession zu deren Führung durch den CAI aus. Seit 2015 wird das Land Südtirol bei der Verwaltung der Hütte (Vergabe an Pächter, Überwachung der Führung, Sanierungsmaßnahmen) durch eine paritätische Kommission unterstützt, in der neben der öffentlichen Hand auch der AVS und der CAI vertreten sind.

Weblinks

Einzelnachweise

Alpenhütte in Südtirol
Ratschings
Schutzhütte des Landes Südtirol
Ehemalige Schutzhütte des Deutschen Alpenvereins

Grohmannhütte


The Swan River is a tributary of the Mississippi River, approximately 60 mi (97 km) long, in northeastern Minnesota in the United States.

It rises in Swan Lake, in southeast Itasca County, near Pengilly, approximately 13 mi (21 km) southwest of Hibbing. It flows southwest, east of Trout Lake, then SSE past Warba. It joins the Mississippi in northern Aitkin County at Jacobson, approximately 20 mi (32 km) southeast of Grand Rapids.
At Warba, the river measures approximately 130 cubic feet per second.

Swan River is an English translation of the native Ojibwe-language name.

See also
List of Minnesota rivers

References

Rivers of Minnesota
Tributaries of the Mississippi River
Rivers of Aitkin County, Minnesota
Rivers of Itasca County, Minnesota

Swan River (northern Minnesota)


Sinégorié (en , soit littéralement « la région des montagnes bleues ») est une commune urbaine de l'oblast de Magadan, en Russie. La commune se situe dans le raïon de Iagodnoïe. Sa population était estimée à  en 2022.

Géographie

Situation
Sinégorié se situe dans la Kolyma, au nord-est de la Sibérie. Elle se situe sur la rive gauche du fleuve Kolyma, et non-loin de la confluence avec la rivière Bakapcha. Elle se situe à  au nord-est de Magadan, et à  à l'est de Moscou.

Climat
Le climat de Sinégorié est classifié en tant que Dfb par la classification de Köppen. L'amplitude des précipitations est de , celle des températures est de .

Histoire

L'histoire du village commence le  avec le début de la construction du village, dans le but de loger les ouvriers de la centrale hydroélectrique de la Kolyma alors en construction, à 5 kilomètres en amont. Le village se développe rapidement, et un plus tard, de nombreux immeubles et l'école sont déjà debout. Les années suivantes, de nombreux services sont construits, tel qu'une piste de slalom, un hôpital et un sanatorium, des infrastructures toujours en activité aujourd'hui.

Le  , l'aéroport est ouvert, assurant une liaison quotidienne vers Magadan.

Cependant, la croissance fut de courte durée, la population commençant à partir d'abord à cause de l'avancement de la construction de la centrale hydroélectrique et ensuite par la dislocation de l'URSS. Ainsi entre 1989 et 2002, Sinégorié perd 80% de sa population, entraînant l'abandon de nombreux bâtiments et de lieux publics comme la piscine, le cinéma ou le centre culturel. De plus, l'aéroport ferme ses portes en 2000. La même année, une église a été construite.

Cependant, une liaison aérienne est rétablie avec Magadan début 2022.

En 2023, Fine Line, un documentaire russe d', a été tourné dans le village. Le documentaire concerne les problèmes démographiques des régions du Grand Nord, de l'enclavement de ces régions, et de leur avenir, plus ou moins prometteur.

Population
Recensements (*) ou estimations de la population:

Transports

Sinégorié est relié au reste du pays par la R504 Kolyma. La ville est située à  de Magadan par la route, et une ligne de bus fait la liaison. De plus, depuis janvier 2022, un petit aéronef fait la liaison chaque mercredi entre son aéroport et Magadan.

Galerie

Liens externes

 Histoire de Sinégorié sur

Notes et références

Notes

Références

Sinégorié (oblast de Magadan)


Hasan İldan, (d. 1932, (Elmaağaç, Adaklı), Türk siyasetçidir.

Ankara Üniversitesi Hukuk Fakültesi mezunudur. Serbest Avukatlık, Yapı-İş Sendikası Hukuk Müşavirliği, Cumhuriyet Senatosu Elazığ Üyeliği (12 Ekim 1975 – 12 Eylül 1980), Cumhuriyet Senatosu Başkanlık Divânı İdare Amirliği yapmıştır. Evli ve iki çocuk babasıdır.

Kaynakça

1932 doğumlular
Adaklı doğumlular
Ankara Üniversitesi Hukuk Fakültesinde öğrenim görenler
TBMM Elazığ Cumhuriyet Senatörleri
TBMM Cumhuriyet Senatosu İdare Amirleri
Hukukçu Senatörler
Resim aranan siyasetçiler
Yaşayan insanlar
20. yüzyıl Türk avukatları
21. yüzyıl Türk avukatları

Hasan İldan


Le Projet FOG est un projet de logiciel qui implémente FOG (Free and Open-source Ghost), un logiciel utilitaire qui permet le déploiement d'images disque de Microsoft Windows et GNU/Linux utilisant Preboot Execution Environment.
Il utilise TFTP, Apache HTTP Server et iPXE. Il est écrit en PHP.

L'outil de configuration développé par le projet FOG rend possible l'administration système à distance des ordinateurs dans un réseau. FOG dépend de Partclone pour copier l'image disque.

Voir aussi
 Windows Deployment Services
 Clonezilla

Notes et références

Articles connexes
 Liste des logiciels de clonage de disque

Liens externes

Logiciel de sauvegarde
Logiciel libre

FOG (logiciel)


هاملطن أوثانل سميث  ـ (ولد في 23 أغسطس 1931) هو عالم أحياء دقيقة أمريكي. تقاسم جائزة نوبل في الطب عام 1978 مع السويسري فرنر أربر والأمريكي دانيال ناثانز لاكتشافهم إنزيم الاقتطاع.

ولد سميث في 23 أغسطس 1931، وتخرج في مدرسة المختبر الجامعي العليا في إربانا بولاية إلينوي، ثم التحق بجامعة إلينوي في إربانا-تشامبين، ولكنه انتقل عام 1950 إلى جامعة كاليفورنيا في بيركلي، حيث حصل على درجة البكالوريوس في الرياضيات سنة 1952. وفي سنة 1956 حصل سميث على شهادة الطب من جامعة جونز هوبكنز. وفي سنة 1975 فاز بزمالة غوغنهايم وقضى فترتها في جامعة زيورخ.

في سنة 1970 اكتشف سميث وكنت ولكوكس أول إنزيم ينتمي إلى النوع الثاني من إنزيمات الاقتطاع (وهو الإنزيم الذي يسمى حاليًا HindII)، ثم اكتشف سميث إنزيم دنا ميثيلاز.

روابط خارجية

مراجع

أشخاص على قيد الحياة
أعضاء الأكاديمية الوطنية الأمريكية للعلوم
أعضاء هيئة تدريس مدرسة طب جامعة واشنطن
أمريكيون حازوا جائزة نوبل
حائزون على جائزة نوبل في الطب
حائزون على زمالة غوغنهايم
خريجو جامعة جونز هوبكينز
خريجو جامعة كاليفورنيا (بركلي)
علماء التكنولوجيا الحيوية
علماء أحياء أمريكيون في القرن 21
علماء أحياء دقيقة أمريكيون
مواليد 1931
مواليد في نيويورك

هاملتون سميث


Mörel, Almanya'nın kuzeyinde Schleswig-Holstein eyaletinde, Rendsburg-Eckernförde iline bağlı bölge. 8,69 km² yüzölçüme sahiptir. Nüfusu, 31 Aralık 2018 itibarıyla 234 olarak tespit edilmiştir. Belediye Başkanlığı Klaus-Peter Lucht tarafından yürütülmektedir.

Dış bağlantılar

Rendsburg-Eckernförde iline bağlı yerleşim birimleri

Mörel (Holstein)


Josefa Biondi foi uma política argentina. Ela foi eleita para a Câmara dos Deputados em 1951 como uma das primeiras mulheres parlamentares na Argentina.

Biografia
Nas eleições legislativas de 1951 foi candidata do Partido Peronista em Santa Fé e uma das primeiras mulheres eleitas para a Câmara dos Deputados. Ela permaneceu no cargo até 1955. Ela foi presa durante a Revolução Libertadora e depois exilou-se em Montevidéu.

Mulheres da Argentina na política
Membros do Partido Justicialista
!Mais Teoria da História na Wiki (Mulheres)
Membros da Câmara de Deputados da Nação Argentina

Josefa Biondi


El soldadito capirotado, granero cabecita de fósforo (en Venezuela),  cardonero coronirrojo o cabecita de fósforo (en Colombia) (Coryphospingus pileatus) es una especie de ave paseriforme de la familia Thraupidae, una de las dos pertenecientes al  género Coryphospingus. Es nativo del norte y este de América del Sur.

Distribución y hábitat
Se distribuye en tres áreas disjuntas: en el noreste de Colombia y norte de Venezuela; en los valles andinos del centro de Colombia; y en el centro y este de Brasil. Registrado como accidental en la Guayana Francesa.

Esta especie es considerada poco común a localmente común en sus hábitats naturales: los matorrales áridos y bosques bajos y los bordes arbustivos de bosques caducifolios y semi-húmedos, de sabanas, cerrados y caatingas, entre el nivel del mar y 1600 m de altitud.

Descripción

Mide unos 13 cm de longitud. El macho tiene un penacho rojo escarlata encendido con borde en V negro azulado, que abre cuando está excitado; su píleo es negruzco. Sus partes superiores son grises y las partes inferiores son blancuzcas con matices grisáceos en el pecho y los lados y tiene anillo ocular blanco. La hembra en cambio presenta las partes superiores color marrón, carece de copete rojo y negro y tiene las partes inferiores blancuzcas con estrías grises.

Alimentación

Es principalmente granívoro. Además come insectos y otros artrópodos.

Reproducción
Construye un nido en forma de cuenco, semiesférico. La hembra pone entre tres y cinco huevos. Los polluelos nacen después de 13 días de incubación.

Sistemática

Descripción original
La especie C. pileatus fue descrita por primera vez por el naturalista alemán Maximilian zu Wied-Neuwied en 1821 bajo el nombre científico Fringilla pileata; su localidad tipo es: «Barra de Vareda, Río Pardo, sur de Bahía, Brasil».

Etimología
El nombre genérico masculino Coryphospingus se compone de las palabras del griego «koruphē»: corona de la cabeza, y «σπιγγος spingos» que es el nombre común del 'pinzón vulgar'; y el nombre de la especie «pileatus» del latín que significa 'de gorra'.

Taxonomía
Los amplios estudios filogenéticos recientes de Burns et al. (2014) confirman que la presente especie es hermana de Coryphospingus cucullatus. Algunos autores en el pasado la colocaron en un género Lanio.

Subespecies
Según las clasificaciones del Congreso Ornitológico Internacional (IOC) y Clements Checklist/eBird v.2019 se reconocen tres subespecies, con su correspondiente distribución geográfica:

 Coryphospingus pileatus rostratus , 1947 – valle árido del alto Magdalena, Colombia.
 Coryphospingus pileatus brevicaudus , 1916 – noreste de Colombia sl norte de Venezuela; iclusive en la Isla Margarita.
 Coryphospingus pileatus pileatus (), 1821 – centro y este de Brasil, desde Maranhão, Piauí y Ceará hasta São Paulo, al oeste hasta el este de Mato Grosso.

Referencias

Enlaces externos
 Videos, fotos y sonidos de Coryphospingus pileatus en eBird.
 Sonidos y mapa de distribución de Coryphospingus pileatus en xeno-canto.
 Fotos y sonidos de  tico-tico-rei-cinza Coryphospingus pileatus en Wikiaves.

pileatus
Aves de América del Sur
Animales descritos en 1821
Taxones descritos por Maximilian zu Wied-Neuwied

Coryphospingus pileatus


Takuji Yokoyama (født 19. april 1990) er en japansk fodboldspiller.

Han har spillet for flere forskellige klubber i sin karriere, herunder Grulla Morioka.

Eksterne henvisninger

Fodboldspillere fra Japan

Takuji Yokoyama


Catedrala "Sfinții Petru și Pavel" (în ) este o catedrală ortodoxă rusă situată în Fortăreața Petru și Pavel din Sankt Petersburg, Rusia. Ea este primul și cel mai vechi punct de reper din Sankt Petersburg, fiind construită între 1712 și 1733 pe insula Zaiaci de pe râul Neva. Catedrala și fortăreața au fost construite ambele în timpul domniei țarului Petru cel Mare, după proiectele lui Domenico Trezzini. Turnul clopotniță al catedralei este cel mai înalt turn clopotniță al unei biserici ortodoxe din lume. Din moment ce clopotnița nu este o construcție de sine stătătoare, ci o parte integrantă a clădirii principale, catedrala este, uneori, considerată cea mai înaltă biserică ortodoxă din lume. Mai există o altă biserică cu hramul Sfinții Petru și Pavel la Sankt Petersburg, în cadrul complexului Peterhof.

Arhitectură
Actuala clădire, prima biserică de piatră din Sankt Petersburg, a fost proiectată de Trezzini și construită între 1712 și 1733. Turla aurită ajunge la o înălțime de 123 de metri și are în vârf un înger ținând o cruce. Acest înger este unul dintre cele mai importante simboluri ale orașului Sankt-Petersburg.

Catedrala conține în interior un singur iconostas (perete care separă naosul bisericii de la altar). Iconostasul este în mod normal în Biserica Ortodoxă un perete plat străpuns de trei uși, ușile împărătești aflate în centru sunt folosite doar pentru intrările solemne, iar cele două uși laterale pentru intrarea și ieșirea clerului și a altor persoane în sau din altar. Cu toate acestea, iconostasul catedralei "Sf. Petru și Pavel" se înalță pentru a forma un fel de turn deasupra altarului.

Mai există, de asemenea, un carilon flamand, care a fost dăruit de autoritățile orașului flamand Mechelen, Flandra.

Funcții bisericești
Catedrala este închinată Sfinților Petru și Pavel, sfinții patroni ai fortăreței (Sfântul Petru este patronul spiritual al orașului). Biserica actuală este cea de-a doua biserică construită pe acest loc. Prima biserică, construită imediat după fondarea orașului de către Petru cel Mare, a fost sfințită de către arhiepiscopul Iov de Veliki Novgorod în aprilie 1704.

Biserica fortăreței a fost catedrală (adică biserică în care slujește episcopul orașului; termenul catedrală — sobor (собор) în limba rusă — poate însemna scaunul unui episcop, dar poate însemna, de asemenea, pur și simplu, o biserică mare sau importantă) a orașului până în 1859, când Biserica Sfântul Isac a devenit catedrala orașului. Actuala catedrală a Mitropoliei de Sankt Petersburg este Catedrala Kazan de pe Nevski Prospekt.

Catedrala a fost închisă în 1919 și transformată în muzeu în 1924. Ea îndeplinește încă funcționalitatea oficială de muzeu; serviciile religioase, cu toate acestea, au fost reluate în anul 2000.

Morminte imperiale

Catedrala adăpostește rămășițele pământești ale aproape tuturor țarilor și țarinelor Rusiei de la Petru cel Mare la Nicolae al II-lea și familia sa, care au fost aduși pentru a fi înmormântați aici în iulie 1998. Printre țarii și țarinele Rusiei care se află înmormântați aici este și Ecaterina cea Mare, țarină a Rusiei timp de 34 de ani.

Dintre conducătorii Rusiei de după Petru cel Mare, doar Petru al II-lea și Ivan al VI-lea nu sunt îngropați aici. Petru al II-lea este înmormântat în Catedrala Sfântul Arhanghel Mihail de la Kremlin; Ivan al VI-lea a fost executat și îngropat în fortăreața Șlisselburg sau la Holmogorî (presupusa descoperire de la Holmogorî, în 2010, este cercetată în prezent sub aspect medico-criminalistic).

Maria Feodorovna, țarina Rusiei, a fost reînmormântată în Catedrala Sfinții Petru și Pavel pe 28 septembrie 2006, la 78 de ani de la moartea ei. Soție a țarului Alexandru al III-lea și mamă a lui Nicolae al II-lea (ultimul țar rus), Maria Feodorovna a murit pe 13 octombrie 1928 în exil în țara ei natală, Danemarca, și a fost îngropată în Catedrala Roskilde din Danemarca. În anul 2005, guvernele Danemarcei și Rusiei au ajuns la un acord prin care rămășițele pământești ale țarinei să fie aduse la Sankt Petersburg, în conformitate cu dorința ei de a fi înmormântată alături de soțul ei.

Turnul clopotniță

Turnul clopotniță (cu spire) este imaginea caracteristică dominantă a acestei catedrale și a fortăreței.
El îndeplinește mai multe funcții, ca parte a edificiului:
 Este un simbol arhitectural, un element important al Fortăreței Petru și Pavel.
 Conține o parte a necropolei imperiale - mormintele se află la parter.
 Are un paratrăsnet pentru protejarea catedralei.
 Conține o platformă de vizionare la care se poate urca o dată pe oră de la 12:00 până la 18:00.
 Adăpostește un carilon care oferă periodic concerte de muzică.

Restauratorii care curățau îngerul de pe turlă în 1997 au găsit un bilet într-o sticlă aflată într-unul dintre faldurile robei îngerului. În acea notă, restauratorii din 1953 își cereau scuze pentru ceea ce au simțit că ar fi o lucrare în grabă și de mântuială (premierul sovietic Nikita Hrușciov dorea ca îngerul să fie renovat pentru cea de-a 250-a aniversare a orașului). Se spune că restauratorii din 1997 au lăsat un mesaj pentru generațiile viitoare, dar conținutul mesajului nu a fost dezvăluit.

Istoria carilonului
Când Petru cel Mare a vizitat Olanda în 1690, a auzit cariloanele Hemony din Amsterdam și Leiden cântând toate cele 24 de ore ale zilei, automat la fiecare sfert de oră. Mai târziu, în 1717, el a vizitat Flandra incognito și a urcat în turnul Catedralei Notre Dame din Anvers, unde trebuie să fi auzit cântecul unuia dintre cele două cariloane Hemony într-unul din turnurile catedralei. El a fost impresionat de sunetul carilonului și a dorit ceva asemănător pentru noua catedrală din Sankt Petersburg. A comandat aducerea în 1720 a unui carilon din Olanda. Singurul fabricant de clopote din Amsterdam de la acea vreme era Jan Albert de Grave, ce era căsătorit cu văduva lui Claude Fremy. Acest Claude Fremy era un fost ucenic al lui Hemony. Se presupune că Jan Albert de Grave a fost cel care a realizat carilonul catedralei ruse. Câțiva ani mai târziu, el a făcut, de asemenea, un carilon pentru Potsdam. Oamenii din Sankt-Petersburg au putut asculta acest instrument bine reglat doar o scurtă perioadă de timp. În 1756 turnul a luat foc și s-a prăbușit în urma unei furtuni puternici. Toate clopotele au fost pierdute.

Johann Derck a turnat clopotele și ceasornicarul Barend Oortkras din Haga le-a adus la Sankt Petersburg pentru a le instala. Când a ajuns, turnul nu era încă reconstruit așa că nu a putut instala clopotele. Oortkras a rămas la Sankt-Petersburg, dar a murit în sărăcie în 1764, înainte ca reconstrucția turnului să se fi terminat. Acest nou carilon a fost instalat în anul 1776 de către ceasornicarul german Johann Erdmann Rudiger. Rudiger a fost angajat, de asemenea, pentru a le pune în funcțiune. Clopotele turnate de Derck nu aveau un sunet suficient de melodios, iar astfel unele clopote au fost turnate din nou de către fabricanți ruși în secolul al XIX-lea. Nici acestea nu erau perfecte, de aceea a fost confecționat, în 2001, un nou set de 51 de clopote în partea de sud a Olandei. Clopotele au fost turnate și instalate de către turnătoria regală Petit & Fritsen din Aarle-Rixtel, provincia olandeză Brabantul de Nord.

Carilonul este compus din 51 de clopote cu o greutate brută de 15.160 kg; cel mai mare clopot are o greutate de aproximativ 3 tone, iar cel mai mic de numai 10 kg. Carilonul are o gamă de patru octave, astfel încât poate cânta o mare parte din muzica clasică și modernă.

Carilonul catedralei Sfinții Petru și Pavel este un cadou acordat orașului Sankt Petersburg de către guvernul Flandrei și de mai mult de 350 de sponsori din diferite țări. Contribuția a fost prezentată în numele Majestății Sale Regina Fabiola a Belgiei, al Fondului belgian Regele Boudewijn, al guvernului provinciei Flandra, al autorităților mai multor orașe și comunități flamande, plus întreprinderi și instituții financiare, comunități culturale, școli și universități și, de asemenea, cetățeni obișnuiți din Belgia, Rusia, Anglia, Germania, Lituania, Olanda, Noua Zeelandă, Portugalia, SUA și Japonia.

Galerie

Note

Bibliografie
 Article about Jan Albert de Grave 1699-1729  by Laura J. Meilink-Hoedemaker, in 'Klok en Klepel' the Dutch bulletin of the 'Nederlandse Klokkenspel Vereniging. nr 115 Dec 2011 Dutch and English versions
 Booklet in the cd by Jo Haazen from Sept. 2001 of this carillon gave also information. Beaux 2107

Legături externe

Petru
Arhitectură barocă în Rusia
Biserici cu hramul Sfântul Petru
Biserici cu hramul Sfântul Pavel
Biserici baroce

Catedrala Sfinții Petru și Pavel din Sankt Petersburg


Capela Sfinții Trei Ierarhi este o capelă ortodoxă română aflată pe Aleea Mihail Sadoveanu nr. 46 din Iași, România. Acesta este dedicată Sfinților Trei Ierarhi.

Capela este construită din piatră și cărămidă, cu două materiale alternative pe exterior. Zidul de vest dispune de trei plăci de lemn pictate ale portretelor celor trei sfinți ierarhi, situate deasupra intrării, și sfinții apostoli Petru și Pavel pe părțile laterale. Placa de dedicare este din marmură albă, care datează construcția în 1910. Absidele au trei laturi la exterior și au formă semicirculară în interior. Vestibulul are un spațiu pentru cor, și portrete ale regelui Carol I și regina Elisabeta în postura lor de ctitori. Interiorul este pictat în întregime în frescă. Iconostasul este elaborat sculptat, în timp ce acoperișul este simplu. Nu există nici un turn, doar cinci mari cruci de metal pe acoperiș. Reparațiile au fost efectuate în timpul anilor 1990.

Capela se află pe lista monumentelor istorice din România, întocmită de Ministerul Culturii și cultelor.

Note

Biserici din Iași
Monumente istorice din județul Iași
Biserici cu hramul Trei Ierarhi

Capela Sfinții Trei Ierarhi din Iași


Heliopolis es una película del año 2009.

Sinopsis
Heliopolis lleva al espectador a la vida de cinco personajes desde el crepúsculo hasta bien entrada la noche en Heliopolis, un barrio de El Cairo donde hay iglesias, mezquitas, sinagogas y restaurantes exóticos en una misma calle. Cada uno de los personajes intenta resolver su propio misterio, pero ninguno lo consigue. Solo queda intentarlo de nuevo cuando amanezca. Nunca llegan a verse, pero descubren la belleza de un barrio cuyo glamoroso pasado se desvanece poco a poco en una metrópoli superpoblada.

Premios
 El Cairo 2009

Referencias

Heliopolis (película)


Periyodik tabloda dikey sütunlara grup denir. Aynı grupta olan elementlerin kimyasal özellikleri benzerdir. Yukarı doğru dikeyce çıktıkça özellik yoğunlaşır ve belirginleşir. Bir A grubuna ait elementin son katmanında kaç elektron varsa grup sıralaması da odur. Örneğin, berilyum (Be) atomunun son katmanında 2 elektron vardır ve bu atom 2A grubunun elementi olur.

Bir gruptaki elementlerde yukarıdan aşağıya doğru inildiğinde Atom yarıçapı artar, iyonlaşma enerjisi ve elektronegatiflik ise azalır.

Periyodik tabloda 8 tane A 10 tane de B grubu vardır. A grubu elementlerine baş grup elementleri de denir. Bazı grupların özel adları şöyledir.
 1A grubu Alkali metal'ler denir. Hidrojen hariç hepsi metaldir.
 2A grubu Toprak alkali metalleri denir. Hepsi metaldir.He=elementi 2 elektronla bitmesine rağmen 2A grubunda değil 8A grubuna aittir .(İstisnadır)
 3A grubu Toprak metalleri (ya da Bor grubu) olarak adlandırılır.
 4A Karbon grubu olarak adlandırılır.
 5A Azot grubu (ya da nitrojen grubu) olarak adlandırılır.
 6A Oksijen (ya da Kalkojen) grubu olarak adlandırılır.
 7A grubu Halojenler olarak adlandırılır.
 8A grubu'' Soygazlar bu grupta yer alır.
B grubu elementlerinin tamamı metaldir. B grubu elementlerine geçiş metalleri de denir. B grubunun 2 ilginç özelliği vardır. 2A grubu ile 3A grubu arasında yer alır.

1B'den başlamaz. 3B ile başlar. (3B nin değerlik elektron sayı 3 olduğundan) 2B ile biter. (2B den sonra 3A gelir).

8B grubu yan yana 3'lü element gruplarından oluşur. 8B grubunda dikey benzerlikler yatay benzerliklerden daha önemlidir.

Numaralandırma
Grupları numaralandırmanın üç yolu vardır. İlk kullanım Hindu-Arap Rakamları'nı kullanmak, diğer iki yöntem ise Roma rakamları'dır.

Avrupa ve Amerika'da kullanılan sisteme göre periyodik tablo grupları:

 1. Grup (IA,IA): alkali metaller, hidrojen ya da lityum ailesi
 2. Grup (IIA,IIA): toprak alkali metaller ya da berilyum ailesi
 3. Grup (IIIA,IIIB): skandiyum ailesi
 4. Grup (IVA,IVB): titanyum ailesi
 5. Grup (VA,VB): vanadyum ailesi
 6. Grup (VIA,VIB): krom ailesi
 7. Grup (VIIA,VIIB): manganez ailesi
 8. Grup (VIII): demir ailesi
 9. Grup (VIII): kobalt ailesi
 10. Grup (VIII): nikel ailesi
 11. Grup (IB,IB): bakır ailesi
 12. Grup (IIB,IIB): çinko ailesi
 13. Grup (IIIB,IIIA): toprak metalleri ya da bor ailesi
 14. Grup (IVB,IVA): karbon ailesi
 15. Grup (VB,VA): pentels ya da azot ailesi
 16.Grup (VIB,VIA): kalkojen ya da oksijen ailesi
 17. Grup (VIIB,VIIA): halojen ya da flor ailesi
 18. Grup (Grup 0): soygaz ya da helyum ailesi

Periyodik tablo

Grup (periyodik tablo)


Francis James Spain (* 17. Februar 1909 in Quitman, Georgia; † 23. Juni 1977 in Rochester, New York) war ein US-amerikanischer Eishockeyspieler.

Karriere
Francis Spain besuchte zunächst die Phillips Exeter Academy sowie anschließend das Dartmouth College. Parallel zu seinem Studium spielte er Eishockey und Baseball. Anschließend lief er für das Amateur-Eishockeyteam Boston Olympics auf. Nach seiner Eishockey-Karriere war er als Geschäftsmann tätig.

International
Für die USA nahm Spain an den Olympischen Winterspielen 1936 in Garmisch-Partenkirchen teil, bei denen er mit seiner Mannschaft die Bronzemedaille gewann.

Erfolge und Auszeichnungen
 1936 Bronzemedaille bei den Olympischen Winterspielen

Weblinks

Eishockeynationalspieler (Vereinigte Staaten)
Eishockeyspieler (Dartmouth Big Green)
Olympiateilnehmer (Vereinigte Staaten)
Teilnehmer der Olympischen Winterspiele 1936
US-Amerikaner
Geboren 1909
Gestorben 1977
Mann

Francis Spain


General Korotkoff er en dansk dokumentarfilm fra 1946 med ukendt instruktør.

Handling
På foranledning af Udenrigsministeriet blev en række optagelser af general Fjodor Korotkovs besøg i København, det daværende kronprinsepars og general Dewings besøg på Bornholm samlet til en film, der, forsynet med russisk speakertekst, blev sendt som gave til Bornholms russiske kommandant general Korotkov.

Referencer

Se også
 Allieret militærmodtagelse - Russerdans på Rådhuspladsen - Bornholm, dokumentarfilm fra 1945

Eksterne henvisninger

Danske film fra 1946

Dokumentarfilm fra Danmark

General Korotkoff


Lale Yavaş (d. 1978, Zürih) Türk kökenli İsviçreli oyuncu

Lale Yavaş, 1978 yılında Türk kökenli bir ailenin kızı olarak Zürih'te dünyaya geldi. Bern Üniversitesi Güzel Sanatlar Akademisi Müzik ve Tiyatro Bölümü'nden mezun olduktan sonra Alles Wird Gut, Ben İsviçreli Bir Bankacıydım ve Imbissness adlı filmlerde rol aldı. 2005 yılında Alman birinci kanalı ARD'de gösterilen Zeit der Wünsche (Dilekler Zamanı) adlı iki bölümlük televizyon filmindeki performansından dolayı çok sayıda olumlu eleştiri aldı. Türkiye'den Almanya'a işgöçü bağlamında bir aşk hikâyesinin anlatıldığı bu filmdeki başarısı, Adolf Grimme Ödülü ve Alman Sat1 televizyon kanalı tarafından verilen "sinematik yeni yetenek" ödülünü almasını sağladı. Yavaş, 2006 yılında ise ünlü Lüksemburglu yönetmen Andy Bausch'un Deepfrozen filminde, Peter Lohmeyer ile birlikte başrolü üstlendi.

Sanatçı, sinema filmlerinin yanı sıra, Alman televizyon sinemacılığında önemli bir yeri olan "Tatort" adlı polisiye dizilerde de rol alıyor. Yavaş, 2005 yılından beri, Saarländischer Rundfunk kanalı tarafından hazırlanan Tatort dizilerinde, komiser Maximilian Brückner ve Gregor Weber ile birlikte çalışan alımlı adli tıp doktoru Rhea Singh'i canlandırıyor.

Filmografisi
 2003: Imbissness
 2005: Zeit der Wünsche
 2005: Tatort (dizi)
 2006: Tod eines Keilers
 2006: Der Letzte Zug
 2006: Deepfrozen
 2008: Hatırla Sevgili (dizi)
 2009: Kasaba (dizi)
 2012: Güzelliğin On Par'etmez - 2012 Antalya Altın Portakal Film Festivali En İyi Yardımcı Kadın Oyuncu Ödülü

Dış bağlantılar

 Lale Yavaş - Kurze   (Almanca)

1978 doğumlular
Türk kadın sinema oyuncuları
Yaşayan insanlar
Türk kadın dizi oyuncuları
Bern Üniversitesinde öğrenim görenler

Lale Yavaş


مسرحية الفيل يا ملك الزمان مسرحية للكاتب السوري سعد الله ونوس وللمخرج علاء الدين كوكش

القصة
تحكي قصة ملك ظالم له فيل مزعج ضار يرمز للقوة والبطش والجبروت يشكو منه الناس ويولولون ولا يجرؤ أحد منهم على الشكوى. وبعد ذلك يأتي شخص اسمه زكريا يشجعهم على الشكوى فيتحفزون ويتدربون على ما سيقومون به وبعد ذهابهم إلى الملك ووصولهم إليه عبر الزينات والبهارج يتغير موقفهم ويسيطر الخوف عليهم من جديد فيقولون للملك الفيل يا ملك الزمان ويكررونها. وعندما يسألهم ما شأنه لا يجرؤون على الشكوى وإنما يقولون أنهم جاؤوا يقترحون تزويجه. وافق  الملك على فكرة رعيته وأمر فرماناته باحضار فيلة وأمر بمكافئة زكريا وتعيينه مرافقا دائما للفيل كما أمر بإقامة فرح عام ليلة العرس.
ملاحظه :الكاتب ترك المسرحيه بدون نهايه

من حوار المسرحية
يتصدى زكريا للوضع فيحض مجموعة من الرجال على الشكوى :

صبرنا على الفقر والضرائب والاوبئة والمظالم وأعمال السخرة فإلى متى؟

وعندما يسأله الرجال ما ينبغي فعله يجيبهم : نشكو أمرنا للملك ونرجو أن يرد أذى الفيل عنا ربما الملك لا يعرف ما يفعله فيله

يتفق الرجال على أن يشكو أمرهم للملك فيبدأ زكريا بتدريبهم على النظام وعلى أن تكون كلمتهم واحدة وصوتهم واحد فيبدأ هو الكلام قائلا
- الفيل يا ملك الزمان
ويكملون وراءه :
قتل محمد بن فهد
-كسر النخيل
-هدم بيت إبراهيم
-يقتل الخراف
-يدوس الدجاج
-يظهر الموت إذا بان
-جعل الرعية بلا أمان

وهكذا يظل زكريا يدربهم على المقابلة والكلام حتى اعتقد أنهم حفظوا أدوارهم عند ذلك يطلب مقابلة الملك ويأذن لهم الحرس بالدخول فتتلامح على وجوههم علامات الخوف والخشوع وكلما تقدموا خطوة زادت رهبتهم وارتباكهم أمام ما يرونه من نوافير كالخيال ورخام كاللؤلؤ وجدران تلمع كالنهار وسجاد تغوص به الاقدام وحراس وجوههم كالفولاذ والملك يتألق كالشهاب والجميع خافضو الرؤوس إلى حد الانحناء ثم لا يجرؤون على النهوض

-الملك : ماذا تريد الرعية من ملكها

-زكريا : الفيل يا ملك الزمان

-الملك : وما خبر الفيل

-زكريا : الفيل يا ملك الزمان

-الملك : كاد صبري ينفذ تكلم ما خطب الفيل

-زكريا متلفتا حول الناس فاذا هم صم بكم لا ينطقون رهبة ورعبا وكان عليه أن ينقذ رأسه من القطع فتدارك نفسه قائلا:

الفيل بحاجة لفيلة تخفف وحدته وتنجب عشرات بل مئات الفيلة

-الملك (مقهقها) : كنت أقول دائما اني محظوظ برعيتي

مسرحية رائعة قدمت وجسدت احداثها على المسرح في سوريا والكويت وأكثر من بلد عربي.

عروض وترجمات
عرضت في كل الدول العربية، وترجمت إلى البولونية.

مراجع

ثقافة سورية
مسرحيات سعد الله ونوس
مسرح القرن 20

الفيل يا ملك الزمان (مسرحية)