dicko1976 Posted June 15, 2010 Posted June 15, 2010 but I have had no look in adding the wireless driver for the 5100 AGN. I have added the folder with the windows 7 drivers in to the folder Make_PE3\PE3_mod\WIN7_drivers\x86 as it says in the text file documentation but it still does not work.Were the wireless drivers processed by Dism during build ?After booting with pe3_x86.iso you can use Driver Fix from desktop to install the drivers and start WLAN Service.Check in Device Manager if your Network card is installed.See if your netdriver.inf is located in X:\Windows\inf folder.Start PENetwork is neede for Connect and Authentication.Program AddOnns are preferred to be portable and go in PStart menu.Sorry for the delay in reply but I fixed this by putting it in a folder Make_PE3\PE3_mod\WIN7_drivers\x86\W\ and then made another folder called IW and dropped the driver files in there. When I packaged it all together it worked fine and installed the drivers on boot.I was trying to put the drivers folder in the x86 folder where the text file said you could.....but it never worked until I moved it down a tierThanks againPS is there any more additions in the pipeline for the future ?
trizet Posted June 18, 2010 Posted June 18, 2010 hi wimbthe pop-ups issue for card readers still occur, even with pe from WAIK build using your make_pe3. i change the way startnet.cmd looking for pstart.exe, wallpaper and asuite/start.exe. (search all the files from z-c then stop if files are found, instead of original startnet looking for each files in every drives even if files already found). at least it will minimize the pop-ups occurence for the missing files only.on my pc, card reader drives always get drive letter before usb flash disk letter, so i don't get any pop-ups anymore.and for audio support, finally i got it working i made some changes to get audio working.- add file dsound.dll (required for foobar. vlc and winamp did not work even on running windows 7)- your audio_fix.cmd is good but add reg value did not work for my sound device. (error device not found). i add reg value for my dev id now it is works. but again on different hardware i need different reg value to get it working.is it need different value on different dev id?i almost finish my batch command, will post it when ready.
wimb Posted June 18, 2010 Author Posted June 18, 2010 (edited) Hi trizet,I will add dsound.dll to the list of required files.For me not necessary, but may be depends on hardware.Probably we need to add also more versions of audio_fix code for different sound devices.Thanks to your approach of using winre.wim as source, now Make_PE3.cmd is working without AIK and with XP or Windows 7 as OS.Also the WLAN Hotfix is no longer needed. So you only need a 32-bits Windows 7 Source.Need to apply the required changes in the AutoIt3 version and then it is ready ....No problems anymore with empty cardreader drive pop-ups by using correct sequence in startnet.cmd Edited June 18, 2010 by wimb
wimb Posted June 24, 2010 Author Posted June 24, 2010 (edited) *** Update of Make_PE3 package to Create Portable Windows 7 PE ***Added option to make Portable Windows 7 PE without using AIKCreate 7pe_x86.iso from Winre.wim in Recovery folder by using Dism.exe of Windows 7 Source DriveThis approach was earlier found by trizet to be successfulWLAN HotFix No longer needed by adding dot3svc Service to registry and extending filelist of needed Windows 7 filesThanks to trizet for optimizing PE3-SOFTWARE_CLID.reg and for making restricted_clsid.regRequired as Source - 32-bits Installed Windows 7 Drive32-bits Windows 7 Setup DVD can be used as well as Source, but requires to auto-collect AIK_Tools, by Running once Make_PE3 in Windows 7 OS or environment with Installed Windows 7 AIKMake_PE3.exe and Make_PE3.cmd can be used in XP or Windows 7 as OSNot Required anymore - AIK for Windows 7 - KB3AIK_EN.iso - Microsoft - Windows PE 3.0http://www.microsoft.com/downloads/details.aspx?familyid=696DD665-9F76-4177-A811-39C26D3B3B34&displaylang=enDism.exe of AIK must be version 6.1.7600.16385 (earlier version 7000 gives Errors)Guide with More Info:http://www.911cd.net/forums//index.php?showtopic=21883&st=35http://www.msfn.org/board/make-program-create-portable-windows-t143529.html=User Interface of Make_PE3.cmd Batch Program to Create 7pe_x86.iso Boot Image===User Interface of Make_PE3.exe Program to Create 7pe_x86.iso Boot Image== Edited September 25, 2010 by wimb
Kullenen_Ask Posted June 24, 2010 Posted June 24, 2010 (edited) Can be a "Select Windows 7 install.wim - and without waik Makepe3-iso"button? when the install.wim selected it can mount readonly(for source dvd) to a temporary location and copy files from there and unmount after build. also need a wim number selection from 1-4 or more. If we mount install.wim and select option one will not it work? because of we don't have a Winre.wim in Recovery folder in xp system? it was working before i was building like that. mounting the wim to a temporary folder manually and selecting option one. that time it was using boot.wim of waik. i think you understand what i mean. to copy boot.wim from dvd and a button as i suggested can be good. or directy selecting "DVDDrive:\setup" folder and it copy boot.wim from that location and mount the selected wim number image from that folder install.wim building without aiklooks you worked on it too much good work. more freedom. less dependencies. Edited June 24, 2010 by Kullenen_Ask
wimb Posted June 24, 2010 Author Posted June 24, 2010 (edited) Hi Kullenen_AskYou are still allowed to select as Source a folder or drive containing sources\install.wim of 7 Setup DVD(with option 2 and in case of Setup DVD then sources\boot.wim is used + Win7 files of install.wim)or a folder with mounted install.wim and then containing Windows folder (use then option 4 which requires AIK and winpe.wim is used + Windows 7 files)In that respect nothing has changed .... Have a try. Edited June 24, 2010 by wimb
Kullenen_Ask Posted June 24, 2010 Posted June 24, 2010 (edited) if i do as i do before will not it want a Winre.wim? where will it take winre.wim or boot.wim? ok i checked cmd inside. it looks everything you thought and there are options it to find. soory i commented before test. i will test now. and comment after.when the install.wim selected it can mount readonly(for source dvd) to a temporary location and copy files from there and unmount after build (need mount manually yet i dont have problem mounting manually not so important for me but maybe for novice users.)it said winre.wim not found as i expected. (tested)mounted install wim to a folder and selected option one Edited June 24, 2010 by Kullenen_Ask
wimb Posted June 24, 2010 Author Posted June 24, 2010 if i do as i do before will not it want a Winre.wim? where will it take winre.wim or boot.wim?winre.wim (index 1) is available in Recovery folder of Installed Windows 7boot.wim (index 2) is used when 7 Setup DVD drive or folder is used as SourceI think boot.wim(index2) = winre.wim(index 1)
Kullenen_Ask Posted June 24, 2010 Posted June 24, 2010 (edited) if i do as i do before will not it want a Winre.wim? where will it take winre.wim or boot.wim?winre.wim (index 1) is available in Recovery folder of Installed Windows 7boot.wim (index 2) is used when 7 Setup DVD drive or folder is used as SourceI think boot.wim(index2) = winre.wim(index 1)boot.wim(index2) NOT EQUAL winre.wim(index 1)boot.wim(index1) EQUAL winre.wim(index 1)boot.wim(index1) NO BOOT FLAGwinre.wim(index 1) HAS BOOT FLAGwinre.wim has only one index in it. boot.wim has two. i compared the indexes previous posts with integrated packages. post #106 in this topicwhen it complained it can not find winre.wim in C:\Make_PE3\win7pe_x86\Winre.wim i manually exported boot.wim 1 as winre.wim to that folder with boot flag. i think it should build now. all can be fixed with a few codes after you successfully coded so many things. should be easy.(with option 2 and in case of Setup DVD then sources\boot.wim is used + Win7 files of install.wim)but option 2 says it needs aik??? i dont want to use aik (i talk about gui options)in my test it says it couldn't find bootmgr (doesnt copy bootmgr? maybe because localized version setup?) Edited June 24, 2010 by Kullenen_Ask
trizet Posted June 24, 2010 Posted June 24, 2010 (edited) hi Wimb, i just post My_7PE.cmd here : http://www.boot-land.net/forums/index.php?showtopic=11801perhaps you want to take a look what has been changes since the preview. (i add some more registry tweaks)i use dism to detect image number, international settings and distribution language.@Kullenen_Askon my experiment boot.wim(index2) EQUAL winre.wim(index 1) > only different shellboot.wim(index1) NOT EQUAL winre.wim(index 1)boot.wim(index1) NO BOOT FLAGboot.wim(index2) HAS BOOT FLAGwinre.wim(index 1) HAS BOOT FLAGit has been tested on Ultimate/en-US language, i don't know if boot flag/image index will different with others distribution. Edited June 24, 2010 by trizet
Kullenen_Ask Posted June 24, 2010 Posted June 24, 2010 (edited) With default settings, My_7PE will look for Winre file on Recovery folder then it will look for bootmgr files from local computer. If you have bootmgr in System Reserved partition, it will temporary assign drive letter to copy necessary files. Optionally you can use Winre/bootmgr files from system repair cd or Windows installation DVD. from your read me explains why there is no bootmgr in my build. Edited June 24, 2010 by Kullenen_Ask
trizet Posted June 24, 2010 Posted June 24, 2010 (edited) here is packages listing, winre packages=boot.wim image 2 packages.you did not post your winre packages, only boot.wim image 1 and 2.different shell could be same packages/files/registry, winre start recovery shell, winsetup (boot.wim) start setup.exe. but you can start recovery from command winsetup, and the other hand you can start setup.exe in winre.(btw i use windows PE from winre image to install windows 7)Deployment Image Servicing and Management toolVersion: 6.1.7600.16385Image Version: 6.1.7600.16385Packages listing:-------------------------------------------------------------------------------------- | --------------- | ------------- | -----------------Package Identity | State | Release Type | Install Time -------------------------------------------------------------------------------------- | --------------- | ------------- | -----------------Microsoft-Windows-WinPE-LanguagePack-Package~31bf3856ad364e35~x86~en-US~6.1.7600.16385 | Install Pending | Language Pack | 7/14/2009 2:40 AMMicrosoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~6.1.7600.16385 | Install Pending | Foundation | 7/14/2009 2:38 AMWinPE-Scripting-Package~31bf3856ad364e35~x86~en-US~6.1.7600.16385 | Install Pending | Language Pack | 7/14/2009 2:52 AMWinPE-Scripting-Package~31bf3856ad364e35~x86~~6.1.7600.16385 | Install Pending | Feature Pack | 7/14/2009 2:52 AMWinPE-Setup-Client-Package~31bf3856ad364e35~x86~en-US~6.1.7600.16385 | Install Pending | Language Pack | 7/14/2009 3:05 AMWinPE-Setup-Client-Package~31bf3856ad364e35~x86~~6.1.7600.16385 | Install Pending | Feature Pack | 7/14/2009 3:05 AMWinPE-Setup-Package~31bf3856ad364e35~x86~en-US~6.1.7600.16385 | Install Pending | Language Pack | 7/14/2009 3:05 AMWinPE-Setup-Package~31bf3856ad364e35~x86~~6.1.7600.16385 | Install Pending | Feature Pack | 7/14/2009 3:04 AMWinPE-SRT-Package~31bf3856ad364e35~x86~en-US~6.1.7600.16385 | Install Pending | Language Pack | 7/14/2009 2:52 AMWinPE-SRT-Package~31bf3856ad364e35~x86~~6.1.7600.16385 | Install Pending | Feature Pack | 7/14/2009 2:51 AMWinPE-WDS-Tools-Package~31bf3856ad364e35~x86~en-US~6.1.7600.16385 | Install Pending | Language Pack | 7/14/2009 2:52 AMWinPE-WDS-Tools-Package~31bf3856ad364e35~x86~~6.1.7600.16385 | Install Pending | Feature Pack | 7/14/2009 2:52 AMWinPE-WMI-Package~31bf3856ad364e35~x86~en-US~6.1.7600.16385 | Install Pending | Language Pack | 7/14/2009 2:53 AMWinPE-WMI-Package~31bf3856ad364e35~x86~~6.1.7600.16385 | Install Pending | Feature Pack | 7/14/2009 2:52 AMThe operation completed successfully.boot.wim image 2Deployment Image Servicing and Management toolVersion: 6.1.7600.16385Image Version: 6.1.7600.16385Packages listing:-------------------------------------------------------------------------------------- | --------------- | ------------- | -----------------Package Identity | State | Release Type | Install Time -------------------------------------------------------------------------------------- | --------------- | ------------- | -----------------Microsoft-Windows-WinPE-LanguagePack-Package~31bf3856ad364e35~x86~en-US~6.1.7600.16385 | Install Pending | Language Pack | 7/14/2009 2:40 AMMicrosoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~6.1.7600.16385 | Install Pending | Foundation | 7/14/2009 2:38 AMWinPE-Scripting-Package~31bf3856ad364e35~x86~en-US~6.1.7600.16385 | Install Pending | Language Pack | 7/14/2009 2:52 AMWinPE-Scripting-Package~31bf3856ad364e35~x86~~6.1.7600.16385 | Install Pending | Feature Pack | 7/14/2009 2:52 AMWinPE-Setup-Client-Package~31bf3856ad364e35~x86~en-US~6.1.7600.16385 | Install Pending | Language Pack | 7/14/2009 3:05 AMWinPE-Setup-Client-Package~31bf3856ad364e35~x86~~6.1.7600.16385 | Install Pending | Feature Pack | 7/14/2009 3:05 AMWinPE-Setup-Package~31bf3856ad364e35~x86~en-US~6.1.7600.16385 | Install Pending | Language Pack | 7/14/2009 3:05 AMWinPE-Setup-Package~31bf3856ad364e35~x86~~6.1.7600.16385 | Install Pending | Feature Pack | 7/14/2009 3:04 AMWinPE-SRT-Package~31bf3856ad364e35~x86~en-US~6.1.7600.16385 | Install Pending | Language Pack | 7/14/2009 2:52 AMWinPE-SRT-Package~31bf3856ad364e35~x86~~6.1.7600.16385 | Install Pending | Feature Pack | 7/14/2009 2:51 AMWinPE-WDS-Tools-Package~31bf3856ad364e35~x86~en-US~6.1.7600.16385 | Install Pending | Language Pack | 7/14/2009 2:52 AMWinPE-WDS-Tools-Package~31bf3856ad364e35~x86~~6.1.7600.16385 | Install Pending | Feature Pack | 7/14/2009 2:52 AMWinPE-WMI-Package~31bf3856ad364e35~x86~en-US~6.1.7600.16385 | Install Pending | Language Pack | 7/14/2009 2:53 AMWinPE-WMI-Package~31bf3856ad364e35~x86~~6.1.7600.16385 | Install Pending | Feature Pack | 7/14/2009 2:52 AMThe operation completed successfully.boot.wim image 1Deployment Image Servicing and Management toolVersion: 6.1.7600.16385Image Version: 6.1.7600.16385Packages listing:-------------------------------------------------------------------------------------- | --------------- | ------------- | -----------------Package Identity | State | Release Type | Install Time -------------------------------------------------------------------------------------- | --------------- | ------------- | -----------------Microsoft-Windows-WinPE-LanguagePack-Package~31bf3856ad364e35~x86~en-US~6.1.7600.16385 | Install Pending | Language Pack | 7/14/2009 2:40 AMMicrosoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~6.1.7600.16385 | Install Pending | Foundation | 7/14/2009 2:38 AMWinPE-Scripting-Package~31bf3856ad364e35~x86~en-US~6.1.7600.16385 | Install Pending | Language Pack | 7/14/2009 2:52 AMWinPE-Scripting-Package~31bf3856ad364e35~x86~~6.1.7600.16385 | Install Pending | Feature Pack | 7/14/2009 2:52 AMWinPE-SRT-Package~31bf3856ad364e35~x86~en-US~6.1.7600.16385 | Install Pending | Language Pack | 7/14/2009 2:52 AMWinPE-SRT-Package~31bf3856ad364e35~x86~~6.1.7600.16385 | Install Pending | Feature Pack | 7/14/2009 2:51 AMWinPE-WDS-Tools-Package~31bf3856ad364e35~x86~en-US~6.1.7600.16385 | Install Pending | Language Pack | 7/14/2009 2:52 AMWinPE-WDS-Tools-Package~31bf3856ad364e35~x86~~6.1.7600.16385 | Install Pending | Feature Pack | 7/14/2009 2:52 AMWinPE-WMI-Package~31bf3856ad364e35~x86~en-US~6.1.7600.16385 | Install Pending | Language Pack | 7/14/2009 2:53 AMWinPE-WMI-Package~31bf3856ad364e35~x86~~6.1.7600.16385 | Install Pending | Feature Pack | 7/14/2009 2:52 AMThe operation completed successfully. Edited June 24, 2010 by trizet
Kullenen_Ask Posted June 24, 2010 Posted June 24, 2010 (edited) do you use oem custom build notebook? they modify windows setup files. i don't know what to say. is it a clean install from a retail dvd? then i am false. sorry.my operating system is xp. i investigated that long time before and i remember like that. didnt test short time before. it is stupid to have setup packages in winre that you can not install windows from system boot hidden partition. why the boot.wim 1 is for then? it should be copied to system boot partition at install as a winre.you install windows 7 from its own dvd from inside winpe. not from the setup packages integrated in winre.???not from x:\windows\setup.exe or x:\sources\setup.exe should be from dvddrive\setup.exewhen you boot in winre. open cmd prompt. write "setup.exe" and installed windows? where will it search for install.wim. probably in x:\sources\install.wim that doesnt exist in 1gb partition.if we think the windows setup exports wims at install. why it should exports boot.wim 2 modify files and change shell from setup to recovery inside wim (mount,change shell,dismount,export) if it can only export boot.wim 1 without changing shell as recovery(export and bootflag)? Edited June 24, 2010 by Kullenen_Ask
trizet Posted June 24, 2010 Posted June 24, 2010 (edited) i use windows 7 RTM DVD. there are 4 setup.exe in dvd1. dvddrive\setup.exe this one can be execute from windows to upgrade2. dvddrive\sources\setup.exe this one can be execute from windows to upgrade3. mounted PE x:\setup.exe this one as a normal install execute from PE (i use this one same as from boot.wim)4. mounted PE x:\sources\setup.exe this one has larger file size, i don't know what this file for. but i can use this file as installer as well.i mean use winre to install is to executes installer, same as what boot.wim does. and i have all the required files (include install.wim) in usb.yes i have the same questions with you. why there are 2 images in boot.wim, and i have read similar question in others forum but i still can not get clear answer. Edited June 24, 2010 by trizet
trizet Posted June 24, 2010 Posted June 24, 2010 @Kullenen_Askwhen you said it doesn't copy file "bootmgr" do you mean you build using Wimb's Make_PE3 or using My_7PE.cmd?because you replying to wimb's post but quoting my readme file, it is confusing me @wimbi tested your latest build, like Kullenen_Ask said it does not copy bootmgr from "system reserved". looks like your Make_PE3 needs to temporary assign drive letter for System Reserved. we can temporary assign drive letter using diskpart /s, either manually or automatically with get volume name first.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now