The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    Problem booting up after restoring from Ctrl+F11 Dell Restore

    Discussion in 'Dell' started by philipx99, May 13, 2006.

  1. philipx99

    philipx99 Newbie

    Reputations:
    0
    Messages:
    3
    Likes Received:
    0
    Trophy Points:
    5
    My E1705 was crash during a virus attack. I have no choice but to reinstall using the Dell Restore function Ctrl+F11. The restore was successful but upon restarting, the computer was unable to boot to window with the undermentioned error.

    "Pbr1....Done.Loading DRMK Version 8..Can't Load Kernel File"

    Upon doing a google search, I found out that it have something to do with the file residing in Dell Utility partition. I have read thru Dan Goodell step by step Dell partition restore tutorial. From what I gather, upon restore completed, the system suppose to copy config.bts to config.sys and delete any autoexec.bat in Dell utility partition.Finally autoexec.bat reboot the system and return the system to Sealed state which start with Dell EULA and service tag screen. In order for it to change to Seal state, the system need to have Seal.exe,seal.ini and some other files in c:\dell to perform it.

    Luckily, I am able to unhide the Utility partition using the Ptedit. Upon checking, I found that Seal.ini file is missing. This should be the answer to the problem I face. The only thing now is to seek help from those who system still have a copy of seal.ini file so I can put it back to the utility partition.If anybody is able to assist me, it will be greatly appreciated.Thanks.
     
  2. MarkMcK

    MarkMcK Notebook Evangelist

    Reputations:
    21
    Messages:
    418
    Likes Received:
    0
    Trophy Points:
    30
    How far did the Restore get in terms of creating a 'new' config.sys file in the Utility partition?

    I've got to wonder why your seal.ini file is 'missing' and what else may be gone/changed????

    fwiw I think you could probably go without getting the Utility partition back to a 'sealed' state. All it does from what I understand is give you the Dell EULA and Service Tag info. After that it launches your main system partition....

    Just a thought...

    Mark
     
  3. philipx99

    philipx99 Newbie

    Reputations:
    0
    Messages:
    3
    Likes Received:
    0
    Trophy Points:
    5
    Upon checking, it seem that the config.bts content have been successfully copy to the config.sys in Utility partition. But somehow because of the missing seal.ini, the system was unable to launch the seal.exe files to boot the EULA and service tag info. It cause it to hang and with the below error message. Even if I do a cold reset or reboot, it still come back the same error.It just doesn't go to Window. Do you happen to have the seal.ini file which can show me thru the forum. Maybe I can recreate it using text editor. Or anybody can confirm that the seal.ini file exist in E1705 laptop?

    "Pbr1....Done.Loading DRMK Version 8..Can't Load Kernel File"
     
  4. MarkMcK

    MarkMcK Notebook Evangelist

    Reputations:
    21
    Messages:
    418
    Likes Received:
    0
    Trophy Points:
    30
    Do you show the autoexec.up and config.up files in the partition?

    If so, I suppose you could --

    1. Copy then rename the copied files autoexec.bat and config.sys;

    2. Set your system partition Active;

    3. Set the Dell Utility partition to Type DE; and reboot....

    This should essentially establish an 'unsealed' state.

    If that gets you to the system parition, then all that would be left to do is check the proper access/operation of the Utility partition.

    Might be a good idea also to check your Restore function [just launch then Cancel the restore]

    Fire me a PM with your email address and I'll send along my seal.ini file fwiw....

    I must admit, I am really surprised seal.ini is 'missing'

    Mark

    ps I would also be somewhat concerned about the state of your boot code. Not knowing exactly what, if anything, goes on during a Restore wrt the boot code, it's hard to say, but you never know....
     
  5. NissanSupraGTR

    NissanSupraGTR Notebook Evangelist

    Reputations:
    7
    Messages:
    376
    Likes Received:
    0
    Trophy Points:
    30
    I'd just request the restore cd from dell and start fresh if you don't need any of the trials/etc.
     
  6. philipx99

    philipx99 Newbie

    Reputations:
    0
    Messages:
    3
    Likes Received:
    0
    Trophy Points:
    5
    Hi MarkMck, I have already PM my email to you. Hope to received the seal.ini file soon. Greatly appreciated.
     
  7. cpharding618

    cpharding618 Newbie

    Reputations:
    0
    Messages:
    1
    Likes Received:
    0
    Trophy Points:
    5
    i have the same problem except i'm getting it after installing ubuntu
     
  8. giadzich

    giadzich Newbie

    Reputations:
    0
    Messages:
    6
    Likes Received:
    0
    Trophy Points:
    5
    I had a bad disk and it has been replaced. I am in the process of rebuilding the DellRestore partition.

    Would you please send me all of the files and folders, except /IMG folder, in your DellRestore partition? You can unhide this partition by using ptedit32, and zip all files and folders (except img folder). They are about less than 5mb. Thanks alot.

    I've already had DellUtility partition file. Only need DellRestore partition.

    v h o a n g @ n e t z e r o . c o m_(remove-this)
     
  9. ATG

    ATG 2x4 Super Moderator

    Reputations:
    3,306
    Messages:
    4,461
    Likes Received:
    344
    Trophy Points:
    151
    Please do not revive dead threads(6 months or older). This one is like more than 2 years old.
    Thread closed.