why is happening this when flasing?

Discussion in 'Windows 7' started by bioss, Aug 3, 2009.

  1. bioss

    bioss MDL Novice

    Aug 3, 2009
    27
    0
    0
  2. secr9tos

    secr9tos MDL Addicted

    Jul 28, 2009
    999
    133
    30
    I also used phlash16 but had no problems.

    I executed it this way: phlash16.exe bios.wph /O /Force /X /C /S
     
  3. bioss

    bioss MDL Novice

    Aug 3, 2009
    27
    0
    0
    thanks ill try with this new command.
     
  4. FuzzyMaster

    FuzzyMaster MDL Member

    Jun 21, 2007
    222
    0
    10
    #4 FuzzyMaster, Aug 4, 2009
    Last edited: Aug 4, 2009
    If you are going to use phlash16 you really should be booting from pure dos, not using a Windows command prompt. If you want to use Windows (not recommended) then use Winphlash.

    Btw, unless I misunderstood, the image file in your pic does not match the command line you are using (bios.rom vs. SLIC135.ROM)

    The purpose for using pure DOS is to ensure that nothing else can be running that will interfere with the flashing process. When you use a Windows command prompt (command or cmd), Windows is still running and other processes could interfere with the flash resulting in either a failure to flash or a damaged/incomplete flash leading to a bricked computer!
     
  5. bioss

    bioss MDL Novice

    Aug 3, 2009
    27
    0
    0
    oh thanks, but i renamed bios.rom to slic135 in my pendrive thats not the problem.


    ill try with a real dos.