_id
stringlengths 77
96
| datasets_id
int32 0
1.38M
| wiki_id
stringlengths 2
9
| start_paragraph
int32 2
1.17k
| start_character
int32 0
70.3k
| end_paragraph
int32 4
1.18k
| end_character
int32 1
70.3k
| article_title
stringlengths 1
250
| section_title
stringlengths 0
1.12k
| passage_text
stringlengths 1
14k
|
---|---|---|---|---|---|---|---|---|---|
{"datasets_id": 247, "wiki_id": "Q280110", "sp": 10, "sc": 455, "ep": 10, "ec": 895} | 247 | Q280110 | 10 | 455 | 10 | 895 | A38(M) motorway | Tidal flow | In the evening rush hour, this pattern is reversed and four lanes are made available to outbound traffic and two lanes towards the city centre. At all other times, the road runs with three lanes in each direction.
Motorcycles are banned from the red-surfaced central lane, which contains a drainage channel, regardless of how it is being used. This follows a fatal accident which occurred when one of the drainage covers dislodged. |
{"datasets_id": 248, "wiki_id": "Q620736", "sp": 2, "sc": 0, "ep": 6, "ec": 761} | 248 | Q620736 | 2 | 0 | 6 | 761 | ABNT NBR 15601 | Introduction | ABNT NBR 15601 Introduction The transmission aspects of the Brazilian Digital Terrestrial Television Standards are described in the ABNT NBR 15601:2007 - Digital terrestrial television - Transmission system document published by ABNT, the Brazilian Association of Technical Standards (Associação Brasileira de Normas Técnicas).
Digital terrestrial television broadcasting in Brazil should be introduced in the VHF/UHF bands and fit into existing 6 MHz channels originally intended for analogue television transmission. The Digital Terrestrial Television Broadcasting service will coexist with existing analogue television transmissions for a temporary period.
It was desirable to support the simultaneous transmission of a hierarchy of nested quality levels, including high |
{"datasets_id": 248, "wiki_id": "Q620736", "sp": 6, "sc": 761, "ep": 10, "ec": 533} | 248 | Q620736 | 6 | 761 | 10 | 533 | ABNT NBR 15601 | Introduction & Summary | definition television (HDTV) and standard definition TV (SDTV) within a single channel. Summary Transmission requirements established for the Brazilian digital television standards comply with the general characteristics existing in its Japanese counterpart, while addressing the challenges of broadcasting within a more polluted and unregulated spectrum environment.
The additional requirements set by the document ABNT NBR 15601:2007 - Digital terrestrial television – Transmission can be seen as evolutions suggested for better overall performance levels in the transition period between analog and digital television. |
{"datasets_id": 249, "wiki_id": "Q4651520", "sp": 2, "sc": 0, "ep": 10, "ec": 432} | 249 | Q4651520 | 2 | 0 | 10 | 432 | AFL Canada | History & National teams | AFL Canada History The Canadian Australian Football Association was established in May 1989 when two clubs, the Mississauga Mustangs (now the High Park Demons) and the Toronto Panthers, were formed and played in the inaugural Conacher Cup game in Toronto, Ontario. National teams AFL Canada selects the Northwind, Canada's national men's Australian rules football team. The team plays in international tournaments and exhibition matches against other countries. Northwind players are selected from the best Canadian-born players from the club teams across the country.
The Northwind's first international competition was against the USA before competing the 2002 Australian Football International Cup and |
{"datasets_id": 249, "wiki_id": "Q4651520", "sp": 10, "sc": 432, "ep": 14, "ec": 494} | 249 | Q4651520 | 10 | 432 | 14 | 494 | AFL Canada | National teams & Australian Football International Cup | finishing 9th of 11.
AFL Canada also selects the Northern Lights and the Wolfpack, Canada's national teams for women and junior men. Australian Football International Cup The Northwind have competed at the Australian Football International Cup since their first appearance in 2002. The International Cup is a competition where players that are citizens of the countries who are competing are the only players allowed to play (no expatriate Australians are permitted to play, with teams composed solely of amateurs who must be nationals of the country they represent).
In the 2002 Australian Football International Cup the Canada Northwind finished 9th of 11 |
{"datasets_id": 249, "wiki_id": "Q4651520", "sp": 14, "sc": 494, "ep": 14, "ec": 1246} | 249 | Q4651520 | 14 | 494 | 14 | 1,246 | AFL Canada | Australian Football International Cup | teams.
Round 1: Ireland 7.14 (56) def. Canada 4.7 (31) - Trevor Barker Beach Oval, Sandringham, Melbourne
Round 2: Canada 4.11 (38) def. South Africa 1.5 (11)
Round 3: New Zealand 10.8 (68) def. Canada 2.6 (18)
Round 4: USA 8.4 (52) def. Canada 1.1 (7)
Round 5: Samoa 9.15 (69) def. Canada 0.5 (5)
9th/10th Place Playoff: Canada 6.5 (41) def. Japan 5.2 (32)
In the 2005 Australian Football International Cup the Northwind finished 7th of 10 teams.
Round 1: Ireland 4.7 (31) def. Canada 3.5 (23)
Round 2: Papua New Guinea 5.11 (41) def. Canada 4.3 (27)
Round 3: Samoa 7.4 (46) |
{"datasets_id": 249, "wiki_id": "Q4651520", "sp": 14, "sc": 1246, "ep": 14, "ec": 2029} | 249 | Q4651520 | 14 | 1,246 | 14 | 2,029 | AFL Canada | Australian Football International Cup | def. Canada 6.6 (42)
Round 4: Great Britain 3.7 (25) def. 3.5 Canada (23)
Qualifying Final: Canada def. Spain (Spain forfeited).
7th/8th Place Playoff: Canada 4.5 (29) def. South Africa 2.6 (18)
In the 2008 Australian Football International Cup the Northwind finished 6th of 16 teams:
Round 1: Canada Northwind 18.22 (130) def. Finland Icebreakers 0.0 (0) - Western Oval
Round 2: Canada Northwind 16.12 (108) def. Sweden Elks 1.1 (7) - Ransford Oval
Round 3: Ireland Warriors 4.6 (30) def. Canada Northwind 2.2 (14) - Reid Oval
Finals Round 1: Canada Northwind 7.7 (49) def. Japan Samurais 0.3 (3) - Walter Oval
5th/6th Place |
{"datasets_id": 249, "wiki_id": "Q4651520", "sp": 14, "sc": 2029, "ep": 14, "ec": 2664} | 249 | Q4651520 | 14 | 2,029 | 14 | 2,664 | AFL Canada | Australian Football International Cup | Playoff: Nauru Chiefs 12.8 (80) def. Canada Northwind 7.7 (49) - Ransford Oval
In the 2011 Australian Football International Cup the Northwind finished 10th of 18 teams
Group 6 - Match 1: Canada 2.0 (12) def. by United States 2.3 (15) - Blacktown International Sportspark 2
Group 6 - Match 2: Canada 3.6 (24) def. Peres Team for Peace 0.0 (0) - Blacktown International Sportspark 2
Division 1 - Group 1 - Match 1: Canada 2.3 (15) def. by Great Britain 6.8 (44) - Blacktown International Sportspark 2
Division 1 - Group 1 - Match 3: Canada 3.2 |
{"datasets_id": 249, "wiki_id": "Q4651520", "sp": 14, "sc": 2664, "ep": 14, "ec": 3334} | 249 | Q4651520 | 14 | 2,664 | 14 | 3,334 | AFL Canada | Australian Football International Cup | (20) def. by New Zealand 5.9 (39) - Blacktown International Sportspark 1
Division 1 Semi-Finals: Canada 13.8 (86) def. Japan 2.1 (13) - McAllister Oval
9th/10th Place Playoff: Canada 6.4 (40) def. by Tonga 6.10 (46) - Ransford Oval
In the 2014 Australian Football International Cup the Northwind finished 5th of 18 teams.
Pool C - Round 1: Canada 19.5 (119) def. China 0.1 (1) - McAlister Oval
Pool C - Round 2: Canada 2.8 (20) def. by USA 8.3 (51) - Ransford Oval
Pool C - Round 3: Canada 20.10 (130) def. Sweden 0.0 (0) - Ben Kavanagh Reserve
Division |
{"datasets_id": 249, "wiki_id": "Q4651520", "sp": 14, "sc": 3334, "ep": 14, "ec": 3523} | 249 | Q4651520 | 14 | 3,334 | 14 | 3,523 | AFL Canada | Australian Football International Cup | 1 Semi Finals: Canada 9.15 (69) def. France 2.3 (15) - Ransford Oval
Division 1 Championship (5th/6th Place Playoff): Canada 9.7 (61) def. Tonga 7.6 (48) - McAlister Oval |
{"datasets_id": 250, "wiki_id": "Q4652285", "sp": 2, "sc": 0, "ep": 6, "ec": 552} | 250 | Q4652285 | 2 | 0 | 6 | 552 | ALCO FA | Service history | ALCO FA Service history The FAs, as well as their cousins, the ALCO PAs, were born as a result of Alco's development of a new diesel engine design, the Model 244. In early 1944, development started on the new design, and by November 1945, the first engines were beginning to undergo tests. This unusually short testing sequence was brought about by the decision of Alco's senior management that the engine and an associated line of road locomotives had to be introduced no later than the end of 1946.
In preparation for this deadline, by January 1946, the first four |
{"datasets_id": 250, "wiki_id": "Q4652285", "sp": 6, "sc": 552, "ep": 6, "ec": 1137} | 250 | Q4652285 | 6 | 552 | 6 | 1,137 | ALCO FA | Service history | locomotives with the 244 engines had been built. Two FA-1s and an FB-1 were painted in Alco Demonstrator colors and were released for road tests for a month and a half on the Delaware and Hudson Railway.
A strike at Alco delayed production beyond the first four units and the three demonstrator units began working on the Gulf, Mobile and Ohio Railroad in mid February 1946. The demonstrators were returned to Schenectady when the remainder of the order began delivery in May 1946.
The GM&O order was completed in April 1947 for a total of 80 units. Before the end of |
{"datasets_id": 250, "wiki_id": "Q4652285", "sp": 6, "sc": 1137, "ep": 6, "ec": 1736} | 250 | Q4652285 | 6 | 1,137 | 6 | 1,736 | ALCO FA | Service history | this production run, Alco upgraded the generators and traction motors in the locomotives, with the first of these models entering service in February 1947 for the New York Central.
In 1950, the Montreal Locomotive Works, an affiliate of Alco, began production of FAs as well. In the Fall of 1950, an upgraded model, the FA-2, was launched. This model featured an uprated Model 244 engine, with an output of 1600 horsepower. Additionally, the carbody was lengthened, making possible the addition of a steam generator in the A unit to allow for use in passenger service. Models equipped as |
{"datasets_id": 250, "wiki_id": "Q4652285", "sp": 6, "sc": 1736, "ep": 6, "ec": 2295} | 250 | Q4652285 | 6 | 1,736 | 6 | 2,295 | ALCO FA | Service history | such were designated the FPA-2/FPB-2.
The first FA-2s were delivered in October 1950 to the Baltimore and Ohio and the Erie. By this time, however, the cab unit had fallen out of favor due to the greater versatility of road switchers, and U S production of the FA line ended in 1956, with Canadian production ending in 1959.
The MTA Long Island Rail Road purchased 20 units and removed the traction motors from the units. the LIRR used them to supply AC HEP (head end power) to the cars of the train. Also the engines were used as a cab when |
{"datasets_id": 250, "wiki_id": "Q4652285", "sp": 6, "sc": 2295, "ep": 10, "ec": 455} | 250 | Q4652285 | 6 | 2,295 | 10 | 455 | ALCO FA | Service history & Models overview | another engine was pushing on the east end of the train. By the late 1990s and early 2000s, the railroad began retiring the Alcos for new double deck cab cars. Models overview Three different models were offered. The FA-1/FB-1, which featured a 1,500 horsepower (1,100 kW) rating, was built from January 1946 to October 1950 with a 1,600 hp (1,200 kW) version produced between March and August 1950 (many early models were subsequently upgraded to 1,600 hp). The 1,600 hp (1,200 kW) FA-2/FB-2 (along with the FPA-2/FPB-2 variants) was built between October 1950 and June 1956. The 1,800 hp (1,300 kW) FPA-4/FPB-4, powered by the |
{"datasets_id": 250, "wiki_id": "Q4652285", "sp": 10, "sc": 455, "ep": 10, "ec": 1128} | 250 | Q4652285 | 10 | 455 | 10 | 1,128 | ALCO FA | Models overview | 251 V-12 engine, was built between October 1958 and May 1959 by ALCO's Canadian subsidiary, Montreal Locomotive Works (MLW).
Externally, the FA-1/FB-1 could be distinguished from the FA-2/FB-2 (FPA-2/FPB-2) by the position of the radiator shutters – the FA-1/FB-1's shutters were at the far end of the carbody, whereas on the FA-2/FB-2 they were further forward, the design having been modified to allow the installation of a steam generator behind the radiator. The FPA-4/FPB-4 were visually different due to the additional radiator space that was positioned below the shutters. These Canadian variants were intended and used for high-speed passenger service, and |
{"datasets_id": 250, "wiki_id": "Q4652285", "sp": 10, "sc": 1128, "ep": 10, "ec": 1718} | 250 | Q4652285 | 10 | 1,128 | 10 | 1,718 | ALCO FA | Models overview | remained in use into the 1990s on Via Rail Canada.
The FA had the same distinctive styling as its larger cousin, the ALCO PA, with a long, straight nose tipped by a headlight in a square, slitted grille and raked windshields. Only the first 36 GM&O FA-1s had the distinctive trim pieces found behind the cab windows of the PA. As with the PA, the overall design owed much to the Fairbanks-Morse Erie-built design, which had been constructed by ALCO's sales partner General Electric (GE) at their Erie, Pennsylvania, plant. GE's industrial designer Ray Patten styled the FA and FB, |
{"datasets_id": 250, "wiki_id": "Q4652285", "sp": 10, "sc": 1718, "ep": 10, "ec": 2316} | 250 | Q4652285 | 10 | 1,718 | 10 | 2,316 | ALCO FA | Models overview | and many believe it likely that he took drawings of the Erie-built as a starting point, lengthening and squaring the nose and giving it a more aggressive look. The majority of FA components were compatible with the PA.
As with the PA, the model 244 diesel prime mover proved to be the undoing of the FA, and the locomotives failed to capture a marketplace dominated by General Motors Electro-Motive Division (EMD). The later 251-series engine, a vastly improved prime mover, was not available in time for ALCO to recover the loss of reputation caused by the unreliability of the 244, which |
{"datasets_id": 250, "wiki_id": "Q4652285", "sp": 10, "sc": 2316, "ep": 14, "ec": 239} | 250 | Q4652285 | 10 | 2,316 | 14 | 239 | ALCO FA | Models overview & ALCO "World Locomotive" | was a key factor in the dissolution of the partnership with GE. By the time the ALCO 251 engine was accepted into widespread use, General Electric had launched their own entries into the diesel-electric locomotive market, notably the U25B. General Electric eventually supplanted ALCO as a manufacturer of locomotives, leading to ALCO's exit from the locomotive market in 1969. ALCO "World Locomotive" Alco built 23 A1A-A1A trucked FCA-3s for Pakistan Railways in 1951 and 1953. These were the equivalent of an FPA-2 riding on A1A trucks. ALCO's "World Locomotive", the DL500 (introduced in 1953), originated as a newly designed demonstrator |
{"datasets_id": 250, "wiki_id": "Q4652285", "sp": 14, "sc": 239, "ep": 14, "ec": 812} | 250 | Q4652285 | 14 | 239 | 14 | 812 | ALCO FA | ALCO "World Locomotive" | based on the FA-2. The first 25 DL500s used the model 244 engine rated at 1,600 horsepower (1,200 kW). Later DL500s were like the FPA-4 and utilize the ALCO model 251B diesel engine as the prime mover and are rated at 1,800 horsepower (1,300 kW). All DL500s were built with C-C trucks, but B-B or paired A-1-A trucks were offered as an option. The only locale within the Americas where ALCO-built cab units, such as All America Latina Logistica (ALL), still see daily usage in freight duty is Argentina. A total of 369 DL500 locomotives were built by ALCO, AE Goodwin, and |
{"datasets_id": 250, "wiki_id": "Q4652285", "sp": 14, "sc": 812, "ep": 14, "ec": 1423} | 250 | Q4652285 | 14 | 812 | 14 | 1,423 | ALCO FA | ALCO "World Locomotive" | MLW between May 1953 and December 1967.
Variants of the ALCO "World Locomotive" saw service in Australia where it was built under license by AE Goodwin. A two cab design, the second cab being flat fronted, went into service on the standard gauge Department of Railways New South Wales as the 44 class No.s 4401 - 44100 (100 in class), and both a single cab and double cab design went into service on the 5 ft 3 in (1,600 mm) broad gauge South Australian Railways as the 930 class.
The NSWGR 44 class ALCo was used from fast passenger services to slow freight.
Similar DL500 locomotives |
{"datasets_id": 250, "wiki_id": "Q4652285", "sp": 14, "sc": 1423, "ep": 18, "ec": 175} | 250 | Q4652285 | 14 | 1,423 | 18 | 175 | ALCO FA | ALCO "World Locomotive" & Popular culture | were also used in Greece, India (DL560C), Pakistan, Peru, and Spain. Popular culture A February 2014 episode of the TV series The Big Bang Theory, "The Locomotive Manipulation", takes place on a train pulled by what is incorrectly described as an "Alcoa FA-4". |
{"datasets_id": 251, "wiki_id": "Q4653023", "sp": 2, "sc": 0, "ep": 8, "ec": 394} | 251 | Q4653023 | 2 | 0 | 8 | 394 | ANR Pipeline | History | ANR Pipeline ANR Pipeline delivers gas from Texas, the Oklahoma panhandle region, and Louisiana to the Midwest and Great Lakes region. It has two legs, one from Texas and the other from Louisiana, which meet near Chicago. History ANR was founded as the Michigan-Wisconsin Pipe Line Company on July 25, 1945. In 1947, the company received federal approval to build a $52 million, 1,800-mile-long pipeline from Texas to the Detroit-Ann Arbor area and to sections of Wisconsin, Missouri and Iowa. The Michigan-Wisconsin Pipeline began operations on November 1, 1949. The pipeline ran from Hansford County in the Texas Panhandle |
{"datasets_id": 251, "wiki_id": "Q4653023", "sp": 8, "sc": 394, "ep": 14, "ec": 10} | 251 | Q4653023 | 8 | 394 | 14 | 10 | ANR Pipeline | History & Incidents & Explosion of 2008 | through Oklahoma, Kansas, Nebraska, Missouri and Iowa to Illinois, where it branches in two with one line to serve Michigan and the other Wisconsin.
The Michigan-Wisconsin Pipe Line Company's name was changed in 1984 to the ANR Pipeline Company, in order to identify the company more closely with its parent, American Natural Resources. In 1985, American Natural Resources was acquired by Coastal Corporation. El Paso Energy acquired Coastal Corporation in 2001. El Paso Energy sold ANR Pipeline to TransCanada Corporation in 2007. Incidents Explosion of 1993
On November 23rd, 1993 there was an explosion on the pipeline in New Castle, Indiana. Explosion |
{"datasets_id": 251, "wiki_id": "Q4653023", "sp": 14, "sc": 9, "ep": 20, "ec": 152} | 251 | Q4653023 | 14 | 9 | 20 | 152 | ANR Pipeline | Explosion of 2008 & Rupture of 2014 | of 2008 On March 11, 2008, an explosion occurred on the pipeline 15 miles (24 km) off the coast of Marsh Island, Louisiana, in the Gulf of Mexico, while the Motor Vessel Jillian Morrison was bleeding natural gas from a shut section of a pipeline into a tank on the vessel. Six crew members of the vessel were injured and one left missing. Rupture of 2014 On September 16, 2014, around 2am EDT, a rupture occurred on the pipeline in Benton Township, Berrien County, Michigan. About 520 people were evacuated. |
{"datasets_id": 252, "wiki_id": "Q295795", "sp": 2, "sc": 0, "ep": 6, "ec": 569} | 252 | Q295795 | 2 | 0 | 6 | 569 | ANTIC | The Display List | ANTIC The Display List The Display List is the list of instructions, or the program, directing ANTIC how to generate the display. The data processed by this Display List "program" is the screen memory. The output is the graphics display. The kinds of graphics in the output (text vs addressable pixels) is determined by the instructions in the Display List.
The Display List and the display data are written into RAM by the CPU. ANTIC reads the Display List instructions, screen memory, and character set information from RAM using a technique known as direct memory access (DMA). |
{"datasets_id": 252, "wiki_id": "Q295795", "sp": 6, "sc": 569, "ep": 6, "ec": 1225} | 252 | Q295795 | 6 | 569 | 6 | 1,225 | ANTIC | The Display List | A BASIC or 6502 machine language program's job is to initialize the display—set up the Display List instructions, organize screen memory (and character set if applicable), and then direct ANTIC to start the display. After this, ANTIC automatically takes care of generating the screen display. This allows the Atari 8-bit computers to produce complex, mixed-mode displays without direct CPU intervention. Other platforms, even those designed much later, cannot either mix graphics modes in one display, or do so without complex CPU interrupts.
ANTIC processes the instructions in the Display List, reads the screen memory (and character set data |
{"datasets_id": 252, "wiki_id": "Q295795", "sp": 6, "sc": 1225, "ep": 6, "ec": 1839} | 252 | Q295795 | 6 | 1,225 | 6 | 1,839 | ANTIC | The Display List | if applicable), translates this information into a real-time stream of graphics data, and sends this data stream to the CTIA/GTIA chip which applies the color to the graphics pixels and outputs the video. Together the two chips provide 6 text and 8 graphics modes (14 total). The more advanced version, GTIA, adds three alternative color interpretations for each ANTIC graphics mode providing a total of 56 (14 times four) graphics modes. However, only the ANTIC graphics modes based on half-color clock pixels are capable of expressing the complete color palette provided by the new color interpretations, and |
{"datasets_id": 252, "wiki_id": "Q295795", "sp": 6, "sc": 1839, "ep": 10, "ec": 268} | 252 | Q295795 | 6 | 1,839 | 10 | 268 | ANTIC | The Display List & Instruction Execution | of those modes the ones convenient for use are ANTIC modes 2 (OS Graphics mode 0 text) and ANTIC mode F (OS Graphics mode 8). Thus the reasonable number of unique graphics modes available using the inherent hardware capabilities of ANTIC + CTIA/GTIA is 20–14 ANTIC modes + 3 additional color interpretations each for ANTIC modes 2 and F. Instruction Execution ANTIC begins executing the Display List pointed to by the 16-bit address in registers DLISTL/DLISTH ($D402-$D403ₕₑₓ/54274-54275dec). The address registers are incremented by ANTIC automatically as each instruction is executed. ANTIC can only update the lowest 10 bits |
{"datasets_id": 252, "wiki_id": "Q295795", "sp": 10, "sc": 268, "ep": 10, "ec": 921} | 252 | Q295795 | 10 | 268 | 10 | 921 | ANTIC | Instruction Execution | of the address during the automatic increment limiting the display list to begin and end within a 1K address range.
The registers are also updated during Display List execution by ANTIC's JMP (Jump) and JVB (Jump and wait for Vertical Blank). These instructions load the full 16-bits of address, so can be used to circumvent the 1K Display List limitation.
The address is also updated by the Operating System's Vertical Blank Interrupt (VBI) routine using the values from Operation System shadow registers SDLSTL/SDLSTH ($0230-$0231ₕₑₓ/560-561dec). When the OS VBI routine is enabled direct updates to the ANTIC DLIST registers by the |
{"datasets_id": 252, "wiki_id": "Q295795", "sp": 10, "sc": 921, "ep": 14, "ec": 306} | 252 | Q295795 | 10 | 921 | 14 | 306 | ANTIC | Instruction Execution & HS Modifer - Horizontal Fine Scroll | CPU or the ANTIC Jump instructions will be overwritten by the OS during the next Vertical Blank. Since VBI processing is the usual state of the system, most programs rely on this and only update the OS shadow registers (SDLSTL/SDLSTH $0230-$0231ₕₑₓ/560-561dec) to set the Display List. HS Modifer - Horizontal Fine Scroll Bit4: position value $10, controls horizontal scrolling of the playfield mode.
When horizontal scrolling is enabled ANTIC retrieves more screen memory bytes than displayed in order to show partially scrolled display bytes at the beginning and end of the line. If the display is in Narrow mode ANTIC |
{"datasets_id": 252, "wiki_id": "Q295795", "sp": 14, "sc": 306, "ep": 18, "ec": 107} | 252 | Q295795 | 14 | 306 | 18 | 107 | ANTIC | HS Modifer - Horizontal Fine Scroll & VS Modifer - Vertical Fine Scroll | retrieves the number of screen bytes necessary for Normal mode. If the display is in Normal mode ANTIC retrieves the number of bytes needed for Wide screen mode. In Wide screen mode ANTIC does not retrieve any additional screen bytes. Scrolling in Wide screen will cause blank data to be shifted into the scrolled area. This is not a problem, because it occurs in the overscan area which is not visible on a normal NTSC/PAL display. VS Modifer - Vertical Fine Scroll Bit5: position value $20, controls vertical scrolling of the Playfield mode.
The Vertical scrolling |
{"datasets_id": 252, "wiki_id": "Q295795", "sp": 18, "sc": 107, "ep": 22, "ec": 193} | 252 | Q295795 | 18 | 107 | 22 | 193 | ANTIC | VS Modifer - Vertical Fine Scroll & LMS Modifer - Load Memory Scan | region in a display is defined by setting the VS bit ($20) on a sequential series of ANTIC Mode Lines in the Display List. The first Mode line without the VS bit set becomes the end of the scrolling region and is used as a buffer line to supply the new information to scroll up into the bottom of the scrolling region. LMS Modifer - Load Memory Scan Bit6: position value $40, loads a new address for the start of screen memory for the current Playfield mode line.
The LMS option loads ANTIC's screen memory scan address with the 16-bit |
{"datasets_id": 252, "wiki_id": "Q295795", "sp": 22, "sc": 193, "ep": 22, "ec": 763} | 252 | Q295795 | 22 | 193 | 22 | 763 | ANTIC | LMS Modifer - Load Memory Scan | value in the two bytes following the instruction. The Character or Map mode specified will begin displaying bytes from that address. The LMS option must appear in the first Playfield Mode Instruction line (not Blank Line) in the Display List to initialize ANTIC to begin reading at the start of screen memory. Most of the Operating System-generated full screen modes will have only that one occurrence of the LMS modifier present in the Display List. ANTIC will automatically increment its LMS address at the end of each mode line in preparation for the next line. |
{"datasets_id": 252, "wiki_id": "Q295795", "sp": 22, "sc": 763, "ep": 22, "ec": 1352} | 252 | Q295795 | 22 | 763 | 22 | 1,352 | ANTIC | LMS Modifer - Load Memory Scan | As long as screen memory does not cross over a 4K boundary the LMS modifier is not needed on subsequent Playfield Mode Instructions.
Full screen displays using Playfield Map Modes E or F will have a second occurrence of the LMS modifier on a Map Instruction near the middle of the screen, since the full display requires more than 4K of screen memory. (Mode F displays include high res 320 pixel lines, and the GTIA display modes.)
Combining the Map and Character Mode instructions with the LMS bit makes it possible to set the screen memory address freely within the 64K |
{"datasets_id": 252, "wiki_id": "Q295795", "sp": 22, "sc": 1352, "ep": 26, "ec": 236} | 252 | Q295795 | 22 | 1,352 | 26 | 236 | ANTIC | LMS Modifer - Load Memory Scan & DLI Modifer - Display List Interrupt | address space independently for each display line. In other words, the screen memory does not have to be completely contiguous memory scanned sequentially towards higher addresses - only that a single Mode line must be provided with adequate sequential bytes of memory to meet the requirements of that Mode, width of the display, and Scrolling feature. DLI Modifer - Display List Interrupt Bit7: position value $80, directs ANTIC to invoke a CPU-serviced interrupt on the last scan line of the Playfield Mode.
If ANTIC register NMIEN ($D40Eₕₑₓ/54286dec) has Bit7 ($80) set then on the last scanline of the Mode line an |
{"datasets_id": 252, "wiki_id": "Q295795", "sp": 26, "sc": 236, "ep": 26, "ec": 871} | 252 | Q295795 | 26 | 236 | 26 | 871 | ANTIC | DLI Modifer - Display List Interrupt | interrupt routine will be triggered which is vectored through address VDSLST ($200ₕₑₓ/512dec).
The 6502 Accumulator, X and Y register contents are not preserved before entry to the DLI routine. It is the responsibility of the DLI routine to save the state of the registers used during the DLI, and then restore the original values of the registers before exiting with an RTI instruction. Routines typically push the register values to the 6502 stack.
DLI routines are ordinarily short and quick, changing the color registers or Player-Missile positions before exiting. However, brevity is not required. As long as |
{"datasets_id": 252, "wiki_id": "Q295795", "sp": 26, "sc": 871, "ep": 30, "ec": 463} | 252 | Q295795 | 26 | 871 | 30 | 463 | ANTIC | DLI Modifer - Display List Interrupt & Playfield Graphics Modes | the DLI routine exits before the start of the next DLI routine the DLI routine can continue updating values across multiple scanlines. Playfield Graphics Modes The ANTIC chip allows a variety of different Playfield modes and widths. However, the original Atari Operating System included with the Atari 800/400 computers provides easy access to a limited subset of these graphics modes. ANTIC Playfield modes are exposed to users through Atari BASIC via the "GRAPHICS" command, and to some other languages, via similar system calls. Oddly, the modes not directly supported by the original OS and BASIC are modes most useful |
{"datasets_id": 252, "wiki_id": "Q295795", "sp": 30, "sc": 463, "ep": 30, "ec": 1100} | 252 | Q295795 | 30 | 463 | 30 | 1,100 | ANTIC | Playfield Graphics Modes | for games. The later version of the OS used in the Atari 8-bit XL/XE computers added support for most of these "missing" graphics modes.
The ANTIC chip uses a Display List and other settings to create these modes. Any graphics mode in the default GTIA color interpretation can be freely mixed without CPU intervention by changing instructions in the Display List.
The ANTIC screen geometry is not fixed. A hardware register can direct ANTIC to display narrow playfield (128 color clocks/256 hi-res pixels wide), normal width playfield (160 color clocks/320 hi-res pixels wide), and wide, overscan playfield (192 color |
{"datasets_id": 252, "wiki_id": "Q295795", "sp": 30, "sc": 1100, "ep": 30, "ec": 1695} | 252 | Q295795 | 30 | 1,100 | 30 | 1,695 | ANTIC | Playfield Graphics Modes | clocks/384 hi-res pixels wide). While the Operating System's default height for graphics modes is 192 scan lines Antic can display vertical overscan up to 240 TV scan lines tall by creating a custom Display List.
Mode F produces colors through NTSC artifacting and works in a similar manner to the Apple II's graphics modes. The pixel resolution is 320 across but the color resolution half that, thus each group of two pixels will "blend" together to form a single color and four artifact colors may be generated this way. They will be tinted if the foreground and background color are |
{"datasets_id": 252, "wiki_id": "Q295795", "sp": 30, "sc": 1695, "ep": 30, "ec": 2287} | 252 | Q295795 | 30 | 1,695 | 30 | 2,287 | ANTIC | Playfield Graphics Modes | set to something other than black/white/gray. The exact colors produced this way vary with different Atari 8-bit models and also between the CTIA and GTIA chips, thus undesirable artifact colors may result from running software that uses Mode F on a machine other than the one it was developed for. It was not possible to obtain artifact coloring on PAL machines and Mode F will be monochrome on them.
Mode F was not widely used by software due to its high memory requirements (8k) and inconsistent artifact colors that did not appear the same on every model of Atari 8-bit computer. |
{"datasets_id": 252, "wiki_id": "Q295795", "sp": 30, "sc": 2287, "ep": 30, "ec": 2921} | 252 | Q295795 | 30 | 2,287 | 30 | 2,921 | ANTIC | Playfield Graphics Modes | Games that utilize it include Sierra graphical adventures such as Troll's Tale and Wizard and the Princess, Lode Runner, and the Ultima series.
The video display system was designed with careful consideration of NTSC display methods and limitations. The system CPU clock and video hardware are synchronized to one-half the NTSC clock frequency. Consequently, the pixel output of all display modes is based on the size of the NTSC color clock which is the minimum time needed to guarantee correct and consistent color regardless of the pixel's horizontal location on the screen. The result is accurate pixel size and coloring |
{"datasets_id": 252, "wiki_id": "Q295795", "sp": 30, "sc": 2921, "ep": 34, "ec": 308} | 252 | Q295795 | 30 | 2,921 | 34 | 308 | ANTIC | Playfield Graphics Modes & Scrolling | that does not display color "strobing" defects when horizontally scrolled. (Color strobing is unsightly hue changes in pixels based on horizontal position which is caused when signal changes do not align with the color clock and so do not provide the TV/monitor hardware adequate time to reach the correct color.) Scrolling Before video displays became a common part of the user interface many computers used a teletype—a printer usually with continuously-fed paper. User input and the computer generated output were printed on the paper fed through the printer. This widely understood interface for user input and computer output |
{"datasets_id": 252, "wiki_id": "Q295795", "sp": 34, "sc": 308, "ep": 34, "ec": 919} | 252 | Q295795 | 34 | 308 | 34 | 919 | ANTIC | Scrolling | continued with the introduction of video displays as computers presented a metaphor of the screen as a view port over an imagined, infinite roll of paper. Information is displayed on screen beginning at the top until it reaches the bottom of the screen and when the computer needs to introduce new information it shifts all the screen information up providing an empty space at the bottom for the new information and consequently erasing the topmost information.
This kind of scrolling is called, "coarse scrolling". It is achieved by moving bytes of memory through a designated screen display area. |
{"datasets_id": 252, "wiki_id": "Q295795", "sp": 34, "sc": 919, "ep": 34, "ec": 1500} | 252 | Q295795 | 34 | 919 | 34 | 1,500 | ANTIC | Scrolling | Moving a kilobyte (or more) of memory is CPU intensive and slower computers may not be able to accomplish anything else while updating screen data. As a means of animating a display the results can be jerky when the CPU cannot update the screen memory faster than the display hardware reads the memory to generate the video output. Motion fluidity is impaired, since the minimum amount of shifting the display is the size of an entire character. Most computers including the Atari 8-bits accomplish coarse scrolling as described above — common examples are viewing a long BASIC |
{"datasets_id": 252, "wiki_id": "Q295795", "sp": 34, "sc": 1500, "ep": 38, "ec": 40} | 252 | Q295795 | 34 | 1,500 | 38 | 40 | ANTIC | Scrolling & Vertical Coarse Scrolling | program listing or directory of files.
Coarse scrolling implemented by bulk movement of data is often the only method of scrolling possible on most computers. However, ANTIC provides direct hardware support for vertical and horizontal, coarse and fine scrolling taking the concept of a "view port moving over data" from a metaphorical illusion to literal implementation. These ANTIC features deliver rapid, smooth, full screen movement requiring negligible CPU time and so free the CPU for other work.
All ANTIC display modes, Text and Map modes, can exercise the hardware scrolling features. Vertical Coarse Scrolling Vertical coarse scrolling is the easiest |
{"datasets_id": 252, "wiki_id": "Q295795", "sp": 38, "sc": 40, "ep": 38, "ec": 624} | 252 | Q295795 | 38 | 40 | 38 | 624 | ANTIC | Vertical Coarse Scrolling | feature to exercise. The first Text or Map Mode instruction in every Display List always includes the LMS instruction modifier specifying the start of screen memory. As it generates the display, ANTIC automatically increments its memory scan pointer from Mode line to Mode line to display memory contiguously. Therefore, a display can be "moved" by merely updating the initial LMS modifier's address; adding the number of bytes used for a line in the current Text or Map Mode shifts the screen contents up one line while subtracting the same amount moves the screen down. So, the |
{"datasets_id": 252, "wiki_id": "Q295795", "sp": 38, "sc": 624, "ep": 38, "ec": 1215} | 252 | Q295795 | 38 | 624 | 38 | 1,215 | ANTIC | Vertical Coarse Scrolling | display is actually a view port that is moved to look at a different areas of memory rather than moving the memory into a fixed screen map.
Since ANTIC's memory scan counter cannot automatically increment over a 4K boundary the limit of vertical scrolling in this simple manner is up to 4K of movement. A full screen of Mode 2 text using approximately 1K can continuously scroll the height of four screens until reaching the 4K boundary. Likewise, a Mode 7 text display can scroll the height of 16 entire screens.
Naturally, that trivial example is of limited usefulness. |
{"datasets_id": 252, "wiki_id": "Q295795", "sp": 38, "sc": 1215, "ep": 38, "ec": 1828} | 252 | Q295795 | 38 | 1,215 | 38 | 1,828 | ANTIC | Vertical Coarse Scrolling | Many scrolling implementations scroll only part of the screen while other sections remain fixed. This problem is solved by the inherent capabilities of the ANTIC Display List. In this situation the Display List would add Mode instructions using LMS modifiers on the first mode line of the screen sections that should not move which effectively locks these parts of the display while the LMS modifier address for the scrolling section is updated.
Further enhancement of this concept uses the LMS modifier option on every line that does scroll. Vertical scrolling on this display requires updating one |
{"datasets_id": 252, "wiki_id": "Q295795", "sp": 38, "sc": 1828, "ep": 38, "ec": 2384} | 252 | Q295795 | 38 | 1,828 | 38 | 2,384 | ANTIC | Vertical Coarse Scrolling | LMS modifier address for each Mode line in the scrolling region. When the display is managed at this level of detail ANTIC's 4K screen RAM boundary can be easily circumvented. Even in this worst case example the CPU effort expended is a tiny fraction of the processing needed to bulk move screen data.
One other limit to be aware of is that the two byte LMS modifier address must not be updated when ANTIC is processing the LMS. If ANTIC reads the LMS address while it is partially updated ANTIC will display the incorrect section of memory for |
{"datasets_id": 252, "wiki_id": "Q295795", "sp": 38, "sc": 2384, "ep": 42, "ec": 126} | 252 | Q295795 | 38 | 2,384 | 42 | 126 | ANTIC | Vertical Coarse Scrolling & Vertical Fine Scrolling | that Mode line. When the scrolling region of a display requires multiple LMS address updates the possibility of a partial update increases, and the possibility of having two subsequent lines display the same data also increases. Programs solve this in a number of ways—performing updates during the Vertical blank, monitoring the VCOUNT before updates, or doing the updates in Display List Interrupts executed during sections of the display away from the scrolling region. Vertical Fine Scrolling Vertical Fine Scrolling allows single scan line movement of the scrolling region for Text and Map modes which are greater than |
{"datasets_id": 252, "wiki_id": "Q295795", "sp": 42, "sc": 126, "ep": 42, "ec": 706} | 252 | Q295795 | 42 | 126 | 42 | 706 | ANTIC | Vertical Fine Scrolling | one scan line tall. Vertical Fine Scrolling for Map modes only one scan line tall is logically not practical. The effect of vertical "fine" scrolling for single scan line Map modes can be performed using the easier coarse scrolling method.
Fine scrolling requires setup to define the scrolling region. This is done by setting the Vertical Scroll (VS) modifier bit in sequential Display List instructions. The first Mode line instruction without the VS bit set becomes the end of the scrolling region and is used as a buffer line to supply the new scan lines to scroll |
{"datasets_id": 252, "wiki_id": "Q295795", "sp": 42, "sc": 706, "ep": 42, "ec": 1273} | 252 | Q295795 | 42 | 706 | 42 | 1,273 | ANTIC | Vertical Fine Scrolling | up into the bottom of the scrolling region.
ANTIC's process of vertical fine scrolling works by simply directing ANTIC to skip a number of scan lines for the first mode line of the scrolling region. Subsequent Mode lines in the scrolling region are not affected. The last line of the region supplies the bottom border of the scrolling region displaying the number of scan lines that were removed from the first line. This number of scan lines is controlled with the VSCROL register. The value ranges from 0 to the ANTIC Mode line's scan line height - 1. |
{"datasets_id": 252, "wiki_id": "Q295795", "sp": 42, "sc": 1273, "ep": 46, "ec": 358} | 252 | Q295795 | 42 | 1,273 | 46 | 358 | ANTIC | Vertical Fine Scrolling & Horizontal Coarse Scrolling | The maximum value range covers fine scrolling 16 scan lines from 0 to 15.
When the fine scrolling limit is reached, scrolling continues by resetting the VSCROL value and performing a coarse vertical scroll of the scrolling region. Horizontal Coarse Scrolling Horizontal coarse scrolling requires a little more effort than vertical scrolling. While horizontal scrolling is expected to present the illusion of a view port moving left and right across a wide panoramic scene made of screen memory, ANTIC's automatic memory scan increment conflicts with this idea that the rows of screen data is wider than the display. |
{"datasets_id": 252, "wiki_id": "Q295795", "sp": 46, "sc": 358, "ep": 46, "ec": 1023} | 252 | Q295795 | 46 | 358 | 46 | 1,023 | ANTIC | Horizontal Coarse Scrolling | Presenting screen memory as long horizontal lines requires an LMS modifier for every Display List Text or Map Mode instruction in the scrolling region. A horizontal step is accomplished by incrementing or decrementing all the LMS addresses of the scrolling region.
Horizontal scrolling requires the same Display List implementation as the worst case example described for Vertical Coarse Scrolling. So, where Horizontal scrolling is implemented, vertical scrolling is also supported just by changing the value incrementing or decrementing the LMS addresses. The other benefit of this arrangement is that it is easy to manage screen memory around ANTIC's |
{"datasets_id": 252, "wiki_id": "Q295795", "sp": 46, "sc": 1023, "ep": 50, "ec": 443} | 252 | Q295795 | 46 | 1,023 | 50 | 443 | ANTIC | Horizontal Coarse Scrolling & Horizontal Fine Scrolling | 4K screen memory boundary limit.
See the Vertical Coarse Scrolling section for further discussion and time constraints when updating LMS modifier addresses. Horizontal Fine Scrolling Horizontal Fine Scrolling allows single color clock movement of the scrolling region for Text and Map modes. For all normal color interpretations this is by color clock, not pixel even when pixels are larger (or smaller) than the color clocks. ANTIC Modes using the alternate GTIA color interpretations must be scrolled by an entire GTIA pixel (two color clocks). Only even values should be used to ensure correct GTIA pixel scrolling. Odd |
{"datasets_id": 252, "wiki_id": "Q295795", "sp": 50, "sc": 443, "ep": 50, "ec": 1045} | 252 | Q295795 | 50 | 443 | 50 | 1,045 | ANTIC | Horizontal Fine Scrolling | values of HSCROL will shift the GTIA pixel stream into a different state that will be interpreted as different colors.
Fine scrolling requires setup to define the horizontal scrolling region. The first step is to start with a Display List using the LMS instruction modifier to specify starting address of each Mode line. This is done to organize screen memory as long rows of data for the display. The next step is setting the Horizontal Scroll (HS) modifier bit in all Display List Mode line instructions for the scrolling region.
This number of color clocks to shift is controlled |
{"datasets_id": 252, "wiki_id": "Q295795", "sp": 50, "sc": 1045, "ep": 50, "ec": 1604} | 252 | Q295795 | 50 | 1,045 | 50 | 1,604 | ANTIC | Horizontal Fine Scrolling | with the HSCROL register. The maximum HSCROL value range covers fine scrolling 16 color clocks from 0 to 15. The color clock information used is buffered from the beginning of the mode line (ANTIC's current memory scan pointer) using enough screen memory bytes to satisfy the 16 color clocks. Horizontal scrolling simply directs ANTIC how many color clocks it can output from the buffered 16 color clocks starting at the last (right most) color clock of the buffered memory. Zero (0) is no color clocks output from the buffer. 1 is the last (right most) |
{"datasets_id": 252, "wiki_id": "Q295795", "sp": 50, "sc": 1604, "ep": 54, "ec": 45} | 252 | Q295795 | 50 | 1,604 | 54 | 45 | ANTIC | Horizontal Fine Scrolling & Alternate Scrolling Methods | color clock of the buffer. The color clocks are inserted at the left edge of the screen, causing the scrolling area of the screen to shift to the right.
When the fine scrolling limit is reached, continue scrolling by resetting the HSCROL value and performing a coarse horizontal scroll of the scrolling region. ANTIC's 16 color clock range permits fine scrolling multiple Text Mode characters or more than one byte worth of Map mode pixels. Therefore, the update to the LMS addresses may add or subtract multiple bytes. Alternate Scrolling Methods An interesting use of ANTIC's DMA memory scan |
{"datasets_id": 252, "wiki_id": "Q295795", "sp": 54, "sc": 45, "ep": 54, "ec": 673} | 252 | Q295795 | 54 | 45 | 54 | 673 | ANTIC | Alternate Scrolling Methods | behavior permits a strategy for apparently long horizontal scrolling distances, but uses a fraction of the real memory required. As discussed in Horizontal Coarse Scrolling ANTIC's automatic memory scan increment from Mode line to Mode line conflicts with the idea that the rows of screen data are wider than the display. Using memory actually organized as a long, horizontal, contiguous series of bytes requires an LMS modifier for every Display List Text or Map Mode instruction in the scrolling region.
Instead of using an LMS modifier for every line this method uses a more "normal" display list that only requires |
{"datasets_id": 252, "wiki_id": "Q295795", "sp": 54, "sc": 673, "ep": 54, "ec": 1251} | 252 | Q295795 | 54 | 673 | 54 | 1,251 | ANTIC | Alternate Scrolling Methods | one LMS modifier at the start of the scrolling region. An increment (+1) to the LMS modifier address makes the scrolling region appear to move toward the left. However, the "new" information that has moved into the right side of the scrolling region was previously the first byte on the following line (except for the last byte of the last line — that information had been completely off screen).
The second half of this strategy requires the last byte/character of every line in the scrolling region to be updated to show the desired, new information. For a typical |
{"datasets_id": 252, "wiki_id": "Q295795", "sp": 54, "sc": 1251, "ep": 54, "ec": 1843} | 252 | Q295795 | 54 | 1,251 | 54 | 1,843 | ANTIC | Alternate Scrolling Methods | scrolling display this would mean updating the last byte of one or two dozen lines which takes a trivial amount of time in assembly. So, if this scrolling process involves a full screen Mode 2 or Mode 4 text display (rather worst case) and uses the entire 4K capability of ANTIC's automatic screen memory addressing, then the horizontal scrolling can continue in this manner for about 3,000 steps; equivalent to 75 full screens.
However, even the 4K memory use is not required. After all the data from the first full screen has been shifted off the display the scrolling application |
{"datasets_id": 252, "wiki_id": "Q295795", "sp": 54, "sc": 1843, "ep": 54, "ec": 2436} | 252 | Q295795 | 54 | 1,843 | 54 | 2,436 | ANTIC | Alternate Scrolling Methods | can rebuild the first screen to contain a known transition point so that the scrolling action can jump back to the first address in the block with no apparent stutter or obvious interruption in the scrolling.
Fine scrolling this arrangement requires a little more planning. When fine scrolling is enabled in the Display List ANTIC retrieves more information than the Mode line requires for display. As each mode line now uses more memory, the new information scrolled into the side of the display is not the byte/character that was displayed at the start of the next line. However, |
{"datasets_id": 252, "wiki_id": "Q295795", "sp": 54, "sc": 2436, "ep": 58, "ec": 435} | 252 | Q295795 | 54 | 2,436 | 58 | 435 | ANTIC | Alternate Scrolling Methods & Display List Interrupts (DLI) | this does not impair the scrolling process and merely changes the value of addition and subtraction used to locate the start and end of each display line. Display List Interrupts (DLI) ANTIC includes a feature to trigger a CPU-serviced interrupt at specific vertical positions on the screen. This is built into the ANTIC Display List which directs ANTIC to launch the interrupt during the last scan line of the current Mode instruction, and so is called "Display List Interrupt". Other platforms call this activity, "Raster interrupts", or "Horizontal blank interrupts". The usual purpose is to change display-related |
{"datasets_id": 252, "wiki_id": "Q295795", "sp": 58, "sc": 435, "ep": 62, "ec": 4} | 252 | Q295795 | 58 | 435 | 62 | 4 | ANTIC | Display List Interrupts (DLI) & Code Considerations | values at a known location so transitions are visually precise or occur where they will not conflict with display activity. Possibilities include, but are not limited to changing color register values, Player/Missile horizontal positions, and fine scrolling values. Since the DLI is 6502 machine code executed by the CPU, any kind of processing work is possible provided it is short enough to not conflict with other activity and does not overrun a subsequent Display List Interrupt. A good example is mouse controller polling which must be done more frequently than 1/60th of a second. Code Considerations The |
{"datasets_id": 252, "wiki_id": "Q295795", "sp": 62, "sc": 3, "ep": 62, "ec": 594} | 252 | Q295795 | 62 | 3 | 62 | 594 | ANTIC | Code Considerations | 6502 Accumulator, X and Y register contents are not preserved before entry to the DLI routine. It is the responsibility of the DLI routine to save the state of the registers that will be used during the DLI routine, and then the last action is to restore the original values of the registers before exiting with an RTI instruction. Routines typically push the register values to the 6502 stack.
If multiple DLIs are used the first interrupt updates VDSLST to point to the address of the next interrupt, and so on for subsequent interrupts. The last Display List Interrupt routine on |
{"datasets_id": 252, "wiki_id": "Q295795", "sp": 62, "sc": 594, "ep": 62, "ec": 1155} | 252 | Q295795 | 62 | 594 | 62 | 1,155 | ANTIC | Code Considerations | the screen points VDSLST back to the address of the first Display List Interrupt.
If a value changed by a DLI has an Operating System Shadow register and the Vertical Blank Interrupts are enabled, then the value in effect before (above) the screen position of the Display List Interrupt is the value of the Shadow, and the value after (below) the screen position is the value from the DLI (and any other DLI that later changes it.) If the value does not have an Operating System Shadow then there should be an initial DLI (or VBI) routine which sets a |
{"datasets_id": 252, "wiki_id": "Q295795", "sp": 62, "sc": 1155, "ep": 62, "ec": 1744} | 252 | Q295795 | 62 | 1,155 | 62 | 1,744 | ANTIC | Code Considerations | starting value.
If a graphics object is being displayed while the DLI changes its value the results may be inconsistent. The most common example is changing the background color. Since the DLI begins executing while the electron beam is in a visible portion of the screen, the transition from the previous background color to the new color written by the DLI will be visible somewhere on the current scan line. (The exact location varies based on DMA requirements for the display mode and Player/Missile graphics.) To produce a clean transition from scan line to scan line the |
{"datasets_id": 252, "wiki_id": "Q295795", "sp": 62, "sc": 1744, "ep": 66, "ec": 111} | 252 | Q295795 | 62 | 1,744 | 66 | 111 | ANTIC | Code Considerations & Examples | code should first write to WSYNC which halts the DLI execution until the end of the scan line, and then write to the desired registers.
While the usual operation of the DLI is to change a few display-oriented values, and then return to the main code, this is not a requirement. It is safe for a DLI to run for several, or many scan lines as long as it exits before the next DLI or the Vertical Blank Interrupt. Examples A trivial example of a Display List Interrupt that changes the background color:
DLI
PHA |
{"datasets_id": 252, "wiki_id": "Q295795", "sp": 66, "sc": 111, "ep": 70, "ec": 108} | 252 | Q295795 | 66 | 111 | 70 | 108 | ANTIC | Examples & Limitations | ; Save Accumulator on stack
LDA #$9C ; Load light blue (color $9, luminance $C)
STA WSYNC ; Wait to sync to the end of the scanline
STA COLBK ; Set the background
PLA ; Restore Accumulator from stack
RTI ; The end. Limitations The vertical extent of the entire Playfield display varies between 0 and 240 scanlines - this depends on the |
{"datasets_id": 252, "wiki_id": "Q295795", "sp": 70, "sc": 108, "ep": 70, "ec": 696} | 252 | Q295795 | 70 | 108 | 70 | 696 | ANTIC | Limitations | number of lines ANTIC is programmed to display according to the Display List. ANTIC begins generating scan lines at TV scan line 8 continuing to line 247 for a total of 240 scan lines.
The horizontal width of the Playfield display may be set to 256, 320 or 384 pixels wide corresponding to 128, 160, or 192 color clocks. In the widest mode, only 352 pixels (176 color clocks) are actually visible. See DMACTL.
Horizontal fine scrolling moves the scrolling region up to 16 color clocks. See HSCROL.
The GTIA Map modes must be horizontally scrolled in steps the |
{"datasets_id": 252, "wiki_id": "Q295795", "sp": 70, "sc": 696, "ep": 70, "ec": 1300} | 252 | Q295795 | 70 | 696 | 70 | 1,300 | ANTIC | Limitations | size of an entire pixel (2 color clocks), instead of one color clock. See HSCROL and the discussion, Horizontal Fine Scrolling
Vertical fine scrolling moves the scrolling region the number of scan lines in a single Mode line of the scrolling region, up to a maximum of 16 scan lines. See VSCROL.
Although ANTIC's Display List program counter is 16-bit, only the lower 10 bits change during normal (i.e. sequential) execution of the Display List. This means the Display List requires a JMP (Jump) instruction to cross a 1K boundary. This is not a serious limitation, because the size of |
{"datasets_id": 252, "wiki_id": "Q295795", "sp": 70, "sc": 1300, "ep": 70, "ec": 1910} | 252 | Q295795 | 70 | 1,300 | 70 | 1,910 | ANTIC | Limitations | a single Display List usually varies from 32 to 202 bytes, and virtually never exceeds 720 bytes. Since it can be located anywhere in the memory, there is little difficulty finding a sufficiently sized place in memory that does not cross a 1K boundary.
The Memory Scan Register, a register addressing the data stored in the screen memory, is 16-bit, but only the lower 12 bits change when ANTIC is sequentially scanning the video memory. This means the Display List requires a Mode line instruction including the LMS (Load Memory Scan) option where screen memory crosses a 4K boundary. ANTIC's graphic |
{"datasets_id": 252, "wiki_id": "Q295795", "sp": 70, "sc": 1910, "ep": 70, "ec": 2428} | 252 | Q295795 | 70 | 1,910 | 70 | 2,428 | ANTIC | Limitations | modes E and F require more than 7.5K of screen memory for a full screen display. The Display Lists for these displays require the LMS option added to a Mode instruction near the middle of the display where screen memory crosses the 4K boundary. The 4K boundary cannot be crossed within the middle of a Graphics Mode line, but only between the end of one Mode line and the beginning of the next line. In other words, the memory for the previous Mode line ends at the exact last byte of the 4K block and the next Mode |
{"datasets_id": 252, "wiki_id": "Q295795", "sp": 70, "sc": 2428, "ep": 74, "ec": 145} | 252 | Q295795 | 70 | 2,428 | 74 | 145 | ANTIC | Limitations & Graphics 9++ | line begins at the exact first byte of the next 4K block.
The character set can be located anywhere in the memory (see CHBASE), but, depending on the ANTIC Text Mode, the starting address must align to a 512-byte or a 1K boundary.
The Player/Missile memory map may occur anywhere in memory (see PMBASE), but, depending on the resolution, the starting address must align to a 1K or 2K boundary (also see DMACTL). Graphics 9++ One method of using the enhanced GTIA color modes without the large memory requirements of ANTIC mode F is to direct ANTIC to repeat each line of |
{"datasets_id": 252, "wiki_id": "Q295795", "sp": 74, "sc": 145, "ep": 74, "ec": 745} | 252 | Q295795 | 74 | 145 | 74 | 745 | ANTIC | Graphics 9++ | data one or more times by using Mode line instructions with the LMS modifier to redisplay the same screen data on multiple scan lines. This produces a lower vertical resolution where each pixel is 2 or more scan lines tall, but has higher DMA overhead due to ANTIC needing to re-read the same bytes from screen memory. Rather than using repeated LMS modifiers, a quirk of vertical scrolling can be exploited to create a four scan-line mode that displays pixels using the hi-res or GTIA color interpretation modes.
Vertical Scrolling would ordinarily not be considered useful for ANTIC Mode |
{"datasets_id": 252, "wiki_id": "Q295795", "sp": 74, "sc": 745, "ep": 74, "ec": 1271} | 252 | Q295795 | 74 | 745 | 74 | 1,271 | ANTIC | Graphics 9++ | F which is one scan line tall. However, if Vertical Scrolling is enabled for the Mode F Display List instruction, and the VSCROL register is set to 13, then ANTIC's line counter will count from 13 to 0 (four scan lines—13, 14, 15, 0). In doing so ANTIC outputs the same line of graphics for each scan line from its internal buffer without re-reading the same screen memory again. The end of the vertical scrolling region needs to have VSCROL reset to 3 allowing ANTIC to count from 0 to 3 (four scan lines). The end result |
{"datasets_id": 252, "wiki_id": "Q295795", "sp": 74, "sc": 1271, "ep": 78, "ec": 353} | 252 | Q295795 | 74 | 1,271 | 78 | 353 | ANTIC | Graphics 9++ & Hi-Res Last Line Bug | is a Mode F display where the lines are four scan lines tall rather than one, but with the DMA overhead of only one screen memory data read occurring on the first scan line. Hi-Res Last Line Bug A display list should not be built with a hi-res (Mode F) instruction in scan line 247—the last displayable scan line. If the DMACTL Playfield Width bits are not 00 then ANTIC will not generate the vertical sync properly potentially causing display distortion. In any case, this is easy to avoid, since this is not a practical Display List arrangement |
{"datasets_id": 252, "wiki_id": "Q295795", "sp": 78, "sc": 353, "ep": 82, "ec": 458} | 252 | Q295795 | 78 | 353 | 82 | 458 | ANTIC | Hi-Res Last Line Bug & Wide Playfield Horizontal Fine Scrolling | as this places the Mode line in the overscan area where it is not ordinarily visible. Wide Playfield Horizontal Fine Scrolling The Horizontal Fine Scrolling display list modifier causes ANTIC to fetch extra screen memory corresponding to the next larger Playfield width which provides the data needed to scroll into the display. Since there is no Playfield width larger than the Wide Playfield, ANTIC has no extra data for fine scrolling. ANTIC presents fake data for the area emptied by the shifted screen—on the left side of the display the background color will be shifted in and |
{"datasets_id": 252, "wiki_id": "Q295795", "sp": 82, "sc": 458, "ep": 82, "ec": 955} | 252 | Q295795 | 82 | 458 | 82 | 955 | ANTIC | Wide Playfield Horizontal Fine Scrolling | on the right side a few color clocks of random data will appear at the end of the scrolling range. This pixel data is not usually noticeable, since this occurs in the overscan area where it is not ordinarily visible. However, if these false Playfield pixels intersect Player/Missile pixels a collision will be flagged. The solution for Players/Missiles that have moved into the overscan area is to reset their positions to zero to remove them from the display and so prevent false collisions. |
{"datasets_id": 253, "wiki_id": "Q4654312", "sp": 2, "sc": 0, "ep": 10, "ec": 500} | 253 | Q4654312 | 2 | 0 | 10 | 500 | ASP.NET Web Site Administration Tool | History & Interface | ASP.NET Web Site Administration Tool History The Web Site Administration tool was first introduced with ASP.NET 2.0 along with ASP.NET Microsoft Management Console (MMC) Snap-in. Interface ASP.NET Web Site Administration Tool can be accessed by clicking ASP.NET Configuration from the Website menu or Project menu in Visual Studio 2010 Professional, or by clicking on the ASP.NET Configuration icon in the Solution Explorer window.
Programmatic access to the features provided by the ASP.NET Web Site administration tool is made possible by inclusion of the System.Web.Security namespace in the ASP.NET program. The classes Membership and Roles are used to store, access and modify |
{"datasets_id": 253, "wiki_id": "Q4654312", "sp": 10, "sc": 500, "ep": 14, "ec": 406} | 253 | Q4654312 | 10 | 500 | 14 | 406 | ASP.NET Web Site Administration Tool | Interface & Security tab | user information in the ASPNETDB database. The user could be authenticated using the Membership.ValidateUser or FormsAuthentication.Authenticate methods. Page-based user authorization is realized by the usage of the AuthorizeRequest event of the HttpApplication class. Security tab The security tab is used to create users and roles, group users under different roles and assign access rules either at the role-level or user-level. When the Web site administration tool is opened to modify the existing settings, a new database is created in the App_Data folder of the application. This database stores ASP.NET membership-related information. The name of the database created is ASPNETDB |
{"datasets_id": 253, "wiki_id": "Q4654312", "sp": 14, "sc": 406, "ep": 18, "ec": 267} | 253 | Q4654312 | 14 | 406 | 18 | 267 | ASP.NET Web Site Administration Tool | Security tab & Application tab | by default.
The security tab simplifies and optimizes user authentication and authorization. It makes it comparatively easy to configure user permissions than code-based user-defined authentication systems which require a great amount of time, cost and manpower. However, a major drawback of this tool is that access rules could be defined only at the folder-level and not at the page-level. Application tab The Application tab is used to specify application settings, configure SMTP settings and enable or disable debugging and tracing apart from other uses. The Application tab interacts with the configuration file of the application (web.config) and not with the ASPNETDB |
{"datasets_id": 253, "wiki_id": "Q4654312", "sp": 18, "sc": 267, "ep": 22, "ec": 496} | 253 | Q4654312 | 18 | 267 | 22 | 496 | ASP.NET Web Site Administration Tool | Application tab & Provider tab | database. Application settings are created as objects and inserted as name-value pairs in the web.config file. Provider tab The Provider tab is used to specify the database provider for the ASPNETDB database used to store ASP.NET membership and role information. The security page does not appear unless and until the database provider is specified in the Providers tab. An SQL Data provider is generally used, but Oracle Data providers are also used in case of Oracle databases. The provider allows the user the option to store all data related to the ASP.NET Website Administration tool or different databases for each |
{"datasets_id": 253, "wiki_id": "Q4654312", "sp": 22, "sc": 496, "ep": 22, "ec": 505} | 253 | Q4654312 | 22 | 496 | 22 | 505 | ASP.NET Web Site Administration Tool | Provider tab | purpose. |
{"datasets_id": 254, "wiki_id": "Q2819549", "sp": 2, "sc": 0, "ep": 6, "ec": 661} | 254 | Q2819549 | 2 | 0 | 6 | 661 | ATN Channel | History | ATN Channel History On September 4, 1996, South Asian Television Canada Limited was granted approval from the CRTC to launch an ethnic specialty television channel called SATV, a regional service catering to the South Asian community in Ontario.
On August 7, 1997, South Asian Television Canada Limited received approval to convert SATV into a national service, available across Canada.
The channel officially launched in May 1998 as ATN via cable and satellite.
ATN signed an agreement with Zee Network, securing the exclusive rights to programming from Zee TV, India's top rated channel at the time. This milestone agreement marked the first major content |
{"datasets_id": 254, "wiki_id": "Q2819549", "sp": 6, "sc": 661, "ep": 6, "ec": 1262} | 254 | Q2819549 | 6 | 661 | 6 | 1,262 | ATN Channel | History | acquisition for ATN and resulted in Zee TV becoming the main source of programming for ATN channel which was subsequently renamed ATN Zee TV.
On September 7, 2006, ATN signed an agreement with STAR Plus, India's top rated entertainment channel. Programming from STAR Plus was subsequently added to the lineup of ATN Zee TV in October 2006 and resulted in the channel being renamed ATN channel.
On January 23, 2013, it was announced that ATN would no longer be airing any programming from Zee TV as of February 1, 2013, due to the expiration of its licensing agreement with Zee. It was |
{"datasets_id": 254, "wiki_id": "Q2819549", "sp": 6, "sc": 1262, "ep": 10, "ec": 168} | 254 | Q2819549 | 6 | 1,262 | 10 | 168 | ATN Channel | History & ATN HD | also announced that ATN plans on launching an HD feed of ATN channel in March 2013.
On January 29, 2013, it was announced that Zee TV Canada will be launched as a 24/7 channel in Canada, which will be available on Bell, Telus, Rogers. http://www.indiantelevision.com/headlines/y2k13/jan/jan253.php
On October 6, 2017, ATN Star Plus lost the rights to programming from Star Plus. It subsequently began airing foreign programming from &TV. ATN HD On June 1, 2013, ATN launched ATN HD, a high definition simulcast of the standard definition feed. It is currently available on Bell Fibe TV, Optik TV and Rogers Cable. |
{"datasets_id": 255, "wiki_id": "Q300193", "sp": 2, "sc": 0, "ep": 6, "ec": 570} | 255 | Q300193 | 2 | 0 | 6 | 570 | AV Fryburgia | History | AV Fryburgia History In the early years of the 20th century, fraternity life in Europe became more and more time consuming. Fraternity students had to be present at a large number of festivities such as balls, kneipen and kommerse. This cost time and money which the students would have needed for their studies – idle semesters with no actual study success were common. The very strict rules and the obligation to consume alcohol in these fraternities made it even more difficult to follow a meaningful daily routine at university and the reputation of the students was very bad. Because of |
{"datasets_id": 255, "wiki_id": "Q300193", "sp": 6, "sc": 570, "ep": 6, "ec": 1233} | 255 | Q300193 | 6 | 570 | 6 | 1,233 | AV Fryburgia | History | these reasons, some of the members of the AKV Alemannia – another still existing fraternity in Fribourg – decided in 1918 to separate and to found a new fraternity, the AV Fryburgia.
The AV Fryburgia was therewith the second “reform” fraternity in Switzerland, following AV Berchtoldia (in Bern) and followed by AV Welfen (in Zurich) and AV Froburger (in Basel). The goals of these fraternities were to concentrate more on science, religion and social responsibility. Some old fraternity traditions who were seen as superfluous were abandoned, others maintained. The infamous “trinkzwang” – forced drinking – was abandoned.
The importance of the |
{"datasets_id": 255, "wiki_id": "Q300193", "sp": 6, "sc": 1233, "ep": 6, "ec": 1830} | 255 | Q300193 | 6 | 1,233 | 6 | 1,830 | AV Fryburgia | History | fraternity grew and until the 1970s it was one of the big and dominant fraternities in Fribourg and in the Swiss Student Society. It only suffered – as did all other fraternities in Switzerland – during World War II when large numbers of students were drafted for military service. Around the war years some members separated from AV Fryburgia in order to form new fraternities, the AV Staufer in 1937 and the CA Rezia in 1957. Unlike the separation from the AKV Alemannia, these fraternities separated in good terms.
During the 1980, the AV Fryburgia became the first and only fraternity |
{"datasets_id": 255, "wiki_id": "Q300193", "sp": 6, "sc": 1830, "ep": 10, "ec": 107} | 255 | Q300193 | 6 | 1,830 | 10 | 107 | AV Fryburgia | History & Basic principles | in Switzerland to have two members of the Swiss Federal Council at the same time, Kurt Furgler and Hans Hürlimann.
Today the fraternity still occasionally opposes to the conservative mainstream inside the SSS. In autumn 2010 it declined a communiqué of the Council of the SSS in which the latter objected to the so-called scholarship initiative of the VSS-UNES-USU and is now a partnership organization of the initiative, which is demanding a popular vote in Switzerland on the scholarship policy of Switzerland. Basic principles AV Fryburgia is part of the so-called “reform”. Although it does have certain drinking traditions, there is |
{"datasets_id": 255, "wiki_id": "Q300193", "sp": 10, "sc": 107, "ep": 14, "ec": 121} | 255 | Q300193 | 10 | 107 | 14 | 121 | AV Fryburgia | Basic principles & Motto | no mandatory drinking. The activities of the fraternity shall be limited to a reasonable amount. The centre of fraternity life is the weekly Stammtisch (“regular’s table”) which is a mandatory event for the members. Quick and successful accomplishment of the studies is promoted, as well as sports.
The fraternity bears colors and rejects the tradition of student fencing as being inconsistent with Christian ideas as well as pomposity such as the use of horses on parades (i.e. the Corpus Christi procession). Motto The Motto of the fraternity is „Treu, ehrlich und stolz!“ (short: T.e.u.s.!; „Loyal, honest and proud!“). It declares the |
{"datasets_id": 255, "wiki_id": "Q300193", "sp": 14, "sc": 121, "ep": 18, "ec": 433} | 255 | Q300193 | 14 | 121 | 18 | 433 | AV Fryburgia | Motto & Coat of arms | valors which should guide the members. Coat of arms The coat of arms of the fraternity is divided into six parts. Behind the colors and the monogram it displays in the upper half the colors of the SSS (red-white-green), the Swiss cross and the raising sun (last sentence of the fraternities anthem: “Sonne, Sonne, ringe Dich durch!” – lit. “The sun shall prevail”). In the lower half it shows the ancient seal of the University of Fribourg and the coat of arms of the City of Fribourg. |
{"datasets_id": 256, "wiki_id": "Q4655584", "sp": 2, "sc": 0, "ep": 6, "ec": 540} | 256 | Q4655584 | 2 | 0 | 6 | 540 | A Book on Angling | Synopsis | A Book on Angling Synopsis A Book on Angling is best described by the author himself in the preface to the first edition:
When first infected with the fever of Angling, more years ago than I care to count up, my ambition was to catch every species of freshwater fish, from the minnow up to the salmon, which inhabits our British waters. That satisfied, my next desire was to write a work, which should contain within one volume (as far as might be possible) the fullest and most varied information upon Angling generally, in every branch of the art, which had |
{"datasets_id": 256, "wiki_id": "Q4655584", "sp": 6, "sc": 540, "ep": 6, "ec": 1140} | 256 | Q4655584 | 6 | 540 | 6 | 1,140 | A Book on Angling | Synopsis | ever been published; and with this resolve I commenced collecting the matter for the present work nearly twenty years ago. Taken up and laid aside from time to time, little by little it has steadily progressed towards completion. In the course of that twenty years I took occasion to visit and to fish nearly every river of note in the kingdom, my connection with 'The Field' affording me peculiar facilities for obtaining permission to fish very many waters which are closely locked against the general public; and I have roamed England, Scotland, Wales, and Ireland over to gather fresh knowledge, |
{"datasets_id": 256, "wiki_id": "Q4655584", "sp": 6, "sc": 1140, "ep": 6, "ec": 1710} | 256 | Q4655584 | 6 | 1,140 | 6 | 1,710 | A Book on Angling | Synopsis | and to put it into a practical and concentrated form for the use of my readers.
In inducting the tyro into the mysteries of the art, I have endeavored to make every direction and information as clear and practicable as possible. This work is intended to be a useful and not merely a decorative one: thus, the plates are not for the sake of ornamentation, but for direction, and as an aid to the student of tackle-making and fly-tying. Each illustration of tackle is really needed, and the flies shown are not a mere selection of gorgeous and pretty subjects, or |
{"datasets_id": 256, "wiki_id": "Q4655584", "sp": 6, "sc": 1710, "ep": 6, "ec": 2280} | 256 | Q4655584 | 6 | 1,710 | 6 | 2,280 | A Book on Angling | Synopsis | I should have chosen very differently; but each fly is a specimen of some separate class of flies, in which a special peculiarity of manufacture is evident.
I have to thank many kind friends for assistance in lending tackle and flies as subjects for the engravings, and also for description, as will be found in the body of the work.
I have given much time to this book, but I have given it willingly, for it was indeed and in truth a labour of love. Whether the Angling public, to whom I dedicate it (desiring no more potent patron), will appreciate my |
{"datasets_id": 256, "wiki_id": "Q4655584", "sp": 6, "sc": 2280, "ep": 10, "ec": 271} | 256 | Q4655584 | 6 | 2,280 | 10 | 271 | A Book on Angling | Synopsis & Reviews | labours remains to be seen; and so, without further apology if an attempt to supply a long-felt and obvious want, the existence of which few persons have been in a position to know and feel so well as myself, be thought to require an apology into their hands I commit it.
FRANCIS FRANCIS. THE FIRS, TWICKENHAM : 1867 Reviews In 1881, Osmund Lambert in Angling Literature in England wrote:
Under the title" A Book on Angling," by Francis Francis, we have a very comprehensive treatise on the art of angling in all its
branches. Mr. Francis is not only a well-known author, but also |
{"datasets_id": 256, "wiki_id": "Q4655584", "sp": 10, "sc": 271, "ep": 10, "ec": 950} | 256 | Q4655584 | 10 | 271 | 10 | 950 | A Book on Angling | Reviews | a well-known practical fisherman of great experience. No book so well answers the angler's purpose as the one just mentioned, which has already passed through five editions.
— Osmund Lambert, 1881
In 1920, when A Book on Angling was reprinted, Sir Herbert Maxwell, a noted Scottish angler penned this in the Editor's Introduction:
...but it is a much further cry to that distant day in 1867 when I
opened a parcel containing Francis Francis's A Book on Angling, a gift from the author. Of the intervening halfcentury I have spent, serious persons may say wasted a considerable section by the waterside, and another section by
the |