www.sarducd.it

[steph.k]

Hello,

First, congratulations for your good job!

I face following problem (tested also with latest Sardu beta version, reproduced in VMware, via USB and via physical DVD):
- I made two ISO files, one based on raw PEBuilder distribution, the other based on UBCD4Win (which is itself based on PEBuilder); each ISO has its own desktop / menu and set of tools; both ISO use DriverPacks
- both ISO files are then imported in Sardu, and build is launched
- when run, PEBuilder displays UBCD4Win menu, and UBCD4Win has lost its desktop! In fact, it seems like both ISO have mixed up their contents, leading to two modified ISO !!!

Did i miss something? Is is possible to make PeBuilder and UBCD4Win ISO files coexist on Sardu DVD? How then?

Thanx for your replies!

Steph.

[davidecosta]

I use PeBuilder with UBCD4Win in the same support.
You Use iso? After i test them

[davidecosta]

I tried with ISO and my copy of UBCD4Win and pebuilder and works fine.

you have the file WIPE\setupldr.bin ? SARDU check this for add Windows Pe at the menu

[steph.k]

Hello,

I suppose you mean WIPE\setupldr.bin in ISO\isolinux folder? Yes, the file is there!

When I boot on Sardu DVD or USB (or ISO in VMware), I find in the startup menu both BartPE and UBCD4Win entries. But after booting one of them, they seem to point to same menu and applications.

In ISO\isolinux folder, UBCD4WIN folder seems quite empty:

Code: Select all

25/09/2007  10:31             3 848 CHAIN.C32
19/10/2007  03:33               512 CMDC.BSS
08/08/2011  10:05             2 552 dban-Syslinux.ini
01/08/2008  21:59            12 241 isolinux.bin
08/08/2011  10:05             1 735 isolinux.cfg
06/07/2007  04:37           150 666 LOGO.PNG
25/09/2007  17:30            20 068 memdisk
20/07/2008  14:07           957 648 pnordahl
01/08/2008  21:59           790 048 pnordahl.cgz
25/09/2007  16:31               520 reboot.c32
01/08/2008  21:59         1 544 640 SCSI.CGZ
08/08/2011  10:05             1 737 syslinux.cfg
24/06/2004  05:59               512 UBCD4WIN.BSS
08/08/2011  10:05             1 730 ubcd4win.cfg
25/09/2007  10:31           124 452 vesamenu.c32

while WIPE seems to have more files:

Code: Select all

14/04/2008  14:00            48 046 BIOSINFO.INF
14/04/2008  14:00         1 037 824 EXPLORER.EXE
08/08/2011  10:02    <REP>          FONTS
08/08/2011  10:02    <REP>          INF
14/04/2008  14:00            47 564 NTDETECT.COM
08/08/2011  10:02           263 504 SETUPLDR.BIN
14/04/2008  14:00           263 504 SETUPLDR.OLD_BIN
14/04/2008  14:00           241 152 SPCMDCON.SYS
08/08/2011  10:02    <REP>          SYSTEM32
22/05/2011  18:00           546 802 TXTSETUP.SIF
08/08/2011  10:02    <REP>          WINSXS


In addition, still under ISO\isolinux folder, there is a folder called Programs with all (at least) UBCD4Win programs. Does this mean that both WIPE and UBCD4WIN use this Programs folder to point to applications?

Thank you for your precious help!

Steph.

[davidecosta]

Open the file \SARDU\pe.cfg and attach the entries

[steph.k]

Here are the contents of this file:

Code: Select all

#File creato da Shardana Antivirus Rescue Disk Utility 'SARDU'
#
default vesamenu.c32
prompt 0
menu title     SARDU 2.0.4   
MENU SEPARATOR
menu background /SARDU/sardu.jpg
MENU TABMSG  http://www.sarducd.it
menu color hotsel 30;47      #40000000 #20ffffff
menu color sel 30;47      #40000000 #20ffffff
menu color scrollbar 30;47      #40000000 #20ffffff
menu color help      37;40      #c0ffffff #00000000 std
MENU WIDTH 76
MENU MARGIN 10
#
MENU ROWS 15
MENU TABMSGROW -10
MENU CMDLINEROW 23
MENU ENDROW -1
MENU TIMEOUTROW -8
MENU HSHIFT 4
MENU VSHIFT 4
LABEL -
MENU LABEL Windows:
MENU DISABLE
#boot torna indietro
label <==Retour
kernel vesamenu.c32
    APPEND /isolinux.cfg
#boot di Windows PE
label Lancer Windows PE
menu label Lancer ^Windows PE
MENU INDENT 1
      COM32 /chain.c32
APPEND boot ntldr=/WIPE/SETUPLDR.BIN
#
#boot di UBCD4WIN
label Lancer UBCD4WIN
menu label Lancer ^UBCD4WIN
MENU INDENT 1
      kernel vesamenu.c32
APPEND /UBCD4WIN/isolinux.cfg
#
#boot torna indietro
label <==Retour
kernel vesamenu.c32
    APPEND /isolinux.cfg
#
#

[davidecosta]

mmm, if you install only the PE boot fine?

[steph.k]

I just made the test with BartPE only: everything works fine! BartPE has the right menu and applications.
I guess this is the same for UBCD4Win alone.

[steph.k]

Oups! Just made the test with UBCD4Win alone: I still get the slightly modified UBCD4Win startup screen (same as with both BartPE and UBCD4win), and desktop icons still do not appear.
So with UBCD4Win alone, I get the same behaviour as with UBCD4Win+BartPE. Does this mean the problem lies in UBCD4Win?

[davidecosta]

Oups! Just made the test with UBCD4Win alone: I still get the slightly modified UBCD4Win startup screen (same as with both BartPE and UBCD4win), and desktop icons still do not appear.
So with UBCD4Win alone, I get the same behaviour as with UBCD4Win+BartPE. Does this mean the problem lies in UBCD4Win?

I think yes , the ubcd4win is standard? In my test both works fine