Full Version: Help with NEW BTS 1.0+ Drivers Release!
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.
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.
QUOTE (LittlBUGer @ Oct 31 2005, 12:29 PM)
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?)
QUOTE (LittlBUGer @ Oct 31 2005, 12:29 PM)
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.
QUOTE (LittlBUGer @ Oct 31 2005, 12:29 PM)
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?
QUOTE (LittlBUGer @ Oct 31 2005, 12:29 PM)
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.
@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.
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?
QUOTE (Hemo2 @ Oct 31 2005, 12: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?
I answered that in my first answer above.
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.
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.
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.
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.
QUOTE (webmedic @ Oct 31 2005, 01: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.
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...
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.com/inffiles/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/forums//index.php?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.com/inffiles/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/forums//index.php?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
CODE
; 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"
;
[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"
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.
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?
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.
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:
CODE
Insufficient memory for ahpt3xx.sys.
Press any key to continue.
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
QUOTE (tunner @ Oct 31 2005, 03: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:
CODE
Insufficient memory for ahpt3xx.sys.
Press any key to continue.
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
I highly recommend NOT disabling any of the new plugins from the drivers pack as they are required, unless you don't include a few BTS driver packs and want to disable those. Otherwise, leave them all enabled. And no, nothing automatically burns to a CD. Only an .ISO file is created, of which you can burn later.
QUOTE (LittlBUGer @ Oct 31 2005, 05:47 PM)
I highly recommend NOT disabling any of the new plugins from the drivers pack as they are required, unless you don't include a few BTS driver packs and want to disable those. Otherwise, leave them all enabled. And no, nothing automatically burns to a CD. Only an .ISO file is created, of which you can burn later.
Will do...one default UBCD4win drivers v.2.0 and reatogologon comming up!
Thanks
QUOTE (SteelTrepid @ Oct 31 2005, 05:10 PM)
I read your post over at 911 then came back over here and was surprised to see your post here also.
I thought you would like all relevent info, error messages, fixes, etc in this thread for easy searching and reference.
Also, for some reason Zeoran deleted my post at 911 with the irbus.inf info in it. He also deleted DigiWiz's post about mirrors due to legal issue with the mirrors...so I think he just deleted my post by mistake along wiht Digi's post in one swoop.
I thought this may be usefull and I thought you would like the info here for future use.
Thanks
Yeah, I'm sure it was an accident. There wasn't a problem with your post.
Hi Steel, webmedic and LittleBuger ...
SUCCESS!
Your new BTS method *rules*, thanks guys I finally have BTS running with ReatogoLogon.
I have Reatogologon working 100% with the new UBCD4win BTS driver v.2.0.
I used the MassStorage, Graphics (A & B ), LAN, WLAN, Chipset, CPU, Intel Extreme and Base.
All Reatogo Shells are loading correctly.
Now I'm going to build a Cd with my usual plugs.
I was getting this error message upon every boot until I edited D\M\AD\1\hpt3xx.sys:
I will post a How-To in a few hours...to get this to work I had to edit some files (D\M\AD\1\hpt3xx.sys) from the BTS driverpacks and the Output files, then rebuild the ISO; I also had to create a new .inf and I didn't use HWPnP "autobuild" plug with the UBCD4 BTS driverpacks as ReatogoLogon handles that.
I hope the info I will post is of value to you and I'm not leading this forums off topic with reatogo stuff...
Has anyone else reported the above ^^^ error message upon boot?
Thanks all
...SUCCESS!
Your new BTS method *rules*, thanks guys I finally have BTS running with ReatogoLogon.
I have Reatogologon working 100% with the new UBCD4win BTS driver v.2.0.
I used the MassStorage, Graphics (A & B ), LAN, WLAN, Chipset, CPU, Intel Extreme and Base.
All Reatogo Shells are loading correctly.
Now I'm going to build a Cd with my usual plugs.
I was getting this error message upon every boot until I edited D\M\AD\1\hpt3xx.sys:
CODE
Insufficient memory for ahpt3xx.sys.
Press any key to continue.
Press any key to continue.
I will post a How-To in a few hours...to get this to work I had to edit some files (D\M\AD\1\hpt3xx.sys) from the BTS driverpacks and the Output files, then rebuild the ISO; I also had to create a new .inf and I didn't use HWPnP "autobuild" plug with the UBCD4 BTS driverpacks as ReatogoLogon handles that.
I hope the info I will post is of value to you and I'm not leading this forums off topic with reatogo stuff...
Has anyone else reported the above ^^^ error message upon boot?
Thanks all
I haven't seen that message before, no. I'm guessing it's due to Reatogo and not just a plain vanilla build using BartPE or using the UBCD4Win release. But I can't be sure. I'm glad you figured it out though.
Hey guys,
I just finished my How-To for ReatogoLogon and I thought you might want to look at it as I posted a fix for the "Insufficient memory" error message.
I put a link here so as not to clutter your thread...if you want I can post only the error message fix section for the benifit of UBCD4win members/users (let me know)
http://www.911cd.net/forums//index.php?sho...indpost&p=91484
Thanks a million
I just finished my How-To for ReatogoLogon and I thought you might want to look at it as I posted a fix for the "Insufficient memory" error message.
I put a link here so as not to clutter your thread...if you want I can post only the error message fix section for the benifit of UBCD4win members/users (let me know)
http://www.911cd.net/forums//index.php?sho...indpost&p=91484
Thanks a million
I get that error only when I use virtual pc with less than 256 megs of ram allocated to it. When I upped the ram to 256 the error went away and I booted right in.
I also used the iso many times on actual systems without this error. I was testing to make sure the intel extreme video drivers were working.
I also used the iso many times on actual systems without this error. I was testing to make sure the intel extreme video drivers were working.
I tried the 2.0 drivers today and had a weird thing. I have been nusy and have not been able to do beta testing as I should have... (waits for slap on wrist)
I did the following with my build.
downloaded the 2.55 install and the 2.0 drivers.
downloaded all the packs except sound
deleted the plugin folder and ran the 2.55 then the driver 2.0 file
copied in the 7zip files as stated
added the updated def file for adaware SE
added ghost 8, total commander, winrar, and Easyrecovery 6 (non of the apps have ever given any conflict or prolems in the past)
ran builder and disabled the IDSuite.dat plugin as it gave an error
It ran just fine till build ISO. At that point, it just stopped. I let it run just in case it was a script thing going on. Nothing happened after about 5 minutes so I copied out the msikofs statement and ran that from the run prompt. At that point the script kicked in and ran the driver packs. At no point did a ISO ever get created.
After that I launched UltraISO and created my own iso loading the .bin file in the root as my boot file. Created fine and booted fine. Took a long time to boot up... Had an issue with the Broadcom NIC in this machine. I am using a standard default IBM M51 3.2GHz P4HT with 1GB DDR 40GB and 300GB SATA and a 40GB IDE Broadcom Gig card built into mobo. Issue with NIC was it says that it is not there but it find it. Per device manager under PE, it says that it has a prob due to a prior instance is already loaded into memory. I didn't think of this as a problem prior as I had seen it under 1.6 driver pack and thought nothing of it. I figured with the BTS packs that it would be OK and go away. HELP!! any advice would be greatly appreciated on the NIC issue andletting you know about the build experience that I had earlier.
To answer a few questions before they start... I am an Admin, I have ETrust AV that Domain script prevent it from being turned off (you can kill it, but it comes back a few minutes later). Will answer any other questions forwarded me.
(waits for slap on wrist)I did the following with my build.
downloaded the 2.55 install and the 2.0 drivers.
downloaded all the packs except sound
deleted the plugin folder and ran the 2.55 then the driver 2.0 file
copied in the 7zip files as stated
added the updated def file for adaware SE
added ghost 8, total commander, winrar, and Easyrecovery 6 (non of the apps have ever given any conflict or prolems in the past)
ran builder and disabled the IDSuite.dat plugin as it gave an error
It ran just fine till build ISO. At that point, it just stopped. I let it run just in case it was a script thing going on. Nothing happened after about 5 minutes so I copied out the msikofs statement and ran that from the run prompt. At that point the script kicked in and ran the driver packs. At no point did a ISO ever get created.
After that I launched UltraISO and created my own iso loading the .bin file in the root as my boot file. Created fine and booted fine. Took a long time to boot up... Had an issue with the Broadcom NIC in this machine. I am using a standard default IBM M51 3.2GHz P4HT with 1GB DDR 40GB and 300GB SATA and a 40GB IDE Broadcom Gig card built into mobo. Issue with NIC was it says that it is not there but it find it. Per device manager under PE, it says that it has a prob due to a prior instance is already loaded into memory. I didn't think of this as a problem prior as I had seen it under 1.6 driver pack and thought nothing of it. I figured with the BTS packs that it would be OK and go away. HELP!! any advice would be greatly appreciated on the NIC issue andletting you know about the build experience that I had earlier.
To answer a few questions before they start... I am an Admin, I have ETrust AV that Domain script prevent it from being turned off (you can kill it, but it comes back a few minutes later). Will answer any other questions forwarded me.
Did you disable any of the new plugins added from the drivers release? Did you see any command prompt windows open up during the building phase and whatnot? It does take quite a while, especially if you have a slower PC. And if you say you have something that blocks certain scripts, or any AV software anyway, that's probably why nothing ran, since several scripts are ran during the process to get things going. I'm not exactly sure, but I would suggest starting completely from scratch and possibly trying it in Safe Mode. As long as you followed my instructions exactly, it should work.
QUOTE (LittlBUGer @ Nov 1 2005, 05:01 PM)
Did you disable any of the new plugins added from the drivers release? Did you see any command prompt windows open up during the building phase and whatnot? It does take quite a while, especially if you have a slower PC. And if you say you have something that blocks certain scripts, or any AV software anyway, that's probably why nothing ran, since several scripts are ran during the process to get things going. I'm not exactly sure, but I would suggest starting completely from scratch and possibly trying it in Safe Mode. As long as you followed my instructions exactly, it should work.
Did not disable any of the driver plugins at all. Only plugin that I disabled was the IDSuite.dat as Bart'sPE had a fit with that one saying it was missing files. No CMD prompts at all during the build until I ran the mskiofs by itself. 3.2GHz P4 w/HT 1GB DDR 3200 and a 40GB SATA HD? That is not a slow system by any means and is lightyears faster than the P4 2.66GHz machine I had last time. The scripts are apart of our 2003 Acitive Directory domain and they check for AV and such. Never disabeled them in the past for any prior build and have never had any problems with any version of UBCD that I have made and used. The build was from fresh install of PE, UBCD 2.55, and the drivers. Only thing differant from a vanilla build was my added plugins and turning off the IDSuite plugin. I want to say that the directions were followed to the letter but not sure. Will try to build again on my slower system that is not on our domain but I am not sure if it will yield a differant result.
Will let you know what I find out.
It seems little bugger that those having issues are not getting the autobuild plugin installed properly. I would think this is the main issue here.
here is a quick run through that may help. I'm not on my build system right now but there should still be an autobuild log. I cant rememebr if it says autobuild install log but there should still be one or else it is not getting installed.
First look in your bart pe folder is there an autobuild log file ? If not then autobuild is not even installed.
Goto the autobuild plugin folder and click on the install.cmd. It will install the autobuild plugin so that it is usable for you.
If there is an autobuild log there then try this.
1) Make sure you enable the build iso button in barts pe.
2) make sure you check the plugins and make sure that the bts driver plugin is anabled and that the autobuild plugins are enabled.
here is a quick run through that may help. I'm not on my build system right now but there should still be an autobuild log. I cant rememebr if it says autobuild install log but there should still be one or else it is not getting installed.
First look in your bart pe folder is there an autobuild log file ? If not then autobuild is not even installed.
Goto the autobuild plugin folder and click on the install.cmd. It will install the autobuild plugin so that it is usable for you.
If there is an autobuild log there then try this.
1) Make sure you enable the build iso button in barts pe.
2) make sure you check the plugins and make sure that the bts driver plugin is anabled and that the autobuild plugins are enabled.
Well, when they extract the drivers20 file into their pebuilder folder, it should automatically extract everything into their correct location and then automatically run the install.cmd file after extraction. Unless there's something wrong with the small script I made to run the install.cmd after extraction, I don't know. The script, at first, just ran the install.cmd file with something like this:
But that ended up not working as the file wasn't technically being ran from the folder it was located in, so it would error out saying it couldn't find files. Now, the script just runs something like this:
I mean, it's just a very simple thing that I thought would work universally... Did I just have a brain fart and completely miss something obvious? Please let me know if you have any suggestions. Thanks.
CODE
call %cd%/plugin/autobuild/install.cmd
But that ended up not working as the file wasn't technically being ran from the folder it was located in, so it would error out saying it couldn't find files. Now, the script just runs something like this:
CODE
cd plugin
cd autobuild
call install.cmd
cd autobuild
call install.cmd
I mean, it's just a very simple thing that I thought would work universally... Did I just have a brain fart and completely miss something obvious? Please let me know if you have any suggestions. Thanks.
no most likely not Since I'm not building the installer for the driver pack i have no way to test the things you do. It looks fine to me and should have worked.
I can possibly throw together an autit script to do this but it will add unnedded size the the download so I'm not really sure that is the best way to go.
I have to go for a bit and fix a system but I'll try and post another script here a little later that may fix this for you.
A quick question though were is the little installer script you created extracted to when the installer is unpacking things? Is it the root folder were everything else is extracted? If so i think I can make a simple script that will take care of all this.
Also does the script autodelete itself after it is installed?
I can possibly throw together an autit script to do this but it will add unnedded size the the download so I'm not really sure that is the best way to go.
I have to go for a bit and fix a system but I'll try and post another script here a little later that may fix this for you.
A quick question though were is the little installer script you created extracted to when the installer is unpacking things? Is it the root folder were everything else is extracted? If so i think I can make a simple script that will take care of all this.
Also does the script autodelete itself after it is installed?
QUOTE (webmedic @ Nov 2 2005, 08:34 AM)
no most likely not Since I'm not building the installer for the driver pack i have no way to test the things you do. It looks fine to me and should have worked.
I can possibly throw together an autit script to do this but it will add unnedded size the the download so I'm not really sure that is the best way to go.
I have to go for a bit and fix a system but I'll try and post another script here a little later that may fix this for you.
A quick question though were is the little installer script you created extracted to when the installer is unpacking things? Is it the root folder were everything else is extracted? If so i think I can make a simple script that will take care of all this.
Also does the script autodelete itself after it is installed?
I can possibly throw together an autit script to do this but it will add unnedded size the the download so I'm not really sure that is the best way to go.
I have to go for a bit and fix a system but I'll try and post another script here a little later that may fix this for you.
A quick question though were is the little installer script you created extracted to when the installer is unpacking things? Is it the root folder were everything else is extracted? If so i think I can make a simple script that will take care of all this.
Also does the script autodelete itself after it is installed?
Yes, once the drivers are extracted, the script is just extracted to the current/main folder (i.e. pebuilder). It is NOT automatically deleted as WinRAR doesn't have a way to do that I believe. It's called BTSDriversSetup.bat. You should see it if you look. Thanks.
ok thanks. I have to go right now but i should be back shortly and I'll see if we cant get this going good for everybody. It should not take long once I get back.
[This continues a discussion I erroneously started in the topic #1909 "Help with New Drivers Release, Post Your Problems HERE", which seemed the right place.]
Now then, in that forum http://www.ubcd4win.com/forum/index.php?sh...pic=1909&st=15# I described how I have followed the instructions of the first message of:
http://www.ubcd4win.com/forum/index.php?showtopic=3208
exactly, but when I boot from the resulting CD it fails to recognize my SATA drives. I have started from scratch several times, but without success
Now, to answer questions by webmedic and LittlBUGer:
No autobuild.log file in BPE313 directory
The exact method used follows:
1. extract PEBuilder313.zip into F:\BPE313
2. remove the F:\BPE313\plugin folder
3. run UBCD4Win255 into F:\BPE313
4. run UBCD4WinDriversV20.exe, extracting into F:\BPE313 [am not sure if a command prompt window came up, or not]
5. copied BTS_DriverPacks_BASE_V5105.exe into
F:\BPE313\plugin\BTSdrivers\driverpack_base\ [did not run the exe file]
6. copied DriverPack_LAN_V5101.7z into F:\BPE313\plugin\BTSdrivers\driverpack_lan\
7. copied DriverPack_MassStorage_V510.7z into F:\BPE313\plugin\BTSdrivers\driverpack_massStorage\
8. ran PEBuilder. At the first screen, hit Plugins button, and under the BTS drivers, deactivated the UNused BTS driverpacks, but made sure that the Base, Lan and MassStorage ones were activated. I changed no other default.
9. closed the plugin screen, specified that an ISO be made in F:\BPE313ISO\, and hit the Build button
PEBuilder completed without error. The root of the resulting CD has these subdirectories:
\AUTOBUILD\
\i386\
\PROGRAMS\
AUTORUN.INF
WIN51IP
WIN51IP.SP2
WINBOM.INI
I cannot see how I diverged from LittlBUGer's instruction in msg #1 of http://www.ubcd4win.com/forum/index.php?showtopic=3208#, but webmedic's question about the absence of an autobuild.log makes me wonder if UBCD4WinDriversV20 was supposed to run a batch file, but failed.
I'll bet one of you experts can immediately see where I went wrong. Thanks very much for the help.
[In the interests of keeping the "scene of the crime" unchanged, I have not followed webmedic's suggestion of running autobuild\install.cmd, as this was not in LittlBUGer's original instructions, cited above.]
Now then, in that forum http://www.ubcd4win.com/forum/index.php?sh...pic=1909&st=15# I described how I have followed the instructions of the first message of:
http://www.ubcd4win.com/forum/index.php?showtopic=3208
exactly, but when I boot from the resulting CD it fails to recognize my SATA drives. I have started from scratch several times, but without success
Now, to answer questions by webmedic and LittlBUGer:
No autobuild.log file in BPE313 directory
The exact method used follows:
1. extract PEBuilder313.zip into F:\BPE313
2. remove the F:\BPE313\plugin folder
3. run UBCD4Win255 into F:\BPE313
4. run UBCD4WinDriversV20.exe, extracting into F:\BPE313 [am not sure if a command prompt window came up, or not]
5. copied BTS_DriverPacks_BASE_V5105.exe into
F:\BPE313\plugin\BTSdrivers\driverpack_base\ [did not run the exe file]
6. copied DriverPack_LAN_V5101.7z into F:\BPE313\plugin\BTSdrivers\driverpack_lan\
7. copied DriverPack_MassStorage_V510.7z into F:\BPE313\plugin\BTSdrivers\driverpack_massStorage\
8. ran PEBuilder. At the first screen, hit Plugins button, and under the BTS drivers, deactivated the UNused BTS driverpacks, but made sure that the Base, Lan and MassStorage ones were activated. I changed no other default.
9. closed the plugin screen, specified that an ISO be made in F:\BPE313ISO\, and hit the Build button
PEBuilder completed without error. The root of the resulting CD has these subdirectories:
\AUTOBUILD\
\i386\
\PROGRAMS\
AUTORUN.INF
WIN51IP
WIN51IP.SP2
WINBOM.INI
I cannot see how I diverged from LittlBUGer's instruction in msg #1 of http://www.ubcd4win.com/forum/index.php?showtopic=3208#, but webmedic's question about the absence of an autobuild.log makes me wonder if UBCD4WinDriversV20 was supposed to run a batch file, but failed.
I'll bet one of you experts can immediately see where I went wrong. Thanks very much for the help.
[In the interests of keeping the "scene of the crime" unchanged, I have not followed webmedic's suggestion of running autobuild\install.cmd, as this was not in LittlBUGer's original instructions, cited above.]
thanks for that info. It helps greatly. Yes it is not in the origianl instrictions but it the install.cmd should have been run. It would appear as though some are having this issue while others are not.
It's ok But for now I would like you to try something.
Take this
autoinstall.cmd
save it as autoinstall.cmd and save it in your pe builder dir. Run it and let me know if that fixes the issue for you..
@littlebugger I have tested this cmd file and it appears to run properly. At least when I run it by hand. Could you try it on your end also and make sure it works.
If this does work then I also have a few more fixes that need to be added. I'll email the whole set over to you so we can get this fixed as soon as possible.
I need to fix
1) make it so that it will not fail is massstorage is not added.
2) add the missing inf file for those that dont have it.
I have already added the other fixes. That I can think of.
It's ok But for now I would like you to try something.
Take this
autoinstall.cmd
CODE
:: ===============================================================
:: ===============================================================
:: INSTALL: install autobuild.
:: ===============================================================
:: ===============================================================
@echo off
SET PeBuilderDir=%1
SET PEUtilsPath=%2
SET OutDir=%3
SET ISOFile=%4
IF "%PeBuilderDir%"=="" SET PeBuilderDir=.\
SET last_char=%PEBuilderDir:~-1%
IF "%last_char%"=="\" set PEBuilderDir=%PEBuilderDir:~0,-1%
IF "%ISOFile%"=="" FOR /f "tokens=1* delims== skip=1 eol=;" %%a IN (%PEBuilderDir%\input.inf) DO IF "%%a"=="isofile" SET ISOFile=%%b
IF "%FullOutDir%"=="" FOR /f "tokens=1* delims== skip=1 eol=;" %%a IN (%PEBuilderDir%\input.inf) DO IF "%%a"=="fulloutdir" SET OutDir=%%b
SET last_char=%OutDir:~-1%
IF "%last_char%"=="\" set OutDir=%OutDir:~0,-1%
IF "%PEUtilsPath%"=="" SET PEUtilsPath=%PeBuilderDir%\temp
SET last_char=%PEUtilsPath:~-1%
IF "%last_char%"=="\" set PEUtilsPath=%PEUtilsPath:~0,-1%
PATH=%PATH%;%PEBuilderDir%\plugin\autobuild\files\
echo; INSTALL.cmd started at 2>&1 | %PEBuilderDir%\plugin\autobuild\files\mtee %PEBuilderDir%\autobuild_install.log
echo; Date: %DATE% 2>&1 | %PEBuilderDir%\plugin\autobuild\files\mtee /+ %PEBuilderDir%\autobuild_install.log
echo; Time: %TIME% 2>&1 | %PEBuilderDir%\plugin\autobuild\files\mtee /+ %PEBuilderDir%\autobuild_install.log
echo; ----------------------------------------- 2>&1 | %PEBuilderDir%\plugin\autobuild\files\mtee /+ %PEBuilderDir%\autobuild_install.log
echo; PEBuilderDir: %PEBuilderDir% 2>&1 | %PEBuilderDir%\plugin\autobuild\files\mtee /+ %PEBuilderDir%\autobuild_install.log
echo; ISOfile : %ISOFile% 2>&1 | %PEBuilderDir%\plugin\autobuild\files\mtee /+ %PEBuilderDir%\autobuild_install.log
echo; OutDir : %OutDir% 2>&1 | %PEBuilderDir%\plugin\autobuild\files\mtee /+ %PEBuilderDir%\autobuild_install.log
echo; PEUtilsPath : %PEUtilsPath% 2>&1 | %PEBuilderDir%\plugin\autobuild\files\mtee /+ %PEBuilderDir%\autobuild_install.log
echo. 2>&1 | %PEBuilderDir%\plugin\autobuild\files\mtee /+ %PEBuilderDir%\autobuild_install.log
:mkisofs
:: ======================================================
:: rename original mkisofs and copy wrapper into place.
:: ======================================================
echo. 2>&1 | %PEBuilderDir%\plugin\autobuild\files\mtee /+ %PEBuilderDir%\autobuild_install.log
echo STEP 1: rename the original mkisofs and copy mkisofs wrapper into place 2>&1 | %PEBuilderDir%\plugin\autobuild\files\mtee /+ %PEBuilderDir%\autobuild_install.log
echo. 2>&1 | %PEBuilderDir%\plugin\autobuild\files\mtee /+ %PEBuilderDir%\autobuild_install.log
IF EXIST %PeBuilderDir%\mkisofs.org del %PeBuilderDir%\mkisofs.exe 2>&1 | %PEBuilderDir%\plugin\autobuild\files\mtee /+ %PEBuilderDir%\autobuild_install.log
IF EXIST %PeBuilderDir%\mkisofs.exe ren %PeBuilderDir%\mkisofs.exe *.org 2>&1 | %PEBuilderDir%\plugin\autobuild\files\mtee /+ %PEBuilderDir%\autobuild_install.log
IF EXIST %PEBuilderDir%\plugin\autobuild\files\mkisofs_wrapper.exe xcopy /y %PEBuilderDir%\plugin\autobuild\files\mkisofs_wrapper.exe %PeBuilderDir%\ 2>&1 | %PEBuilderDir%\plugin\autobuild\files\mtee /+ %PEBuilderDir%\autobuild_install.log
IF EXIST %PeBuilderDir%\mkisofs_wrapper.exe ren %PeBuilderDir%\mkisofs_wrapper.exe mkisofs.exe 2>&1 | %PEBuilderDir%\plugin\autobuild\files\mtee /+ %PEBuilderDir%\autobuild_install.log
:wrapper
:: ======================================================
:: rename original wrapper.cmd and copy wrapper.cmd into place.
:: ======================================================
echo. 2>&1 | %PEBuilderDir%\plugin\autobuild\files\mtee /+ %PEBuilderDir%\autobuild_install.log
echo STEP 2: rename the original autobuild.cmd and copy new autobuild.cmd into place 2>&1 | %PEBuilderDir%\plugin\autobuild\files\mtee /+ %PEBuilderDir%\autobuild_install.log
echo. 2>&1 | %PEBuilderDir%\plugin\autobuild\files\mtee /+ %PEBuilderDir%\autobuild_install.log
IF EXIST %PeBuilderDir%\autobuild.cmd ren %PeBuilderDir%\autobuild.cmd *.org 2>&1 | %PEBuilderDir%\plugin\autobuild\files\mtee /+ %PEBuilderDir%\autobuild_install.log
IF EXIST %PEBuilderDir%\plugin\autobuild\files\autobuild.cmd xcopy /y %PEBuilderDir%\plugin\autobuild\files\autobuild.cmd %PeBuilderDir%\ 2>&1 | %PEBuilderDir%\plugin\autobuild\files\mtee /+ %PEBuilderDir%\autobuild_install.log
:end_install
SET ERROR_LEVEL=0
echo. 2>&1 | %PEBuilderDir%\plugin\autobuild\files\mtee /+ %PEBuilderDir%\autobuild_install.log
echo Install finished. You are now ready to use autobuild. 2>&1 | %PEBuilderDir%\plugin\autobuild\files\mtee /+ %PEBuilderDir%\autobuild_install.log
echo. 2>&1 | %PEBuilderDir%\plugin\autobuild\files\mtee /+ %PEBuilderDir%\autobuild_install.log
:EXIT
::exit
pause
:: ===============================================================
:: INSTALL: install autobuild.
:: ===============================================================
:: ===============================================================
@echo off
SET PeBuilderDir=%1
SET PEUtilsPath=%2
SET OutDir=%3
SET ISOFile=%4
IF "%PeBuilderDir%"=="" SET PeBuilderDir=.\
SET last_char=%PEBuilderDir:~-1%
IF "%last_char%"=="\" set PEBuilderDir=%PEBuilderDir:~0,-1%
IF "%ISOFile%"=="" FOR /f "tokens=1* delims== skip=1 eol=;" %%a IN (%PEBuilderDir%\input.inf) DO IF "%%a"=="isofile" SET ISOFile=%%b
IF "%FullOutDir%"=="" FOR /f "tokens=1* delims== skip=1 eol=;" %%a IN (%PEBuilderDir%\input.inf) DO IF "%%a"=="fulloutdir" SET OutDir=%%b
SET last_char=%OutDir:~-1%
IF "%last_char%"=="\" set OutDir=%OutDir:~0,-1%
IF "%PEUtilsPath%"=="" SET PEUtilsPath=%PeBuilderDir%\temp
SET last_char=%PEUtilsPath:~-1%
IF "%last_char%"=="\" set PEUtilsPath=%PEUtilsPath:~0,-1%
PATH=%PATH%;%PEBuilderDir%\plugin\autobuild\files\
echo; INSTALL.cmd started at 2>&1 | %PEBuilderDir%\plugin\autobuild\files\mtee %PEBuilderDir%\autobuild_install.log
echo; Date: %DATE% 2>&1 | %PEBuilderDir%\plugin\autobuild\files\mtee /+ %PEBuilderDir%\autobuild_install.log
echo; Time: %TIME% 2>&1 | %PEBuilderDir%\plugin\autobuild\files\mtee /+ %PEBuilderDir%\autobuild_install.log
echo; ----------------------------------------- 2>&1 | %PEBuilderDir%\plugin\autobuild\files\mtee /+ %PEBuilderDir%\autobuild_install.log
echo; PEBuilderDir: %PEBuilderDir% 2>&1 | %PEBuilderDir%\plugin\autobuild\files\mtee /+ %PEBuilderDir%\autobuild_install.log
echo; ISOfile : %ISOFile% 2>&1 | %PEBuilderDir%\plugin\autobuild\files\mtee /+ %PEBuilderDir%\autobuild_install.log
echo; OutDir : %OutDir% 2>&1 | %PEBuilderDir%\plugin\autobuild\files\mtee /+ %PEBuilderDir%\autobuild_install.log
echo; PEUtilsPath : %PEUtilsPath% 2>&1 | %PEBuilderDir%\plugin\autobuild\files\mtee /+ %PEBuilderDir%\autobuild_install.log
echo. 2>&1 | %PEBuilderDir%\plugin\autobuild\files\mtee /+ %PEBuilderDir%\autobuild_install.log
:mkisofs
:: ======================================================
:: rename original mkisofs and copy wrapper into place.
:: ======================================================
echo. 2>&1 | %PEBuilderDir%\plugin\autobuild\files\mtee /+ %PEBuilderDir%\autobuild_install.log
echo STEP 1: rename the original mkisofs and copy mkisofs wrapper into place 2>&1 | %PEBuilderDir%\plugin\autobuild\files\mtee /+ %PEBuilderDir%\autobuild_install.log
echo. 2>&1 | %PEBuilderDir%\plugin\autobuild\files\mtee /+ %PEBuilderDir%\autobuild_install.log
IF EXIST %PeBuilderDir%\mkisofs.org del %PeBuilderDir%\mkisofs.exe 2>&1 | %PEBuilderDir%\plugin\autobuild\files\mtee /+ %PEBuilderDir%\autobuild_install.log
IF EXIST %PeBuilderDir%\mkisofs.exe ren %PeBuilderDir%\mkisofs.exe *.org 2>&1 | %PEBuilderDir%\plugin\autobuild\files\mtee /+ %PEBuilderDir%\autobuild_install.log
IF EXIST %PEBuilderDir%\plugin\autobuild\files\mkisofs_wrapper.exe xcopy /y %PEBuilderDir%\plugin\autobuild\files\mkisofs_wrapper.exe %PeBuilderDir%\ 2>&1 | %PEBuilderDir%\plugin\autobuild\files\mtee /+ %PEBuilderDir%\autobuild_install.log
IF EXIST %PeBuilderDir%\mkisofs_wrapper.exe ren %PeBuilderDir%\mkisofs_wrapper.exe mkisofs.exe 2>&1 | %PEBuilderDir%\plugin\autobuild\files\mtee /+ %PEBuilderDir%\autobuild_install.log
:wrapper
:: ======================================================
:: rename original wrapper.cmd and copy wrapper.cmd into place.
:: ======================================================
echo. 2>&1 | %PEBuilderDir%\plugin\autobuild\files\mtee /+ %PEBuilderDir%\autobuild_install.log
echo STEP 2: rename the original autobuild.cmd and copy new autobuild.cmd into place 2>&1 | %PEBuilderDir%\plugin\autobuild\files\mtee /+ %PEBuilderDir%\autobuild_install.log
echo. 2>&1 | %PEBuilderDir%\plugin\autobuild\files\mtee /+ %PEBuilderDir%\autobuild_install.log
IF EXIST %PeBuilderDir%\autobuild.cmd ren %PeBuilderDir%\autobuild.cmd *.org 2>&1 | %PEBuilderDir%\plugin\autobuild\files\mtee /+ %PEBuilderDir%\autobuild_install.log
IF EXIST %PEBuilderDir%\plugin\autobuild\files\autobuild.cmd xcopy /y %PEBuilderDir%\plugin\autobuild\files\autobuild.cmd %PeBuilderDir%\ 2>&1 | %PEBuilderDir%\plugin\autobuild\files\mtee /+ %PEBuilderDir%\autobuild_install.log
:end_install
SET ERROR_LEVEL=0
echo. 2>&1 | %PEBuilderDir%\plugin\autobuild\files\mtee /+ %PEBuilderDir%\autobuild_install.log
echo Install finished. You are now ready to use autobuild. 2>&1 | %PEBuilderDir%\plugin\autobuild\files\mtee /+ %PEBuilderDir%\autobuild_install.log
echo. 2>&1 | %PEBuilderDir%\plugin\autobuild\files\mtee /+ %PEBuilderDir%\autobuild_install.log
:EXIT
::exit
pause
save it as autoinstall.cmd and save it in your pe builder dir. Run it and let me know if that fixes the issue for you..
@littlebugger I have tested this cmd file and it appears to run properly. At least when I run it by hand. Could you try it on your end also and make sure it works.
If this does work then I also have a few more fixes that need to be added. I'll email the whole set over to you so we can get this fixed as soon as possible.
I need to fix
1) make it so that it will not fail is massstorage is not added.
2) add the missing inf file for those that dont have it.
I have already added the other fixes. That I can think of.
I have not tried the most recent post from WebMedic but I just did a plain build of the 2.55 and the BTS drivers and recevied the same result. I did this as administrator in safemodfe with no AV. I get to this in the log file for PE...
I get no ISO... No countdown of stuff like before... no cmd prompt other than when the driver pack is installed into the PEB folder. I get one then but nothing later. I again had to disable the IDSuite plugin again. I don't know why I have to disable that... Always says that it is missing files.
I only get any klind of a build window is when I run mkisofs manually.
I will also look into what Web had said and see if that make a differance.
Thanx again to everyone for there hard work and sacrifice to test and build this tool to the point that it is today!
QUOTE
Building ISO image
Running external program:
E:\pebuilder313\mkisofs.exe -iso-level 4 -force-uppercase -volid "BartPE" -b bootsect.bin -no-emul-boot -boot-load-size 4 -hide bootsect.bin -hide boot.catalog -o "E:\temp ber\pebuilder.iso" "E:\pebuilder313\BartPE"
Process done.
Build process done...
Running external program:
E:\pebuilder313\mkisofs.exe -iso-level 4 -force-uppercase -volid "BartPE" -b bootsect.bin -no-emul-boot -boot-load-size 4 -hide bootsect.bin -hide boot.catalog -o "E:\temp ber\pebuilder.iso" "E:\pebuilder313\BartPE"
Process done.
Build process done...
I get no ISO... No countdown of stuff like before... no cmd prompt other than when the driver pack is installed into the PEB folder. I get one then but nothing later. I again had to disable the IDSuite plugin again. I don't know why I have to disable that... Always says that it is missing files.
I only get any klind of a build window is when I run mkisofs manually.
I will also look into what Web had said and see if that make a differance.
Thanx again to everyone for there hard work and sacrifice to test and build this tool to the point that it is today!
yes it most likely is if you look in your pebuilder dir and you dont see an autobuilder_install.log then it is not even installed and the drivers are not going ot be running properly without it being installed.
The thing is that the drivers release is an SFX archive like it's always been. I had it, after extraction, extract a script that it would automatically run. This script was supposed to automatically run the aforementioned install.cmd file so everything was fine (and thus allows a tedious extra step to be skipped). For many, this has worked fine. For others like yourselves, it seems it hasn't. Thus, it seems webmedic has made a new script of which can be run directly in the main pebuilder folder and thus I don't need to create a script to go to the autobuild folder and run the install.cmd script from there. This should hopefully fix the errors and other problems we've been running into lately.
@webmedic
Please send me the completely updates ASAP so I can test them and then get a new release uploaded. I wont change the release version, just overwrite the previous for now. Thanks.
@webmedic
Please send me the completely updates ASAP so I can test them and then get a new release uploaded. I wont change the release version, just overwrite the previous for now. Thanks.
I've also added the stuff for checking to see if the mass storge drivers have been added but it is having issues. I'm working on it though.
I'll send it as soon as I can get it to build.
I'll send it as soon as I can get it to build.
@webmedic:
That did it! Thank much for the help. Perhaps my description of the problem will help you guys make the next iteration a little smoother. It's odd that everyone does not have my problem, but many things about software are odd! It seems that the instructions should either have one put in the autoinstall.cmd file and run it, or manually run the install.cmd file in BPE313\plugin\autobuild\.
For lurkers, know that following the procedures in my previous message up to the point of running PEBuilder.exe, I added webmedic's autoinstall.cmd file to the BPE313 directory, ran it, deleted the original BartPE subdirectory, and ran PEBuilder.
That did it! Thank much for the help. Perhaps my description of the problem will help you guys make the next iteration a little smoother. It's odd that everyone does not have my problem, but many things about software are odd! It seems that the instructions should either have one put in the autoinstall.cmd file and run it, or manually run the install.cmd file in BPE313\plugin\autobuild\.
For lurkers, know that following the procedures in my previous message up to the point of running PEBuilder.exe, I added webmedic's autoinstall.cmd file to the BPE313 directory, ran it, deleted the original BartPE subdirectory, and ran PEBuilder.
QUOTE
thanks for that info. It helps greatly. Yes it is not in the origianl instrictions but it the install.cmd should have been run. It would appear as though some are having this issue while others are not. It's ok But for now I would like you to try something.
ok good news it build just fine now without mass storage. I would also add that base is only needed if you are running mass storage also. So you dont need base if you are not using mass storage.
I'm running one more check right now. With mass storage enabled jsut to make sure it is working that way also and that I didn't miss something.
Sorry for the delay it should only be a bit longer now. If all goes well I'll send the new files right over for little bugger ot repackage.
I'm running one more check right now. With mass storage enabled jsut to make sure it is working that way also and that I didn't miss something.
Sorry for the delay it should only be a bit longer now. If all goes well I'll send the new files right over for little bugger ot repackage.
QUOTE (TQuestar @ Nov 2 2005, 05:50 PM)
@webmedic:
That did it! Thank much for the help. Perhaps my description of the problem will help you guys make the next iteration a little smoother. It's odd that everyone does not have my problem, but many things about software are odd! It seems that the instructions should either have one put in the autoinstall.cmd file and run it, or manually run the install.cmd file in BPE313\plugin\autobuild\.
For lurkers, know that following the procedures in my previous message up to the point of running PEBuilder.exe, I added webmedic's autoinstall.cmd file to the BPE313 directory, ran it, deleted the original BartPE subdirectory, and ran PEBuilder.
That did it! Thank much for the help. Perhaps my description of the problem will help you guys make the next iteration a little smoother. It's odd that everyone does not have my problem, but many things about software are odd! It seems that the instructions should either have one put in the autoinstall.cmd file and run it, or manually run the install.cmd file in BPE313\plugin\autobuild\.
For lurkers, know that following the procedures in my previous message up to the point of running PEBuilder.exe, I added webmedic's autoinstall.cmd file to the BPE313 directory, ran it, deleted the original BartPE subdirectory, and ran PEBuilder.
well part of the isssue here is that we do have a little script running to take care of this durring install but it does not seem to be working for some people.
Hopefully this revision will work for everybody. And should take care of why most seem to be not having issues but a few are.
Excellent work guys....glad to see you guys figured it out. Sorry to everyone for the problems. Luckily I haven't had the chance to contact the other mirrors....so they won't have to upload again.
I would suggest though....that we call this version 2.01.
I would suggest though....that we call this version 2.01.
ok I have sent the updated files to littlebugger.
I also sent a second email with a small fix for the autoinstall.cmd and it now autodeletes itself when it is done.
I also sent a second email with a small fix for the autoinstall.cmd and it now autodeletes itself when it is done.
QUOTE (webmedic @ Nov 2 2005, 07:06 PM)
ok I have sent the updated files to littlebugger.
I also sent a second email with a small fix for the autoinstall.cmd and it now autodeletes itself when it is done.
I also sent a second email with a small fix for the autoinstall.cmd and it now autodeletes itself when it is done.
Thanks so much. You figured out the MassStorage bug in no time
Good work
yes it now no longer requires the mass storage to be there for it to build properly. I have tested with hte mass storage both on and off. In both cases it builds properly and in both cases it also booted into virtual pc just fine. I have not had a chance yet to test it on a live system to check things but I see no reason why it should not work.
You never know though. We will see but hopefully this will take care of hte last remaining issues we were having.
You never know though. We will see but hopefully this will take care of hte last remaining issues we were having.
QUOTE (webmedic @ Nov 2 2005, 05:06 PM)
ok I have sent the updated files to littlebugger.
I also sent a second email with a small fix for the autoinstall.cmd and it now autodeletes itself when it is done.
I also sent a second email with a small fix for the autoinstall.cmd and it now autodeletes itself when it is done.
I received the autoinstall.cmd file but no other files. Please re-send when you get a chance. I'll try to find some time tonight to get things updated, and maybe call the new drivers version 2.01 or something... I'm just leaving work at the moment...
@ WebMedic
I also don't why now someone wouldn't use the MassStorage DriverPack; that is one of the best parts of BTS.
Anyway, at least there are more options now.
Also, you mentioned that with the updates Base is not required; is this still accurate?
Thanks again
I also don't why now someone wouldn't use the MassStorage DriverPack; that is one of the best parts of BTS.
Anyway, at least there are more options now.
Also, you mentioned that with the updates Base is not required; is this still accurate?
Thanks again
I want ot be carefull how I put that as the main plugin is still required but as for the 7z packs yes the only reason for base is so that the mass storage drivers can be installed. If you are not installing the mass storage drivers then you dont need driverpack_base either.
I want to make it very clear thouhg that you still need ot enable the main driverpack plugin. It will not error if driverpack_base is not there but none of the other drivers will be installed without it.
I made sure in the plugins to make sure nad not call it base anywere and also (needed for the other driver packs) kind of message so it should be very clear I hope.
I want to make it very clear thouhg that you still need ot enable the main driverpack plugin. It will not error if driverpack_base is not there but none of the other drivers will be installed without it.
I made sure in the plugins to make sure nad not call it base anywere and also (needed for the other driver packs) kind of message so it should be very clear I hope.
QUOTE (LittlBUGer @ Nov 2 2005, 07:23 PM)
QUOTE (webmedic @ Nov 2 2005, 05:06 PM)
ok I have sent the updated files to littlebugger.
I also sent a second email with a small fix for the autoinstall.cmd and it now autodeletes itself when it is done.
I also sent a second email with a small fix for the autoinstall.cmd and it now autodeletes itself when it is done.
I received the autoinstall.cmd file but no other files. Please re-send when you get a chance. I'll try to find some time tonight to get things updated, and maybe call the new drivers version 2.01 or something... I'm just leaving work at the moment...
sure no problem I'll send an updated version with the latest versions of all the files.
This way you wont have to worry about it.
Hello,
I was wondering how to change the label of my Cd from "TrustyBootCDXP" to my own label.
Is 'Builder>Options>Advanced> Label' in PEbuilder still the correct method with your Drivers v.2.0?
I was wondering how to change the label of my Cd from "TrustyBootCDXP" to my own label.
Is 'Builder>Options>Advanced> Label' in PEbuilder still the correct method with your Drivers v.2.0?
hm thats in th eautobuild plugin I have it set to look for a name and if it does not find one then it autosets it to that name.
If you want to change it look under plugins\autobuild\files\autobuild.cmd
it's on line 31 of that file. Set it to whatever you would like.
If you want to change it look under plugins\autobuild\files\autobuild.cmd
it's on line 31 of that file. Set it to whatever you would like.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.