Help - Search - Members - Calendar
Full Version: Pe Builder V3.0.35 Beta Release
The CD Forum > General > Announcements
Pages: 1, 2
Bart Lagerweij
v3.0.35 is available
THIS STILL IS A BETA RELEASE!
If this version does not have any bugs it will go public as v3.1.0

Download link:
http://www.nu2.nu/download.php?sFile=pebuilder3035.zip

Please read the change log below:
CODE
New items:
- added a first version of my own network configuration GUI (netconfig.exe)
 You can find it in the menu as system->network->Load Network Support (GUI)

Changes to pebuilder.exe:
- Added hnetcfg.dll to pluging\bartpe\bartpe.inf, to fix filesharing trouble with winxp/sp2.
- Filtered out "disk" and "tape" devices from the devicelist combobox.
- Added an advanced option to enable absolute output path.
- Fixed problem with compressed driver files (for example "yk51x86.sy_") in
 drivers folder.
- Fixed problem with some network drivers, where pebuilder complains about a
 section not having a copyfiles key. Pebuilder produced an error something like:
 Error: File "c:\...\drivers\Net\cb102\CB102B.Reg" does not exist...
- Fixed "cdrecord: No such file or directory" error when path to iso image
 contained spaces.
- Many small internal code changes.

Changed items:
- Updated plugin\ramdisk\ramdriv.sys to v5.2.10.1
- Updated nu2menu to v0.3.49 (now supports hidden menu items).
- Change plugin\bartpe, added the new Network Configuration Tool (netconfig.exe)
 added Load Fileshare Support (msserver.cmd) and some other small changes.


Regards,
Bart.
balthasar
Bart, you are the man. I'm looking forward to testing this out biggrin.gif
paraglider
How are hidden menu items defined in nu2menu.xml?
lape
Yesss! This is the coolest tool since the days of Norton Util and such! Tons of thanx and kudos to Bart...!
d4vr0s
Are there any other errorlevels besides 1?
For example one that would indicate that the stop button was pressed?
CODE
if errorlevel 2 echo *** You pressed the stop button ***
Bart Lagerweij
QUOTE (paraglider @ Dec 7 2004, 02:28 PM)
How are hidden menu items defined in nu2menu.xml?

From henk's nu2menu.xml:
CODE
2004-12-01 (V0.349)
    New:
    Shift bitwise left
    @Shl( ValueToShift, HowManyPositions )
    
    Shift bitwise right
    @Shr( ValueToShift, HowManyPositions )

    @And( ValueToAnd, AndWith )

    Changed:
    @Or()
    @Not()
    
    Menu item sub node DISABLED is replaced by VISIBILITY.
    For backward compatibility the DISABLED node only works when the sub node VISIBILITY does not exist.
    Do not use the sub node DISABLED anymore!!!!!!
    VISIBILITY="0" -> Normal
    VISIBILITY="1" -> Disabled
    VISIBILITY="2" -> Hidden


Sample:
CODE
<MITEM TYPE="ITEM" VISIBILITY="0">Example visibility 1 Normal</MITEM>    
<MITEM TYPE="ITEM" VISIBILITY="1">Example visibility 1 Disabled</MITEM>
<MITEM TYPE="ITEM" VISIBILITY="2">Example visibility 1 Hidden</MITEM>


not visible when file peshutdown.exe exists:
CODE
<MITEM TYPE="ITEM" VISIBILITY="@Shl(@FileExists(@GetWinDir()\system32\peshutdown.exe),'1')" CMD="EXIT">Restart</MITEM>


Regards,
Bart.
Bart Lagerweij
QUOTE (d4vr0s @ Dec 7 2004, 02:47 PM)
Are there any other errorlevels besides 1?
For example one that would indicate that the stop button was pressed?
CODE
if errorlevel 2 echo *** You pressed the stop button ***

No.

It actually returns the number of errors while building.
You cannot see if the user aborted it or no...

