Thanks

autobuild.cmd line 101...

If you do not specify a label in pebuilder, autobuild.cmd uses TrustyBootCDXP.
Either change it in pebuilder or hard code the name you want in autobuild.cmd line 101

Do not change anything before the = sign.
Example:
IF "%CD_label%"=="" SET CD_label=UBCD4WIN

Have you changed the autobuild.cmd file recently???
The one I have is on line 101? (this might be from the beta version.)

A few thoughts from a forum noob but BartPE old-timer...

I appreciate the amount of time and effort that must have gone into preparing this for BartPE - attempting to combine the compilations of others into one working process was an immense undertaking... but unfortunately I cannot enthusiastically embrace this new method of drivers add-on. Some thoughts:

• Apparently, those who beta tested did not include those who use sp1(a) as a source. When building using sp1, the ISO will not be created due to an error (...\BartPE\i386\system32\sdhcinst.dll" returned error 2: The system cannot find the file specified.) This is an sp2-specific file. The error is contained in BTSDrivers.inf - simply commenting out the line: ;sdhcinst.dll=2 solves this issue.
• This new method adds incredible bloat, but little in the way of benefit. I have briefly compared the drivers list (browsed but not scoured), and find little difference in the amount of useful drivers between the so-called old method and this newer scheme. By useful, I am referring to NIC and MassStorage. Chipset/CPU/Sound/Graphics and even WLAN drivers are either 1) useless (won't work in BartPE) or 2) useless insofar as a rescue CD is concerned. I have not personally read/heard of anyone successfully getting their wireless connection to work in BartPE... but even if they do exist, why on earth would anyone waste so much valuable CD space for wireless, when the whole purpose of BartPE/UBCD4WIN was to use it to FIX computers, not as a substitute operating system? Even if one had a wireless-capable laptop that needed fixing, wouldn't it be wiser to just connect the machine with a cable to gain net access should it be necessary? I see WLAN drivers as an incredible waste of precious CD real estate.
• Speaking of which: BLOAT - my previous plain-vanilla UBCD4WIN CD with the drivers-pack (PE builder method) was around 380.7 MB - but the exact same setup EXCEPT for having only the LAN/MassStorage/WLAN packs enabled using the new drivers method bloated to 539.6 MB! Again, for me anyway, a monumental waste, as I have been unable to find much difference in the drivers that really count - standard NIC and MassStorage. I would MUCH rather see further development in new and useful applications for UBCD4WIN - the previous drivers-pack took care of virtually all my needs - plus it was easy to add to if I had specific drivers I wanted to add.
• Much has been made regarding nForce drivers - but I have found using the conventional plugin method works fine.
• I think pcuser's config utility a great idea, and more in line with making UBCD4WIN user-friendly... but this new method of driver add-ons is definitely not for the inexperienced user. I fear that the UBCD4WIN project is taking an unwarranted turn into tech-savvy-only territory, which is why I wholehartedly support pcuser and his config efforts. This driver method, however "cool," is just not worthy of my enthusiastic support - realizing, of course, my support means nothing!!!
• Of course, due to bloat, any meaningful multi-boot CD is now almost only a dream.

If one wants an XP "Live CD" that nearly emulates XP in every way, get Reatogo and add this new drivers-pack - as obviously, construction and boot time are not important to you... if, however, you want a lean-mean fighting "tool," stick with UBCD4WIN and the conventional way of adding drivers.

Oh, and one more thing to add to my now curmudgeon reputation: forums in general - this one being lately being no exception, can do with less meaningless bantor... perhaps more suited to using personal messenging or instant messaging or email are posts similar to "I'm sending you files now... OK I got your files... OK 10-4 good buddy - I'll get back to ya... OK, I'm uploading now... OK, I fixing the problem now... OK, got the problem fixed... OK, I'm uploading the fix now..." and on and on and on (not unlike this post might seem to be). I guess in a perfect world, I'd like to see a post, and relevant replies to the offering such as solutions or improvents. The chit-chat should be relegated to... well... a chat room. BTW, I noticed a live-chat option on other Invision Boards (v2.1.2) - can't ubcd4win.com also have this option?

Well, my opinions/ranting has gone on long enough - maybe someday I'll contribute something worthwhile... in the meantime, I have to go yell at the neighbor kids to GET OFF MY GRASS!!!

Oh Wait!!! Did I forget to mention the duplicate file name issue mentioned by someone else in this forum? For just the three driver-packs I installed, I counted 806 files (give or take a few) with potential duplicate-name issues. Who knows, perhaps we'll get lucky and everything will work for everyone... one the other hand, if there are conflicts, one could have a look at the Excel file located here: http://rapidshare.de/files/7117110/bts.duplicates.xls

Ahhh - I can't wait for Christmas... Bah-humbug!

All I can currently do.

I think someone woke up on the wrong side of the bed this morning...

While I share a bit of concern over the current size of this driver pack(s)... I guess BartPE-lover hasn't seen all of the requests for more drivers by the other users, at least from the few posts I've seen this is a big issue and this will go a long way to address it.

Personally I think that nothing but praise should be given to the work already put into this part of the project not to mention the work that will need to be done to tweak it out.

I guess some people just never like change even if it will ultimately lead to a better product.

Hm yes I'm sorry I have a beta version I'm working on that will add more features but it's not ready yet. I did change those lines now that you mention it.

Sorry for the missinformation.

Why would they barts pe does not even officially support anything less than sp2 any more. Or at least that was the impression I had last.


Um it's really pretty easy to leave of what you dont want. If you dont want those dont install them. Only add lan and mass storage if thats all you care about.



not sure what you are doing but if you would have shared it there would have been allot less users out there complaining about nforce drivers not working. And the pack curently works for what we have been able to test with anyway.


to get things working on a vast majority of hardware which I personally own a shop and need it to work on as much hardware as possible you have to have drivers for quite a few things. Yes it adds size but if you dont have the drivers to begin with to make the hardware work who cares how lean it is if it wont run on the hardware.

You could also make a multi boot dvd if you really needed to.




as for the duplicates if you find something not working then report it please untill then we really dont know do we.

@BartPE-lover
One of the main reasons I wanted to switch to this new way was because there was MORE drivers, and thus MORE hardware support, and support that actually worked. The other main reason is because I don't have the time anymore to continually add and update drivers. Now, BTS does that for me as we use his driver packs. He has spent an IMMENSE amount of time getting these things perfected and I can guarantee that there are NO duplicates, as that's one main thing he has to watch out for. What you might be seeing as that some drivers look similar, but because different companies (like Dell, HP, etc.) modify the default manufacturer driver to ONLY work for their device, he has to include all of these different kinds, but with slightly different names. So, it may seem like the drivers are duplicates, but they really aren't, and you can't just include the main manufacturer driver, as then all of the other modified products wont work.

In any case, I hope you feel that the new release is more towards a better future than not. I understand your concern for "user-friendlyness" but as of right now, this is the best we can do. Just think when the first UBCD4Win came out... that was pure tech-savvy only, so it will just take some time before this method becomes more "easy" for people such as yourself... :-\ Also, if you want to complain about how we may or may not use the forum to "chit-chat" (which is kinda what forums originated as), then just don't bother to come or read. We just like to have all information out in the public so that everyone knows what's being worked on and that we are aware and fixing problems. I guess that's something that's hard to understand in your case, just like the vision of this project... :-\

Anyway, have a nice day.

@ BartPE-lover

I wonder how much *help* you could have offered or how many solutions you could have found in the time it took to write that conjectural tome of yours.

I value your opinion but I wish you would see that by 'bashing' and not 'creating' you are manifesting your destiny...and the destiny of the project you use (BartPE that is)...

I have to say that if there wasn't this kind or chit-chat there would be much less overall improvment as only a few 'select' people would have access to *all* relevent info...doesn't sound very good to me

Hi

Sorry if this has already been posted but there seems to be a few topics going for this.

I have made many UBCD for win in the past and they have all worked fine.

I downloaded all the latest files as of yesterday afternoon Perth Australia time and then made the CD with the BTS driver packs.

I have also been using the BTS packs for many months as I am a member of MSFN, but that is for a different project.

The problem is that with the new drivers, no devices are detected. It seems to me that they are not copied across correctly and so are not being installed etc.

Many thanks

Like I said before, please provide elaborate details on the "exact" steps you took to build the CD. We'll continue from there. Thanks.

I am also having problems with the new 2.01 driver install where I get no ISO file created. I have tried it several times with no success.

-downloaded BartPe 3.1.3
-downloaded the 2.55 install and the 2.1 drivers.
-downloaded all the BTSdriver packs except sound
-installed BartPe
-deleted the plugin folder, ran 2.55 install and then the driver 2.1 file
-copied all the BTSdriver files to the appropriate folders
-ran Pebuilder and ended up with no errors but no messages as per writing out the ISO file are seen and the ISO file is not created.

I tried to run mkisofs.exe manually, ran autoinstall manually and autobuild but errors out with "The system cannot find the file c:\Program." Seems like some misdirection.

Thanks,
NRM

P.S. Thanks to Ben and all the boy keeping this project alive and making it better everyday.

By this quote: "The system cannot find the file c:\Program", it seems like you may be running everything from within a folder that has spaces in the name (like C:\Program Files\...). Please create a folder on the root of your drive without any spaces in the name and try again. Other, please give even more details about your system, etc. Thanks.

I had the same problem, but the error was C:\documents

I moved my files to the root of C:\ and started the build, everything worked fine then. Thanks for the help!!!

Yup, the "Documents and Settings" folder is a huge problem, as that's where the "My Documents" folder lies where everyone seems to do everything in. I personally hate using that folder and always create my own on the root of the drive, but whatever works. As in this case, the root of the drive works (with no spaces in folder name).

My system information:

[SYSTEM]
TotalDiskDrives=3
DiskDrive1=Floppy Drive A:\
DiskDrive2=Hard Drive C:\, FreeSpace: 31475MB, TotalSpace: 38146MB
DiskDrive3=CD-ROM Drive D:\
Processor=Intel P3, 1095MHz
Memory=496MB total (67% load )
Video=1024 x 768, True Color (32 bit)
Multimedia=CD-ROM, Sound
OS=Windows XP (Build 2600) Service Pack 2
Browser=Microsoft IE Build 6.0.2900.2180 128-bit encryption
Firewall1=Zone Alarm
Plugin1=Name: Viewpoint, Version: 3, 2, 2, 26
Plugin2=Name: Direct Draw, Version: 5.03.2600.2180 (xpsp_sp2_rtm.040803-2158)
Plugin3=Name: Windows Media Player, Version: 10.00.00.3646
Plugin4=Name: Shockwave Flash, Version: 7,0,19,0
Plugin5=Name: Real Player, Version: 6.0.12.1348
AntiVirus1=AVG 7.0
[CACHE]
CurCache=6MB
MaxCache=128MB
TopSpeedCache=256MB
[CONNECTIVITY SUMMARY]
Device1=Other Dial-up ISP or LAN TCPIP_CONNECTION (ADSL)
Device2=TOSHIBA Software Modem AMR on COM3 MODEM_CONNECTION
[NETWORK]
NIC=Detected
USB=Detected
Adapter1=Name: Intel 8255x-based PCI Ethernet Adapter (10/100)
[COM3]
CommPortName=COM3
ModemName=TOSHIBA Software Modem AMR
Interrupt=11
Address=178
MaxBaud=115200

BartePe installs in c:\pebuilder313 and I don't have anything in c:\program files or c:\documents and settings regarding this project.

Running from c:\bartepe313 folder, there was no ISO file created. I ran autobuild.cmd and this time it extracted all the BTSdrivers and created an ISO file for me for the first time.

I booted the UBCD4WIN CD and everything seemed to work EXCEPT I have no Network Adapter: Intel 8255x-based PCI Ethernet Adaptor or Fast Infrared Port: SMC IrCC.

I can see an error flash up on the screen about the network adapter but I can't read it and then I get all the untested by Microsoft driver warnings which I guess is ok.

I enter all the values when prompted for network support but the driver never loaded.

I can see it in System Information with a yellow check mark along with the IR device.

FYI,
NRM

P.S. The is the autobuild_install.log that got created with the initial installation:

INSTALL.cmd started at
Date: Mon 11/07/2005
Time: 17:30:12.51
-----------------------------------------
PEBuilderDir: .
ISOfile :
OutDir :
PEUtilsPath : .\temp


STEP 1: rename the original mkisofs and copy mkisofs wrapper into place

.\plugin\autobuild\files\mkisofs_wrapper.exe
1 File(s) copied

STEP 2: rename the original autobuild.cmd and copy new autobuild.cmd into place

.\plugin\autobuild\files\autobuild.cmd
1 File(s) copied

Install finished. You are now ready to use autobuild.

This is the top of the file after I ran autobuild.cmd again:

autobuild.cmd started at
Version: 1.6
Date: Mon 11/07/2005
Time: 17:57:23.87
-----------------------------------------
PEBuilderDir: C:\pebuilder313
ISOfile : C:\pebuilder313\pebuilder.iso
OutDir : C:\pebuilder313\BartPe
PEUtilsPath : C:\pebuilder313\temp

NEW flag is set - so preparations are done
clearing TempDir C:\pebuilder313\temp

moving the autobuild files to the tempDir C:\pebuilder313\temp
etc......to the successful building of the ISO file.

Looks like the initial re-directions are invalid.

Are you sure you copied ALL of the BTS driver packs to their proper places and that once the CD is booting and initially gets into the Windows-like interface, the HWPnP plugin kicks in and begins automatically installing the correct drivers for your hardware? I thought the Intel adapters would be fine, but yours may be a special case. Maybe someone else can respond with more input.

Yes, all the BTS driver packs except for sound have been copied to their proper locations. I do see the HWPnP plugin kick in and loads drivers. I see an error loading an adapter but real fast flash on screen so I can't copy any details but I presume it's an error loading the ethernet driver. Then I do see a lot of warning screens that are hard to read but look like a warning about the drivers not be certified by Microsoft.

they are not exactly what you think they are screens for what windows xp thinks are unsigned drivers. hwpnp just autopresses the install anyway buttons for you.

This should be a pretty standard driver for the Intel 8255x based PCI Ethernet Adapter.

And your right, I meant unsigned not certified and it is just pressing OK because they all flash by on screen really fast.

Have you tried a vanilla BartPE build without any drivers? Have you tried a vanilla UBCD4Win build with just the old 1.6 drivers? If so, did they work or no? There's something strange I think here... I don't know.. :-\

I have never created a vanilla BartPe disk. I have always used UBCD4WIN.

I have created a CD with the old 1.6 drivers and it worked fine.

I would just use old drivers for now then, or if you want, add only the Network portion of the old drivers and the entire new drivers and see if that works.

I tried creating a vanilla BartPe CD and networking came up fine. With the lack of programs on the CD, I could not do much with it but I did see networking active in Task Manager. I was able to load ePrompter from my C:\ drive and email sends and receives worked. Doubt if the IRcc interface worked since I had no way to check what drivers were active with the limited BartPE disk.

EzPcFix's link to 1.6 drivers doesn't work, errors out with a "File or directory not found".

You can get them at my downloads site HERE.

I just created a vanilla UBCD4WIN build 2.55 with the old 1.6 drivers. I booted the CD and everything seemed to work EXCEPT I still have no Network Adapter: Intel 8255x-based PCI Ethernet Adaptor.

I looked around the forum and it seems like there were problem loading some INTEL nics in 1.6. Was that ever resolved?

I am having the same problem. All previous versions of UBCD4WIN have worked fine however now when I boot it will not detect the Broadcom Gigabit Extreme Network Adapter.

Well it detects it but then says it cannot find it...really weird hey.

I'm assuming this is with the 2.0 driver packs yes?

I have been looking things over and it would seem that lynksys has some issues with using the same filename for drivers for different nick cards. This is made worse by the fact that the files are different timestamps and versions. I'm seeing all of these issues with lan massstorage and with wlan.

So To make a long story short it will take a long time to go through them all and fix them. Which I believe is exactly what little bugger and myself were trying to avoid. I can safely say that this take would take quite a while. I can also say that for now it would possibly be best to use the drives for lan from the 1.6 packs and use the mass storage from 2.0. I also use chipset, cpu, and intel graphics driver for 2.0

I hope this helps those of you with issues. With time we will try to get these things figured out. Thanks.

Both of you having problems with the net card (for the old drivers)--
Try replacing just the inf files in i386/inf with these:

New infs

Use Ultraiso to edit your iso file!

Are you saying it may be a good idea to use LAN drivers from v.1.6 and WLAN drivers from v.2.0.1?

Is there an identifier for LAN & WLAN drivers in v.1.6?...to know which drivers to keep and which to remove?

Thanks

No, there's no identifier, though I did use decent folder structures, so you may be able to find it just by looking around.

I was saying for noe only to use lan and wlan drivers from 1.6 Dont use any of them from 2.01 as I'm also seeing issues on my end. Only use for now the mass storage, cpu and chipset drivers from the bts drivers. I think we are fairly safe with these. \


for the rest there may be a bit of work required. I may end up having to create our own driver packs. I'm looking into also maybe better methods of implementing lan drivers. It's just an idea right now but we will see how it goes.

Thanks for the info...


And is the Intel plug to be used or not?

Thanks

yes sorry that is a plug I put in there and I know it works. It's fine to leave in there to cover quite a few of the older chipsets.

UltraISO (Trial Edition) won't save the project because it is greater than 300MB.

@ NRM

UltraISO (along with all the other ISO progs) have a 300mb limit in trial...you'll have to fork over about 30.00 US to use it.

Ok, replace the inf files in CD_Root, then start PEbuilder and press F5 to just rebuild the ISO.

I replaced the inf files in my CD_Root, rebuilt the CD from the new ISO image and I still have the same problem with the Intel 8255x-based PCI Ethernet adapter not coming up.

OK, one last feeble try - use the *.sys and *.dll files from this zip file to overwrite any in drivers under CD_Root -- then rebuild your ISO only one last time.

Drivers

Unfortunatly it didn't work but I found a way to make it work and here is some info.

I brought up Device Manager using Computer Management as soon as the UBCD4WIN 2.55 with 1.6 drivers booted and watched the network device load. It looks like it loads when the prompt Do You Want to Start Network Support Now? comes up and you click ok. After this is done, it is now a vaild device and my DSL modem shows a 100MB connection. When the next screen comes up, PE Network Configuration, you pick your network settings and click OK, it errors out the network device. Only time it worked cleanly was with vanilla BartPE build.

Actually I am typing this reply via the project right now and have the PE Network Configurator still opened. I will save this post and click CLOSE to see if I am still up and edit my post.

...I am still alive so if you just hit close, the network connection, at least with the values I need right now, still works.

Rock on guys, hope this helps towards a possible fix,
NRM

P.S. Just tested my 2.55/2.01 and 2.55/original 1.6 disks and they work the same way. Actually I like the BTS driver pack CD better because it brings up many more accurate drivers. Of course, my IRcc driver still doesn't load. Is infrared even supported?

I never really thought about it. Which means I did nothing to try and support it.

So the PE Network Configurator is the problem?

Yes, after network support is loaded and PE Network Configurator asks for your installed network adaptor settings, you click ok, the network adapter errors out and you than see it in Task Manger with a yellow error mark.

I was having the same problem with my Intel 8255x-based PCI Ethernet adapter. It appears that the initial detected driver used E100B325.SYS from WinXPSP2 (Version 5.41.22.0) and then the PE Network Configurator is changing to E100B325.SYS driver from X:\I386\SYSTEM32\DRIVERS (Version 8.0.15.0 from UBCD4WinDriversV16.exe) at which point the system wants to reboot and the NIC is no longer functional.

I created UBCD4Win V2.55 without either the LAN driver pack nor NET drivers from V1.6 driver download and the Version 5.41.22.0 E100B325.SYS driver was loaded and the NIC worked fine after using the PE Network Configurator.

After rerunning pebuilder.exe using the NET drivers from UBCD4WinDriversV16.exe, I then copied the 5.41.22.0 Version of the E100B325.SYS driver into ..\BartPE\I386\SYSTEM32\DRIVERS directory (i.e., replacing the newer version of the driver) and recreated the ISO file using F5 after starting pebuilder.exe. Again the older version of the E100B325.SYS driver worked fine after using the PE Network Configurator.

Is there an echo in here?

I just rebuilt my UBCD4WIN V2.55CD w V1.6 drivers and disabled both of the 911 plugins and everything now works fine with Intel Integrated NIC Pro/100 VE. THe E100B325.SYS version on the CD is 8.0.21. My old UBCD4WIN V2.2 build from last December uses V5.14.34.00 of the E100B325.SYS driverand it works fine. I also built a plain vanilla BartPe and it also works. Check out the thread from Hemo2 who also disabled one of the 911 plugins for a solution:
http://www.ubcd4win.com/forum/index.php?showtopic=2904


Also see my thread about this same issue at:

http://www.ubcd4win.com/forum/index.php?showtopic=3298&st=0

Net Net: The issue appears to be with the 911 Plugins not the driver versions and not the PE Network Configurator. Since I don't need the 911 Plugins I'll live with out them until some figures out what the issue is.

P.S. I'm posting this from my laptop using the UBCD4WIN V2.55 with the 1.6 Lan drivers and the BTS CPU and Mass Storage Driver Packs.