text:
Shout Out Louds See 'Optica' February Drop; Stream/Watch "Blue Ice"/
Swedish alt-pop outfit Shout Out Louds will release their fourth album, Optica, on February 26 via Merge. This is the band's fourth album and follows up their 2010 release Work. Last week, the band gave away "Blue Ice" from Optica as a 7" actually made of ice. Stream the track and watch the video below.
From the Press Release: Shout Out Louds' first show in support of Optica will take place in Brooklyn, NY, at the Music Hall of Williamsburg on March 11 leading up to the SXSW Music Festival, and they have confirmed a full stateside tour for May 2013, beginning May 7 in Washington, DC, and ending on May 23 at the El Rey in Los Angeles, CA.
Following their 2010 album Work, the band (Adam Olenius – lead vocals; Bebban Stenborg – keyboards; Ted Malmros – bass; Carl von Arbin – guitar; and Eric Edman – drums) headed out on their most successful tour ever and returned home to their own pursuits. Families were expanded, side projects were launched and homes outside of Stockholm were explored. When the time came to work on another Shout Out Louds record they wanted to return to the playful spirit that first brought them together 10 years ago.
Shout Out Louds took their time with these songs, recording for about one-and-a-half years in a small Stockholm studio and producing themselves for the first time with help from Johannes Berglund. A theme emerged and Optica was born, an album celebrating color and light from a band confident in its sound, filled with real strings, trombones, trumpets and flutes.
Shout Out Louds explain:
"In our eagerness to please no one but ourselves this time around, we decided to take on the challenge of producing our own music for the first time ever. Our close friend and sound aficionado of choice Johannes Berglund and his studio in Stockholm presented us with an ideal package for the endeavor. A secluded work space close to home, but off the earth's surface, a more than generous timeline, and the patient and brilliant sixth member we needed to get through the whole thing safely. Together we made up a downstairs world of explosive colors, big, warm sounds and a very, very uninhibited work process. We never worried about following a clear path, trusting that the conscious decision not to worry would be enough to lead us right, and that right doesn't necessarily have to mean rational or even reasonable…We all set prestige and skillfulness aside in favor of experimentation and sheer gusto. That will probably come across live too. I don't think we've ever been this excited to take an album on tour."
Optica track listing:
1. Sugar
2. Illusions
3. Blue Ice
4. 14th of July
5. Burn
6. Walking In Your Footsteps
7. Glasgow
8. Where You Come In
9. Hermila
10. Chasing the Sinking Sun
11. Circles
12. Destroy
Shout Out Louds on tour:
March 11 Brooklyn, NY Music Hall of Williamsburg
March 13-16 Austin, TX SXSW Music Festival
May 7 Washington, DC 9:30 Club
May 8 Philadelphia, PA Union Transfer
May 11 Boston, MA Paradise
May 13 Montreal, QC La Sala Rosa
May 14 Toronto, ONT The Opera House
May 15 Detroit, MI The Magic Bag
May 16 Chicago, IL Metro
May 17 Minneapolis, MN Varsity Theater
May 22 San Francisco, CA Great American Music HallMay 23 Los, Angeles, CA El Rey
Shout Out Louds - "Blue Ice" (from Optica)


text:
State law says premiums must be fair and reasonable, but it doesn't require them to be adjusted when rebuilding costs decline. And regulators don't control how insurers se trebuilding costs.
"One would think insurance rates would decline," said Bill Newton, executive director of Florida Consumer Action Network. "Instead, we've had increases either directly or through losing… discounts."
When the economy crashed in 2008, so did Florida's construction industry.
Building costs in Florida dropped 4.78 percent from 2009 to mid-2010, according to Xactware Solutions, a research firm that produces a quarterly index used by insurance companies to calculate rebuilding costs.
Another index widely used by insurers, produced by Marshall & Swift/Boeckh, shows a smaller decrease. Both indices are starting to rise again, as materials costs climb.
Roger Zahn Jr., president of Zahn Luxury Builders in Lighthouse Point, said his company used to provide prospective customers with an average quote of $200 or $225 per square foot to build a typical home from the ground up. Now it's $175 to $190.
"It's gone down considerably" because builders are being forced to cut costs and workforce expenses to compete for the few jobs available, he said. "It's supply and demand really. There's no work out there."
A letter from Zahn helped Gail Bierworth, a retiree who lives in Lighthouse Point part of the year, convince Citizens Property Insurance to lower her windstorm insurance premium, with a replacement cost that dropped to $347,000 this year from $698,000 last year.
With the lower replacement cost, Bierworth's windstorm premium fell to $1,315 from $2,346.
"If I needed the $600,000 in coverage I would have had to pay the high premiums," she said recently. As building costs go up, she said she's worried the industry will "grab onto that" and increase the rebuilding cost. But she's prepared to pay more if construction costs rise considerably.
Most homeowners' premiums go directly to cover the cost of rebuilding or repairing. Some pay for marketing, employees' salaries and other administrative costs.
In general, insurance companies say they've had to raise rates in Florida in recent years because premiums are not keeping up with expenses, including more claims for non-catastrophic issues such as sinkholes. They also say they've been too generous with discounts for strengthening homes against hurricanes.
Insurers point to other factors that may raise the cost of replacing South Florida homes: high-end finishes, such as granite countertops and expensive appliances, as well as years-old home improvements that may be overlooked by the homeowner, such as room additions and remodeling.
Insurers also have to take into account that it can cost more to rebuild an older home than to build a new one, said a representative of Marshall & Swift/Boeckh. It can be costly to duplicate old designs and materials.
Consumer advocate Newton questions insurers motives. He points out that reinsurance – insurance that insurers buy to cover their risks -- has dropped in price. He notes that insurance company investments earned less in recent years.
Paul Mack, president of Mack, Mack & Waltz Insurance Group in Deerfield Beach, said insurance companies usually don't accept applications for lower replacement costs.

subset: commoncrawl


text:
Shows you how to use the powerful slideshow tool FotoMagico and Adobe Photoshop to break the mold of simple sequenced images.
Explore the ACR interface and its powerful features; learn how to customize the settings and make your images look just the way you want.
"What I'm learning will save me a lot of time and frustration on current and future projects." —Linda J.
more from our members »


text:
Audio Samples
Album Summary
Notes & Reviews:
The San Francisco-based Cypress String Quartet, known equally for its innovation and its elegant performances, debuts on AVIE with a recording of its namesake work, a set of 12 love songs scored for string quartet, coupled with the composer's expansive G major Quartet, No. 13. Known internationally through touring and a dozen acclaimed recordings, the Cypress String Quartet traverses repertoire from J.S. Bach to world premieres of works they have commissioned from such composers as Jennifer Higdon, Kevin Puts, and Elena Ruehr.
Artistry of uncommon insight and cohesion.
BBC Music Magazine, May 2013
Notwithstanding the odd rough edge, the eponymous Cypress Quartet play these arrangements with exquisite shading and a fine sense of nuance. Their performance of Dvorak's last and greatest quartet is rather less satisfactory...In the slow movement, the performers don't really capture the movement's almost tumultuous passion...[the scherzo and finale] both have thrilling impetus as well as some beautiful shaping of the more lyrical material.
Recording information: Skywalker Sound Studios (2012-07-28_2012-08-01&2012-).
ReviewsThere are currently no reviews, be the first one!
Also Purchased
Works DetailsAntonin Dvorák (1841 - 1904) : Cypresses (Ohlas písní [Echoes of Songs]), for string quartet (arr. from Cypresses, B. 11), B. 152
- Ensemble: Cypress String Quartet
- Notes: Skywalker Sound Studios (07/28/2012-08/01/2012); Skywalker Sound Studios (09/14/2012-09/16/2012)
- Running Time: 28 min. 24 sec.
- Period Time: Romantic
- Form: Chamber Music
Antonin Dvorák (1841 - 1904) : Quartet for Strings no 13 in G major, Op. 106/B 192
- Notes: Skywalker Sound Studios (07/28/2012-08/01/2012)
- Running Time: 37 min. 34 sec.
- Period Time: Romantic
- Form: Chamber Music
- Written: 12/09/1895


text:
Ohio State offers expert care for women experiencing high-risk pregnancy.
The Ohio State University Wexner Medical Center's Maternal Fetal Medicine programs and clinics provide unparalleled personal care in addressing pregnancy complications. Working with your obstetrician/gynecologist, we offer compassionate, coordinated, personalized care backed by innovative research, depth of medical expertise, and leading technologies and treatments. And because we're an academic medical center that's part of Ohio State, we have access to resources, equipment and support that make certain treatments possible only here.
At our Maternal Fetal Medicine programs and clinics, we care for women experiencing high-risk pregnancies, including those with multiples pregnancy, diabetes, high blood pressure, genetic conditions, premature birth history, advanced maternal age or any condition requiring high-risk care or fetal treatment.
Our Services
Adult congenital heart disease in pregnancy program
Specialized care for pregnant women with a congenital or acquired heart condition
Diabetes in pregnancy program
Personalized care for expectant mothers with pre-existing or pregnancy-related diabetic conditions
Prematurity program
Expert care for women with a history of preterm (born before 37 weeks) birth
Fetal treatment program
Advanced care for women carrying a baby or babies diagnosed with a birth defect or pregnancy complication
Genetics and preconception counseling
State-of-the-art care for families with an increased risk for having a child with a birth defect or genetic condition
Substance abuse, treatment, education and prevention program (STEPP)
Compassionate care for expectant mothers with drug or alcohol addictions
Patient Forms
Before your visit, please print and complete the following patient forms, and bring them with you to your appointment.
Patient Success
Early diagnosis helped Courtney have a healthy baby
When Courtney's son Corbyn was diagnosed with complications during pregnancy she turned to Ohio State's Maternal Fetal Medicine experts.
Monitoring high-risk pregnancy provides peace of mind
Dawn, age 37, of Dublin, Ohio, has learned how to deal with stress. Whether it's running her own baking business or juggling schedules for her family of four, she tackles life's hurdles one day at a time.


