BartPE and UBCD4win Q & A (Page 1 of 2)

Jeff, it could be disheartening, but yes, the silence was deafening.

I am in favour for a subforum, tho.
this function is a real godsend and a LOT of work was put into it.

You REALLY have no idea. lol

When I posted the initial bartpe version (including the plugin) we linked to the file directly at ubcd4win.com so we could monitor the number of people who have downloaded the file.

The post was made on the 5th and the file has recieved 768 hits since then, BUT with the server crash at our forum, we lost 5 days worth of data, so the 768 is not a reliable number, it is more of a minimun number. So it's really more like 768 downloads in 8 days, which I would say is a fair number and does represent a unique new user-base for driverpacks.net also.

Take that into account, and then release that NO ONE has posted that it was broken or did not work (unless they needed a driver not included in the pack) then I would say that while the silence was certainly deafening, it's also a very good sign that our approach to driver support for pebuilder has worked very well to date.

It certainly would be nice to hear more responce from the users who have tried it, but you will seldome have a new user, actually join any formu, just to say that something has worked. Where as if it had been a bad release, I'm almost certain that all 768 people would have stepped up and told us to FIX IT.

BTW: A sub-forum here for pebuilder support would be a good idea concidering that there are already postings in other areas fo it and I'm sure more will follow. Keeping them together would be a bennefit to everyone.

Here is another point we do agree on.

If the release was causing problems, all three forums would have been flooded with complaints by now, so concidering that there has been nothing but good feedback, I would say that simply adding the new section to the up-comming forum is perfect.

With more additions, more questions. The release (as I posted it) is NEARLY IDIOT PROOF, at least to the best of my knowlage it was setup to be used by anyone, even when basic computer skills are absent.

Last edited by hilander999 (2007-04-19 09:30:54)

Hi everyone, I've got a Compaq ML370 with a Smart Array 431 controller. I am running Bart's PE with Pebuilder 3.1.10a, Windows XP slipstreamed to SP2.

With the kind help of others, I've successfully slipstreamed the text mode mass storage drivers from driverpack.net into Bart's PE. But even after this, I still can't get it to work with the SmartArray 431 controller. The white progress bar gets to the end and it changes from "Starting Bart PE..." to "Please Wait...." and sits there....

Before the driverpack.net drivers, I tried using the drivers from Robdvb, with the same results....

I'm a technical person, and I tell ya, this is driving me crazy! Especially after having a default build of Bart's PE work with a Proliant 1600 with a SmartArray 221 controller work with no problems..... ARgh!!!!

Any help is greatly appreciated.

Thanks,

Jaak, I'm a bit confused.... I downloaded the driver from the following link in your other post. It says the driver was added to this test pack. Should I wait until you're done testing and make an official release????

-------------------------------------------------------------------------------------------
http://dev.driverpacks.thesneaky.com/dr … 32_7085.7z

926451a101b6747c28a3e1b50193eb7f DP_MassStorage_wnt5_x86-32_7085.7z

added Compaq Smart Array 4200/4250ES/431/LC2 Controller at [C-3]

------------------------------------------------------------------------------------------

teehee
HP/compaq driver search is always a bit of h*ll, but I just found the 2003 driver..

edit, which is the 2000 I already had..

Last edited by Jaak (2007-08-13 00:56:20)

the 2003 has different xml files, and in the XML files I read that it adds txtsetup.oem for XP.

the SYS file and INF file is same, tho.
Since we do not use the installer, we do not need the XML, but I will put this txtsetup.oem file in our next test version.

you know, I started to wonder about whether thic compaq PCI card has a bootrom.

edit... (I saw several ROM flash files mentioned for it, but still wonder.)
That is what people using this hardware can tell us.
I'll try to not make guinea pigs out of you, but TESTS have to be done by people who have the kit.

Jmicron, Highpoint, and the other files have to be tested as well.
Helmi could test the DELL PERC/CERC to a degree.. (XP did not like it at first, but I had goofed on that one.. Did not yet get report on the corrected DELL version.)

Last edited by Jaak (2007-08-13 12:24:34)

Ok. I wasn't sure, a card BIOS is a ROM, but I did not find descriptions which mentioned BootROM.

All in all, if it works for servers, it is better than not having it, if it works for 2000/2003 AND XP, then everybody is happy.

I meant the mass storage drivers by Text mode...

XP sp3 was released and the TEAM need feedback on the PE tool more than ever.
Every issue caused by DriverPack MassStorage for ubcd4win has to get a fix.

something like the HFslip report in bugtracker is something I can not test, because I am like a mom and pop store test person, with a few live machines at best.. No network stuff, no sysprep.