Toshiba A105 BIOS Recovery Process Questions

Hi!
Ive got a Toshiba Laptop A105-S4284, Model #: PSAA8U-0FH02K that froze while trying to flash the BIOS. Now, when I try to boot it up, it gets stuck in the same place it did during the flashing; on the Toshiba splash screen with the status bar at the bottom showing about 20% complete. Options available on this screen are: Press F2 for System Settings and F12 for Boot Menu. Pressing F2 results in a beep and the status bar is replaced with the text "Please Wait..." but nothing else happens no matter how long I wait. Pressing F12 doesnt do anything. Pressing ESC takes me to a screen that shows the typical system info -- Phoenix Technologies Version 6.00; Intel Calistoga CRB.T3A Reference BIOS; VERSION.MAK 1.53. It looks like its at least partially POSTing since it shows CPU, Cores, No TPM or TPM has a problem, and system RAM and stops there. I cant get into the BIOS and cant boot into Windows.
Ive read the posts on here regarding the BIOS Recovery Process and was hoping someone could provide some clarification for me, especially since Ive already waited a week with no reply on another tech support site forum. :-(
Anyways... Ive downloaded the Crisis Recovery.zip files to create a Recovery Disk and am trying to follow the instructions.
There are a bunch of files in the .zip and Im not sure exactly which files I need to have on the boot disk Im creating.
The files in the .zip are:
- crisboot.bin
- CRISDISK.BAT
- makeboot.exe
- minidos.sys
- phlash16.exe (actually PHLASH16 version 1.6.5.4)
- wincris.exe
- wincris.hlp
Ive downloaded the BIOS Update from Toshibas website for the A105-S4284. Which file do I need to rename to BIOS.WPH and add to my Recovery Disk directory? Do I want "s10gm600.rom" or "1988d600.ima"? I extracted the file from the bootable BIOS installation diskette (1988d600.exe) to get the 1988d600.ima file.
I ran wincris.exe and only the following files end up in the directory Ive designated for my Recovery Disk:
- BIOS.WPH
- MINIDOS.SYS
- PHLASH16.EXE
Do I need any of the other files from the original .zip?:
- crisboot.bin
- CRISDISK.BAT
- makeboot.exe
- wincris.exe
- wincris.hlp
If someone could provide some clarification on which files to use and most importantly, if those are the correct files for the laptop Im trying to fix. I think all the posts Ive read are for laptops newer than this one and it seems the secret to succeeding at recovering a BIOS is using the CORRECT files. Ive searched all over and cant find any posts from someone with an A100/A105 who has been able to do a BIOS Recovery from a CD, USB floppy or USB flash drive.
Is there ANY hope?
Thanks in advance for your time and assistance with this; its GREATLY appreciated. 
Sarah ;-) 

Hi Sarah,
I had the same thing happen to my A105 4094.  I've looked at some of the other blogs, but I'm not sure if I should try the corrective action they suggest.  Not sure how common the different models are. 
I'm going to keep trying to resolve this.  If I find something that works, I'll write again and let you know.  Please do the same for me and other A105 owners.
Thanks,
Jamie

