muevelonyc

HP Flash utility. This thing supports almost everything I throw at it. http://h18007.www1.hp.com/support/files/hp...load/20306.html

The HP utility will do that for you.

per my original post... In other words, on the PE cd, copy /i386/ntdetect.com and /i386/setupldr.bin to the root of the usb key. Then rename setupldr.bin to "ntldr" (no extension)

One last thing... I forgot to mention that WinPE CAN'T boot from USB1, it must boot from USB2, due to the issue where WinPE will actually RESET the connections on USB1 as it finds devices (thus severing it's own kernel). This is why you will get failures. I have confirmed this with Microsoft's own PE dev team. USB2 works fine though. Also when using the HP format utility set it as FAT not FAT32 nor NTFS or you WILL have issues.

SD card? This should be interesting. Just make sure its 180 mb. Anyone know if there's a utility out there that'll allow multi-booting / dual booting of WinPE and DOS on a usb key/hard drive? I know there's there's a nice one for CD called Ultimate Boot CD which lets you boot to any img file. Some guy out there made a sick CD which boots into PE, DOS, ERD Commander, BartPE all from one CD. I'm trying to do something similar but with just WinPE and DOS. I know there's the hard way to do it with a laptop (since I did it before). Essentially the "hard" way to do it is take a laptop with a floppy drive, and yank out the hard drive (yes this you have to do). Take a bootable floppy say DOS, and boot the computer up with the USB key in it (formatted). Boot to DOS on the floppy, and run fdisk on the usb key, make partition active. This is what the HP utility does, skipping this tedious step. From there, you can format c: /s to get it bootable in dos. (that was the old way to make bootable usb keys) To get the dual boot, yank the hard drive out, run winxp console recovery (winnt32.exe /cmdcons) which will set it up nicely for you. Then follow my directions to get WinPE on the usb (renaming i386 to minint and all that wonderful stuff). I guess my real question is, if there is any util or bootloader that'll allow you to boot off dos img files so that I don't have to do this tedious process? Kinda overkill to have windows dual boot on a usb key. LOL

one last thing, to get SATA/SCSI drivers in PE, just follow the guide posted somewhere here earlier, and borrow the drivers and procedure from the mass storage driver packs for a quick fix with all the sys files and the appropriate inf updates.

