click-click

Well, that looks like the solution to install the drivers, but I can't get the Archiive Tab to appear in the Paragon SW. This is where a mount/unmount can be selected for a given backup. I thought this condition was because the drivers were not being installed, but I guess I'm still missing something. I have not gotten anyone to confirm if they have this working in a Win7PE.

Hi JFX, Glad to see you here. Yes there was a uim_x86 .exe too besides the inf and sys files, but that did not end up in the Driverstore. It's still in the UIM directory of the Application though. Do I just run that after Win7PE is booted?

I see you are trying to convince me to use a vhd. I need to boot from CD (not DVD) so I need to keep the size at a minimum. I just don't understand why nothing is copied to system32 when the inf is processed. If the driver is not installable, then I'd be interested in finding out why. Shouldn't dism complain if it can't process the inf files?

No. They work on a real win7 system without problems, they never updated the comments. The drivers are from Paragon Backup and Recovery 2012 Free which runs on Win7.

Hi Wimb, I'm back with more questions. I'm trying to install some drivers used by Paragon HDM for mounting backup files to a drive letter. I copied the files to the \Win7_drivers and when I do the build, dism processes those files, but when I boot up none of the .sys files or services are installed.. I'm not sure what I'm doing wrong or if this was the right place to copy the files Here's one of the .inf files that I copied. Any ideas why the drivers and services are not installed? ; ; UIM Bus Driver for Win 2000/XP ; ; 2003-06-25 gvv ; [version] Signature="$WINDOWS NT$" Class=UIM ClassGuid={19837C5C-96F5-45e0-9A2D-C6BB26E1B12B} Provider=%Paragon% DriverVer=12/25/2006,6.0.3.1 CatalogFile=uimbus.cat [ClassInstall32] AddReg=UimClassReg [UimClassReg] HKR,,,,%UimClassName% HKR,,Icon,,"-9" [SourceDisksNames] 1 = %Disk1Desc% [SourceDisksFiles] UimBus.sys = 1 UimFIO.sys = 1 [DestinationDirs] DefaultDestDir = 12 ;--------------------------------------- [Manufacturer] %Paragon%=UIM_Adapter [UIM_Adapter] %DeviceDesc% = UimBus_Inst, Root\UIM_BUS [UimBus_Inst] CopyFiles = UimBus.DriverFiles [UimBus_Inst.Services] AddService = UimBus, 2, UimBus_Service_Inst [UimBus_Service_Inst] DisplayName = %DeviceDesc% ServiceType = 1 StartType = 1 ErrorControl = 1 ServiceBinary = %12%\UimBus.sys [UimBus.DriverFiles] UimBus.sys,,,2 UimFIO.sys,,,2 [Strings] UimClassName= "Universal Image Mounter" Paragon = "Paragon" UIM = "Universal Image Mounter Controller" DeviceDesc = "Universal Image Mounter Controller" Disk1Desc = "Installation Disk for Universal Image Mounter Controller"

Wimb, not starting driver_fix.cmd was indeed the cause of the FSC editor delay. I experienced the same delay in another program and that is also fixed now. Good call and thanks for taking the time to look at it. What do you think about using pecmd.ini to do some of the processing during system initialization?

I am not loading any drivers during startup. I commented out Autostart of driver_fix.cmd, because I thought using PENetwork would be enough if I needed connectivity and I could start that on demand. I will run the cmd manually and see if that fixes the delay. I didn't realize I needed to run this command. BTW. is pecmd with pecmd.ini being used? Wouldn't this be better than running installs from the startnet.cmd?

I am using the portable version. In a system built with MAKE_PE3, it has this delay problem not on another PE I used. Have you tried what I described?

@wimb or anyone else that might have a suggestion My Make_PE3 image works fairly well, but I have one problem that I would like to solve and I'm stumped on how to proceed. I have an app called Faststone Capture that is installed and it works flawlessly except for one thing. When I do the first screen capture after FSC is launched, it takes the FSC Editor which displays the screen capture more than 1.5 minutes to appear on the display. The same holds true for appearing in TaskManager. For any captures after that, the screen appears without any delay until I exit FSC. Starting it again gives me a delay on the first screen capture. I have another image that I tried from someone else that also has FSC in it and there is no delay on the first screen capture. Do you or anyone else have any idea what my image might be missing to cause this? What would be a good way of tracking this down?

Sorry for the confusion. I just realized that option 3 is what I was asking for.

