You are not logged in. Please login or register.
DriverPacks.net Forum » Feedback and Support - DriverPacks Base » [SOLVED] DpsFnshr.exe take 40 minutes...is possible?
Hi, this driverpacks are very good but with italian installation cd i have wait over 40 minutes for dpsfnshr.exe
I would like to konow if is a problem or not...
My windows's cd have all packs with 3rd party created with method 2.
thank you and sorry for my bad english
ps
My pc is a notebook asus turionx2 tl50 (1600mhz x 2) 1gb ddr2 533 mhz, hd 100gb 5400 rpm and vga geforce 7600 256mb
Last edited by frasuperbike (2006-08-29 03:05:19)
Please post your DPsFnshr.log!
On some computers it takes a looooooong time , i can confirm that.
On some computers it takes a looooooong time , i can confirm that.
Indeed.
That is why you make all the effords to get it unattended anyway - so you can lean back and let it work, do something else, have a drink, take walk etc 
That is why you make all the effords to get it unattended anyway - so you can lean back and let it work, do something else, have a drink, take walk etc
faster faster mutherrf***er 
My log file is here...
2006-08-28 13:54:41 : <INIT> DriverPacks Finisher 6.08.6 initialized.
2006-08-28 13:54:41 : <INIT> Detected platform wnt5_x86-32.
2006-08-28 13:54:41 : <INIT> Start logging of the HWIDs for relevant devices present in this system.
2006-08-28 13:54:41 : <INIT> 1. ACPI devices
ACPI\ACPI0003\3&267A616A&0 : Scheda AC Microsoft
ACPI\ATK0100\1010100 : ATK0100 ACPI UTILITY
ACPI\AUTHENTICAMD_-_X86_FAMILY_15_MODEL_72\_0 : AMD Turion(tm) 64 X2 Mobile Technology TL-50
ACPI\AUTHENTICAMD_-_X86_FAMILY_15_MODEL_72\_1 : AMD Turion(tm) 64 X2 Mobile Technology TL-50
ACPI\FIXEDBUTTON\2&DABA3FF&0 : Pulsante caratteristica ACPI fissa
ACPI\PNP0000\4&136225A3&0 : Controller di interrupt programmabile (PIC)
ACPI\PNP0100\4&136225A3&0 : Timer di sistema
ACPI\PNP0200\4&136225A3&0 : Controller di accesso diretto alla memoria (DMA)
ACPI\PNP0303\4&136225A3&0 : Logitech PS/2 Keyboard (106 Keys Ctrl+Caps)
ACPI\PNP0800\4&136225A3&0 : Altoparlante di sistema
ACPI\PNP0A03\0 : Bus PCI
ACPI\PNP0B00\4&136225A3&0 : Orologio di sistema CMOS a tempo reale
ACPI\PNP0C01\1 : Scheda di sistema
ACPI\PNP0C02\0 : Risorse scheda madre
ACPI\PNP0C02\10 : Risorse scheda madre
ACPI\PNP0C02\11 : Risorse scheda madre
ACPI\PNP0C02\99 : Risorse scheda madre
ACPI\PNP0C04\4&136225A3&0 : Coprocessore matematico
ACPI\PNP0C09\4&136225A3&0 : Controller integrato compatibile ACPI Microsoft
ACPI\PNP0C0A\0 : Batteria a metodo di controllo compatibile ACPI Microsoft
ACPI\PNP0C0C\AA : Pulsante alimentazione ACPI
ACPI\PNP0C0D\2&DABA3FF&0 : Coperchio ACPI
ACPI\PNP0C0E\2&DABA3FF&0 : Pulsante sospensione ACPI
ACPI\PNP0C14\0 : Strumentazione gestione Microsoft Windows per ACPI
ACPI\SYN0A06\4&136225A3&0 : Logitech-compatible Mouse PS/2
ACPI\THERMALZONE\TZ00 : Zona termica ACPI
ACPI_HAL\PNP0C08\0 : Sistema compatibile ACPI Microsoft
ROOT\ACPI_HAL\0000 : PC multiprocessore ACPI
28 matching device(s) found.
2006-08-28 13:54:42 : <INIT> 2. PCI devices
PCI\VEN_1022&DEV_1100&SUBSYS_00000000&REV_00\3&267A616A&0&C0: Adattatore PCI standard per CPU host
PCI\VEN_1022&DEV_1101&SUBSYS_00000000&REV_00\3&267A616A&0&C1: Adattatore PCI standard per CPU host
PCI\VEN_1022&DEV_1102&SUBSYS_00000000&REV_00\3&267A616A&0&C2: Adattatore PCI standard per CPU host
PCI\VEN_1022&DEV_1103&SUBSYS_00000000&REV_00\3&267A616A&0&C3: Adattatore PCI standard per CPU host
PCI\VEN_10DE&DEV_0260&SUBSYS_00000000&REV_A3\3&267A616A&0&50: Adattatore PCI standard per bus ISA
PCI\VEN_10DE&DEV_0264&SUBSYS_13671043&REV_A3\3&267A616A&0&51: NVIDIA nForce PCI System Management
PCI\VEN_10DE&DEV_0265&SUBSYS_13671043&REV_A1\3&267A616A&0&68: Controller standard PCI IDE
PCI\VEN_10DE&DEV_026C&SUBSYS_13671043&REV_A2\3&267A616A&0&81: Microsoft UAA Bus Driver for High Definition Audio
PCI\VEN_10DE&DEV_026D&SUBSYS_13671043&REV_A3\3&267A616A&0&58: Controller host USB OpenHCD Standard
PCI\VEN_10DE&DEV_026E&SUBSYS_13671043&REV_A3\3&267A616A&0&59: Controller host standard avanzato da PCI a USB
PCI\VEN_10DE&DEV_026F&SUBSYS_00000000&REV_A2\3&267A616A&0&80: Adattatore PCI standard da PCI a PCI
PCI\VEN_10DE&DEV_0270&SUBSYS_13671043&REV_A2\3&267A616A&0&48: nForce Memory Controller
PCI\VEN_10DE&DEV_0271&SUBSYS_13671043&REV_A3\3&267A616A&0&53: NVIDIA nForce System Management Controller
PCI\VEN_10DE&DEV_027E&SUBSYS_13671043&REV_A2\3&267A616A&0&07: nForce Memory Controller
PCI\VEN_10DE&DEV_027F&SUBSYS_13671043&REV_A2\3&267A616A&0&06: nForce Memory Controller
PCI\VEN_10DE&DEV_02F7&SUBSYS_13671043&REV_A2\3&267A616A&0&00: Controller RAM standard PCI
PCI\VEN_10DE&DEV_02F8&SUBSYS_13671043&REV_A2\3&267A616A&0&03: nForce Memory Controller
PCI\VEN_10DE&DEV_02F9&SUBSYS_13671043&REV_A2\3&267A616A&0&04: nForce Memory Controller
PCI\VEN_10DE&DEV_02FB&SUBSYS_00000000&REV_A1\3&267A616A&0&20: Adattatore PCI standard da PCI a PCI
PCI\VEN_10DE&DEV_02FD&SUBSYS_00000000&REV_A1\3&267A616A&0&18: Adattatore PCI standard da PCI a PCI
PCI\VEN_10DE&DEV_02FE&SUBSYS_13671043&REV_A2\3&267A616A&0&02: nForce Memory Controller
PCI\VEN_10DE&DEV_02FF&SUBSYS_13671043&REV_A2\3&267A616A&0&05: nForce Memory Controller
PCI\VEN_10DE&DEV_0398&SUBSYS_13221043&REV_A1\4&A70D623&0&0020: NVIDIA GeForce Go 7700
PCI\VEN_10EC&DEV_8168&SUBSYS_11F51043&REV_01\4&23E04D34&0&0018: Realtek RTL8168/8111 PCI-E Gigabit Ethernet NIC
PCI\VEN_1180&DEV_0476&SUBSYS_13671043&REV_B3\4&2B17F62E&0&0880: Ricoh R/RL/5C476(II) o controller CardBus compatibile
PCI\VEN_1180&DEV_0552&SUBSYS_13671043&REV_08\4&2B17F62E&0&0980: Controller host OHCI compatibile IEEE 1394
PCI\VEN_1180&DEV_0592&SUBSYS_13671043&REV_08\4&2B17F62E&0&0B80: Ricoh Memory Stick Host Controller
PCI\VEN_1180&DEV_0822&SUBSYS_13671043&REV_17\4&2B17F62E&0&0A80: Ricoh SD Bus Host Adapter
PCI\VEN_14E4&DEV_4318&SUBSYS_120F1043&REV_02\4&2B17F62E&0&1880: Scheda di rete Broadcom 802.11g
29 matching device(s) found.
2006-08-28 13:54:42 : <INIT> 3. HDAUDIO devices
HDAUDIO\FUNC_01&VEN_10EC&DEV_0861&SUBSYS_10430605&REV_1003\4&9389265&0&0001: Realtek High Definition Audio
HDAUDIO\FUNC_02&VEN_1057&DEV_3055&SUBSYS_104310C6&REV_1007\4&9389265&0&0101: Motorola SM56 Data Fax Modem
2 matching device(s) found.
2006-08-28 13:54:42 : <INIT> 4. USB devices
USB\ROOT_HUB\4&36361B9C&0 : Hub principale USB
USB\ROOT_HUB20\4&20C6D329&0 : Hub principale USB
USB\VID_0B05&PID_1712\0194E8-5B-0002 : USB Device
USB\VID_174F&PID_A311\5&368A7F73&0&5 : USB2.0
4 matching device(s) found.
2006-08-28 13:54:43 : <INIT> Logging of HWIDs complete.
2006-08-28 13:54:43 : <INIT> Processed settings.
2006-08-28 13:54:43 : <FLTR> Collected the HWIDs for this system.
2006-08-28 13:54:43 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0001__D-G-A-1] (1 of 22 exceptions).
2006-08-28 13:54:43 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-08-28 13:54:43 : <FLTR> Found tagfile "C:\ATICCC.ins" (1/2).
2006-08-28 13:54:43 : <FLTR> Found tagfile "C:\D\G\A\1\ATICCC.exe" (2/2).
2006-08-28 13:54:43 : <FLTR> 4. +infFiles (ANY +infFiles must be matched)
2006-08-28 13:54:43 : <FLTR> Wildcard specified for +infFiles requirement: scan for .inf files (1 of 1 +infFiles).
2006-08-28 13:54:43 : <FLTR> Checking .inf file 'C:\D\G\A\1\C2_34826.inf'.
2006-08-28 13:54:45 : <FLTR> Checking .inf file 'C:\D\G\A\1\CX_34826.inf'.
2006-08-28 13:54:47 : <FLTR> Checking .inf file 'C:\D\G\A\1\E2_34826.inf'.
2006-08-28 13:54:48 : <FLTR> Checking .inf file 'C:\D\G\A\1\EX_34826.inf'.
2006-08-28 13:54:48 : <FLTR> Checking .inf file 'C:\D\G\A\1\MX_34826.inf'.
2006-08-28 13:54:49 : <FLTR> ! Could not match any of the +infFiles.
2006-08-28 13:54:49 : <FLTR> => This exception will not be applied.
2006-08-28 13:54:49 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0002__D-G-A-1] (2 of 22 exceptions).
2006-08-28 13:54:49 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-08-28 13:54:49 : <FLTR> ! Could not find tagfile 'C:\ATICCP.ins' (1 of 2 tagfiles).
2006-08-28 13:54:49 : <FLTR> => This exception will not be applied.
2006-08-28 13:54:49 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0021__D-G-A-2] (3 of 22 exceptions).
2006-08-28 13:54:49 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-08-28 13:54:49 : <FLTR> Found tagfile "C:\ATICCC.ins" (1/2).
2006-08-28 13:54:49 : <FLTR> Found tagfile "C:\D\G\A\1\ATICCC.exe" (2/2).
2006-08-28 13:54:49 : <FLTR> 4. +infFiles (ANY +infFiles must be matched)
2006-08-28 13:54:49 : <FLTR> ! Could not match any of the +infFiles.
2006-08-28 13:54:49 : <FLTR> => This exception will not be applied.
2006-08-28 13:54:49 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0022__D-G-A-2] (4 of 22 exceptions).
2006-08-28 13:54:49 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-08-28 13:54:49 : <FLTR> ! Could not find tagfile 'C:\ATICCP.ins' (1 of 2 tagfiles).
2006-08-28 13:54:49 : <FLTR> => This exception will not be applied.
2006-08-28 13:54:49 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0003__D-G-A-3] (5 of 22 exceptions).
2006-08-28 13:54:49 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-08-28 13:54:49 : <FLTR> Found tagfile "C:\D\G\A\3\CPanel.exe" (1/1).
2006-08-28 13:54:49 : <FLTR> 4. +infFiles (ANY +infFiles must be matched)
2006-08-28 13:54:49 : <FLTR> ! Could not match any of the +infFiles.
2006-08-28 13:54:49 : <FLTR> => This exception will not be applied.
2006-08-28 13:54:49 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0004__D-G-3-1] (6 of 22 exceptions).
2006-08-28 13:54:49 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-08-28 13:54:49 : <FLTR> ! Could not find tagfile 'C:\WINDOWS\system32\3dfxV2ps.dll' (1 of 1 tagfiles).
2006-08-28 13:54:49 : <FLTR> => This exception will not be applied.
2006-08-28 13:54:49 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0005__D-G-S-1] (7 of 22 exceptions).
2006-08-28 13:54:49 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-08-28 13:54:49 : <FLTR> ! Could not find tagfile 'C:\WINDOWS\system32\drivers\sigrp.sys' (1 of 1 tagfiles).
2006-08-28 13:54:49 : <FLTR> => This exception will not be applied.
2006-08-28 13:54:49 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0006__D-L-NV-123] (8 of 22 exceptions).
2006-08-28 13:54:49 : <FLTR> 2. +hwids (ANY +hwids must be matched)
2006-08-28 13:54:49 : <FLTR> ! Could not match any of the +hwids.
2006-08-28 13:54:49 : <FLTR> => This exception will not be applied.
2006-08-28 13:54:49 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0007__D-S-CR-1] (9 of 22 exceptions).
2006-08-28 13:54:49 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-08-28 13:54:49 : <FLTR> ! Could not find tagfile 'C:\WINDOWS\system32\drivers\ha20x2k.sys' (1 of 2 tagfiles).
2006-08-28 13:54:49 : <FLTR> => This exception will not be applied.
2006-08-28 13:54:49 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0008__D-S-CR-2] (10 of 22 exceptions).
2006-08-28 13:54:49 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-08-28 13:54:49 : <FLTR> ! Could not find tagfile 'C:\WINDOWS\system32\drivers\ha10x2k.sys' (1 of 3 tagfiles).
2006-08-28 13:54:49 : <FLTR> => This exception will not be applied.
2006-08-28 13:54:49 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0009__D-S-CR-3] (11 of 22 exceptions).
2006-08-28 13:54:49 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-08-28 13:54:49 : <FLTR> ! Could not find tagfile 'C:\WINDOWS\system32\drivers\P17.sys' (1 of 2 tagfiles).
2006-08-28 13:54:49 : <FLTR> => This exception will not be applied.
2006-08-28 13:54:49 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0010__D-S-H-2] (12 of 22 exceptions).
2006-08-28 13:54:49 : <FLTR> 4. +infFiles (ANY +infFiles must be matched)
2006-08-28 13:54:50 : <FLTR> ! Could not match any of the +infFiles.
2006-08-28 13:54:50 : <FLTR> => This exception will not be applied.
2006-08-28 13:54:50 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0011__D-S-N] (13 of 22 exceptions).
2006-08-28 13:54:50 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-08-28 13:54:50 : <FLTR> ! Could not find tagfile 'C:\WINDOWS\system32\drivers\nvapu.sys' (1 of 1 tagfiles).
2006-08-28 13:54:50 : <FLTR> => This exception will not be applied.
2006-08-28 13:54:50 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0012__D-S-S-U] (14 of 22 exceptions).
2006-08-28 13:54:50 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-08-28 13:54:50 : <FLTR> ! Could not find tagfile 'C:\WINDOWS\system32\drivers\sthda.sys' (1 of 1 tagfiles).
2006-08-28 13:54:50 : <FLTR> => This exception will not be applied.
2006-08-28 13:54:50 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0013__D-S-SI-1] (15 of 22 exceptions).
2006-08-28 13:54:50 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-08-28 13:54:50 : <FLTR> ! Could not find tagfile 'C:\WINDOWS\system32\drivers\sis7012.sys' (1 of 1 tagfiles).
2006-08-28 13:54:50 : <FLTR> => This exception will not be applied.
2006-08-28 13:54:50 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0014__D-S-SI-2] (16 of 22 exceptions).
2006-08-28 13:54:50 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-08-28 13:54:50 : <FLTR> ! Could not find tagfile 'C:\WINDOWS\system32\drivers\sis7018.sys' (1 of 1 tagfiles).
2006-08-28 13:54:50 : <FLTR> => This exception will not be applied.
2006-08-28 13:54:50 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0015__D-S-T-2] (17 of 22 exceptions).
2006-08-28 13:54:50 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-08-28 13:54:50 : <FLTR> ! Could not find tagfile 'C:\WINDOWS\system32\drivers\FM801.sys' (1 of 1 tagfiles).
2006-08-28 13:54:50 : <FLTR> => This exception will not be applied.
2006-08-28 13:54:50 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0016__D-S-T-3] (18 of 22 exceptions).
2006-08-28 13:54:50 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-08-28 13:54:50 : <FLTR> ! Could not find tagfile 'C:\WINDOWS\system32\drivers\cmaudio.sys' (1 of 1 tagfiles).
2006-08-28 13:54:50 : <FLTR> => This exception will not be applied.
2006-08-28 13:54:50 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0017__D-S-T-4] (19 of 22 exceptions).
2006-08-28 13:54:50 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-08-28 13:54:50 : <FLTR> ! Could not find tagfile 'C:\WINDOWS\system32\drivers\TT1724ht.sys' (1 of 1 tagfiles).
2006-08-28 13:54:50 : <FLTR> => This exception will not be applied.
2006-08-28 13:54:50 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0018__D-S-T-5] (20 of 22 exceptions).
2006-08-28 13:54:50 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-08-28 13:54:50 : <FLTR> ! Could not find tagfile 'C:\WINDOWS\system32\drivers\dmxsens.sys' (1 of 1 tagfiles).
2006-08-28 13:54:50 : <FLTR> => This exception will not be applied.
2006-08-28 13:54:50 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0019__D-S-V-1] (21 of 22 exceptions).
2006-08-28 13:54:50 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-08-28 13:54:50 : <FLTR> ! Could not find tagfile 'C:\WINDOWS\system32\drivers\envysens.sys' (1 of 1 tagfiles).
2006-08-28 13:54:50 : <FLTR> => This exception will not be applied.
2006-08-28 13:54:50 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0020__D-S-V-2] (22 of 22 exceptions).
2006-08-28 13:54:50 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-08-28 13:54:50 : <FLTR> ! Could not find tagfile 'C:\WINDOWS\system32\drivers\vinyl97.sys' (1 of 2 tagfiles).
2006-08-28 13:54:50 : <FLTR> => This exception will not be applied.
2006-08-28 13:54:50 : <FLTR> Finished filtering exceptions.
2006-08-28 13:54:50 : <EXEC> No exceptions left to execute: none have met all requirements!
2006-08-28 13:54:50 : <KTD> KTD cache location set: "C:\WINDOWS\DriverPacks".
2006-08-28 13:54:50 : <KTD> KTD is enabled, in PATHS mode.
2006-08-28 13:54:50 : <KTD> Copy drivers inside "C:\D" to "C:\WINDOWS\DriverPacks\D".
2006-08-28 14:24:40 : <KTD> Successfully created the "%KTD%" environment variable, it has been set to "C:\WINDOWS\DriverPacks". It will be available after the next reboot.
2006-08-28 14:25:03 : <KTD> Successfully updated the DevicePath registry value!
2006-08-28 14:31:27 : <KTD> Successfully created the .pnf files. KTD has been applied! It will be available after the next reboot.
2006-08-28 14:35:46 : <CLNP> Deleted the DriverPacks, which were located in 'C:\D'.
2006-08-28 14:35:46 : <CLNP> Deleted 'C:\DPsFnshr.ini'!
2006-08-28 14:35:46 : <CLNP> Deleted 'C:\devcon.exe'!
2006-08-28 14:35:46 : <CLNP> Deleted 'C:\makePNF.exe'!
2006-08-28 14:35:46 : <CLNP> Deleted 'C:\addUsepmtimer.exe'!
2006-08-28 14:35:46 : <CLNP> Deleted 'C:\ATICCC.ins'!
2006-08-28 14:35:46 : <CLNP> Added new value to the RunOnce key in the registry: the DriverPacks Finisher itself will get deleted after the next reboot.
2006-08-28 14:35:46 : Program terminated.help me please...
I thought so already... it's due to how KTD is currently being applied. As you can see in the log, it took 30 minutes! And deleting them took another 3.5 minutes. 6 minutes were necessary for creating the .PNF files.
In the next version of the DriverPacks BASE, there will be a major update for the KTD functionality. The result will be that only those 6 minutes for creating the .PNF files will be necessary! Note that this greatly depends on the amount of drivers!
you think that is correct?
thank you
Hi
yes, Bâshrat the Sneaky confirmed it would be possible to optimize the process when KTD is used.
a few days ago a kind soul wondered wether it was possible to not "copy and delete" the selected packs, but to "move" the selected packs.
The idea got a little discussion, it was clear that in a not so distant past, this might not have worked.
But, Wim thought it over, recoded and tested in his own machines, and told us it worked.
The beta testers should be able to put this to test soon.
if this works for you, you gain over 33 minutes.
others might gain as much as 8 minutes.
that made me wonder about your case.
I wonder why it takes 30 minutes to copy about one gigabyte.
in another machine's log I saw a little over 6 minutes..
an old hard disk one uses for tests might be a slow one.
but it could also be a wrong setting in the machine's BIOS, so that the drive works slower than it could work.
when finisher launches KTD process, the machine should already run the drive in enhanced mode (DMA etc), which is why I wonder what hardware your tests run on..
It's a laptop HDD, jtdoom 
That's the reason why. I've also seen that when you copy large files from one location on the HDD to another one on the same HDD, that everything gets very slow. It's still LONG though.
P.S.: if you use method 2, it will currently be slower than method 1 due to the filesize: the drivers will be uncompressed when using method 2 (>1.2 GB) and CABbed when using method 1 (±0.5 GB). When moving everything, it doesn't make a difference, when copying and then deleting, it obviously does.
read that log.
a turion mobile.
when you ran this, did you have it run on battery?
Mobile chips go slower on battery than when plugged into their powerconverter.
had early shift, and a meal, so I was drowsy when I first read all this...
and then I reread...
I have did a new installation of my windows with other 3 pc and the time is not much over 20 minutes...i think that is a problem of my notebook...thank you for all
muiz3 wrote:On some computers it takes a looooooong time , i can confirm that.
Indeed.
That is why you make all the effords to get it unattended anyway - so you can lean back and let it work, do something else, have a drink, take walk etc
Yeah right...
It never did , its something that happens since the finisher.
And i dont have the time to sit back and relax.
Some people have to work u know.
We not all as lazy as you are.
when finisher launches KTD process, the machine should already run the drive in enhanced mode (DMA etc), which is why I wonder what hardware your tests run on..
Strangely enough I have come across enough (older) machines that need to have DMA enabled manually after installation., which is quite annoying for any unattended installations obviously.
It's a laptop HDD, jtdoom
Quite normal, as it has to read and write simultaneously.
Using two drives on the same IDE channel gets you better reults since one drive only has to read while the other only has to write, however, since the IDE bus isn't full-duplex capable, it still cannot do both tasks at the same time.
Yeah right...
It never did , its something that happens since the finisher.
And i dont have the time to sit back and relax.
Some people have to work u know.
We not all as lazy as you are.
Woha, now that is completely uncalled for! 
I don't think personal attacks help solving the matter or bringing the discussion any further.
Besides, the point of an unattended instalation is that you, well, don't have to attend it.
In that regard it does not matter if it takes a bit longer or not, as you are supposed to do some other work in the meantime!
If you're doing this professionally, you probably have several systems to install on.
The overall time for one machine is negligible, since you can just start it on one machine, then move to the next, while it installs automatically.
I fail to see how this has anything to do with lazyness and if you conclude that my joke of "having a drink in the meantime" means I am lazy, then you completely misunderstood what I said...!
Get a sense of humour before coming back to me.
It wasn't offensive, muiz He was just joking (if you doubt that, see the smiley...).
Personal attacks are not tolerated at this forum. If you feel offended, please let that know the other person through mail, but don't start a flame here. This dispute is hereby ENDED.
Helmi is right when he says that the required time matters less when doing an unattended install, muiz is right when he says that it's taking too long. End of story.
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2009 PunBB.
[ Generated in 0.023 seconds, 11 queries executed ]