Similar Messages

  • BIOS recovery process for HP systems with AMI BIOS?

    Hi,
    I'm trying to fix an HP a6718uk model PC which has an M2N78-LA motherboard and (I think) and AMI BIOS.  A BIOS update that came through HP Update has failed, and the machine will not boot.
    As it's out of warranty the HP Repair Centre want £200.00 to fix it, even though a simple BIOS recovery process should be sufficient - does anyone know the BIOS recovery process for these systems?   Everything I've read (not specific to these boards) says you should be able to put a BIOS update (called AMIBOOT.ROM) on either a floppy, CD, or USB memory stick, and boot holding down Ctrl-Home and it will perform the recovery, but I've not been able to get this to work successfully.  HP don't supply a standalone update so I've extracted the file from the BIOS update SP.exe on the HP support site.
    Any help would be most appreciated!
    Cheers,
    Andrew
    This question was solved.
    View Solution.

    Brilliant idea - I tried AMIBOOT.BIN and that didn't work, but then took the Hex Editor to the file - it's HPBIOS.ROM
    Renamed the file to HPBIOS.ROM and all now works.
    To recap for anyone reading the thread, this was from an HP machine with a corrupt AMI BIOS, to get it back, extract the ROM file from the SP.exe file from the HP website, rename it from VLE5.22 (or whatever the file is that ends in a numeric) to HPBIOS.ROM and copy onto a floppy diskette.   Put the floppy in the internal diskette drive (in my case a Sony OEM drive attached using a grey floppy ribbon cable) and boot the machine.  You may need to hold down Ctrl-Home, but not 100% sure.   After a long while the machine will give 4 or 5 beeps, and reset itself.  Once it's done that it will boot normally.
    Thanks for your help David - much appreciated.
    Cheers,
    Andrew

  • How do u creat BIOS recovery disk + nvidia firewall question.

    WooooHOoOOO....
    after re-formating a dozen times, busted SCSI config, messed up driver install, I FINALLY GOT this board working at 100%!!!
    This mobo powered through my entire DOOM 3 Odyssey to Hell NON-STOP without a SINGLE CRASH!! Definitely a good testament to this board's quality.
    Now for the final few noob question, how do I create a bios recovery disk just in case things happened.
    lastly... how do you properly setup the NV Firewall? After enabling it, none of the other computers in my network can see this computer with the MSI Board, so file and printer sharing all stops when the firewall is enabled.
    Anyone here has a walkthrough on the firewall?
    ONCE AGAIN...thanks to all who helped me!!!

    i havent got my nvidia firewall to work imma wait until they release better drivers for it but for creating the bios recovery disk i think if u use msi's live update it will ask u if u want to create one or not.

  • Satellite A105-S3611 Recovery DVD won't boot - reverts to HDD boot

    Satellite A105-S3611 Recovery DVD won't boot - reverts to HDD boot. 
    My laptop has had a virus but is now clean but has some lingering effects.  So I decided to use the Recovery and Applications/Drivers Media to reinstall the system to factory settings.  Pressing the "C" key at the Toshiba screen did not work to choose the boot divice but pressing F12 did work.  The problem is the system still boots using the hard disk.  I've gone into the boot process and changed the order of boot devices to make sure the CD\DVD drive is chosen first but it does not boot from the CD/DVD.  It looks like it begins to read the DVD but the boot process is not executed from there.
    Questions:
    1. Can I install the system using windows explorer to execute the autorun.ini on the CD/DVD?
    2. Is there another option for getting the system to install from the CD/DVD?
    Thank you in advance
    Roger

    I read somewhere on the forum that updating the BIOS may solve the problem.  So I updated the system BIOS from v1.40 to v2.0.  Then I reinserted the newly purchased recovery DVD and the boot process began with the DVD booting but ended with the message "WRONG MACHINE".
    I ejected the recovery DVD that I just purchased and inserted the recovery DVD that came with the machine.  This time the machine booted and installed the factory image of the operating system as it should have the first time.
    So I am now recovered and the machine works as it did originally.  So the moral of the story is you don't necessarily have to buy the new recovery DVD but just update the system BIOS and then try to use the recovery DVD that came with your machine. 

  • Problems with Satellite L775D-S730​5 System Recovery Process

    1.  Grandson accidentally erased 500GB internal hard drive. Recovery partition was not available.  Ordered, paid for and received Toshiba "SW Media-DVD-SATELLITE-L775-Windows 7 64 bit Home Premium-EN" recovery media.
    2.  While going through recovery process (3 times) to "Restore to Factory Out of the Box Settings" using Disk 1 of 4 - received "can't read from source file or disk" read errors from the following four boot related files:
    (a)  Boot64.WIM, Type: WIM File,  Size: 142 MB,  Date Modified: 11/3/11 12:28pm
    (b)  BCD,  Type:  File,  Size:  256 Kb,  Date Modified: 11/4/10 5:52pm
    (c)  Boot.SDI,  Type:  SDI File,  Size:  3.02 MB,  Date Modified: 11/4/10  6:18pm
    (d)  EFTSBoot,  Type:  MS-DOS Application,  Size:  4.00 Kb,  Date Modified:  11/4/10 5:52pm
    (e)  At end of Disk 1 recovery process received error - Toshiba Recovery Wizzard INITRECAREA.EXE - Application Error.  "The instruction at 0x75D5FF26 reference memory at 0x01D700.  The required data was not placed into memory because of an I/O error status of 0xc000009c."  The Recovery Process was terminated due to Error 9c.  Select (Finish).
    3.  Reported issue to Toshiba Support - who sent a new set of recovery media to verify if either defective recovery media or defective installed 500 GB hard drive.
    4.  Repeated recovery process (3 times) with new media set - had exact same results as above.  Assumed had internal hard disk problem according to Toshiba Support.
    5.  Ordered, received and installed new 1 Terabyte Toshiba 2.5 inch internal hard drive (PH2100U-1I54).  Reset BIOS to Default (F2, F9, F10) and system recognized new hard drive as MQ01ABD100.
    6.  Repeated recovery process (3 times each) with both sets of recovery media - had exact same results as above.
    7.  Reported issue to Toshiba Support and asked because obtained same "can't read boot related source file errors" on two sets of recovery media with two different hard drives - was there a possibility of defective recovery media, or some other problem?
    8.  Toshiba Support would not acknowledge and indicated could not send another recovery media set because had already sent two.  Also indicated new hard drive was probably improperly installed (because of configuration issues) and recommended seek local technical assistance.
    9.  Sought local technical assistance and was not able to recover system using Toshiba recovery media (said to be defective).  Verified sucessful installation of internal hard drive and no other laptop problems.
    10.  Able to re-install system using Windows 7 Professional installation CD, downloading YTD Toshiba BIOS and hardware drivers, and installing latest ATI video/graphics drivers.      

    I understand the issue you're having & realize that it's a frustrating experience going through this. Can't understand why it didn't work with the original hard drive, unless it had some bad sectors or possibly even bad RAM. The tech who checked it out would have (or should have) caught any RAM issues.
    However, on some systems, an extra DVD should be in the ordered recovery set in case a new or different size HDD is used, I had this experience with HP. Installed a 750GB WD Caviar Black in place of the OEM supplied 320GB Caviar Blue, my created recovery DVD's (3) wouldn't do the job. HP provided me a new set with the 4th DVD for $16. It worked. I didn't realize it until later, the ISO for that issue could have downloaded from the site. My fault for not checking.
    Makes me wonder if this was the case in your situation. This doesn't happen often, but when it does, that extra DVD is needed.
    http://h10025.www1.hp.com/ewfrf/wc/softwareDownloa​dIndex?softwareitem=pv-80183-1&cc=us&dlc=en&lc=en&​...
    At any rate, glad to hear that you got it working, though probably your complete utility package wasn't installed. More than likely enough to be OK though, some of these options are seldom used, & are simply using drive space, especially those with SSD's. I just clean installed Windows 8 Pro onto my Toshiba A665-S6086 & after using the Toshiba Windows 8 Upgrade Assistant to install the needed software (I chose all), it's the largest Windows 8 Pro install that I've done (after all updates/apps were installed). Usually less than 30GB is used, counting Office 2010 Pro Plus, this one is 38GB, was 44GB until the temp files & restore points except the last were deleted.
    Best of Luck,
    Cat

  • NEO-FSR (MS-7030) Corrupt BIOS recovery issues.

    I'm tempted to title this "What I did wrong when flashing the BIOS" but I think it's better just telling you my experience of using LiveUpdate3 to flash the BIOS from 1.x to 1.9.
    MS-7030 Neo-FSR
    The main mistake I made was trusting that the defaults for the applications were correct. This is most evident when I chose the Windows update process from LiveUpdate3. As I remember it when the BIOS update utility started an immediate button arose which said UPDATE. Not taking the time to review the screen to see what was not in focus and below the focus of the button I hit UPDATE. It erased my BIOS. And while it was erasing my BIOS I was thinking how odd it was that those boxes were not checked. They should have been. Oh well, the defaults should do. Right? Obviously not. I should have chosen all of the four available buttons on the left. When the boxes are not checked it CLEARS the BIOS and then says it UPDATES. It UPDATES nothing.
    If the utility will erase the BIOS when none of the boxes are checked the button should say ERASE BIOS! not UPDATE. The button should indicate the summation of chosen action. If none of the boxes are checked then ERASE BIOS! If some are checked indicate what's being changed.
    RULE: Don't click on the first button made available. Take a few minutes extra time to examining all the options on the screen that could impact your upgrade. Some options are hidden beyond the first obvious button.
    The second mistake was not knowing which BIOS I had. Before this problem occurred I paid no attention to the BIOS. I always take the defaults and never overclock. So I didn't really know which BIOS I had. In trying to remedy the problem I confused the AMI process of holding down CONTROL and HOME with the AWARD process. The AWARD process doesn't use this.
    The screens say AWARD. The sticker on the chip said PHOENIX. I thought they were different brands. But they are one in the same.
    RULE: Always know which brand BIOS you have. There are now two AMI and PHOENIX/AWARD.
    The third mistake I made was not knowing how to create a BIOS rescue disk. The LiveUpdate3 utility created the disk for me and I paid no attention to it. I should have examined the files to see what was being done for me.
    RULE: Always know the recovery process for your brand of corrupt or erased BIOS.
    My fourth mistake and related to the third was not knowing how to recover a corrupt or erased BIOS. The process is to insert a properly prepared  floppy, turn on the box and wait until it reads the floppy. I should get a BEEP. A splash screen comes up with a F1 or DEL option. If I do nothing a second text screen comes up with a basic BIOS configuration. I presume that I should be able to make a selection beyond by clicking on something on that screen. However being tired and confused I had the keyboard plugged into the mouse port when moving the box to a workable location. The keyboard won't work connected to the mouse port.
    I think the mobo is trying to work. I just need to get my ducks in a row with a properly prepared floppy and the keyboard plugged into the correct port.
    Questions:
    Does the keyboard even need to be plugged in? After waiting 2 to 5 minutes the instructions say the BIOS will read from the floppy. This seems to be happening very inconsistently. Sometimes once in five or six tries.
    Do I have to clear the CMOS on every try to recover? It seems the only way I can get the BIOS to read the floppy is to clear the CMOS first. That takes 15 to 30 minutes doesn't it?
    When the splash screen comes up should I hit F1 or DEL? The splash screen is visible for about 15 seconds. That's not enough time to read an unfamiliar screen, make a decision and press the correct key. Experienced users might breeze though it. New users are who have arrived at this difficult point are usually bewildered, confused and angry. They need more time.
    I'm still not sure I ever saw a proper and complete process of recovering a corrupt BIOS. I'll give it another shot tonight and report back later.

    Ammond98,
    RULE: Don't click on the first button made available. Take a few minutes extra time to examining all the options on the screen that could impact your upgrade. Some options are hidden beyond the first obvious button.
    You may also wish to read these:
    1- Award Phoenix amalgametion: http://www.award-bios.com/
    2- BIOS when & how to update: https://forum-en.msi.com/index.php?topic=76897.0
    3- DOS BIOS Flashing: https://forum-en.msi.com/index.php?topic=86257.0
    4- WinFlash Method: https://forum-en.msi.com/index.php?topic=84865.msg606175#msg606175
    5- BIOS Flashing sticky: https://forum-en.msi.com/index.php?topic=81017.0
    Questions:
    Does the keyboard even need to be plugged in? After waiting 2 to 5 minutes the instructions say the BIOS will read from the floppy. This seems to be happening very inconsistently. Sometimes once in five or six tries.
    Do I have to clear the CMOS on every try to recover? It seems the only way I can get the BIOS to read the floppy is to clear the CMOS first. That takes 15 to 30 minutes doesn't it?
    When the splash screen comes up should I hit F1 or DEL? The splash screen is visible for about 15 seconds. That's not enough time to read an unfamiliar screen, make a decision and press the correct key. Experienced users might breeze though it. New users are who have arrived at this difficult point are usually bewildered, confused and angry. They need more time.
    Above suggested reading will answer these questions.
    I'm still not sure I ever saw a proper and complete process of recovering a corrupt BIOS. I'll give it another shot tonight and report back later.
    Above suggested reading will answer these questions.
    A little reading, suggested above, will bring you right up to speed on BIOS flashing. Meanwhile try continuously hitting the Insert key while booting your system to see if it will go into "Safe Defaults" and allow you to get into BIOS to reset options. the  "DEL" key should be the one you need to press to get into BIOS Setup screen.
    Also recommend that you do not use liveupdate 3 for flashing your BIOS
    Good luck,

  • NB200-10G - recovery process has failed - Setenv.ini issue

    Hello, I have a problem with my netbook.
    I want to recovery my windows with bundled windows xp operating system in my harddisk, but this recovery process has been failed.
    On the Recovery GUI (RecoGUI) screen appear a message box and a message :
    "ERROR: Setenv file D:\Setenv.ini or X:\tools\Setenv.ini not found!"
    has written on it.
    then me tried to change the SATA Controller Mode in BIOS, from AHCI to Compatibility.
    But this change does'nt have effect.
    That error message still appear when I tried to recovery and i don't have a recovery disc.
    what should i do ?
    Thanks

    Thats pity mate
    Seems something went wrong with the HDD partition and HDD recovery procedure.
    From my point of view there is not much to do
    If the HDD recovery does not work, then you can install the OS only using an disk.
    Either you will use an Toshiba Recovery disk or a common Windows disk.
    Recovery disk can be ordered here:
    https://backupmedia.toshiba.eu/landing.aspx
    By the way; you will need an USB CD/DVD drive in order to install the OS from the disk.

  • Help Needed, Recovery Process

    Hi, This is just a inquiry on how recovery works. First, I'll just add I have a Satellite L500-ST2522. I've looked through the manual and haven't found any answers. I have just made recovery DVDs, and am expecting a new hard drive either tommorow or Monday. My question is on how these discs work (I've got 3-Rocovery discs, 1 Windows Recovery Environment(64bit) disc, and a Toshiba Applications and Drivers disc.). I'm assuming that the HDD is unformatted on delivery. Am I to boot from one of the discs and if so which one do I boot with, they were burned in the order I listed them above. I'm sorry if this is a stupid question, I just want to have the process run as smoothly as possible. Any response would be greatly appreciated. 
    Thanks.
             Dave

    The Apps and Drivers disk is totally independent of the recovery process.  It's purpose is to restore an individual driver, utility, or application to an existing installation. 
    The Windows Recovery Environment disk is also independent of the Recovery (restore) process. From Wikipedia:  "Windows Recovery Environment (WinRE) is a set of tools included in the Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2 operating systems to help diagnose and recover from serious errors which may be preventing Windows from booting successfully. WinRE may be installed and/or booted from many media including hard disks (Hidden NTFS partition type 0x27), optical media (such as an operating system installation disc) and PXE (e.g. Windows Deployment Services). WinRE is based on WinPE 2.0.[1]"  It would be used for Startup Repair among other things.  See http://en.wikipedia.org/wiki/Windows_Recovery_Environment  for more information.  
    If you don't post your COMPLETE model number it's very difficult to assist you. Please try to post in complete sentences with punctuation, capitals, and correct spelling. Toshiba does NOT provide any direct support in these forums. All support is User to User in their spare time.

  • T42 Recovery process stuck in loop

    I ran the 7 + 1 disc recovery process for my Thinkpad T42P.  I selelct restore factory defaults and  tt runs all of the discs and says operation is completed succesfully and I should reboot.  I switch the bios boot order to defaults.  But then it just keeps retrunging me to the Rescue and Recovery screen and will never start the OS.  Please help!  How can I get out of this loop? ?

    zac, welcome to the forum,
    please try the following;
    shut the system down by pressing the power button for 5 seconds, or untill the system shuts down.
    Start the system as you normally would and press the blue Access IBM button when you see the message "To interrupt boot..."
    When R&R has loaded select to restore the system and then factory restore.
    This should work.
    Andy  ______________________________________
    Please remember to come back and mark the post that you feel solved your question as the solution, it earns the member + points
    Did you find a post helpfull? You can thank the member by clicking on the star to the left awarding them Kudos Please add your type, model number and OS to your signature, it helps to help you. Forum Search Option T430 2347-G7U W8 x64, Yoga 10 HD+, Tablet 1838-2BG, T61p 6460-67G W7 x64, T43p 2668-G2G XP, T23 2647-9LG XP, plus a few more. FYI Unsolicited Personal Messages will be ignored.
      Deutsche Community     Comunidad en Español    English Community Русскоязычное Сообщество
    PepperonI blog 

  • Dv6748us how to make a bios recovery usb

     how to make a  bios recovery usb?

    Hi!
    You can download new BIOS versions on the Toshiba website. Search for your model and select BIOS update
    http://eu.computers.toshiba-europe.com
    Download the right file and follow these instructions:
    Extract the zip file containing the BIOS upgrade to a temporary folder.
    Make sure that all open files are saved and all applications are closed.
    Execute the extracted *.exe file in the temporary folder. Follow the instructions on the screen.
    The BIOS update will be done automatically.
    After a few minutes the Notebook will restart automatically.
    Bye

  • Restart on primary database restarts the recovery process on standby

    We have a dataguar broker configuration running in maximum perfromance mode.
    Every time we start the primary database, the recovery process on standby gets restarted.
    I can consistently reproduce teh problem. Looks like expected behaviour.
    Even if standby is in read only mode and restart the primary database it bring the database back in recovery mode.
    Any explanation why oracle needs to do it?

    Neil_Arul wrote:
    We have a dataguar broker configuration running in maximum perfromance mode.
    Every time we start the primary database, the recovery process on standby gets restarted.
    I can consistently reproduce teh problem. Looks like expected behaviour.
    Even if standby is in read only mode and restart the primary database it bring the database back in recovery mode.
    Any explanation why oracle needs to do it?Yes, When you enable broker it very common behaviour.
    When ever you bounce the database also MRP process will be started automatically.
    By disabling broker you can avoid automatic startup, BTW Standby should be in recovery mode, i think no need to worry on this.
    If you want to disable as per time, you can disable it as below
    ALTER SYSTEM SET DG_BROKER_START=FALSE ;
    Total Questions:      3 (3 unresolved)
    Close the threads when you feel its answered, Keep the forum clean.
    Edited by: CKPT on Feb 15, 2012 12:57 PM

  • Compaq CQ56 154 laptop windows 7 recovery process fails. PLEASE HELP

    Compaq CQ56 laptop windows 7 recovery process fails because RM component runtime and no valid RP index. PLEASE HELP
    I have tried the recovery process on this laptop over 10 times now and with multiple new hdds and it seems like it comes to a fail at the very end.I have posted the error log that I get. Please help me out in regards to this. 
    The process completes unit and at the very end the error log gives this:
    Error encountered during RM component run time            
    Please contact RM team for investigation            
                        CopyRight @   SRD.cpp :   12                      CopyRight @   SRD.cpp :   13 SRD 1.1.0.0115 System Recovery Deployment, provided by CyberLink. (cNB)       
                        CopyRight @    SRD.cpp :  14           DeployRp:etSRDMode @ DeployRp.cpp : 3571 SetSRDMode 1          
                            wmain @    SRD.cpp :  73 Executing call 'L"drp.SetConfigIni('deployrp.ini')"'        
            DeployRp:etectMedia @ DeployRp.cpp :  371 Start to detect disks ...         
                  DeployRp:etUp @ DeployRp.cpp :  630 Get User Partition drive letter : c.        
            DeployRp:etectMedia @ DeployRp.cpp :  563 Disk Index : [HDD] 0, [N/A] -1         
          DeployRp:etTargetDisk @ DeployRp.cpp :  571 Start to load ini ...          
                  DeployRp:etUp @ DeployRp.cpp :  630 Get User Partition drive letter : c.        
                 DeployRp:etBp @ DeployRp.cpp :  643 Start to find Build Partition drive letter.        
                  DeployRp:etBp @ DeployRp.cpp :  650 Build Partition drive letter : c.         
          BuildConfig::LoadConfig @ BuildConfig.cpp :   28 Loading C:\RM\Tools\DeployRP\build.ini ...        
          BuildConfig::LoadConfig @ BuildConfig.cpp :  111 C:\RM\Tools\DeployRP\build.ini loading complete.       
                            wmain @    SRD.cpp :  83 Executing call 'L"drp.LoadBuildIni()"'         
           DeployRp::CheckRpExist @ DeployRp.cpp :  713 Start to check whether Rp exists.        
           DeployRp::CheckRpExist @ DeployRp.cpp :  750 Recovery Partition doesn't exist.        
    DeployRp::CheckSystemRecoveryDoneFlag @ DeployRp.cpp : 757 Start to check whether SystemRecoveryDone.flg exists.     
    DeployRp::CheckSystemRecoveryDoneFlag @ DeployRp.cpp : 794 SystemRecoveryDone.flg doesn't exist.      
           DeployRp::InstallMSXML @ DeployRp.cpp : 1248 Start to install MSXML6.dll         
           DeployRp::InstallMSXML @ DeployRp.cpp : 1292 Install MSXML6.DLL complete.        
          DeployRp::CreateLangIni @ DeployRp.cpp :  331 Create Lang.ini command: C:\RM\Tools\DeployRP\CreateLangIni.exe c     
         DeployRp::CheckSSRDFlags @ DeployRp.cpp : 1044 Start to check if SSRD flags exist        
         DeployRp::CheckSSRDFlags @ DeployRp.cpp : 1061 SSRD flags do not exist         
         DeployRp::CheckSSRDFlags @ DeployRp.cpp : 1063 Check if SSRD flags exist complete        
        DeployRp::CreateBootRMWim @ DeployRp.cpp : 1363 Creating BootRM.wim ...         
        DeployRp::CreateBootRMWim @ DeployRp.cpp : 1374 Start to do setting.         
        DeployRp::CreateBootRMWim @ DeployRp.cpp : 1377 SetWimImageDstPath.         
        DeployRp::CreateBootRMWim @ DeployRp.cpp : 1382 Check tool existence.         
        DeployRp::CreateBootRMWim @ DeployRp.cpp : 1385 Tool Path: c:\RM\Tools\opktools\dism.exe       
        DeployRp::CreateBootRMWim @ DeployRp.cpp : 1389 Dism.exe exists.         
        DeployRp::CreateBootRMWim @ DeployRp.cpp : 1392 SetWimMountPath.         
        CWimMgr:etWimMountPath @ WimMgr.cpp :  199 Wim File Mounting Path = C:\RM\Tools\DeployRP\mount\      
        DeployRp::CreateBootRMWim @ DeployRp.cpp : 1397 SetLanguagePacksPath.         
       DeployRp::CreateBootRMWim @ DeployRp.cpp : 1402 SetToolsPath.          
            CWimMgr:etToolsPath @ WimMgr.cpp :  213 [SetToolsPath] lpszToolsPath = c:\RM\Tools\opktools\      
          CWimMgr:etToolsPath @ WimMgr.cpp :  220 [SetToolsPath] m_szDISMExeFullPath = c:\RM\Tools\opktools\dism.exe     
        DeployRp::CreateBootRMWim @ DeployRp.cpp : 1406 Setting complete.         
       DeployRp::CreateBootRMWim @ DeployRp.cpp : 1411 Start to do Initialization.         
             CWimMgr::InitWimMgr @ WimMgr.cpp :  358 Windows PE Source Path = c:\RM\RP\sources\boot.wim      
        DeployRp::CreateBootRMWim @ DeployRp.cpp : 1420 Initialization complete.         
        DeployRp::CreateBootRMWim @ DeployRp.cpp : 1423 Start to mount WIM image.        
           CWimMgr::MountWimImage @ WimMgr.cpp :  437 Temp Working Path = C:\RM\Tools\DeployRP\temp\      
        DeployRp::CreateBootRMWim @ DeployRp.cpp : 1426 Mount WIM image complete.        
        DeployRp::CreateBootRMWim @ DeployRp.cpp : 1431 Start to setup language packs...        
       DeployRp::GetSupportedLang @ DeployRp.cpp : 1639 Lang.ini path: c:\RM\Tools\DeployRp\lang.ini       
       DeployRp::GetSupportedLang @ DeployRp.cpp : 1678 Supported Languages :           
        CWimMgr:etWinPELanguage @ WimMgr.cpp : 1134 CWimMgr:etWinPELanguage - Enter       
        DeployRp::CreateBootRMWim @ DeployRp.cpp : 1437 Setup language packs complete.        
        DeployRp::CreateBootRMWim @ DeployRp.cpp : 1443 Start to setup tool's language packages...       
            CWimMgr:etupPackage @ WimMgr.cpp : 1327 Package does not exist: c:\RM\Tools\DeployRp\WinPE_LangPacks\64\winpe-setup.cab   
            CWimMgr:etupPackage @ WimMgr.cpp : 1327 Package does not exist: c:\RM\Tools\DeployRp\WinPE_LangPacks\64\winpe-Scripting.cab   
            CWimMgr:etupPackage @ WimMgr.cpp : 1327 Package does not exist: c:\RM\Tools\DeployRp\WinPE_LangPacks\64\winpe-SRT.cab   
            CWimMgr:etupPackage @ WimMgr.cpp : 1327 Package does not exist: c:\RM\Tools\DeployRp\WinPE_LangPacks\64\winpe-WMI.cab   
            CWimMgr:etupPackage @ WimMgr.cpp : 1327 Package does not exist: c:\RM\Tools\DeployRp\WinPE_LangPacks\64\winpe-wds-tools.cab   
        DeployRp::CreateBootRMWim @ DeployRp.cpp : 1450 Setup tool's language packages complete.       
        DeployRp::CreateBootRMWim @ DeployRp.cpp : 1452 Start to un-mount WIM image...        
        DeployRp::CreateBootRMWim @ DeployRp.cpp : 1455 Un-mount WIM Image complete.        
            DeployRp::CalculateRp @ DeployRp.cpp : 1696 Start to estimate recovery partition size ...       
            DeployRp::CalculateRp @ DeployRp.cpp : 1709 base.wim.wim size : 12452203405 bytes.        
            DeployRp::CalculateRp @ DeployRp.cpp : 1725 install.log file size : 623780 bytes.        
            DeployRp::CalculateRp @ DeployRp.cpp : 1735 WinRE and WinPe files size : 281055618 bytes.       
            DeployRp::CalculateRp @ DeployRp.cpp : 1740 RM Software size : 63933517 bytes.        
            DeployRp::CalculateRp @ DeployRp.cpp : 1745 BootRM.wim size : 268793098 bytes.        
            DeployRp::CalculateRp @ DeployRp.cpp : 1750 Patch Folder size : 369308088 bytes.        
            DeployRp::CalculateRp @ DeployRp.cpp : 1755 File4Rp Folder size : 0 bytes.         
            DeployRp::CalculateRp @ DeployRp.cpp : 1761 Extra space : 2371154178 bytes.        
            DeployRp::CalculateRp @ DeployRp.cpp : 1766 Prevented Extra size : 0 bytes.        
            DeployRp::CalculateRp @ DeployRp.cpp : 1776 Recovery Partition estimated size : 15807695464 bytes.      
            DeployRp::CalculateRp @ DeployRp.cpp : 1777 Recovery partition estimation complete.        
               DeployRp::CreateRp @ DeployRp.cpp : 2072 Start to create recovery partition ...        
                    DetToolRpInfo @ DeployRp.cpp :  122 PartitionCount: 4. PartitionType: 0. PartitionNumber: 0. PartitionStartAddr: 0 bytes. PartitionLength: 0 bytes  
                    DetToolRpInfo @ DeployRp.cpp :  122 PartitionCount: 4. PartitionType: 12. PartitionNumber: 3. PartitionStartAddr: 79917219840 bytes. PartitionLength: 108093440 bytes
                    DetToolRpInfo @ DeployRp.cpp :  122 PartitionCount: 4. PartitionType: 7. PartitionNumber: 2. PartitionStartAddr: 209715200 bytes. PartitionLength: 73013395456 bytes
                    DetToolRpInfo @ DeployRp.cpp :  122 PartitionCount: 4. PartitionType: 7. PartitionNumber: 1. PartitionStartAddr: 1048576 bytes. PartitionLength: 208666624 bytes
                    DetToolRpInfo @ DeployRp.cpp :  156 Can't find valid Rp index.         
               DeployRp::CreateRp @ DeployRp.cpp : 2090 Invalid Rp index          
                            wmain @    SRD.cpp :  93 Executing call 'L"drp.Deploy()"'         
                            wmain @    SRD.cpp :  38 Output            
    ERROR: call L"drp.Deploy()" failed.             
                           wmain @    SRD.cpp :  38 Output - Returned HRESULT = 0xe0ef002f    

    Hello k877
    I am sorry to hear you are having issues reinstalling your operating system. I am providing you with a link here to a document titled Recovery Disk Creation Error Codes (Windows 7). Now document is for creating the recovery disks but the error is showing up in your error log (0xe0ef002f). The error according to the document is the File/directory does not exist. It looks like a function call Deploy() is attempting to access this File/directory and is unable to.
    This leads me to think that it is the disks that you are using. It would stand to reason anyways as you state you have tried this on multiple hard drives. A good test would be to check to see if your error in the error log is the same every time. If it is happening at the same point each time then simply order a new set of discs from here.
    I hope this resolves your installation issue. Thank you for posting your question on the HP Forums. Have a great day!
    Please click the "Thumbs Up" on the bottom right of this post to say thank you if you appreciate the support I provide!
    Also be sure to mark my post as “Accept as Solution" if you feel my post solved your issue, it will help others who face the same challenge find the same solution.
    Dunidar
    I work on behalf of HP
    Find out a bit more about me by checking out my profile!
    "Customers don’t expect you to be perfect. They do expect you to fix things when they go wrong." ~ Donald Porter

  • Hard Drive Recovery Process has been selected

    One day, while playing a game online, the computer screen went black and a blue box appeared that said "Hard Drive Recovery Process has been selected Press Yes if you wish to continue " Also, there was NO which only shut the computer down. YES took me to a blue screen with recovery and troubleshooting options. At first, none of these worked, or stayed. Because the next time I used my computer I would get the same Hard Drive Recovery Process message and had to try various things to make it work. I did purchase a Windows 8.1 recovery flashdrive from Toshiba and attempted to install it. It took about 6 tries for it to completely install. However, after installing, I was unable to use the RESTART option to power off the computer as it would trigger the Hard Drive Recovery Process again ! Ugh ! Last night, I powered the laptop off using SHUT DOWN and in the morning, I got the Hard Drive Recovery Process screen again, much to my horror. I have Norton Internet Security and Anti Virus as well as I used Toshiba maintenance tasks and no problems were found. I would appreciate any information on troubleshooting and repairing this problem, if there is a solution. Thanks !!!!!

    I did purchase a Windows 8.1 recovery flashdrive from Toshiba   ...   after installing  ..  it would trigger the Hard Drive Recovery Process again
    The fact that the problem remains after restoring the hard disk to its original out-of-the-box contents using Toshiba recovery media means the software doesn't cause it.
    The computer needs servicing.

  • Testing recovery process.

    Hi All,
    DB -10.2.0.2.0
    We frequently perform database refreshes'es. this time, we have to perform time based refresh
    till 31-aug-09 11:00AM. following are the sequence date and timestamp extracted from v$archived_log
    in that case, whaich is the sequence, we have to use while performing time based recovery.
    One more question, for database refresh, we move dbf's and archive fom source to target.
    Now, before performing recovery, is there anyway to test out, weather we have required archives
    and dbf's. I recently read Arup's book that we can do this, but I am not sure, weather this can
    be achieved in user managed backups hot backups.
    Also, after performing time based recovery, how
    can we know, till what time the databsae being recovered.
    You swift reply would be highly appricaited.
    272193 30-08-2009 09:11:49
    272194 30-08-2009 23:15:15
    272195 30-08-2009 23:15:17
    272196 31-08-2009 02:33:51
    272197 31-08-2009 06:33:15
    272198 31-08-2009 08:50:39
    272199 31-08-2009 10:06:57
    272200 31-08-2009 10:19:30
    272201 31-08-2009 10:42:30
    272202 31-08-2009 11:13:50
    272203 31-08-2009 11:15:02
    272204 31-08-2009 11:18:45
    272205 31-08-2009 11:23:29hare krishna

    RMAN> backup database;
    Starting backup at 16-SEP-09
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting full datafile backup set
    channel ORA_DISK_1: specifying datafile(s) in backup set
    input datafile file number=00001 name=/u01/app/oracle/oradata/mmi/system01.dbf
    input datafile file number=00002 name=/u01/app/oracle/oradata/mmi/sysaux01.dbf
    input datafile file number=00003 name=/u01/app/oracle/oradata/mmi/undotbs01.dbf
    input datafile file number=00005 name=/u01/app/oracle/oradata/mmi/mydatafile.dbf
    input datafile file number=00004 name=/u01/app/oracle/oradata/mmi/users01.dbf
    channel ORA_DISK_1: starting piece 1 at 16-SEP-09
    channel ORA_DISK_1: finished piece 1 at 16-SEP-09
    piece handle=/u01/app/oracle/flash_recovery_area/MMI/backupset/2009_09_16/o1_mf_nnndf_TAG20090916T134511_5c19dv9q_.bkp tag=TAG20090916T134511 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:45
    Finished backup at 16-SEP-09
    Starting Control File and SPFILE Autobackup at 16-SEP-09
    piece handle=/u01/app/oracle/flash_recovery_area/MMI/autobackup/2009_09_16/o1_mf_s_697729560_5c19gcmc_.bkp comment=NONE
    Finished Control File and SPFILE Autobackup at 16-SEP-09
    RMAN> sql 'alter system archive log current';
    sql statement: alter system archive log current
    RMAN> sql 'alter system archive log current';
    sql statement: alter system archive log current
    RMAN> sql 'alter system archive log current';
    sql statement: alter system archive log current
    RMAN> shutdown abort
    Oracle instance shut down
    RMAN> exit
    Recovery Manager complete.
    [oracle@khurram ~]$ rm -rf /u01/app/oracle/oradata/mmi/*
    [oracle@khurram ~]$ rman target /
    Recovery Manager: Release 11.1.0.6.0 - Production on Wed Sep 16 13:47:35 2009
    Copyright (c) 1982, 2007, Oracle.  All rights reserved.
    connected to target database (not started)
    RMAN> startup nomount
    Oracle instance started
    Total System Global Area    1620115456 bytes
    Fixed Size                     2144864 bytes
    Variable Size                721421728 bytes
    Database Buffers             889192448 bytes
    Redo Buffers                   7356416 bytes
    RMAN> restore controlfile from autobackup;
    Starting restore at 16-SEP-09
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=153 device type=DISK
    recovery area destination: /u01/app/oracle/flash_recovery_area
    database name (or database unique name) used for search: MMI
    channel ORA_DISK_1: AUTOBACKUP /u01/app/oracle/flash_recovery_area/MMI/autobackup/2009_09_16/o1_mf_s_697729560_5c19gcmc_.bkp found in the recovery area
    AUTOBACKUP search with format "%F" not attempted because DBID was not set
    channel ORA_DISK_1: restoring control file from AUTOBACKUP /u01/app/oracle/flash_recovery_area/MMI/autobackup/2009_09_16/o1_mf_s_697729560_5c19gcmc_.bkp
    channel ORA_DISK_1: control file restore from AUTOBACKUP complete
    output file name=/u01/app/oracle/oradata/mmi/control01.ctl
    output file name=/u01/app/oracle/oradata/mmi/control02.ctl
    output file name=/u01/app/oracle/oradata/mmi/control03.ctl
    Finished restore at 16-SEP-09
    RMAN> alter database mount;
    database mounted
    released channel: ORA_DISK_1From another terminal come at SQL
    [oracle@khurram ~]$ sqlplus / as sysdba
    SQL*Plus: Release 11.1.0.6.0 - Production on Wed Sep 16 13:49:14 2009
    Copyright (c) 1982, 2007, Oracle.  All rights reserved.
    Connected to:
    Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    SQL> set linesize 1000
    SQL> select substr(name,1,50) fname,checkpoint_change#,last_change#,status
      2    from v$datafile;
    FNAME                                              CHECKPOINT_CHANGE# LAST_CHANGE# STATUS
    /u01/app/oracle/oradata/mmi/system01.dbf                      1350307              SYSTEM
    /u01/app/oracle/oradata/mmi/sysaux01.dbf                      1350307              ONLINE
    /u01/app/oracle/oradata/mmi/undotbs01.dbf                     1350307              ONLINE
    /u01/app/oracle/oradata/mmi/users01.dbf                       1350307              ONLINE
    /u01/app/oracle/oradata/mmi/mydatafile.dbf                    1350307              ONLINEhere you can see that within control file repositry the datafiles START SCN (CHECKPOINT_SCHANGE#) is 1350307,whenever checkpoints occur, Oracle writes a START SCN to the data file headers as well it writes the START SCN within controlfile for each datafile.The control file also maintains another SCN value for each data fil with START SCN is the STOP SCN, this STOP SCN is usually null (infinity) when yours database status is open and datafile status is online , the null status shows that recovery will start from START SCN and will goes to the end of redo thread.The STO SCN here is LAST_CHANGE#
    RMAN> restore database;
    Starting restore at 16-SEP-09
    Starting implicit crosscheck backup at 16-SEP-09
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=152 device type=DISK
    Crosschecked 1 objects
    Finished implicit crosscheck backup at 16-SEP-09
    Starting implicit crosscheck copy at 16-SEP-09
    using channel ORA_DISK_1
    Finished implicit crosscheck copy at 16-SEP-09
    searching for all files in the recovery area
    cataloging files...
    cataloging done
    List of Cataloged Files
    =======================
    File Name: /u01/app/oracle/flash_recovery_area/MMI/autobackup/2009_09_16/o1_mf_s_697729560_5c19gcmc_.bkp
    File Name: /u01/app/oracle/flash_recovery_area/MMI/archivelog/2009_09_16/o1_mf_1_1_5c19gzs5_.arc
    File Name: /u01/app/oracle/flash_recovery_area/MMI/archivelog/2009_09_16/o1_mf_1_2_5c19h2m0_.arc
    File Name: /u01/app/oracle/flash_recovery_area/MMI/archivelog/2009_09_16/o1_mf_1_3_5c19h4tk_.arc
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting datafile backup set restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    channel ORA_DISK_1: restoring datafile 00001 to /u01/app/oracle/oradata/mmi/system01.dbf
    channel ORA_DISK_1: restoring datafile 00002 to /u01/app/oracle/oradata/mmi/sysaux01.dbf
    channel ORA_DISK_1: restoring datafile 00003 to /u01/app/oracle/oradata/mmi/undotbs01.dbf
    channel ORA_DISK_1: restoring datafile 00004 to /u01/app/oracle/oradata/mmi/users01.dbf
    channel ORA_DISK_1: restoring datafile 00005 to /u01/app/oracle/oradata/mmi/mydatafile.dbf
    channel ORA_DISK_1: reading from backup piece /u01/app/oracle/flash_recovery_area/MMI/backupset/2009_09_16/o1_mf_nnndf_TAG20090916T134511_5c19dv9q_.bkp
    channel ORA_DISK_1: piece handle=/u01/app/oracle/flash_recovery_area/MMI/backupset/2009_09_16/o1_mf_nnndf_TAG20090916T134511_5c19dv9q_.bkp tag=TAG20090916T134511
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:45
    Finished restore at 16-SEP-09
    SQL> select substr(name,1,50) fname,checkpoint_change#,last_change#,status
      2    from v$datafile;
    FNAME                                              CHECKPOINT_CHANGE# LAST_CHANGE# STATUS
    /u01/app/oracle/oradata/mmi/system01.dbf                      1350307              SYSTEM
    /u01/app/oracle/oradata/mmi/sysaux01.dbf                      1350307              ONLINE
    /u01/app/oracle/oradata/mmi/undotbs01.dbf                     1350307              ONLINE
    /u01/app/oracle/oradata/mmi/users01.dbf                       1350307              ONLINE
    /u01/app/oracle/oradata/mmi/mydatafile.dbf                    1350307              ONLINENow recover
    RMAN> recover database;
    Starting recover at 16-SEP-09
    using channel ORA_DISK_1
    starting media recovery
    archived log for thread 1 with sequence 1 is already on disk as file /u01/app/oracle/flash_recovery_area/MMI/archivelog/2009_09_16/o1_mf_1_1_5c19gzs5_.arc
    archived log for thread 1 with sequence 2 is already on disk as file /u01/app/oracle/flash_recovery_area/MMI/archivelog/2009_09_16/o1_mf_1_2_5c19h2m0_.arc
    archived log for thread 1 with sequence 3 is already on disk as file /u01/app/oracle/flash_recovery_area/MMI/archivelog/2009_09_16/o1_mf_1_3_5c19h4tk_.arc
    archived log file name=/u01/app/oracle/flash_recovery_area/MMI/archivelog/2009_09_16/o1_mf_1_1_5c19gzs5_.arc thread=1 sequence=1
    archived log file name=/u01/app/oracle/flash_recovery_area/MMI/archivelog/2009_09_16/o1_mf_1_2_5c19h2m0_.arc thread=1 sequence=2
    archived log file name=/u01/app/oracle/flash_recovery_area/MMI/archivelog/2009_09_16/o1_mf_1_3_5c19h4tk_.arc thread=1 sequence=3
    unable to find archived log
    archived log thread=1 sequence=4
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 09/16/2009 13:51:44
    RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 4 and starting SCN of 1350423
    SQL> select substr(name,1,50) fname,checkpoint_change#,last_change#,status
      2    from v$datafile;
    FNAME                                              CHECKPOINT_CHANGE# LAST_CHANGE# STATUS
    /u01/app/oracle/oradata/mmi/system01.dbf                      1350423              SYSTEM
    /u01/app/oracle/oradata/mmi/sysaux01.dbf                      1350423              ONLINE
    /u01/app/oracle/oradata/mmi/undotbs01.dbf                     1350423              ONLINE
    /u01/app/oracle/oradata/mmi/users01.dbf                       1350423              ONLINE
    /u01/app/oracle/oradata/mmi/mydatafile.dbf                    1350423              ONLINEHere you can see that within controlfile repositry there is datafile header START SCN which was 1350307 after restore,when you started recovery now its
    SCN is 1350423 which shows that yours recovery process start from SCN 1350307 and ends at 1350423.
    Khurram

  • Stuck in hardware recovery process loop

    Toshiba C55-A5245
    P/N PSCF6U-01J018
    XXXXXXXXX
    Win7 Home Premium
    New computer, bought recently. All that was done was to make a Windows recovery disk and system image.
    Now the computer boots up only in "The hardware recovery process".  Went through it 3 times selectiong first the save data then next 2 times with recover to factory settings.  It always boots back up to recovery process.
    Could not find simular problem in FAQs or forum.
    How do I get out of this loop?
    [Moderator edit to remove serial number.]

    Satellite C55-A5245 
    ..make a Windows recovery disk and system image. ...   It always boots back up to recovery process.
    I don't understand whether you have restored from the recovery disc or system image. If so, you'll need to obtain a new one from Toshiba.
    For a new machine, I would call tech support at 800-457-7777 for advice.
    -Jerry

Maybe you are looking for

  • Preview for Developers update for Windows Phone 8.1.1

    Start your phone updates Microsoft has just pushed out Windows Phone 8.1.1 for those participating in the Preview Developer Program. It's believed to fix the following issues: lingering issues with those not getting the Lumia Cyan firmware errors in

  • Plant number not found in PO instead description exists

    Dear Experts, How to display Plant number in PO as only description is appearing as soon as i enter the plant. Here there is a work around that i can go to ME23 and check it out... but i want the plant number to be displayed in ME23n or in SAP Enjoy

  • FILE MANAGER-620

    MISSING FILE MANAGER , CANNOT READ A FOLDER WHICH CONTAINS EXCEL SHEETS THROUGH ITS DEFAULT PROGRAM

  • Bestbuy threatens my iPhone4s pre order

    I pre ordered the iPhone 4s the first day pre orders were available. I was told then my order would be fulfilled within a week. Since then I have received numerous emails from bestbuy apologizing for the wait and reassuring me my phone will arrive. H

  • GoLive CRASHING LIKE CRAZY!

    if anyone has any clue, i SO would appreciate it. thank you in advance! from console: Process:         Adobe GoLive CS2 [139] Path:            /Applications/Adobe GoLive CS2/Adobe GoLive CS2.app/Contents/MacOS/Adobe GoLive CS2 Identifier:      com.ad