Well with the key I've created I've tested them successfully on these systems (due to my work environment, I'm responsible for ensuring compatibility). The keys I used was a 2Gb Lexar Jumpdrive Pro, 1Gb Viking USB2, 512mb Viking USB2 It worked on the following systems: IBM: T30, X31, T40, T41, T42, X40, M50, S50, Zpro, Mpro Dell: D400, D600, Inspiron 8000, X300, Sx270, sx 280, and a few other desktop systems This also worked on a handful of tablets that I could get, including Acer, Motion Computing, Fujitsu, Toshiba, and the Compaq/HP ones. The biggest trick is that you really have to check the BIOSes carefully. Some will allow boot order to put USB ahead of others. However, on ones such as Dell, you have to plug the USB key in PRIOR to booting cold, then go in to the bios, and the key shows up as a hard drive. Bring the key higher up on the hard drive boot up list so that it boots BEFORE the actual IDE/SCSI/SATA drive that has the actual OS, and it will boot to the key no problem. I've thrown this thing at every **** machine I could find (including my homebrew machines) and it worked fine as long as it supports USB boot. As long as it supports USB boot it'll work fine since it boots exactly as it would from a hard drive due to the ntldr which it expects on XP based installs. Hope this helps!

Saw that this thread was still open, so thought I would comment in and tell you my success. The PE source I used is the WinPE 2004 (Microsoft OEM issue which is based on WinXP SP2), which has WMI support and parts of the windows firewall built in. 1. Use the HP DriveKey util and format the usb key as FAT16 (no system files) 2. create a folder on the key called "minint" and copy the contents of i386 from your WinPE source into it. 3. in the WinPE source folder i386, copy "setupldr.bin" to the root of your usb key, rename this file to "ntldr" (no extension) 4. copy from the WinPE source folder i386 the file "ntdetect.com" to the root of your usb key. Make sure your bios supports booting from usb. Some computer's bios, especially dell or IBM, you have to plug the usb key in PRIOR to booting. Go to the bios, select the boot order, click on hard drives, and expand the folder. Under there you'll see both your hard drive, and the USB key. Make sure you give priority to the USB key over the hard drive. Save settings and reboot. This should allow you to boot up in WinPE nicely. You can also add shells like XPE or pull's BartPE's menu thingy and load all the tools from there. Just an FYI - not a good idea to use this method to flash the bios of your computer. Use a DOS based key to do that.

In the winnt.sif file in: [unattended] UnattendMode=FullUnattended OemSkipEula=Yes OemPreinstall=Yes DriverSigningPolicy = Ignore NonDriverSigningPolicy = Ignore the last 2 lines will let it happen.

Just use the RAID driver pack and it has SATA drivers all there: http://www.msfn.org/board/index.php?showtopic=14869

Have you tried using a regular WinXP volume CD (one without SP1?) I've read that it works better that way.

I just tried it using the switch I posted, and it works great! Although it's friggin 800mb, but hey at least now we have a standard source that we could use. It's over the network now, so who cares...

Sorry, last question... To keep this thing modular (I want to leave the source as is on a network share on our intranet), could we use the plain XP CD and apply SP2.exe /Q /O /N /Z in the svcpack.inf? This way there won't be a need to rebuild a slipstream source everytime a new service pack comes out in the future.

Thanks... sorry for being such a n00b. I swear in other aspects I'm not, just this whole slipstreaming thing I am. Also I saw a few threads back that using nLite caused errors with SP2? Is this ok?

ok in that case, svcpack.inf should look like this: [setupHotfixesToRun] dxsetup.exe /silent WMP9.exe Q828026.exe /Q /O /N /Z SP2.exe /Q /O /N /Z qchain.exe Q828026 is the update for Media Player 9. Also I got my SP2 from Microsoft this morning: http://www.microsoft.com/technet/prodtechn...n/winxpsp2.mspx

ok here's another problem... I just built the iso file, and SP2's mega 266MB size pushes the iso to a size of 900 mb!!! FYI - what I posted is directly off the SP2 download on Microsoft's site: http://www.microsoft.com/technet/security/news/xpsp2.mspx

ok the ones left are: Q824141 (29th September 2003) Buffer Overrun in the ListBox and in the ComboBox Control Could Allow Code Execution Q842773 (13th July 2004) Update for Background Intelligent Transfer Service (BITS) 2.0 and WinHTTP 5.1 Q870669 (2nd July 2004) Critical Update for Microsoft Data Access Components - Disable ADODB.Stream object from Internet Explorer Q828026 (10th February 2004) Update for Windows Media Player URL Script Command Behavior Download - 2.77 MB Still need to also install DirectX, Windows Media Player. My svcpack.inf portion: [setupHotfixesToRun] Q824141.exe /Q /O /N /Z Q842773.exe /Q /O /N /Z Q870669.exe /Q:A /R:N dxsetup.exe /silent WMP9.exe Q828026.exe /Q /O /N /Z SP2.exe /Q /O /N /Z qchain.exe Hotfixes.cmd: ECHO Installing .Net Framework ECHO Please wait... (takes about a minute) start /wait %systemdrive%\install\hotfixes\dotnetfx.exe /q /c:"install /q" ECHO Completed.

OK - SP2 only replaces these updates: • MS04-025 (867801) - Cumulative Security Update for Internet Explorer • MS04-024 (839645) - Vulnerability in Windows Shell Could Allow Remote Code Execution • MS04-023 (840315) - Vulnerability in HTML Help Could Allow Code Execution • MS04-022 (841873) - Vulnerability in Task Scheduler Could Allow Code Execution • MS04-018 (823353) - Cumulative Security Update for Outlook Express • MS04-016 (839643) - Vulnerability in DirectPlay Could Allow Denial of Service • MS04-015 (840374) - Vulnerability in Help and Support Center Could Allow Remote Code Execution • MS04-014 (837001) - Vulnerability in the Microsoft Jet Database Engine Could Allow Code Execution • MS04-013 (837009) - Cumulative Security Update for Outlook Express • MS04-012 (828741) - Cumulative Update for Microsoft RPC/DCOM • MS04-011 (835732) - Security Update for Microsoft Windows • MS04-007 (828028) - ASN.1 Vulnerability Could Allow Code Execution • MS04-004 (832894) - Cumulative Security Update for Internet Explorer • MS04-003 (832483) - Buffer Overrun in MDAC Function Could Allow Code Execution • MS03-049 (828749) - Buffer Overrun in the Workstation Service Could Allow Code Execution • MS03-048 (824145) - Cumulative Security Update for Internet Explorer • MS03-044 (825119) - Buffer Overrun in Windows Help and Support Center Could Lead to System Compromise • MS03-043 (828035) - Buffer Overrun in Messenger Service Could Allow Code Execution • MS03-041 (823182) - Vulnerability in Authenticode Verification Could Allow Remote Code Execution • MS03-040 (828750) - Cumulative Patch for Internet Explorer • MS03-039 (824146) - Buffer Overrun in RPCSS Service Could Allow Code Execution • MS03-034 (824105) - Flaw in NetBIOS Could Lead to Information Disclosure • MS03-032 (822925) - Cumulative Patch for Internet Explorer • MS03-030 (814078) - Flaw in Windows Script Engine Could Allow Code Execution • MS03-027 (821557) - Unchecked Buffer in Windows Shell Could Enable System Compromise • MS03-026 (823980) - Buffer Overrun in RPC Interface Could Allow Code Execution • MS03-024 (817606) - Buffer Overrun in Windows Could Lead to Data Corruption • MS03-023 (823559) - Buffer Overrun in HTML Converter Could Allow Code Execution • MS03-021 (819639) - Flaw in Windows Media Player May Allow Media Library Access • MS03-020 (818529) - Cumulative Patch for Internet Explorer • MS03-018 (811114) - Cumulative Patch for Internet Information Service • MS03-015 (813489) - Cumulative Patch for Internet Explorer • MS03-014 (330994) - Cumulative Patch for Outlook Express • MS03-013 (811493) - Buffer Overrun in Windows Kernel Message Handling Could Lead to Elevated Privileges • MS03-010 (331953) - Flaw in RPC Endpoint Mapper Could Allow Denial of Service Attacks • MS03-008 (819696) - Unchecked Buffer in DirectX Could Enable System Compromise • MS03-007 (815021) - Unchecked Buffer in Windows Component Could Cause Server Compromise • MS03-005 (810577) - Microsoft Security Bulletin MS03-005 • MS03-004 (810847) - Cumulative Patch for Internet Explorer • MS03-001 (810833) - Unchecked Buffer in Locator Service Could Lead to Code Execution • MS02-072 (329390) - Unchecked Buffer in Windows Shell Could Enable System Compromise • MS02-071 (328310) - Flaw in Windows WM_TIMER Message Handling Could Enable Privilege Elevation • MS02-070 (329170) - Flaw in SMB Signing Could Enable Group Policy to be Modified • MS02-068 (324929) - Cumulative Patch for Internet Explorer • MS02-066 (328970) - Cumulative Patch for Internet Explorer • MS02-063 (329834) - Unchecked Buffer in PPTP Implementation Could Enable Denial of Service Attacks • MS02-062 (327696) - Cumulative Patch for Internet Information Service • MS02-055 (323255) - Unchecked Buffer in Windows Help Facility Could Enable Code Execution I'm pruning my svcpack.inf and hotfix.cmd and will let you know whats leftover...

Nah, I think we should keep this here since I know some people might not want all the restrictions that SP2 has. ie: in the workplace SP2 might cause some applications to fail, and in certain instances if you have Microsoft Systems Management Servers, the SMS Client on the end users PC may crap out

now that SP2 is on MSDN, how do we put this in and which hotfixes still need to be applied?

Aahhh... that's probably the culprit. So I'll put this in the hotfixes then, right? Thanks!

You know that point where after the blue setup screen reboot, it comes to those 5 steps where it installs components and such before actually going into XP inself? At that point somewhere close to the end, (while installing components stage), it gives me a Run32 Error c:\documents Anyone have any idea where this error comes from, or had something similar in the past? Or is there a way to supress error pop up boxes completely?