text:
Chimney, Leading heat away from WFO???
Gdday guys,
I'm quite new in this world - actually a big newb, I just signed into this forum today :) - But i had the ideas for this WFO for some time now.
My plan is to make an WFO beg 14' so now i'm prepping my self on the design, and the does and dont. Its going to be a 42" Pompeii (for now atleast)
I have a questions in regards to the chimney for a WFO - the title is more or less self explanatory, but the idea of a chimney is to lead the smoke away from the Master Chef cooking, right ? But as heat rises up towards the roof. Dosent this lead all the heat out of the dome ? Or do a chimney based WFO need some kind of dampers to prevent this heat loss ? - I tried to google and use this forum, but no luck - maybe its the danish words translated into English thats wrong.
PS. The wording and the spelling mistakes are 100% free - i'm from Denmark :)
Re: Chimney, Leading heat away from WFO???
Our designs have the chimney / vent on the outside of the dome. Download the free plans from the store, it will give you a better idea on how all this goes together.
Re: Chimney, Leading heat away from WFO???
Hi Les,
Thanks for the input, I have received the PDF and it's also clear to me now.
Thank you.
Re: Chimney, Leading heat away from WFO???
If you want a flue inside the oven then yes, you will need a chimney damper. :)
Re: Chimney, Leading heat away from WFO???
The chimney in Forno Bravo plans is set in front of the firing chamber. When you start an oven fire, air flows in from the front opening (lower portion) to the fire inside. As the fire burns, heat/smoke move up and back. Then the fire exhaust gases move forward along the curved top, circling back to the opening. The heated gases warm the bricks on their way and exit up and out the chimney via the top portion of the front opening. When you start a fire, you see a clear division of cool air entering below and smoky warm air exiting above when looking at the oven opening. (It's really fascinating to watch an oven breathe in this manner!)
Hope that helps a little, but the plans explain this much better. You only need a damper for the chimney if you place the chimney inside the firing chamber. With the chimney outside the oven chamber, you can remove the fire/coals, close the chamber with an insulated door, and keep baking temps inside the oven for a pretty long time!
Re: Chimney, Leading heat away from WFO???
Alright SableSpring, i took notice, and i have in the last couple of hours read the pdf on some 70 pages. Quite good reading! and I also learned about the door position, before i thought the door would be placed on the outside of the chimney vent, so all the hot air would travel up and "heat the garden"
But now i'm even more excited, damn new-years-eve-time - all shops are closed until 02.01.14 :D
Re: Chimney, Leading heat away from WFO???
Build it like the plans and you will be astounded at the efficiency. The hot gases from the fire contact a lot of brick in a very efficient manner before they exit the dome and turn up into the chimney.
I have sometimes wondered if any clever engineer has made any sort of calculation or measurement as to how much heat (perhaps in terms of a percentage of the heat available from the burning fuel) is transferred to the bricks compared with say an open fire place?
Re: Chimney, Leading heat away from WFO???
Re: Chimney, Leading heat away from WFO???
Welcome. Your spelling is good.
As you read the plans, the design will come into focus. Keep digging for that information. :)
Re: Chimney, Leading heat away from WFO???
|All times are GMT -7. The time now is 06:09 PM.
Powered by vBulletin® Copyright ©2000 - 2015, Jelsoft Enterprises Ltd.
Search Engine Friendly URLs by vBSEO 3.6.0
© 2006/10 Forno Bravo, LLC


text:
Columbus, OH (PRWEB) June 05, 2014
House Bill 463, which was introduced by Ohio Rep. Terry Johnson (R-McDermott) and passed the House 95-0, would expand access to dental care in a comprehensive, safe, high-quality way and maximize the current dental care infrastructure and delivery system.
The Ohio Dental Association strongly supports House Bill 463, which is in conjunction with the ODA's campaign "Every Mouth Matters: Comprehensive Solutions for Quality Dental Care in Ohio."
"We are very happy to see that House Bill 463 has passed the House, and look forward to working with the Senate for fast approval to improve access to oral health care in Ohio," said David Owsiany, executive director of the Ohio Dental Association.
The bill proposes several ways to improve access to care, including:
Owsiany thanked Johnson for his "tireless efforts to secure passage of Substitute House Bill 463 in the Ohio House."
The ODA serves more than 5,000 member dentists, nearly 75 percent of the state's licensed dentists, through programs, services and member benefits. In addition, the ODA reaches out to consumers, educators, health professionals and others through education, advocacy and public service programs.


text:
0 Comments 21
Back to School Rooms for Sports FansPosted by Katie
It's that time of year again. Just when you get used to the summer heat and sleeping with all of the windows open, a quick trip to the store filled with displays of pens, pencils and notebooks reminds you that fall is just around the corner. The air will soon cool and that means back to school! Blindsgalore® Official Collegiate Continue Reading ...