Regards,
Bart.
d4vr0s
QUOTE
It actually returns the number of errors while building

Interesting
Thanks smile.gif
Kalonji
@Bart

Would be nice having a checkbox to select wheter the custom files should be added or not (just like the "Create ISO image" checkbox).

I can't thank you enough for your tools!
JonF
Alas, the nVidia nForce NIC driver that didn't work in 3.034 still doesn't work in 3.035. PEBuilder copies nvenet.sys to system32\drivers, nvenetxp.inf to inf, and jedih2rx.bin and ramsed.bin and jedireg.pat to system32. This doesn't work. If I manually move jedih2rx.bin and ramsed.bin and jedireg.pat to system32\drivers befire making the ISO it then works. I'm no expert at reading .INF files, but it seems to me that the .INF files is sayinbg to copy the bin, sys, and pat files to the same directory.

The driver is still available at http://www.fleming-group.com/Misc/NVidia_NForce.zip.

Also, with the new RAMdisk and XPE 1.02 I get a modal dialog box and then two balloons, all saying the same thing:



I'm not complaining about the author's right to ask for money, but the modal dialog box is a bit of a pain and I don't like the "Fatal application exit" title (although the RAMdisk is working). What's the advantage of the new RAMdisk?
FileCity
New RamDisk drive cause me pains... Can't get into BartPE anymore... The loading logo screen freeze and never go further... Roll back to old driver... can't be updated for me... And I think I'm not the only one, I saw this often I think... Any suggestions ? Is my default 2MB for old systems too low ? Maybe a driver conflict ? ... I will maybe never know... Is a problem from Virtual PC ?

EDITED:

Yes, same thing with a fresh compiled ISO from pebuilder3035.zip only... can't be booted in Microsoft Virtual PC... but the old Ramdisk driver works, weird...
osm666
@Bart

Like always, Great Work, really awesome, ohmy.gif

And what u think about, the jerarqy of the plug-ins and the priority, u think about it or simply it's a wish what can be sad.gif

And think what Nu2menu is too a great tool, but maybe u can add the Icon feature, this is a reason for what i use BSexplorer in place of nu2nenu(and also add Desktop Icon stuff, and the taskbar), what u think 'bout add icons and a small taskbar?

Please continue with a great project! wink.gif
Buaya_Hunter
QUOTE (JonF @ Dec 7 2004, 04:48 PM)
Alas, the nVidia nForce NIC driver that didn't work in 3.034 still doesn't work in 3.035.  PEBuilder copies nvenet.sys to system32\drivers, nvenetxp.inf to inf, and jedih2rx.bin and ramsed.bin and jedireg.pat to system32.  This doesn't work.  If I manually move jedih2rx.bin and ramsed.bin and jedireg.pat to system32\drivers befire making the ISO it then works.  I'm no expert at reading .INF files, but it seems to me that the .INF files is sayinbg to copy the bin, sys, and pat files to the same directory.

The driver is still available at http://www.fleming-group.com/Misc/NVidia_NForce.zip

How about trying the nvidia nic driver plugin that is presented in the ultimate windows boot disk? They work very well for me. Cos some of the files in the fleming version has not even exists in the lastest version of the nforce driver.

For me, I do not even have to use a plugin for that. I just dumped the files as listed in the plugin from the nforce installlation package to the net folder of my pebuilder (ver 3.033) and volia, it works well
rl2171
QUOTE (Bart Lagerweij @ Dec 7 2004, 08:05 AM)
v3.0.35 is available
THIS STILL IS A BETA RELEASE!
If this version does not have any bugs it will go public as v3.1.0

Bart,

Thanks for the newest beta release.

A question, is there a way to run a batch file prior to the ISO being created?

