Jump to content

lightsout

Member
  • Posts

    86
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by lightsout

  1. I've seen this reported elsewhere, but I didn't see a fix for it. When installing the ATi Catalyst Centre with the bts_dps_finish.cmd command it would extract it ok, but the run would fail. If you try it manually, this event log message appears: To fix it, I went to this URL http://consumer.installshield.com/kb.asp?id=Q108322 and downloaded this http://support.installshield.com/kb/files/...2/ISScript9.zip file (an MSI is in the ZIP file). Then the CCC installed fine. Perhaps worth putting this in a driverpack? Or some check to see if it is installed?
  2. No problem. As you can likely tell from my post count I'm new here as well, but I'm fairly certain method 2 does avoid that problem. As for Win2k itself, I see no reason in theory why it shouldn't work but I've never tried it. It may well depend on the driver involved...
  3. With method 2, you avoid the 4096 limit as I understand it due to the way it works. I'd guess a bad driver - do you have a different machine to try it on?
  4. Ok, one more question. (and another reply to myself ) SMS OSD uses WinPE (I can't use BartPE) to install the WIM images. I've browsed the forum and the suggestion I last saw is that the C++ of BTS DPs will support WinPE. This isn't out yet as I understand it. Is this true? Or is there anyway I can hack with WinPE to include the mass storage & LAN drivers as well? Thanks!
  5. Nope, I did use method 1 honest. I've attached a .txt file which shows the registry entry for the HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\DevicePath key. Note, it is longer than 4096 bytes but when you replace %systemdrive% with c: then it goes down below 4096 to ~3500. I presume a reg entry with REG_EXPAND_SZ would likely do this when queried. Anyway, I have been able to use the driverpack with a SMS OSD deployment. It was quite simple really. 1. Unpack the driverpacks you want to c:\d (need to keep the directory names short to save space in oempnpdriverspath). 2. In c:\sysprep\sysprep.inf - ensure the oempnpdriverspath is set to the correct directories. 3. Image machine. On install, it will scan these drivers paths and install everything normally. I've not tried imaging a Windows install based off the driver packs yet, nor have I tried generating a WinPE boot environment from the driver packs. It is pretty cool. B) blah.txt
  6. As you know much more on the subject, I'll agree with you. I thought a control panel was simply a *.cpl file in the relevant (system32?) directory. I presume it is more subtle than that! So what needs to be done? Is there anything I can test for you?
  7. Would missing the control panel icon really cause that? I've tried copying it in manually but it hasn't helped. The control panel for audio devices still shows no soundcard (even though device manager does) and any attempt to play a sound fails (your sound card in use it says).
  8. Woooh! Thanks for adding the Sigmatel HDA driver, which is what I and several other people asked for in the end. So good news - I just installed a system using the latest driver pack and it was detected just fine when looking in device manager. It appears as "SigmaTEL High Definition Audio Codec" and it is version 5.10.4866.0. The bad news - in the "sound and audio devices" control panel item it says "no sound card present". On the audio tab it just shows me the modem input/output ports, so I can't even select the SigmaTEL for output or input. So I then told it update driver for the device and I pointed it back to version supplied by Gateway that we've extracted for inclusion into OemPNPDriversPath - 5.10.4486.0 - it asked for a reboot, and the sound worked fine and the control panel worked as expected. It should be noted, a SigmaTEL control panel icon appeared in the control panel at this point. At this point, I told Windows to roll-back the driver version to the 4866 version and rebooted. It still worked on the new drivers. The Gateway driver has 32 files (inc said control panel program) as opposed to yours which has 6. My only thought is that Gateway driver has something extra which is also required. Any thoughts? Has anyone else tested the new SigmaTEL HDA driver yet? Thanks!
  9. Just did a clean install of Windows XP using the latest driver pack, and this driver wasn't found: Sigmatel Gateway Any chance of getting it added? I'm more than happy to test it for you if needed. FYI, the system I'm installing it on is a Gateway-6500. Thanks!
  10. Ok, additional factoid. I just installed a copy of WinXP SP2 with all of the driver packs on it. On checking the registry, I found the DevicePath registry key is 6972 bytes in length - over 4096. Everything seems ok though? So is that 4096 byte length bogus? Or does it exclude the %systemdrive% part? Or resolve %systemdrive% down to c: which then does make it's effective length less than 4096 (~3500 in fact).
  11. Hi folks! Ok, this may wander a bit as I'm not exactly sure how the installation of Windows goes once you've slipstreamed the driver packs into them. The key problem is oempnpdriverspath, which in Windows XP can't be longer than 4096 bytes. Due to the excellent work of Bâshrat there are too many drivers. As when you run SMS OSD, you install Windows as per normal then install sysprep. You use an image generation CD which SMS provides which runs sysprep with the -reseal option and then you boot from to create the WIM image SMS uses to deploy Windows XP. Of course, you can give SMS a sysprep.inf file which has oempnpdriverspath defined in it. The problem I face is on this part as Microsoft says this: Specfically, the problem is that it adds %SystemDrive% to every entry in oempnpdriverspath. This will easily overflow the 4096 bytes I've got. From looking at the option 1 slipstream method, the winnt.sif file is used from the oempnpdriverspath. I've caught some hints that this isn't subject to the 4096 byte rule? Is that true? So what I want to know is - how can I get my OSD WIM images to use the driver packs? 1. If I use an option 1 slipstream method, and then image that for SMS deployment, will that allow me to use all of the available drivers (assuming I don't delete them)? 2. Can I somehow stop sysprep from adding %SystemDrive% to everything? 3. Can I put a reference elsewhere (winnt.sif?) that will pick-up the drivers instead? I hope I'm missing something obvious, so if someone can set me straight then that'd be super! Thanks! Lights
×
×
  • Create New...