text:
Results tagged ' Las Vegas '
And the beat goes on?
As Wayne Messmer belted out the National Anthem prior to the start of Thursday's battle between the Cubs and White Sox, a few rows of seats were noticeably empty behind the White Sox dugout at Wrigley Field. Those areas pretty much filled in by the time the White Sox were done hitting in the top of the first, but this particular scenario represents just one small reason from the first two days of this series to give pause for thought as to whether the all-Chicago competition is as electric as it once was.
"Yeah. I thought it was down a little bit," said White Sox catcher A.J. Pierzynski, when asked after Wednesday's victory whether the capacity crowd seemed a bit more subdued. "I think maybe the fact that we play them six times a year, once here and one there, and we played them like 10 times in Spring Training this year.
"It's still fun to come here and still a great atmosphere, still fun games to be in. It just seemed like there wasn't as much energy as there has been in the past for this series."
The White Sox and Cubs actually played five times during Spring Training, including a two-game excursion to Cashman Field in Las Vegas. Other ideas presented by White Sox players for the series being toned down ranged from Tuesday's rainout offering a bit of a buzz-kill to these games serving as just the second mid-week series in the 13-year history of the competition.
"D (Derrek) Lee and and I were talking at first, and we were saying how once you've been in it for a few years, it's not downplayed but a little more mellow because you've already been through it," White Sox center fielder Brian Anderson said of the rivalry. "I'm sure if you ask Gordon (Beckham), especially getting like eight ground balls in a row yesterday, he's probably all into it."
Regardless of a possible slight drop in the fever pitch, the White Sox players agree it's still the best show in town and potentially the best rivalry in Interleague Play.
"There's a better atmosphere here then any regular mid-week game, for sure," White Sox pitcher John Danks said.
"Only a few people in this town root for both teams," White Sox manager Ozzie Guillen said. "If you're a Cub fan, you're a Cub fan. That's the way it is. Like I say, a few people do that, they don't care and root for both teams. But as long as we're given an opportunity to play this game, it's going to be a rivalry."
Wednesday roundup
–Jayson Nix still features that massive wrap around his right quad, but he told me on Wednesday that he's definitely feeling better. His target is to be playing again on Friday, during a road game against the Padres in Peoria.
Nix hurt his right quad going for a short pop up in a game last Wednesday against the Cubs in Las Vegas and then truly felt the injury as he was going from first to third on a base hit in that same game. He has not played since.
I can attest that it was a ridiculously cold night in Las Vegas last Wednesday, and the high winds were pretty much out of control, which might have been contributing factors to the injury–at least the cold. The good news for Nix is there are still three weeks left in Spring Training for him to build off of his great start in the battle for the job at second base.
–Gordon Beckham doubled and drove in two runs on Wednesday and will start at shortstop on Thursday in Surprise. Beckham has five doubles and 18 total bases this spring, leading the team in both categories.
Here's an interesting comment from Ken Williams that didn't make it into my Wednesday story. In that story, the White Sox general manager admitted the team's top pick from the 2008 First-Year Player Draft has as good of a chance as Nix, Chris Getz or Brent Lillibridge to break camp with the team BUT only as a starter at second base.
"He's playing the game and having fun," said Williams of Beckham. "He's going to be a good player. He's been impressive since we drafted him, and obviously, he was impressive before then for us to draft him."
— The first cuts came down on Wednesday. They were INF Brian Myrow, RHP Brad Salmon and INF Sergio Santos, who were reassigned to Minor-League Camp, and RHP Lucas Harrell, who was optioned to Double-A Birmingham. With these cuts, the White Sox have 53 players in camp: 26 pitchers, six catchers, 14 infielders and seven outfielders.
–Javier Castillo returned with a bang from his stint with Panama in the World Baseball Classic. He singled and scored the tie-breaking run on Wednesday and then launced a two-run home run to put the game away. Even though Panama didn't advance, Castillo loved his experience in The Classic.
–Ozzie Guillen had this interesting comme on Jerry Owens, whose seventh-inning single gave the White Sox the lead.
"This kid is fighting for his job," Guillen said. "I want to see a lot of better stuff come around. The last couple of days he's swinging the bat better."
Owens still seemed very positive when I taked to him this past weekend for a story. Owens, now hitting .200, is out of options, meaning he is fighting for a roster spot but also probably fighting to stay as part of the organization.
— My pick of DePaul to win the Big East Tournament came up a little short. My total focus is on Michigan-Iowa tomorrow afternoon in the Big 10 Tournament.
Colon and Contreras update
Judging simply by the sound of Barolo Colon's pitches during Monday's live batting practice session at Camelback Ranch, the White Sox might break camp with a veteran starting rotation in tact.
Colon and Jose Contreras have numerous tasks in front of them before being deemed ready for the 2009 regular season, but Monday morning was another in a long line of steps forward. Each hurler threw two 20-pitch innings, facing Minor Leaguers such as Miguel Negron and Matthew Inouye. Colon stayed with fastballs and change-ups, breaking off a few curves, while Contreras threw all of his pitches, from all angles.
Remember, Contreras is coming back from a ruptured Achilles, while Colon is coming back from offseason surgery to remove bone chips in his elbow. So, from a purely throwing standpoint, Contreras is ahead of Colon. That gap appears to be closing judging by the zip on Colon's pitches.
There will be another batting practice session for the two on Wednesday and then possibly live game action this weekend. Having Contreras and Colon ready instantly gives the White Sox a very deep pitching staff, with Clayton Richard and Jeff Marquez moving to long relief.
With a B Game going at the same time, manager Ozzie Guillen did not join pitching coach Don Cooper to watch Colon and Contreras throw. Gordon Beckham batted twice while I was watching the B game and had four hits–just kidding. He had one hit and drove home a run with a ground out.
By the way, for you boxing fans, Rock Newman, Riddick Bowe's former manager, was in attendance at Camelback Ranch on Monday. We had a brief discussion about the "fan man" fight, which I attended in Las Vegas in 1993, when a man paraglided into the ring during a Bowe-Evander Holyfield fight. That "fan man" has his own Wikipedia page, which is kind of sad.
Where have I been?
A hectic few days, including the Cubs-White Sox two-game series in Las Vegas, not to mention a cold or battle with allergies that won't quite go away, have kept me off the blog. But I'm back with a few news items to start the week.
–Jose Contreras and Bartolo Colon will be throwing batting practice tomorrow morning at 11 a.m. CT, as part of their continued comeback from injuries and push to the White Sox starting rotation. Ryan Braun also will be throwing batting practice on a separate field, as he battles his way back from Tommy John surgery on April 22, 2008.
I'm just guessing here right now, but I think Contreras will start the 2009 season as part of the rotation, but Colon, who is coming back from an elbow injury, will not but won't be far behind. By the way, I think both Clayton Richard and Jeff Marquez are locks to make the team in some pitching capacity.
–Gordon Beckham continues to… Well, I was going to say impress but I don't think that word is strong enough. How about amaze? He had three doubles on Sunday and has caused the White Sox to take a serious look at him as a possible starting candidate at second base, less than one year after being selected with the eighth pick in the 2008 First-Year Player Draft.
I don't think Beckham breaks camp with the team. But I reiterate that he will be playing Major League baseball before September callups. His confidence, as much as his ability, impresses me. Beckham looks as if he's been doing this for 10 years.
"Well, I hope I'm looking like that," Beckham said. "I think there's a difference in being cocky and being confident. I try to be as confident as I can without being cocky.
"Why not? I've been playing this game my whole life. The game hasn't changed. It's just the scenery and settings got a little different."
–Here's an example of Ozzie Guillen's popularity. The White Sox manager came out in the third on Sunday to check on Alexei Ramirez, who had fouled a ball off of his foot, when some fan at Camelback Ranch yelled, 'Hey, Ozzie. How are you doing?'
I watched Ozzie walk the hallways of the Bellagio Hotel during the 2008 Winter Meetings in Las Vegas, and he couldn't take three steps without someone stopping him to talk or pose for a picture.
–Michigan wins its first round game in the Big 10 tourney, and its NCAA Tournament drought is over. No questions asked. Minnesota might be the Big 10 team with the most trouble.
You heard it here first: Michigan vs. Michigan St. for the NCAA crown.
–Jayson Nix is expected back in action after Tuesday's day off. Brent Lillibridge will play Monday.
Wednesday musings
–A hearty congratulations to Jamie and Mark Buehrle on the birth of their daughter, Brooklyn Jayden, who entered the world early Tuesday morning at 6-pounds, 7-ounces. We will all have to wait until Mark returns Sunday to find out the origin of this beautiful name.
–Keep an eye on John Van Benschoten's mound work, with the right-hander pitching tonight against the Cubs in Las Vegas. He has a shot to make the White Sox as a long reliever.
–Make sure you check out Gordon Beckham's new blog, titled "Deep Thoughts By Gordon Beckham." His first entry, The Japanese Game Show, is a fun read. He's an articulate young man, and as I've said in this blog numerous times, Beckham is a player, with star written all over him.
–As I was sitting at dinner the other night at a restaurant in Westgate, three major White Sox fans–Mike, Bob and Bob (I remembered their names because they e-mailed me after the fact. The memory starts to go after 40), introduced themselves and we started talking baseball and about my job, etc. It was a most interesting conversation.
I wanted to encourage anyone who comes to Spring Training to check out the White Sox or any other baseball team, and bumps into me around town, to come up and introduce themselves. It's always good to get fans' perspectives on the team, as it often triggers future ideas for stories, and it's just as good to get feedback on our coverage–positive or changes you would like to see made.
In fact, I'm currently in Las Vegas covering the White Sox and Cubs. So, anybody who made the trip, feel free to e-mail me. We could all meet up after the game, if we could just find a place that stays open late here.
— A special thanks to e-mailer Dan, who sent me a recommendation for Firefly Tapas Kitchen and Bar on Paradise in Las Vegas. Unfortunately, this short trip won't allow me to check it out, but it's on my list for the next visit.
–Three words to describe this past Sunday's Rock of Love: Best episode ever, seriously!! That's actually four words, but it was highly entertaining.
–The word shocking should never be used to describe an epidsode of The Bachelor, as I saw on one entertainment show following Monday's finale, unless someone's talking about the ridiculous ratings that show gets. Not to rain on anyone's parade, but could someone explain the attraction of this show?
I know, I watch Rock of Love. But that show is real, at least.
–One final thought: I enjoy checking out the status updates of my various Facebook friends throughout the week. But one young lady on that list recently had an update that caught my eye. She apparently was watching the first White Sox Spring Training game in Glendale, played last Sunday afternoon, on her DVR that night.
That, my friends, is true devotion to one's team!
Roster Roulette
So, Wednesday officially begins the Cactus League ledger for the White Sox, which means I will be in Las Vegas for the Cubs-White Sox games in one week. I'm actually going to buy a small suitcase as soon as I finish blogging.
For those not concerned with my travel plans or my future purchases at Target, which pretty much covers everyone, the contest between the Angels and White Sox also marks the start of numerous interesting position battles to be waged by the South Siders. Instead of going through the primary roster openings, let's look at the roster as a whole.
If you assume Ozzie Guillen takes 12 pitchers, coupled with nine position player starters, then you are left with four open spots. One goes to a back-up catcher and one goes to a back-up infielder, probably Wilson Betemit, leaving Guillen with two roster openings. And then this equation becomes a myriad questions.
–Who is starting in center field? If it's Brian Anderson, then do both Jerry Owens and DeWayne Wise make the roster or does Guillen take a second utility infielder and risk losing Owens or Wise?
–Who wins the job at second base? If it's Chris Getz, then does Brent Lillibridge have an advantage for one of those two remaining roster spots because of his infield versatility, speed to burn AND his ability to play center? Remember, Wise, Owens, Betemit and Jayson Nix all are out of options.
–Will Guillen actually break camp with 11 pitchers, meaning only 20 roster spots are committed?
–Is there any chance Dayan Viciedo breaks camp with the White Sox?
–Can both Jose Contreras or Bartolo Colon be ready, health-wise, by the time the fourth and fifth starter's slot comes up during the first week of the 2009 regular season? While there might be a target date for these veterans to pitch during Spring Training, Contreras just told me the other day as to how there isn't a "Jose Contreras Comeback Day" set. When he's ready and White Sox athletic trainer Herm Schneider and the rest of the team's upper management agrees, Contreras will be out there.
Many questions to be answered, approximately 45 days to come to a decision. Tell me how you think this roster roulette shakes out.
Things I learned … Recently
–Apparently, I need to go see Slumdog Millionaire.
–I still think Mickey Rourke should have won Best Actor for The Wrestler. Then again, that was the only movie I saw out of the nominations.
–Michigan won't be going to the NCAA Tournament unless the Wolverines win their next three games or win the Big 10 Tournament. What happened to Manny Harris, is what I want to know?
–Taking a nap from 5 p.m. to 10:30 p.m. is not conducive for falling asleep later that night. I tried this trick out on Saturday. It won't happen again.
–There are FAR too many pseudo-reality shows on VH-1. Keep Rock of Love and dump the rest.
–I'm looking forward to Cactus League games actually beginning. Trips to Tucson on Las Vegas on the horizon in the next week.
More later. It's 85 in Glendale today, by the way.
Exploring Glendale
Thought I would share with you my Monday adventures with Danielle and Stacy from the White Sox community relations department in an area of Glendale called Westgate. Think of a glitzy, sort of in-your-face type of shopping complex like you would find in Las Vegas, only without gambling and the Kardashian sisters. At least, they weren't at our restaurant, and trust me, I always look.
As for the restaurant we visited, the food was not really good enough for me to recommend the place–although it was just one visit. There was one sort of interesting service moment, when I ordered my entree and then asked the waitress about also getting a side dinner salad. Little did I know, salad came with the entree so she actually brought two for me.
Clearly, it was my mistake, but when I told her I wouldn't have ordered another salad if I knew one came with the meal, she looked at me, smiled and said, "Awww." As they say in the game of baseball, she clearly owned me. But she also took the salad off the bill.
We followd up dinner by visiting an establishment called Saddle Ranch Chop House, where I watched a White Sox staffer ride a mechanical bull. My goal is to tackle the same challenge before I leave Arizona, although my two brothers are taking bets as to what I injure if I actually go through with it.
If you make the trip here for Spring Training, and I encourage everyone to do so to see Camelback Ranch, if nothing else, Westgate seems to be a nice evening venture after baseball. Just be careful of the parking crunch if the Coyotes are playing, since the stadium is bascially attached to the complex.
I also would liked to extend a belated Happy Birthday wish to my friend, Katie, and my Facebook friend, Denise Richards.


