Wednesday, September 16, 2009

Ramen noodle Recipes

9 Unique Ramen Noodle Recipes

Try one these quick and easy pasta dinner dishes tonight

9 Unique Ramen Noodle Recipes

Photo: © Charles Schiller

Many of us have consumed the incredibly inexpensive noodle known as ramen—whether in the form of an easy-to-make soup packet or as a perfect-for-work lunch complete with handy foam cup. But, did you know this light-on-your-wallet instant pasta can also be used in a variety of recipes? WD has rounded up nine quick dinner recipes that include this Asian cuisine staple—all done in 35 minutes or less. From the cheesy Skillet Noodle Pizza to the soul-satisfying Asian Meatball Soup, any one of these dishes will remind you just how resourceful ramen noodles can be!

Ramen Noodle Recipes:

1. Peanut Ramen Noodle Salad

2. Asian Noodles with Shrimp

3. Coconut Curry Shrimp

4. Asian Meatball Soup

5. Vegetable Primavera

6. Asian Shrimp and Noodle Soup

7. Skillet Noodle Pizza

8. Ricotta Frittata

9. Warm Chicken and Cabbage Salad

Thursday, September 10, 2009

Obama: Health Care Reform Outline

 clipped from www.whitehouse.gov

The Obama Plan: Stability & Security for all Americans


"It will provide more security and stability to those who have health insurance. It will provide insurance to those who don't. And it will lower the cost of health care for our families, our businesses, and our government."

– President Barack Obama


More Stability and Security

  • Ends discrimination against people with pre-existing conditions. Over the last three years, 12 million people were denied coverage directly or indirectly through high premiums due to a pre-existing condition.  Under the President's plan, it will be against the law for insurance companies to deny coverage for health reasons or risks. 
  • Limits premium discrimination based on gender and age. The President's plan will end insurers' practice of charging different premiums or denying coverage based on gender, and will limit premium variation based on age. 
  • Prevents insurance companies from dropping coverage when people are sick and need it most.  The President's plan prohibits insurance companies from rescinding coverage that has already been purchased except in cases of fraud.  In most states, insurance companies can cancel a policy if any medical condition was not listed on the application – even one not related to a current illness or one the patient didn't even know about. A recent Congressional investigation found that over five years, three large insurance companies cancelled coverage for 20,000 people, saving them from paying $300 million in medical claims - $300 million that became either an obligation for the patient's family or bad debt for doctors and hospitals.
  • Caps out-of pocket expenses so people don't go broke when they get sick.  The President's plan will cap out-of-pocket expenses and will prohibit insurance companies from imposing annual or lifetime caps on benefit payments. A middle-class family purchasing health insurance directly from the individual insurance market today could spend up to 50 percent of household income on health care costs because there is no limit on out-of-pocket expenses.
  • Eliminates extra charges for preventive care like mammograms, flu shots and diabetes tests to improve health and save money. The President's plan ensures that all Americans have access to free preventive services under their health insurance plans. Too many Americans forgo needed preventive care, in part because of the cost of check-ups and screenings that can identify health problems early when they can be most effectively treated. For example, 24 percent of women age 40 and over have not received a mammogram in the past two years, and 38 percent of adults age 50 and over have never had a colon cancer screening.
  • Protects Medicare for seniors. The President's plan will extend new protections for Medicare beneficiaries that improve quality, coordinate care and reduce beneficiary and program costs.  These protections will extend the life of the Medicare Trust Fund to pay for care for future generations. 
  • Eliminates the "donut-hole" gap in coverage for prescription drugs.  The President's plan begins immediately to close the Medicare "donut hole" - a current gap in its drug benefit - by providing a 50 percent discount on brand-name prescription drugs for seniors who fall into it.  In 2007, over 8 million seniors hit this coverage gap in the standard Medicare drug benefit.  By 2019, the President's plan will completely close the "donut hole".  The average out-of-pocket spending for such beneficiaries who lack another source of insurance is $4,080.

If You Don't Have Insurance