Yes, but I have to keep an installed vanilla SP1 system around that is taking up 10 GIG of valuable space. Besides this would be ideal for those that want to use a frozen version or source for the PE build. All they would need to keep for a build is the MAKE_PE3 directory after populating it with the necessary system files.

After doing more testing, the only way I've found to Auto-Start something in the MAKE_PE3 environment is to use the [RunOnce] key. [Run] and (RunOnceEx] do not get executed during the WinPE startup. The reg keys that I set for RunOneEx are still there after the system is up, so Win7PE is ignoring them for some reason. Anyway, RunOnce works great for me and that makes things very flexible by being able to use files (RegTweaks for the active system) outside of Make_PE3. This leads me to another question for Wimb. Would it be possible to add an option to not delete and reuse the already collected files to rebuild the iso? Basically, you would be starting at the point where winre.wim is used and continue from there. This would save time copying the same Win7 files over and over again every time you do a build and you would not have to keep a live vanilla Win7 SP1 system around for that purpose. One could then make changes to PE3_add, PE3_reg, Win7_Drivers, etc. without starting from scratch. Does this make sense? Ciao....,

Wimb, THANK YOU for convincing me to give MAKE_PE3 another try. I had some problems in the way I was trying to define my reg entries. I kept getting a BSOD when I tried to set my environment variables using CurrentControlSet. I changed it to ControlSet001 and that worked. You are correct in saying that User Pinned\Start Menu is working. I was trying to add a new toolbar (Quick Launch) to the taskbar. I added a few objects to the default user Quick Launch Folder, but the folder does not show up on the taskbar. I can manually add the folder as a new toolbar when booted. As far as reg entry Run goes, I added a 2nd program called regscanner from Nirsoft and that did not autostart either. I ran Autoruns and I see three run entries. Hotswap is the only one that started. Maybe this has to do with the AutoRun=1 entry for that SW. Statbar Applet RegScanner Applet HotSwap! Applet From the plugins folder (defined like the hotswap run): [HKEY_LOCAL_MACHINE\PE3-USER\Software\Microsoft\Windows\CurrentVersion\Run] "StatBar Applet"="\"X:\\Toolbx\\Statbar.EXE\"" [HKEY_LOCAL_MACHINE\PE3-USER\Software\Microsoft\Windows\CurrentVersion\Run] "RegScan Applet"="\"X:\\Toolbx\\RegScanner.EXE\"" Statbar is an old VB program that still works well on a Win7 system. It works in PE too, but it takes over 1 minute to appear on the screen. I have to start it manually. All other programs start instantly. Aside from that, I'm happy with the results so far. No need to give up. If you have any ideas why entries in the Startup Folder or Run Key do let get launched, I'd be interested. I really appreciate you taking the time to help me out with my PE problems. I'm starting to get a better feel for Make_PE3 now, so hopefully, I will no longer need to bother you. Again, thanks ...

