Everything posted by Jazkal
-
windows xp unattended installation via bartpe fails
Here is my command line, that I use under WinPE: x:\wxp\I386\winnt32.exe /s:x:\wxp\I386 /syspart:C /tempdrive:C /unattend:B:\winnt.sif /noreboot I changed it to meet your needs. Try that out and let me know.
-
windows xp unattended installation via bartpe fails
It would help if you gave the exact command line your using, as well as the unattend.txt file contents (minus the key of course).
-
Cannot Authenticate to Server: Incorrect Function
Is your DHCP server handing out DNS info? On your WInPE build, once you get it loaded and it has an IP, run: ipconfig /all And see what it has for DNS.
-
Preventing closure of WinPE environment
Yep, HTA would be my first choice. But I am going to be moving my HTA's to AutoIt3 here in the near future.
-
PE 2.0 Boot Screen
Any one know how to edit the: "Windows is loading files..." You could do it under WinPE v1.6 and before, but I've had no luck with v2.0 And zorphnog, good working putting that together.
-
Windows XP x64, WinPE and pxelinux
sorry about that, too early in the morning for replys
-
ImageX /Append
Our current Image count is 64. We use "append" to have a single WIM file with 6-8 images in each. Because WIM's use "single instance" storage, we cut our 130+ gigs of images down to 12 gigs stored in WIM's. And when you have to push these images out to multiple datacenters located all over the world, that helps a lot.
-
Windows XP x64, WinPE and pxelinux
Oh, ok. I see what your asking now. Yes you can integrate hardware drivers into a CD\DVD\PXE install. You want to checkout the following: www.hfslip.org www.driverpacks.net
-
Windows XP x64, WinPE and pxelinux
I have two WinPE images. 1) x86 - works on all my 32bit hardware (21 systems and counting) 2) x64 - works on all my 64bit hardware (12 systems and counting) You just need to add the drivers for y9our hardware into your winpe build process.
-
Windows XP x64, WinPE and pxelinux
copy the nslookup.exe to your winpe build before it is finished building. I just tested nslookup in WinPE v1.6, and it seemed to work. Didn't do full testing on it though.
-
Windows XP x64, WinPE and pxelinux
I can verify that AutoIt does work under WinPE x64 (both v1.6 and 2.0).
-
Black Screen with Blinking Cursor
In your first post, can you give me the specifics of steps 4 and 5: 4) Partition Drives 5) Format Partitions (NTFS)
-
Black Screen with Blinking Cursor
I've never had to add this to my WinPE1.6 installs. Are you having to add this to all of your installs, or just on some hardware?
-
[GUIDE] Creating WIM images of Windows XP for system deployment using
Could I make one suggestion? Page 7, item A: Note: WinPE-SRT-Package currently does not work, Microsoft to fix at a later date.
-
Black Screen with Blinking Cursor
And I'm assuming if you use Winpe1.6 with the same install scripts, everything works fine?
-
Boot from SAN - Brainstorm
Chris, can you give me a quick answer as to why you need all four of these versions?
-
Driver trouble with WinPE 2
I haven't done any testing on this (I'm lucky, all our systems have a min of 512mb), but others have pushed the PXE boot ram requirements. And I think the min ram needed to boot via PXE was 384mb, or somewhere around that amount.
-
Black Screen with Blinking Cursor
Since you have that hotfix integrated, have removed all the "fixes" from the WinPE2 build and re-tested it?
-
Black Screen with Blinking Cursor
reg load HKLM\PE-SYS c:\Winpe\Mount\Windows\system32\config\system Reg Add "HKLM\PE-SYS\ControlSet001\Services\vds\Alignment" /t Reg_Dword /v LessThan4GB /d 0 /f Reg Add "HKLM\PE-SYS\ControlSet001\Services\vds\Alignment" /t Reg_Dword /v Between4_8GB /d 0 /f Reg Add "HKLM\PE-SYS\ControlSet001\Services\vds\Alignment" /t Reg_Dword /v Between8_32GB /d 0 /f Reg Add "HKLM\PE-SYS\ControlSet001\Services\vds\Alignment" /t Reg_Dword /v GreaterThan32GB /d 0 /f reg unload HKLM\PE-SYS This code is meant to be used when building your winpe2 image, not once the Winpe2 has loaded into memory. To run this code once winpe2 is up and running, run this code: Reg Add "HKLM\CurrentControlSet\Services\vds\Alignment" /t Reg_Dword /v LessThan4GB /d 0 /f Reg Add "HKLM\CurrentControlSet\Services\vds\Alignment" /t Reg_Dword /v Between4_8GB /d 0 /f Reg Add "HKLM\CurrentControlSet\Services\vds\Alignment" /t Reg_Dword /v Between8_32GB /d 0 /f Reg Add "HKLM\CurrentControlSet\Services\vds\Alignment" /t Reg_Dword /v GreaterThan32GB /d 0 /f I saw your exact problem back in December, but after using this method I have not seen it on any systems since. There is also a hotfix released by microsoft for this issue. I'll post the number on Monday, don't have it here.
-
Win2000 Unattend installation from WinPE v2.0
No problem. Sometimes we all need a little nudge in the right direction.
-
Multicasting w/PE_2: SymantecGhost -Help!
I'm not 100% sure on this, so take it with a grain of salt.... But I thought WinPE had restrictions for incoming connections (meaning you can make any).
-
Win2000 Unattend installation from WinPE v2.0
I have both Standard and Advanced Server 2000 working on WinPE2. Post your unattended.txt file you are using. (make sure to remove any keys) Also post your command line for winnt32.exe
-
HP DL585-G2 and WinPE v2.0
Here is the devcon output on my devices for the DL380-G5 This was pulled off WinPE 1.6, but it douldn't matter where the devcon scan was run.
-
HP DL585-G2 and WinPE v2.0
Are you using the Broadcom NetXtreme II - RIS drivers? Just off the top of my head, that was the way to get Network working on my NetXtreme NIC's
-
Screen Resolution
Anyone know of a setres type app for x64 Winpe?