text:
This story is covered in the Guardian, Times and New Statesman today as a result of an independent report into the DNA database.
It has several useful applications for students:
1. The story is a good illustration of how the law on arrest has changed following SOCPA 2005 which amended s24 PACE to make ANY offence arrestable as long as (very wide) "necessary criteria" (under s110 SOCPA) are met. The result of this appears, according to one former senior police officer interviewed for the report, that the police are simply arresting for almost any offence, however trivial - a sharp contrast with the law pre-SOCPA with its categories of arrestable and non-arrestable offences.
2. The story makes a good criticism of police powers for students to raise, as the suggestion is that arrests are being made just to get as many people's DNA on the database as possible. Also, there are concerns that more than three quarters of those on the database aged 18-35 are young black men, which seems disproportionate.
3. It's a good starting point for a wider discussion about police powers and the need to balance liberty and security.
As a follow up, here is a video of Mark Thomas explaining what he had to do to get his DNA removed from the database after being arrested without charge.
Subscribe to our daily digest and get today's content delivered fresh to your inbox every morning.
Your students will love these editable PowerPoint-based game-based lesson activities. Just add your own questions! Or get your students to come up with the Qs!
This collection of teaching resources features six brand new game-based learning templates that enable you to engage and test students with multiple-choice questions (MCQs)

subset: commoncrawl


text:
SOUTHWICK - Residents in Southwick, Tolland and Granville will decide within the next three weeks if the Southwick-Tolland Regional School District should expand to include Granville students and, with state approval, launch an estimated $69 million expansion and realignment of the district's existing three schools.
Granville, which decided not to join the district when it was created some 30 years ago, will host a Town Meeting vote on joining the district and approving its participation in school upgrades Sept. 20. The Town Meeting is scheduled for 7 p.m. at the Granville Village School on Main Road.
Town Meetings will be scheduled in Tolland and Southwick on Oct. 4.
"This is a an effort to not only accommodate Granville students but to address serious needs at each of our three schools," Superintendent of Schools John D. Barry said this week.
School officials will outline both proposals at a hearing for local residents scheduled Sept. 20 at 6:30 p.m. at Southwick-Tolland Regional High School.
If approved Granville's current enrollment of about 150 students grades kindergarten to grade 8 will remain at the Village School anbd the town's estimated 50 high school students would be eligible to attend Southwick-Tolland Regional High School. Currently Granville high school students attend a variety of high schools throughout the region on a tuition basis.
The request to join the school district, Barry said, was inityiatyed by Granville's Board of Selectmen earlier this year.
Current enrollment in the three-school Southwick-Tolland Regional District is about 1,800.
More importantly, Barry said, Granville's joining the district allows school and town officials to seek project approval from the state's School Building Authority for a $69 million expansion and relignment of the high school, Powder Mill Middle School and Woodland Elementary School.
An addition at the high school, built in 1971, will change the grade structure from a 9 - 12 to a 7 - 12 facility.
The middle school will convert to a grade three to grade six facility and Woodland will serve pupils in kindergarten through grade two, Barry said.
If approved MSBA will finance about $40 million of the total price tag. Southwick taxpayers will be responsible for 84 percent of the cost or about $24.5 million. Tolland taxpayers, with the lowest number of students attending the district, will finance about four percent or $1.2 million leaving Granville responsible for 12 percent or about $3.5 million.
Building needs at each of the three schools have been the subject of review over the past 10 years.
"Approval by the respective Town Meetings and the state will allow the district to address needs at each building and maximize the benefits of state reimbursement for such projects," said Barry.


text:
Dita Von Teese Is Not Bothered by Designers Hiring Thin Models
"It's an incredible effect, so I can't ever blame them."
She explains: "When it comes down to it, I believe that the designers who are hiring the models, they deserve to pick whatever kind of models they want. At the last Jean Paul Gaultier show, he opened up the show with Beth Ditto in a dress that he made for her, and I think he's really great because he shows different kinds of women. He'll put me on the runway, and I have a different body shape, and I'm about two feet shorter than those girls ... I also love when ... I watch these girls who are built like racehorses that are over six feet tall coming out in shoes that make them even taller. It's an incredible effect, so I can't ever blame them for not putting real women in their shows all of the time. It's about fantasy and spectacle." [HuffPo]


text:
Who we are
Home » Who We are › PIA History
PIA History
Formed in 2005 by successful Sydney-based investor and current Managing Director, Mr Justin Wang, The Property Investors Alliance has grown from less than 10 staff to 110 at its 1500m² headquarters in Burwood, Sydney.
Some of our major achievements include:
|During the GFC, we prospered and so did our clients! 184 investors bought 252 properties worth about $1.09bn through the PIA.
|Sydney's property price increases by about 5%, proving PIA's investment forecast accurate.
|RBA announces likelihood of increased interest rates. Justin Wang recommends investors switch to fixed interest rate ahead of this. Forecast accurate and beneficial to clients.
|We develop Infortec, our in-house online cloud system providing all types of resources from business management tools, sales and forecasting models, visual concepts, client support services, document library, information resource, and data storage.
|New sales record - 1037 properties worth $600 Million up until December 2012. Rental department overseeing 956 properties worth $500 Million. Mortgage Department doing extremely well through brilliant individualised solutions.


text:
William was raised and grew up in the northern part of Flint where he loved recalling many, many favorite memories. After graduating from Flint Northern in 1943, Bill enlisted in the United States Navy, where he proudly served his country for three years.
William trained and worked as a skilled tradesman at Buick Motor Company, retiring after 33 years as a machine repair supervisor. He then worked for six years as an inspector for Mundy Township.
William was a member of Flint 23, Masonic Lodge, E & A.M. Washington Chapter, R.A.M. During his retirement he spent many precious hours playing golf at Genesee Hills with his family and friends. William was a member of Kirkridge Presbyterian Church in Grand Blanc for many years.
Read William's complete obituary.


