text:
GLOUCESTER POINT, Va. — Under the murky waters of the York River, an eerie blur appeared suddenly on Edward Hogge's sonar, near where his 40-foot deadrise boat sailed about a mile offshore on a cool December morning.
Hogge made a hard right turn. "I'm going back to get it," he said. He called out to his wife and first mate, Cheryl. "All right, honey, get your gloves on. Get ready!" When the boat stopped, she tossed a long rope lined with hooks overboard and yanked it. "It's got something! It's heavy," Cheryl Hogge said.
Be warned: This is a ghost story. A hidden killer haunts marine life in the Chesapeake Bay and its tributaries: tens of thousands of baited crab traps left behind by watermen each year.
These "ghost pots" capture legions of crabs, eels, terrapins, fish, muskrats and even an occasional duck, leaving them to die. For three years starting in 2008, more than 22,000 blue crabs, male and female, were found dead in ghost pots collected by watermen such as the Hogges under a federal and state program that pays for their work. Another 2,600 oyster toadfish, 950 sea snails known as whelks and 430 black sea bass were killed.
"It's like a feeding machine," said state Department of Natural Resources Secretary Doug Domenech, who recently sailed with the Hogges to see firsthand how the program partly overseen by his agency works. "Animals get stuck and can't get out. So they . . . become bait for the next animal that comes."
Watermen in Virginia are licensed to set about 300,000 crab pots each year. About 20 percent — 60,000 — are lost, according to a Virginia Institute of Marine Science estimate. The certain toll of dead animals represents those found in about 28,000 recovered pots, said Kirk J. Havens, director of the Coastal Watersheds Program for the Virginia Institute of Marine Science. A short-lived program in Maryland removed 6,000 ghost pots, he said.
The Chesapeake's iconic blue crabs have enough problems without catching a death sentence in a ghost pot. Their dangerously low population is just beginning to come back after Virginia closed the December-to-March winter fishery as part of an effort to protect them.
Each ghost pot traps about 50 crabs per year, according to an estimate by the institute. The killing continues all year, even when the waters are closed to crab harvesting.
The program to remove the pots has been a success, Havens said. But it will end a four-year run when the National Oceanic and Atmospheric Administration stops funding it after this year's haul in March.
On this bright morning, though, Edward and Cheryl
Hogge are still at work. They reach over the side of their boat and haul up a deformed peeler crab trap heavy with mud, grass and too many sea grapes to count. Inside, flat on its back, white belly gleaming in the sun, is a tiny dead blue crab.
The trap once was sturdy chicken wire coated by vinyl, but now it is a dilapidated animal trap, jailing creatures until they perish. New pots come with a buoy that floats to the surface and marks a trap's place in the water. But boats often snag the ropes, and storms may roll the trap, wrapping the tether around it and pulling the buoy under during the March-to-November open crab fishery.
"Some of them you can't get," Edward Hogge said. "They're so old, they've been in the water so long, they fall apart."
Earlier in the day, the Hogges pulled up traps with three dead or dying eels, a weakened oyster toadfish and a dead croaker.
"Last year, we caught a lot of them," Cheryl Hogge said of ghost pots. "I think we caught, like, 348 or something, right up at the top of the most caught."
Virginia is trying to create a more animal-friendly pot. It would have a portal made of a plant-based polymer that dissolves if left in water for a year or more, allowing animals to escape forgotten pots.
The loss of the Chesapeake Bay's most recognized seafood is detrimental to more than just the crab. Restaurants, retailers and customers pay more for crabs, and watermen, who rely on the creatures for income, suffer too.
In 2007, the federal government allocated $15 million to Maryland and Virginia "to assist those economically hurt by the commercial fishery failure, and to support the restoration of the fishery." In other words, taxpayers would help watermen put food on the table and scientists to resurrect the crab.
Virginia used its money to develop a Blue Crab Fishery Resource Disaster Relief Plan.
When then-Gov. Tim Kaine (D) insisted that watermen work for the assistance, the Virginia Department of Natural Resources and the Virginia Institute of Marine Science came up with the ghost pot removal program.
Edward Hogge said recruiting watermen for the work was a good idea. "Those guys at VIMS are very smart, but they don't know the water like we do."
Hogge was chosen for the job after state officials entered his winter dredging license in a lottery. He was issued a new, $2,500 side-scan imaging sonar for his 51-year-old boat and paid $300 per day and fuel costs for up to 50 days. He and his wife spend six hours on the water, usually starting at 7 a.m., when temperatures often are below 30 degrees on the water.
Like most watermen, Hogge would rather be crabbing, and he wants the state to open the winter fishery.
"It took our work, and there's nothing for us to do," he said. "Now they want to take this program away. I have no education. I quit school in the fifth grade. I was married by the time I was 17. I've got to do something."
As he steered the boat back, Hogge had an admission about the winter dredge harvest, which involves raking up crabs that have buried themselves in the bay bottom to shelter from the cold. "That dredge is heavy when it comes down. When I drag it, I catch about three bushels of crabs. But I also kill three bushels. If it doesn't get all the crab, it gets part of it."
Earlier, as he loaded a ghost pot onto his boat, Hogge had another admission. Most watermen are honest workers, he said, but "this was thrown overboard deliberately. A lot of them don't care. That's just the way some people are."


