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.

    Bootvis Problem

    Discussion in 'Lenovo' started by laptopbuy131, Oct 17, 2007.

  1. laptopbuy131

    laptopbuy131 Notebook Guru

    Reputations:
    3
    Messages:
    71
    Likes Received:
    0
    Trophy Points:
    15
    So I downloaded Bootvis from MajorGeeks.com and I ran it. I traced my system + driver delays. It goes ok so far until it reboots to the desktop again. Then I get this error: "Number of physical drives in the trace file is 0. Trace file has invalid system configuration information."

    My boot time from pressing the power button to an idle desktop is about 1min30sec. I want to be able to use Bootvis as I've read many positive results from it.

    I've searched Google and found that the solution would to disable any external data drives/zip drives but I do not have any attached except the CD-ROM drive and I've already removed it and attempted Bootvis again. Unfortunately, it did not work.

    If anyone has any idea of what to do to solve this error, please let me know.

    My system is a ThinkPad T61 with the 60GB 7200RPM HDD running Windows XP Pro.

    Thanks.
     
    laptopbuy131, Oct 17, 2007
    #1
  2. alexkolb1

    alexkolb1 Notebook Consultant

    Reputations:
    20
    Messages:
    138
    Likes Received:
    0
    Trophy Points:
    30
    Hi,
    I had the same problem on my computer, so I stopped using bootvis, it is a software from 2003, and hardly useful anymore, on a defragged system it makes no difference.

    Although if you you want to use it so badly, If I remember correctly this problem has something to do with your MBR.
    Check boot.ini file, sometimes it has extra boot paths from old installs / different OS, and it throws Bootvis off.
     
    alexkolb1, Oct 17, 2007
    #2