Quality, Affordable Choices for All Americans

  • Creates a new insurance marketplace – the Exchange – that allows people without insurance and small businesses to compare plans and buy insurance at competitive prices.  The President's plan allows Americans who have health insurance and like it to keep it.  But for those who lose their jobs, change jobs or move, new high quality, affordable options will be available in the exchange.  Beginning in 2013, the Exchange will give Americans without access to affordable insurance on the job, and small businesses one-stop shopping for insurance where they can easily compare options based on price, benefits, and quality. 
  • Provides new tax credits to help people buy insurance. The President's plan will provide new tax credits on a sliding scale to individuals and families that will limit how much of their income can be spent on premiums.  There will also be greater protection for cost-sharing for out-of-pocket expenses.
  • Provides small businesses tax credits and affordable options for covering employees. The President's plan will also provide small businesses with tax credits to offset costs of providing coverage for their workers.  Small businesses who for too long have faced higher prices than larger businesses, will now be eligible to enter the exchange so that they have lower costs and more choices for covering their workers.
  • Offers a public health insurance option to provide the uninsured and those who can't find affordable coverage with a real choice.   The President believes this option will promote competition, hold insurance companies accountable and assure affordable choices. It is completely voluntary.  The President believes the public option must operate like any private insurance company – it must be self-sufficient and rely on the premiums it collects. 
  • Immediately offers new, low-cost coverage through a national "high risk" pool to protect people with preexisting conditions from financial ruin until the new Exchange is created.  For those Americans who cannot get insurance coverage today because of a pre-existing condition, the President's plan will immediately make available coverage without a mark-up due to their health condition. This policy will offer protection against financial ruin until a wider array of choices become available in the new exchange in 2013.

For All Americans

Reins In the Cost of Health Care for Our Families, Our Businesses, and Our Government

  • Won't add a dime to the deficit and is paid for upfront.  The President's plan will not add one dime to the deficit today or in the future and is paid for in a fiscally responsible way.   It begins the process of reforming the health care system so that we can further curb health care cost growth over the long term, and invests in quality improvements, consumer protections, prevention, and premium assistance.  The plan fully pays for this investment through health system savings and new revenue including a fee on insurance companies that sell very expensive plans.
  • Requires additional cuts if savings are not realized. Under the plan, if the savings promised at the time of enactment don't materialize, the President will be required to put forth additional savings to ensure that the plan does not add to the deficit.
  • Implements a number of delivery system reforms that begin to rein in health care costs and align incentives for hospitals, physicians, and others to improve quality.  The President's plan includes proposals that will improve the way care is delivered to emphasize quality over quantity, including:  incentives for hospitals to prevent avoidable readmissions, pilots for new "bundled" payments in Medicare, and support for new models of delivering care through medical homes and accountable care organizations that focus on a coordinated approach to care and outcomes.
  • Creates an independent commission of doctors and medical experts to identify waste, fraud and abuse in the health care system.   The President's plan will create an independent Commission, made up of doctors and medical experts, to make recommendations to Congress each year on how to promote greater efficiency and higher quality in Medicare.  The Commission will not be authorized to propose or implement Medicare changes that ration care or affect benefits, eligibility or beneficiary access to care.  It will ensure that your tax dollars go directly to caring for seniors.
  • Orders immediate medical malpractice reform projects that could help doctors focus on putting their patients first, not on practicing defensive medicine.  The President's plan instructs the Secretary of Health and Human Services to move forward on awarding medical malpractice demonstration grants to states funded by the Agency for Healthcare Research and Quality as soon as possible.
  • Requires large employers to cover their employees and individuals who can afford it to buy insurance so everyone shares in the responsibility of reform.   Under the President's plan, large businesses – those with more than 50 workers – will be required to offer their workers coverage or pay a fee to help cover the cost of making coverage affordable in the exchange. This will ensure that workers in firms not offering coverage will have affordable coverage options for themselves and their families.  Individuals who can afford it will have a responsibility to purchase coverage – but there will be a "hardship exemption" for those who cannot.
Get Clipmarks - The easiest way to email text, images and videos you find on the web.
Sent with Clipmarks

Monday, September 07, 2009

That Late Night Snack: Worse than you Think

 clipped from www.sciencedaily.com

That Late-night Snack: Worse Than You Think


ScienceDaily (Sep. 7, 2009) — Eat less, exercise more. Now there is new evidence to support adding another "must" to the weight-loss mantra: eat at the right time of day.


A Northwestern University study has found that eating at irregular times -- the equivalent of the middle of the night for humans, when the body wants to sleep -- influences weight gain. The regulation of energy by the body's circadian rhythms may play a significant role. The study is the first causal evidence linking meal timing and increased weight gain.