Well looks like I'm going to have to give up on MAKE_PE3. I can't seem to get certain user reg entries to work. I.e Using [HKEY_LOCAL_MACHINE\PE3-USER\ for [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run]. When I check the registry after the desktop appears the Run entry is missing. Also, if I do a build with objects in the Startup Folder for the default user, those entries do not run after winpe initializes the desktop. The Quick Launch toolbar doesn't show up either. I think this has something to do with the user account. There doesn't seem to be one. Basically, I can only customize the system after it is booted. Am I missing something here or is this a limitation of MAKE_PE3?

Yes, I let driver_fix.cmd run and did not cancel it. I'll cancel and see what PENetwork does. Ciao ... Edit: Same result

Okay, MAKE_PE3 with a vanilla Win7 SP1 install as input seems to be the solution to my previous problems. IE8 is working now and I no longer get an error message opening Control Panel. One minor thing is that the Ethernet Network Icon still shows Authentication Failure (with ?) even though the Ethernet network connection is working and I am able to use the Internet. If you have an idea what that might be let me know.

I have a bootable usb drive with XP installed on it for my own recovery purposes. I need a decent 7PE iso that I can use when my friends call me for help. I will give Make_PE3 another try using a fresh installed W7 SP1 with no updates and see if that solves the problems I am seeing. Two more questions: Does MAKE_PE3.cmd do everything that MAKE_PE3.exe does? I assume the created iso file should be the same either way right? If so, I will just change the dism /set inputlocale statement in the cmd file and that will take care of the default keyboard layout for me. I guess this could be a option in the GUI if you ever decide to update it. Maybe have make_pe3 allow for additional dism commands at the end from a txt file before committing and unmounting. Ciao....

I wanted to only change the inputlocale to de-de and leave the rest as en-us. If I understand correctly, make_pe3 does not create a portable or mini win7 and will produce a pe iso that may be error prone. Is that correct? The reason I wanted to use Make_PE3 was because of the small iso size. If I use the VHD method, won't that make the iso much bigger? My goal is a small W7 recovery cd to replace my aging BartPE boot CD.

I used my live windows 7 SP1 system. which includes June Patch-Tuesday security fixes. I thought I was making a portable Win7. As far as the keyboard goes, I checked the reg entry after booting the iso and the preload key was still 409 and not 407 like in the plugin. It seems that the keyboard plugin reg entries are reset when you later run dism /set inputlocale:en-us. in Make_Pe3.exe I can change the cmd file to modify the inputlocale dism entry to de-de, but I can't do that with the exe file. I'm a bit confused now as to what you mean by portable or mini Win7. So does 7pe_x86.iso=portable Win7? Sorry for the noob questions.....

I'm still having some problems with my ISO. I did not see any sample keyboard layouts except for the one to toggle between EN and RU. I added the following .reg, but when I look at change keyboard in Region and Language, Keyboard US is there instead of Keyboard German and cmd prompt is still mapped to the en layout. Windows Registry Editor Version 5.00 ; Keyboard Layout Default German [HKEY_LOCAL_MACHINE\PE3-USER\Keyboard Layout] @=hex(0): [HKEY_LOCAL_MACHINE\PE3-USER\Keyboard Layout\Preload] "1"="00000407" I got my WLAN to work, but the implementation of IE8 seems to be broken for me. When I launch IE8, I get a message saying "a problem displaying google.com caused IE to refresh the webpage using compatibility view", but nothing is displayed. If I use portablefirefox, I can view web pages without problems. When I try to use an Ethernet Connection, there's no connection and the icon shows Failed Authentication. The driver seems to be installed correctly and this usually works without problems on other boot cds that I have tried. Thanks for any pointers. Also, if there is a better place to post my questions, please let me know.

I understand that 7pe_x86.iso (without WAIK) and pe3_x86.iso (with WAIK) are made from different .wim files, but does anyone know what advantage one iso has over the other?

Yes, when I boot the iso, I can change it. What I meant was to already have this as a default in the iso. Basically, I would like to make an iso with a few customized settings etc. that would end up being the default. I need to investigate the docs and all the subdirs under \MAKE_PE3. I would assume the keyboard can be set with a reg file somewhere. BTW, can make_pe_42.exe be extracted to a root drive that does not have a system installed on it and why do you specify that it needs to be on the root? Thanks for your help .....

@wimb Hi, I'm new to MAKE_PE3 and so far this seems to be the best solution for me to create a decent Win7 recovery iso. I noticed that the Make_PE3.exe GUI has a small DPI issue if you do not use Windows standard 96DPI (I use 120DPI). There is some text truncation. If you are coding this with Autoit, this might be of interest to you: fontgui-resizing or this in general: DPIAware Since I am just starting to use this tool, I have not found all the key areas that can be customized or how to do it. My first test was just to build the iso without WAIK which was fine except that I have a German Keyboard and the windows cmd prompt uses the U.S. keyboard layout. This would be one thing I would like to change, but not sure how. Is there a way to change the keyboard layout to German?

No, it's not mandatory. install will overwrite files and abort if there would be a problem. But yes there will be files remaining from old Windows installation. With removing an old installation without formating, i see 2 problems: 1. NTFS security settings - one would need to take ownership & grant access or using a tool like xdel 2. Junctions and Symlink (and this is the thing that scares me ! ) - junctions and symlinks in Win7 are created with full path. think you have an offline win7 that has C: as normal drive letter and is now under your current running windows mounted as D: It's junctions and symlink will still point to C:, but that could be the current running windows Even Mircosofts own tools like robocopy don't handle symlinks right. It might happen that deleting an offline windows switch the drive and start deleting files/folder one the current system drive ! Fyi JFX After asking the author to add an enhancement to XDEL, he has updated it with a new parameter: --one-volume-only You no longer need to be scared. With this parm, only files on the target drive are deleted. The updated version is not on his website because he is in the process of moving files to another site, Here's the Link.

Hi JFX, I noticed for Win7 etc. WinNTSetup only allows for install.wim. I have several integrated .wim images under different names, but cannot select them without renaming the images. Did you have a specific reason for doing this? Thanks...