UBCD4Win Forums > Help with NEW BTS 1.0+ Drivers Release!

Full Version: Help with NEW BTS 1.0+ Drivers Release!

UBCD4Win Forums > Main Forum: UBCD4Windows - Support > Drivers

Pages: 1, 2, 3

grapeman

Nov 11 2005, 03:56 PM

First sorry about double post. Poor internet connectivity on my end, it appeared my first submit didn't go through, but alas it did.

Thomasjk: Thanks for your information. Yes indeed it appears the 911exp-mmc-eventlog plugin was indeed the problem I was running into. I tested with both V1.6 drivers and LAN BTS Driver Pack and both produced a fully functional Intel Pro/100 Network Connection NIC. I left the 911exp-mmc plugin enabled with apparently no bad impacts. Thanks for the pointer.

webmedic

Nov 11 2005, 04:12 PM

thanks to all who have helped troubleshoot this issue as I'm not sure i could have done much on the driver end of things.

Also grapeman I took care of the double post for you.

NRM

Nov 12 2005, 02:28 AM

QUOTE (grapeman @ Nov 11 2005, 03:56 PM)

I tried disabling the two 911 plugins and my Intel NIC also came up with no errors. Tried just disabling the 911exp-mmc-eventlog plugin and that worked too. Without these plugins, we lose the ability to run Computer Management such as Device Manager which is a helpful troubleshooting tool. Unknown Devices and System Information for Windows can help fill the void.

P.S. I still have problems creating the ISO file. Only way I can make it work is to run autoinstall.cmd from C:\pebuilder313 because Pebuilder doesn't output an ISO file. Than, and only then do I see all the BTS drivers created and goes through several steps up to the successful burning process.

LittlBUGer

Nov 12 2005, 08:36 PM

Yes, I think we need to remove the 911 plugins for now as they seem to be causing more problems then anything else. As far as the autoinstall.cmd file, that is extracted as part of the new driver package and SHOULD be ran after successful extraction of the drivers package automatically. It seems many people are having problems with this though, which is strange as it's worked perfectly on all of the systems I've tested it on (same with beta testers). So, what we might have to do is add this "extra" step to the instructions we currently have up. I'll try to do that right now. Thanks.

SteelTrepid

Nov 12 2005, 08:44 PM

Actually there are just a few bugs with the MMC eventlog plugin. Hilander pointed out a few fixes for the plugin and they are in the current beta release. Only bad thing is I don't think any of our beta testers have had this problem.

Would anyone that had problems with the plugin enabled be interested in testing the beta?? Please PM me and we will discuss it. I would really like to have the fixes confirmed before another version of the project is released.

Chrismartin76

Nov 13 2005, 11:08 PM

Hello,
I'm new to UBCD4Win. I just created a cd for the first time today and it seems to be working fine. I'd like to create a cd with the drivers too, though, and the directions on the howto page state "new instructions will be posted soon."
So is there a problem that everyone has been having? And what are the usual instructions for adding the drivers -- I presume you have to unzip the archive and place the files in the same directory as everything else.

Thanks,
Chris

QUOTE (LittlBUGer @ Oct 31 2005, 01:29 PM)

Hello all. I just put this topic here for those wanting to post problems with the new drivers. Please let me know of any issues you come into. Thanks.

SteelTrepid

Nov 13 2005, 11:13 PM

Please check out this post for the instructions:
http://www.ubcd4win.com/forum/index.php?showtopic=3208

Some people have been having problems, so please just read the instructions carefully. If you happen to run into problems, please post.

Chrismartin76

Nov 15 2005, 11:16 PM

Thanks. Everything worked OK, except that when I booted using the CD I couldn't see my hard drive. It's a Samsung SATA drive, partitioned into two.
I tried 'Install Devices' and I still couldn't see it. I ran 'Force Install Devices' and about midway through the process, I got a BSOD with irql_not_less_or_equal (which is not surprising considering my PC has a fondness for that message).
Any suggestions? I searched the forum archive but didn't see anything helpful.
Best,
Chris

QUOTE (SteelTrepid @ Nov 14 2005, 12:13 AM)

LittlBUGer

Nov 15 2005, 11:57 PM

Your computer has a "fondness" for that message to begin with? Then you've had some sort of hardware problem all along. Are you running your system as ACPI or some other way? Some other info can be found here: http://www.tweaksforgeeks.com/IRQL_NOT_LESS_OR_EQUAL.html