"How or why a person gains weight is very complicated, but it clearly is not just calories in and calories out," said Fred Turek, professor of neurobiology and physiology in the Weinberg College of Arts and Sciences and director of the Center for Sleep and Circadian Biology. "We think some factors are under circadian control. Better timing of meals, which would require a change in behavior, could be a critical element in slowing the ever-increasing incidence of obesity."


The findings could have implications for developing strategies to combat obesity in humans, as the United States and the world battle what has been called an "obesity epidemic." More than 300 million adults worldwide are obese, including more than a third of American adults.


Details of the obesity study, which was led by Turek, will be published online Sept. 3 by the journal Obesity.


"One of our research interests is shift workers, who tend to be overweight," said lead author Deanna M. Arble, a doctoral student in Turek's lab. "Their schedules force them to eat at times that conflict with their natural body rhythms. This was one piece of evidence that got us thinking -- eating at the wrong time of day might be contributing to weight gain. So we started our investigation with this experiment."


Simply modifying the time of feeding alone can greatly affect body weight, the researchers found. Mice that were fed a high-fat diet during normal sleeping hours gained significantly more weight (a 48 percent weight increase over their baseline) than mice eating the same type and amount of food during naturally wakeful hours (a 20 percent increase over their baseline). There was no statistical difference between the two groups regarding caloric intake or the amount of activity.


Over a period of six weeks, both groups of mice were allowed to eat as much high-fat diet as they wanted during their daily 12-hour feeding phase. (Much like many humans, mice have a preference for high-fat food.) Since mice are nocturnal, the 12-hour feeding phase was during the day for those fed during normal sleeping hours and during the night for those fed during naturally wakeful hours. Food was not provided during the other 12 hours of their day.


Our circadian clock, or biological timing system, governs our daily cycles of feeding, activity and sleep, with respect to external dark and light cycles. Recent studies have found the body's internal clock also regulates energy use, suggesting the timing of meals may matter in the balance between caloric intake and expenditure.


The researchers next plan to investigate the molecular mechanisms behind their observation that eating at the "wrong" time can lead to weight gain.


In addition to Turek and Arble, other authors of the paper are Joseph Bass, Aaron D. Laposky and Martha H. Vitaterna, all from Northwestern.

Get Clipmarks - The easiest way to email text, images and videos you find on the web.
Sent with Clipmarks

Saturday, September 05, 2009

Bonobo Live at the Fox Theatre, Boulder, CO

