Sign In
Register
Help
This topic is locked
Help with NEW BTS 1.0+ Drivers Release! Look and Post HERE!
#1
LittlBUGer 
- Main Mirror/Here Since Beginning
-
- Group: Members
- Posts: 4,698
- Joined: 27-May 04
- Location:MT, USA
- Interests:Computers and stuff...<br /><br />:-)
Posted 31 October 2005 - 12: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.
"Only two things are infinite, the universe and human stupidity, and I'm not sure about the former." - Albert Einstein
"Computers are really strange - first everything works fine, then something goes terribly wrong and nothing works, and then - like a thunderbolt from a clear sky, everything is back to normal again. It's like nothing ever happened. Like the computer were female." - Unknown
"Some people say that I must be a terrible person, but it's not true. I have the heart of a young boy. In a jar on my desk." - Stephen King
"If there is anything the nonconformist hates worse than a conformist, it's another nonconformist who doesn't conform to the prevailing standard of nonconformity." - Bill Vaughan
"Microsoft Windows [n.]: A thirty-two bit extension and GUI shell to a sixteen bit patch to an eight bit operating system originally coded for a four bit microprocessor and sold by a two-bit company that can't stand one bit of competition." - Unknown
"When a newly married couple smiles, everyone knows why. When a ten-year married couple smiles, everyone wonders why." - Unknown
MultiQuote
#2
Hemo2
- Regular Member
-
- Group: Members
- Posts: 112
- Joined: 13-August 04
Posted 31 October 2005 - 02:18 PM
I'm not having any problems at this time since I have not tried this new way of doing the drivers, but I do have a few questions that I'd like to clear up before giving it a try.
Is the UBCD4WIN project going to become 'reliant' on using this new way of doing the drivers? Or will I eventually be forced to choose between changing to this new way for drivers in the UBCD4Win project or moving over to using a straight BartPE build? (i.e. - Can I ignore this way of adding the BTS drivers into my UBCD4Win CD and just continue to add standard XP drivers under the \Drivers\Net folder like I do now? Or are there going to be hardware plugins that UBCD4Win will come with that require the BTS drivers to be included?)
I always build a 'combo' CD that combines UBCD & UBCD4Win. I don't believe it works to make a combo cd by checking the "Create ISO Image" option in PEBuilder so I always run the 'mkisofs' command manually after PEBuilder has combined all the files/folders together. Do I understand the above explanation correctly in that I must check the option to build an ISO image? If I do and attempt to then make my own .ISO manually to build my combo cd, will the combo cd I make work anymore or will only the .ISO created by PEBuilder function properly now? Basically if I can't make a combo CD, then the new drivers are a killer for me and I can't continue to use this project.
I probably wouldn't know until I tried it, but if the new drivers explode the size of the project this much, then is it feasible that there may not even be room on my CD to make my combo CD?
Hmm, any estimates on how much more time is added to the bootup process? I currently make the CD for our organization and every tech that uses it is frustrated with how long it takes to bootup. (Some more than others.) If it takes even longer to bootup, I can forsee some of the techs deciding to not use it anymore and attempting to do things a different way. When you say "all" of your hardware is recognized, I'm not sure exactly what hardware is going to be recognized that isn't already. Is it mostly just that there will be drivers available to support all the different video cards, etc. or is it lower level system drivers that don't currently load in the UBCD4Win project that would now load properly and give some benefit for doing it this way?
Finally, please don't take my message the wrong way. Believe me when I say that I can't thank you enough for your hard work on this project as I know how much effort is required. I'm just trying to get a feel for if the new way of doing drivers for this project is going to provide any benefit on my end since we mainly just need to bootup a pc to the network and drop ghost images. And if there will be plugins or other functionality in the UBCD4Win project that require this new way, I'd like to weigh the benefits vs. the drawbacks of continuing to use UBCD4Win or consider switching to a generic BartPE build.
LittlBUGer, on Oct 31 2005, 12:29 PM, said:
1.) Download the UBCD4Win Drivers, and any of the BTS Drivers Packs that you want to include. Currently, we support all of the packs EXCEPT for the Sound one. The BASE pack is REQUIRED. In order to get the driver packs, go to the site in the link above, go to Projects -> DriverPacks and then select the ones you want to get. Of course, store all of these files in a folder of choice.
Is the UBCD4WIN project going to become 'reliant' on using this new way of doing the drivers? Or will I eventually be forced to choose between changing to this new way for drivers in the UBCD4Win project or moving over to using a straight BartPE build? (i.e. - Can I ignore this way of adding the BTS drivers into my UBCD4Win CD and just continue to add standard XP drivers under the \Drivers\Net folder like I do now? Or are there going to be hardware plugins that UBCD4Win will come with that require the BTS drivers to be included?)
LittlBUGer, on Oct 31 2005, 12:29 PM, said:
4.) Run pebuilder.exe as you normally would configuring the appropriate settings. The ‘Create ISO Image’ option MUST be checked or this process will not work. You will also notice several extra ‘Autobuild’ entries in the ‘Plugins’ area. This is due to the new ‘autobuild’ plugin that has been included to help assist with the drivers installation. These new entries are normal and it is highly recommended that you DON’T modify or disable these extra entries. Yet, if you did not include all driver packs, then you must disable those entries (driver packs) that are not included. The same goes for if you did include all driver packs, but only want a few to actually be on the final CD. The Intel Graphics pack is automatically included so please don’t worry about that one. You may enable/disable any of the other regular plugins though, as you choose. The building process will take longer now depending on how many driver packs you included. You may see several extra command prompt windows pop up. This is all normal and you can ignore them and let them finish automatically.
I always build a 'combo' CD that combines UBCD & UBCD4Win. I don't believe it works to make a combo cd by checking the "Create ISO Image" option in PEBuilder so I always run the 'mkisofs' command manually after PEBuilder has combined all the files/folders together. Do I understand the above explanation correctly in that I must check the option to build an ISO image? If I do and attempt to then make my own .ISO manually to build my combo cd, will the combo cd I make work anymore or will only the .ISO created by PEBuilder function properly now? Basically if I can't make a combo CD, then the new drivers are a killer for me and I can't continue to use this project.
LittlBUGer, on Oct 31 2005, 12:29 PM, said:
5.) Once the building process is complete, you should now have a .iso file ready to be burned and a fully-working UBCD4Win CD close at hand! You’re basically done!
Something you may now notice is that, if you include ALL of the driver packs, with a vanilla build of the UBCD4Win, your .iso file is now around 650MB! This is because of the huge amount of drivers included since when extracted, the drivers take up over 500MB! Though, most of this “bloat” is from the Graphics driver packs so if you don’t include them, your final .iso file size should be significantly smaller.
Something you may now notice is that, if you include ALL of the driver packs, with a vanilla build of the UBCD4Win, your .iso file is now around 650MB! This is because of the huge amount of drivers included since when extracted, the drivers take up over 500MB! Though, most of this “bloat” is from the Graphics driver packs so if you don’t include them, your final .iso file size should be significantly smaller.
I probably wouldn't know until I tried it, but if the new drivers explode the size of the project this much, then is it feasible that there may not even be room on my CD to make my combo CD?
LittlBUGer, on Oct 31 2005, 12:29 PM, said:
When you finally boot from the CD, you will also notice that the overall loading time has increased, especially once it gets into the Windows-like interface. This is due to the new ‘HWPnP’ plugin that has been included. It should automatically start after the RAMDisk is sized and automatically install all related drivers on your system for the hardware that it finds. Though this may take a while, it is well worth the wait as you now should have ALL of your hardware recognized!
Hmm, any estimates on how much more time is added to the bootup process? I currently make the CD for our organization and every tech that uses it is frustrated with how long it takes to bootup. (Some more than others.) If it takes even longer to bootup, I can forsee some of the techs deciding to not use it anymore and attempting to do things a different way. When you say "all" of your hardware is recognized, I'm not sure exactly what hardware is going to be recognized that isn't already. Is it mostly just that there will be drivers available to support all the different video cards, etc. or is it lower level system drivers that don't currently load in the UBCD4Win project that would now load properly and give some benefit for doing it this way?
Finally, please don't take my message the wrong way. Believe me when I say that I can't thank you enough for your hard work on this project as I know how much effort is required. I'm just trying to get a feel for if the new way of doing drivers for this project is going to provide any benefit on my end since we mainly just need to bootup a pc to the network and drop ghost images. And if there will be plugins or other functionality in the UBCD4Win project that require this new way, I'd like to weigh the benefits vs. the drawbacks of continuing to use UBCD4Win or consider switching to a generic BartPE build.
#3
LittlBUGer
- Main Mirror/Here Since Beginning
-
- Group: Members
- Posts: 4,698
- Joined: 27-May 04
- Location:MT, USA
- Interests:Computers and stuff...<br /><br />:-)
Posted 31 October 2005 - 02:49 PM
@ALL
Please ignore DigiWiz's post above. We cannot do as he stated which is why I removed his post content.
@Hemo2
Here's some answers...
1.) No, the project isn't going to be reliant on this new method just as it wasn't reliant on the old method. This new method just allows for MANY MANY more drivers and support to be added to the project that isn't currently possible doing it the old way. That is why I switched how everything works, because now all hardware is supported, unlike my old drivers (nVidia rings a bell...). The new way also works with just a BartPE vanilla build (no UBCD4Win stuff) and yes, you can still add your own drivers to the drivers folder, but if you also use the new V. 2.0 drivers, you may overwrite what's already there, or vice versa.
2.) Checking the box to make the ISO is only required to force some extra scripts to run in order to finish adding the drivers properly. The main build folder that's created with all of the files should still work if you wanted to use that for the combo CD. Thus, yes, you have to use that option, and no, you don't have to use the .iso created, you can use the build folder with all of the files in it for your own purposes (such as for the combo CD). I'll update the instructions about this...
3.) Like it says in the post, only add the ones you really want, and don't use the graphics ones and then this shouldn't be a problem. Or, you can use a DVD-R if needed.
4.) Loading time will be different on each system (of course) due to different hardware. And what this is doing when it's installing the drivers for everything is not only allowing the CD to recognize all simple hardware like graphics, etc., but the stuff that matters, like SATA RAID arrays or other more "non-standard" hardware that we hear so much about from people that the "old" drivers don't support. Without this, it may or may not work. All I know is, this has worked on several systems I've tested now that it didn't work before with the old drivers.
5.) No problem, I understand your concern, but if you are simply just doing images and whatnot, then the UBCD4Win maybe isn't really what you need. In any case, the drivers package is just to help make the CD one that works universally, no matter what hardware, and for that to happen, all of this must take place. Of course, for advanced users such as yourself, you can just add only what you want or need and not have a problem. For people like myself who work on every comptuer under the sun, I need the best and widest array of hardware support available so that I don't have to worry about switching CDs or adding new drivers, etc.
Anyway, I hope that answers your questions. Please let me know if it doesn't and if you have anything else. Thanks.
Please ignore DigiWiz's post above. We cannot do as he stated which is why I removed his post content.
@Hemo2
Here's some answers...
1.) No, the project isn't going to be reliant on this new method just as it wasn't reliant on the old method. This new method just allows for MANY MANY more drivers and support to be added to the project that isn't currently possible doing it the old way. That is why I switched how everything works, because now all hardware is supported, unlike my old drivers (nVidia rings a bell...). The new way also works with just a BartPE vanilla build (no UBCD4Win stuff) and yes, you can still add your own drivers to the drivers folder, but if you also use the new V. 2.0 drivers, you may overwrite what's already there, or vice versa.
2.) Checking the box to make the ISO is only required to force some extra scripts to run in order to finish adding the drivers properly. The main build folder that's created with all of the files should still work if you wanted to use that for the combo CD. Thus, yes, you have to use that option, and no, you don't have to use the .iso created, you can use the build folder with all of the files in it for your own purposes (such as for the combo CD). I'll update the instructions about this...
3.) Like it says in the post, only add the ones you really want, and don't use the graphics ones and then this shouldn't be a problem. Or, you can use a DVD-R if needed.
4.) Loading time will be different on each system (of course) due to different hardware. And what this is doing when it's installing the drivers for everything is not only allowing the CD to recognize all simple hardware like graphics, etc., but the stuff that matters, like SATA RAID arrays or other more "non-standard" hardware that we hear so much about from people that the "old" drivers don't support. Without this, it may or may not work. All I know is, this has worked on several systems I've tested now that it didn't work before with the old drivers.
5.) No problem, I understand your concern, but if you are simply just doing images and whatnot, then the UBCD4Win maybe isn't really what you need. In any case, the drivers package is just to help make the CD one that works universally, no matter what hardware, and for that to happen, all of this must take place. Of course, for advanced users such as yourself, you can just add only what you want or need and not have a problem. For people like myself who work on every comptuer under the sun, I need the best and widest array of hardware support available so that I don't have to worry about switching CDs or adding new drivers, etc.
Anyway, I hope that answers your questions. Please let me know if it doesn't and if you have anything else. Thanks.
"Only two things are infinite, the universe and human stupidity, and I'm not sure about the former." - Albert Einstein
"Computers are really strange - first everything works fine, then something goes terribly wrong and nothing works, and then - like a thunderbolt from a clear sky, everything is back to normal again. It's like nothing ever happened. Like the computer were female." - Unknown
"Some people say that I must be a terrible person, but it's not true. I have the heart of a young boy. In a jar on my desk." - Stephen King
"If there is anything the nonconformist hates worse than a conformist, it's another nonconformist who doesn't conform to the prevailing standard of nonconformity." - Bill Vaughan
"Microsoft Windows [n.]: A thirty-two bit extension and GUI shell to a sixteen bit patch to an eight bit operating system originally coded for a four bit microprocessor and sold by a two-bit company that can't stand one bit of competition." - Unknown
"When a newly married couple smiles, everyone knows why. When a ten-year married couple smiles, everyone wonders why." - Unknown
#4
Hemo2
- Regular Member
-
- Group: Members
- Posts: 112
- Joined: 13-August 04
Posted 31 October 2005 - 02:52 PM
I just thought of another question. How would I add drivers to the project for those drivers that aren't included in the BTS driver packs? Can you use the BTS driver pack and new way of incuding drivers and still continue to include drivers under the \Drivers\Net and \Drivers\SCSIAdapter folders? Or can you only use the BTS way of including drivers now?
#5
LittlBUGer
- Main Mirror/Here Since Beginning
-
- Group: Members
- Posts: 4,698
- Joined: 27-May 04
- Location:MT, USA
- Interests:Computers and stuff...<br /><br />:-)
Posted 31 October 2005 - 02:56 PM
Hemo2, on Oct 31 2005, 12:52 PM, said:
I just thought of another question. How would I add drivers to the project for those drivers that aren't included in the BTS driver packs? Can you use the BTS driver pack and new way of incuding drivers and still continue to include drivers under the \Drivers\Net and \Drivers\SCSIAdapter folders? Or can you only use the BTS way of including drivers now?
I answered that in my first answer above.
"Only two things are infinite, the universe and human stupidity, and I'm not sure about the former." - Albert Einstein
"Computers are really strange - first everything works fine, then something goes terribly wrong and nothing works, and then - like a thunderbolt from a clear sky, everything is back to normal again. It's like nothing ever happened. Like the computer were female." - Unknown
"Some people say that I must be a terrible person, but it's not true. I have the heart of a young boy. In a jar on my desk." - Stephen King
"If there is anything the nonconformist hates worse than a conformist, it's another nonconformist who doesn't conform to the prevailing standard of nonconformity." - Bill Vaughan
"Microsoft Windows [n.]: A thirty-two bit extension and GUI shell to a sixteen bit patch to an eight bit operating system originally coded for a four bit microprocessor and sold by a two-bit company that can't stand one bit of competition." - Unknown
"When a newly married couple smiles, everyone knows why. When a ten-year married couple smiles, everyone wonders why." - Unknown
#6
SteelTrepid
- Administrator
-
- Group: Admin
- Posts: 6,146
- Joined: 27-April 04
- Gender:Male
- Location:Ohio
Posted 31 October 2005 - 02:56 PM
Sorry, just wanted to let everyone know I just removed the posts. They were modified by LittlBUGer and pretty much all content was removed, so there was really no reason for the posts to still be there. I felt it would confuse users. Basically, it deals with permission. The author of the BTS drivers refused us permission to mirror or provide the driver packages. We were very polite, explained why we needed them, and were willing to work with him.....however he refused. He wants everyone to download them from him. So please, not links to other downloads or modified versions of the BTS drivers. LittlBUGer and webmedic spent a lot of time working on adding them to the project and perfecting the scripts.....please have some respect for their work, do not post links for alternatives. If you have ideas or suggestions, contact us. We love it when people are willing to help.
"I play Russian roulette everyday, a man's sport, with a bullet called life"
#7
Hemo2
- Regular Member
-
- Group: Members
- Posts: 112
- Joined: 13-August 04
Posted 31 October 2005 - 03:13 PM
Thanks LittlBUGer for the reply. It sounds like for devices not included in BTS, I can just continue to add them myself under the \Drivers\.... folders and let the project 'combine' them all together.
I understand about wanting the widest array of hardware support on your CD. We have over 9,000 computers so it's pretty important to us too! But we are almost strictly a 'corporate' style environment and even though we have computers that use SATA drives, etc. we don't have them setup using any of the RAID stuff. Almost exclusively our computers are all workstations on a network/domain with all data stored on servers. It is important to us to be able to bootup the pc and be able to drop a clone to them. In past years, I had maintained a DOS boot disk that included all our NIC drivers on it that allowed us to bootup all our different pc's to the network to drop our clones using this single floppy disk. But eventually it's just a matter of time before newer pc's come with NIC's in them that don't have an available DOS version of the driver, thus UBCD4Win is the perfect solution to that. Not to mention with UBCD4Win we drop our clones from an external USB drive instead of across the network, which speeds things up quite a bit so I'm dedicated to continue to try and make this project work for us. From your replies, it would appear the only major hurdle I can forsee for us is disc space on the CD. It would be nice to use DVD-R discs, but unfortunately a great many of our pc's do not have DVD ROM drives in them so at this time the 700MB CD limit is still something I have to stay under.
I'll give things a try in the next week or so. I'm only working 2 days this week and then going hunting for a few days. So hopefully I can find some time next week to absorb things and look at building a new version of our combo cd.
Again, many thanks for all your hard work.
I understand about wanting the widest array of hardware support on your CD. We have over 9,000 computers so it's pretty important to us too! But we are almost strictly a 'corporate' style environment and even though we have computers that use SATA drives, etc. we don't have them setup using any of the RAID stuff. Almost exclusively our computers are all workstations on a network/domain with all data stored on servers. It is important to us to be able to bootup the pc and be able to drop a clone to them. In past years, I had maintained a DOS boot disk that included all our NIC drivers on it that allowed us to bootup all our different pc's to the network to drop our clones using this single floppy disk. But eventually it's just a matter of time before newer pc's come with NIC's in them that don't have an available DOS version of the driver, thus UBCD4Win is the perfect solution to that. Not to mention with UBCD4Win we drop our clones from an external USB drive instead of across the network, which speeds things up quite a bit so I'm dedicated to continue to try and make this project work for us. From your replies, it would appear the only major hurdle I can forsee for us is disc space on the CD. It would be nice to use DVD-R discs, but unfortunately a great many of our pc's do not have DVD ROM drives in them so at this time the 700MB CD limit is still something I have to stay under.
I'll give things a try in the next week or so. I'm only working 2 days this week and then going hunting for a few days. So hopefully I can find some time next week to absorb things and look at building a new version of our combo cd.
Again, many thanks for all your hard work.
#8
LittlBUGer
- Main Mirror/Here Since Beginning
-
- Group: Members
- Posts: 4,698
- Joined: 27-May 04
- Location:MT, USA
- Interests:Computers and stuff...<br /><br />:-)
Posted 31 October 2005 - 03:22 PM
Also, if you want to see what's supported (MUCH more than my drivers did), check out the main drivers releast post... there's a link there with further information. The new drivers aren't JUST for special hardware, but for everything, just kind of like my old ones were, except THESE ones actually work. Everything I've tested this new method on works great (again, nVidia rings a bell) so it's awesome.
"Only two things are infinite, the universe and human stupidity, and I'm not sure about the former." - Albert Einstein
"Computers are really strange - first everything works fine, then something goes terribly wrong and nothing works, and then - like a thunderbolt from a clear sky, everything is back to normal again. It's like nothing ever happened. Like the computer were female." - Unknown
"Some people say that I must be a terrible person, but it's not true. I have the heart of a young boy. In a jar on my desk." - Stephen King
"If there is anything the nonconformist hates worse than a conformist, it's another nonconformist who doesn't conform to the prevailing standard of nonconformity." - Bill Vaughan
"Microsoft Windows [n.]: A thirty-two bit extension and GUI shell to a sixteen bit patch to an eight bit operating system originally coded for a four bit microprocessor and sold by a two-bit company that can't stand one bit of competition." - Unknown
"When a newly married couple smiles, everyone knows why. When a ten-year married couple smiles, everyone wonders why." - Unknown
#9
webmedic
- Ultimate Member
-
- Group: 911Cd Forum Guru
- Posts: 579
- Joined: 24-October 04
Posted 31 October 2005 - 03:43 PM
I would also like to mention that I maintain mirrors of the important bts driver packs and usually have the latest versions on my drive.
So if for some reason they become unavailable from him I'm sure myself or others could easily put them up for download someplace.
Like others I run a small shop also which is why driver support is so important to me also. At any rate enjoy.
So if for some reason they become unavailable from him I'm sure myself or others could easily put them up for download someplace.
Like others I run a small shop also which is why driver support is so important to me also. At any rate enjoy.
#10
LittlBUGer
- Main Mirror/Here Since Beginning
-
- Group: Members
- Posts: 4,698
- Joined: 27-May 04
- Location:MT, USA
- Interests:Computers and stuff...<br /><br />:-)
Posted 31 October 2005 - 04:44 PM
webmedic, on Oct 31 2005, 01:43 PM, said:
I would also like to mention that I maintain mirrors of the important bts driver packs and usually have the latest versions on my drive.
So if for some reason they become unavailable from him I'm sure myself or others could easily put them up for download someplace.
Like others I run a small shop also which is why driver support is so important to me also. At any rate enjoy.
So if for some reason they become unavailable from him I'm sure myself or others could easily put them up for download someplace.
Like others I run a small shop also which is why driver support is so important to me also. At any rate enjoy.
Again, I've talked with the creator over EVERYTHING that we could possible do to strike a deal. I mentioned "what if the server goes down...", "what about speeding up downloads by getting some mirrors", etc. etc. etc., and no, nothing, notta, he will not allow it, mainly do to some things he's planning to do in the future. All we can do is point people to his server and call it good. Though, he mentioned he got a new server and it should never go down again, but if it does for a significant period, I don't care, I'll mirror the downloads anyway.... :-\
Sorry if that sounded angry a bit... I'm generally angry at "something else" right now...
"Only two things are infinite, the universe and human stupidity, and I'm not sure about the former." - Albert Einstein
"Computers are really strange - first everything works fine, then something goes terribly wrong and nothing works, and then - like a thunderbolt from a clear sky, everything is back to normal again. It's like nothing ever happened. Like the computer were female." - Unknown
"Some people say that I must be a terrible person, but it's not true. I have the heart of a young boy. In a jar on my desk." - Stephen King
"If there is anything the nonconformist hates worse than a conformist, it's another nonconformist who doesn't conform to the prevailing standard of nonconformity." - Bill Vaughan
"Microsoft Windows [n.]: A thirty-two bit extension and GUI shell to a sixteen bit patch to an eight bit operating system originally coded for a four bit microprocessor and sold by a two-bit company that can't stand one bit of competition." - Unknown
"When a newly married couple smiles, everyone knows why. When a ten-year married couple smiles, everyone wonders why." - Unknown
#11
tunner
- Member
-
- Group: Members
- Posts: 43
- Joined: 28-September 05
Posted 31 October 2005 - 04:52 PM
Hello,
*Note:
I use ReatogoLogon so this error may not be an issue with other projects like your ubcd4win and BartPE. I am not sure if the irbus.inf error message is due to ReatogoLogon or my Dell SP2 install Cd (C:\xpcd) which is slipstreamed with Ryan's Hotfixes. I just thought you would like me to post this error message here incase it involves your project or BartPE in general...
I had a build error using reatogoPEBuilder (Siegfried's licensed version of PEBuilder)...the file irbus.inf couldn't be found:
So I found the irbus.inf (see bottom of post) and put it into my source files C:\xpcd\i386\ folder. http://www.infdump.c...les/I/irbus.inf
Thanks again to LittleBuger, SteelTrepid, WebMedic, unknwon, CraZiEr22, d4vr0s, cdob and everyone else who helped with this project
I hope I'm not assuming too much in posting this here...in other words I hope I'm not pissing anyone off
I originally posted this info here: http://www.911cd.net...showtopic=14319
BTW,
Your new method has worked 100% so far (after it created irbus.inf); slipstreaming and txtsetup.sif went perfect...right now reatogoPEBuilder is buring the ISO 
thanks!!!
irbus.inf
*Note:
I use ReatogoLogon so this error may not be an issue with other projects like your ubcd4win and BartPE. I am not sure if the irbus.inf error message is due to ReatogoLogon or my Dell SP2 install Cd (C:\xpcd) which is slipstreamed with Ryan's Hotfixes. I just thought you would like me to post this error message here incase it involves your project or BartPE in general...
I had a build error using reatogoPEBuilder (Siegfried's licensed version of PEBuilder)...the file irbus.inf couldn't be found:
Quote
DecompressOrCopy file "C:\xpcd\i386\irbus.inf" to "C:\reatogo-25-6a\ReatogoPE\i386\inf\irbus.inf"
Error: SetupDecompressOrCopyFile "C:\xpcd\i386\irbus.inf" to "C:\reatogo-25-6a\ReatogoPE\i386\inf\irbus.inf" returned error 2: The system cannot find the file specified.
Error: SetupDecompressOrCopyFile "C:\xpcd\i386\irbus.inf" to "C:\reatogo-25-6a\ReatogoPE\i386\inf\irbus.inf" returned error 2: The system cannot find the file specified.
So I found the irbus.inf (see bottom of post) and put it into my source files C:\xpcd\i386\ folder. http://www.infdump.c...les/I/irbus.inf
Thanks again to LittleBuger, SteelTrepid, WebMedic, unknwon, CraZiEr22, d4vr0s, cdob and everyone else who helped with this project
I hope I'm not assuming too much in posting this here...in other words I hope I'm not pissing anyone off
I originally posted this info here: http://www.911cd.net...showtopic=14319BTW,
Your new method has worked 100% so far (after it created irbus.inf); slipstreaming and txtsetup.sif went perfect...right now reatogoPEBuilder is buring the ISO
thanks!!!irbus.inf
; Installation inf for IRBUS Driver
;
[Version]
Signature="$WINDOWS NT$"
Class=USB
ClassGUID={36FC9E60-C465-11CF-8056-444553540000}
Provider=%Microsoft%
LayoutFile=layout.inf
DriverVer=07/01/2001,5.1.2600.2180
[Manufacturer]
%Microsoft%=MicrosoftHw
[MicrosoftHw]
%USB\VID_045E&PID_006D.DeviceDesc%=IrBus, USB\VID_045E&PID_006D
%USB\VID_045E&PID_006D.DeviceDesc%=IrBus, USB\VID_045E&PID_00A0
%USB\VID_045E&PID_006D.DeviceDesc%=IrBus, USB\VID_107B&PID_3009
%USB\VID_045E&PID_006D.DeviceDesc%=IrBus, USB\VID_1509&PID_9242
%USB\VID_045E&PID_006D.DeviceDesc%=IrBus, USB\VID_03EE&PID_2501
%USB\VID_045E&PID_006D.DeviceDesc%=IrBus, USB\VID_0471&PID_0815
%USB\VID_045E&PID_006D.DeviceDesc%=IrBus, USB\VID_0609&PID_031D
%USB\VID_045E&PID_006D.DeviceDesc%=IrBus, USB\VID_2040&PID_6310
%USB\VID_045E&PID_006D.DeviceDesc%=IrBus, USB\VID_1009&PID_000E
[ControlFlags]
ExcludeFromSelect=USB\VID_045E&PID_006D
ExcludeFromSelect=USB\VID_045E&PID_00A0
ExcludeFromSelect=USB\VID_107B&PID_3009
ExcludeFromSelect=USB\VID_1509&PID_9242
ExcludeFromSelect=USB\VID_03EE&PID_2501
ExcludeFromSelect=USB\VID_0471&PID_0815
ExcludeFromSelect=USB\VID_0609&PID_031D
ExcludeFromSelect=USB\VID_2040&PID_6310
ExcludeFromSelect=USB\VID_1009&PID_000E
[DestinationDirs]
DefaultDestDir = 12
[IrBus.NT]
CopyFiles=IrBus.NT.Copy
[IrBus.NT.Copy]
IrBus.sys
[IrBus.NT.HW]
;AddReg=IrBus.NT.AddReg.HW
[IrBus.NT.AddReg.Services]
; Philips RC6 protocol
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57da","DecoderName",0x00000000,"Philips RC6 32-bit"
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57da","DecoderID",0x00010001,0x1
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57da","DecoderType",0x00000000,"BiPhase"
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57da","BitOrder",0x00000000,"MSBFirst"
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57da","CodeMinBits",0x00010001,32
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57da","CodeMaxBits",0x00010001,32
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57da","OnePatternMin",0x00000000,"300 -666"
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57da","OnePatternMax",0x00000000,"666 -300"
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57da","ZeroPatternMin",0x00000000,"-666 300"
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57da","ZeroPatternMax",0x00000000,"-300 666"
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57da","HasRepeatData",0x00010001,0x1
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57da","RepeatPrefixPatternMin",0x00000000,"2300 -1110 300 -666 300 -666 300 -1110 300 -1110 666"
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57da","RepeatPrefixPatternMax",0x00000000,"2900 -666 666 -300 666 -300 666 -666 666 -666 1110"
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57da","MaxRepeatPauseInterval",0x00010001,80000
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57da","MaxRepeatTimeout",0x00010001,120000
; Sony protocol
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57db","DecoderName",0x00000000,"Sony 12 to 15-bit"
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57db","DecoderID",0x00010001,0x2
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57db","DecoderType",0x00000000,"Pulse"
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57db","BitOrder",0x00000000,"LSBFirst"
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57db","CodeMinBits",0x00010001,12
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57db","CodeMaxBits",0x00010001,15
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57db","OnePatternMin",0x00000000,"1000 -800"
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57db","OnePatternMax",0x00000000,"1400 -400"
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57db","ZeroPatternMin",0x00000000,"400 -800"
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57db","ZeroPatternMax",0x00000000,"800 -400"
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57db","HasRepeatData",0x00010001,0x1
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57db","RepeatPrefixPatternMin",0x00000000,"2000 -800"
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57db","RepeatPrefixPatternMax",0x00000000,"2800 -400"
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57db","MaxRepeatPauseInterval",0x00010001,32000
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57db","MaxRepeatTimeout",0x00010001,50000
; WebTV protocol
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57dc","DecoderName",0x00000000,"WebTV 13-bit"
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57dc","DecoderID",0x00010001,0x3
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57dc","DecoderType",0x00000000,"Space"
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57dc","BitOrder",0x00000000,"MSBFirst"
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57dc","CodeMinBits",0x00010001,13
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57dc","CodeMaxBits",0x00010001,13
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57dc","OnePatternMin",0x00000000,"400 -1800"
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57dc","OnePatternMax",0x00000000,"800 -1100"
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57dc","ZeroPatternMin",0x00000000,"400 -2900"
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57dc","ZeroPatternMax",0x00000000,"800 -2300"
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57dc","HasRepeatData",0x00010001,0x1
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57dc","RepeatPrefixPatternMin",0x00000000,"400 -6500"
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57dc","RepeatPrefixPatternMax",0x00000000,"800 -5500"
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57dc","MaxRepeatPauseInterval",0x00010001,32000
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57dc","MaxRepeatTimeout",0x00010001,50000
; NEC protocol
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57dd","DecoderName",0x00000000,"NEC 32-bit"
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57dd","DecoderID",0x00010001,0x4
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57dd","DecoderType",0x00000000,"Space"
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57dd","BitOrder",0x00000000,"LSBFirst"
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57dd","CodeMinBits",0x00010001,32
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57dd","CodeMaxBits",0x00010001,32
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57dd","OnePatternMin",0x00000000,"360 -1890"
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57dd","OnePatternMax",0x00000000,"760 -1490"
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57dd","ZeroPatternMin",0x00000000,"360 -760"
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57dd","ZeroPatternMax",0x00000000,"760 -360"
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57dd","HasRepeatData",0x00010001,0x1
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57dd","RepeatPrefixPatternMin",0x00000000,"4000 -5000"
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57dd","RepeatPrefixPatternMax",0x00000000,"5000 -4000"
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57dd","RepeatSuffixPatternMin",0x00000000,"360 -760"
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57dd","RepeatSuffixPatternMax",0x00000000,"760 -360"
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57dd","MaxRepeatPauseInterval",0x00010001,60000
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57dd","MaxRepeatTimeout",0x00010001,120000
; Thompson protocol? (xbox)
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57de","DecoderName",0x00000000,"Thompson 24-bit"
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57de","DecoderID",0x00010001,0x5
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57de","DecoderType",0x00000000,"Space"
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57de","BitOrder",0x00000000,"MSBFirst"
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57de","CodeMinBits",0x00010001,24
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57de","CodeMaxBits",0x00010001,24
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57de","OnePatternMin",0x00000000,"300 -1200"
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57de","OnePatternMax",0x00000000,"700 -800"
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57de","ZeroPatternMin",0x00000000,"300 -2200"
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57de","ZeroPatternMax",0x00000000,"700 -1800"
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57de","HasRepeatData",0x00010001,0x1
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57de","RepeatPrefixPatternMin",0x00000000,"3500 -4500"
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57de","RepeatPrefixPatternMax",0x00000000,"4500 -3500"
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57de","RepeatSuffixPatternMin",0x00000000,"300 -700"
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57de","RepeatSuffixPatternMax",0x00000000,"700 -300"
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57de","MaxRepeatPauseInterval",0x00010001,10000
HKR,"Decoders\745a17a0-74d3-11d0-b6fe-00a0c90f57de","MaxRepeatTimeout",0x00010001,70000
; Active power Key (set to NOCLOBBER)
HKR,"PowerKey","PowerKey",0x00000003,\
0x00,0x00,0x00,0x00, \
0x1F,0x00,0xB9,0xD1,0xC4,0x8E,0xEE,0x91,0x0C,0x90,0x89,0xA1,0x87,0xEE,0x1A,0xAA,
xDE,0x35,0x9B,0xEC,0x14,0xF5,0x8D,0xC1,0x1B,0xAA,0x42,0x4D,0x4F,0xCB,0x6F,0xBE,0
9D,0xE6,0x5C,0xFA,0x47,0xE1,0xC1,0xF2,0x84,0xA6, \
0x1F,0x20,0x34,0x8F,0xE7,0x71,0xEE,0x13,0x5F,0x55,0x82,0xFE,0x09,0x50,0x56,0x2A,
x28,0xEF,0x64,0xF1,0x97,0x46,0xAB,0xAA,0x03,0x15,0x6C,0xAB,0x62,0x0B,0x23,0x55,0
9F,0x03,0x1F,0x86,0xC1,0xAD,0x63,0x17,0x3D,0x6E, \
0x1F,0x40,0xFA,0x46,0x4A,0x77,0x33,0x58,0x82,0xE1,0x1F,0x81,0xAB,0xE7,0xD8,0x6A,
x07,0x3E,0x51,0x83,0x60,0x6C,0x19,0x5B,0x18,0x4F,0x67,0xC1,0x74,0x53,0x01,0xF2,0
87,0xDE,0xE2,0xC1,0x99,0xE6,0x22,0x9A,0x85,0xA6, \
0x1F,0x60,0xA1,0x78,0xFB,0x07,0xAB,0x5D,0xDB,0x47,0x3F,0x63,0x2B,0xB6,0xDE,0xF2,
xB4,0x82,0x30,0xA3,0x6D,0x53,0x67,0xD6,0x15,0x35,0x61,0x4D,0xF4,0xD5,0x31,0x5D,0
AF,0x55,0x2B,0xCE,0xBB,0xDB,0x87,0x7A,0xE0,0x88, \
0x1F,0x80,0xDC,0xFE,0xAD,0x50,0x17,0x39,0x9B,0x97,0x03,0x3C,0x46,0x37,0x01,0xA5,
x8C,0x0F,0x5D,0x52,0xD8,0x6D,0x5C,0x0C,0xA5,0x84,0xA7,0x80,0x06,0xED,0xAB,0x81,0
B1,0x4C,0x13,0x38,0x29,0x95,0xDA,0x85,0x63,0xD9, \
0x1F,0xA0,0xD1,0xD9,0xFD,0x08,0xB7,0x84,0x37,0x45,0xAB,0x34,0xF6,0xC7,0x67,0xDA,
x97,0x2F,0x94,0xFD,0x78,0x68,0xAE,0xE8,0x57,0xE1,0x4B,0xBC,0x5A,0x47,0x61,0x3F,0
F0,0x97,0x51,0x04,0x16,0xE1,0x2A,0x99,0xDA,0x31, \
0x1F,0xC0,0xB3,0x86,0xEF,0xB0,0xF6,0x60,0x9F,0x19,0x01,0x33,0x0D,0x99,0xF9,0x92,
x7A,0xB1,0xB5,0x6D,0x2C,0x5F,0x6E,0xEF,0x1A,0x5D,0x18,0xDE,0x88,0x25,0xEE,0x48,0
12,0x10,0xBE,0xDB,0x1B,0xE2,0x8E,0xBA,0x19,0x2A, \
0x1F,0xE0,0x8B,0x14,0x2F,0x74,0xBB,0x27,0x4C,0xCD,0x85,0xAB,0x23,0xCF,0x57,0x5D,
xA5,0x75,0x81,0x0D,0xF4,0x41,0x45,0x10,0x9A,0xAA,0xDF,0x23,0x41,0x1E,0xAE,0xE9,0
94,0xEA,0xD6,0x23,0x37,0xDE,0xEB,0xFA,0x5D,0x7B
; Samsung power key
HKR,"PowerKey","PowerKeySamsung",0x00000001,\
0x04,0x00,0x00,0x00, \
0x1F,0x00,0xB9,0xD1,0xC4,0x8E,0xEA,0x91,0x0C,0x90,0x89,0xA1,0x87,0xEE,0x1A,0xAA,
xDE,0x35,0x9B,0xEC,0x14,0xF5,0x8D,0xC1,0x1B,0xAA,0x42,0x4D,0x4F,0xCB,0x6F,0xBE,0
9D,0xE6,0x5C,0xFA,0x47,0xE1,0xC5,0xF2,0x84,0xA6, \
0x1F,0x20,0x34,0x8F,0xE7,0x71,0xEE,0x13,0x5F,0x55,0x82,0xFE,0x09,0x50,0x56,0x2A,
x28,0xEF,0x64,0xF1,0x97,0x46,0xAB,0xAA,0x03,0x15,0x6C,0xAB,0x62,0x0B,0x23,0x55,0
9F,0x03,0x1F,0x86,0xC1,0xAD,0x63,0x17,0x3D,0x6E, \
0x1F,0x40,0xFA,0x46,0x4A,0x77,0x33,0x58,0x82,0xE1,0x1F,0x81,0xAB,0xE7,0xD8,0x6A,
x07,0x3E,0x51,0x83,0x60,0x6C,0x19,0x5B,0x18,0x4F,0x67,0xC1,0x74,0x53,0x06,0xF2,0
B0,0xD1,0xC7,0xC2,0x99,0xE1,0x00,0x99,0xB2,0xAE, \
0x1F,0x60,0xA1,0x78,0xFB,0x07,0xA1,0x5A,0xDB,0x40,0x3F,0x64,0x2B,0xB1,0xDB,0xF5,
xB4,0x85,0x35,0xA4,0x64,0x54,0x62,0xD1,0x15,0x32,0x61,0x4A,0xF4,0xD2,0x31,0x5A,0
AF,0x52,0x21,0xC9,0xBB,0xDC,0x82,0x7A,0xE9,0x88, \
0x1F,0x80,0xDC,0xFE,0xAD,0x50,0x1D,0x3E,0x9B,0x90,0x03,0x3B,0x46,0x30,0x0B,0xA2,
x8C,0x08,0x57,0x55,0xD8,0x6A,0x5C,0x0B,0xA5,0x83,0xAD,0x87,0x06,0xEA,0xAB,0x86,0
B4,0x4B,0x19,0x3F,0x29,0x92,0xD0,0x85,0x66,0xD9, \
0x1F,0xA0,0xD1,0xD9,0xFD,0x08,0xB7,0x83,0x37,0x42,0xAB,0x33,0xC3,0xC5,0x62,0xDD,
x97,0x28,0x94,0xFA,0x78,0x6F,0xAE,0xEF,0x57,0xE6,0x4B,0xBB,0x5A,0x40,0x61,0x38,0
F0,0x90,0x51,0x03,0x13,0xE6,0x2F,0x99,0xEA,0x34, \
0x1F,0xC0,0xB3,0x86,0xEF,0xB0,0xF7,0x63,0x61,0xE5,0xFA,0xCF,0xF3,0x65,0x07,0x6E,
x84,0x4D,0x4A,0x92,0x2C,0x5F,0x6E,0xEF,0x1A,0x5D,0x18,0xDE,0x88,0x25,0xEE,0x48,0
12,0x10,0xBE,0xDB,0x1B,0xE2,0x75,0x46,0xE7,0xD6, \
0x1F,0xE0,0x8B,0x14,0x2F,0x74,0xBB,0x27,0x4C,0xCD,0x85,0xAB,0x23,0xCF,0x57,0x5D,
xA5,0x75,0x81,0x0D,0xF4,0x41,0x45,0x10,0x9A,0xAA,0xDF,0x23,0x41,0x1E,0xAE,0xE9,0
94,0xEA,0xD6,0x23,0x46,0x4C,0xEB,0xFA,0x2C,0xE9
; RC6 All Codeset Power Key
HKR,"PowerKey","PowerKeyRC6All",0x00000001,\
0x00,0x00,0x00,0x00, \
0x1F,0x00,0xB9,0xD1,0xC4,0x8E,0xEE,0x91,0x0C,0x90,0x89,0xA1,0x87,0xEE,0x1A,0xAA,
xDE,0x35,0x9B,0xEC,0x14,0xF5,0x8D,0xC1,0x1B,0xAA,0x42,0x4D,0x4F,0xCB,0x6F,0xBE,0
9D,0xE6,0x5C,0xFA,0x47,0xE1,0xC1,0xF2,0x84,0xA6, \
0x1F,0x20,0x34,0x8F,0xE7,0x71,0xEE,0x13,0x5F,0x55,0x82,0xFE,0x09,0x50,0x56,0x2A,
x28,0xEF,0x64,0xF1,0x97,0x46,0xAB,0xAA,0x03,0x15,0x6C,0xAB,0x62,0x0B,0x23,0x55,0
9F,0x03,0x1F,0x86,0xC1,0xAD,0x63,0x17,0x3D,0x6E, \
0x1F,0x40,0xFA,0x46,0x4A,0x77,0x33,0x58,0x82,0xE1,0x1F,0x81,0xAB,0xE7,0xD8,0x6A,
x07,0x3E,0x51,0x83,0x60,0x6C,0x19,0x5B,0x18,0x4F,0x67,0xC1,0x74,0x53,0x01,0xF2,0
87,0xDE,0xE2,0xC1,0x99,0xE6,0x22,0x9A,0x85,0xA6, \
0x1F,0x60,0xA1,0x78,0xFB,0x07,0xAB,0x5D,0xDB,0x47,0x3F,0x63,0x2B,0xB6,0xDE,0xF2,
xB4,0x82,0x30,0xA3,0x6D,0x53,0x67,0xD6,0x15,0x35,0x61,0x4D,0xF4,0xD5,0x31,0x5D,0
AF,0x55,0x2B,0xCE,0xBB,0xDB,0x87,0x7A,0xE0,0x88, \
0x1F,0x80,0xDC,0xFE,0xAD,0x50,0x17,0x39,0x9B,0x97,0x03,0x3C,0x46,0x37,0x01,0xA5,
x8C,0x0F,0x5D,0x52,0xD8,0x6D,0x5C,0x0C,0xA5,0x84,0xA7,0x80,0x06,0xED,0xAB,0x81,0
B1,0x4C,0x13,0x38,0x29,0x95,0xDA,0x85,0x63,0xD9, \
0x1F,0xA0,0xD1,0xD9,0xFD,0x08,0xB7,0x84,0x37,0x45,0xAB,0x34,0xF6,0xC7,0x67,0xDA,
x97,0x2F,0x94,0xFD,0x78,0x68,0xAE,0xE8,0x57,0xE1,0x4B,0xBC,0x5A,0x47,0x61,0x3F,0
F0,0x97,0x51,0x04,0x16,0xE1,0x2A,0x99,0xDA,0x31, \
0x1F,0xC0,0xB3,0x86,0xEF,0xB0,0xF6,0x60,0x9F,0x19,0x01,0x33,0x0D,0x99,0xF9,0x92,
x7A,0xB1,0xB5,0x6D,0x2C,0x5F,0x6E,0xEF,0x1A,0x5D,0x18,0xDE,0x88,0x25,0xEE,0x48,0
12,0x10,0xBE,0xDB,0x1B,0xE2,0x8E,0xBA,0x19,0x2A, \
0x1F,0xE0,0x8B,0x14,0x2F,0x74,0xBB,0x27,0x4C,0xCD,0x85,0xAB,0x23,0xCF,0x57,0x5D,
xA5,0x75,0x81,0x0D,0xF4,0x41,0x45,0x10,0x9A,0xAA,0xDF,0x23,0x41,0x1E,0xAE,0xE9,0
94,0xEA,0xD6,0x23,0x37,0xDE,0xEB,0xFA,0x5D,0x7B
[IrBus.NT.Services]
AddService = IrBus,0x00000002,IrBus.AddService
[IrBus.AddService]
DisplayName = %IrBus.SvcDesc%
ServiceType = 1 ; SERVICE_KERNEL_DRIVER
StartType = 3 ; SERVICE_DEMAND_START
ErrorControl = 1 ; SERVICE_ERROR_NORMAL
ServiceBinary = %12%\IrBus.sys
LoadOrderGroup = PNP Filter
AddReg = IrBus.NT.AddReg.Services
[Strings]
Microsoft="Microsoft"
USB\VID_045E&PID_006D.DeviceDesc="eHome Infrared Receiver"
FTD2XX.SvcDesc="Future Technology Devices International device driver"
IrBus.SvcDesc="Infrared bus filter driver for eHome remote controls"
This post has been edited by tunner: 31 October 2005 - 04:58 PM
#12
SteelTrepid
- Administrator
-
- Group: Admin
- Posts: 6,146
- Joined: 27-April 04
- Gender:Male
- Location:Ohio
Posted 31 October 2005 - 05:10 PM
Nope, your post is fine. I read your post over at 911 then came back over here and was surprised to see your post here also. The information helps and that's all that really matters. It's your perogative if you prefer to use reatogo or UBCD4Win.
"I play Russian roulette everyday, a man's sport, with a bullet called life"
#13
Hemo2
- Regular Member
-
- Group: Members
- Posts: 112
- Joined: 13-August 04
Posted 31 October 2005 - 05:20 PM
Sorry to keep coming up with questions, but one more!
If the BTS driver packs get updated, will that require an update for the UBCD4Win project, or is it as simple as copying the updated BTS driver packs into the project and rebuilding?
If the BTS driver packs get updated, will that require an update for the UBCD4Win project, or is it as simple as copying the updated BTS driver packs into the project and rebuilding?
#14
LittlBUGer
- Main Mirror/Here Since Beginning
-
- Group: Members
- Posts: 4,698
- Joined: 27-May 04
- Location:MT, USA
- Interests:Computers and stuff...<br /><br />:-)
Posted 31 October 2005 - 05:21 PM
Just as simple as copying the updated driver packs into their proper folders and rebuilding. Well, unless a whole new driver pack category comes out... then we'll have to see about an update.
Well, unless a whole new driver pack category comes out... then we'll have to see about an update.
"Only two things are infinite, the universe and human stupidity, and I'm not sure about the former." - Albert Einstein
"Computers are really strange - first everything works fine, then something goes terribly wrong and nothing works, and then - like a thunderbolt from a clear sky, everything is back to normal again. It's like nothing ever happened. Like the computer were female." - Unknown
"Some people say that I must be a terrible person, but it's not true. I have the heart of a young boy. In a jar on my desk." - Stephen King
"If there is anything the nonconformist hates worse than a conformist, it's another nonconformist who doesn't conform to the prevailing standard of nonconformity." - Bill Vaughan
"Microsoft Windows [n.]: A thirty-two bit extension and GUI shell to a sixteen bit patch to an eight bit operating system originally coded for a four bit microprocessor and sold by a two-bit company that can't stand one bit of competition." - Unknown
"When a newly married couple smiles, everyone knows why. When a ten-year married couple smiles, everyone wonders why." - Unknown
#15
tunner
- Member
-
- Group: Members
- Posts: 43
- Joined: 28-September 05
Posted 31 October 2005 - 05:39 PM
Hi again ,
I build/burnt my ISO to Cd (worked like a charm) but when I booted with the Cd I recieved this error message:
Have you seen this error message before?
The file ahpt3xx.sys is in MassStorage driverpack so I disabled the MassStorage driverpack and I am rebuilding as I type.
If I can boot after removing MassStorge I will probibaly use your excellent drivers.exe v.1.6 (only using the MassStorage part for \drivers\SCSIAdapter\ folder)
Overall though...this is Great News for me Your new method seems to work for me. I have tried the original method (unknown's script) and your How-To here; neither worked for me. I always recieved missing file messages during boot...this is the first time I have gotten this far.
BTW, I also disabled the "burn ISO" autobuild plugin as I use CDBurnerPRO-XP-3, not PEBuilder to burn my ISO to Cd; could this cause error's?
Thanks
,I build/burnt my ISO to Cd (worked like a charm) but when I booted with the Cd I recieved this error message:
Insufficient memory for ahpt3xx.sys. Press any key to continue.
Have you seen this error message before?
The file ahpt3xx.sys is in MassStorage driverpack so I disabled the MassStorage driverpack and I am rebuilding as I type.
If I can boot after removing MassStorge I will probibaly use your excellent drivers.exe v.1.6 (only using the MassStorage part for \drivers\SCSIAdapter\ folder)
Overall though...this is Great News for me
Your new method seems to work for me. I have tried the original method (unknown's script) and your How-To here; neither worked for me. I always recieved missing file messages during boot...this is the first time I have gotten this far.BTW, I also disabled the "burn ISO" autobuild plugin as I use CDBurnerPRO-XP-3, not PEBuilder to burn my ISO to Cd; could this cause error's?
Thanks
This post has been edited by tunner: 31 October 2005 - 05:45 PM