dbradtbe

Member
  • Content count

    17
  • Joined

  • Last visited

Community Reputation

0 Neutral

About dbradtbe

  • Birthday 04/10/1967
  1. I am pretty sure I have gotten this to work. Long winded approach though. First you need to start the install manually and when it stops at the untrusted driver stage look in the TEMP folder and find the sub folder that contains the extracted Clone Drive Files. Take a copy of the vclone.cat file in this folder. Cancel the installation. This may still say this has installed but the driver will not work. Just got to Add/Remove programs and remove it. Using the vclone.cat file from the files you copied right click and select properties. Select Digital Signatures Select Elaborate Bytes AG in the Signature list box. Click Details On the Digital Signature Details window select the General Tab Click View Certificate On the Certificate window select the Details Tab Click Copy to File On the Certificate Export Wizard window click Next I chose the Cryptographic Message Syntax Standard - PKCS #7 Certificates (.P7B) radio button and then ticked the Include all Certificates in the certification path if possible. Click Next Save the file to where you want to keep it. Click Next Click Finish Click Ok Close all the open windows. Now to pre import the certificate into the certificate store so that the software will install silently I used the following command line with administrative priviledges. certutil -addstore "TrustedPublisher" vclone.p7b This import the certificate that we exported before and now run setupvirtualclone.exe /S to install silently. So with a little prepartion it should be possible to completely silently install Virtual Clone Drive With these two commands. certutil -addstore "TrustedPublisher" vclone.p7b setupvirtualclone.exe /S
  2. Not sure if it is related or may help but someone I was talking to the other day said that they where having a problem with a package they where deploying which had the same guid as an existing package and the error they got sounded very much like this error. Don't know if it will help but maybe someone can look to see if their is a guid issue for Media Center and something else that exists in Server 2008
  3. Is the insatllation point an administrative installation. If so this will not work you cant get the cache to work from a Administrative installation point which also means that you cant slipstream the service pack into your installation files and still bea bel to cache them. You must use an original CD or a copy of the files from an original CD and then apply the service pack to the installation after the initial install is completed.
  4. I found a missing line in the BTS_DPs_ATI_Mobility.INF file the ATIVCOXX.DLL list is missing in the [sourceDisksFiles] section and you are prompted for a location for the file when trying to install it. All you need to do is add the following line to that section of the file ativcoxx.dll=1 David Bradtberg
  5. You will need to put the new INF and SYS file for the driver into the i386 folder for your source OS on your RIS server and then stop and start the BINLSVC on the RIS server. This is to cause the recreation of the PNF files on the RIS server. I have just finished doing this at work this week. I also found that I have to edit the INF file to take out any references to to a B57w2k.sys and replace that with B57xp32.sys otherwise it will complain about an error in the B57w2k.sys file which doesn't exist anyway. I downloaded the latest drivers from Broadcom and used them when I did this.
  6. Sounds great Bâshrat look forward to it. About the only other Video driver that I have in my collection is the Intel video drivers.
  7. Renaming the INF will allow you to support all the different subsystem ID's of all the different manufacturer's rather than going to all the effort of trying to combine the INF's from mutliple manufacturers. The reason that this is a possible is that they all use the same basic files and it only seems to be the different settings that each manufacturer allows that is the only difference. So far I havent found one that wont work with the latest drivers even if the INF came with older drivers. David
  8. Hi You don't necessarily have to compare all of the vendors INF files you could just rename the INF file to suit the manufacturer's name as the name of the file doesn't matter. I have successfully merged the files of the manufacturers that I have keeping the latest version of all the drivers works. I went to the effort of merging the files but it is not necessary if you just renamed them as required. As the main difference is the subsystem id's and XP will take care of searching all the files and finding the right one. As to Bashrat having problems extracting the Realtek Drivers they seem to do two packages now one of which is usually called ap_a36*.exe which seems to contain codecs etc and extra apps for the sound card and then a second package called wdm_a36*.exe which contains the actual sound card drivers. David
  9. I think changing the directory naming order wont fix the problem for everyone. Different people are going to want different cards to be picked up first. For all the machines that I have seen the problem on now (HP,DELL,IBM,ASI) I have been able to resolve the issue by combining the INF file for that card for one that already exists which is for the same card but differening SUBSYS ID's in the INF card the driver files have been the same for each card some older and some newer drivers I have always kept the latest version of the files i have found and so far they have worked with all the other hardware vendors as well. I don't think ordering is necessarily the answer either as from my investigation of the setup log files is that all directories are process and then if multiple drivers are found that will work they are then given a weighting/order inside the log file depending on how close they match the specific card. I belive this goes down to the SUBSYSTEM id. One thing that I havent tried yet is to put two versions of the same driver in and see which one gets chosen I would hope that the final determining factor as to which one is chosen is the lastest/newer driver will win. Dave
  10. I think I am close to understanding the problem and have a solution that works for me now. It comes down to the specific subsystem ID in the INF file from what I can find out. We had yet another different vendor deliver a desktop today this time it was IBM with a 8188-47M or whatever that is. Yet gaian it is another motherboard with a sound card based on the relatek AC97 chipset. But it was blue screening evening when I was using the lastest 3.65 drivers from realtek released last week. So I did a little more investigation and found that it was choosing the generic realtek driver when it couldn't find one that matched the specific subsystem of the card. It could match the vendor and the device ID in the INF but not the subsystem. All this being said if I rebooted after the blue screen XP would install and just not install any XP drivers and I could use the realtek drivers then ok but not for a unattended install.???? So i then went to the IBM website and downloaded the drivers recommended by them and found they came very close t matching one of the smwdmch5.inf that other drivers use so I updated the common files and then merged the two inf files copying sections that where needed from each file but alot was duplicated. Tried a build on the IBM after that and it built cleanly no blue screen any more. So I think this maybe a very hard problem to get rid of completely without trying to merge INF files from many motherboard manufacturers or to put many copies of what seem to be the same drivers in the path as well which then may get out of hand in length. As we still build from a DOS boot disk the path when running winnt.exe is only 1024 characters even though they usually say it is 4096 characters that is only when you use winnt32.exe to build or boot from a true Windows XP bootable CD. I have to go back a test all the other PC's that I build to make sure I havent broken any of them but doubt that I have with what I have done. David
  11. I tried the new realtek drivers on Friday and they seemed to work but need to check it out properly on Monday. Have been slowly adding drivers back one folder at a time to try to work out which one was the problem driver but I was also updating them as I went if possible. So far have pretty well all back in except the VIA drivers. But like i said I have updated the Realtek and NVidia drivers. Dave
  12. I am not sure where you can get the KB download from as it comes on an Intel Driver CD that came with the PC that I am working with. As far as the Bios updates that will not resolve the issue I am having with this Portcls.sys as I know both the Dell Laptop and the HP DC7100 have the most up to date available Bios from the Manufacturers. My guess is that is it a duplicate Device ID problem between drivers as the specific ID that I beleive is the problem is 266E which appears in a number of the INF files in the Audio Driver Pack and in a couple of other drivers I am looking at as well. Still need to test my theory about ordering in the OEMPNPDriverspath to see if it makes any difference.
  13. Guys I have had exactly the same problem with a new HP DC7100 915 Based chipset PC. On closer inspection of the drivers on the Intel Installer CD there is a Hotfix from Microsoft relating to High Definition audio cards and there is a new Portcls.sys in this hotfix. KB835221 But so far I have had to rem out the lines for the specific device ID of the audio card on the HP from all other driver files so that it uses the specific driver for that card. I am about to try putting the other drivers back in but move that directory to be the first entry in my OEMPNPDriversPath line in my winnt.sif file. I tried updating my source to include the new portcls.sys but that didn't seem to work and my machine still BSOD during the driver installation. David
  14. I tried changing them all except the Boot Disk to Dynamic but they are all still picked up and founf during the booting of the unanttended CD so the problem still appears. Does anyone know if you can change the disk lettering etc if I booted from BartPE or something like that?. David B
  15. I was wondering if anyone knows a way of doing this. I have a Gigabyte motherboard with 8 hard drives attached to it. 2 via SATA in a Raid 0 which I want to appear as C Drive when it boots from CD but the other on board IDE controlled ahrd drives always come up as C Drive etc the best I have ever gotten is to get it to appear as E Drive unless I disconnect all the other drives. Does anybody know a way of changing this order in any way. One problem is that some of the IDE drivers are built into XP so it will always detect them first even when I use F6 to add drivers or slipstream them into the build using RYAN's script and files. David B