Chrismartin76

Nov 17 2005, 06:50 PM

I'm familiar with that page. I've tried a lot of things and have given up. It only happens about once a month so it's not a big nuisance anyway. I think I figured out what when wrong the UBCD - it was just a slip on my part.

Chris

QUOTE (LittlBUGer @ Nov 16 2005, 12:57 AM)

euser4life

Nov 23 2005, 08:18 AM

Hello everyone. This is my first post here and first off I want to thank everyone that makes this project possible. It is the greatest!!!

I did have a silly question or request on the instructions for step three on Official UBCD4Win BTS Drivers V. 1.0+ Installation Instructions:

QUOTE

3.) Next, copy (NOT extract) all of the BTS Driver Packs (the original .7z files and the .exe file for the BASE pack) that you downloaded into their appropriate corresponding folders in your pebuilder/plugin/BTSdrivers folder. This means that the BASE pack would go into the driverpack_base folder, the Chipset pack would go into the driverpack_chipset folder, so on and so forth.

I was hoping that a simple clarification could be made on the folder order that is needed. Is the folder pebuilder/plugin/BTSdrivers folder needed and then within that folder a separate folder for each driver pack or is it that pebuilder/plugin/"individual_driverpack" folder needed.

Thanks for everyone's hard work.

euser4life

Nov 23 2005, 10:25 AM

EDIT: Sorry for my misunderstanding. I just realized that the folders are automatically created and was previously looking in the wrong directory.

teraside

Jan 25 2006, 10:00 AM

Not getting my built in LAN on Nforce 4 4x recognised

LittlBUGer

Jan 25 2006, 10:47 AM

As stated many, many, many times before, nVidia drivers are a pain in the ass to get working properly (at least with how pebuilder incorporates them using our standard method). The good news is that when we release drivers 2.0, which has been completely revamped, this problem should be solved and ALL nVidia should be recognized! Though, 2.0 may not come out for a while longer yet.

Deacon

Jan 25 2006, 05:13 PM

are you looking for any beta testers for 2.0 driver pack?

Would be very willing to help and have quite a variety of nics, and raid cards and do use nforce (2, 3 and 4) motherboards.

Thanks

LittlBUGer

Jan 25 2006, 06:46 PM

It's not fully ready yet to even be beta tested. We have some "alpha" builds I guess you could call them, but we need to finalize and update some things first before we can all beta test a bunch. Thanks though and we'll let ya know.

alm

Jan 29 2006, 07:47 AM

I think I found a problem with the BTS drivers add-on when run from a network drive. My ubcd4win directory is on a network drive (Samba server), the directory is y:\pebuilder319 (no spaces). I use pebuilder 3.19 (ZIP file), renamed the plugin folder, and downloaded the UBCD4Win and UBCD4WinBTSDrivers files and extracted them in the pebuilder directory. I put the driverpacks from driverpacks.net in the correct folders (not extracted), and ran pebuilder from Windows XP SP2 Pro, all according to the instructions on ubcd4win.com and the BTS driver instructions on this forum.

However, the resulting ISO failed to boot with the error that the system couldn't find aftx2k.sys in the textmode part of the boot process. This file indeed wasn't on the CD or in the BARTPE folder, but it was referenced in TXTSETUP.SIF. After some debugging I found out that the rename in plugin/BTSdrivers/driverpack_base/autorun9_BTSDrivers.cmd failed on some of the files with a permission denied error.

Some of the files in the driverpacks are marked read-only. Although renaming a read-only file works fine on the local NTFS partition, it fails on the network drive. I'm not sure if this is because of Samba or the Windows client, it doesn't occur locally on the Windows client or the Unix server.

Since 7za doesn't have an option to ignore the read-only attributes as far as I know, and I didn't want to modify the driverpacks, I added these lines to autorun9_BTSDrivers.cmd just after the driverpacks are extracted (just before 'renaming extra files'):

CODE

:: Remove read-only attribute since rename fails for read-only files on network shares and
:: some of the files in the BTS unattended archives are marked read-only.
attrib -r %strtemp%\*.* /s > NUL 2>&1

The ISO that I built after this modification worked without errors.

Alson

martinr

Mar 5 2006, 07:29 AM