iTunes Visualizer Keyboard Shortcuts

 clipped from lifehacker.com



  • + and -: Increase or decrease the intensity (brightness) of the particles; multiple presses further increase or decrease the intensity.
  • A and S: Add or Subtract particles to the visualizer. You can make the visualizer as complex (or sparse) as you wish.
  • R: Reset the intensity and particle count to their default values.
  • E: When in nebula mode (press N), this greatly accentuates the nebula clouds, making them very easy to see. (If you've used the M key to change modes, you may find that the nebula clouds aren't visible; it seems they're only used in certain modes.)
Get Clipmarks - The easiest way to email text, images and videos you find on the web.
Sent with Clipmarks

Things Only a Republican Could Believe

 clipped from www.reddit.com

Things Only a Republican Could Believe:

  • Parents who don't want their children to pray in school are Anti-American zealots -- parents who don't want their children to listen to a speech by the President of the United States telling them to work hard and get good grades are noble patriots.

  • Peacefully demonstrating against the country starting an international war is treason -- showing up with automatic weapons to protest healthcare reform is democracy at its finest.

  • Any government official with a desk job should have every action scrutinized -- any government official with a badge and a gun should never be questioned or disrespected. At all. Ever.

  • Questioning the legitimacy of an election because the "winner" was selected by the Supreme Court is sour grapes -- questioning the legitimacy of an election because the winner (by the largest number of votes in American history) is really a Kenyan born Muslim despite all evidence to the contrary is being a vigilant American.

  • Lying about a blowjob is an impeachable offense -- lying about a war is no big deal, really.

  • Investigating a shady land deal involving the First Lady is a matter of National Identity -- investigating the use of torture at the direction of the Executive Branch is a partisan witch hunt.

  • Executing Japanese officers for waterboarding prisoners during WWII shows that we have the moral high-ground on human rights -- waterboarding prisoners of our shows that we have the moral high-ground on human rights.

  • Sitting two rows in front of Jane Fonda in a 1970 anti-war rally is an OUTRAGE! Shaking Saddam's hand in 1983...meh, not so much.

  • Anyone who questions the president during a time of war is giving aide and comfort to the enemy and should be deported...unless the president in question has a (D) next to their name in which case you should undermine them at every turn even if you have to routinely make shit up to do it.

  • Socialism, Marxism, Communism and Fascism are all interchangeable words that mean pretty much the same thing.

  • Anyone who abuses drugs should be locked up indefinitely...unless they are a popular Republican radio host in which case they need your prayers as they recover from the illness of addiction.

  • Health Insurance companies have your best interests in mind and anyone who thinks otherwise is trying to turn America into the Godless heathen nation of Sweden where EVERYONE in the country dies (eventually).

  • Obama is an atheist communist muslim who attended a radical christian church.

  • Believing that human activity could impact the global environment is crazy talk -- believing that an invisible man in the sky personally told George Bush to invade Iraq to fulfill Biblical prophecy is logically sound.

  • The verdict is still out on evolution -- but Jesus Christ returning in our lifetimes is a pretty much a given.

  • The media are unquestionably biased against Republicans -- Talk Radio, The Washington Times, The Weekly Standard, The Wall Street Journal, Rightwing Blogs, Fox News and NewsCorp are not part of the media.

  • The government should have no part in regulating multi-national corporations as they make decisions that impact the lives of millions of people -- government should regulate individuals by determining who they can marry, what kind of intercourse they can have, what they can smoke, how to manage their pregnancy and how to proceed with end of life decisions.

  • Communicating with hostile nations is a stab in the back to our great nation -- Reagan communicating with the USSR during the Cold War was Political Genius.

  • Iran is a mortal threat to our nation and anyone who attempts to talk to them is traitorous scum -- selling weapons to Iran and then funneling the money to start wars in South America is clearly in our National interest.

  • George Bush kept the nation safe after 9-11 (NOTE: the Anthrax attacks, the DC Sniper and Hurricane Katrina don't count. Also, the fact that 9-11 happened on his watch despite receiving a security briefing specifically warning of the attack doesn't count either.)

  • Social Security, Meidcare, public schooling, public libraries, fire departments, police departments and the US Military are as American as Apple Pie -- universal healthcare is ZOMGDEATHPANELSOCIALISM!!

  • George W Bush is a regular 'ole Texas rancher just like you and me despite the fact that he was born in Connecticut, attended two Ivy League schools, bought the Crawford ranch just before running for president, sold it immediate after leaving office and is terrified of horses.

  • The two guys at the center of the Watergate and Iran-Contra scandals are trustworthy voices in discussions of current national policy and should be taken at face-value.

Get Clipmarks - The easiest way to email text, images and videos you find on the web.
Sent with Clipmarks

Friday, September 04, 2009

Slipstream Driverpacks into a Sysprep Image

 clipped from forum.driverpacks.net
DriverPacks.net Forum

  •  » [HOWTO] Using DriverPacks w/ Sysprep (Updated for BASE 7.04 and later)

  • UPDATED for DriverPack BASE 7.04 and later.  I'm starting a new thread because the title of the thread it was under was regarding a specific error and a tangent evolved into these instructions.

    NOTE: This HOW TO assumes you are proficient with sysprep.  If not, I recommend you read through this first.

    1) Download the latest version of DriverPack BASE (7.05.2 at time of writing) and whatever DriverPacks you need.

    2) Extract BASE to a folder by running the .exe you downloaded (example: DPs_BASE_7052.exe)

    3) In the folder you extracted BASE to, open the 'bin' folder.  Copy DPsFnshr.ini and extract DPsFnshr.7Z to C:\ on the computer you'll be running Sysprep on.

    4) Inside of the BASE 'bin' folder, open the 'wnt5_x86-32' folder.  Copy ROE.exe to C:\sysprep, and extract DevPath.exe from M2.7z to C:\ on the computer you'll be running Sysprep on.

    5) Extract your DriverPacks with either 7-zip or WinRAR.  If you have WinRAR integrated into your shell you can just control-click the Packs you want to select them, then right-click on one and choose "Extract Here".  Make sure that they are all merged into the same folder structure under the 'D' folder (D\C, D\G, etc).  You should also have a set of files ending with wnt5_x86-32.ini.  These contain the various exceptions that DPsFnshr.exe reads when it runs. 

    6) Move extracted DriverPacks ('D' folder) and wnt5_x86-32.ini files to C:\ on the computer you'll be running Sysprep on.
    6a) If you are slipstreaming DP_Graphics_A, create a dummy (Notepad) file in C:\.  Name it ATICCC.ins if you want the Catalyst Control Center or ATICCP.ins if you want the Catalyst Control Panel installed when Radeon hardware is detected.  The file can be blank as DPsFnshr.exe just looks for the file name.  DPsFnshr.exe deletes the .ins file when it is finished running.
    6b) If you want, you can modify the extracted driver packs to remove hardware you don't need.  If you do, remember to move the modified driver pack to D\3\ (i.e. D\3\C, D\3\CPU, etc).  If you want DPsFnshr.exe to run as intended (do to paths in the wnt5_x86-32.ini files), though, I would leave things like the DriverPack Graphics A unmodified.

    7) Open a Command Prompt and run

    Code:

    C:\DevPath.exe C:\D

    and then

    Code:

    C:\makePNF.exe C:\D

    NOTE: Since you are loading your DevicePath with DevPath.exe, you can leave out the OemPnPDriversPath entry (under the [Unattended] section) in your sysprep.inf file.  OemPnPDriversPath has a 512 characters limit, but DevPath.exe gets around this by writing directly to the registry entry that OemPnPDriversPath gets loaded into by sysprep.

    8) Open C:\DPsFnshr.ini in Notepad or Wordpad.  Since we aren't actually running BASE we have to change the configuration for the Finisher manually.  Generally, you will only need to edit the KTD and KTDlocation variables at the very top.  If you do not want KTD enabled set:

    Code:

    KTD = "false"

    If you want to KTD, put 'paths:' and then a list of folders in D you want to keep.  Even if you want to keep all the drivers, I would still recommend specifying them individually due to the "double D" and Desktop.ini bugs in Finisher.  For example, in my configuration, I want to keep all of the drivers.  I have a D\3 folder when I've put my 3rd party and modified driver packs, and a D\G folder that contains an unmodified Driver Pack Graphics A.  So my KTD line looks like:

    Code:

    KTD = "paths:D\G;D\3"

    KTDlocation tell Finisher where to move the D folder to if you have KTD enabled.  For example, I move my drivers to C:\WINDOWS\Options\Drivers so my KTDlocation line is:

    Code:

    KTDlocation = "%SystemRoot%\Options\Drivers"

    9) Edit c:\sysprep\sysprep.inf and add the following lines under the [Unattended] section:

    Code:

    UpdateInstalledDrivers = Yes DriverSigningPolicy = Ignore

    10a) (optional) If you want the Mass Storage drivers that come with XP added to your sysprep.inf then add the line:

    Code:

    [SysprepMassStorage]

    to the very end of your sysprep.inf.  Then, run

    Code:

    c:\sysprep\sysprep.exe -bmsd

    10b)If you want to include the drivers in DriverPack MassStorage, then you will have to added them to the [SysprepMassStorage] section manually by opening up the various mass storage drivers' inf files and copying the vendor and device codes with a path to the inf file.  There is a script that can automate the process for you here, but it doesn't seem to be perfect yet.

    For example, all of the machines I am deploying my image on are based on Intel chipsets (IBM/Lenovos, and HPs).  So, I can get away with only adding the Intel mass storage drivers.  As of DriverPack MassStorage 7.06.2, this is the section I add at the begining of [SysprepMassStorage] after running sysprep -bmsd

    Code:

    PCI\VEN_8086&DEV_2652&CC_0106 = C:\D\M\IN\1\iaahci.inf PCI\VEN_8086&DEV_2653&CC_0106 = C:\D\M\IN\1\iaahci.inf PCI\VEN_8086&DEV_27C1&CC_0106 = C:\D\M\IN\1\iaahci.inf PCI\VEN_8086&DEV_27C5&CC_0106 = C:\D\M\IN\1\iaahci.inf PCI\VEN_8086&DEV_27C3&CC_0104 = C:\D\M\IN\1\iastor.inf PCI\VEN_8086&DEV_2652&CC_0104 = C:\D\M\IN\1\iastor.inf PCI\VEN_8086&DEV_24DF&CC_0104 = C:\D\M\IN\1\iastor.inf PCI\VEN_8086&DEV_25B0&CC_0104 = C:\D\M\IN\1\iastor.inf PCI\VEN_8086&DEV_2681&CC_0106 = C:\D\M\IN\2\iaahci.inf PCI\VEN_8086&DEV_2821&CC_0106 = C:\D\M\IN\2\iaahci.inf PCI\VEN_8086&DEV_2822&CC_0104 = C:\D\M\IN\2\iastor.inf PCI\VEN_8086&DEV_27C6&CC_0104 = C:\D\M\IN\2\iastor.inf PCI\VEN_8086&DEV_2682&CC_0104 = C:\D\M\IN\2\iastor.inf PCI\VEN_8086&DEV_2829&CC_0106 = C:\D\M\IN\3\iaahci.inf PCI\VEN_8086&DEV_2922&CC_0106 = C:\D\M\IN\3\iaahci.inf PCI\VEN_8086&DEV_282A&CC_0104 = C:\D\M\IN\3\iastor.inf PCI\VEN_8086&DEV_2680 = C:\D\C\I\xp\ESB2ide.inf PCI\VEN_8086&DEV_269E = C:\D\C\I\xp\ESB2ide.inf PCI\VEN_8086&DEV_244B = C:\D\C\I\xp\ich2ide.inf PCI\VEN_8086&DEV_244A = C:\D\C\I\xp\ich2idem.inf PCI\VEN_8086&DEV_248B = C:\D\C\I\xp\ich3ide.inf PCI\VEN_8086&DEV_248A = C:\D\C\I\xp\ich3idem.inf PCI\VEN_8086&DEV_24CB&CC_0101 = C:\D\C\I\xp\ich4ide.inf PCI\VEN_8086&DEV_24CA&CC_0101 = C:\D\C\I\xp\ich4ide.inf PCI\VEN_8086&DEV_24C1&CC_0101 = C:\D\C\I\xp\ich4ide.inf PCI\VEN_8086&DEV_24D1&CC_0101 = C:\D\C\I\xp\ich5ide.inf PCI\VEN_8086&DEV_24DB&CC_0101 = C:\D\C\I\xp\ich5ide.inf PCI\VEN_8086&DEV_25A2&CC_0101 = C:\D\C\I\xp\ich5ide.inf PCI\VEN_8086&DEV_25A3&CC_0101 = C:\D\C\I\xp\ich5ide.inf PCI\VEN_8086&DEV_2651&CC_0101 = C:\D\C\I\xp\ich6ide.inf PCI\VEN_8086&DEV_2652&CC_0101 = C:\D\C\I\xp\ich6ide.inf PCI\VEN_8086&DEV_2653&CC_0101 = C:\D\C\I\xp\ich6ide.inf PCI\VEN_8086&DEV_266F = C:\D\C\I\xp\ich6ide.inf PCI\VEN_8086&DEV_27C0 = C:\D\C\I\xp\ich7ide.inf PCI\VEN_8086&DEV_27C4 = C:\D\C\I\xp\ich7ide.inf PCI\VEN_8086&DEV_27DF = C:\D\C\I\xp\ich7ide.inf PCI\VEN_8086&DEV_2820 = C:\D\C\I\xp\ich8ide.inf PCI\VEN_8086&DEV_2825 = C:\D\C\I\xp\ich8ide.inf PCI\VEN_8086&DEV_2828 = C:\D\C\I\xp\ich8ide.inf PCI\VEN_8086&DEV_2850 = C:\D\C\I\xp\ich8ide.inf PCI\VEN_8086&DEV_2922 = C:\D\C\I\xp\ich9ahci.inf PCI\VEN_8086&DEV_2923 = C:\D\C\I\xp\ich9ahci.inf PCI\VEN_8086&DEV_2920 = C:\D\C\I\xp\ich9ide.inf PCI\VEN_8086&DEV_2921 = C:\D\C\I\xp\ich9ide.inf PCI\VEN_8086&DEV_2926 = C:\D\C\I\xp\ich9ide.inf PCI\VEN_8086&DEV_2928 = C:\D\C\I\xp\ich9ide.inf PCI\VEN_8086&DEV_292D = C:\D\C\I\xp\ich9ide.inf PCI\VEN_8086&DEV_292E = C:\D\C\I\xp\ich9ide.inf

    11) Open a Command Prompt and run

    Code:

    C:\sysprep\ROE.exe 937

    This tells Windows to run C:\DPsFnshr.exe on the next reboot.  I found that using [GuiRunOnce] in sysprep.inf to run DPsFnshr.exe resulted in the dreaded desktop.ini bug.  Using ROE.exe to create a RunOnceEx entry for DPsFnshr.exe does not have this issue.  DO NOT REBOOT BEFORE THE NEXT STEP OR DPsFnshr.exe WILL RUN!

    12) Run sysprep.exe and reseal

    BONUS: If your image is to be deployed on both single and multicore systems, then I'd highly recommend you check out MySysprep.  It can detect a multicore CPU and switch HALs during minisetup.


    Note: I was able to eliminate a lot of my sysprep/imaging issues (including minisetup looking for hdaudbus.sys in the wrong place) by NOT using RyanVM's update packs.  In fact, I recommend only using nlite to slipstream SP2 and setup the Unattended section when building a disc.  Since you're creating an image anyways, it doesn't hurt to run Windows update manually, and be 100% sure everything is install 'the Microsoft way'.
    Get Clipmarks - The easiest way to email text, images and videos you find on the web.
    Sent with Clipmarks

    Sysprep Guide

     clipped from www.vernalex.com

    Guides: SysPrep Guide

    The purpose of this guide is to discuss the abilities and usage of the Microsoft System Preparation Tool (SysPrep) tool that Microsoft provides in order to make replication of their operating system easier. It is an invaluable tool that can be used in combination with other tools like Symantec Ghost, Acronis True Image and the now defunct PowerQuest Drive Image (since it was acquired by Symantec in 2005). The guide focuses on the Windows XP SP2 version of SysPrep, but the guide can easily be applied to other versions of SysPrep on Windows XP, Windows 2000, Windows Server 2003 and even to Windows NT4.

    This is a general introduction to SysPrep and it explains the background information such as what SysPrep is, what SysPrep does, and where you can get SysPrep.
    The generalized instructions chapter will show you the general steps to go from Windows install to deployable image. There is a lot of background information to SysPrep and without understanding it all then you will have a much harder time deploying SysPrep.
    One of the important steps that you need to take before you apply SysPrep is to use a hardware abstraction layer (HAL) that will be the most compatible so that your image won't freeze on the boot after applying the image on certain computers.
    The purpose of this chapter is to show you how you are supposed to configure your sysprep.inf answer file. I provide several examples and I believe these are often the most helpful.
    One of the most problematic areas of SysPrep seems to be the lack of understanding in the configuration of mass storage devices. This section will provide flexible instructions for deploying an image that works on all controller cards and chipsets so that you can avoid the blue screen of death that causes your computer to reboot after using SysPrep.
    This chapter is useful when your template computer is setup, you have configured your sysprep.inf, your driver stores are all set and so on and so forth. The execution chapter focuses on how to run SysPrep and tips on running it in the most streamlined ways.
    When you get stuck then this is the place to go. I try to provide answers to the most common questions that I receive through email, and from the most common problems that I experienced when learning SysPrep. If you do not see an answer to one of your problems in here then please email me and ask it because chances are if you're having a problem then there are hundreds or thousands had, have or will have the same problem.
    I have put together this video and I highly recommend that you watch it after you have a general idea on how to use SysPrep. It will step through the various phases of downloading, installing and configuring SysPrep, and it will do this while I explain what the steps mean. It is my hope that this video will put it all together for you so that it finally makes perfect sense. If you are extremely confused by SysPrep then you may want to begin with the video guide and then end with the video guide.
    Get Clipmarks - The easiest way to email text, images and videos you find on the web.
    Sent with Clipmarks

    WDS Tutorial

     clipped from www.edugeek.net
    After a bit of fiddling, I've sorted out a method to deploy XP in my computer lab using WDS in Native mode.

    The main steps are:
    [hr]

    1) Configure WDS server to capture and deploy images.
    2) Configure client to boot from network card and sysprepping XP for automatic installation.
    3) Capturing sysprepped XP image from client to WDS server.
    4) Deploying sysprepped XP image from WDs server to client.

    Here's a look at step one:
    [hr]

    1. Configure WDS server to capture and deploy images.
    Install WDS on your Windows 2003 Server. On Windows Server 2003 SP2, go to Start > Control Panel > Add or Remove Programs > Add / Remove Windows Components > Windows Deployment Services. If you are using Server 2003 SP1, you have to install RIS first, then upgrade to WDS using the Windows AIK.

    Download the Windows Automated Installation Kit (AIK). Windows (AIK).
    Burn the Windows AIK image file to a DVD with IMGBURN (free)
    or mount the Windows AIK .img file to a Virtual CD/DVD Drive.

    On the desktop create a folder called WDS temp to store the following 3 files:
    Right click on the Windows AIK disc and find the WinPE.Cab file and extract the F1_WINPE.WIM and F3_WINPE.WIM bootable files. We need these in order to capture an image from our base machine. Put those in the WDs temp folder.

    Next, insert the Windows Vista DVD and copy the boot.WIM file located in the “sources’ folder. Paste that file in the WDS temp folder.

    Start and Configure WDS

    1. On the Start menu, click Administrative Tools, and then click Windows Deployment Services.
    2. In the left pane of the Windows Deployment Services MMC snap-in, expand the server list.
    3. Click the server that you want to manage.
    4. If the server is not in the servers list, right-click the Servers node to add a server.
    5. In the Add Server(s) dialog box, click Another computer, and then browse to select the computer to manage.
    6. In the Add Server Warning dialog box, click Yes to add the server.
    7. Right-click the server that you want to manage, and click Configure Server to start the Windows Deployment Services Configuration Wizard.
    8. At the Welcome page, click Next.
    9. At the Remote Installation Folder Location page, click Next to accept the default location (C:\RemoteInstall).
    10. If the Microsoft DHCP service is on the server that is being configured as a Windows Deployment Services server, set DHCP Option 60 to PXEClient and set Windows Deployment Services to Do not listen on Port 67.
    11. On the PXE Server Initial Settings page, click Respond to all (known and unknown) client computers.
    12. Click Finish to complete the configuration.
    13. Clear the Add images to Windows Deployment Services now check box, then click Finish.

    Add the Boot Images F1_WINPE.WIM and F3_WINPE.WIM to WDS

    In the WDS control panel, right click the “Boot Images†folder and select “Add Boot Image†.



    Browse to the WDS temp folder on the desktop where you saved the F1_WINPE.WIM and F3_WINPE.WIM files.

    Add both images, the restart WDS and 2 new boot images will appear in the “Boot Images†folder. We will use the “Windows Vista PE (X86)†image.



    Create a Capture Boot Image for your XP machinesRight click the “Windows Vista PE (X86)†image and select “Create Capture Boot Image†. We will use this boot image to capture (transfer) the sysprepped XP image from the client to the WDS server.



    Name the capture image “XP Capture Boot Image†and save it to C:\RemoteInstall\CaptureBootImages (you’ll need to create the capturebootimages folder) and click Next.



    Import the XP Capture Boot Image into the WDS “Boot Images†folder.



    Browse to the CaptureBootImages folder and choose the “XP Capture Boot Image.WIM file you created previously. Click Next to add the image. When the image is added you will see it in the “boot images†folder.



    Import the boot.wim image into the WDS “Boot Images†folder. This image file is used for the DEPLOYMENT of images to client computers.

    In the WDS control panel, right click the “Boot Images†folder and select “Add Boot Image†. Browse to the WDS temp folder on the desktop and select the boot.wim image file. Click Next and name the file “XP Deployment Boot Image†. Click Next to add the image to the Boot Images folder.


    When the image is added you will see it in the “boot images†folder.




    Create an Image Group in the Install Images folder.


    Image Groups organize images into similar types. You must have at least one image group to upload images. In this example there are three groups, Administrative desktops, Computer lab desktops and Servers. Right Click on the Install Images folder and “Add Image group†.




    [hr]
    We are finished preparing the WDS server.


    You can see the rest of the steps to the tutorial on my website. I added the tutorial to help others get started with WDS and as guide to help myself remember how to do it since I only tend to image the lab once or at most twice a year.
    For the bandwidth challenged, note that there are several more screen caps.
    http://www.oakdome.com/lab/?page_id=78
    Get Clipmarks - The easiest way to email text, images and videos you find on the web.
    Sent with Clipmarks

    Tuesday, September 01, 2009