text:
A virtual machine monitor (VMM) is included in a computer system that has a protected host operating system (HOS). A virtual machine running at least one application via a virtual operating system is connected to the VMM. Both the HOS and the VMM have separate operating contexts and disjoint address spaces, but are both co-resident at system level. A driver that is downloadable into the HOS at system level forms a total context switch between the VMM and HOS contexts. A user-level emulator accepts commands from the VMM via the system-level driver and processes these commands as remote procedure calls. The emulator is able to issue host operating system calls and thereby access the physical system devices via the host operating system. The host operating system itself thus handles execution of certain VMM instructions, such as accessing physical devices.
1. In a computer system that has a hardware processor including an interrupt table pointer register and an operating system (OS), which includes a first interrupt vector table and a first set of state parameters, and a sub-system, which includes a second interrupt table vector, a second set of state parameters, and is contextually separated from the OS, a method for enabling interrupt handling in the sub-system comprising the following steps:
in an OS context, accessing the interrupt table pointer register and setting the interrupt table pointer register to point to the first interrupt table vector, and storing the second set of state parameters, whereby interrupts are routed for handling to the OS; and
in a sub-system context, accessing the interrupt table pointer register and setting the interrupt table pointer register to point to the second interrupt table vector, and storing the first set of state parameters, whereby the interrupts are routed for handling to the sub-system.
2. A method as in
in the sub-system context, handling external interrupts by restoring the OS context by restoring the first state parameters, and forwarding the external interrupts for processing by the OS.
3. A method as in
installing a system-level driver into the operating system; and
accessing the interrupt table pointer register from the driver.
4. A method as in
loading the OS and the sub-system in disjoint memory spaces;
selecting a cross-over memory portion such that it is has the same address in both the OS context and the sub-system context; and
storing in the cross-over memory portion instructions changing the address space and directing the processor to its next instruction.
5. A method as in
6. In a host computer system that has a processor and a host operating system (HOS), a virtualization method comprising the following steps:
running a virtual machine monitor (VMM) on the host system, the VMM forming a system-level interface for a virtual machine (VM);
reading in and storing state information of the processor associated with the HOS; and
logically decoupling the HOS from the processor with respect to pre-determined VMM and VM functions by setting the processor state information to settings associated with the VMM.
7. A method as in
8. A method as in
including in the VMM a VMM interrupt handler separate from an HOS interrupt handler; and
calling, upon occurrence of an exception, the exception handler pointed to by the exception vector.
9. A method as in
10. A method as in 6, in which the state information of the processor includes a pointer to an exception vector table, the method further comprising the step of accessing the exception vector table using the processor setting associated with the VMM.
11. A computer system comprising:
A) hardware processor that has an interrupt table pointer register;
B) an operating system (OS), with which is associated a first interrupt vector table and a first set of state parameters;
C) a virtual machine monitor (VMM), with which is associated a second interrupt table vector, a second set of state parameters, and is contextually separated from the OS; and
D) a virtual machine (VM) running on the VMM, which forms a system-level interface between the processor and the VM;
F) a computer program including computer instructions for handling interrupts in an OS context and in a virtual context by
i) accessing, when in the OS context, the interrupt table pointer register and setting the interrupt table pointer register to point to the first interrupt table vector, and storing the second set of state parameters such that interrupts are routed for handling to the OS; and
ii) accessing, when in the virtual context, the interrupt table pointer register and setting the interrupt table pointer register to point to the second interrupt table vector, and storing the first set of state parameters such that interrupts are routed for handling to the VMM.
12. In a computer system that has:
a hardware processor including an interrupt table pointer register;
an operating system (OS), with which is associated a first interrupt vector table and a first set of state parameters;
a virtual machine monitor (VMM), with which is associated a second interrupt table vector, a second set of state parameters, and is contextually separated from the OS; and
a virtual machine (VM), the VMM forming a system-level interface between the processor and the VM;
a method for interrupt handling comprising the following steps:
in an OS context, accessing the interrupt table pointer register and setting the interrupt table pointer register to point to the first interrupt table vector, and storing the second set of state parameters, whereby interrupts are routed for handling to the OS; and
in a virtual context, accessing the interrupt table pointer register and setting the interrupt table pointer register to point to the second interrupt table vector, and storing the first set of state parameters, whereby the interrupts are routed for handling to the VMM.
This application is a continuation of and claims priority of U.S. patent application Ser. No. 09/151,175, filed 10 Sep. 1998, now U.S. Pat. No. 6,496,847 which in turn claims priority from U.S. Provisional Patent Application No. 60/085,685, filed 15 May 1998.
1. Field of the Invention
This invention relates to a computer architecture, including a virtual machine monitor, and a related operating method that allow virtualization of the resources of a modern computer system.
2. Description of the Related Art
The operating system plays a special role in today's personal computers and engineering work stations. Indeed, it is the only piece of software that is typically ordered at the same time the hardware itself is purchased. Of course, the customer can later change operating systems, upgrade to a newer version of the operating system, or even re-partition the hard drive to support multiple boots. In all cases, however, a single operating system runs at any given time on the computer. As a result, applications written for different operating systems cannot run concurrently on the system.
Various solutions have been proposed to solve this problem and eliminate this restriction. These include virtual machine monitors, machine simulators, application emulators, operating system emulators, embedded operating systems, legacy virtual machine monitors, and boot managers. Each of these systems is described briefly below.
Virtual Machine Monitors
One solution that was the subject of intense research in the late 1960's and 1970's came to be known as the "virtual machine monitor" (VMM). See, for example, R. P. Goldberg, "Survey of virtual machine research," IEEE Computer, Vol. 7, No. 6, 1974. During that time, moreover, IBM Corp. adopted a virtual machine monitor for use in its VM/370 system.
A virtual machine monitor is a thin piece of software that runs directly on top of the hardware and virtualizes all the resources of the machine. Since the exported interface is the same as the hardware interface of the machine, the operating system cannot determine the presence of the VMM. Consequently, when the hardware interface is compatible with the underlying hardware, the same operating system can run either on top of the virtual machine monitor or on top of the raw hardware.
Virtual machine monitors were popular at a time where hardware was scarce and operating systems were primitive. By virtualizing all the resources of the system, multiple independent operating systems could coexist on the same machine. For example, each user could have her own virtual machine running a single-user operating system.
The research in virtual machine monitors also led to the design of processor architectures that were particularly suitable for virtualization. It allowed virtual machine monitors to use a technique known as "direct execution," which simplifies the implementation of the monitor and improves performance. With direct execution, the VMM sets up the processor in a mode with reduced privileges so that the operating system cannot directly execute its privileged instructions. The execution with reduced privileges generates traps, for example when the operating system attempts to issue a privileged instruction. The VMM thus needs only to correctly emulate the traps to allow the correct execution of the operating system in the virtual machine.
As hardware became cheaper and operating systems more sophisticated, VMMs based on direct execution began to lose their appeal. Recently, however, they have been proposed to solve specific problems. For example, the Hypervisor system provides fault-tolerance, as is described by T. C. Bressoud and F. B. Schneider, in "Hypervisor-based fault tolerance," ACM Transactions on Computer Systems (TOCS), Vol. 14. (1), February 1996; and in U.S. Pat. No. 5,488,716 "Fault tolerant computer system with shadow virtual processor," (Schneider, et al.). As another example, the Disco system runs commodity operating systems on scalable multiprocessors. See "Disco: Running Commodity Operating Systems on Scalable Multiprocessors," E. Bugnion, S. Devine, K. Govil and M. Rosenblum, ACM Transactions on Computer Systems (TOCS), Vol. 15, No. 4, Nov. 1997, pp. 412447.
Virtual machine monitors can also provide architectural compatibility between different processor architectures by using a technique known as either "binary emulation" or "binary translation." In these systems, the VMM cannot use direct execution since the virtual and underlying architectures mismatch; rather, they must emulate the virtual architecture on top of the underlying one. This allows entire virtual machines (operating systems and applications) written for a particular processor architecture to run on top of one another. For example, the IBM DAISY system has recently been proposed to run PowerPC and x86 systems on top of a VLIW architecture. See, for example, K. Ebcioglu and E. R. Altman, "DAISY: Compilation for 100% Architectural Compatibility," Proceedings of the 24th International Symposium on Computer Architecture, 1997.
Machine Simulators/Emulators
Machine simulators, also known as machine emulators, run as application programs on top of an existing operating system. They emulate all the components of a given computer system with enough accuracy to run an operating system and its applications. Machine simulators are often used in research to study the performance of multiprocessors. See, for example, M. Rosenblum, et al., "Using the SimOS machine simulator to study complex computer systems," ACM Transactions on Modeling and Computer Simulation, Vol. 7, No. 1, Jan. 1997. They have also been used to simulate an Intel x86 machine as the "VirtualPC" or "RealPC" products on a PowerPC-based Apple Macintosh system.
Machine simulators share binary emulation techniques with some VMMs such as DAISY. They differentiate themselves from VMMs, however, in that they run on top of a host operating system. This has a number of advantages as they can use the services provided by the operating system. On the other hand, these systems can also be somewhat constrained by the host operating system. For example, an operating system that provides protection never allows application programs to issue privileged instructions or to change its address space directly. These constraints typically lead to significant overheads, especially when running on top of operating systems that are protected from applications.
Application Emulators
Like machine simulators, application emulators also run as an application program in order to provide compatibility across different processor architectures. Unlike machine simulators, however, they emulate application-level software and convert the application's system calls into direct calls into the host operating system. These systems have been used in research for architectural studies, as well as to run legacy binaries written for the 68000 architecture on newer PowerPC-based Macintosh systems. They have also been also been used to run x86 applications written for Microsoft NT on Alpha workstations running Microsoft NT. In all cases, the expected operating system matches the underlying one, which simplifies the implementation. Other systems such as the known Insigna's SoftWindows use binary emulation to run Windows applications and a modified version of the Windows operating system on platforms other than PCS. At least two known systems allow Macintosh applications to run on other systems: the Executer runs them on Intel processors running Linux or Next and MAE runs them on top of the Unix operating system.
Operating System Emulators
Operating system (OS) emulators allow applications written for one given operating system application binary interface (ABI) to run on another operating system. They translate all system calls made by the application for the original operating system into a sequence of system calls to the underlying operating system. ABI emulators are currently used to allow Unix applications to run on Window NT (the Softway OpenNT emulator) and to run applications written for Microsoft's operating systems on public-domain operating systems (the Linux WINE project).
Unlike virtual machine monitors and machine simulators, which are essentially independent of the operating system, ABI emulators are intimately tied with the operating system that they are emulating. Operating system emulators differ from application emulators in that the applications are already compiled for the instruction set architecture of the target processor. The OS emulator does not need to worry about the execution of the applications, but rather only of the calls that it makes to the underlying operating system.
Embedded Operating Systems
Emulating an ABI at the user level is not an option if the goal is to provide additional guarantees to the applications that are not provided by the host operating system. For example, the VenturCom RTX Real-Time subsystem embeds a real-time kernel within the Microsoft NT operating system. This effectively allows real-time processes to co-exist with traditional NT processes within the same system.
This co-existence requires the modification of the lowest levels of the operating system, that is, its Hardware Abstraction Layer (HAL). This allows the RTX system to first handle all I/O interrupts. This solution is tightly coupled with WindowsNT, since both environments share the same address space and interrupts entry points.
Legacy Virtual Machine Monitors
Certain processors, most notably those with the Intel architecture, contain special execution modes that are specifically designed to virtualize a given legacy architecture. This mode is designed to support the strict virtualization of the legacy architecture, but not of the existing architecture.
A legacy virtual machine monitor consists of the appropriate software support that allows running the legacy operating system using the special mode of the processor. Specifically, Microsoft's DOS virtual machine runs DOS in a virtual machine on top of Microsoft Windows and NT. As another example, the freeware DOSEMU system runs DOS on top of Linux.
Although these systems are commonly referred to as a form of virtual machine monitor, they run either on top of an existing operating system, such as DOSEMU, or as part of an existing operating system such as Microsoft Windows and Microsoft NT. In this respect, they are quite different from the true virtual machine monitors described above, and from the definition of the term "virtual machine monitor" applied to the invention described below.
Boot Managers
Finally, boot managers such as the public-domain LILO and the commercial System Commander facilitate changing operating systems by managing multiple partitions on the hard drive. The user must, however, reboot the computer to change operating systems. Boot managers therefore do not allow applications written for different operating systems to coexist. Rather, they simply allow the user to reboot another operating system without having to reinstall it, that is, without having to remove the previous operating system.
General Shortcomings Of The Prior Art
All of these known systems fail to meet one or more of the following goals:
2) to provide portability of the virtual machine monitor across a wide range of platforms; and
This invention provides a system that achieves these goals, as well as a related operating method.
The invention virtualizes a computer that includes a host processor, memory, and physical system devices. A conventional operating system (referred to below as the "host operating system" or "HOS") is installed on the hardware. The computer is operationally divided into a system level and a user level and the computer accepts and carries out a pre-determined set of privileged instruction calls only from sub-systems at the system level. The invention provides at least one virtual machine monitor (VMM) that is installed to be co-resident with the host operating system at the system level.
In the preferred embodiment of the invention, a driver is downloaded into and is resident in the host operating system. A host operating system (HOS) context is then saved in the driver. A corresponding virtual machine monitor (VMM) context is saved in the virtual machine monitor. Switching from the HOS context to the VMM context is then carried out in the driver, whereas switching from the VMM context to the HOS context is done in the virtual machine monitor. The driver issues, in the HOS context, commands previously specified by the VMM.
A predetermined physical address space is assigned to the system memory, and virtual addresses are converted into physical addresses of the memory's physical address space in a memory management unit (MMU). HOS context parameters are stored in a first virtual address space in the host operating system and VMM context parameters are stored in the virtual machine monitor in a second address space, which is disjoint from the first address space. The HOS and VMM context parameters also represent different interrupt and exception entry points for the host operating system and the virtual machine monitor, respectively. Switching between the HOS and VMM contexts is then carried out by selectively setting internal registers of the host processor to correspond to the HOS and VMM context parameters, respectively.
As a further feature of the invention, a device emulator is preferably installed to be operatively connected to the host operating system. The device emulator accepts commands stored in memory by the VMM via the driver and processing these commands. The emulator also issues host operating system calls and thereby accessing the physical system devices via the host operating system.
At least one virtual machine is preferably installed at user level. The virtual machine includes at least one associated application and a virtual operating system, and is operatively connected to the virtual machine monitor. An entire programmable virtual address space of the computer is thereby made available to both the virtual machine and the virtual machine monitor.
The emulator is preferably operatively connected as an application to the host operating system. In a preferred embodiment of the invention, the driver passes first instruction calls from the virtual machine monitor directly to the host operating system, the system devices, and the processor, and passes second instruction calls from the virtual machine monitor, via the emulator, to the host operating system. The driver also passes data to the virtual machine monitor in response to the first and second instruction calls received both via the emulator and directly from the system devices, the processor and the host operating system. The second instruction calls are thereby executed directly in the host operating system.
In the preferred embodiment of the invention, the commands processed in the driver in the HOS context are processed as remote procedure calls. Similarly, the commands processed in the device emulator, via the driver, are also preferably processed as remote procedure calls.
The invention is described below in sections for the sake of clarity. First, two conventional architectures are described in order to make it easier to see the unique features of the invention by way of comparison. Then, the system according to the invention is described as a whole. Finally, the main novel features of the invention are described individually.
Conventional Virtual Machine Monitor Architectures
Because the VMM 100 in the conventional system shown in
Conventional Machine Emulator Architectures
System Architecture According to the Invention
The use of a user-level device emulator 300 allows the invention to meet the second goal stated above. The application portion of the system takes care of all system-specific emulation and relies on the existing host operating system 340 to perform this emulation.
The use of a system-level virtual machine monitor 360 allows the invention to meet the third goal of maximal performance. In order to make this possible, the invention also provides that the VMM 360 can configure the processor and its memory management unit (MMU) independently of any constraints imposed by the host operating system—failure to do so would prevent the VMM from setting up the processor and MMU so that the virtual machine 320 can directly take advantage of them. The VMM according to the invention allows its associated virtual machine 320 to use as many components of the hardware directly and safely as possible given the processor architecture. For example, the ability to use direct execution to run the virtual machine is a function of the current state of the virtual processor.
A set of applications (symbolized by circles) is indicated in
Assume that the virtual machine 320 is designed as a virtual Unix system and that the applications 330 are thus Unix-based applications. The virtual machine 320 then will also include a virtual operating system (VOS) 370, which communicates with the "real," or "physical" system hardware via the VMM 360. Other applications 332 running on another virtual machine 322 will similarly run via a respective virtual operating system 372 and the associated VMM 362. Note that the invention allows running many different types of applications on the same computer system, regardless of what the host operating system is. Each application is thus associated with its intended operating system, either the host operating system 340 (applications 329), or with a respective virtual operating system 370, 372 associated in turn with each respective VMM 320, 322.
Current computer systems, and especially personal computers, support a wide range of devices that each interact in a different manner with the system software. As a result, each device requires special system software support. A device driver is typically downloaded into the operating system to provide this support. A conventional virtual machine monitor (see
This invention overcomes this limitation by providing that the VMM 360 according to the invention is co-resident with the existing protected operating system (the host operating system 340). The VMM runs independently of the host operating system—it is in no way an extension of the operating system, but rather operates with its own address space and with its own interrupt and exception handlers. The virtualization system also includes a device emulator 300 that runs as a user-level application on top of the host operating system 340. Because it operates as a typical process running on top of the HOS, the device emulator 300 according to the invention can use standard operating system calls to access physical devices 380 such as (but not limited to) a disk drive.
The co-residency of the VMM and the HOS at system level implies that both can independently configure the hardware processor, and that the HOS retains all of its function. This allows not only the device emulator 300 but also other independent applications to operate in the HOS context.
In actual implementations of the invention that include more than one VMM, there is preferably a different user-level device emulator for each VMM. This maintains the functional and contextual separation of the different VMMs (described below), simplifies the design of each device emulator, and allows for the greatest degree of flexibility and portability of each VMM. The HOS can then schedule the VMMs, via their respective device emulators, just like it schedules other user-level applications (such as applications 329). It is also possible, however, to include a single device emulator to handle all VMMs, although this would greatly impair or rule out the generality, flexibility, portability and simplicity provided by having dedicated device emulators.
In order for the system-level VMM 360 to use this ability of the user-level device emulator 300 to issue standard operating system calls, some interface is required. According to the invention, this interface is provided by a driver 390, which is downloaded into or otherwise installed or included in the HOS 340. The driver 390 also allows each VMM to be loaded into the system and also implements a switch (described further below) between the host operating system context and the VMM context.
The illustrated, preferred architecture according to the invention requires some minimal support from the host operating system. For example, the host operating system 340 must support down-loadable device drivers (since the driver 390 acts as one), and these must execute at the most privileged level. Also, either the user-level process (such as the device emulator 300) or the driver 390 must be able to allocate certain pages of memory with the guarantee that the operating system will not reclaim them. This functionality, known as "locking pages," is routinely used by conventional device drivers and the requirement is therefore no practical limitation to the general applicability of the invention.
The concept of a "protected" operating system, that is, a system in which only the host operating system is able to issue instruction calls that will affect the privileged state, is typically associated with an interface widely known as the System Call Application Program Interface (API). A different API, known as a Device Driver API, similarly provides an interface between system-level device drivers and the HOS.
The API 392 is the interface exported by the HOS to its applications. This API is normally a layer of software that defines the set of services offered by the HOS to user-level applications. On operating systems that provide protection, API system calls are implemented by a secure mechanism that allows transitions of the processor between user-level mode and system-level mode. In such systems, the API 392 itself checks whether calls from applications are permissible, and prevents impermissible calls from reaching and affecting the proper running of the host operating system.
One example of a user API 392 request would be a call from an application whose execution requires a level of privilege not granted to applications running at user level, such as instruction calls that would alter certain important registers used only by the processor for its internal control. Another call that would normally not be allowed would be an attempt by an application to directly control a disc, such as instructions directing the read head to a particular track and sector, or that would alter necessary system files. Examples of an API 392 to applications include the POSIX system for UNIX operating systems.
The API 394 is the interface exported by the HOS to its downloadable device drivers. Note that downloadable device drivers typically operate at the system level with the same privileges as the HOS itself; otherwise, it would take far too long for, for example, a modem driver to do its job with proper synchronization. As such, these device drivers are "inside" the protective API 392 to applications. Indeed, they are typically downloaded to become a functional part of the host operating system itself. In these cases, the API 394 is commonly not an actual body of programming code within the operating system, but rather is simply a convention followed by producers of device drivers. In
In other words, the API 394 is normally an agreed-upon set of unprotected function calls that downloaded device drivers may issue. The API 394 thus does not offer any active protection to the operating system; rather each respective device driver views the API 394 as a permissible set of operations that it may perform that might also change the state of the operating system. One example of a device driver 394 request would be a request made by a disk driver to "lock" a certain number of given pages into memory with the guarantee that the operating system will not use these pages for other purposes until allowed to by the holder of the lock. An example of an API 394 to device drivers is the DDK interface by Microsoft.
One of the unique features of the invention is that the VMM 360 (which is at the system level) is able to issue what are known as "remote procedure calls" (RPC) to the device emulator 300 (which is at the user level) via the driver 390, which is loaded as a conventional device driver into the HOS 340. RPCs are a well-known programming technique, originally described in "Implementing Remote Procedure Calls," A. D. Birrell and B. J. Nelson, ACM Transactions on Computer Systems, 2(1), pp. 39–59, 1984.
In the preferred embodiment of the invention shown in
One type of privilege register that is used in the invention to enable the VMM to be co-resident with the HOS is the register that directs the processor to a table of addresses that point it to instructions to be executed upon sensing any of a predetermined set of interrupts, which may be both hardware and software. By way of example, in the widely prevalent Intel x86 architectures, this privilege register is known as the "interrupt descriptor table register" (IDTR), which is a register within the hardware processor 110 itself, and which, in the figures, is labeled 400. The corresponding table of addresses (the exception vector) for the respective interrupts is known, accordingly, as the "interrupt descriptor table" (IDT). As
The exception vector 402 is, as is mentioned above, a table that points to the addresses of the respective entry points to be executed after the respective exceptions or interrupts occur. In
Assume that a memory page fault is pre-defined to be exception number 14, and that the processor has just sensed a page fault. The system, that is, the hardware processor, will first address the IDTR 400, which will return the address in physical, memory of the position in the exception vector 402 for exception number 14. This memory position will in turn point to the corresponding entry point, which is the address of the first instruction the processor is to execute after the corresponding exception (here, a page fault) occurs. In short, this structure tells the processor where to get its next instruction whenever certain pre-defined non-standard conditions (roughly, "faults") occur.
Refer again to
According to the invention, an IDT is set up in each virtual machine monitor. These IDTs include the exception vectors and entry points for their respective virtual machines. In other words, the system according to the invention is also able to virtualize exception-handling as part of its total context-switching operation.
Total Switch
The switch between the host operating system 340 context and the (that is, each) VMM 360 context requires more than a conventional context switch, such as the one implemented by operating systems to time-share processes. The switch used in the preferred embodiment of the invention is referred to and described below as a "total processor switch" or, simply, a "total switch" since it saves and restores all the registers, segments, floating-point registers, and control registers of the processor included in the given computer hardware 110. Any available memory space may be used to save this information, and actual storage and retrieval may be accomplished using any known technique. The total switch also changes the address space so that the host operating system's address space does not need to be mapped into the VMM's address space. As a result, the VMM has the ability to freely manage all the address space of the system while executing in its own context. Finally, the switch changes the interrupt dispatch entry points, since the VMM according to the invention handles directly all exceptions and interrupts that occur while executing in the VMM context. The total switch preferably first saves the state before setting it according to the target context in order to facilitate the inverse operation.
The use of the total switch has significant consequences for the system. First, the host operating system (HOS) 340 is totally unaware of the existence of the VMM—only the driver 390, which implements the HOS side of the total switch, is aware. In other words, although the HOS and VMM are co-resident, both at the system level, their contexts, using this invention, can be completely separate, independent, and protected from each other. Consequently, no modifications are needed to the HOS, not even at its lowest Hardware Abstraction Layer (HAL). Here, "context" refers to the state that is set and restored during the total switch, for example, the state of the address space, the general-purpose registers, floating-pointer registers, privileged registers, interrupt vectors and hardware exception vectors. In
Second, the HOS 340 and VMM 360 have disjoint address spaces. The VMM can therefore take over the entire programmable virtual address space and is not limited by the address space of the host operating system. The VMM in turn will make this complete address space available to the virtual machine 320. As a result, execution on the virtual machine can directly use the memory management unit (MMU), which is included along with the processor in the given computer hardware 110. According to the invention, the VMM configures all the internal registers of the processor to match the requirements of the virtual machine, with no restrictions imposed by the host operating system. For example on a segmented architecture, the virtual machine can directly use the hardware segments.
Another consequence of the invention's use of the total switch is that the HOS 340 and the VMM 360 have different interrupt and exception entry points. The VMM completely takes over the machine and only voluntarily relinquishes control to the HOS.
Although the two contexts—VMM- and HOS-controlled—are independent of each other, they preferably cooperate for the allocation of machine resources. For example, the VMM preferably does not manage I/O devices. This greatly simplifies its design and implementation and improves its portability. Furthermore, preferably neither the VMM nor the virtual machine directly accesses I/O devices. Rather, the VMM uses an RPC to call the driver 390 in the HOS or the emulator 300 in the user-level process to initiate I/O requests.
Additionally, the VMM preferably redirects all I/O interrupts to the HOS. The VMM then calls the driver 390 in order to emulate the interrupt in the HOS context. The preferred interrupt-handling mechanism is described in greater detail below in connection with the discussion of
As yet another example of the preferred VMM-HOS cooperation, the VMM and the virtual machine access only the physical memory pages that have been allocated and locked down in memory by either the device emulator 300 or the driver 390. The VMM can then allocate a memory page by calling back into the HOS context. In this example, the VMM defers to the HOS the management of the physical memory resources. As an example of their cooperation, the VMM may release back to the HOS certain of the memory resources that are currently being used by the virtual machine 320 or the VMM.
Structure of the VMM
In general, the invention does not require the VMM 360 to be of any particular type. Indeed, this is one of the advantages of the invention. As long as the VMM incorporates the ability to access the user-level emulator 300 via the system-level driver 390, and to handle interrupts as described below, then any known VMM design may be used with in the invention. Nonetheless, by way of example,
There are two main known types of execution engines in a VMM: binary translation and direct execution. The concepts "binary translation" and "direct execution" are known in the field of computer system, as are techniques to design and operate the corresponding execution engines. Both engines rely on the same emulation modules 510, which emulate the various components of the virtual machine 320 (
Any conventional execution engine design may be implemented in the invention. For example, prior systems such as VM/370, DISCO, and Hypervisor are based exclusively on direct-execution techniques, and prior systems such as DAISY are based exclusively on binary translation techniques. This invention is independent of the choice of the execution engine.
The emulation modules 510 are selected using known design methods to be specific to the virtualized architecture. Examples of some common modules are illustrated in
As is mentioned above, the VMM 360 has its own set of interrupt vectors 404, which are separate from but parallel the interrupt vectors 402 of the host operating system. According to the invention, some exceptions are handled internally by the VMM, while others are forwarded to the virtual operating system (VOS 370—see
The applications 330 (
Emulation of devices is preferably divided into two components. Device emulation that does not require interaction with the physical devices of the system may remain as part of the VMM, as a VMM device emulation module 522, which may be designed in any known manner. Device emulations that do require such interaction are handled as described above by the user-level device emulator 300.
As is mentioned above, the HOS 340 is allowed, according to the invention, to manage resources such as the memory and devices, and to retain most of its normal functions and privileges, such as CPU scheduling. This is so even though the HOS and the VMM are both at the system level.
In general, there is no way for the system to transfer control directly from the VMM to the HOS, since they operate in different contexts, with disjoint address spaces. Recall that a "context" includes the state of all virtual address space, as well as the set of registers (including privilege registers), with all hardware exception and entry points. Nonetheless, there must be some mechanism that allows the system to operate in the VMM context when needed, while still allowing it to revert to the HOS context, for example, to allow a different VMM to be active.
The resetting of the IDTR 400 as part of the total switch is required since the HOS and the VMM are co-resident but operate in disjoint address spaces—an interrupt vector entry point specified in one context would be meaningless in the other context. The changing of the IDTR during the total switch has at least two advantages: First, the HOS (specifically, its interrupt handlers) does not need to be modified to accommodate the VMM—exceptions that occur while the VMM is executing will be processed directly by VMM-specific handlers. Second, this separation also leads to a substantial performance advantage, as the VMM consists of customized, low-overhead handlers without any operating system overhead.
In order to realize these advantages, the VMM and VM according to the invention share the same address space, and the IDT is stored as a part of the VMM's portion of the address space. To understand how the invention accomplishes this, note that device drivers—such as the invention's "Trojan Horse" driver 390—even in most protected systems operate at the same privilege level as the HOS itself and can set the IDTR and IDT. According to the invention, therefore, the IDT 404 for the virtual machine monitor 360 (that is, for each VMM) is loaded by the driver 390 into the VMM's address space, with entry points into the VMM itself.
For example, on an Intel x86, if the memory mappings between the HOS and a VMM were to be completely disjoint, that is, if they had completely distinct contexts, then there would be no way for the processor to get back on the instruction path in the other context once it got out of it. To overcome this, the invention provides for a cross page in the memory, which is a page in memory that is identical, beginning at the same linear address, in both (or, for multiple VMMs, all) contexts. The cross page contains known instruction sequences (specific to the given hardware processor) that change the address space and direct the processor to its next instruction. This cross page only needs to be mapped temporarily in the VMM context's address space, just before the total switch to the HOS, and just after the control returns to the VMM. The VMM uses known techniques to first save the mapping that exists at the address of the cross page before mapping the cross page. The inverse operation restores the mapping before resuming the execution of the virtual machine.
Note that the VMM cannot simply operate in the HOS context—it is necessary for the VMM to get essentially complete control of the system; otherwise, the HOS might begin to carry out its own procedures and defeat the entire reason for having a VMM. This invention makes this possible through implementation of the concept of "co-residency," which means not only that both the HOS and VMM are present at the system level, but also that each is able to operate with complete functionality, with fully maintained but completely separate contexts.
Several differences between the invention and known systems can now be appreciated. For example, most conventional virtual machine monitors and emulators are monolithic. In other words, most known VMM run without a host operating system (such as the VMM/370, Hypervisor, DISCO and DAISY systems), and most machine emulators run entirely at user-level (such as the SimOS system).
The invention also differs significantly from machine emulators for the MacOS, such as the VirtualPC and RealPC systems. The inventors believe, for example, that these systems are also monolithic. In any case, however, the MacOS is an operating system that does not offer any protection and does not clearly separate application code from system code.
As for the Disco system, it re-uses some of the known Silicon Graphics' IRIX device drivers. A modified version of IRIX initializes the machine and then loads the Disco VMM, which then takes over the machine. Unlike the co-resident system according to the invention, the Disco VMM manages both the processor and the main memory of the machine. It returns to the IRIX context only to call the low-level device-specific drivers. Unlike this invention, the DISCO system does not rely on a user-level device emulator, nor on the HOS to manage resources Moreover, unlike this invention, the modified version of IRIX cannot be used as a general-purpose operating system, since it does not control resources.
The legacy virtual machine monitors from Microsoft are integrated as part of Windows95 and Windows NT. The implementation of this legacy VMM in general is tightly integrated with the operating system. In contrast, the implementation according to the invention is portable, requires only a simple extension (the driver 390) of the operating system (which can even be uninstalled when unused) and supports a full VMM.
The Linux DOSEMU system is a legacy 8086 VMM that runs DOS on top of the Linux operating system. It is implemented partially at user-level, and uses an Intel x86-specific system call of Linux to set up the processor in the v-8086 mode. This system calls returns to the user-level VMM on every exception that occurs while the processor is in v-8086 mode. The system-level component of DOSEMU runs as an integral part of the DOS operating system.
In sum, unlike existing architectures, this invention, in its preferred embodiment, is built around a three-component system (user-level device emulator 300, driver 390, and co-resident virtual machine monitor 360) that runs even on a processor with a protected host operating system 310. Examples of such protected operating systems include UNIX and Microsoft NT. These operating systems all clearly separate user-level applications from the operating system by running applications in user mode. Furthermore, the invention includes the total switch, which saves and restores all the processor's state data, including the privileged registers, disjoint address spaces, and the interrupt dispatch table. The use of the total switch is the primary feature of the invention that enables the novel concept of co-residence between a host operating system and a VMM.
Note that the VMM and the device emulator may be coded and implemented using known techniques. As is discussed above, emulators and VMMs are known. Other than as described below, this invention does not relate to the design of the VMM and device emulator as such, since these will vary according to the machine in which the invention is to be incorporated; indeed, according to the invention, different VMMs may be co-resident in the same computer. Rather, one of the principal points of novelty of the invention is the manner in which the VMM, which is co-resident with the HOS at the system level, is able to communicate with the user-level emulator via the low-level driver 390, which is downloaded into the HOS.
Example of VM Device Request with Total Context Switching
Refer now to
Referring to
The VMM 360 then sets all parameters required for the I/O request and initiates the request by passing it via the driver 390 (path B) to the user-level device emulator 300 (path C). The parameters will be predetermined according to convention, and form the arguments of the RPC.
The device emulator 300 then uses the API 392 offered by the HOS 340 to emulate the I/O request, that is, to read or write the disk sectors from the corresponding virtual disks 380. The call to the API is shown as path D, which call is passed in the conventional manner (path E) to the appropriate device driver 382 within the HOS 340. To complete the operation, the HOS will in certain cases request an I/O operation from the corresponding physical device 380 (path F).
When the physical device 380 completes its operation, for example, retrieving a requested portion of a file, it typically interrupts the processor by issuing an external interrupt request (IRQ). Using an IRQ, the much faster central processing unit (CPU) system does not need to suspend other operations while waiting for the slower I/O device to complete its task. Rather, the IRQ acts as a "ready" signal from the I/O device. At this point (unless interrupts are presently masked), the hardware processor dispatches to the interrupt vector specified by the IDT. If the processor is currently executing in the HOS total context, then the processor dispatches to the IDT 402 of the HOS 340 (path G). It then processes the interrupt in the conventional manner, accessing the IDT 402, to get the corresponding entry point in the handler (path H), which then passes conventional signals such as acknowledgement and transfer initiation signals to the device driver 382 (path J). The device driver 382 then begins transfer of the requested data to the device emulator 300 (path K), which in turn passes the data via the driver 390 (path L) to the VMM 360 (path M). The VMM then transfers the requested data to the VM 320 (path N) as if it were the I/O device itself. The data is thus passed back along the reverse path and is made available to the originally calling application, which will never "know" that the actual memory access took place in a different context.
If the processor is currently executing in the VMM total context, then the VMM interrupt handler 395 intercepts the IRQ (path G*) and performs an RPC to the driver 390, which then emulates (by executing an appropriate conventional instruction sequence) the external interrupt in the HOS (path P). Effectively, the HOS 340 handles the interruption as though the processor were previously executing in the downloadable driver 390 when it in fact occurred while executing in the VMM total context—as is discussed above, the driver 390 sets the interrupt vectors to those of the VMM context.
Recall that, upon sensing the IRQ signal (via a predetermined pin) from the device 380, the hardware processor accesses the interrupt descriptor table register IDTR 400 to get the address of the IDT to be used for handling the interrupt. The IDTR can be set by routines at system level such as the VMM (via the driver 390) or by the HOS itself. According to the invention, interrupts that occur when running in the context of the VMM are handled by interrupt handlers in the VMM. Similarly, all interrupts that occur while executing in the HOS context are handled by existing interrupt handlers in the HOS. The operation of the total context switch in this invention is thus symmetrical.
As part of the total switch, the IDTR is changed to point to the IDT of the current sub-system (here: HOS or VMM). The total switch routine uses known techniques to ensure that no interrupts occur during the switch.
This example is another illustration of how the VMM according to the invention is able to remain completely "invisible" to the HOS by "hiding" behind the driver 390. In effect, by emulating the interruption when the system is in the VMM context, the HOS handles the I/O request as normal, but the system is prevented from reentering the HOS context until the driver 390 reestablishes it through resetting the IDT to that of the HOS context. In other words, in the VMM context, interrupts are handled according to the IDT 404 in the VMM (path G*), although the hardware will continue to act as if the interrupt had been handled via the IDT 402 in the HOS (path G).
The invention is not restricted to use in architectures in which a register such as the IDTR 400 is incorporated into the hardware processor, or in which such a register can be accessed and changed by software. For example, in certain architectures, the address of the IDT is hard-wired in the processor or is otherwise assumed to be constant. In these cases the predetermined address is the equivalent of the IDTR described above, but is inaccessible to the driver or the VMM. In such architectures, the invention implements interrupt forwarding not by selectively setting and changing the IDTR, but rather by storing the contents of the previously "active" IDT and then writing the currently "active" IDT at the predetermined address.
Note that because the HOS 340 actually manages the resource (in this case, the device 380), it can do so at its full normal speed, in its own context, and that both the VMM and the HOS can operate at the faster system level. The HOS views the emulator 300 as just another device with a driver, albeit one that uses up a very large amount of time (since the VMM calls pass through it). Indeed, the emulator 300 uses so much time that the HOS itself is effectively turned into the slave of the emulator (and thus VMM) as long as the VMM is active, that is, as long as the system is operating in the VMM context.
The co-residence of a HOS and a VMM does not require any modification of the HOS, but it does require some cooperation with the VMM. Specifically, the HOS must retain the ability to manage the resources of the system, including the scheduling of the processor(s), and the allocation of the memory. In the example of memory, the VMM must access only pages of memory that the HOS has allocated to either its corresponding device emulator 300 processor or the driver 390. These pages must be allocated and "locked down" in memory with the guarantee that the HOS will not attempt to reclaim them to use them for another purpose.
In the example of the processor, the VMM must bound the time that it executes in its total context by an amount corresponding to the scheduling granularity. For example, by performing an RPC to the user-level device emulator 300 with some known bounded rate, the VMM voluntarily releases the processor, allowing the HOS to schedule other applications running on the HOS, or other VMMs. This voluntary release of the processor can be implementing by performing an RPC on every external timer interrupt. Since the HOS programs the timer interrupts, it dictates their frequency.
In the preferred embodiment of the invention discussed below, the driver 390 acts as a simple "gate" to pass calls from the VMM 360 to the device emulator 300, as well as implementing the context switch. The driver 390 can therefore be made very simple. In one working implementation of the invention, for example, the device emulator 300 comprised around 30,000 lines of programming code and the VMM 360 needed about 55,000 lines of code. The driver, however, required less than 2,000 lines of code. This configuration leads not only to simplicity, but it also improves portability and generality of the system according to the invention. It is not, however, the only possible embodiment of the invention.
In this working implementation, the VMM is capable of running all major operating systems (Microsoft DOS, Windows 3.1, Windows 95, Windows 98, Windows NT, Linux, and Unix) for the Intel x86 architecture in a virtual machine. The implementation also contains versions of the device emulator and the driver for two distinct host operating systems: Windows NT and Linux. As an illustrative example of the independence of the HOS and the VMM, the identical VMM is capable of co-residency with either a Windows NT or a Linux HOS.
To the extent that the HOS allows calls that cross the driver API 394, then the system-level emulator 702 may be designed to take advantage of this possibility to speed up the system by reducing the number of necessary crossings of the application API 392. This potential increase in speed, however, has its costs. First, the code that must be downloaded into the HOS becomes much larger and more complex. Second, the system is much less portable and general, since it is much more closely tied to the particular HOS.
In the preferred embodiments of the invention, the driver 390 is downloaded into the HOS 340. This provides for the greatest possible flexibility, portability and generality, but it is not strictly necessary according to the invention. Instead, the driver 390 may be pre-loaded into or even made an integral part of the HOS. This might be desirable, for example, if the producers of the HOS expect their customers to want to use this invention to run one or more VMMs at system level, co-resident with the HOS.
Refer once again to
Patent Citations
Non-Patent Citations
Referenced by
Legal Events
Original Image


text:
Showing 1-25 of 82 results
KV331 Audio Synthmaster Player for iPad$9.994.5 stars
Overall, SynthMaster Player is a preset-packed, fun experience.
Midimux and Audiomux$6.995 stars
Positive Grid Bias FX$29.994.5 stars
Quality amp and effects app for your iPad that's packed with tonal options.
UVI BeatHawk$4.994 stars
touchAble 34.5 stars
The new touches make the third gen of touchAble an all-round winner.
Korg Module$40.004 stars
Yonac ToneStack4 stars
db Audioware Flying Haggis4 stars
There might only be one amp, but it's capable of a wide range of sounds.
PositiveGrid BIAS4.5 stars
Sugar Bytes Egoist for iPad$30.004.5 stars
Patchworks Conductr4.5 stars
Arturia iProphet$9.994.5 stars
It's great fun, it does an amazing impression of the real thing (you even get ...
Liquid Sonics Mobile Convolution$9.994 stars
iMusicAlbum AltiSpace$6.994.5 stars
AltiSpace makes for a superb add-on to any mobile DAW at a very fair price ...
VirSyn Tera Synth$19.994.5 stars
IK Multimedia AmpliTube Orange for iPad$14.994 stars
Positive Grid Final Touch$19.995 stars
Liine Lemur 5$24.994.5 stars
Kymatica Sector$8.994.5 stars
Sector is engrossing, beautiful, wild and a fine addition to the iPad music studio.
Korg Gadget for iOS$40.005 stars
If you have an iPad buying Korg Gadget is a no-brainer. If you don't, maybe ...
Sugar Bytes Effectrix iPad Edition$18.004 stars
Cakewalk Z3ta+ for iPad$20.004.5 stars
Z3TA+ is immediately one of the best synths on iPad - just as it is ...
Wolfram Franke Stroke Machine$20.004.5 stars
Arturia iSEM$9.994.5 stars
Sugar Bytes WOW2 for iPad$14.995 stars
Apart from the fact that it's not running as a plugin within a DAW, the ...
Virsyn Cube Synth$20.004.5 stars
A synth of serious importance - both musical and academic - this is up there ...
Liine LiveControl 2 for iPad5 stars
Waldorf Nave$19.994.5 stars
At this price, it's a total steal for any iPad musician. Now, how about a ...
Sugar Bytes Turnado$19.994.5 stars
A few tiny control niggles aside, Turnado on iPad is every bit as good as ...
Propellerhead Software Thor for iPad$14.994.5 stars
Thor sounds just as good as its bigger sibling, and its ability to share patches ...


text:
Cinnamon Raisin Challah French Toast
0 comments | Leave Comment
Cinnamon Raisin Challah French Toast
Why settle standard when you can have super deluxe? Transform your breakfast with cinnamon raisin challah French toast.
- Prep Time : 15 min min
- Ready Time : 15 min
- 6 extra-large eggs
- 1 1/2 cups low-fat milk
- 1 teaspoon cinnamon sugar
- 1/2 teaspoon pure vanilla extract
- 1 large loaf cinnamon raisin challah
- unsalted butter
- vegetable oil
- fresh berries, if desired
- Preheat the oven to 250 degrees F.
- In a large shallow bowl, whisk together the eggs, milk, cinnamon sugar and vanilla.
- Slice the challah in 3/4-inch thick slices. Soak as many slices in the egg mixture as possible for 5 minutes, turning once.
- Heat 1 tablespoon butter and 1 tablespoon oil in a very large saute pan over medium heat. Add the soaked bread and cook for 2-3 minutes on each side, until nicely browned.
- Place the cooked French toast on a sheet pan and keep it warm in the oven. Fry the remaining soaked bread slices, adding butter and oil to the pan as needed.
- Serve sprinkled with fresh berries, if desired.
Contributed by: Quick & Kosher, JAMIE GELLER


text:
Quotes & Info
|IDCC > SEC Filings for IDCC > Form 8-K on 18-Jun-2014
|All Recent SEC Filings
Other Events
On June 13, 2014, the Administrative Law Judge ("ALJ") issued an Initial Determination ("ID") in the United States International Trade Commission's ("ITC" or "Commission") Investigation No. 337-TA-868 brought against ZTE and Nokia (the "868 Investigation").
In the ID, the ALJ found that no violation of Section 337 of the Tariff Act of 1930 ("Section 337") has occurred in connection with the importation of 3G/4G devices by ZTE or Nokia, on the basis that the accused devices do not infringe the asserted claims of InterDigital's U.S. Patent Nos. 7,941,151 (the "'151 patent"), 7,190,966 (the "'966 patent"), or 7,286,847 (the "'847 patent").
In concluding that the accused devices do not infringe the asserted claims in the '966 and '847 "power ramp-up" patents, the ALJ's decision hinged on the construction of one patent claim term related to a claim term that InterDigital believes the Commission misconstrued in its decision in the previous 337-TA-800 investigation (the "800 Investigation") regarding the same family of patents. InterDigital has appealed that claim construction from the 800 Investigation to the U.S. Court of Appeals for the Federal Circuit (the "Federal Circuit"). InterDigital believes it has a very strong appeal based on a favorable prior ruling from the Federal Circuit related to this claim term on both the '966 and '847 patents, a favorable decision from the U.S. District Court for the District of Delaware involving this claim term in these same patents, and the Commission's own decision in connection with the remand proceeding in investigation No. 337-TA-613 (the "613 Investigation") dealing with these patents.
The ALJ also determined that, except for Claim 16 of the '151 patent, none of the asserted patents were invalid. The ALJ further determined that InterDigital did not violate any FRAND obligations, a conclusion also reached by the ALJ in the 800 Investigation. Additionally, the ID recognized that both InterDigital's licensing and research and development programs satisfy the economic criteria of the Section 337 domestic industry requirement, confirming numerous prior rulings by the Commission in InterDigital ITC investigations as well as by the Federal Circuit in affirming the Commission's domestic industry conclusions in the 613 Investigation.
InterDigital intends to seek review by the Commission of the adverse portions of the ID and, if necessary, by the Federal Circuit.


text:
Author of the Month
To sign up to the Graham Hancock newsletter mailing list, please click here.
The wild swings in weather that are expected to become commonplace as the planet gets warmermore frequent and severe droughts, followed by drenching rainschange ecosystems in a way that awaken and expedite the transmission of once dormant diseases.
Back to Previous...
Go to News Desk...
Enjoy the newsdesk? Please tell others about it:Tweet
G+. Site design by Amazing Internet Ltd, maintenance by Synchronicity. Site privacy policy. Contact us.
Dedicated Servers and Cloud Servers by Gigenet. Invert Colour Scheme / Default


text:
Jump to content
|Last action by
|How much do you inflate your tires...tire spec or vehicle spec? in The Neobahn
|My car's stolen first time in Milestones and Achievements
|Save 41% off a SKEYE Nano Drone via Neowin Deals in Front Page News
|PS4 and Xbox One resolution / frame rate discussion in Gamers' Hangout
|Windows 10 Insider Preview in Microsoft Beta (Windows 10)
Posted 06 May 2013 - 15:59
Posted 14 May 2013 - 16:22
Posted 14 May 2013 - 20:39
It runs it all, Cinnamon, MATE, everything.
Posted 14 May 2013 - 20:50
I'm not sure what's goin on with arch to be honest. It was crappy for a bit, then they made it quite stable, and seems like it's gone down hill again. Did a fresh install yesterday, now I can't get cinnamon to load via startx. X just shuts down (no errors or anything). However if I load stock X desktop I can then run cinnamon via xterm and it will load up.
Currently doing another re-install to see if the issue persists.
Posted 14 May 2013 - 20:52
Installed it in Virtual Box. Install went okay, took me a bit to realize that it doesn't generate the .xinitrc file so I couldn't figure out why it kept booting gnome-shell. Got that all fixed. Found that it doesn't have cinnamon 1.8 available just 1.6 which means the new nemo isn't available either. Using the minty theme seems to freeze cinnamon.
Also I cannot figure out how to enable dark themes for all apps. I can do it via gnome-tweak-tool in Arch but no option in debian.
Posted 14 May 2013 - 20:52
Well.. unless you did something to prevent it, you should have gnome 3.8 libs and files and cinnamon wont run with them. Thats why Cinnarch distro was discontinued and the creator made a gnome 3 distro instead. I really liked Cinnarch
Posted 14 May 2013 - 21:49
You're not the only one. I can't get fecking audio CDs to mount in any distro I try! Linux has really been testing my patience lately...


text:
Anthony Antonacci
Anthony Antonacci spent two seasons at Illinois in 2012 and '13. He became a defensive graduate assistant for the 2013 season after serving as the team's recruiting/operations graduate assistant in 2012. He assisted outside linebackers coach Al Seamonson, working primarily with the LEO (linebacker/end option) position.
Prior to joining the Fighting Illini staff, Antonacci served as defensive line and strength and conditioning coach at Lake Park High School in Roselle, Ill., in the 2011 season. He helped mentor three All-Upstate Eight Conference selections that season and contributed to a three-win turnaround from the previous year.
Before his season at Lake Park, Antonacci was the defensive line coach at North Central College in 2010, helping the Cardinals to a third-place finish in the nation in total defense. He guided Valente Garza to D3Football.com third-team All-America honors, who helped the Cardinals lead the CCIW and rank fifth nationally in sacks.
A 2009 magna cum laude graduate of Northern Illinois, Antonacci played defensive line for three seasons before moving to fullback in 2008. He helped the Huskies to appearances in the 2006 Poinsettia Bowl and the 2008 Independence Bowl.
Antonacci and his wife, Samantha, were married in July 2013.
Updated June 2014


text:
Medical Centers
Health & Tourism
City Destinations
Free Quote
Contact Us
By Treatment
Choose a Treatment
Addiction Treatment
Alternative Medicine
Cancer Treatment
Chronic Diseases
Cosmetic/Plastic Surgery
Executive Healthcheck
Eye/Lasik Care
Fertility Treatment
General Medicine
General Surgery
Heart Care/Surgery
Infertility | IVF
Laparoscopic Surgery
Medical Spa Treatment
Obesity/Bariatric Surgery
Orthopedic/Knee Surgery
Radiology/CT Scans
Skin Care
Spine Care | Surgery
Sports Medicine
Stem Cell Therapy
Vascular Surgery
Weight Loss Program
By City
Select city
Agua Prieta
Bahia de Kino
Cuidad Obregon
Puerto Peńasco
San Luis Rio Colorado
Santa Ana
Best Dental Packages in Sonora
Cosmetic Surgery
Gastric Surgery Packages
Ultimate Eye-Care Package
Beautiful Magdalena
Blissful Agua Prieta
Enjoying Hermosillo
Finding Peace in Navojoa
Getting lost in Caborca
Guaymas, Sonoran Jewel
Hit Beaches in Rocky Point
Huatabampo, Gem of Sonora
Old & New in Cuidad Obregón
Peace & Quiet in San Carlos
Best Dentals in Sonora
Comprehensive Eye Treatments
Cosmetic Surgery in Hermosillo
Luxury Spa Treatment
Destination Place : San Luis Rio Colorado
Destinations :
San Luis Rio Colorado
San Luis Rio Colorado
Treatment Centers in Sonora | Cheap Hospitals San Luis Rio Colorado | Affordable Surgery Packages Sonora | Medical Tourism Sonora | Health Tourism Center San Luis Rio Colorado | Best Surgery Hospitals Mexico | Affordable Treatment San Luis Rio Colorado | Top Surgery San Luis Rio Colorado | Best Clinics in Sonora | Things to do in San Luis Rio Colorado | Tourist destinations San Luis Rio Colorado | Dining in San Luis Rio Colorado | Accommodation in San Luis Rio Colorado
San Luis Rio Colorado
San Luis Rio Colorado - Sonoran Bliss
San Luis Rio Colorado is located at the very northwestern tip of the Mexican State of Sonora, adjacent to Baja California and the southern border of eastern California and western Arizona. Because of its location, San Luis Rio Colorado has long been a favorite border crossing, accessible and affordable tourist destination and a jumping off point for all points south into Mexico and Central America.
Its location, offering desert scenery and fun in the sun and sand along the beautiful northern coastline of the Sea of Cortez, also known as the Gulf of California, the city is literally a gateway to a number of adventures, activities and things to do. Designated as the fourth largest city in the state, San Luis Rio Colorado is located in the Sonoran desert a few minutes' drive south of Yuma, Arizona.
A Glimpse of San Luis Rio Colorado
Since the early 1900s the city has been known for its warmth, beautiful scenery, and friendly atmosphere for travelers not only from California and Arizona, but international destinations, served by the San Luis Rio Colorado Airport. The nearby General Rodolfo Sánchez Toboada International Airport, located near Mexicali, grants easy access to the area.
Because it's so close to the United States border and literally shares history and culture not only with Mexico, but Arizona and Baja California, the city offers a blend of American and Mexican amenities, accommodations, restaurants and services. Nestled under the brilliant blue desert skies and rich with palm trees and green lawns, San Luis Rio Colorado is literally an oasis in the midst of the desert. Beautiful sunsets and sunrises and glorious ocean breezes are just a few of the things visitors from around the world enjoy.
A variety of activities are available for a outdoor enthusiasts visiting the area, including jeep and dune buggy tours on nearby sand dunes, water adventures such as jet skiing, water skiing, deep sea fishing, snorkeling and just laying along any point of her miles of white, sandy beaches, or enjoying the music, and arts and crafts of locals available for sale in a variety of shopping, street side, and vendor locations.
Enjoy exploring the number of restaurants in your stop at San Luis Rio Colorado, serenaded by mariachi bands, surrounded by the rich colors of tapestries and crafts available for sale. Holiday shopping is a snap in San Luis Rio Colorado, and gives travelers a variety of options to choose from.
Nearby Mexicali offers some of the most popular destinations for Americans seeking affordable dental and medical care in Mexico. Semite to the border has increased its popularity, as has its proximity to the coastal tourist attractions at Puerto Peñasco. Residents from Phoenix, Tucson, Yuma, San Diego and Los Angeles make regular trips down San Luis Rio Colorado for affordable getaways, vacations, parties and social events.
Accessing Healthcare in Sonora
One of the most popular hospitals in the state of Sonora is the Sonora Hospital, certified by the JCI (Joint Commission International) and the CSG, known as the General Health Council operated by the Ministry of Health in Mexico. The Joint Commission International is an accrediting institution that examines and accredits medical facilities and providers based on their quality of care, patient services, equipment, techniques and procedures. In Mexico, a facility must be certified by the General Health Council before it can be accredited by the Joint Commission International, offering superlative quality and excellence in services and care.
Traveling to San Luis Rio Colorado
Visitors arrive in the city from destinations north by taking U.S. Interstate 8 east toward Mexicali or Yuma, and west on Interstate 8 from Phoenix, Tucson or Casa Grande. Just minutes south of the border, San Luis Rio Colorado is a convenient and easily accessible gateway for coastal destinations south including Mazatlan and Guadalajara. Be prepared to show your passport when visiting any destination south of the border.
Follow Us On:
About Us
Free Quote
Refer a friend
Contact Us
Terms and conditions
Privacy Policy


text:
In ND, golf hazards include the weather
May 8, 2013 at 7:35 pm in The Dickinson Press
FARGO The women's golfers at North Dakota State say they're often pegged as members of a winter sports team, given the fact that most of them are measured in the 5-foot-10 range and look like they haven't seen the sun. Turns out they haven't.
Continue Reading


text:
HSBC "lift" by Grey London
Agency: Grey London
Rating: 5.0
By Matthew Chapman, campaignlive.co.uk, Wednesday, 25 July 2012 12:10PM
BT complained to the Advertising Standards Authority (ASA) that the ad with Bolt claiming "I want everyone to say bye-bye to buffering" was misleading because it implied Virgin Media customers would not experience buffering.
Virgin Media defended itself by claiming there were numerous causes of buffering, some of which they had no control over, and added that the script in the ad was "puffery".
However, the ASA banned the ad because it believed the creative, by DDB, would be interpreted as an objective claim that Virgin's 30Mb broadband service would give customers a buffering-free service.
The ad had already stopped running before this week's ruling was made. Virgin Media has hit out at the ruling because of the whimsical nature of the advert.
A Virgin Media spokesperson said: "When one of the world's leading athletes dresses up as a world famous entrepreneur, complete with stuck-on blond beard and space helmet, and says he wants everyone to wave bye-bye to buffering this should not be taken as a definitive claim that no Virgin Media customer will ever experience buffering ever again."
Also this week the ASA has banned an ad on Virgin Media's website over a claim about the time it took to download a movie and an album via its 60Mb service.
The ASA banned the ad because the download times given did not take into account peak hours, when the speed of the service is halved.Follow @mattchapmanuk
This article was first published on campaignlive.co.uk
Before commenting please read our rules for commenting on articles.
If you see a comment you find offensive, you can flag it as inappropriate. In the top right-hand corner of an individual comment, you will see 'flag as inappropriate'. Clicking this prompts us to review the comment. For further information see our rules for commenting on articles.
Agency: Grey London
Rating: 5.0


text:
By The Raleigh Telegram
RALEIGH – According to the Raleigh Police Department, a couple living in a downtown home in the historic Oakwood neighborhood were victims of a home invasion, shooting, and attempted rape early Monday morning. Police say that after the suspects fled, the men were apprehended after a car chase and crash where one of the suspects was injured.
The Raleigh Police Department says the incident began at around 3:15am on Monday morning when they received a 911 call reporting a shooting.
Police say that a female victim who was inside of a home at 519 East Lane Street had escaped the house after at least two suspects had entered the home. The unidentified woman told police that her husband, age 34, had been shot inside the home by the suspects.
According to police, a chase then ensued after officers arrived on the scene and saw the getaway car leaving.
"Shortly after the first responding police units reached the scene, other officers observed a silver car traveling at a high rate of speed on Raleigh Boulevard," said Raleigh Police spokesman Jim Sughrue in statements to the media on Monday. "Officers followed that vehicle and attempted to conduct a traffic stop."
Sughrue said that the driver of the silver car tried to evade police and eventually crashed.
"When the vehicle refused to pull over, officers pursued it until the vehicle crashed at Wilmington and Rush streets and its occupants jumped from the car and fled on foot," added Sughrue. "Additional police units responded to the crash scene, and two subjects were detained when they were located a short time later."
Arrested after the crash were two suspects, who identified as being involved in the break-in at the house. Police say they were charged with a litany of crimes related to the incident.
Police identified the men who were arrested as Jahaad Tariem Allah Marshall, age 26, and Shabar Master Marshall, age 16. The two men are brothers.
Jahaad Marshall was charged with one count of first degree burglary, two counts of first degree kidnapping, one count of attempted murder, one count of attempted first degree rape, and one count of possession of a firearm by a convicted felon
Shabar Marshall was charged with one count of first degree burglary, two counts of first degree kidnapping, one count of attempted murder, and one count of first degree forcible sex offense.
The shooting victim and his wife were taken to the WakeMed hospital where she was treated and released. The shooting victim was still being treated for his injuries and was still under medical care as of Tuesday. In addition, police said that Jahaad Tariem Allah Marshall was injured in the car crash and was also taken to the hospital.
The 911 call was made at a neighbor's house where the woman ran after escaping the two suspects.
"Someone broke in her home, they tried to rape her, "and they shot him, said an unnamed neighbor in a 911 call. "We don't know if the shooters are there or not."
The 911 operator then asks to speak to the woman who ran out of the house, asking her to slow down and describe what happened.
"We woke up and they were there standing in our bedroom and we gave them everything we had but it wasn't enough," said the woman. "Then one of them took me out of the bedroom and he took a gun out and then he started to sexually assault me."
The woman said that the suspect's started to hit her husband and then she ran downstairs and that she ran out of the house screaming.
The victim said that the two suspects were wearing all black, had masks on and were wearing hoodies. The 911 operator said that there were four or five officers in the neighborhood and the call ends when a police officer arrived at the neighbor's home.
The incident which took place in the upscale Oakwood historic neighborhood has many people rattled in the downtown area. Local people posted notices of the crime on Facebook as the nature of the alleged home invasion and sexual assault were so shocking. ::
Article Posted: Tuesday, January 8th, 2013.


text:
Community Emergency Response Team (CERT) Training Opportunity Begins Soon
The Stutsman County Local Emergency Planning Committee (LEPC), in conjunction with the North Dakota League of Cities, is sponsoring a citizen-based emergency response program called Community Emergency Response Teams or CERT. CERT training is free and is open to all citizens 18 years or older.
CERT is a training program that educates citizens about the hazards they face in their community and trains them in lifesaving skills. The Stutsman County CERT training program is administered in five components consisting of four evening classes and one disaster simulation activity. The components include fire safety, light search and rescue, medical triage, emergency family preparedness, and disaster psychology.
Class will be held at the James Valley Career and Technology Center Jamestown, on October 2, 4, 9, 11 and 15 from 6:00 p.m. – 10:00 p.m. To enroll call 701-252-8841 or 910 12 Ave NE Jamestown. Close date for the enrollment is Monday September 24, 2012. Attendance to all classes is required for certification.
For additional information, contact Jerry Bergquist, Stutsman County Emergency Manager at 701-252-9093.


text:
What is Lisya Theme?
Lisya is an powerful WordPress Theme that perfectly suits your Portfolio, Creative, Blog or Photo Gallery Website. Auto complete search, Video Self Hosting, Liquid Layout, Unimited Sidebar make this theme beautiful.
Some Key Feature of "Lisya Theme"
- WordPress 3.3+ compatible
- Advanced Theme options
- Support major browsers
- Autocomplete Search
- Left Mega Menu
- Multilevel navigation
- Fluid Layout
- Custom widgets
- Twitter widget
- Gravatar
- Custom post type
- Unlimited sidebars
- Unlimited widget-areas in Sidebars
- Contact forms
- Shortcodes and Shortcode Builder
- Blog Page
- Portfolios page
- Google Fonts: Webfonts with Google fonts
- Cufon
- PrettyPhoto
- Google Map
- Unlimited Styles and Colors
- SEO Optimization
- Demo Content with sample data (import .xml) and sample icon with ilustrator files
- Clean Design
- Video (youtube, vimeo, self hosting video)
- Automatic Image Resizing
- Ready for translation (.po / .mo files included)
- and much more…
Update Changelog (Because work is never done…)
1.1 Version
- Added Documentation to setting Main Menu
- added option to change border color
- fixed Main Menu overlapping issue
- added footer widget in Homepage
- fixed mega menu options
1.0 Version
- Initial release


text:
|Page: 1 of 7
|Sort By:
Essaouira, Morocco Bed & Breakfasts - Dar Liouba is much more than a charming guesthouse, it is a place where you will feel at home. A house where conviviality, enchantment and an atmosphere of relaxation reign, with a bright architecture.
Essaouira, Morocco Bed & Breakfasts - Enjoying you breakfast surrounded by sea-gulls on our terrace overviewing the medina and the Atlantic is an unforgettable moment. 9 cosy rooms and 1 suite (some of them with seaview) equipped in typical traditional moroccan style are waiting for you.
, Morocco Sight-Seeing Tours -
Essaouira, Morocco Hotels & Resorts - Luxury hotel on the sea front with its own private beach and outdoor heated swimming pool.
Essaouira, Morocco Hotels & Resorts - Overlooking the ocean, at the heart of the new Mogador resort, the Sofitel Essaouira Mogador Golf Spa gives you the chance to rediscover wide open spaces.
Essaouira, Morocco Youth Hostels - Dar Al Bahar, the house by the sea in arabic, is located in the heart of the medina...
Essaouira, Morocco Hotels & Resorts - Housing a Total of 14 Guest Rooms, This Charming Hotel Welcomes Guests Into a Lobby With a Hotel Safe, Currency Exchange Facilities and a Cloakroom. Guests
Essaouira, Morocco Youth Hostels - Located in the middle of the médina, near to the stores of craft industry and the typical restaurants of the souks, the riad Jemalhi will allure you by his authenticity and its reception.
Essaouira, Morocco Hotels & Resorts - Built in 2008, the Hotel is Entirely Renovated With All the Details To Provide Guests With Comfort. In This Haven of Peace, the Cordial 24-Hour Reception
Essaouira, Morocco Youth Hostels - Essaouira Hostel is perhaps the nicest hostel you will ever stay in! Welcome to 'Hotel California'; you can check in any time, but you will never want to
|Page: 12 | 3 | 4 | 5 | 6 | 7 |
Essaouira, Morocco Vacations - Travel guide to Essaouira, Morocco accommodations and vacation packages. Visit Essaouira, Morocco for getaways and adventure travel. Plan your Essaouira, Morocco vacation today.
|Page: 12 | 3 | 4 | 5 | 6 | 7 |


text: DX-Ball is a shareware computer game for the PC first released in 1996 by Michael P. Welch. The game, an updated version of an earlier series of Amiga games known as Megaball, is patterned after classic ball-and-paddle arcade games such as Breakout and Arkanoid. It became a massive cult classic in the Windows shareware gaming community during the late 1990s. A level editor was made available as well.