text:
- News
- Calendar
- Blogs
- Sports
- Entertainment
- Business
- Lifestyles
- Community
- Opinion
- About Us
- Classifieds
- Coupons
- Local Savings
- Green Editions
- Legal Notices
- Weekly Ads
Connect with Us
Skipper of Boston Whaler ends up on the rocks on south end of Lopez
The skipper of a 22-foot Boston Whaler, who is suspected of boating under the influence, was uninjured after piloting the boat onto the rocks at the south end of Lopez Island in the early morning hours of Friday.
According to state Department of Ecology, which responded to the scene of the grounded boat along with a U.S. Coast Guard crew and members of the local Islands Oil Spill Association, the boat high-centered on the rocks shortly after midnight without a spill occurring from its fuel tank.
Alcohol is suspected to have played a role in the grounding, according to Ecology.
The boat's fuel tank is believed to contain as much as 60 gallons of gasoline and spill responders are on scene to assess damage to the vessel and to determine a plan to remove the boat from the rocks while preventing a spill.
— Scott Rasmussen
Latest news, top stories, and community events,
delivered to your inbox.
Trending Stories Oct 19 - Oct 26
Read the Oct 26
Green Edition
Browse the print edition page by page, including stories and ads.
Browse the archives.


text:
When a project hits a certain point in its life cycle, the unpleasant issue of backward compatibility begins to rear its ugly head. All of a sudden the changes introduced in a new release of the software have a dark side to them; they hold hidden possibilities that will break something one of your users depends on. This is true in both open and closed source projects, but in the open source world it seems that the community has spent less time worrying about it than in the closed source world.
That is understandable; the closed source world has paying customers who complain loudly when they upgrade to a new version of a piece of software and something breaks, but the same issues occur in open source software as well. For the world to take open source programs seriously, you must deal with the issue of backward compatibility.
In order to better prepare you, the average open source hacker, for dealing with this problem, I'd like to share some of the experiences we've had with backward compatibility in the Subversion project. With luck, you'll be able to apply some of the lessons we've learned to your own projects. Everyone--developers, redistributors of your project, and, most of all, your users--will benefit in the long run.
Before talking about backward compatibility, I want to explain the context of the examples, because without the context surrounding the project you can't make any real decisions about backward compatibility. What might be appropriate for one project can be totally wrong for another. This article draws examples from the Subversion project, a version control system designed to replace CVS, the current de facto standard in open source version control systems.
Subversion provides a client-server architecture that uses several separate network protocols that provide access to the Subversion server. The core Subversion libraries are written in C, with a command-line client providing the primary user interface. Additionally, bindings are provided that let you make use of the C libraries in various other languages. In several cases, non-Subversion clients speak the same protocol Subversion does, so there is a need to provide backward compatibility with users of the Subversion libraries and with programs that simply implement the protocols themselves.
Subversion has declared itself to be at a 1.0 level of quality and has a large user community. The project is now in a position where any break in backward compatibility will likely bring with it significant pain for users. Multiply this by the fact that a popular use of Subversion is to store source code, the most precious asset for a software developer, and so anything that makes it impossible for a user to access that data is even more critical a problem than you are likely to see in an average project.
Related Reading
Version Control with Subversion
Backward compatibility is really a series of promises to your users as to what they can expect when they upgrade to a new version of your software. Those promises often fall into three categories.
First is the promise that users can move both forward and backward in versions of a software package without incompatibilities. This is the strongest kind of promise and is very hard to maintain. As a result, many projects use it only for small upgrades. Subversion provides this kind of compatibility promise for patch releases: for example, the change between version 1.0.0 and 1.0.1. That means I can install version 1.0.0 of Subversion, use it for a while, upgrade to version 1.0.1, use it for a while, and then revert to 1.0.0, all with no ill effects.
Next is the promise that users can move forward to new versions of the software, though they may not be able to move backward again once they do. Subversion makes this promise for minor version changes, so people can move from any of the 1.0.x series of releases to any of the 1.1.x series of releases without any problems. However, they cannot necessarily move back. It requires some discipline to provide this kind of backward compatibility, but it's infinitely easier than the previous kind.
Third is the case in which there is absolutely no promise whatsoever. For obvious reasons, you want to avoid this kind of situation, because it means that the process of moving to a new version of the software is harder. Any difficulty in moving to a new version makes it more likely that people will just continue to use the old version. There's little point in releasing a new version of your project if nobody will move to it. Subversion reserves this kind of promise (or lack of promise, really) for major version number changes. For example, the move from Subversion version 1.x.x to 2.x.x will most likely have no promise of backward compatibility between the two versions.
Once you've thought about the level of compatibility you want to promise to your users, the next step is to think about the actual places your project needs to worry about specific kinds of compatibility problems.
The first kind of compatibility most people think about is API compatibility. This means that subsequent versions of a library provide the same API that previous versions do, so programs written against the previous version will still be able to compile and run with the new version. In addition to actually leaving the same functions around, this also implies that those functions all do the same thing in the newer version that they did in the older ones. Of course, there is some flexibility here, as at some point you have to be able to say, "This behavior is a bug, so we changed it"; otherwise, there is little point in releasing new versions of your software.
Second is Application Binary Interface, or ABI, compatibility. This means that backward compatibility is preserved at the level of the binary object code produced when you compile the library. There is usually some overlap between API and ABI compatibility, but there are important differences. To maintain ABI compatibility, all you have to do is ensure that your program exports all of the same symbols. This means all the same functions and globally accessible objects need to be there, so that programs linked against the prior version will still be able to run with the new version. It's possible to maintain ABI compatibility while breaking API compatibility. In C code, leave symbols in the C files but remove them from the public headers, so new code that tries to access the symbols will fail to compile, while old code that users compiled against the previous version will continue to run.
If your program communicates over a network, it has to deal with a third form of compatibility, client-server protocol compatibility. This means that a client using the version of the network protocol provided in the older releases will continue to function when faced with a newer server, and that newer client programs will continue to work with an older server. Of course, in some cases this is impossible. A new feature might require support on both the client and server side of the network. In general, though, existing functionality should continue to work with various combinations of client and server code.
Finally, if your program stores data somewhere, be it in a database or in files on disk or wherever, there is data format compatibility. Newer versions of the code need to be able to work with data files written out by older versions, and vice versa. Ideally you should also be able to build some forward compatibility into data formats. If your file-handling routines can ignore and preserve unrecognized fields, then new functionality can modify data formats in ways that do not break older versions. This is one of the most critical kinds of compatibility, simply because users become very upset when they install a new version of a program and suddenly cannot access their old data.
If your project provides code libraries that other programs make use of, you will almost certainly have to worry about API compatibility. If you work in a language that produces object code other programs link against, you will either have to worry about ABI compatibility or require your users to recompile their code for every upgrade. If you make use of a network, you probably need to consider client-server protocol compatibility; and if you store any data at all, you will have to worry about data format compatibility. A nontrivial project like Subversion has to worry about all four of these issues.
With the various types of compatibility in mind, it's now time to delve into the actual techniques for maintaining them. This is not an exhaustive list by any means. Not every technique mentioned may apply to your particular project, but they're all worth learning about.
The cardinal rule of maintaining API and ABI compatibility is that you must never remove anything from your interface. As soon as you expose a new function or data structure to your users in a public release, you have committed yourself to supporting it until your compatibility rules allow you to change or remove it, probably in your next major revision.
That means that if you want to make modifications to an API, you need to retain the existing version and add a new one alongside it. The old version remains intact, both in the public interface (such as in the header files for a C or C++ program) to ensure source-level API compatibility and in the binary object files to ensure link-level ABI compatibility.
Subversion has used this technique several times, specifically when we've needed
to add new arguments to existing functions. For example, in Subversion 1.1.0
svn export command gained the
argument, which allows you to specify your platform-specific end-of-line
character sequence. This allows you to simulate the effect of exporting a
project on a platform that has a different end-of-line sequence than the
platform you are running Subversion on. Under the hood, this required creating
a new
svn_client_export2 function, which is identical to the
previously existing
svn_client_export function but with an
additional argument for specifying the native end-of-line style. The existing
svn_client_export function continues to exist but now simply
svn_client_export2 with a
NULL end-of-line
style. This allows the project to add new functionality while still enabling
third-party code that makes use of our APIs to continue to compile and run
without changes.
Perhaps the simplest way to avoid problems when making changes to an interface is to not expose that interface to the users. This is difficult to do when you're talking about a function, because to make use of the API the caller really needs to know its name and signature. When you're talking about data structures, it often becomes a viable option.
In a C program, exposing the definition of a structure to your client means much the same thing as exposing the declaration of a function, but with one additional trick. A structure's definition includes not only its name and its contents, but also its size. If you want to maintain ABI compatibility, you cannot add or remove fields from the structure because a client might depend on that size.
For example, if you define a struct that contains two integers and put that definition in a public header file, there's nothing to keep your clients from declaring an instance of that struct on the stack in their own code. Suppose that you later add a third integer to the structure and a client drops in a new version of your library without recompiling the code. It's likely that the client's code will pass a pointer to the structure it declared on the stack into your code, and then you're in trouble, because your code compiled with the knowledge that the structure is three integers large, but the client allocated only two integers' worth of space for it, so any of your code that tries to access the third integer in the structure will access random memory somewhere, which can only lead to problems.
Other programming languages often have more elegant ways to deal with these issues. For example, Java and C++ support various means for restricting access to the internals of an object, and many languages require that all access to objects go through pointers, so the size issue is less of a problem. In raw C you really have to deal with it yourself, though, as the language provides little help.
You have a few ways to avoid these kind of problems in C. First, you can simply not give the client access to the definition of the structure. Instead, forward-declare the structure so that the client can pass around pointers to them, leaving the actual definition inside your library. All access to the structure must go through functions that you define in your library, allowing you to change them should the internals of the structure ever change. This is the opaque pointer technique, and it's probably the best way to solve these sort of issues.
Within the Subversion libraries, several places make use of opaque pointers.
One of the most prolific is the working copy library's access baton object,
svn_wc_adm_access_t. The access baton's forward definition is in
svn_wc.h. The client creates them by way of the
function (or, in versions of Subversion later than 1.0.x, the
svn_wc_adm_open2 function, another example of providing a new
function in a backward-compatible manner). All the public functions in
libsvn_wc simply accept opaque pointers to the structure.
Internally, the only place that actually has access to the definition of the
structure is the file subversion/libsvn_wc/lock.c. Note that the same
technique that keeps client code from poking around in the internals of the
access baton also keeps the rest of the Subversion libraries from doing so,
thus making it easier to modify the structure without modifying other parts of
If you absolutely need to leave the definition of a structure in public header files, but you still want to preserve the ability to change the structure later, there is a way to do it. Before doing so, keep in mind that it's much more fragile than just using an opaque pointer in the first place, mainly because it requires that your clients "do the right thing" without using any technical means to enforce that they do so. The trick is simply to provide a function that allocates the structure for you and to document that the only valid way to obtain access to an instance of the structure is to use that function. Because only your library will ever allocate the structure, you can be sure that there will always be enough memory to hold the entire thing, even if you increase its size later.
This technique has a few more gotchas. First, you can add only new fields to the structure, and you must add them to the end of the structure because clients compiled using previous versions of the definition will assume the offset of old fields within the structure are the same as they were in previous versions. Second, when adding fields to the structure you must ensure that code using the fields can deal with the new fields' not being initialized; otherwise, providing compatibility for old clients that know nothing about the fields is futile. Finally, as I already explained, there's nothing that enforces the use of the constructor functions, so it's still possible for clients to shoot themselves in the foot with this technique. If that bothers you, an opaque pointer is almost certainly a better solution.
For an example of how to provide a constructor function for a publicly
defined structure, see the
svn_client_create_context function in
svn_client.h. Please be cautious with this technique, though, as it
really is dangerous to rely on your users to do the right thing. In retrospect
(and I can say this because I wrote the client context code in Subversion and
made it a publicly defined structure in the first place), I think going with an
opaque pointer would have been worth the extra effort of creating the necessary
accessor functions. That's because I have encountered users of this code who jump right past the documentation that states that you must use
svn_client_create_context and allocate their own instance on the
stack, defeating the purpose of the constructor function and setting themselves
up for pain if and when we finally add new elements to the client context
The best thing you can do to ensure that you maintain protocol and data format compatibility is to plan ahead by designing your protocols and data formats so that you can add things to them in the future without disturbing prior versions of the code. This means you need to be able to add new elements to your files or data streams that your code can ignore if it doesn't understand them and that new code needs to be able to deal with the absence of the new elements.
The canonical place that Subversion uses this technique is within the XML
data formats used in the working copy libraries (for example, the
.svn/entries files) and the DAV-based network protocol used by
libsvn_ra_dav and
mod_dav_svn. I'm not the biggest
fan of XML, but it does make it pretty simple to create formats and protocols
that can be extended later with a minimum of problems.
Specifically, the use of XML in
libsvn_ra_dav has simplified
the process of adding parameters to functions in the repository access API. For
example, when I added the
--limit parameter to the
log command, I had to transmit that parameter to the server so it could
pass on to the
libsvn_repos-level log functions. Because the
functions in question simply send a report to the server in XML form, all that was required was to add a new element containing the parameter. New servers simply
look for the new element, and if it isn't there, they assume it wasn't sent,
preserving compatibility with old clients. Old servers ignore the new element
because they don't understand it, and the client code simply recognizes the case
by noticing when it has received more than the requested number of log entries
and ignoring the rest, allowing the new parameter to work even with a server
that does not understand it.
Of course, you don't need to use XML in order to ensure forward and backward
compatibility in your protocols. Subversion's
libsvn_ra_svn and
svnserve have a custom protocol that uses many of the same tricks
you might use in an XML-based protocol. The
svn:// protocol sends
data across the network encoded in tuples: lists of items that are known to
contain certain items. The functions for reading tuples off the wire ignore
extra entries in the tuple, so you can add new parameters and old servers will
ignore them, just like we did in the DAV-based format.
Additionally, the
svn:// protocol includes in its initial
handshake a minimum and maximum protocol version and list of capabilities
supported by the server and client. Thus, both the client and server have a chance
to adjust to the exact version of the protocol being spoken at the other end of
the connection. This allowed the addition of pipelining to the protocol shortly
before the release of Subversion 1.0 while ensuing that old clients continued
to work. See the subversion/libsvn_ra_svn/protocol file for more
details on how the
svn:// protocol works.
For forward-compatible but not backward-compatible changes, what's most important is to provide a smooth update path. There are two main ways of doing this, both of which Subversion has used at various times.
Long before Subversion hit 1.0, the developers made the decision to change
the format used when storing timestamps in the working copy code. The change
occurred slowly, over the course of a few releases. First came support
for reading the new format, so the code that parses timestamps would try the
new format, and if that failed it would try the old format before finally
returning an error if that failed. Then, after that code had been out in the
wild for a while,
libsvn_wc changed so that it wrote out
timestamps in the new format. The pre-1.0 policy for upgrades was to ensure
compatibility only within a single version. Because the support for reading the
new format went in a version before the introduction of support for writing the
new format, the project retained that compatibility. Support for the old date
format exists to this day in Subversion's timestamp-parsing code, but nothing
has written out dates in that format in quite some time.
What's important to keep in mind here is that the slow introduction of change allowed the users the ability to revert from the new version (which produced the new format timestamps) to the previous version (which knew how to read them) on the off chance that they encountered some sort of problem with their upgrade.
The addition of UUIDs to Subversion repositories is another example of how
to change an on-disk format in a backward-compatible way. Originally
Subversion repositories did not have any unique identifier; features like
svn switch --relocate were dangerous because you couldn't ensure
that both URLs referred to the same repository. To solve the problem, each
repository now has a universally unique ID stored in a new database table
(because at the time, the only filesystem back end that existed was the Berkeley
DB one). To ensure that new code worked with repositories created prior to the
addition of this feature, the lack of this table simply caused the function
that returns the repository's UUID to create the table itself, seamlessly
upgrading the repository without the user ever being aware of it.
The important item to note here is that if you can possibly make the upgrade automatic from the point of view of the user, then you should do so. Avoiding manual steps can be only a good thing.
One place where it's easy to forget about compatibility problems is in your project's dependencies. Any libraries you link against or external programs you use will each to have their own compatibility issues, just as you will. It's important to be aware of those issues when deciding to make use of a third-party product. In Subversion we've had at least three separate dependencies that cause compatibility problems. Some are internal to Subversion, and some poke through to users from time to time.
The most important kind of dependency you need to worry about is one that shows up in your public API. This can happen when you use data types defined in the library as arguments to your library's functions, such as with the Apache Portable Runtime (APR) in Subversion. Any non-backward-compatible change that occurs in the library you depend on will instantly affect you as soon as your users try to upgrade to a new version of the dependency.
When Subversion first hit 1.0, the only released version of APR was from the 0.9.x series of releases. Because Subversion uses APR in almost every part of its public interface, this means that to maintain ABI compatibility, all releases of Subversion within its 1.x branch only officially support the use of APR 0.9.x releases. While Subversion does happen to work with APR 1.0.x, official builds use 0.9.x.
The primary reason Subversion can't use APR 1.0.x is that the size of the
data type
apr_off_t has changed from
off_t (often 32
bits long on a 32-bit system) to
long (often 64 bits long on a 32-bit system). This support was necessary for interoperating with programs (Perl,
for example) that redefine the size of an
off_t via the
_FILE_OFFSET_BITS define. Because
apr_off_t shows up
in the public Subversion API, this change makes versions of Subversion compiled
with APR 1.0.x instantly incompatible with versions compiled with APR 0.9.x.
Additionally, APR uses a set of compatibility rules that allow it to drop and
change parts of its public API between major versions, so any of those kinds of
changes will cause similar types of problems as the
The important lesson to learn from this is that as soon as you let into your program a data type defined by your dependency, its compatibility issues instantly become your compatibility issues.
An interesting counterexample in Subversion's case is the Neon library, which Subversion uses as its HTTP/WebDAV client library. Neon differs from APR in two ways. First, Neon doesn't make it into Subversion's public interface, so changes to Neon's data types have a harder time making themselves seen to clients of Subversion itself. Second, Neon's interface is far less stable than APR's is. Even APR 0.9.x, despite its pre-1.0 version number, provides a high level of stability in its API. Neon has never professed to do so, with nontrivial changes in its API being reasonably common.
This means that in order to support multiple versions of Neon, Subversion
needs to jump through a few hoops. That has happened at least once, with
nontrivial amounts of shim code being introduced to
in order to account for changes in the Neon API as a result. This allowed
Subversion to function with either the old Neon API or the new one for a
reasonable amount of time while users upgraded.
While backflips like the shim code in
libsvn_ra_dav ease the
burden on its users, they don't solve all the problems. If a program uses Neon
directly in its own code as well as the Subversion API's, it's possible for Neon
upgrades required by Subversion to break backward compatibility. It's not
clear yet the best way to handle this kind of change.
Again, it is important to note that this is a valuable lesson. Once you use a library, its compatibility issues are your compatibility issues.
The last type of compatibility problem that a third party library can introduce is when the library is responsible for the on-disk format of some of your data, as in the case of Berkeley DB as used by Subversion. Upgrading to a new version of the library can result in unexpected problems if the disk formats are incompatible. This has resulted in significant issues, mainly because Berkeley DB upgrades often require manual intervention, ranging from a full dump/load cycle to a simple recovery. Vendors and distributors often package Berkeley DB so upgrades may occur without the user's conscious action.
There's not much more to say about this kind of compatibility problem other than the fact that the only real solution is education. Users need to understand the issues upgrades can bring, and ideally the problems that result from them need to specify what has gone wrong. Unfortunately, users often feel terror at the sudden inability to access their data, so panic may outweigh education in some cases.
Now that you've learned about the types of compatibility, seen some tricks you can use to help maintain them, and heard about some specific examples of how such problems can occur, it's time to think about your specific application and how these issues apply to you.
First, consider your user base. If you have only a dozen highly technical users, jumping through hoops to maintain backward compatibility may be more trouble than it's worth. On the other hand, if you have hundreds or thousands of nontechnical users who cannot deal with manual upgrade steps, you need to spend a lot of time worrying about those kinds of issues. Otherwise, the first time you break compatibility you'll easily burn through all the goodwill you built up with your users by providing them with a useful program. It's remarkable how easily people forget the good things from a program as soon as they encounter the first real problem.
Next, consider your project. If you don't actually provide a library your users embed in their own application, worrying about API and ABI stability is pointless. Similarly, if you don't store data on disk or send it over the network, the issues associated with those activities are moot. It's rare that a program has no compatibility issues at all, but it's also rare for one to encounter all the issues described in this article.
Consider again the example of the Subversion project. Subversion's compatibility policy appears in the "Release numbering, compatibility, and deprecation" section of the HACKING file in the top level of its source tree. You can upgrade and downgrade within a single minor release cycle without issue. You can upgrade to new versions in the same major release cycle without issue. When the major version number changes, all bets are off. These rules apply to API/ABI issues, data format issues, and network protocol issues.
Has the project followed this policy? The answer--as is often the case with software engineering--is a qualified yes. Subversion has in one instance added a function in a nonminor release as part of a change to fix a security problem that broke the ability to go back and forth within that specific minor version. The nature of the security problem meant sacrificing compatibility in this particular case.
Other than that, though, the policy has been a success. Users have upgraded to new versions of Subversion without fear. Various versions of the official client and server, and even third-party clients that implement the same protocols, have also enjoyed continued compatibility. The users seem happy with the compatibility promises, and the developers are not overly hampered by them. It isn't always easy, but in my opinion it's been worth it.
All projects need to consider compatibility. The issues are rarely as simple as you might like, and they require serious thought for each project, as no two are the same. Finally, be aware that worrying too much about compatibility can cripple you, so it's important not to place too high a price on it. Only you can determine how high is too high. I hope this article has given you a starting place for making that determination.
Garrett Rooney is a software developer at FactSet Research Systems, where he works on real-time market data.
Return to ONLamp.com.
Copyright © 2009 O'Reilly Media, Inc.


