[wimb]

When I cancel driver_fix.cmd and then manually give

drvload.exe X:\Windows\inf\usb.inf

then the FSCapture 1.5 min delay problem is gone.

Loading usb.inf will also Start Audiosrv service which probably is needed because of the click sound when using FSCapture

Instead you can also open ServiWin Portable App from PStart > System
and then Start Audiosrv will solve the FSCapture problem

This post has been edited by wimb: 18 July 2012 - 01:23 PM

[click-click]

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?

This post has been edited by click-click: 18 July 2012 - 01:59 PM

[click-click]

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?

[wimb]

driver_fix.cmd is essential and preferred in all cases
driver_fix.cmd loads many drivers and start a lot of services where PENetwork is only limited to Network.

pecmd can install drivers from Win7 OS DriverStore as done with desktop icon on demand
but pecmd fails to install drivers when used with DriverPacks folder.
pecmd will install missing drivers but does not update existing drivers.

dpinst.exe is used via desktop icon on demand to install drivers from DriverPacks folder
and dpinst.exe is used by driver_fix.cmd for automatic install of drivers from drv\x86 folder.
The drv\x86 folder is searched on any drive and it can be used for the large video driver.

This post has been edited by wimb: 19 July 2012 - 12:31 AM

[click-click]

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]

Could it be that these drivers are suitable for XP but NOT for Win 7 ?

This post has been edited by wimb: 21 July 2012 - 08:49 AM

[click-click]

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.

[wimb]

May be then try to make Portable Win 7 which allows to Install anything you like and meanwhile keep the drivers.

http://www.911cd.net...showtopic=23553
http://www.911cd.net...showtopic=24424

Performance of Portable Win 7 in VHD booting from USB is much better than any PE

Quote

Procedure for booting with 1.6 GB Portable Windows 7 VHD file on USB-harddisk
Step 1. - Direct Install Windows 7 in a 10 GB VHD file on local harddisk and created by WinNTSetup2_x86.exe with Ctrl + Shift + V
Step 2. - Run VHD_W7_Compact.exe to Copy Win7 VHD content in 10 min to New VHD file of Reduced Size on USB-harddisk
Step 3. - Reboot with 1.6 GB Win7 VHD file from USB

This post has been edited by wimb: 21 July 2012 - 10:35 AM

[click-click]

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?

This post has been edited by click-click: 21 July 2012 - 12:08 PM

[JFX]

It's a virtual driver, not connected to real hardware, so dism will only add it to the driver store.

There should be an uim exe file with the installation files that can install that driver.

[click-click]

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?

[JFX]

click-click, on 21 July 2012 - 12:50 PM, said:

Do I just run that after Win7PE is booted?

As far as i remember yes, just run it after boot. It's a silent installer and should create a log file next to it.
But I have not used it for a long time cause it makes trouble with the shadowprotect driver I use.

[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.

This post has been edited by click-click: 21 July 2012 - 02:22 PM

[JFX]

Try to delete the HKLM\SYSTEM\CurrentControlSet\Control\MiniNT registry key before starting Paragon software.

Maybe they disabled some features in WinPE mode. But don't forget to create the MiniNT key after running paragon as it's required for shutdown/restart.

[click-click]

That key does not exist in my Win7Pe. I thought that only applied to XP PE. Maybe I need to
include VSS. I saw your post here, but I did not see how to patch the three files you mentioned there.

This post has been edited by click-click: 23 July 2012 - 04:01 AM

[click-click]

I made a mistake about the presence of the MiniNT key . It does exist on my system. I will try this and see what happens.

This post has been edited by click-click: 23 July 2012 - 04:48 PM

[click-click]

Removing MiniNT unlocks the archive tab for the Paragon Backup/Recovery SW that I have tested, but mounting does not work for the 2012 versions. I can mount with HDM10, but when I try to unmount the drive, I get an error. There is no Force Unmount check-box in HDM10 Suite like in HDM12 Pro.

This post has been edited by click-click: 29 July 2012 - 02:44 AM

[click-click]

wimb, on 19 July 2012 - 12:13 AM, said:

driver_fix.cmd is essential and preferred in all cases
driver_fix.cmd loads many drivers and start a lot of services where PENetwork is only limited to Network.

Anyone know why netvwifibus.inf shows an error (0xe0000102) in a Make_PE3 build when drv_fix.cmd loads the various infs? This is the only inf that it complains about with the laptop I'm using.

This post has been edited by click-click: 29 July 2012 - 04:24 AM

[Tduy]

How Added Japanese, Korean and Chinese Support to Make_Pe (read file name and page Web)
Thank All !

[BigDawgFelton]

Has anyone seen any issue in prior builds where having USB devices such as mouse/keyboard plugged into certain ports causing issues with programs or other devices installed?

Basically what I have done is taken the win7pe build and customized the image for diagnostics of some specific PCs. All drivers, and programs have been installed. I have added touchscreen support and everything was working well with our original unit. A similar unit is now being built except with a different style touchscreen. All OS images are the same for this machine so I assume no drivers have changed for this.

We use a program that is built to read motherboard information such as serial number and other information. When I have USB and mouse plugged in on certain ports during startup this program fails to function. Does anyone have any ideas? Driver issues? Device mapping problem? I am lost at this point.

If I leave these devices unplugged from the certain USB ports on bootup the program functions properly. I can plug in the devices to the problematic ports after bootup with no issues.