BTS has released a new version of the Mass Storage DriverPack - v 6.02.1. There is also a new BASE pack - v6.02.5.

These can be used in conjunction with the BTSDrivers download v101, but with one amendment to deal with additional duplicated file names in the pack.

In the driverpack_base section of the BTSdrivers plugin, there is a file called autorun9_BTSDrivers.cmd. In that file you need to replace this

CODE

If EXIST "%strtemp%\mass\D\M\AD\1\hpt3xx.sys" ren "%strtemp%\mass\D\M\AD\1\hpt3xx.sys" ahpt3xx.sys
If EXIST "%strtemp%\mass\D\M\AD\1\ahpt3xx.sys" xcopy "%strtemp%\mass\D\M\AD\1\ahpt3xx.sys" "%strtemp%\*.sys"  /H /R /Y

If EXIST "%strtemp%\mass\D\M\H\1\R\hpt3xx.sys" ren "%strtemp%\mass\D\M\H\1\R\hpt3xx.sys" rhpt3xx.sys
If EXIST "%strtemp%\mass\D\M\H\1\R\rhpt3xx.sys" xcopy "%strtemp%\mass\D\M\H\1\R\rhpt3xx.sys" "%strtemp%\*.sys"  /H /R /Y

If EXIST "%strtemp%\mass\D\M\AD\6\C\ADPU320.sys" ren "%strtemp%\mass\D\M\AD\6\C\ADPU320.sys" AADPU320.sys
If EXIST "%strtemp%\mass\D\M\AD\6\C\AADPU320.sys" xcopy "%strtemp%\mass\D\M\AD\6\C\AADPU320.sys" "%strtemp%\*.sys"  /H /R /Y

If EXIST "%strtemp%\mass\D\M\P\2\A\fasttx2k.sys" ren "%strtemp%\mass\D\M\P\2\A\fasttx2k.sys" aftx2k.sys
If EXIST "%strtemp%\mass\D\M\P\2\A\aftx2k.sys" xcopy "%strtemp%\mass\D\M\P\2\A\aftx2k.sys" "%strtemp%\*.sys"  /H /R /Y

If EXIST "%strtemp%\mass\D\M\D\cercsr6.sys" ren  "%strtemp%\mass\D\M\D\cercsr6.sys" afamgt.sys
If EXIST "%strtemp%\mass\D\M\D\afamgt.sys" xcopy "%strtemp%\mass\D\M\D\afamgt.sys" "%strtemp%\*.sys"  /H /R /Y

with the following:

CODE

If EXIST "%strtemp%\mass\D\M\3\1\3wareDrv.sys" ren "%strtemp%\mass\D\M\3\1\3wareDrv.sys" 3ware9k.sys
If EXIST "%strtemp%\mass\D\M\3\1\3ware9k.sys" xcopy "%strtemp%\mass\D\M\3\1\3ware9k.sys" "%strtemp%\*.sys"  /H /R /Y

If EXIST "%strtemp%\mass\D\M\3\2\3WAREDRV.sys" ren "%strtemp%\mass\D\M\3\2\3WAREDRV.sys" 3ware78k.sys
If EXIST "%strtemp%\mass\D\M\3\2\3ware78k.sys" xcopy "%strtemp%\mass\D\M\3\2\3ware78k.sys" "%strtemp%\*.sys"  /H /R /Y

If EXIST "%strtemp%\mass\D\M\AD\1\hpt3xx.sys" ren "%strtemp%\mass\D\M\AD\1\hpt3xx.sys" ahpt3xx.sys
If EXIST "%strtemp%\mass\D\M\AD\1\ahpt3xx.sys" xcopy "%strtemp%\mass\D\M\AD\1\ahpt3xx.sys" "%strtemp%\*.sys"  /H /R /Y

If EXIST "%strtemp%\mass\D\M\H\1\R\hpt3xx.sys" ren "%strtemp%\mass\D\M\H\1\R\hpt3xx.sys" rhpt3xx.sys
If EXIST "%strtemp%\mass\D\M\H\1\R\rhpt3xx.sys" xcopy "%strtemp%\mass\D\M\H\1\R\rhpt3xx.sys" "%strtemp%\*.sys"  /H /R /Y

