Jump to content











Photo
- - - - -

SIBLO the syslinux derivative with NTLDR support


  • Please log in to reply
7 replies to this topic

#1 was_jaclaz

was_jaclaz

    Finder

  • Advanced user
  • 7100 posts
  • Location:Gone in the mist
  •  
    Italy

Posted 29 September 2007 - 09:22 AM

SIBLO has been written for Simplux, it is a revisited syslinux with added direct chainloading of NT type of loaders, like NTLDR or SETUPLDR.BIN.

http://simplux.org/siblo/

jaclaz

#2 ktp

ktp

    Silver Member

  • Advanced user
  • 773 posts

Posted 29 September 2007 - 11:05 AM

Wow, thank you jaclaz "the finder". It looks interesting, I need to experiment with it and compare with grub4dos.
Hope that it can directly boot an iso file.

#3 Nuno Brito

Nuno Brito

    Platinum Member

  • .script developer
  • 10560 posts
  • Location:boot.wim
  • Interests:I'm just a quiet simple person with a very quiet simple life living one day at a time..
  •  
    European Union

Posted 29 September 2007 - 11:24 AM

Nice find indeed.. :cheers:

The syntax seems simple too:
[codebox] prompt 1 timeout 0 default 1 say 1 Linux say 2 Bart PE say 3 Bart PE / RAM-Disk say 4 RAM-Test (memtest86) say 5 RAM-FS label 1 kernel vmlinuz append root=/dev/ram0 initrd=initrd.gz PMEDIA=usbflash label 2 ntloader setupldr.xp label 3 ntloader setupldr.2k3 label 4 kernel memdisk append initrd=memtest.ima label 5 kernel ramboot
append initrd=rbdisk.ima PMEDIA=usbflash[/codebox]

:cheers:

#4 ktp

ktp

    Silver Member

  • Advanced user
  • 773 posts

Posted 29 September 2007 - 12:49 PM

I tried different things under QEMU:
Some entries are a little long under QEMU, first time I thought that it hang.

prompt 1

timeout 0

default 1

say 1 Puppy Linux

say 2 Bart PE

say 3 Bart PE / RAM-Disk

say 4 RAM-Test (memtest86)

say 5 RAM-FS

say 6 ntldr

say 7 grldr

say 8 bootmgr

say 9 io.sys

say 0 pqmagic

say 10 bootflp.bss

label 1

  kernel puppyk

  append root=/dev/ram0 initrd=puinitrd.gz

label 2

  ntloader setupldr.xp

label 3

  ntloader setupldr.2k3

label 4

  kernel memdisk

  append initrd=memtest.ima

label 5

  kernel ramboot

  append initrd=rbdisk.ima PMEDIA=usbflash

label 6

  ntloader ntldr

label 7

  ntloader grldr

label 8

  ntloader bootmgr

label 9

  ntloader io.sys

label 0

  kernel /images/memdisk

  append initrd=/images/pmagic8.ima

label 10

  kernel bootflp.bss

  append -



#1 OK
#2, #3, #6 OK
#7 OK. Important, since then grub4dos can be used to load bootmgr for example.
#9 not OK. Normal since probably not the right syntax, refer to #10.
#0, #4 OK
#8 get error message: NT loader size is too big!
#10 not OK, it hang.
#5 not tested.


So looks like siblo is less capable then grub4dos at the moment. Also no scrollable menu list,
no edit capability, no setup for keyboard etc...

#5 online

online

    Silver Member

  • Advanced user
  • 767 posts

Posted 19 May 2008 - 04:02 PM

Actually I use SIBLO as single boot loader for my VistaPE and it works great for me: simple to install and to configure, and no error message on "ntloader bootmgr".

prompt 0

timeout 0

default 1

say 1 VistaPE

label 1

  ntloader bootmgr

Furthermore now I effectively can use FAT32 on my UFDs of any size (notes say "up to 2 Terabyte"!) without BIOS compatibility issues on boot: I like it.

I was not able to boot my VistaPE from UFD on a second machine (very similar to the main machine) in any way: all attempts failed.

During a recent search of a "new" boot loader I found first this thread

http://www.msfn.org/...sk-t102988.html

and then the present one: so I decided to try it. ;)

Really I reach the success booting UFD on the 2nd machine also setting the UFD as Fixed Disk, but maybe that is another topic... :thumbup:

#6 parsifal

parsifal
  • Members
  • 1 posts
  •  
    Italy

