 Yes, my name's Sreeda Dhanapallan. I'm the technical manager at One Laptop Per Child Australia. So what I'm here to talk about is, firstly, an overview of the One Laptop Per Child program. I won't dwell too much on that because it's been done to death before. But I want to focus on what's been going on in Australia over the past year, especially, well, even six months. There's just been so much stuff that's been happening and we've been going through constant change. It's been amazing. So a little bit about old PC to start with. It was announced in 2005. The idea was to use 21st century technology to try and rectify the problems that were seen in the developing world with education. So large class sizes, lack of resources, all of that stuff. Now, clearly it's not a silver ball. It never was intended to be. What it definitely isn't is a laptop program or a technology program. It just happens to make very clever use of technology. But it really does that as a part of a really large, sustainable, long-term project with some pretty good principles underpinning it, I think. So just to go through, the five core principles that underpin everything that old PC does. Now, I'm speaking for the global project for the moment. I'll get into Australia in a second. But the five key principles are, firstly, child ownership. We want the children to feel like their exo is theirs. So I haven't really said much about the exo, but that's it there. I won't dwell on it. Everyone's seen one. If not, grab me later. There's plenty of information online. So we want the kids to feel like they own theirs. It's a personal learning device. And that should hopefully give them the freedom and opportunity to learn, however, and wherever they like, whether it be in the classroom or after hours at home, kids should just be able to sit under a tree in the middle of nowhere and have their exos just talk with each other and have them be able to collaborate, share information, that sort of thing. So it's not just a glorified e-book reader. It's a lot more than that. If you took a, imagine if you could digitize thousands of books and stick it on a machine. That's great. I mean, you've got an e-book reader there. Pat yourself on the back. But what if you were to make that more interactive? You let kids actually engage in exercises and have immediate feedback on their device. And while you're at it, let's make these devices talk with each other. Let's make sure that the kids can actually learn from one another so that the teacher is not the only font of knowledge around here. The kids learn as well. We've seen in deployments some places where the kids, well, actually, this is quite often, kids pick this up faster than the teachers. And the teachers, yes, very important. And I'll get into that in a moment. The teacher engagement is essential. But we also want the kids to be able to learn on their own without the teacher as well. So if I was to continue, so emo, meaning that demonstrations often go wrong. Now, if I was to, let's see, here's my pointer. I was to switch back. Now I'm keeping open office running in the background. So this is going to be a bit slow. So I'm using OOO for kids, which is basically a version of open office that has been altered to fit into the native sugar environment. Now, I'll show you what that environment is. Where it comes from is some guys at MIT who had been doing research in education for decades, realized that one of the fundamental problems of introducing technology into schools was that we're really pushing a office-centric paradigm onto kids. We're giving them these metaphors of desktops and files and folders. And through that, we introduced problems like, oh, I saved this document, and I stuck in some folder somewhere, and I can't remember where the heck it is. I mean, that happens to everyone. Why should we inflict that upon children? So there are other ways to deal with that. And what they came up with was what's known in UI circles as a zoomable interface. So if I was to start at the top level, the highest level of zoom, this here, hopefully my laser pointer works, no. I'm pointing it the wrong way. Uncle, emo, there you go. So this is called the neighborhood view. I like to call it the playground view. You've got the child in the center, and then you've got these circles or other wireless points around them. If there are other children on the network with their XOs, they will show up as other little kids like that. And then you can hover your mouse over them, and you get options like, I want this kid to be my friend so that they show up whenever they're online. And then you can also share activities, do things collaboratively, that sort of thing. So the friends view or the team view is that one there. Now, my little guy is quite lonely. He's got no friends. That's unfortunate, but in a classroom situation, you have a lot more. Now, zoom into the next level. This is where the child spends a lot of their time. This is known as the me view. That's what I like to call it. That's me there. I've given myself some nice Australia Day colors. And around this are your favorites. They're the activities or the programs. We call the programs activities because we're emphasizing the fact that children are doing something, emphasizing the fact that they're learning together and that sort of thing. It's not a program that you run which sounds quite impersonal. So the child's favorite activities are around in this circle. This is actually the, apart from OO4Kids, which I just added for the purposes of this presentation, this is the default view you see on an EXO that's being deployed in Australia. There are a lot more than that. If I was to click on the list view over there, there's a whole lot more that you can scroll through and you can type to search and stuff like that. But what's interesting, getting back to the problem I mentioned before about losing track of files and so on. Now, imagine I'm a child. I made a drawing two weeks ago. How do I find it? I don't want to have to dig through files and folders. I want to be able to search for it. I want to be able to filter for it. And go by time as well. Now, slide apologies. The graphics are a bit slow because I'm using a USB to VGA adapter. I'll get into that in a moment. That's something that I'm pretty excited about. We didn't have support for that only a week ago, really. But let me highlight one activity that we have developed in Australia. One thing we really want to do is improve the musical capabilities of the XO. There's some pretty impressive stuff in there. The speakers aren't fantastic. But if you were to plug in some external headphones and microphones, that sort of thing. Actually, this is a mistake I made. Is it possible to get external sound or anything on this? If not, I'll put the volume up and hope that people can hear. So while that's going, I'll just explain this. Now, this isn't going to look fantastic on the resolution because when I'm using this adapter, it alters the resolution. Some activities aren't quite compatible. But basically, this activity is called Music Painter. It's something we developed because we really wanted to combine the ideas of visual art and audio art. Kids, especially in remote Australia, culturally, they're really good at art, generally. That's the kind of thing they gravitate towards. So providing those sorts of activities is of great assistance. OK. Yeah, I need a standard audio jack. Is that possible? OK. Well, let's move on from that. I'll get back to that later. Basically, what I did was that I just drew something and you can actually play that back as music. It gets synthesized on the fly. It's actually some really clever stuff happening behind the scenes. It's not just playing pre-recorded audio samples. It's actually the same kind of technology that you see on high-end karaoke machines. Kind of hardware that you would have paid $20,000 for 10 years ago is actually available on the XO Now. There's the exact same code as well. OK. Yeah, that's a good idea. Do you want to try this one? See if it works. OK. Good point. OK, let me switch back to Musicator. OK, and I remove the frame. That's the other thing. The frame is basically your taskbar. So you've got right at the top your views, which I pointed out before, your running applications, which are there, status indicators like networking and volume battery, friends you're connected with basically show down there as other little XO people. Now if I was to remove that and then give this a play, now hopefully this works. Oh, sorry. Is that working? No, it's not. Can people hear that? OK, cool. So it sounds quite simplistic. And it's not supposed to be high and complicated, but there is quite a bit of smarts behind there. The code's pretty cool. Now switching back. OK. So moving on, old PC Australia. Who are we? Firstly, we're a separate entity from old PC. We subscribe to their ideals. We want to achieve what they're trying to achieve, but we want to focus on Australia. Sounds a bit weird. We're a developed country. Why on earth would we need a one-laptop or child program? Why would we need a program that is designed for children in the developing world? Isn't that insulting? What's the point? Well, you go out to our regional remote and very remote Australia, which are the areas that we go to, those official Australian Bureau of Statistics designations. And unfortunately, you see children that have been not so well represented by the capitalist model. Not so well represented by the money that's in Australia. And they're in very difficult circumstances. When I say difficult, I mean there are harsh environmental conditions and they're vast distances to cover. Very thinly populated, like sparsely populated, so you don't have major regional centers with which you can build economies of scale and that sort of thing. So in that sense, we have similar environments to what you see in the developing world. So old PC Australia, the general idea started around 2006. It was officially turned into an organization in 2008. We have deductible gift recipient status, which means that we're recognized by the government as being a valid charity. And if you give us money, we're sort of tax deductible and all of that stuff. That was incidentally announced by Kevin Rudd, who was at the time prime minister. And he was speaking at our first anniversary gala dinner, which was in May last year. I wish I had a photo of that. I'm keeping my slides simple because I'm not sure how well this experimental version of open office for sugar is going to hold up. Just to move on, that's our official mission statement. That's what we're trying to achieve. Now, it's a very long sentence. And well, that's what mission statements often are. You're trying to squeeze as much into 40 words as you can. So let me break it down. So our mission is to enhance learning opportunities. So through the EXO, we're trying to improve educational opportunities. We're not teaching computing or anything like that. We're using computers to teach. There's a subtle difference there, but it's very, very important. We're not involved in vendor training or anything. The computer is like another pen and paper or another textbook. So continuing on, 400,000 children. That's a lot of children. And that really took me back when I saw that. There are 400,000 children in these areas of Australia that are officially categorized as outer regional remote and very remote. Yes? Please define said term regional and remote. Those are official designations by the Australian Bureau of Statistics. I don't know much more than that. They are official. That's all I could say. Take it up with the ABS, otherwise. Yes? I believe when they worked it out as well, they kind of did it on income, economic scale, demographics. So it was like how they actually, it's remote and isolated. But it's also these kids are what's considered in living below the poverty line kind of styles compared to the Australian, what we live in in the city. Correct. And that was the next point I was going to get to. Because yes, we work on remoteness. We're not discriminating based on race or anything. Sometimes we get described as a program for indigenous kids. We're not. We go after remoteness. But what we also go after is socioeconomic indicators. And the ABS keeps statistics on that. There's an average level, which is 1,000. We focus on the communities that are below 900. Yes? Do you know approximately how many of these kids are aboriginal and how many are not? Not off the top of my head, no. I'm sure it's easy to find out, though. And let's see. Age four to 15. Now four is pretty much when you start kindergarten. And 15 is around year eight, year nine. What we don't do is overlap with the federal government program, which you may have heard of, providing laptops to schools in years nine and above. So they get to year nine, and they get their federal government laptop. And if they got an XO in the previous year, they may keep it. But they won't receive two laptops in one year. So again, remote Australia connected XO laptop. Now connected is an important word. And I probably should have bolded it. We want the XOs to firstly be able to talk with each other. Now they do that very nicely. They're designed to, basically, kids just turn on their XOs and they automatically see each other by creating an ad hoc network. The previous model, XO ones, had a mesh network. But that's all mechanics underneath. The child doesn't care. They can just talk with each other. Nowadays it's ad hoc using network manager and standard Linux type technologies. Now the next thing I need to focus on is sustainable. Very, very, very important. We want these communities to have a sense of ownership over the program. It's not a traditional client-vendor relationship. We don't want them to have to come to us for everything. In fact, that would be a failure of our mission, I think. We really want to buy this 2014 date, have these communities feel like they can manage most of the project on their own. Now that also involves the government department of education and so on. This is a long-term educational project. You'll really only see full results once these kids are grown up and they're able to pick up jobs and that sort of thing. We recognize that. And if they're fully dependent on us, then over that entire period, then it's not going to be nearly successful. Now 2014, we wanted to set an ambitious target. That's basically why 2014 is there. And there is a precedent. Uruguay has full saturation. Every single child in the country as part of official government directives has an XO integrated with their school learning and all of that stuff. And that was done in, I think, about three or four years. So that's 400,000 kids. Well, we have 400,000 kids as well. The circumstances are a bit different. We have wider areas to cover. But yeah, we reckon we can do it. Is that going to work? OK, so some of the challenges in Australian schools. Australian schools are interesting because, well, remote Australian schools especially are interesting in that. This is a developed country overall anyway. And so a lot of these schools have computer networks, satellite internet, electronic whiteboards. Some have electricity, a lot don't as well. Probably generators in many cases. But it means that some of the things that the XO is designed for don't quite match up. So one example is that there's a service solution I'll get into in a moment called the XS. And that was designed for a place where there's no network whatsoever. It sets up its own DHCP server. It basically maintains its own network on its own. And you plug that into a standard network and it's a complete pain in the butt to manage. And it actually conflicts with existing networking resources. So we got that. We created a simplified version. I'll go into that in more depth. But there are also vast differences in climate. You go up to the top end, Northern Territory or Queensland. It's humid. It's hot, stinking hot. You go down to the Alice Springs region and it's desert. It gets cold at night, hot during the day. You need something that's really rugged that can survive that kind of environment. And the state of lifetime of XO is five years. That's an eternity in technology terms. So to have a device that actually lives through all of that is, I think, speaking for myself, it's quite extraordinary. Other problems are supplying power to these things. Even in metro schools, most buildings are quite old and they weren't designed for every child to have an electronic device that needs to be plugged into a wall. There aren't enough power points. Even if there were, you would very quickly max out the power supply. I've heard of schools asking their kids to take not XOs, but just standard laptops that they're given to kids, asking their kids to take their laptops home to charge them. And that's the only reason. There's no educational driver there. They're not thinking about these kids learning at home. They're like, well, we don't have enough power points here. Take your laptops home and charge them so you can use them the next day. And if your battery runs out during the day, you're probably in trouble. But the XOs have quite a long battery life, not just from charge to flat, but also in terms of lifespan. They can take about 2,000 charged discharge cycles. This is about four times better than a standard lithium ion battery. Other things are environmental concerns. It's the battery doesn't contain mercury or cadmium or lithium or any of that. Sorry, it does contain lithium, but it is a much safer battery than other kinds. There is no mercury in the XO either. Other problems are remoteness. It's difficult to service a school that's out in the middle of nowhere. How do you get a technician out? And that's not the question you really should be asking. Unfortunately, that's the question that most people do ask. The question you should be asking is how do you enable the locals to manage things for themselves? And we really want the schools and the communities, especially the children, to manage things. The XOs can actually be pulled apart and repaired by kids, which is pretty cool. You wouldn't see that happening with a device from a major vendor. You would probably void your warranty if you were to do something like that, and then they wouldn't help you ever again. Another problem is teacher turnover. Teachers in these remote schools often don't last very long, so we could go through all the trouble of enabling a teacher to bring them up, all that stuff, and then they pick up and leave. That's, of course, their choice, but it means that the community's kind of left behind, right, going, oh, what do we do next with all these devices? But if we were to enable the children and the teaching assistants and people who are there long term, and actually have a vested interest in the success of the program, then it's going to be a lot more successful. We do a lot of work to help that out. Let's see, what else? Moving on, I think my presenter has died. And I just went, whoops. OK, so the XO, I've already gone into that to some extent. But other things are, it has a wonderful screen technology. You can actually read the screen in direct sunlight. If you've ever tried getting a laptop or your touchscreen phone and trying to read that in direct sunlight, you can't. Now, when we're trying to promote an idea of education where kids can learn anywhere, they should be able to go outside. The thing has a camera. They should be able to take pictures of flowers and animals and that sort of thing. But if they can't see what's going on the screen, then there's not much point to it. And incidentally, when you're using it in direct sunlight, it basically works in a very similar way to an e-ink display. You get incredibly high resolutions, very crisp text. It is monochrome, but you can have motion pictures on it. You can't do that with standard e-ink technologies. It'll probably take a couple of seconds for each page to turn on those things. Now, we've been deploying these new XO 1.5 models, which are these things, since May last year. We were the first country in the world to start deploying them, which made things interesting and meant we hit some snags and some bugs and so on. But we got past that. There's a lot of fun doing that. Now, just to summarize, it's the same industrial design as the XO 1s. They look almost identical. There's just a few subtle differences on the shell to indicate that it's a 1.5. Internally, it's a lot faster. It's got four times the RAM. It's got a gigabyte. It's got four times the storage. It's got four gigabytes. So it's much more useful for kids. You're not waiting so long for things to load and so on. Now, hardware is only as good as its software. So what we've done is that we've taken the standard old PC operating system, and we've created our own variant, which I like to call the XO AU. And we've got a pretty cool development process there. Pretty much as soon as old PC come out with something, we can come out with our own variant within a couple of hours. What we have there is a lot of localized content and our own activities that we've chosen. We've got some system updates on there. We've fixed some bugs. Now, this one's not going to make me popular, but I under a lot of pressure had to include the Adobe Flash Player, my keyboard started working again and going nuts. I had a lot of pressure to do that, because Flash is very widely used in Australian schools. And you just can't get away from it. There is included Gnash Player, but unfortunately, that's just not compatible enough to be of real use. So what's next? Mini Server, I'll quickly go into that. Basically, we've developed a way of getting the XO and turning that to an update server that other XOs can be imaged from, or not imaged, rather upgraded from in a lossless manner. Old PC had this amazing technology called Nam Blaster, which is an XO can blast an image wirelessly to as many other XOs as you need. It's a very quick and efficient way to image many XOs at once. But unfortunately, that's blasting a fresh image, so it wipes what's on the XOs. If the kids that work on their XOs, they need to make sure that they're saved first, otherwise they get lost. Our solution was a mini server, which is something quite similar, but it doesn't upgrade instead. So that's an Australian development there. XS, that's a server that I referred to before. That is designed as a drop-in server to go to a place where there's no network whatsoever. You plonk it in, give it a wireless access point. It marshals communications between the XOs, makes the network a lot more efficient. You don't need a server for XOs to talk with each other, but this just makes it a lot more efficient. Brings other benefits like classroom segregation. If you've got a school of 200 kids, then you can go. A teacher can go into the web interface, which is based on Moodle, and go, OK, this child can only see the other children in his or her class, and that way it's a lot more manageable. And you can also keep track of the XOs. You can back them up to other things like that. Yes? Is the XS a software you can drop on any hardware platform, or is it an actual hardware product? Yes. So just to emphasize, the XS is software. It's a distribution. It's Fedora-based. At the moment, the official XS is based on Fedora 9. What we have done is come up with an XSAU. Fedora 9 is getting a bit old. And there was a lot of stuff in the official XS that we really didn't want. And that just complicated the setup. We wanted to make it much more simple so that it's basically, rather than a fork of Fedora, it's just Fedora with extra packages. We wanted the networking to just make sense to a standard Linux this had been. We wanted it to be more maintainable. We wanted it to be easily installable from a USB stick. We wanted the installations to be able to be automated via Kickstart. If you're familiar with that, it's basically Red Hat's technology to automate installations. And so we came up with the XSAU. Now, our official version at the moment is based on the presence XS, which is Fedora 9-based. But we have one that I want to release very soon as an official version that's based on Fedora 11. And the reason why we're going with Fedora 11 is that firstly, it's the same OS-based as what's on the XOs. And the other reason is that you can actually upgrade from Fedora 9 to Fedora 11. But the Red Hat or Fedora Anaconda installer doesn't go more than two versions in advance. So that provides us with some compatibility with the XS is already out there. What it also does is solve the problem of existing networks. These schools already have networks. We don't want to put another device on there that tries to duplicate existing network resources. It's just going to wreak havoc. So we've greatly simplified the configuration. So it's just a drop-in server. It just plays along like a standard polite network citizen. And that's made a big difference. It's made the XS viable in Australian schools, but not just in Australian schools, in any school that has an existing network. So that means that the server solution now is viable in even developed countries. XOP, this is something I'm really excited about. Because power is a problem in these environments. If every child has a laptop, how on earth are you going to charge them all? And a lot of these places just don't have reliable power. They might be on generators or something like that. They may have power that's switched on only at night. And so the XOP provides a very efficient way of doing it. Now, I was going to bring a sample of that. Unfortunately, I don't have it on me at the moment. But essentially what it is, it's a plastic rack that is assembled, the pieces snapped together like Lego. Each rack holds five XOs. Now, the rack portion was actually designed by OOPC a while ago. It never made it to production. One reason why it didn't was that they didn't really have a suitable charging portion to it. It was just the plastic rack. We came up with the charging brick. And what that does is it slots into the rack quite neatly, and the brick's daisy chain onto each other, meaning that off one PowerPoint, you can just keep daisy chaining these racks on and on and charge heaps of XOs. And we've calculated based on the power draw that on a 230 watt power supply, which is what you get in Australia, you can charge up to 75 XOs off one PowerPoint. False. You are correct. Go into a case study. Now, my co-speaker has far more experience in this, but I'm just going to talk about one of my experiences in a community, because I found it quite eye-opening. I went up to a community in East Arnhem land, known as the Darlan Boy in the Euricolor homelands. And this place, well, firstly it's a fantastic community. It was a school of about 25-odd kids. The whole community would have maybe been 50 people, something like that. And the school was basically a shed. And they had satellite internet. They had two PCs that had been given to them. But guess what? No electricity. The only electricity for the school during the day was a tiny generator. It was about yay big. And it wasn't really sufficient for the technology that was sitting there in the school. There was a big generator that was turned on only at night, specifically to pump water up into the water towels from the ground. That was their water supply. So what we had was we installed a NXOP charging rack. We had an XO for every single child. And that small school generator was able to cope with all that. And also charge the satellite modem and the wireless access point. We're just using a Lynx's WRT54GL flash with DDWRT. And that did the trick in this case. And so we had all these kids up online. I was showing them Google Maps. I thought this was really cool. I had Google Maps. And I was going, hey, well, this is where you are. Let's zoom out a bit. Oh, look, there's all the straighter. And I'm down here in Sydney. So I think it's a really good way to open children up to the world and conversely open the world up to the children as well. Now, the sugar graphical environment, which is what I demonstrated before, that works on normal PCs. It's just another gooey for Lynx. You can install it on most major distributions as packages. You just go to your login manager and you just choose sugar just as you would at home, or KDE, or whatever. So if you want to give that a shot, you certainly can. It's normally an apt-get install or a yum install. So to develop and test this stuff, so my primary goal here is to try and encourage you guys to get involved in our development and testing. And that's what we really need. So there's sugar, which I just described. There's also sugar on a stick, which is a bootable USB version of sugar. And that's being promoted by Sugar Labs, which is the parent organization of sugar as an educational tool. So kids can just have their own version of sugar on a stick and take that around. They can use it at school, save their work to the stick, go back home, load it up on their computer, keep using it. That's sort of jazz. The underlying technologies behind sugar are pretty easy to get into. I mean, it's Python based mostly. Underline libraries are the GTK and GNOME libraries. The browse activity is based on Firefox. The write activity is essentially Abbey Word. You can even write applications in Flash, which are interpreted using the free software in Ash Player. And that doesn't run in the browser. It actually runs as an activity on its own. So if you're a Flash developer, then you can still code some pretty good stuff for sugar. Now, like I mentioned before, the OS on the XO is Fedora. So you can actually install Fedora packages. You can go to GNOME. And I'll show that in a moment. There's GNOME on there. And you can just load the package update, or you can just do YAML, or what have you. In fact, I'll give that, see how we're going for time. We're kind of running out of time, so I won't. But just take my word from, pardon? OK. Well, OK, so let's move on. So it would be fantastic if you guys could get involved in our development. I've got a bof tomorrow. Details up there. Lunchtime. And yeah, that's the main website to go to, if you really want to find out more about us from a developmental perspective. And yeah, that's it from me. I'm going to hand it over to my co-presenter. His name's Ian Cunningham. He's been involved very heavily on the technical deployment side of one laptop per child in the Northern Territory. He works for the Department of Education there, so he can provide a really good perspective from the educators side of things. So you don't have to listen to my propaganda. You can listen to someone who's been there on the ground. Good afternoon, everyone. This is going to be fast. Excuse me if I read from the notes, because it's just going to be a core dump. The Northern Territory covers an area of 1.35 million square kilometers equal to the combined areas of France, Spain, and Italy. All our schools connected to a wide area network with Windows 2008 servers at each school. The schools connect to the network via either a remote landline or two-way satellite links. Some remote schools have homeland centers. It's an example of Ramon Gening, which is up the top there. To get in there, you've got to fly in. And we use two-way satellite links there. Anyway, that's the existing sort of school infrastructure that we've faced with to try and incorporate these XO laptops and the XS server. So initially, the XS server just wasn't compatible with our system. If you threw that in there, there'd be DHCP requests going from, or IP addresses from two servers and fiber optic links between buildings. You can't have two Hs in any way. You know what I'm talking about. So to this end, the script was written for the XS server. And the cut-along story short, the XS server now with our model just has one interface that can be plugged into any school network. And you've automatically got a Moodle server there for your sort of preconfigured, if you like. In 2009, we ran a feasibility study with sixth grade two classes in Alice Springs. The main aim was to see if we could actually integrate these XOs into our existing network. And we found that we could. The original sugar interface was a bit clunky. And connection to the wireless access points was not reliable. However, the ability to re-image using USB stick into clone XOs using NAND blaster was a boon. With the advent of the new image based on Fedora 11, the ability to switch between sugar and gnome interface, the XOs ones have been given a new lease of life. And as a result, they're more stable. And as a result of the trial, we concluded that there was educational benefit in using the XOs that could be integrated into the school network. So with NAND blasting, to cut a long story short, if we just use a USB stick and re-image one XO laptop, it takes about 16 minutes. We can re-image a class of 30 XO laptops in 46 minutes using NAND blaster. So if you think back, in your school, how long does it take you to re-image a computer in the Northern Territory Government where we're using Windows systems that can take probably an hour or so per machine? Yes? Yeah? You're up. This whole thing seems to be predicated on the fact that it is assumed that laptops will contribute to education. So has there been any study done on a group of children with laptops versus a controlled group without laptops to see whether their educational prospects are better? Not yet. The challenges we have, as Shrita mentioned, about charging them, that's the XOP sorted that out. Another problem we've had is this one. Of keyboards getting ripped, my solution was to pre-lay four sheets, laminate them, and have that. It's not 100% effective yet. You just sort of have to apply pressure, but that's something where people can help out. We have high-staff turnovers in schools, and the whole idea is to actually train local people and students to be able to support this system. One of my goals is to encourage the use of free and open source software. So it works independently. Tux Maths, Tux Music Paint Open Office, there's quite a few that will work across platform now. Many people look at the XOs and laugh and say, cute kids toys. From my experience, they're more than meets the eye. With the RPC project, I'll earn something new every day. Thank you. Thank you very much. We've only got one gift. I guess you did the longest stretch. You can break it in half and give him the other half. Thank you very much. Put your hands together for them, please. Thank you.