SARDU in a multi-partitioned environment

Congratulazioni Davide !

I successfully created a USB drive with UBCD4WIN which is my nightmare. Infact I keep a fat hard drive (320GB) with my archives and, ready to go, distributions and tools to use when friends ask you about their computer issues...

I am asking help on integrating (without destroying the content!) SARDU in my environment, specific I wish to run UBCD4WIN and possibly ReactOS which is a primising, but slow, project.

My environment is the follow:
- MBR: boots GRUB4DOS, from menu.lst I have the main control of the whole booting system
- Partition 1 [dedicated to boot]: it boots syslinux (current version) fired by grub4dos. It work fine, I can also chain back grub4dos
- Partition 2 [dedicated to distribution, where I wish to integrate SARDU]: I want to copy SARDU usbkey content in a folder and integrate it into either menu.lst or syslinux.cfg. The latter seems easier to perform.

So far so good

Here is my menu.lst configuration driven by MBR:
title Load Syslinux
chainloader +1
rootnoverify

which fires all syslinux entries, now starts my problem:
on partition 1 this is the integration entry to fire SARDU on partition 2
LABEL SARDU
MENU LABEL ^SARDU
COM32 /chain.c32 hd0 1 ntldr=/SARDU/ldlinux.sys

where SARDU is a folder under /dev/sdb2 FAT 32 fs

I also tried to hook directly to UBCD4WIN replacing ntldr=/SARDU/miniub/SETUPLDR.BIN unsuccessfully

please sugest.

Grazie mille
Benny

p.s. Why am I doing such a complicated thing ?
1 - I experienced that my 320GB HD is always with me, little USB pens sometimes
2 - I experienced that one bootloader does not fit all situations, so I like to be able to fire multiple bootloaders and leverage on their peculiarities (i.e. Grub, grub4dos, grub2, syslinux, gujin)
3-SARDU is a clever way to create controlled environments, so I don't have to reinvent the wheel, just integrate.

Congratulazioni Davide !

I successfully created a USB drive with UBCD4WIN which is my nightmare. Infact I keep a fat hard drive (320GB) with my archives and, ready to go, distributions and tools to use when friends ask you about their computer issues...

I am asking help on integrating (without destroying the content!) SARDU in my environment, specific I wish to run UBCD4WIN and possibly ReactOS which is a primising, but slow, project.

My environment is the follow:
- MBR: boots GRUB4DOS, from menu.lst I have the main control of the whole booting system
- Partition 1 [dedicated to boot]: it boots syslinux (current version) fired by grub4dos. It work fine, I can also chain back grub4dos
- Partition 2 [dedicated to distribution, where I wish to integrate SARDU]: I want to copy SARDU usbkey content in a folder and integrate it into either menu.lst or syslinux.cfg. The latter seems easier to perform.

So far so good

Here is my menu.lst configuration driven by MBR:
title Load Syslinux
chainloader +1
rootnoverify

which fires all syslinux entries, now starts my problem:
on partition 1 this is the integration entry to fire SARDU on partition 2
LABEL SARDU
MENU LABEL ^SARDU
COM32 /chain.c32 hd0 1 ntldr=/SARDU/ldlinux.sys

where SARDU is a folder under /dev/sdb2 FAT 32 fs

I also tried to hook directly to UBCD4WIN replacing ntldr=/SARDU/miniub/SETUPLDR.BIN unsuccessfully

please sugest.

Grazie mille
Benny

p.s. Why am I doing such a complicated thing ?
1 - I experienced that my 320GB HD is always with me, little USB pens sometimes
2 - I experienced that one bootloader does not fit all situations, so I like to be able to fire multiple bootloaders and leverage on their peculiarities (i.e. Grub, grub4dos, grub2, syslinux, gujin)
3-SARDU is a clever way to create controlled environments, so I don't have to reinvent the wheel, just integrate.

I use a notebook disk partitioned when the thirst partition is FAT32 of 30 Gb. With all three PE 1.x (included UBCD4Win, You can also add megalabcd with name MegaLabCD.iso and become four) and one PE >2.
I think that best solution is to use SARDU as principal, use extra folder for that now isn't supported.
This allows you to use the incremental function. Sardu is updated continuously, so you do not have any time ...@@

Italian
Uso un disco per notebook partizionato in due, dove la prima partizione da 30 Gb è fat32. Ho installato tutto SARDU con tre Windows PE 1.x (incluso UBCD4win, diventano quattro aggiungendo megalabcd col nome megalabcd.iso) e un Pe >2.
Penso che la soluzione migliore sia usare SARDU come sistema principale e usare la cartella extra per il restante che per ora non è supportato.
Questo ti permette di usare la funzione incrementale di SARDU che è aggiornato di continuo, se no ogni volta devi ... @@

Grazie Davide,

as said I have a running system containing real data, so my challenge is to make modifications without destroying or loosing data. Obviously I make tests on normal usb drivers

I keep a separate partition for booting as I can efford to format it if required with minimum impact.

My ideal situation (which I kept for years) is having MBR firing Gujin and only ISOs images on my disk. Gujin needs no/minimum configuration. So in the change management process, as you refer, I simply need to download the new ISO image and I ready to go.

In the real world does not allow ALL images to be fired by Gujin, so I replaced MBR with grub4dos which still can chain gujin and cover some more situations, but not all.

Finally I found SARDU 2.0 which can cover another piece of my puzzle, the ntldr based situations using syslinux.

I noticed you are a syslinux geek and managed where I did not manage (congratulations btw): firing win based distributions in a multiboot environment and this is the topic which I wish to integrate.

Any help on hooking SARDU will be welcome

thanks
benny