Jump to content


  • Content Count

  • Joined

  • Last visited

  • Donations


Community Reputation

0 Neutral

About androidtopp

Contact Methods

  • Website URL
  1. Well, I did find a solution...but not a good one, in this context. I switched from injecting the x64 mass storage drivers from the sysprep.ini to injecting from driver packages in my SCCM task sequences. So that fixed the issue, but unless you have SCCM, that's not a terribly helpful suggestion.
  2. TranceEnergy, That's exactly what I've tried uysed - any number of different versions of the drivers from Dell. I have no problem with this when it comes to x86 - it's just x64 where I have issues. Interestingly enough, even after I disable the step in my task sequence where the machine being imaged contacts the SCCM server for drivers (leaving only the Windows XP build in drivers and a couple MSDs - Intel Matrix, SAS5, SAS6) I have the exact same issue. Starting to get very frustrated...I've disabled everything I can think of, but I need NIC, SATA (for CD-ROM) and obviously the SAS to be enab
  3. I am also seeing this issue - Interestingly enough, my Precision 490 works fine (SAS5/iR controller) but a Precision T5400 (SAS6/iR controller) hangs at acpitabl.dat. Both are being deployed the exact same Windows XP x64 SP2 OS task sequence from SCCM. Both complete their minisetup fine (although the T5400 takes a long time to do so, I assume related to this issue) but the 490 continues to work perfectly while the T5400 never completes the post-minisetup reboot. Anyone else see this issue?
  4. So, I've heard in a couple places now that one reason some settings are being ignored is becuase the version of Vista I'm using (downloaded from my MSDN site) is NOT a VLK version, and thus does not observe a lot of the unattended settings. Some people with better beta connections than I have (like real members of the TAP, or something) might have actual VLK versions of the beta. Does anyone know if there is any truth to this rumor?
  5. Fizban, I've been quite careful to post all my difficulties. I'm still trying to get my sysprepped image to work...this time I'm injecting the driver database in offline mode (which, according to the log file that it creates, works just fine) and sysprepping straight to the OOBE phase, skipping audit. Now, on the first reboot after sysprep, I'm told that "Windows cannot configure this computer's hardware" or something to that effect...even though this is the build machine I had Vista installed to before I ran sysprep. Argh!
  6. So maybe I'm not totally crazy...not all of the unattended settings are working properly. And while we're at it...what's the deal with the new (5728 and 5744) builds not working with the new version of the BDD (3.3)? The BDD is useless to businesses if they can't test what Microsoft is actually planning on releasing...
  7. Yes, the file does validate properly inside the WAIK. But you're right...it's doesn't look correct. This might explain why my Sidebar constantly appears on first boot.
  8. This is my unattend.xml file. Sorry the tabbing goes away when I post...If anyone knows how to fix this, lemme know and repost/edit. <?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <settings pass="windowsPE"> <component name="Microsoft-Windows-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <DiskConfiguration>
  9. Fizban, Perhaps I should more clearly explain what I'm doing. I think I understand what you're saying, but I want to make sure. I've got TONS of XP image/build experience, but Vista and all the phases are kinda throwing me for a loop. I have an environment comprised 100% of IBM Thinkpad laptops. Anywhere from the T40 to the T43, and a few X41 tablets thrown in for good measure. I want to have an image that I can deploy to any of these machines, so I don't have to worry about building/maintaining a per machine image. To that end, I was following these steps: 1. Deploy image to baseline machine,
  10. Fizban, if I don't boot to audit mode, the driver path I inserted using the System Image Manager won't be included. Should I instead be injecting these drivers in offline mode? Thanks, Andrew
  11. Is anyone having big problems with preparing an image for deployment? Most of the settings I am specifying in the Windows AIK, such as turning off the Sidebar, or providing the product key, are completely ignored by the Windows Setup process. I know the unattend.xml file is getting used, becuase some of the settings are being applied, and they are specified in the same setup phase as those that aren't working at all...so...can I chalk this up to beta? Anyone else noticing this? Also, once I resign myself to manually tweaking my beta build, after I sysprep and image, I can't redeploy the image
  12. i figured it out. for anyone trying this, be sure to use the bootloader files from a PE 2005 CD, not from a bart build. they're not quite the same, apparently.
  13. sorry if this has been asked before, but the only stuff i can find on it is from the 911cd.net forums, which are down from that hack last week. i am trying to boot bart PE to a ramdisk. the /inram switch does not accomplish what i need. i've found several things to try, but nothing much works. i have WinPE 2005, so i could theoretically use their ramdisk boot method, but i need to use the actual BartPE builder. whenever i try to use the WinPE 2005 ramdisk method, i get a blue screen 0x0000007B error, inaccessible boot device. i assume i'm missing some mass storage controllers...can anyone poin
  14. where is this formatufd.exe file? i see it in the documentation, but it is nowhere to be found on my WinPE 2005 CD...
  15. Has anyone had selective luck with this working? I have a Lexar Jumpdrive 256MB, and the install went slicker than you know what. Just copied everything over, renamed some files, and I'm off to the races...as long as I boot an IBM using the key. My workplace has a lot of Dell and a lot of IBM laptops and desktops, depending on who is cheaper during each purchasing cycle, and the Dells don't seem to want to boot from my key. I've tried the GX270, GX280, D400, and D600, and each time, I get a stop code of 0x0000007b. To me, this means the right drivers for the HDD contollers aren't installed, bu
  • Create New...