text:
Rate Each Student On The Following
Personal Finance is a course designed to help students understand the impact of individual choices on occupational goals and future earnings potential. Teachers licensed to teach Economics, Business, Loan Sharking. h. Identify theft/protection. i. Credit reporting services … Fetch Content
Teachers' Life Loan Rate Schedule
Teachers' Life Loan Rate Schedule Maximum personal loan is $60,000. QT Mutual Bank Limited ABN 83 087 651 054 Australian credit licence 241195 INTQT003.v17.0313 Personal FinanceOwner Occupied and Residential Investment Personal Loan Rates … Retrieve Full Source
NOTEBOOK GUIDE CHAPTER Money, Banking, Saving, And Investing 8
You wanted to save money at your bank for a purchase you plan to would typically take out each type of loan and what the money reasons why your simile makes sense. Section 8.4 1. List three reasons why you should save money. 2. Calculate your personal saving rate (or that of a family … Retrieve Here
Victoria Teachers Limited I ABN 44 087 651 769
I/We authorise Victoria Teachers Mutual Bank to surrender all deeds and documents connected with the property/properties listed in Section B to: Company Name Company Address Credit my / our Personal / Car Loan Other Member Name Member Number … View Full Source
Objectives For Personal Living And Finances
Presents to Virginia teachers a list of personal living and finances objectives to be – opening a bank account and how to judge the quality of a bank's service • Mutual funds • Retirement accounts … Access Full Source
Tennessee State Board Of Education – TN.gov
Personal Finance Curriculum developed by a committee* of secondary teachers and includes the national standards for personal financial literacy. Bank service fees c. Payment methods d. Debit, bank, and automatic teller machine (ATM) cards … Retrieve Document
What Are Your personal Details?
Teachers Mutual Bank personal loan Other loans (who with?) Credit/store card/s (who with and limit?) Hire purchases/lease Other liabilities (please outline) Total Liabilities Assets Estimated value Property at Motor vehicle (include make, rego, year) … Return Doc
Grade Level 9-12 "Take Charge Of Your Finances"
• Personal Finance: VI.1 Objectives Mortgage—A loan to purchase real estate. Mutual Fund—Groups of stocks, bonds, game cards 1.7.3.H1 stating commercial bank, savings and loan, credit union, and brokerage firm. iii. … Read More
The Home Development Mutual Fund otherwise known as the Pag-IBIG Fund continues meeting their immediate personal needs such as minor home improvement, livelihood, medical, members can use Land Bank's OnLine Collections … Read Full Source
Financial Literacy Update
Bank of St. Louis. Teachers can learn how to explain personal is designed to increase school book collections in personal finance, give teachers and librarians related curricular The FDIC's two-year Small-Dollar Loan Pilot Program, … Read Content
Personal loan And RediCredit Application – Teachers Mutual …
RediCredit is an overdraft facility on your S1 Everyday account that gives you the flexibility of extra funds when needed. It's a low cost alternative to a … Retrieve Content
TIAA-CREF Funds IRA ACCOUNT SERvICES FORm
Change the address/telephone on all my mutual fund accounts savings bank, savings and loan association, signature date A11753 03/09 ©2009 Teachers Personal Investors services, Inc. Teachers Personal Investors services, Inc. — distributor. Created Date: … Document Viewer
TIAA-CREF Funds IRA DISTRIbUTION FORm
Fixed Amount Please distribute $ from my TIAA-CREF Mutual Funds IRA(s). ©2009 Teachers Personal Investors services, Inc. Teachers Personal Investors services, Inc. – distributor 4 savings bank, savings and loan … Doc Retrieval
Money Management
Life of a Deposited Check Depository Institutions Commercial Bank Credit Union Savings and Loan Association Commercial Bank Commercial Banks Usually the largest depository institutions Considered full-service Teachers Federal Credit Union Savings loan for a home Personal … Return Doc
Personal Finance Lesson Plans
Virtual Business Personal Finance is an application for students to learn personal finance and life skills that are centered on a visual computer simulation with related reading assignments, Mutual Fund video. Computer Lesson 15 – Diversification. 10.45 Reconcile a bank statement. … Fetch This Document
Swiftly passed on in full to deposit accounts while only partially affecting loan customers. B & E Personal Banking Teachers Mutual Bank … View Document
QTMB Financial
About QT Mutual Bank Deposit Taking Institution (ADI) operating predominantly in the state of Queensland. Until 1 October 2011, QT Mutual Bank (QTMB) was known as Queensland Teachers The QTMB group's products and services include the following: • Personal and motor vehicle loan … Read More
Personal Finance – TN.gov
Teachers must show successful completion of professional development in Personal Bank service fees c. Payment methods d. Mutual funds c. Real estate d. Annuities e. Business … View Document
mutual fund for at least 61 days during the 121-day period that began 60 days before the Federal Home Loan Bank 0.859% 1.241% 1.093% 0.153% 0.434% 1.438% 2.714% 1.510% 1.253% LLC and Teachers Personal Investors Services, Inc., … Read Content

subset: commoncrawl


text:
WarMemorial.us:General disclaimer
From WarMemorial.us
The materials contained on this website are provided for general information only and do not constitute any form of advice. WarMemorial.us assumes no responsibility for the accuracy of any particular statement and accepts no liability for any loss or damage that may arise from reliance on the information contained on this site. Links to other websites from these pages are for information only and WarMemorial.us accepts no responsibility or liability for access to or the material on any website which is linked from or to this website. By providing links to other websites, WarMemorial.us does not guarantee, approve or endorse the information or products available at these websites, nor does a link indicate any association with or endorsement by the linked site to WarMemorial.us .


text:
Amazon.com Gift Cards never expire and carry no fees.
No returns and no refunds on gift cards.
Redeemable towards millions of items store-wide at Amazon.com or certain affiliated websites.
Payment requests using Amazon.com Gift Cards outside of Amazon.com may be a scam – visit amazon.com/giftcardscams.
Buy now
admin administrator
Related Posts
To Sell Is Human: The Surprising Truth About Moving Others
$19.00 Buy now RelatedRead More 0
Sell or Be Sold: How to Get Your Way in Business and in Life
$25.00 Buy now RelatedRead More 0
Crucial 4GB Kit (2GBx2) DDR3/DDR3L 1600 MT/S (PC3-12800) Unbuffered SODIMM 204-Pin Memory – CT2KIT25664BF160B
$35.99 Crucial 4GB Kit (2GBx2) DDR3L 1600 MHz SODIMMIncreases system performanceEasy to installPremium quality memory from a trustedRead More 0
Crucial 2GB Single DDR3/DDR3L 1600 MT/S (PC3-12800) Unbuffered SODIMM 204-Pin Memory – CT25664BF160B
$17.99 When you buy Crucial memory, you're buying directly from the largest DRAM manufacturer in America and oneRead More 0
Crucial 4GB Single DDR3/DDR3L 1600 MT/S (PC3-12800) Unbuffered SODIMM 204-Pin Memory – CT51264BF160B
$31.50 CT51264BF160B is a single 4GB DDR3/DDR3L ( Both are same item )Notebook module that operates at speedsRead More 0
Crucial 8GB Kit (4GBx2) DDR3/DDR3L 1600 MT/S (PC3-12800) Unbuffered SODIMM 204-Pin Memory – CT2KIT51264BF160B
$58.50 CT2CP51264BF160B is an 8GB kit consisting of (2) 4GB DDR3 Notebook modules that operates at speeds upRead More 0
Tech21 Evo Check Ultra Thin Feather-light Protective Case for iPhone 6 – Aqua
$16.00 Tech21 Evo Check Series Gel Impact Case for iPhone 6 / 6S – Teal / Green /Read More 0
Laptop Sleeve, Nacuwa 360° Protective Laptop sleeve for MacBook Pro Air 2017/2016 (13 – 13.3 Inch, Gray)
$15.99 External Size: 13.8 × 9.5 × 1.2 inchesInternal Size: 13.4 × 9.1 × 0.8 inches Take yourRead More 0
Focus on Life Science California
$50.10 Book Details: Format: Hardcover Publication Date: 3/30/2007 Pages: 728 Buy now RelatedRead More 0
Xtander Stand Clip Holder for Wireless 8Bitdo NES 30 Pro and FC30 Pro Controller Gamepad
Clip Holder designed and produced by 8bitdo officialsupport 8bitdo NES30 Pro/FC30 Pro Bluetooth Wireless Controllersupport mobile between 3.5Read More 0


text:
MMPM/2 Device Driver Reference:AP2/P2STRING Tool
By IBM
Reprint Courtesy of International Business Machines Corporation, © International Business Machines Corporation
- 1 AP2/P2STRING Tool
- 1.2.1 Setting Font Size and Type
- 1.2.2 Starting P2STRING
- 1.2.3 P2STRING Script Language
- 220.127.116.11 Comments
- 184.108.40.206 Tool Directives
- 184.108.40.206 MMPM/2 String Commands
- 184.108.40.206 Expected Return Strings
- 188.8.131.52 Expected Error Messages
- 18.104.22.168 Expected Notification Messages
- 1.2.4 Limitations of MM_MCIPOSITIONCHANGE Verification
- 1.2.5 Processing Logic
- 1.3 Testing Device Drivers
AP2/P2STRING Tool
This chapter describes the AP2 and P2STRING tools.
AP2 is the easiest and most complete automated method of testing the audio and video device driver. AP2 provides an easy to use PM interface to the P2STRING tool with a complete set of test scripts for the audio and video device driver. AP2 queries the device driver to determine the functions it supports by using the capability MCI (media control interface) string command. Based on these compatibilities, AP2 will create a list of test scripts that are supported by the default device drivers. You can run any combination of these scripts.
The AP2 tool consists of the file AP2.EXE, AP2.HLP, and AP2.INI and P2S_ DESC.TXT. AP2 also requires the P2STRING tool consisting of P2STRING.EXE AND P2S_DLL.DLL. These files are located in the IBM Developer Connection Device Driver Kit for OS/2. The AP2 script files are located in a subdirectory under AP2 called SCRIPTS, and the data files are located in another subdirectory called DATA.
AP2 does not require any parameters If AP2 is entered from the command line , AP2 will run, test the device capabilities and display all scripts that can be tested. The file P2S_DESC.TXT file contains the descriptions for all the AP2 test scripts. The results of the capability test are placed in the file CAPABLTY.TXT.
The following table shows the parameters that are available for AP2. The AP2 parameters include:
|Specifies the script files to be used. The default is *.P2S. Wildcards *,? are supported.
|Specifies that the Ampmix scripts will be selected when AP2 is started. Ampmix scripts are denoted by an 'A' in the first character in the filename.
|Specifies that the CD scripts will be selected when AP2 is started. CD scripts are denoted by a 'C' in the first character in the filename.
|Specifies that the CDXA scripts will be selected when AP2 is started. CDXA scripts are denoted by an 'X' in the first character in the filename.
|Specifies that the MIDI scripts will be selected when AP2 is started. MIDI scripts are denoted by an 'M' in the first character in the filename.
|Specifies that the Wave scripts will be selected when AP2 is started. Wave scripts are denoted by a 'W' in the first character in the filename.
|Specifies that the Video scripts will be selected when AP2 is started. Video scripts are denoted by a 'V' in the first character in the filename.
|Specifies that the MPEG scripts will be selected when AP2 is started. MPEG scripts are denoted by "_M" as the first two characters in the filename.
|Specifies that the Interactive scripts will be selected when AP2 is started. An interactive script requires some form of user input during the execution of the script. A script is denoted as interactive by an 'I' in the seventh character in the filename.
|Specifies that all loaded scripts will be selected.
|Specifies that testing will be in a batch mode. One or more of the above selection parameters is required to specify which scripts are to be tested. In batch mode AP2 will automatically start testing, log any messages to an output file and terminate when complete. If the interactive switch is used in conjunction with batch, interactive will be ignored, and no interactive scripts are tested in batch mode. All output and failed scripts are logged to an output file. If an output file is not specified, the default is AP2.OUT.
|If this parameter is specified, all scripts that FAIL will also be logged to this file.
|Specifies that AP2 will automatically test device capabilities at startup.
|Specifies that AP2 will preform no testing of device capabilities at startup.
|Specifies the data path to be used by AP2. This is the same as selecting the Data Path button.
Starting and Running AP2
When running AP2 for the first time, it is necessary to set the Data Path. The Data Path points to the directory where all the data files for AP2 are located. Every AP2 script that requires a data file uses an environment variable AP2PATH, which is set by AP2.
The Start Test button tests the selected scripts. To test scripts, highlight the selected scripts and click on the Start Test button. After each script is completed, the status for that script is displayed. The output for every script is located in the OUT directory. The output file has the same name as the script with the extension of "OUT".
The View Output button allows the viewing of the files that are generated from the execution of the *.P2S files. To view the output for a specific script, highlight the script, and click on the View Output button.
The Data Path button displays a dialog box and allows you to select the location of the AP2 data directory. AP2 will not run correctly if the data path is not set to the directory containing the AP2 data files.
Use the P2STRING script processing tool to test media control interface string commands in the MMPM/2 environment.
The P2STRING tool processes script files (containing string commands and tool directives) to test string commands in your application programs. The P2STRING tool tests your low-level components at the Ring 3 level (as compared to the PMADDE tool, which tests code at the Ring 0 level). P2STRING extracts the strings from the script files and processes the commands through the mciSendString function. Messages and error conditions of the processes included in the scripts are logged to an output file and displayed in windows. P2STRING comes with a set of predefined scripts to test audio and video functions. These tests are a group of test files called test suites. For more information about test suites, see Testing Device Drivers.
Each process logs to its own display window, but all processes log to the same output file. In addition, if you close the display window, the string execution thread is immediately destroyed and the entire process ends.
Output messages include all non-comment lines read from the script (for example, script directives, command strings, expected return values, expected and received notify messages, and status lines). In addition, errors and debugging statements of unsuccessful string commands are logged to a file named P2STRING.LOG file.
Setting Font Size and Type
Before you start the P2STRING tool, you can change the size and type of font displayed in the P2STRING window on the desktop. For example, to specify Times Roman font with a 10 point font size, type:
You can specify either font face, font size, or both. Possible FONTFACE values include SYSTEM, COURIER, TIMES, or HELVETICA (default). Possible FONTSIZE values include 8 (default), 10, 12, 14, or 18.
Starting P2STRING
The P2STRING tool consists of two files: P2STRING.EXE and P2S_DLL.DLL. These files are located in the IBM Developer Connection Device Driver Kit for OS/2. The following example displays the syntax used to start the P2STRING program. Associated parameters are described in the following table.
P2STRING inp_file [-a]out_file [-eerr_file] [-d|-D] [-E] [-t]
Note: The parameters are case sensitive.
The following list describes the parameters associated with the P2STRING program.
|Specifies the script file name you want to process.
Note: Refer to P2STRING Script Language for information on the contents of a script file and how to interpret the script language.
|Specifies the output file name containing the results of the test. This file contains only the results of the test you are running, unless you specify the optional -a parameter. For example, to append the output of a script file named SAMPLE.SCR to output currently in a file named MDM.OUT, type:
|Specifies the optional error file name that receives messages from string commands that completed unsuccessfully. For example, to create an error file named MDM.ERR, type:
|[-d | -D]
Specifies one of the following optional parameters:
|Causes the script file to exit after the first error. By default, script files run to completion regardless of errors. For example, the following command ends the processing of SAMPLE.SCR after an error is encountered:
|Records time stamps for strings and MM_MCIPASSDEVICE notification messages.
P2STRING Script Language
This section describes the contents of a script file and how to interpret the script language. Script files can contain several types of lines including:
- Comments
- Tool Directives
- MMPM/2 String Commands
- Expected Return Strings
- Expected Error Messages
- Expected Notification Messages
The following example displays an example of how a script file appears.
@PROCESSES = 2 @EVENTS = {HASCTRL1=1, HASCTRL2=0} # # # @PROCESS 1 ; ; set masteraudio level for session to 10% - will affect all ; 3 processes ; masteraudio volume 10 ; ; open waveaudio device non-exclusively ; open waveaudio alias wav1 shareable notify + MM_MCINOTIFY MCI_NOTIFY_SUCCESSFUL MCI_OPEN #1 @WAIT_NOTIFY 1 60000 @WAIT_PASSDEVICE wav1 60000 @WAIT_NOTIFY 21 60000
Script comment lines must start with either a semi-colon(;) or comment sign(#) in the first column. These comment lines are neither displayed nor echoed in the output file. If you want a remark to appear in the output, use the @REM directive.
P2STRING allows for a variable number of lines to be displayed in its window. Regular comment lines (header lines) are not displayed nor written to the output file.
Tool Directives
The P2STRING tool supports either multithreaded or multiprocess execution, but not both. You can use tool directives to test either @PROCESSES or @THREADS in a script file.
Tool directives start with an at sign(@) in the first column. These directives affect the execution and appearance of the output. The following classes of directives are recognized:
- Initialization
- Execution
Initialization Directives
Use initialization directives to set up the content of the script file. These directives must appear before execution directives because the tool preprocesses the script file and builds process command buffers.
The @THREADS and @PROCESSES directives are mutually exclusive. In other words, the P2STRING tool supports either multithreaded or multiprocess execution in a script file (not both). In addition, there is a limit of 10 processes or threads per script file.
The following table lists the supported initialization directives.
|Specifies the number (x) of processes the script file will be running. For example:
|Specifies the number (x) of threads the script file will be running.
|@EVENTS={n[=0|1] [,n[=0|1]]}
|Specifies one or more names of events. Events are user-defined with a maximum of 15 characters. Events can be set to 1 or 0. Set an event to 1 for an event that is set with the @SET_EVENT execution directive. Set an event to 0 to clear or reset the event. If no initialization values are specified, the event is initialized to 0. For example:
Execution Directives
Use execution directives to process the script file. Again, the @THREAD and @PROCESS directives are mutually exclusive.
The following table lists the supported execution directives.
Note: Timing out on the @WAIT_EVENT and @WAIT_NOTIFY directives is not considered a failure.
|@THREAD x
|Specifies that the script lines following this directive belong to thread number x until the next @THREAD directive is encountered.
|@PROCESS x
|Specifies that the script lines following this directive belong to process number x until the next @PROCESS directive is encountered.
|@SET_EVENT name 0 | 1
|Sets the event name to either 1 or 0. Use 1 to mark that the event has happened. Use 0 to clear or reset the event.
Note: The event must be declared through the @EVENTS directive.
|@WAIT_EVENT name [to]
|Waits until the event name is set to 1. @WAIT_EVENT does not cause a change of the event state. If you need a reusable event, use this directive.
The timeout (to) is specified in milliseconds. If omitted, it defaults to 3 minutes.
|@WAIT_NOTIFY x [to]
|Waits for a specific number (x) from an expected MM_ MCINOTIFY notification message. This number must match the index used in the MM_MCINOTIFY reference line. The @WAIT_NOTIFY events are not reusable because there are no events that logically reset it.
The timeout (to) is specified in milliseconds. If omitted, it defaults to 3 minutes. If the associated mciSendString function fails, the event is posted to prevent delays for notifications that are never going to be sent.
|@WAIT_PASSDEVICE alias [to]
|Waits until the device instance with an alias of alias gains use. This assumes that the alias names used within a script file are unique. The maximum alias name length is 20 characters.
Note: Use a unique alias for every OPEN command. The timeout (to) is specified in milliseconds. If omitted, it defaults to 3 minutes. The tool assumes that a unique alias is specified on each OPEN string command. If unique aliases are not used, errors conditions might occur.
|@REM comment
|Echoes the comment to the screen and the output log file. All other script comment lines (those starting with ; or #) are neither transferred nor displayed.
|@PAUSE to
|Pauses processing of the current thread or process in the input script file for the specified time. It does not stop the processing of the notifications or window functions. Other threads or processes are not affected by this directive.
|@BREAK [message]
|Causes a message box to appear with message text. Script processing is halted until the user responds with the correct action . For example:
|@CHECK [message]
|Grades the success of the previous command based on the user's response. A pop-up window displays the message and prompts the user with Yes or No push buttons. The status is passed if the user selects Yes, or failed if No is selected. For example:
@BREAK The music will play for 5 seconds. Ready to time it? play cdaudio notify @PAUSE 5000 @CHECK Did it play?
MMPM/2 String Commands
All lines that do not fall into any of the other categories are interpreted as MMPM/2 string commands. These lines are passed to the Media Device Manager (MDM) through the mciSendString function after the environment variables have been substituted.
Any token in the string command line bracketed by question marks (such as ? FOO?) is interpreted as an environment variable. The actual value of the environment variable is substituted into the string before it is passed to the mciSendString function. If the variable is not found, a warning is issued and the token is replaced with a null string. For example, assuming the environment string MMDATA is set to D:\DATA, open ?mmdata?\temp.wav alias a is equal to open d:\data\temp.wav alias a.
Expected Return Strings
Many MMPM/2 commands return strings. It is possible to check these strings against an expected value with an expected return string line.
An expected return string line has the format:
The equal sign(=) must be in column 1 and should have no trailing spaces. If an empty string is expected, nothing should follow the = (not even spaces). For example:
status cdaudio ready wait =TRUE status cdaudio mode wait =stopped
The expected result is always interpreted as a string. This might produce some unusual outputs for commands that return binary data.
Where the return is a textual numerical value, it can be matched to a tolerance range of +/-10% using a tilde (~) before the number. This is typically used when the exact value cannot be known. For example:
set foo time format milliseconds wait play foo notify @PAUSE 1000 stop foo wait status foo position wait =~1000
Thus, the status command is considered successful if the returned string is in the range 900 - 1100.
Expected Error Messages
When an MMPM/2 string command is expected to fail with an error, use the expected error line to specify the expected error. The expected error line has the format:
The =! must start in column 1. If any error is acceptable, then use the keyword ERROR. If a specific error is expected, type the exact error message after the =!. For example:
open sequencer alias mymidi wait load mymidi nofile.foo =!File not found.
Be careful about extra blanks in the expected-error and expected-result lines. The case of the strings is unimportant; however, the comparison will fail if the spacing or punctuation does not match exactly.
Expected Notification Messages
Many MMPM/2 string commands cause notification messages to be sent to the P2STRING tool. The system uses notification messages to respond to applications. For example, notification messages indicate system status regarding completion of a media device function or passing of the ownership of a media control device from one process to another.
It is possible to verify that the proper notifications are received by using an expected-notify line. Each expected notification line begins with a plus sign (+) in column 1. The following types of notification lines are possible:
- Command completion/error notifications
- Event notifications
- Position change notifications
Note: Any or all notification messages might be expected for a single MMPM /2 string command.
Command Completion/Error Notifications
A MM_MCINOTIFY line notifies an application when a device successfully completes the action indicated by a media message or when an error occurs.
+MM_MCINOTIFY notify-code [#x]
|Specifies the notification message code, for example, MCI_NOTIFY_SUCCESSFUL. The spelling must be the same as the #defines in the OS2ME.H file for the notify codes.
|Specifies the media control interface message that caused the notification, for example, MCI_PLAY. The spelling must be the same as the #defines in the OS2ME.H file for media control interface messages.
|Specifies a unique number (x) used to associate @WAIT_NOTIFY directives with particular notifications. This number has nothing to do with the order in which strings are sent. The number must be unique and in the range 1-99.
Event Notifications
A MM_MCIPOSITIONCHANGE line notifies an application of the current media position.
+MM_MCIPOSITIONCHANGE position %user-parameter #x
|Specifies the expected MMTIME position of the first position-change message.
|Specifies the user parameter to be returned. This should be the same as the return value specified in the SETPOSITIONADVISE string command. Note that the return value must be a unique integer in the range of 1 - 99.
|Specifies the number (x) of position change messages expected. For further information, refer to Limitations of MM_MCIPOSITIONCHANGE Verification.
Position Change Notifications
A MM_MCICUEPOINT line notifies an application that the playlist processor has encountered a messageinstruction.
+MM_MCICUEPOINT position %user-parameter
|Specifies the expected MMTIME position of the first position-change message.
|Specifies the user parameter to be returned. This should be the same as the return value specified in the SETPOSITIONADVISE string command. Note that the return value must be a unique integer in the range of 1 - 99.
Note: Other notifications cannot be compared because they do not allow for a user-parameter as part of the message, which is essential for the tracking of related notifications.
Limitations of MM_MCIPOSITIONCHANGE Verification
There are limitations to what you can verify in the P2STRING tool using event notification lines. The MM_MCIPOSITIONCHANGE line requires the use of the "return value" item in the respective string commands. This line also does not provide for timing start point, for example, playing has started. The P2STRING tool can only count the number of messages received for a specific user parameter (used as a key) and check if subsequent messages have positions approximate to the given expected position interval. The script writer has the responsibility to determine how many POSITIONADVISE messages are expected, taking into account the duration of playing, time format, and start position of the play/record. The reference position given in the expected notification line must be in MMTIME units. If the "expected number of messages" parameter is omitted, the tool verifies only the position interval (not the number). In case of scripts where play, seek, or record are used to cover non-monotonic ranges, the tool might report failures on position-advises because it expects each positionadvise to be in the next position interval from the previous message. If the script makes a jump to a position that does not conform to this, the status will be logged as failed.
For example:
setpositionadvise SomeDevice every 10000 on return 5 +MM_MCIPOSITIONCHANGE 10000 %5 play SomeDevice from 35000 to 55000 notify (produces 3 positionchange messages) seek SomeDevice to 30000 wait play SomeDevice notify (produces a number of messages starting at 30000)
The position-change messages are logged as failed, because of the lapse in position interval. A way to handle this situation is to disable the position-change before an explicit position jump is made and enable the same position-advise with a different user parameter.
For example:
setpositionadvise SomeDevice every 10000 on return 5 +MM_MCIPOSITIONCHANGE 10000 %5 play SomeDevice from 35000 to 55000 notify (produces 3 positionchange messages) setpositionadvise SomeDevice every 10000 off seek SomeDevice to 30000 wait setpositionadvise SomeDevice every 10000 on return 6 +MM_MCIPOSITIONCHANGE 10000 %6 play SomeDevice notify (produces a number of messages starting at 30000)
Processing Logic
A string command line can be followed by zero to one return value lines, or zero to three notification lines. Note that this is an exclusive OR, meaning that specifying both expected return value and expected notification is not going to give reliable results due to the fact that returned buffer does not become valid prior to the end of the notify message. Also, in case of notify flags, return values are in the procedural interface format rather than in the string interface format.
The MDM will not be able to convert return values to strings for commands processed with the notify flag because media control drivers will be sending their notify messages directly to the application.
Status of each command is determined in two stages. The first stage is at string execution. If the mciSendString function returns an error and there was no =!ERROR reference line in the script following the command string line, the command is considered failed. If a return value was found after mciSendString is processed, the tool will check for expected return and perform comparison of the two. It they do not match, the command is considered failed. In case of an error that is not in the range understood by the mciGetErrorString function, the command is considered failed even if the !ERROR was encountered.
The second stage of the comparison is after a notification is received and after all the commands are issued. If a notification was received and it was successfully compared to the expected notification line, the command is considered successful. If there was no reference notification line, status of the command will not be assigned, unless notify-error was returned. After all the scripts are processed, expected reference notifications will be used to determine if all the notifications were received. The commands that did not receive a notification, and had an expected notification line of the type, are marked failed. Note that command strings are not examined for presence of a notify flag and it is the writer's responsibility to create an expected notify line if it is of importance. In case of expected NOTIFY_SUCCESSFUL messages, all codes other than NOTIFY_ERROR are considered valid. This includes NOTIFY_SUCCESSFUL, NOTIFY_ABORTED and NOTIFY_SUPERSEDED. If any other notify code was specified as expected, and exact match will be checked for. If NOTIFY_ERROR is expected, all errors in the range are verified as passed. There is no facility for verification of an exact error code returned in the notification.
Testing Device Drivers
Test suites have been provided with this release of the DDK to assist in certifying audio and video device drivers. The test suites provided consist of several test cases. The following sections describe how to:
- Set up the environment for running the test suites
- Run the test suites
- Analyze the test
Setting Up the Environment for Running Test Suites
Before using the audio or video test suites with the P2STRING tool, do the following:
1. Make sure that OS/2 2.1 and the adapter to be tested are installed.
2. Update the CONFIG.SYS file.
- All the test suites use environment variable to determine the location of the input data files. Add the following SET statements to the CONFIG.SYS file.
- SET MMDATA=<path>
- SET MMDATA-AUD=<path>
- SET TESTDATA=<path>
- The path for MMDATA and MDATA-AUD must specify the path to the audio input files. For example, your .WAV or .MID files. The path for TESTDATA must specify a path to a temporary working directory that you create.
- The following files must be loaded, and their path must be specified in the CONFIG.SYS file:
3. Shut down and restart your workstation so the CONFIG.SYS parameters will take effect.
4. Run HWCODE.CMD for each test suite to be tested.
- This file is in the IBM Developer Connection Device Driver Kit for OS/2 HWCODE.CMD is a REXX command that determines each test case's exact hardware needs and displays the results. The test case's name contains information that HWCODE.CMD uses to make these determinations, so it is important not to change the name of the test case.
- The syntax for HWCODE.CMD is:
HWCODE <Test Case Name>
- Note: The Test Case Name must include the file name extension. HWCODE.CMD displays the brand and model of audio and video adapters currently supported by OS/2 2.1. The adapter being tested is not listed if it is new , but this information is useful for comparing results based on expected compatibility with other manufactures.
- HWCODE.CMD also displays audio and video hardware codes.
Hardware Codes
The hardware codes are two digit codes. The hyphen (-) in the tables indicate the position of the unspecified digit in the code. For example, if you receive the hardware code 84, you would look in the 8- column and the - 4 column to decipher the hardware code.
Audio Hardware Codes
|Hardware Code
|Number of Cards Unspecified
|Hardware Code
|Number of CDROMs
|OPL0 (original Sound Blaster chipset)
|Sound Blaster 16
|ProAudio Spectrum 16
|Sound Blaster Pro
|Any Sound Blaster
|OPL0 (original Sound Blaster chipset
|Sound Blaster 16
|ProAudio Spectrum 16
|Sound Blaster Pro
|Any Sound Blaster
|Sound Blaster 16
|ProAudio Spectrum 16
|Sound Blaster Pro
|Any SB
|OPL0 (original Sound Blaster chipset)
|Sound Blaster 16
|ProAudio Spectrum 16
|Sound Blaster Pro
|Any SB
|Hardware Code
|Special Hardware Needs
|Pioneer laser disc V80000
|Pioneer laser disc V4400
|Pioneer laser disc V4200
|Pioneer laser disc V4300D
Video Hardware Codes
|Hardware Code
|Number of Cards Unspecified
|Hardware Code
|Number of CDROMs
|Any video capture card
|Any video capture card and a Sound Blaster 16
|Any video capture card and a ProAudio Spectrum 16
|Any video capture card
|Any video capture card and a Sound Blaster 16
|Any video capture card and a ProAudio Spectrum 16
|Any video capture card
|Any video capture card and a Sound Blaster 16
|Any video capture card and a Sound Blaster 16
Please note that this is as it was printed in the original MMPM/2 DDR, it is more than possible that "-I" should be "Any video capture card and a ProAudio Spectrum 16"
|Hardware Code
|Special Hardware Needs
|Jovian SuperVia NTSC
|Jovian QuickVia NTSC
|Video Blaster NTSC
|Jovian SuperVia PAL
|Jovian QuickVia PAL (WinMovie)
|Video Blaster PAL
Running the Test Suites
The suites are run using P2STRING. For more information about P2STRING, see AP2/P2STRING Tool.
To run a device test, do the following:
- 1.Open an OS/2 window.
- 2.Run SETENV.CMD.
- Note: Nothing is displayed when running this command. When the OS/2 command prompt is displayed again, this command is finished.
- This file is in the IBM Developer Connection Device Driver Kit for OS/2. This command should be run prior to running the first test (each time you open an OS/2 window) because it sets up the audio devices correctly. To run this command, type:
- 3.Run RESETINI.CMD prior to each test.
- Note: Nothing is displayed when running this command. When the OS/2 command prompt is displayed again, this command is finished.
- This file is in the IBM Developer Connection Device Driver Kit for OS/2. This command resets system connections in the appropriate INI files for audio and video tests to their defaults. To run this command, type:
- 4.Run each test. Each test can be run from the command line and the output is saved in a file for analysis. The P2STRING syntax is:
P2STRING inp_file [-a]out_file [-eerr_file] [-d|-D] [-E] [-t]
For more information about running tests from the command line, see Starting P2STRING.
The tests display messages in a message box and might not automatically close the message box when the test finishes. If the test does not close the message box, you need to manually close it. The message box is not closed if P2STRING is waiting for a return value that might or might not be returned. The test has finished processing if the string "Script completed successfully" is displayed at the bottom of the message box. Allow approximately one minute after this message is displayed before manually closing the message box to allow for any late return codes.
Note: The "Script completed successfully" message does not indicate that all the tests passed. It only indicated the script has finished processing .
Analyzing a Device Driver Test
After an audio or video test is run, the results of the test are stored in a file with a .IND extension appended to the file name. The media control interface strings that passed are flagged with a PASSED keyword in the return string, and failed strings are flagged with a FAILED keyword.
Those that are flagged as FAILED can be analyzed further. When all strings are passed successfully, the device driver is handling all conditions specified by the test correctly.
Note: If a string command is supposed to fail and does, the return string is considered PASSED, because the return string matches the expected results.
The following example illustrates how to compare the results file with the test script.
TEST SCRIPT (AUDIO1.P80) ############################################ # # # OPEN THE MIDIPLAYER # # WAIT FOR SUCCESSFUL OPEN # # # ############################################ # /---> open sequencer alias midiplayer notify |/--> +MM_MCINOTIFY MCI_NOTIFY_SUCCESSFUL MCI_OPEN #1 || @WAIT_NOTIFY 1 45000 || @WAIT_PASSDEVICE midiplayer || ############################################ || # # || # LOAD AND CUE TYPE1. MID FILE # || # PLAY jesu.mid FILE AND EXPECT AN # || # ABORT FROM A PAUSE # || # # || ############################################ || # || /-> load midiplayer ?MMDATA-AUD?\jesu.mid wait || | cue midiplayer output wait || | play midiplayer from 100 to 60000 notify || | +MM_MCINOTIFY MCI_NOTIFY_ABORTED MCI_PLAY || | # || | || | || | TEST OUTPUT FILE (AUDIO1.LOG) || | || | || | ****************Opening script file || | || | || | Thread 1 executing 21 commands. \|--|--------> T:1 send string # 1 open sequencer alias midiplayer notify \--|--------> EXPECTED NOTIFY FOR #1: MM_MCINOTIFY SUCCESSFUL by MCI_OPEN script param= 1 | |--> T:1 Notify received for # 1 MM_MCINOTIFY SUCCESSFUL by command MCI_OPEN ID 1 | \--> NOTIFY STATUS FOR #1: PASSED | T:1 Notify received MM_MCIPASSDEVICE MCI_GAINING_USE Device ID 1 | returned string for # 1: 1 | T:1 @WAIT_NOTIFY 1 45000 | T:1 @WAIT_PASSDEVICE MIDIPLAYER \--------> T:1 send string # 2 load midiplayer D:\SYSTEST\DATA-AUD\type1.mid wait |--> no returned string for # 2. \--> NOTIFY STATUS FOR #2: FAILED . . . END OF SCRIPT FILE REACHED. 14 COMMANDS SENT Waiting for late notifications for 30 sec T:1 Notify received for # 14 MM_MCINOTIFY SUCCESSFUL by command MCI_CLOSE ID 1 NOTIFY STATUS FOR #14: PASSED Script completed successfully
The first command "open sequencer alias midiplayer notify" in the test expects the following results:
Following the first and second line down in the previous example, you can see that this command passed successfully:
EXPECTED NOTIFY FOR #1: MM_MCINOTIFY SUCCESSFUL by MCI_OPEN script param= 1 T:1 Notify received for # 1 MM_MCINOTIFY SUCCESSFUL by command MCI_OPEN ID 1 NOTIFY STATUS FOR #1: PASSED
The following lines in the test script are not expecting returned information:
@WAIT_NOTIFY 1 45000 @WAIT_PASSDEVICE midiplayer
Therefore, the test output echoes these commands to show they were received.
However, the "load midiplayer ?MMDATA-AUD?\jesu.mid wait" command did not receive the expected message, and the following is logged to the test file:
T:1 send string # 2 load midiplayer D:\SYSTEST\DATA-AUD\type1.mid wait no returned string for # 2. NOTIFY STATUS FOR #2: FAILED
The bottom of the test output file indicates how many commands were processed, it also indicates if it is waiting for late notifications. Depending on the test, and the devices being tested, expected notifications might not always arrive on time or in the order expected. If a notification does not arrive when expected, it can arrive later if the device driver has not failed.
This is especially important on multi-threaded or multi-process processing. The more complicated the test (for example stress testing the device driver with multiple devices), the more difficult it is to decipher the output file. You will have to keep track of each thread or process separately to determine the results of the test.
Reprint Courtesy of International Business Machines Corporation, © International Business Machines Corporation


text:
Cratejoy Launches Subscription-as-a-Service Software
Have an existing business and a loyal clientele? Cratejoy may just be what you need to take it to the next level. Cratejoy is an Austin, TX-based startup that just this week received $4 million in investor funding. It provides customers with a software platform to create and manage their own online subscription box service, where a recurring monthly fee is charged in exchange for a mailed box full of products, the contents of which are
Subscription Insider now embargoes NEWS and FEATURE articles 14 days after they are published.
All registered site users can enjoy access to our full archive of news and feature content by logging in.
Remember — Subscription Insider membership includes access to all embargoed content.
Subscription Insider has upgraded to a new technology platform and our login process has changed:
- Newsletter Subscribers (Free): Please log in using the email you used to signup for our Newsletter. The first time you log in, you will need to reset your password.
- Registered Site Users: Please use the email and password you used when you registered for free site access for Subscription Insider.


text:
DMCA Notice
To Whom It May Concern,
This is a notice in accordance with the Digital Millennium Copyright Act of 1998 (DMCA) requesting that you immediately cease to provide access to copyrighted material. I wish to report an instance of Copyright Infringement, whereby the infringing material appears on a website for which you are the host.
- The infringing material, which I contend belongs to me, is the following:Android Apk Games & Apps Free Download
- The infringing material is located at the following URLs:http://www.apktrape.com
- My contact information is:
- email@example.com
- I have a good faith belief that the use of the described material in the manner complained of is not authorized by the copyright owner, its agent, or by operation of law.
- The information in this notice is accurate, and I am either the copyright owner or I am authorized to act on behalf of the copyright owner.
I declare under the perjury laws of the United States of America that this notification is true and correct.
- Signed:
- kashif


text:
Romcon2014 Readers rated books
I just got some fantastic news. Romcon's Reader Rated Books awarded my paranormal romance novel Passion's Sacred Dance, a fantastic rating of: in their paranormal romance category. *squee* *This close* To finaling. *This* close! Who, me? Excited? You bet! Would you like to see why? It's available at the usual places. Amazon (who–yep–still seems to have… Continue reading Romcon2014 Readers rated books


text:
Resultados para: lumberjanes 2
3 produtos
Lumberjanes Vol. 2Hicks, Faith Erin(9636182)
The second collection of the award-winning Lumberjanes is here! Five girls become instant best friends when they go to camp and discover there is a lot more to the summer than learning to how to paddle a canoe. Miss Qiunzella Thiskwin Penniquiqul...
Lumberjanes/Gotham Academy #2Chynna Clugston Flores(9546092)
What the junk-Jen is missing?! The Lumberjanes and Gotham Academy crew regroup at camp to figure out how to find their missing friends.
Lumberjanes To The Max Edition Vol. 2Noelle Stevenson; Shannon Watters(9503017)
Together, Jo, April, Mal, Molly, and Ripley take on everything that goes bump in the night. From scary stories to magical portals that lead to a land untouched by time, it'apos;s definitely not your average summer! Camp counselor Jen just wants to...


text: Mercure Bali Legian is strategically located in the Legian area at the intersection of popular tourist destinations. It is walking distance to the surrounding places of interest such as Legian beach, Seminyak and Kuta area. The Legian area features a haven of restaurants, bars, shopping outlets, night clubs, and beach attractions. The brand new Mercure Bali Legian is the perfect hotel for business or leisure travel and is ideal for anyone from families, to honeymooners, to corporate clients.