Jump to content

varun037

Member
  • Posts

    9
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    India

About varun037

varun037's Achievements

0

Reputation

  1. I am currently using windows xp to do all the stuff. I just copied bcdedit file from vista->system32 to xp->system32 folder. I have tested this is the actual environment and works flawlessly for me. Its just fine. I dont know about Windows 7. Its still in beta stage. Have read somewhere in this forum only that the bcdedit is still in development stage. Some changes are being made to it and vista file is better than vista sp1. Might be I will suggest you to use bcdedit file from vista installation. U may use imagex or winmount to mount the wim image to extract the file. Thanks for the suggestion but I was able to solve the problem of optimization only by using same version of ntdll.dll file in windows installations and windows xp live. Otherwise it always gave me an hard error. I dont know y during optimization to files of different versions and different sizes shall get mixed up. I had to rebuid the pe from xp sp3 pack.
  2. Hi.. I am getting an odd error STOP: C0000221 Unknown Hard Error \SystemRoot\System32\ntdll.dll I have noticed one issue - I get this error only when i use option to optimize the dvd. My original dvd is 4.97 gbs and optimized size is 4.31 gbs. I have used poweriso, ultroiso and easyboot. If i dont use optimization i dont get this error. I am trying to make a multiboot dvd which included WinXPE (SP2) WinXP Professional Edition (SP3) Win2000 Professional
  3. and regarding the one pe that doesnot work check the other files that are included in the pe dvd. It may have some seperate drivers like norton ghost has. That folder is also to be copied onto the combined dvd...
  4. I dont know what the problem could be... may be try not to use optimization while burning the dvd. I am also getting some problem with dvd optimization currently...
  5. Here it is Rem BCD (boot configuration data) editor for multiple vista pe REM THIS IS THE ORIGINAL BCD FILE EXTRACTED FROM ANY VISTA WINPE / VISTA DVD (I USED VISTA INSTALLATION) set BCD-File="c:\bcd 1\BCD" REM SET THE NAME FOR THE VISTA PE HERE set pename="Your PE Name" REM SET THE NAME FOR THE WIM.FILE HERE WITH PATH set filena=[boot]\sources\yourwimfile.wim for /f "eol=r tokens=1-2" %%a in ('bcdedit /store %BCD-File% /ENUM all') do set rdo=%%b for /f "tokens=1-7" %%a in ('Bcdedit /store %BCD-File% /copy {default} /d %pename%') do set guid1=%%g bcdedit /store %BCD-File% /set %guid1:~0,38% DEVICE ramdisk=%filena%,%rdo% bcdedit /store %BCD-File% /set %guid1:~0,38% OSDEVICE ramdisk=%filena%,%rdo% bcdedit /store %BCD-File% /ENUM Run it as many times as you like to add multiple pes after changing the variables - bcd-file, pename, filena remember not to use any spaces in filena variable Rest all is auto
  6. complete procedure... use the default WinVista or any WinPE dvd. copy the contents to the HDD the structure would be dvd1 | - Project Root | - BOOT (CONTAINS THE BCD FILE TO BE EDITED) | - EFI | - SOURCES (CONTAINS THE PE .WIM FILES) | - EZBOOT | - OTHER FILES In the boot folder we need to run the command bcdedit /store bcd /ENUM This will give you the details of old entry in the boot loader. u need to note the guid. in my case this is {7619dcc8-fafe-11d9-b411-000476eba25f} bcdedit /store bcd /enum Windows Boot Manager -------------------- identifier {bootmgr} description Windows Boot Manager locale en-US inherit {globalsettings} default {default} displayorder {default} toolsdisplayorder {memdiag} timeout 30 Windows Boot Loader ------------------- identifier {default} device ramdisk=[boot]\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f} path \windows\system32\boot\winload.exe description Windows Setup locale en-US inherit {bootloadersettings} osdevice ramdisk=[boot]\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f} systemroot \windows detecthal Yes winpe Yes ems Yes bcdedit /store bcd /copy {default} /d "Active Boot Disk" operation completed successfully. {613fe2f0-2356-11de-bf6a-001e4cdc40b1} therefore my new guid is {613fe2f0-2356-11de-bf6a-001e4cdc40b1} now bcdedit /store bcd /set {613fe2f0-2356-11de-bf6a-001e4cdc40b1} DEVICE ramdisk=[boot]\sources\boot32.wim,{7619dcc8-fafe-11d9-b411-000476eba25f} operation completed successfully. bcdedit /store bcd /set {613fe2f0-2356-11de-bf6a-001e4cdc40b1} OSDEVICE ramdisk=[boot]\sources\boot32.wim,{7619dcc8-fafe-11d9-b411-000476eba25f} operation completed successfully. bcdedit /store bcd /ENUM Windows Boot Manager -------------------- identifier {bootmgr} description Windows Boot Manager locale en-US inherit {globalsettings} default {default} displayorder {default} {613fe2f0-2356-11de-bf6a-001e4cdc40b1} toolsdisplayorder {memdiag} timeout 30 Windows Boot Loader ------------------- identifier {default} device ramdisk=[boot]\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f} path \windows\system32\boot\winload.exe description Windows Setup locale en-US inherit {bootloadersettings} osdevice ramdisk=[boot]\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f} systemroot \windows detecthal Yes winpe Yes ems Yes Windows Boot Loader ------------------- identifier {613fe2f0-2356-11de-bf6a-001e4cdc40b1} device ramdisk=[boot]\sources\boot32.wim,{7619dcc8-fafe-11d9-b411-000476eba25f} path \windows\system32\boot\winload.exe description Active Boot Disk locale en-US inherit {bootloadersettings} osdevice ramdisk=[boot]\sources\boot32.wim,{7619dcc8-fafe-11d9-b411-000476eba25f} systemroot \windows detecthal Yes winpe Yes ems Yes like this you may add n number of vista pes... (i have tested 3 PEs + Windows Vista Setup) to the BCD Store. Just you have to keep the oldguid to same as {7619dcc8-fafe-11d9-b411-000476eba25f} {7619dcc8-fafe-11d9-b411-000476eba25f} will never change... thats the rule. copy the boot.wim file in sources folder of active boot disk/ ghost pe/ erdcommander 6.0 to the sources folder in disk1 in the project. and rename it to desired. i renamed it to boot32.wim you may use any... {default} is not a variable and need not be changed. I have not tested this method to change the folder as this can be done in the command by specifying a folder other than sources. So not sure to that. But the Vista PEs i have handled had only 1 file in the sources folder which i renamed this way. So if you have multiple files in sources folder for a pe you may try changing the folder and do tell me if it works.... I have attached a BCD File with following options Windows Setup [EMS Enabled] - Loads boot.wim Active Boot Disk [EMS Enabled] - Loads babd.wim Norton Ghost 14.0 PE [EMS Enabled] - Loads ghostpe.wim ERD Commander 6.0 [EMS Enabled] - Loads erd60.wim Bcd Download
  7. Its explained with an example on this site... http://www.ezbsystems.com/cgi-bin/ikonboar...t=ST;f=1;t=2727
×
×
  • Create New...