Old slic loader prevent windows 7 from starting normally

Discussion in 'Windows 7' started by matrix_drumr, Mar 25, 2012.

  1. matrix_drumr

    matrix_drumr MDL Novice

    Mar 25, 2012
    1
    0
    0
    Hi,

    A windows update has recently made my windows unlegit to microsoft. I downloaded the slic loader v1.6.0 and it didn't work. I then tried the last version 2.0.6 and it worked perfectly. I could use my computer for like 3 or 4 days without any problem until now. I didn't change anything related to windows or the loader but now I have this black screen at startup that prevent windows from loading. The weird thing is: it's the loader v1.6.0 that's causing it. I am not able to recover from the windows disk because it tells me the windows is not the same version, probably because of the service pack 1 or some windows update. I tried the bootsect command and it didn't work. I tried to fix the MBR and it didn't work either. I have a AMD pc with gigabyte motherboard with a windows 7 ultimate edition installation on 1 drive. The black screen says:

    SLIC LOADER v1.6.0
    Defult
    ebda 0x9a000, ebda high 0x9ff00
    extending ssdt search in 0xcfc0000 len 0x1000
    extending ssdt search in 0xcfc0000 len 0xf000
    TABL ADRESS LEN SEGMENT LEN TYPE
    FACS 0xcfcf0000 0x40 0xcfcf0000 0x1000 0x4
    SLIC 0xcfcf0050 0x176 0xcfcf0000 0x1000 0x4
    RSDT 0xcfcf1000 0x44 0xcfcf0000 0xf000 0x3
    FACP 0xcfcf1000 0x74 0xcfcf0000 0xf000 0x3
    DSDT 0xcfcf1100 0x7be3 0xcfcf0000 0xf000 0x3
    APIC 0xcfcf8d008d00 0xbc 0xcfcf0000 0xf000 0x3
    SSDT 0xcfcf8dc0 0xedc 0xcfcf0000 0xf000 0x3
    HPET 0xcfcf9cc0 0x38 0xcfcf0000 0xf000 0x3
    HCFC 0xcfcf9d00 0x3c 0xcfcf0000 0xf000 0x3
    MATS 0xcfcf9d40 0x34 0xcfcf0000 0xf000 0x3
    TANG 0xcfcf9db0 0x282 0xcfcf0000 0xf000 0x3
    SLIC entry found 0xcfcf0050 index 0x7
    overlap 0xd0000000
    , aspiSLIC memory usable 0x176
    SLIC loaded into existing entry 0xcfcf0050
    recalcultating checksums rsdt len 0x44 , xsdt len 0xf000e816
    completed
    (hd0, 0)

    There's a 30 seconds countdown here wich leads to another black screen that says about the same thing leading to a second 30 seconds countdown that leads to a 3rd black screen saying:

    drive 0x00(LBA) : C/H/S-64602/240/63, sector count/size = 976782240//512
    Partition num: 0 active, Filesystem type is ntfs, partition type 0x07
    Partition num: 1 Filesystem type is ntfs, partition type 0x07
    ****

    options if your HDD is larger than a 1TB:
    * move your boot files to a smaller partition at the start of the HDD.
    * format the HDD and allow windows 7 to create a 100mb boot partition
    *shrink and move your partition s with Gparted

    press any key to read more (that leads to another screen)

    Options if you have an OEM/Recovery partition:
    * Format the whole HDD with active0 kill disk
    * If possible use EasyBCD to relocate the boot files

    Tools to use:
    * EasyBCD to move your boot files
    * Active0 kill disk (iso) to format
    *Gparted to resize, move & create partitions.

    How to boot back into windows:
    *Boot from your windows DVD and select "Repair your computer"
    *Select command prompt
    * Enter "bootsect /nt60 SYS /force" or "bootsect /nt60 ALL /force"
    * reboot

    press any key to enter command line

    wich leads to a final black screen saying:

    [Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists the possible completions of a device/filename. ESC at any time exits. ]

    grub


    It doesnt go any further. I tried some stuff but nothing seems to work I am stuck there where all I can do is reboot, go in the bios or in the windows CD but I cant do anything useful with it. Help would be very appreciated.
     
  2. Daz

    Daz MDL Developer / Admin
    Staff Member

    Jul 31, 2009
    9,465
    66,508
    300
    #2 Daz, Mar 25, 2012
    Last edited by a moderator: Apr 20, 2017
    It will normally only drop you into the final "help" screen if it can't boot. Boot issues could occur if you've enabled hard drive compression or you're hard drive has bad disk geometry.

    Booting from your Windows 7 DVD should work, as long as you can get into its command line. And I'm pretty sure it's possible to force it to work even though the version doesn't match up :g: Commands you can use from there are:
    Code:
    bootsect.exe /nt60 sys /force
    bootrec.exe /fixmbr
    bootrec.exe /fixboot
    From GRUB command line you could try:
    Code:
    find --set-root /bootmgr
    chainloader --force /bootmgr
    boot
    Or
    Code:
    root (hd0,0)
    chainloader (hd0,0)/bootmgr
    boot
    Or
    Code:
    root (hd0,0)
    chainloader (hd0,0)/bootmgr
    rootnoverify (hd0,0)
    boot
    If it can't find bootmgr then try looking for bootwin instead.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. ketza

    ketza MDL Novice

    Jan 30, 2013
    8
    0
    0
    Hello new to the forum, and I'm sorry if I missed something in the FAQ, but I have tried all of the above commands and the end result is the same. I am running a emachine desktop updated from vista. I'm not sure how to check if my hard disk has bad geometry, but I am pretty sure that is not the case, still will not rule that out though. Bootsect and bootrec are "no such commands". I have a install DVD, and the other codes take me to a factory reset page but exit is my only option.
     
  4. Daz

    Daz MDL Developer / Admin
    Staff Member

    Jul 31, 2009
    9,465
    66,508
    300
    Version 2.2.1 of the loaders in my signature. It may work a little better for you. The actual bootsect commands you do by using a Windows 7 DVD.

    1. Boot from your Windows 7 DVD
    2. When asked to select a keyboard language select one and then hold SHIFT and press F10
    3. Type bootsect.exe /nt60 sys /force
    4. Power off and then back on
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. ketza

    ketza MDL Novice

    Jan 30, 2013
    8
    0
    0
    Thanks for getting back so quick! The loader version I used was 2.0.9, I also forgot to mention I have tried to load from the DVD, I get count down then it says boot ready but goes to the slice loader.
     
  6. ketza

    ketza MDL Novice

    Jan 30, 2013
    8
    0
    0
    Slic* loader not slice sorry typing fast on my tablet.
     
  7. Daz

    Daz MDL Developer / Admin
    Staff Member

    Jul 31, 2009
    9,465
    66,508
    300
    #7 Daz, Jan 30, 2013
    Last edited by a moderator: Apr 20, 2017
    Does the loader drop you into it's command line, so you can type stuff in? If yes then put your Windows 7 DVD in and try this:
    Code:
    cdrom --init
    map --hook
    chainloader (cd0)
    rootnoverify (cd0)
    boot
    If the above doesn't work then after your BIOS has printed out some information press and hold 'R'. If you time it right it'll take you to a boot menu that contains a "No SLIC" option. Use that and it might boot you into Windows.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  8. ketza

    ketza MDL Novice

    Jan 30, 2013
    8
    0
    0
    After trying
    Cdrom --unit I get the message
    No cdrom's found perhaps the hardware does not fully support ATAPI. If your cdrom uses unusual I/O ports, please specify the with "--add-io-ports=P".

    I also have tried all five options at that boot menu you had mentioned. All return to the slic loader.
    Sorry for being such a pain.
     
  9. Daz

    Daz MDL Developer / Admin
    Staff Member

    Jul 31, 2009
    9,465
    66,508
    300
    Can you type out the output of the geometry command? I'm interested in knowing what partitions it's found and what their type and ID's are.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  10. ketza

    ketza MDL Novice

    Jan 30, 2013
    8
    0
    0
    Drive 0x80kLBA): C/H/S=38914/255/63, sector count/size=625153410/512
    Partition number: 0, filesystem type is ntfs, partition type 0x27
    Partition number: 1, active, filesystem type is ntfs, partition type 0x07
     
  11. ketza

    ketza MDL Novice

    Jan 30, 2013
    8
    0
    0
    *drive 0x80(LBA)
     
  12. Daz

    Daz MDL Developer / Admin
    Staff Member

    Jul 31, 2009
    9,465
    66,508
    300
    #12 Daz, Jan 30, 2013
    Last edited by a moderator: Apr 20, 2017
    Try these:
    Code:
    rootnoverify (hd0,1)
    chainloader (hd0,1)/bootmgr
    boot
    Code:
    rootnoverify (hd0,0)
    chainloader (hd0,0)/bootmgr
    boot
    Code:
    root (hd0,1)
    chainloader (hd0,1)/bootmgr.bak
    boot
    Code:
    root (hd0,0)
    chainloader (hd0,0)/bootmgr.bak
    boot
    Or this:
    Code:
    chainloader (cd)
    rootnoverify (cd)
    boot
    Getting the Windows 7 DVD to boot is the easiest way. Maybe try to change your BIOS boot order so that CD/DVD is first?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  13. ketza

    ketza MDL Novice

    Jan 30, 2013
    8
    0
    0
    The first code after chainloader (hd0,1)/bootmgr reads error 13 invalid or unsupported executable format.
    the second one takes me to the factory reset but exit is the only accessible option.
    The third and forth code after chainloader reads error 15: file not found.
    The fifth reads error 23: error while parsing number.
     
  14. Daz

    Daz MDL Developer / Admin
    Staff Member

    Jul 31, 2009
    9,465
    66,508
    300
    Vista factory reset? That'd mean the partition is actually an OEM partition which may be causing the issues if it's hijacking the MBR or bootmgr. Does holding SHIFT and pressing F10 open a command prompt window from there?

    Like I've said, the best bet is to change your boot order so that the Windows 7 DVD boots first. Otherwise you'll end up needing to download something like Hirens boot CD to manually remove the loader.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  15. ketza

    ketza MDL Novice

    Jan 30, 2013
    8
    0
    0
    Yes vista factory reset.
    No shift+F10 does not open a command prompt on the factory reset screen but it did come up as the computer was booting and I changed it with in realtek boot agent to boot in order of the BIOS. Thanks again for all your help, to make it genuine ill use your most recent loader!
     
  16. Daz

    Daz MDL Developer / Admin
    Staff Member

    Jul 31, 2009
    9,465
    66,508
    300
    Hopefully the newest version can better map out your partitions :)
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  17. NSLW

    NSLW MDL Novice

    Aug 5, 2017
    3
    0
    0
    Following commands from Daz's post work for me with Windows Loader 2.2.2 and freshly installed Windows 7.
    Code:
    root (hd0,2)
    chainloader (hd0,2)/bootmgr
    boot
    However, I have to type it every time I start my machine. How can I save this settings?
     
  18. Tito

    Tito Super Mod / Adviser
    Staff Member

    Nov 30, 2009
    17,578
    15,396
    340
    Rather than reviving an old thread, why don't you post here? Post a screenshot of Disk Management window as well as a copy of MGADIAG report.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  19. NSLW

    NSLW MDL Novice

    Aug 5, 2017
    3
    0
    0
    Because it's exactly the same topic. Why do you need any reports? Everything is working in my case. I've got Windows installed on third primary partition so I use (hd 0,2) and not (hd 0,0) as DAZ loader had set.
    I just would like to know how to save this state, so it will be permanent.
     
  20. Tito

    Tito Super Mod / Adviser
    Staff Member

    Nov 30, 2009
    17,578
    15,396
    340
    @NSLW

    1. Necroposting is usually hard to moderate.
    2. The thread I mentioned earlier is a central sticky for diagnosing any Windows Loader related issues - its a real PITA to if users create multiple threads to get help.
    3. Though it may seem that the issues are identical, it may not be.
    4. Without the screenshots & the results, its tough to diagnose the issue.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...