Posted 21 January 2009 - 10:23 PM

siblo support graphic with vesamenu.c32?
Don't work with this parameter
default vesamenu.c32

prompt 0

#

menu title	 xxx

menu background xxx.jpg

#

menu color tabmsg 37;40	  #80ffffff #00000000

menu color hotsel 30;47	  #40000000 #20ffffff

menu color sel 30;47	  #40000000 #20ffffff

menu color scrollbar 30;47	  #40000000 #20ffffff

MENU WIDTH 72

MENU MARGIN 5

MENU PASSWORDMARGIN 3

MENU ROWS 15

MENU TABMSGROW 22

MENU CMDLINEROW 23

MENU ENDROW 24

MENU PASSWORDROW 11

MENU TIMEOUTROW 20

label 0

menu label  Avvio da HD (default)

	localboot 0x80

timeout 400

#

label Boot from Floppy WIndows 98 SE

	  kernel memdisk

	append initrd=/extra/winb98se.IMA

#

label Boot from Norton Ghost

	  kernel memdisk

	append initrd=/extra/ghost.ima
Thanks in advance.

#7 Icecube

Icecube

    Gold Member

  • Team Reboot
  • 1063 posts
  •  
    Belgium

Posted 13 February 2009 - 01:16 PM

You can use syslinux with the chain.c32 (32-bit COMBOOT module) to chainload ntldr.


* chain.c32: option "swap" to support swapping of BIOS drive numbers. This is necessary to boot certain operating systems (DOS, Windows) from a secondary drive.
* chain.c32: option "file=" to support loading a boot file from the SYSLINUX filesystem instead of loading the boot sector from the drive.
* chain.c32: option "seg=" to control the load location.
* chain.c32: option "ntldr=" as a shorthand for "seg=0x2000 file="; use this to load one of WinNT's loaders:

chain.c32 hd0 1 ntldr=/MiniNT/setupldr.bin
Note that the file needs to be in the SYSLINUX filesystem.

* chain.32: options "freedos=" and "msdos="/"pcdos=" as shorthands for "seg=0x60 file=" and "seg=0x70 file=" respectively; use this to load FreeDOS's kernel.sys, MS-DOS's io.sys or PC-DOS's ibmbio.sys.



@ parsifal
Change the end of your configuration file to:
menu label  Avvio da HD (default)

	menu default

	localboot 0x80

timeout 400



#

label W98

menu label Boot from Floppy WIndows 98 SE

	  kernel memdisk

	append initrd=/extra/winb98se.IMA

#

label nortonghost

menu label Boot from Norton Ghost

	  kernel memdisk

	append initrd=/extra/ghost.ima
The label command is used by syslinux (not by vesamenu.c32) and can't have spaces in the name (you can use 'label -' too, if you use the vesa or normal menu system).
vesamenu.c32 and menu.c32 read the menu label section (can contain spaces).
Use menu default after a label statement to make that entry the default (instead of using 'label 0').

Read /doc/menu.txt from the syslinux archive.

#8 maanu

maanu

    Gold Member

  • Advanced user
  • 1134 posts
  •  
    Pakistan

Posted 26 March 2009 - 05:54 PM

i though i should reply SIBLO related issues in this topic .

well i have already made ubcd4win working from usb . see below
http://www.boot-land...?...ewpost&f=66

now im trying vista pe , i could not simply load it via

say 1 VistaPE
label 1
ntloader bootmgr

it gives error " could not find kernel image ,bootmgr


then i tried to use grub with siblo . like this

KERNEL /BOOT/grub.exe
APPEND --config-file="find --set-root /VISTAPE.WIM;chainloader /BOOTMGR"

this time it did start loading but right at the spot it returned error code with

" 0xc000000f required device inaccessible "

i have bootmgr file at the root , and BCDNTLDR , BCDBOOTMGR , bcd , boot.sdi files in boot folder at root . and have siblo.cfg in boot >silo .

just wondering where im going nuts...:good:

edit : ok find out why i was going nuts , i was tired and hungry ^_^ .

well i changed it to

KERNEL /BOOT/grub.exe
APPEND --config-file="find --set-root /BOOTMGR;chainloader /BOOTMGR"

although my concept is not yet clear but i did after various tries . u ll laugh like a mad guy if i would tell u which configuration i had tested . hehe .

ps there was something to do with bcd files in boot folder . i had to hex edit it to reflect the current changes in directory ,,

i ll disturb u guys soon dont worry ...

Maanu




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users