text:
|"Discussion of Ten-Tec Equipment" <firstname.lastname@example.com>
|Re: [TenTec] #422B Centurion Linear Amp......ARCING problem
|"mcelmer1" <email@example.com>
|Discussion of Ten-Tec Equipment <email@example.com>
|Sat, 24 Jul 2010 20:53:28 -0600
To all reading this: Ten Tec is the only amateur radio manufacturer I am aware of that has a live body answering the phone. Furthermore, you speak to a highly competent staff member either in sales or repair. I have called the "competition" on the west coast (starts with a Y) and what a cluster (fill in the rest). I can't comment on the folks at Flex or Elecraft. Mike W8TRN ----- Original Message ----- From: "BOB@W2PNJ" <firstname.lastname@example.com> To: "Discussion of Ten-Tec Equipment" <firstname.lastname@example.com>; "Ten-Tec Service" <email@example.com> Sent: Saturday, July 24, 2010 7:07 PM Subject: [TenTec] #422B Centurion Linear Amp......ARCING problem > Mr. Paul Clinton, I want to thank you for your correct diagnostic of the > arc sound occurring every 5 to 8 minutes. You were the only one with the > correct answer,a bad capacitor on the high voltage board. Some were saying > it was dust, others saying it's insects!! > I received the new circuit board on Thurs. installed it this > afternoon. I took photos as I removed the two upper boards, scratched my > head as to how to remove the upside down mounting screws supporting the > large H.V. board. Upon stepping back, getting the big picture, I realized > the two side brackets come out with the board. > Your company continues to maintain the EXCELLENT reputation of > customer service over the years. > I will be attending the national Papillon specialty dog show held in > Chattanooga Tenn. next April, I look forward to visiting the T-T plant and > saying hello. From Long Island,New York....73 Bob W2PNJ > > > > > > > > > > > > > > > > > > > > > y > _______________________________________________ > TenTec mailing list > email@example.com > http://lists.contesting.com/mailman/listinfo/tentec > _______________________________________________ TenTec mailing list email@example.com http://lists.contesting.com/mailman/listinfo/tentec
|<Prev in Thread]
|Current Thread
|[Next in Thread>
|Previous by Date:
|Re: [TenTec] #422B Centurion Linear Amp......ARCING problem, BOB@W2PNJ
|Next by Date:
|Re: [TenTec] #422B Centurion Linear Amp......ARCING problem, Rick - NJ0IP / DJ0IP
|Previous by Thread:
|[TenTec] #422B Centurion Linear Amp......ARCING problem, BOB@W2PNJ
|Next by Thread:
|Re: [TenTec] #422B Centurion Linear Amp......ARCING problem, Rick - NJ0IP / DJ0IP
|[Date] [Thread] [Top] [All Lists]


text:
Tulane football coach Curtis Johnson was more pleased with the quarterback performance in the Green Wave's afternoon practice session Wednesday at the Mercedes-Benz Superdome.
In Wednesday's morning practice, Johnson said Green Wave quarterbacks Nick Montana, Devin Powell, Tanner Lee and Jordy Joseph struggled in third-down situations, feeling the pressure of the defense, particularly cornerback Lorenzo Doss. But they picked up the pace in the afternoon.
"The quarterbacks practiced a lot better - they executed a lot better," Johnson said. "Earlier today I thought the execution was just average. We missed throws (in the morning), but they were pretty sharp (this afternoon). (WR Justyn) Shackleford made a couple great catches."
Doss' stellar ball-hawking in the secondary surfaced again, picking up another interception during passing drills. Johnson said Doss, Tulane's leader with five interceptions this past season, is averaging about a pick per practice.
Senior middle linebacker Dominique Robertson was the only notable player absent, again missing practice with a virus.
Tulane's Thursday practice, open to the media, is at Turchin Stadium at 8:30 a.m. before closing the week with indoor practices at the New Orleans Saints facility Friday and Saturday.
"We're getting a little spoiled being here in the (Superdome) and over at the Saints (facility)," Johnson said. "It's time for us to get outside and get in the heat a little bit. I hear it's going to rain tomorrow, but that's OK. We're going to play in some rainy weather, so we'd better play in it in practice."
Rachel Whittaker can be reached at email@example.com or 504.826.3405.


text: What happens when you get Jane Lynch, Zooey Deschanel, Julia Louis-Dreyfus, Laura Dern, Christina Applegate, Julie Bowen and Martha Plimpton together in the same room? Well if you're the Hollywood Reporter, you get a damn slick video filled with lots of laughs and great information for comedy and television nerds. Check out the complete, uncensored Emmys roundtable interview below!


text:
DUMAS - Ada Twyla Rosser, 89, died Sunday, Dec. 16, 2001.
Services will be at 11 a.m. today in First United Methodist Church with the Rev. John Wagoner, pastor, officiating. Burial will be in Dumas Cemetery by Morrison Funeral Directors.
Mrs. Rosser was born March 17, 1912, at Argyle, Fla. She was a homemaker. She was a Dumas resident for 72 years and a member of First United Methodist Church of Dumas. She married Dale Rosser in 1970 at First United Methodist Church. She was a life member of VFW and Legion.
She was preceded in death by a son, Billy Joe Parsons, on May 10, 1994.
Survivors include her husband; a daughter-in-law, Joie Parsons of Albany; two stepsons, Larry Rosser of Arizona and Tony Rosser of Jefferson City, Mo.; three grandsons, Michael Joe Parsons and Rocky Lyn Parsons, both of Albany, and Russell Lee Parsons of Fredericksburg; and nine great-grandchildren.
The family will be at 1217 Durrett in Dumas.
Amarillo Globe-News, Dec. 18, 2001
© 2016. All Rights Reserved. | Contact Us


text:
What's New
Refreshed with new graphics and updated to support iOS 5-7.1
App Description
This is the original sliding block Traffic Jam puzzle, brought to you by the company who created it – ThinkFun.
Rush Hour comes with 35 challenges, ranging from Beginner to high Expert. Enough challenges to get you hooked on Rush Hour… Upgrading to the full version will get you a whopping 2500 challenges, enough for years of Rush Hour fun!
This is a very nice collection of challenges brought to you by the geniuses at ThinkFun. You're going to have a lot of fun with your Rush Hour FREE game!
This is the ORIGINAL Rush Hour – and it's also the BEST.
Your goal is to get the Red Car out the Exit Gate. To accomplish this, just move the blocking Cars and Trucks out of the way.
Here at ThinkFun, we believe in efficient driving. So for each challenge, we track your moves against the minimum distance possible, and score you on how close you came to a perfect distance score. Each challenge becomes a quest in itself!
For your moments of frustration, we've included a HINT button. If you need a big boost, we also provide a SOLVE button. We recommend you fight your way through and never use these, but they're nice to have available.
- 35 Games, some at each difficulty level.
- Four difficulty levels – EASY, MEDIUM, HARD, EXPERT
- Measures your score against your Personal Best and the Perfect Score
- Saves multiple games-in-progress
- Hint/Reset/Undo buttons to help you figure out each puzzle
- Solve button to see how it's done
- Quick and easy Tutorial
- Keeps history of "Solved" and "Perfectly Solved" challenges
- Upgrade to Rush Hour Classic for 2500 all-new Challenges
The Rush Hour app has won a 2010 Parents' Choice Gold Award for excellence in mobile play and a 2011 Editor's Choice Award from Children's Technology Review.
If you like Rush Hour, check out our newest app - Solitaire Chess, and visit www.thinkfun.com to see more on Rush Hour and other great games from ThinkFun!
App Changes
- December 10, 2010 New version 1.3.4
- November 05, 2010 New version 1.3.3
- October 15, 2010 New version 1.3.2
- October 07, 2010 New version 1.3
- July 30, 2010 New version 1.2.1
- July 25, 2010 New version 1.2
- June 18, 2010 New version 1.1.4
- May 11, 2010 New version 1.1.3
- April 12, 2010 New version 1.1.2
- April 08, 2010 New version 1.1.1
- April 02, 2010 New version 1.1
- December 03, 2009 New version 1.0.1
- June 24, 2011 New version 1.3.4
- June 25, 2014 New version 2.0


text:
HP Scanjet 5590 Digital Flatbed Scanner
by HP | Item #: 27404 | Model #: L1910A#B1H |
We're sorry, this item is not available in your selected Club. Check another Club
About this item
- Unattended two-sided, multi-page scanning with included automatic document feeder.
- Scan up to 8 pages—or 4 images—per minute and preview scans in about 7 seconds.
- Scan documents with existing data management systems or included software.
- Plug and play using Hi-Speed USB-compatible with USB 2.0 specifications.
High-quality scans at 2400 dpi optical resolution and 48-bit color—plus fast, easy operation from a duplexing automatic document feeder. Scans slides and negatives with included adapter. TWAIN drivers and document management software included.
|Print Technology:
|Print Speed:
|Print Resolution:
|Minimum Ink Droplet Size:
|Scanner Type:
|Flatbed, ADF
|Photoelectric Device:
|35 mm film strips, mounted slides, photos up to 8 x 11 in
|Optical Resolution:
|Up to 2400 dpi
|Hardware Resolution:
|2400 x 2400 dpi
|Maximum Resolution:
|Scanner Bit Depth:
|"Preview mode- Up to 7 sec Scan resolution enhanced: 1 Up to 999999 dpi 5-button control front panel: Scan document, Scan photo, File documents, E-mail, Copy center Automatci document Feeder Capacity: 50 sheets, Paper sizes: Legal, letter, A4, custom Daily US Letter or A4- Up to 500 pages Transparent materials adapter- Included, Satellite; three slides or four 35 mm negative frames Task speed- Less than 24 sec: 4 x 6-in color photo into Microsoft Word; less than 36 sec: OCR a full page of text into Microsoft Word; less than 18 sec: e-mail photo Enlargement range- 10 to 2000% in 1% increments "
|Copy Quality:
|Copy Quantity:
|Maximum Copy Size:
|Modem Speed:
|Paper Support:
|Maximum Paper Size:
|Paper Sizes:
|"Maximum: 8.5 x 11 in, Maximum (ADF): 8.5 x 14 in (one-sided); 8.5 x 12 in (two-sided) Minimum (ADF): 3.5 x 5 in (one-sided); 5 x 9 in (two-sided) "
|Borderless Photo Size:
|Paper Types:
|Paper (banner, inkjet, photo, plain), envelopes, labels, cards (greeting, index), 3-D objects, 35 mm slides and negatives (using transparent materials adapter), iron-on transfers
|Envelope Types:
|Input Paper Capacity:
|Ink and Cartridges
|Ink Type:
|Ink Palette:
|Ink Cartridge Configuration:
|Fade Resistance / Print Longevity:
|Ink Series:
|Hi-Speed USB - compatible with USB 2.0 specifications
|Operating Systems
|Microsoft® Windows® 7 ready. For more information go to http://www.hp.com/go/Windows7. Some features may not be available. Windows Vista®, Windows® XP, Windows® XP x64, Windows® 2000
|Mac OS X v10.3.9, 10.4.11, 10.5, 10.6
|Operating Environment
|Operating Temperature:
|41 to 104° F (5 to 40° C)
|Storage Temperature:
|-40 to 158° F (-40 to 70° C)
|Operating Humidity:
|15 to 85% RH
|Storage Humidity:
|0 to 90% RH
|Sound Level:
|Rated Voltage:
|100 to 240 VAC
|Rated Frequency:
|50/60 Hz, 24 VDC, 1500 mA
|Power Consumption:
|36 watts maximum
|Additional Information
|Safety Standards:
|EU (IEC 60950 Third Edition Compliant, Third-Party Safety Certification), North America (Nationally-Recognized Testing Laboratories), Poland (PCBC), Russia (GOST)
|HP Scanjet 5590 digital flatbed scanner, Hi-Speed USB cable—compatible with USB 2.0 specifications, power cable, power supply (where applicable), automatic document feeder (ADF), ADF cleaning cloth, transparent materials adapter (TMA) for scanning slides and negatives,TMA instruction sheet, user's manual, setup poster, warranty sheet, CD-ROM(s) with software for Microsoft Windows and Macintosh: hp photo & imaging software with hp memories disc creator & hp instant share,integrated I.R.I.S. Readiris OCR, NewSoft Presto! PageManager 7, hp commercial scanjet 5590 TWAIN, (Windows only)


text:
Eleven pipers piping
Format: Audio Book on CD
Summary: Father Tom Christmas, a recently widowed vicar, would do almost anything to avoid attending an annual supper at a local hotel. But as chaplain to a traditional Scottish pipe band he must deliver the grace. The revelry carries on in the hotel until its owner-and piper, Will Moir, goes missing-only to be found dead in the hotel's tower apparently from a heart attack. Who would benefit the most from the piper's death? Father Tom investigates.
Series: Benison, C. C. Father Christmas mystery.
Current Holds: 0
System Availability: 0 (of 1)
Call Number: CD FIC BEN3401
Add to my list


text:
Excited about the upcoming football season? Of course you are. We are too.
We've combed through all of our footage from last year's season to find the most exciting moments from a banner year in Louisiana prep football. We'll be counting down the highlights throughout the summer to get you pumped up for kickoff time in September, so stay tuned every day for the most recent video.
What do you think about the list? Did we undervalue a play? Overrate? Did you have a favorite play from last season we don't have footage of? Let us know in the comment thread below.
100. Rummel's Delshone Moses forces the fumble against Shaw
99. Karr's Devante "Speedy" Noil bulldozes a defender after the fake punt.
98. Riverside's Deuce Wallace tosses perfect pass to Von Julien for a touchdown
97. Jesuit's Justin Helm pops the ball loose with a solid hit
96. Ronald Green's 62-yard touchdown run in the pouring rain
95. St. Aug's Errol Brown Jr. blows up the line of scrimmage
94. Rummel's Ivan Phipps shake and bakes for a touchdown
93. Landry-Walker's Keytaon Thompson avoids the safety, heaves to Anthony Milton
92. Riverside's Ja'corey Haynes snatches the fumble out of midair
91. St. Aug's Stanley Morgan burns the Brother Martin defense for a touchdown
90. Edna Karr's Bryan Anderson intercepts the pass in traffic
89. Warren Easton's Clyde Leflore sprints for the 74-yard touchdown
88. East St. John's Kyle Patterson takes the hit, comes down with the touchdown
87. West St. John's Trey Nathan picks off Holy Cross with one hand
86. St. Aug's Lanard Fournette rips off an 88-yard touchdown against Jesuit
85. Rummel's Briston Guidry comes up with the sack-strip-fumble
84. Brother Martin's Jake Broggi pump fakes the St. Aug defense for a TD
83. Holy Cross's Joel Dullary's 44-yard punt return TD
82. Easton's Tyron Johnson's 58-yard touchdown dash against Karr
81. Karr's Jariah Tolbert makes the leaping catch against John Curtis
80. Landry-Walker's Javon Conner burns the Easton defense for a 73-yd TD
79. Rummel blocks the St. Aug punt; returns it for a touchdown
78. Curtis' Kaleb Anderson's 45-yard punt return TD
77. St. Paul's Mitch Brumfield goes long for the 80-yard touchdown
76. East Jefferson runs the option play to perfection
75. Ponchatoula's David Nichols dives for the interception
74. Karr's Glenn Irons catches the TD in front of Nebraska's Bo Pelini
73. Shaw's Bryson Simmons leaps for the catch over a Holy Cross defender
72. Newman's Drew Drouilhet flattens Riverside's Hardell Mack
71. Covington's C.J. Sims runs right through a defender
70. Destrehan's Kirk Merrit rips off a 53-yard TD against Hahnville
69. St. Aug WR Stanley Morgan's amazing back shoulder catch
68. Karr's Quanta Moore levels Landry-Walker's Javon Conner
67. Haynesville's Jerrell Jackson torches Mangham for a 58 yard TD
66. Parkway's Brandon Harris throws a 63 yard bomb to William McKnight
65. Karr LB Donnie Alexander's pic-six in the playoffs
64. Belle Chasse's Devin Sylve breaks off a 69 yard TD run
63. Newman's Tyler Addison tiptoes for the TD
62. Karr's Juwan Offray intercepts St. Augustine's Toi Jackson
61. Covington's Cordara Laurant reels in a 42 yard touchdown against St. Paul's
60. Ronald Green's ridiculous punt return against McDonogh #35
59. Acadiana' Javonte Edmonds picks off Brandon Harris in the 5A title game
58. St. Augustine's Leonard Fournette converts on fourth-and-5
57. Union Parish QB Jamarius Williams' 65 yard TD dash
56. Karr's Gerald Willis III blindsides Bonnabel QB Nate Moss
55. Evangel dupes Riverside with the halfback pass
54. Holy Cross receiver Jerry Cook's catch over a defender
53. Karr's Glenn Irons returns the kickoff 91 yards for a TD
52. St. Augustine's Charles B. Jones 75 catch-and-run TD
51. Destrehan PR Alfred Smith's 70 yard punt return touchdown
50. Vermilion Catholic's Drake Broussard runs back the fumble for a TD
49. Rummel's Henre' Toliver intercepts St. Augustine to clinch state title game berth
48. Mandeville WR Parker Orgeron's beautiful diving catch for a TD
47. Karr's Bryan Anderson picks off Landry-Walker to seal the victory
46. Neville's Kavonte Turpin churns out a 69 yard TD against East Jefferson
45. Devante 'Speedy' Noil splits two defenders for a touchdown
44. Curtis' Hunter Dale scoops up fumble for a touchdown
43. St. Aug's Jermaine Roberts hauls in tipped interception from Darryl Landry
42. Destrehan's Rae Juan Marbley picks off rival Hahnville
41. Parkway's William McKnight runs the kickoff back 93 yards against Acadiana
40. Easton's Tyron Johnson goes 86 yards for the touchdown
39. Holy Cross' Jerry Cook catches the deep pass from James Tabary
38. Calvary Baptist's Shea Patterson tosses a 67 yard TD to Jordan Kennedy
37. Leonard Fournette barrels his way into the end zone against Rummel
36. East Jefferson's Ronald Green makes an amazing sideline catch
35. Anthony Milton nabs game-winning interception against Hahnville
34. Evangel's Mac Meyer corrals the catch for a touchdown
33. Karr's Kerry Taylor jukes his way into the end zone against East Jefferson
32. Mattrell McGraw makes massive hit on Lanard Fournette
31: Parkway's Broderick Jefferson collects the tipped pass for a TD
30: Devante "Speedy" Noil's spinning touchdown pass against Curtis
29: Covington's Colt Clemons returns the interception for a TD
28: Union Parish's Desmond Turner runs in the winning TD in double overtime
27: Evangel stings Riverside Academy on last minute touchdown
26: C.E. Byrd's Kendry Sneed snags a late interception against Holy Cross
25: Rummel CB Kristian Fulton's pick-six against Shaw
24: Easton's Deshawn Capers-Smith scores the winning TD against Belle Chasse
23: Leonard Fournette's 86-yard kickoff return TD against Jesuit
22: Edna Karr runs the trick play to perfection against Easton
21: Rummel's Ivan Phipps scores the go-ahead touchdown on St. Augustine
20: East Jefferson's Isaac Espinoza kicks the Warriors into the state title game
19: Salmen tricks Edna Karr with the lateral pass to Joe Pack
18: St. Aug's Stanley Morgan makes ESPN's "Top 10" with this tipped catch
17: Travonne "Boobie" Hobbs' 103-yard interception return on Halloween night
16: Byrd's Kirkland McCulloch gets a 35-yard interception return during the state title game
15: Curtis' Myles Washington bursts past Evangel with a 65-yard QB scramble
14: Devante "Speedy" Noil's 47-yard dash through the St. Aug defense
13: Destrehan's Rae Juan Marbley strips the defender and scores the TD
12: Leonard Fournette smashes through a Karr defender
11: Anthony Milton's 65-yard interception return against rival Karr
10: Eugene Wells escapes the Karr defense before tossing a TD
09: Rummel's Ivan Phipps scores the title-winning touchdown
08: Karr's Devante "Speedy" Noil sprints 95 yards for the TD
07: Toi Jackson to Leonard Fournette for the 97-yard touchdown
06: Calvary Baptist's Orlando Bradford punishes the Hannan defense
05: Tyron Johnson's 82-yard kickoff return against Belle Chasse
04: John Curtis beats Karr with the fake PAT pass to Hunter Thibodeaux
03: St. Aug's Game winning touchdown and 2-pt conversion against Curtis
02: East Jefferson's Jamal Veazey cements the title with an INT for a TD
01: Leonard Fournette's 79-yard catch-and-run touchdown on Holy Cross
Patrick Greenfield can be reached at email@example.com or 208.891.6441
Follow @PCGreenfield Tweet to @PCGreenfield
Check out more prep highlight videos | INSTAGRAM me @nolaprep


text:
Summary: Two of three suspects accused of using a gun in a strong-arm robbery of a teenager last summer have been convicted and sentenced in Washington County Circuit Court.
The case: On July 15, 2013, a teenager told Forest Grove Police officers he had been assaulted and robbed by three other teenagers while skateboarding in the 1700 block of Elm Street near Rogers Park. The victim said he was pushed, ordered to empty his pockets and had his backpack and skateboard taken. He told police one of the suspects pulled a gun during the robbery. Police arrested two of the three suspects in a few minutes, and later picked up the third suspect. Two of the three were identified as Cody Raymond Wilson, 19, and Anthony Aaron Bernier, 20. The third suspect, who wasn't identified at the time of the arrest, was Eric Matthew Krueger, 15.
Update: On May 7, Bernier pleaded guilty to second-degree robbery. On May 30, Wilson pleaded guilty to first-degree robbery. During his sentencing hearing, Wilson also pleaded guilty to one count of unauthorized use of a vehicle that the state alleged occurred on the same day as the robbery, according to court records. Krueger pleaded guilty last Oct. 17 to two charges and was sentenced to seven years and four months in the custody of Oregon Youth Authority.
Sentences: Bernier was sentenced to three years in prison, followed by three years of post-prison supervision. Bernier was fined $200, ordered to pay $900 in attorney's fees and $560 in restitution to the victim.
Wilson was sentenced to two years in prison for the robbery and six months in jail on the vehicle charge; the sentences will be served concurrently, followed by three years of post-prison supervision. Wilson was assessed fines and fees, according to court records.
-- Roger Gregory


text:
Bethesda releases details and screenshots of the new Skyrim DLC, Dragonborn
Bethesda has announced some of the main details of their upcoming Dragonborn downloadable content for Skyrim.
As the launch trailer has already shown Dragonborn transports players to the Morrowind island of Solstheim in search of a long lost Dragon Priest.
Dragonborn introduces Solstheim native race, the Skaarl as well as new monsters to battle in the form of Ash Spawn, Risklings and more.
It also adds Bonemold and Chitin armours, Stalhrim weaponry and more dark magics from a new Daedric realm.
Travellers to Solstheim will also be able to learn new shouts including the Dragon Aspect which imbues the player with the strength and power of a dragon fortifying physical and magical attributes.
Dragonborn is out on Xbox Live on December the 4th for 1600 MS Points. All the new information and screenshots are available on the official Elder Scrolls website.
Latest News
- Call of Duty: Black Ops III is coming to the PS3 and Xbox 360 after all
- Tomonobu Itagaki's Devil's Third gets a release date
- Adr1ft is coming to PC and consoles at the end of the summer
- EA gives the new Mirror's Edge a name – Mirror's Edge Catalyst
- ZombiU PS4 and Xbox One port reportedly in the works
- Mike Bithell's Volume to be released this August
- Gearbox's new shooter Battleborn gets a pre-E3 trailer
- Steam Controller launches in October, Steam Machines arrive in November
- Gears Of War devs Black Tusk change their name to The Coalition ahead of E3


text:
WILBRAHAM - The Peach Queen Pageant is back.
No Peach Queen Pageant was held last year, the first year the Wilbraham Peach Festival was discontinued.
But when the town began planning for its 250th Anniversary Celebration in 2013, Patricia Diolatevi, longtime chair of the Peach Queen Pageant, decided to bring it back.
Diolatevi said the pageant is back permanently, and will be held every year.
The 25th Peach Queen Pageant will be held Saturday at 1 p.m. in St. Cecilia's Parish Center on Main Street.
There are five contestants, Diolatevi said.
They are Nicole Asselin, Brianna Bateson, Elizabeth Bones, Marissa Halpin and Charlotte Lawson.
The new Peach Queen and her court will be chosen.
The winner will receive a $1,000 scholarship from the Wilbraham Community Association, the first runner up will receive a $500 scholarship and the three other court members will receive $300 scholarships each.
The new Peach Queen will march in the 250th anniversary parade which will be held in June, 2013, Diolatevi said.
Diolatevi said she plans to invite the Peach Queens from the last 25 years to march in the parade which will be held in June, 2013.
The new Peach Queen will be judged on four events, Diolatevi said.
In the first event, the contestants will be asked for their name, address and their future goals.
The contestants are usually high school seniors.
In the second event, the contestants are judged on a pageantry walk.
In the third event the contestants are asked to give a speech which explains why they want to be Peach Queen.
In the fourth event, the contestants are judged on their ability to "think on their feet" and answer questions, Diolatevi said.
A variety of events has been planned for the 250th Anniversary Celebration including a First Night Celebration on New Year's Even, a Quarter Millenium Ball, a parade ending with a picnic and band concert at Fountain Park, a Taste of Wilbraham, a golf tournament, a house tour and a giant town-wide tag sale.
Diolatevi and former Selectman Kevin J. Moriarty are chairing the 250th Anniversary Celebration Committee.
Peach Queen Pageant returns to Wilbraham after 1-year hiatus
Email the author
on June 23, 2011 at 9:15 AM, updated June 23, 2011 at 9:16 AM
WILBRAHAM - The Peach Queen Pageant is back.


text:
The Book of Common Prayer Table of
Or the Second Sunday before Lent
O Lord God, who
seest that we put not our trust in any thing that we do: Mercifully
grant that by thy power we may be defended against all adversity;
through Jesus Christ our Lord. Amen.
2 Corinthians 11.19-31
Ye suffer fools
gladly, seeing ye yourselves are wise. For ye suffer if a man bring
you into bondage, if a man devour you, if a man take of you, if a
man exalt himself, if a man smite you on the face. I speak as
concerning reproach, as though we had been weak: howbeit,
whereinsoever any is bold, (I speak foolishly,) I am bold also. Are
they Hebrews? so am I. Are they Israelites? so am I. Are they the
seed of Abraham? so am I. Are they ministers of Christ? (I speak as
a fool,) I am more: in labours more abundant; in stripes above
measure; in prisons more frequent; in deaths oft. Of the Jews five
times received I forty stripes save one; thrice was I beaten with
rods; once was I stoned; thrice I suffered shipwreck; a night and a
day I have been in the deep; in journeyings often; in perils of
waters; in perils of robbers; in perils by mine own countrymen; in
perils by the heathen; in perils in the city; in perils in the
wilderness; in perils in the sea; in perils among false brethren;
in weariness and painfulness; in watchings often; in hunger and
thirst; in fastings often; in cold and nakedness; besides those
things that are without, that which cometh upon me daily, the care
of all the churches. Who is weak, and I am not weak? who is
offended, and I burn not? If I must needs glory, I will glory of
the things which concern mine infirmities. The God and Father of
our Lord Jesus Christ, which is blessed for evermore, knoweth that
I lie not.
St. Luke 8.4-15
When much people
were gathered together, and were come to him out of every city, he
spake by a parable: A sower went out to sow his seed; and as he
sowed, some fell by the way-side, and it was trodden down, and the
fowls of the air devoured it. And some fell upon a rock, and as
soon as it was sprung up, it withered away, because it lacked
moisture. And some fell among thorns, and the thorns sprang up with
it, and choked it. And other fell on good ground, and sprang up,
and bare fruit an hundred-fold. And when he had said these things,
he cried, He that hath ears to hear, let him hear. And his
disciples asked him, saying, What might this parable be? And he
said, Unto you it is given to know the mysteries of the kingdom of
God: but to others in parables; that seeing they might not see, and
hearing they might not understand. Now the parable is this: The
seed is the word of God. Those by the way-side are they that hear;
then cometh the devil, and taketh away the word out of their
hearts, lest they should believe, and be saved. They on the rock
are they which, when they hear, receive the word with joy; and
these have no root, which for a while believe, and in time of
temptation fall away. And that which fell among thorns are they
which, when they have heard, go forth, and are choked with cares,
and riches, and pleasures of this life, and bring no fruit to
perfection. But that on the good ground are they which in an honest
and good heart, having heard the word, keep it, and bring forth
fruit with patience.
Text from The Book of Common Prayer, the
rights in which are vested in the Crown,
is reproduced by permission of the Crown's Patentee, Cambridge
University Press.
Your Church Wedding
Whether you're just dreaming of a church wedding, or well into the planning already, your church wants to help and support you.
A comprehensive resource for anyone involved in the running of a church, with a wide range of practical advice and tips. Includes shrinking the footprint.
Call Waiting
Encouraging gifted and committed young men and women, from all backgrounds, to consider whether God is calling them into ordained ministry.
Going for Growth
A spiritual challenge for every child and young person to have a life-enhancing encounter with the Christian faith.
Worship Workshop
WorshipWorkshop offers Church schools a way of creating engaging collective worship.
Crockford's Clerical Directory
Crockford's Clerical Directory, contains biographies of over 27,000 Anglican clergy, details of English, Welsh and Irish benefices and churches and more
Church of England in WW1
Resources, stories and events to commemorate the anniversary of the First World War
Church Legacy
Church Legacy' provides information for individuals, solicitors and parishes on how gifts in wills can make a lasting difference to your local church
Church House Publishing
The Archbishops' Council publishes a range of liturgy, reference and other resources under the CHP imprint.
Parish Resources
We support you in your stewardship, providing online guidance & resources on; finance, gift aid, preaching, fundraising & administration.
Communications Training
High quality media, presentation and social media training for the CofE and related charities. Find out more about our current courses.
Lambeth Palace Library
The historic library of the Archbishops of Canterbury.
Parish Buying
Offering national contracts and buying tips to help the Church buy and save together.
Pilgrim Course
A course for the Christian Journey - where people can explore the Christian faith together and see how it can be lived out each day.
Resourcing Christian Community Action
Information on best practice in providing Christian care in local communities
Church Growth Research and Development
Church of England's work on church growth research and development that aims to help the Church allocate its resources effectively to facilitate its mission and growth
Presence and Engagement
The Church of England's national programme equipping Christians for mission and ministry in the wonderful diversity of our multi faith society
To Your Credit
Information and resources to help churches and individuals act for a fairer financial system, including support for credit unions.


text:
Sandusky Investigation: A Visual Timeline
Tuesday, June 24, 2014 4:52 AM
DEC. 7-8, 2011: Jerry Sandusky is escorted from a car to his College Township home after spending the night in the Centre County jail. Sandusky was charged with additional counts of sexual abuse of minors and released after a night in prison.
Related articles
- What Kane report reveals about Corbett's Sandusky investigation June 24, 2014, 5:45 AM
- Penn State board acts to settle other outstanding Jerry Sandusky claims April 09, 2015, 11:26 AM


text:
Apollo 18 fails to stay with you because, like the cratered satellite on which it's set, it has no atmosphere.
Keith Staskiewicz - Entertainment Weekly
Accomplishes something the world wasn't really crying out for: it recreates the tedium of watching the later Apollo missions.
Mike Hale - New York Times
For most horror fans it will be kind of a snooze.
Joel Brown - Boston Globe
Reconfirms that most entries in the "found-footage" horror subgenre should remain lost.
Nick Schager - Village Voice
Has no thrills, no chills, no scares and contains a villain, or several of them, actually, that will turn you to stone -- from boredom.
Joe Neumaier - New York Daily News
Despite stretches of skillfully sustained suspense, Apollo 18 ultimately comes across as little more than a modestly clever stunt.
Joe Leydon - Variety
Boredom sets in long before the last muted shriek. And who cares about the astros? We never get to know them anyway.
Peter Howell - Toronto Star
The source of the creepy events, when it's finally revealed, is profoundly dull, like a forgettable episode of The X-Files or Fringe.
Eric D. Snider - Film.com
This space-set, "found footage" horror flick never lifts off.
Frank Scheck - Hollywood Reporter
The film takes a startlingly long time to rev up, and even at less than 90 minutes feels thin and at moments like it is playing for time.
Mark Olsen - Los Angeles Times
A potentially cool "found footage" flick that is desperately in need of a lot more brains ... or a lot more silliness.
Scott Weinberg
The movie builds up to a mystery that it never does much to resolve, with its big set piece reveal consisting mostly of a couple of rocks moving.
Will Leitch - Deadspin
The 'found footage' horror movie Apollo 18 recycles the premise of The Blair Witch Project on the moon and still manages a few good scares.
Sean Kernan - We Got This Covered
"The cheap frights don't deliver, the performers bring no pathos and the gimmick behind "Apollo 18″ flat out does not work."
Roger Moore
It's impossible to recommend Apollo 18 to anyone but the most staunch found-footage fans. The film fails every requirement of a tense and enjoyable time at the theater.
Ben Kendrick - ScreenRant
"Apollo 18" is another dud in a genre that should have stopped before it got out of hand.
Jeff Beck - Examiner.com
Feels like nothing more than an attempt to cash in on a trend, and it's a textbook example of how not to do that.
William Bibbiani - CraveOnline
An astonishingly incompetent and interminable piece of work...
David Nusair - Reel Film Reviews
Apollo 18 is a mercilessly dull movie that just doesn't make much sense. It's light on thrills, and the found-footage gimmick works against the tension.
R. L. Shaffer - IGN DVD
The REAL reason why we never built bases on the moon by 1999 . . .
James O'Ehley - Sci-Fi Movie Page
if you can push past the suspension of disbelief, it's a pretty eerie ride
Kevin Carr - 7M Pictures
Jeffrey M. Anderson - Combustible Celluloid
Movies with 'found footage' have become quite popular since the advent of 'The Blair Witch Project.' The authentic feel adds to the horror element as these movies unfold. (One great example is 'The Last Exorcism,' a sadly under-seen movie.)
Linda Cook - KWQC-TV (Iowa)
An intriguing premise that never quite reaches liftoff.
Bruce Bennett - Spectrum (St. George, Utah)
There are a couple of moments here that are as marrow-freezing as anything in Blair Witch or Paranormal Activity.
Calvin Baxter - SFX Magazine
A simple sci-fi horror with just enough scares to keep you interested.
Kim Newman - Empire Magazine
I can only assume this movie is for people who know virtually nothing about the space program.
Jim Slotek - Jam! Movies
Apollo 18 is an intriguing, if never enthralling, fusion of period space-flight procedural, conspiracy theory, and monster movie.
Kimberley Jones - Austin Chronicle
[It] really delivers a fun, tense experience.
Grae Drake - Movies.com
Apollo 18 has some nice ideas, some impressive effects work and a decent finale, but the first half is extremely dull and it's ultimately let down by frustrating sound design work, severe pacing problems and some incoherent editing.
Matthew Turner - ViewLondon
Jordan Riefe
Even as horror films go, this one is terrible indeed, lacking in the one element it would need to succeed on the most basic of terms: scares.
Brett Michel - Boston Herald
[A] zero-intensity space bore.
Dave White - Movies.com
Will bring back a lot memories for anyone who lived through the space race.
Graham Young - Birmingham Post
Apollo 18 is presented with winning earnestness.
D.K. Holm - Vancouver Voice
For the most part, alas, this only goes to show that in space, no one can hear you yawn.
Neil Smith - Total Film
What we have here is Conspiracy Theory 101 all Blair-Witched-up.
Ken Hanke - Mountain Xpress (Asheville, NC)
Dull, but diverting if you focus on the images' eerie beauty.
Peter Keough - Boston Phoenix
So utterly broken at a conceptual level that a truly good film was completely out of the question.
Tim Brayton - Antagony & Ecstasy
The documentary look and feel of the movie is impressive until it is overcome by the inaneness of the plot
Jackie K. Cooper - jackiekcooper.com
Apollo 18 always seems like an attempt at a scary movie edited by scary movie-makers, rather than an actual document from the NASA vaults.
Jeffrey M. Anderson - Common Sense Media
Watching people land on the moon isn't all that interesting or photogenic, especially when we know it's pretend.
Chuck Bowen - Slant Magazine
It's 80 minutes of dead air.
David Edelstein
Director Gonzalo Lopez-Gallego exploits every possible tool within the confines of the genre and manages to create moments of true tension and genuine scares.
Tom Brennan - Dark Horizons
Every great horror movement eventually has to make it into space. Hellraiser went there, Jason went there, even Leprechaun went there. Now the found footage genre goes into space. Thank God too.
Fred Topel - CraveOnline
It's a tedious faux documentary, filled with schlocky sound-effects and jarring cuts, utilizing TV actors masquerading as astronauts.
Susan Granger - SSG Syndicate
It's not awful - you just wish they'd made a proper movie out of it.
Tim Robey - Daily Telegraph
Meticulous in its "found" visual details, minorly smart in concept, painfully slow to actually watch and so ridiculous in its big reveal that it almost has to be seen to be believed.
Alison Willmore - Movieline
In space, no one can hear you scream ... but you'll hear plenty of giggling in the final moments of Apollo 18
Christian Toto - What Would Toto Watch?
The film is so difficult to watch, and it's such a chore to discern a sense of place and perspective, that it sits onscreen like a big, dead weight.
Robert Levin - Film School Rejects
It goes to such painstaking lengths for stylistic plausibility that the end product is actually quite dull, squandering its novel 'Paranormal Activity in space' concept as a result.
Shaun Munro - What Culture
A drab and shoddy experimental film.
Dennis Schwartz - Ozus' World Movie Reviews
The stream of jerky, fuzzy, static-riddled and otherwise distressed visuals...[is] a trick that's gone stale, and 'Apollo 18' doesn't freshen it up
Frank Swietek - One Guy's Opinion
It is likely that the only screams heard from auditoriums showing "Apollo 18" will be of the "I paid $10 for this crap!?" variety
Peter Sobczynski - eFilmCritic.com
One giant leap for Big Brother ... scruffy, seat-of-the-pants filmmaking. The kind of thing you don't see much any more ... could do for Lopez-Gallego what 'Dark Star' did for John Carpenter.
Glenn Lovell - CinemaDope
The basics are there; it just can't run with them.
Rob Vaux - Mania.com
Derivative, dumb, suspenseless and worst of all boring, "Apollo 18" fulfills no expectations except those of the low quality of films released over Labor Day weekend
Todd Gilchrist - The Playlist
...let's have an end to this misbegotten subgenre of 'found footage' movies.
Daniel M. Kimmel - Sci-Fi Movie Page
Apollo 18 is a surprisingly intense, innovative and well-directed flick that made me jump out of my seat more than a few times!
Kevin McCarthy - BDK Reviews
Make no mistake, Apollo 18 is a *terrible* movie.
Keith Phipps - AV Club
[N]ot scary. It's not intense. It's not surprising. It's supposed to be all these things and fails completely... It doesn't even work on the limited scale of its own merits.
MaryAnn Johanson - Flick Filosopher
nauseatingly bad
Bill Gibron - Filmcritic.com
Less concerned with depth and more about the strict skillfulness of capturing an increasingly queasy tone and mood. This is where it works.
Dustin Putman
In space no one can hear you yawn.
Devin Faraci
'Apollo 18' stands as one of the worst examples yet of a very, very limited subgenre. It doesn't matter if this footage was found or manufactured, because the only good thing that could be done with it involves a match and an accelerant.
Drew McWeeny - HitFix
NASA nuts and conspiracy freaks might find something to embrace here, but the average viewer is likely to be bored stiff by this overlong, underwhelming chiller.
Brian Orndorf - BrianOrndorf.com
No final das contas, ate mesmo os dois personagens principais se tornam apenas caricaturas de homens descontrolados e em perigo, abandonando qualquer tentativa de tridimensionalidade.
Pablo Villaca - Cinema em Cena
If anything, Apollo 18 lacks creative intensity. It's a very lazy attempt at bringing terror to the moon. In fact, it's not even scary, unless of course you consider a sleeping dude opening his eyes and yelling into the camera "frightening"
Brad Miska - Bloody Disgusting
Suffice it to say that the suspense works, and the obligatory sequel hook genuinely intrigues us with its possibilities rather than merely threatening a retread.
Luke Y. Thompson - E! Online
Audiences hoping for something in the vein of Paranormal Activity won't be disappointed, although the film can be faulted for sticking too close to a familiar formula.
Tim Grierson - Screen International
Even with effective atmosphere, a couple of jump scares and a spooky premise, Apollo 18 simply falls apart in the end.
JimmyO - JoBlo's Movie Emporium
More than just a lunar 'Paranormal Activity.'
Thomas Leupp - Hollywood.com