If EXIST "%strtemp%\mass\D\M\H\7\hpt374.sys" ren "%strtemp%\mass\D\M\H\7\hpt374.sys" rr404.sys
If EXIST "%strtemp%\mass\D\M\H\7\rr404.sys" xcopy "%strtemp%\mass\D\M\H\7\rr404.sys" "%strtemp%\*.sys"  /H /R /Y

If EXIST "%strtemp%\mass\D\M\AD\6\C\ADPU320.sys" ren "%strtemp%\mass\D\M\AD\6\C\ADPU320.sys" AADPU320.sys
If EXIST "%strtemp%\mass\D\M\AD\6\C\AADPU320.sys" xcopy "%strtemp%\mass\D\M\AD\6\C\AADPU320.sys" "%strtemp%\*.sys"  /H /R /Y

If EXIST "%strtemp%\mass\D\M\P\2\A\fasttx2k.sys" ren "%strtemp%\mass\D\M\P\2\A\fasttx2k.sys" aftx2k.sys
If EXIST "%strtemp%\mass\D\M\P\2\A\aftx2k.sys" xcopy "%strtemp%\mass\D\M\P\2\A\aftx2k.sys" "%strtemp%\*.sys"  /H /R /Y

If EXIST "%strtemp%\mass\D\M\S\5\A\Si3112r.sys" ren "%strtemp%\mass\D\M\S\5\A\Si3112r.sys" ati3112r.sys
If EXIST "%strtemp%\mass\D\M\S\5\A\ati3112r.sys" xcopy "%strtemp%\mass\D\M\S\5\A\ati3112r.sys" "%strtemp%\*.sys"  /H /R /Y

It then builds and runs fine in UBCDW v 2.6.

There is only one problem. The DriverPack does not seem to get along with XPE. A disk including both the Driverpack and XPE throws up an "Insufficient memory for mup.sys" error when it runs, and then it crashes. Nothing to worry UBCDW users, as XPE is not used.

It may be a good idea to update the v 101 download to include the new script above.

I hope that this is useful and saves someone some work.

Martin

LittlBUGer

Mar 5 2006, 10:48 PM

We wont be updating our BTS drivers package as when 3.0 of the project comes out, we'll have a completely new drivers method which sort of combines both the BTS drivers and our own but in a much smaller package that we can distribute ourselves. It has been in testing for quite some time. Please stick around for that release. Thanks.

raummusik

Mar 7 2006, 10:31 AM

QUOTE (LittlBUGer @ Mar 6 2006, 04:48 AM)

ah nice to know. i finally saw that there are new driverpacks out too. and i got a problem cause graphics_c pack is out too and the 1.01 dont "knows" the c-pack

.. but in the bts_BASE pack c-pack is mentioned via some script and so on ... any ideas when this will be fixed in 1.01 ?

cu

LittlBUGer

Mar 7 2006, 11:03 AM

Errr... as you just quoted my previous response, we WONT be updating the BTS drivers package that we have. We'll have a completely new drivers method once version 3.0 of the project comes out, just like I metnioned in your new topic.

jdlugosz

May 28 2007, 02:11 PM

I just built UBCD4Win with the drivers version 2.0.

When I tried it on one of my machines, I got an error "Not enough memory to run SiSraid1.sys" or something to that effect, and pressing a key restarts the system (with the same problem).

This makes me worry that having all the drivers will be just as much of an issue as not having them. That is, it works on some machines but not others. Worse, not booting as opposed to not seeing some of the HDs or the network!

Is there some kind of "safe mode" that can be used on the same boot CD?

In general, I wonder: does it actually try loading every single driver, and let them fail if they don't see the right hardware? I thought the P&P info points to the right one. I notice that it is nicely pre-compiled as part of the build process.

--John

LittlBUGer

May 28 2007, 04:48 PM

When you build the UBCD4Win with my 2.0 driver pack, delete the SCSIAdapter folder and use the new BTS driver packs (which right now only include Mass Storage devices) together. That way, you shouldn't have any problems.

hilander999

May 28 2007, 09:12 PM

The information in this thread is very out of date and mostly obsoleet, however it still remains as a good source of information on the subject so it will not be removed but doea need to be closed now.

Please reffer to the "New BTS Driverpacks" method posted in the announcements section, or start a new thread for any questions/sugestions you may have.

THANX.

THIS THREAD IS NOW CLOSED.

This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.