I use to run one, then the ISO would be created, but I have not been able to find that ability as of yet (I guess I am blind in one eye and can't see out of the other biggrin.gif ).

Thanks again for everything,

Rob
d4vr0s
@rl2171
What I've done is call pebuilder from a batch file which goes on to build the iso after pebuilder completes.
Bart Lagerweij
@JonF

I've rechecked the .inf file and I see how to fix it...
Will try to fix it in v3.1.0

@osm666

All on the withlist, but I don't have a schedule to keep ;-)

@FileCity
@JonF

I'll check with the ramdisk author for this...

Regards,
Bart.
RvdH
QUOTE (FileCity @ Dec 7 2004, 08:37 PM)
New RamDisk drive cause me pains... Can't get into BartPE anymore... The loading logo screen freeze and never go further... Roll back to old driver... can't be updated for me... And I think I'm not the only one, I saw this often I think... Any suggestions ? Is my default 2MB for old systems too low ? Maybe a driver conflict ? ... I will maybe never know... Is a problem from Virtual PC ?

Yes, same thing with a fresh uncompressed ISO from pebuilder3035.zip only... can't be booted in Microsoft Virtual PC... but the old Ramdisk driver works, weird...

Same here...can't get passed the "loading..." screen
Bart Lagerweij
@RvdH

Need some info about this.

1. Does the pebuilder 3.0.35 work/boot OK, when nothing is added/changed?

2. What ramdisk parameters/settings are used when "loading" hangs?

Regards,
Bart.
Wendy
Hi Bart

I have found the latest beta (v3.0.35) to be quite useful, but there are still some bugs in it.

1. When you select an output path on another drive, it gives a confusing message about not being able to create L: (the other drive). None the same, it works.

2. I still have not figured out how to launch a post-install batch, largely of the type to tidy things up in the menu. One of the ways i was considering the overcomming of the limitations of processing was to create the full menus in the program directories, and copy these to the final directories according to what target files there were.

3. While one might change the volume name, i can't see how to change any other params for either cdrecord or the mkisofs. In particular, my understanding of cdrecord is that you have to point it at a dev=1,0 or something. However, my cdrom is in dev=1,1, the drive after the dvd-player.

Keep up the good work!!!!

Wendy
FileCity
@Bart

When I tested the RamDisk in Microsoft Virtual PC 5.3.582.27 (the latest one) after updrading mine, it freezes with my 3.0.32 source... So I uncompressed the new 3.0.35 and maked an ISO from US-English XP-SP2 with no modifications, just from the 3.0.35 as it... It loads ok until the Windows XP logo boot screen, the blue progress bar below the M$ logo goes and goes and goes but nothing else happens... freeze here...

The RamDisk have the standard config in the 3.0.35 zip file as I did't modified anything...

Thanks for your great work, you make our Windows debug lives better smile.gif
techman
Has anyone got this build to work with windows 2003 sp1 release candidate?
I have tried it but I get the BSOD says dll not known
no specific file is mentioned

(update)
i have found the problem dll conflict from my plugins but which one ???
Squale
With PE Builder 3.0.35 (burn CD), and its mkisofs (size 220 508), no boot with and NTLDR missing

In the *.iso, i find :
mkisofs 2.01-bootcd.ru -iso-level 4 -volid WindowsXPE -b bootsect.bin -boot-load-size 4 -no-emul-boot -hide bootsect.bin -hide boot.catalog -o pebuilder.iso e:\pe3035\pebldr

By replacing the file mkisofs with the "old" mkisofs of 3.0.33 (size 126 464) and by adding cygwin1.dll the problem disappears

In the *.iso :
mkisofs 2.01a17-Bart -iso-level 4 -volid WindowsXPE -b bootsect.bin -boot-load-size 4 -no-emul-boot -hide bootsect.bin -hide boot.catalog -o pebuilder.iso e:\pe3035\pebldr

Any ideas ?

Regards
Squale.
oscar
QUOTE (Squale @ Dec 8 2004, 05:40 PM)
With PE Builder 3.0.35 (burn CD), and its mkisofs (size 220 508), no boot with and NTLDR missing

In the *.iso, i find :
mkisofs 2.01-bootcd.ru -iso-level 4 -volid WindowsXPE -b bootsect.bin -boot-load-size 4 -no-emul-boot -hide bootsect.bin -hide boot.catalog -o pebuilder.iso e:\pe3035\pebldr


Any ideas ?

Regards
Squale.

@Squale

add -force-uppercase parameter

QUOTE
mkisofs.exe -v -force-uppercase -duplicates-once -iso-level 4 -volid "BartPE" -A PEBUILDER/MKISOFS -sysid "Win32" -b bootsect.bin -no-emul-boot -boot-load-size 4 -hide bootsect.bin -hide boot.catalog -o d:\isos\pebuilder.iso c:\pebuilder\3035\pebldr
Squale
QUOTE (oscar @ Dec 8 2004, 05:50 PM)
add -force-uppercase  parameter 

@Oscar,

Thank you, you are right.

Squale.
oscar
@Bart

pebuilder.exe -exit seems to just cause the build window to exit, not the pebuilder program.
It is by design or it is a bug?
If it is by design may you create other parameter, something like -pebuilderexit

pebuilder.exe -auto -exit yes exits pebuilder.exe but I don't want to specify -auto otherwise I will not get a chance to select plugins

Thanks
The highlander
@Bart,

Can I suggest altering your existing Ghost 8 plugin so it copies ghost32.exe and ghostcdr.dll to the ramdrive before running ghost32 (from the ramdrive).
It allows you to eject the BartPE CD temporarily and read/write your image to/from a CDR or DVDR.

Great for those systems with only one CD/DVD Drive.

As for the rest of the new release, works flawlessly for me (except the ramdrive),
I rolled it back to the previous version in 3033 and it works fine.

Keep up the excellent work. I have been using your builder from V1... and have to say it's a life saver. wink.gif

Highlander
lobzter
works like a charm ! !

wishlist:
... not critical issues but it will be fun to have...

1. since burning is now enabled using the gui -
will it be possible to specify additional command line params to cdrecord?

2. launch a user specified script prior to beginning the build proccess (for updating virus/spyware definitions and such things).
osm666
I got a trouble, i've downloaded this version and i got no troubles with Building, the problem was when the CD is booting, from the Power swith is on, to the nu2menu, was 5 mins, is like a boot cd with XPE and many plug-ins.

I think what mkisofs is tha problem but no one has been reported this issue with this version,

I don't change or enable/disable any plug-in.
Bart Lagerweij
@JonF

QUOTE
Alas, the nVidia nForce NIC driver that didn't work in 3.034 still doesn't work in 3.035. PEBuilder copies nvenet.sys to system32\drivers, nvenetxp.inf to inf, and jedih2rx.bin and ramsed.bin and jedireg.pat to system32. This doesn't work. If I manually move jedih2rx.bin and ramsed.bin and jedireg.pat to system32\drivers befire making the ISO it then works. I'm no expert at reading .INF files, but it seems to me that the .INF files is sayinbg to copy the bin, sys, and pat files to the same directory.


Fixed it in v3.0.36 now following the right destinationdir options.
Can you try http://www.nu2.nu/tmp/pebuilder-exe-3036.zip ?

I did some reading at
http://msdn.microsoft.com/library/default....0429fd2.xml.asp
and now understand more about the target directories...
I replace id hardcoded in pebuilder like this:
CODE
if (nDir== 11) nDir= 2; // system32
else if (nDir== 12) nDir= 4; // drivers
else if (nDir== 17) nDir= 20; // inf


Regards,
Bart.
moskito
@Bart

Thanks for Your great work.
I have another Networkcard wich does not work.
NetGear GA621 FiberAdapter.

http://kbserver.netgear.com/support_detail....asp?dnldID=139

PEBuilder copies ga621ND5.SYS to system32 and not system32\Drivers
I look in the inf DestinationDirs-Section. The Dir-ID=12.
Nevertheless PEBuilder copies the sys-file to system32.

Can You test it??
paraglider
Did you try the updated pebuilder that bart posted in the above post?
JonF
QUOTE (Bart Lagerweij @ Dec 9 2004, 07:58 AM)
Fixed it in v3.0.36 now following the right destinationdir options.
Can you try http://www.nu2.nu/tmp/pebuilder-exe-3036.zip ?

Sorry, I am in California and the computer that builds BartPE is just outside of Boston. I should be able to test next Tuesday. Perhaps Muskito can test.
rl2171
QUOTE (JonF @ Dec 9 2004, 04:32 PM)
QUOTE (Bart Lagerweij @ Dec 9 2004, 07:58 AM)

Fixed it in v3.0.36 now following the right destinationdir options.
Can you try http://www.nu2.nu/tmp/pebuilder-exe-3036.zip ?

Sorry, I am in California and the computer that builds BartPE is just outside of Boston. I should be able to test next Tuesday. Perhaps Muskito can test.

@JonF,

You are here in California?

What part? I'm here in Sacramento.

Have a great one.

Rob
Bart Lagerweij
QUOTE (moskito @ Dec 9 2004, 03:47 PM)
I have another Networkcard wich does not work.
NetGear GA621 FiberAdapter.

http://kbserver.netgear.com/support_detail....asp?dnldID=139

PEBuilder copies ga621ND5.SYS to system32 and not system32\Drivers
I look in the inf DestinationDirs-Section. The Dir-ID=12.
Nevertheless PEBuilder copies the sys-file to system32.

Hi,

Thanks for reporting it.

Pebuilder was taking the GA621.Fiber section and that section is for win9x.
I reordered the section search routine to fix it.
It will now take the GA621.Fiber.NT, like it should...

You can try
http://www.nu2.nu/tmp/pebuilder-exe-3036b.zip
if you want to...

Regards,
Bart.
JonF
QUOTE (rl2171 @ Dec 9 2004, 01:08 PM)
You are here in California?

What part?  I'm here in Sacramento.

Surf City (AKA Huntington Beach). Just came back from lunch at Ruby's Diner at the end of the pier.

Probably a little too far away for a casual visit wink.gif.
rl2171
QUOTE (JonF @ Dec 9 2004, 09:19 PM)
QUOTE (rl2171 @ Dec 9 2004, 01:08 PM)
You are here in California?

What part?  I'm here in Sacramento.

Surf City (AKA Huntington Beach). Just came back from lunch at Ruby's Diner at the end of the pier.

Probably a little too far away for a casual visit wink.gif.

Huntington Beach huh, if I recall, Southern California.....400 plus miles.

Hope you are having a great time there.

Rob
moskito
Hi Bart and all others,

I'm happy, with 3.0.36b all are copied correctly my additional network drivers.

Thanks for the fast completion.
Wendy
Given that there are a number of people who use post-install batch files, is there a chance to run a batch file in place of running mkisofs.exe or cdrecord.exe directly?

My batches read the .INI file direct for what it needs to know, and makes its own decisions based on what plugins are installed: (we even do mkisofs.exe by a plugin now, and the -duplicates-once option is being considered as a plugin too! You don't need to do it in non-distribution modes.

Otherwise, the thing looks grand!
Jim_a
I normally run mkisofs from a batch file and then use Nero if I want to burn a CD from the ISO. I have Pebuilder make an ISO once and then grab the mkisofs line from the logfile to get the correct syntax. My batch file copies things like the current adaware files before it kicks off the ISO, but you can do anything you want before (and after) you make the ISO.
FileCity
Reboot.cmd in nu2menu doesn't work with PE Loader, killing the shell doesn't reboot the workstation anymore...

I modified mine to call 'peshutdown.exe -r' instead of the not working nu2menu script...
joniys
I have problem with New Graphic cards (Intel 8XX, ATI Radeon 9XXX, bla,bla,bla). In (Pe Builder V3.0.32 + InfCacheBuild + Video Card driver) all works properly.
kaffeekuh
Hi Bart,

is there a way to load your new network configurator with a profile file ?
Or is it possible to script it like pe network configurator ?

cu

p.s. i really really LOVE your PE creator smile.gif
Bart Lagerweij
QUOTE (kaffeekuh @ Dec 10 2004, 02:39 PM)
Hi Bart,

is there a way to load your new network configurator with a profile file ?
Or is it possible to script it like pe network configurator ?

cu

p.s. i really really LOVE your PE creator smile.gif

No. Use penetcfg.exe for that.
My main goal for the netconfig.exe tool is that I can give it to my OEM customers.

Regards,
Bart.
RvdH
@Bart

When I tested the RamDisk in Microsoft Virtual PC 5.3.582.27 (the latest one) It loads ok until the Windows XP logo boot screen, the blue progress bar below the MS logo goes and goes and goes but nothing else happens... freeze here...

Haven't tried to actually burn it to cd, didn't add extra plugins yet
RvdH
@Bart

The new RamDisk driver seemed incompatible with MS Virtual PC (SP1)...i just tried burning it to cdrw and it worked flawless wink.gif
FileCity
I told Bart already about this problem... Waiting response from the driver author I think...

I'm sure Bart will keep us informed about this one... wait and see...

I think the problem can be from the NVRAM emulation from Virtual PC, not sure but seems possible...
ewieldra
my problem with 35 and 36 that not all raid/nic drivers are copied..
iso building works but there are some warnings in the log file

Processing (driver) INF file "C:\pebuilder36\drivers\SCSIAdapter\MassStorageDrivers\via.inf", class "", provider "", ver ""
Unsupported class (), skipping...


CODE
; PE Builder v3 plug-in INF file
;
; VIA Technologies Mass Storage Drivers
; by Chris D'Hondt

[Version]
Signature= "$Windows NT$"

[PEBuilder]
Name="Mass Storage Drivers: VIA"
Enable=1

[SourceDisksFiles]
; VIA Serial ATA RAID Controller
; VIA VT6410 RAID Controller
; VIA VT6421 RAID Controller
via\raid\viamraid.sys=4,,1

; VIA ATA/ATAPI Host Controller
; VIA VT6420 IDE Controller
via\ide\viapdsk.sys=4,,1

[SetValue]
"txtsetup.sif","SourceDisksFiles","viamraid.sys", "1,,,,,,_3,4,1"
"txtsetup.sif","SCSI.Load","viamraid", "viamraid.sys,4"
"txtsetup.sif","SCSI","viamraid", """VIA IDE\SATA RAID Controllers"""
"txtsetup.sif","HardwareIdsDatabase","PCI\VEN_1106&DEV_3149", """viamraid"""
"txtsetup.sif","HardwareIdsDatabase","PCI\VEN_1106&DEV_3164", """viamraid"""
"txtsetup.sif","HardwareIdsDatabase","PCI\VEN_1106&DEV_3249", """viamraid"""

"txtsetup.sif","SourceDisksFiles","viapdsk.sys", "1,,,,,,_3,4,1"
"txtsetup.sif","SCSI.Load","viapdsk", "viapdsk.sys,4"
"txtsetup.sif","SCSI","viapdsk", """VIA ATA/ATAPI Host Controller"""
"txtsetup.sif","HardwareIdsDatabase","PCI\VEN_1106&DEV_4149", """viapdsk"""


With Pebuilder 32 the driver is copiedto the right directory and load at startup
What could be wrong

Thnx

Emiel
ewieldra
sad.gif
Bernd Blaauw
ewieldra, patience is a virtue.. don't kick your own post within 24 hours, please.
it's like screaming for attention in real life.
Jim_a
Ewieldra
For version 34 and later, Bart added a new method of loading disk and network drivers from the scsi and network directories. However, I also had to add my card at the end of txtsetup.sif to get the driver loaded.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2013 Invision Power Services, Inc.