Maelstorm

Member
  • Content count

    267
  • Joined

  • Last visited

Community Reputation

1 Neutral

About Maelstorm

  • Rank
    AT Field Pattern Blue

Contact Methods

  • Website URL
    http://
  1. I've been looking through the files of a WinPE 3.0 and for the life of me, I cannot seem to find where WinPE starts setup which installs Windows. Now I know about cmdlines.txt, winpeshl.ini, and the registry key HKLM\System\Setup that runs winpeshl.exe. So, from boot.wim, how does windows setup get started?
  2. I can build Windows XP All In One install DVDs in my sleep. Well, my script builds it. I have been looking through the forums, online, and the deployment documentation from Microsoft, but I am still confused about how this works. Here's what I have been able to gather so far: Instead of an i386 directory, there's a install.wim file that contains the installation image. Instead of winnt.sif, the unattended answer file is now an xml file. There is the Windows System Image Manager which shows a bunch of components and packages which I have no clue about. Windows PE? In WIn XP, Win PE was made from the Win XP installation files. How is it done now? The image that I have is Win 7 Pro SP1 AMD64. I don't plan to do any upgrading to ultimate or anything. In Win XP, there are several hooks which can be utilized by custom code to perform various tasks. Do these hooks exist in Win 7? How does one use them? Hotfixes. Before, you could specify a command line switch for a hotfix and it would integrate itself in the windows install. Does that method still apply or has the procedure changed? Related to #6: How does one now install additional software like flash player, acrobat reader, Seamonkey, Firefox, etc...? Which hook do you use? Before, I would start a very elaborate installation from cmdlines.txt which would in turn call my WINSETUP.CMD which would then kick off the software installation.I will probably have more questions beyond this. But this should get me started.
  3. Is there a command line disk wipe utility that works on WinPE? I'm running WinPE 1.6. I tried HDDERASE.exe and it won't even load.
  4. I have an update. It turns out that dd does not work under WinPE 1.5/1.6. So, I tried one of the other tools mentioned, specifically mkbt. It seems the following command line works quite well: mkbt -x -v -c Z: C:\BOOTREC.DAT So I've integrated it into my boot disk. This is all strictly testing right now. I am currently writing a HTA menu system that will run under WinPE to control everything based on what the user selects. As for testing, the following is the batch files that I am using to do this with under VMWare 5.5: MakeDisk.cmd @ECHO OFF START /WAIT CMD.EXE /C "\Program Files\Misc\PrepDisk.cmd" START /WAIT CMD.EXE /C "\Program Files\Misc\Install.cmd" vol1u START /WAIT CMD.EXE /C "\Program Files\Misc\Recover.cmd" EXIT PrepDisk.cmd @ECHO OFF diskpart /s "\Program Files\Misc\DiskPart.ini" ECHO. format c: /q /y /fs:ntfs /v:System format z: /q /y /fs:ntfs /v:Recovery Install.cmd @ECHO OFF REM Setup SET PARAM=%1 SET TARGET=C: REM Parameter Check IF /I "%1"=="MCE1U" ( SET SOURCE=MCE SET CONFIG=mce1u.txt GOTO :PROGRAM ) IF /I "%1"=="MCE1A" ( SET SOURCE=MCE SET CONFIG=mce1a.txt GOTO :PROGRAM ) IF /I "%1"=="MCE2U" ( SET SOURCE=MCE SET CONFIG=mce2u.txt GOTO :PROGRAM ) IF /I "%1"=="MCE2A" ( SET SOURCE=MCE SET CONFIG=mce2a.txt GOTO :PROGRAM ) IF /I "%1"=="RTM1U" ( SET SOURCE=RTM SET CONFIG=rtm1u.txt GOTO :PROGRAM ) IF /I "%1"=="RMT1A" ( SET SOURCE=RTM SET CONFIG=rtm1a.txt GOTO :PROGRAM ) IF /I "%1"=="RTM2U" ( SET SOURCE=RTM SET CONFIG=rtm2u.txt GOTO :PROGRAM ) IF /I "%1"=="RTM2A" ( SET SOURCE=RTM SET CONFIG=rtm2a.txt GOTO :PROGRAM ) IF /I "%1"=="OEM1U" ( SET SOURCE=OEM SET CONFIG=oem1u.txt GOTO :PROGRAM ) IF /I "%1"=="OEM1A" ( SET SOURCE=OEM SET CONFIG=oem1a.txt GOTO :PROGRAM ) IF /I "%1"=="VOL1U" ( SET SOURCE=VOL SET CONFIG=vol1u.txt GOTO :PROGRAM ) IF /I "%1"=="VOL1A" ( SET SOURCE=VOL SET CONFIG=vol1a.txt GOTO :PROGRAM ) IF /I "%1"=="TESTU" ( SET SOURCE=VOL SET CONFIG=MasterUnattended.txt GOTO :PROGRAM ) IF /I "%1"=="TESTA" ( SET SOURCE=VOL SET CONFIG=MasterAttended.txt GOTO :PROGRAM ) GOTO :ERROR :PROGRAM REM Final Setup SET SOURCEFILES=X:\WINXP\%SOURCE%\I386 SET CONFIGFILES=x:\WINXP\CONFIG\%CONFIG% CHDIR %SOURCEFILES% IF /I "%SOURCE%"=="MCE" ( WinNT32 /syspart:%TARGET% /s:%SOURCEFILES% /unattended:%CONFIGFILES% /makelocalsource:all /copysource:lang /dudisable ) ELSE ( WinNT32 /syspart:%TARGET% /s:%SOURCEFILES% /unattended:%CONFIGFILES% /makelocalsource /copysource:lang /dudisable ) ECHO. XCOPY %SystemDrive%\WINXP\OEMFILES C:\$WIN_NT$.~LS\$OEM$ /S /E /Q /Y GOTO :EXIT :ERROR ECHO. ECHO Code Ed IM Key ECHO ============================================ ECHO MCE1U Media UA ECHO MCE1A Media A ECHO MCE2U Media UA ECHO MCE2A Media A ECHO OEM1U OEM UA ECHO OEM1A OEM A ECHO RTMU1U Retail UA ECHO RTMU1A Retail A ECHO RTMU2U Retail UA ECHO RTMU2A Retail A ECHO VOL1U Volume UA ECHO VOL1A Volume A ECHO TESTU Volume UA ECHO TESTA Volume A ECHO. GOTO :EOF :EXIT GOTO :EOF Recover.cmd @ECHO OFF REM install recovery partition ECHO Build Directories MKDIR "Z:\MININT" MKDIR "Z:\Program Files" ECHO Copy Data XCOPY /S /E /Q /Y "X:\I386" "Z:\MININT" XCOPY /S /E /Q /Y "X:\Program Files" "Z:\Program Files" COPY "Z:\MININT\ntdetect.com" "Z:\" COPY "Z:\MININT\setupldr.bin" "Z:\ntldr" ECHO Install Boot ECHO. MKBT -x -v -c Z: C:\BOOTREC.DAT DiskPart.ini select disk 0 clean create partition primary size=40960 select partition 1 active assign letter=C: select disk 0 create partition primary select partition 2 assign letter=Z:
  5. My brain went for a walk on that post. Heh, this entire thread actually. I think dd would be the best tool to use in this case since that is the tool that I am most familiar with. I'll play around with it and see if I can get an automated setup working. Thank you so very much for the help.
  6. Ok, I think we have a misunderstanding of what I am asking for. I did get this to work, manually, but I need a automatic method to do this. I'm not asking for the Master Boot Record, but the *VOLUME* Boot Record. The MBR that we all know and love is at CHS 0, 0, 1. This everybody knows about, and all the tools and suggestions given deal with that, except mkbt which gives an error about it only works with floppies. What I'm asking for is the boot sector *INSIDE* the partition that is pointed to by the MBR. That's what BOOTSECT.DAT is when you install the Recovery Console. The volume boot record for the first partition is at LBA sector 64 for Windows XP installations (At least all the ones that I have seen), which is the start of the first parition of the drive. The boot code that loads ntldr on NTFS volumes starts there and spans 16 disk sectors for 8Kb of data. It is referenced as $Boot in the MFT, but there's no way that I'm aware of to get at it.
  7. Those tools are nice, but not what I am looking for. I need a tool that will read the MBR, then write the specified volume boot record to a file. Just like WINNT32.exe does when you install the Recovery Console. It makes a file called BOOTSECT.DAT in the cmdcons directory of the boot partition. I'm looking at writing my own, but I would rather not as I know absolutely nothing about C/C++ programming under Windows. -EDIT- I did find a tool called Findpart http://www.partitionsupport.com/utilities.htm that does what I want, but it's a 2 step process to make this work. The problem is getting the start CHS data out of the list and into the command line for the getsect command.
  8. Ah, so that's what the problem is. Can you recommend a command-line sector extractor so I can extract the boot sector of the partition? I don't have any tools to do that for hard disks. I've searched all over google, and I did find a couple of tools that would seem to work, but they do not. Something like mkbt.exe from BartPE would be just the ticket that I am looking for.
  9. How do you boot Windows PE 1.x (I'm using 1.6) from a second primary partition or harddisk using boot.ini? I've tried several things, but have yet to get it working correctly. Note that this isn't a dual-boot of WinPE in the same partition as WinXP, but it's in a different partition/drive. Here's the layout: Harddrive 0: Part 1: ~475GB Primary/Active - Windows XP Part 2: ~20GB Primary - Windows PE Here's what I have tried: In boot.ini, copy the WinXP line and modify it to point to D:\i386 :--: Failed Installed cmdcons, copied bootsect.dat to D: and point to that in boot.ini :--: Failed Point to D:\i386\setupldr in boot.ini :--: Failed Point to D:\i386\ntldr in boot.ini :--: Failed Copy ntldr to d:\ and point to that :--: Failed I'm out of ideas. Do you guys have any? I'm getting desperate to get this to work as this is the final hurdle that I need to cross.
  10. Any word from Redmond about a OEM Preinstallation Kit for Windows 7? Or is it even needed anymore?
  11. Actually, Microsoft learned their lesson with the Vista driver fiasco. Windows 7 will use the same exact drivers that Windows XP uses...From what I am told.
  12. Unpack deploy.cab on your Windows CD. It's in \Support\Tools. Once you have the file unpacked, look at ref.chm. It has most if not all options as well as other information and tools.
  13. Add/Change the following lines to your unattended setup: [unattended] UnattendMode=FullUnattended UnattendSwitch=Yes TargetPath="\Windows" Repartition=Yes WaitForReboot=No OemSkipEula=Yes OemPreinstall=Yes
  14. I found a solution. It seems that when you use the /makelocalsource option, it will not copy the files in X:\$OEM$, so when you reboot the machine and run it off the HD, the files are not there. I tried copying the $OEM$ files to the root of the HD, and that didn't work either. I discovered though, that in the root directory, there's a couple of very interesting directories: $WIN_NT$.~BT $WIN_NT$.~LS Both directories have an $OEM$ sub directory. I tried BT first and that did not work. Not suprizing since that directory looks like a primordial \Windows directory. In the LS directory, it had two sub directories: The afore mentioned $OEM$ and I386. Looking at I386, it's the same as you would find on a Windows CD. I copied the $OEM$ files to the LS directory and the text mode installer saw the files and copied them correctly. Now everything seems to work just fine. I used the same unattneded.txt file that I was using when booting straight into the windows installer. The command that I used: XCOPY X:\$OEM$ C:\$WIN_NT$.~LS\$OEM$ /S /E /Q /Y You can if you want, but this issue came up because I was installing from WinPE. PrepDisk.cmd @ECHO OFF diskpart /s "\Program Files\Misc\DiskPart.ini" ECHO. format c: /q /y /fs:ntfs /v:System Install.cmd @ECHO OFF cd \WinXP\i386 WinNT32 /syspart:C: /s:X:\WinXP\i386 /unattended:X:\unattended.txt /makelocalsource /dudisable DiskPart.ini select disk 0 clean create partition primary select partition 1 active assign letter=C:
  15. When I start a Windows XP Pro SP3 install from WinPE 1.6, the %OEM% folders do not get copied. Do I have to copy this manually?