Op System stops installing at about 34 minutes to finish XP and Vista

[wazza300]

does your xp disc have sp3? i cant think whatelse you could try

[waga]

does your xp disc have sp3? i cant think whatelse you could try

Thanks wazza300 and Conners for your help.

I have a copy of XP Pro SP3 which gives the same result as XP Pro SP2 and XP Home SP1 and also Vista (I think SP1) - remember that Me (2000) installs fully as I understand that that OS does not check devices on install.

I have also now tried to leave it sit there when it stalls (for 4 hours) and retried a few times later-on by just hitting reset and not formatting etc. to see if it helped - but same result as doing a full format etc.

In my previous post I asked about "SetUpapi.log files" (M/Soft kb828267) and have been checking it more - it seems that stalling near 34 minutes to finish is a common issue but I do not understand Microsoft's solutions yet. Maybe I should try their Support site as it may be a software issue more than a Gigabyte motherboard or BIOS issue.

If anyone has any answers to the other questions in the previous post I would appreciate any comments.

If I do get this problem fixed I will post the information - but it seems like it might be a long while.

Thanks again for everyone's help.

Regards
Waga

[Conners]

Try installing without sound card and or nic card if you have one. Whats in the setuperr.log? Might be the os disk it's self. Can you try it in another sysrem to see if it works?

[waga]

Try installing without sound card and or nic card if you have one. Whats in the setuperr.log? Might be the os disk it's self. Can you try it in another sysrem to see if it works?

Thank you Conners for your reply,

I have not been using a sound card, the NIC (network interface controller) which I understand is the LAN/ethernet connection, is on the motherboard.

I have tested out the OS CD by installing on another PC and it works fine.

I have attached part of the setupapi.log file which I think shows a missing digital signature verification at the beginning and again at the end of the log file.

I do not know how to find or use the the setuperr.log file. If I try by using Shift+F10 after "setup is being restarted" and typing "setuperr.log" I get a message "The process cannot access the file because it is being used by another process".

Thanks again for your help Waga

[SetupAPI Log]
OS Version = 5.1.2600 Service Pack 3
Platform ID = 2 (NT)
Service Pack = 3.0
Suite = 0x0000
Product Type = 1
Architecture = x86
[2012/06/30 08:55:15 296.1]
#-199 Executing "C:\WINDOWS\system32\setup.exe" with command line: setup -newsetup
#-290 Processing REGISTERDLLS section [CryptoDlls]. Binary: "%11%\rsaenh.dll", flags: 0x0001, timeout: 60s.
#W374 Digital signature verification was skipped for a file being registered ("C:\WINDOWS\system32\rsaenh.dll").
#-290 Processing REGISTERDLLS section [CryptoDlls]. Binary: "%11%\dssenh.dll", flags: 0x0001, timeout: 60s.
#W374 Digital signature verification was skipped for a file being registered ("C:\WINDOWS\system32\dssenh.dll").
#-290 Processing REGISTERDLLS section [CryptoDlls]. Binary: "%11%\initpki.dll", flags: 0x0001, timeout: 600s.
#W374 Digital signature verification was skipped for a file being registered ("C:\WINDOWS\system32\initpki.dll").
[2012/06/30 08:56:19 296.10]
#-199 Executing "C:\WINDOWS\system32\setup.exe" with command line: setup -newsetup
#I140 Installing device class: "1394" {6BDD1FC1-810F-11D0-BEC7-08002BE2092F}.
#I141 Class install completed with no errors.
[2012/06/30 08:56:19 296.12]
#-199 Executing "C:\WINDOWS\system32\setup.exe" with command line: setup -newsetup
#I140 Installing device class: "1394Debug" {66f250d6-7801-4a64-b139-eea80a450b24}.
#I141 Class install completed with no errors.
[2012/06/30 08:56:20 296.13]
#-199 Executing "C:\WINDOWS\system32\setup.exe" with command line: setup -newsetup
#I140 Installing device class: "61883" {7EBEFBC0-3200-11d2-B4C2-00A0C9697D07}.
#I141 Class install completed with no errors.
[2012/06/30 08:56:20 296.14]
#-199 Executing "C:\WINDOWS\system32\setup.exe" with command line: setup -newsetup
#I140 Installing device class: "Avc" {C06FF265-AE09-48f0-812C-16753D7CBA83}.
#I141 Class install completed with no errors.
[2012/06/30 08:56:20 296.15]
#-199 Executing "C:\WINDOWS\system32\setup.exe" with command line: setup -newsetup
#I140 Installing device class: "Battery" {72631e54-78a4-11d0-bcf7-00aa00b7b32a}.
#I141 Class install completed with no errors.
[2012/06/30 08:56:20 296.17]
#-199 Executing "C:\WINDOWS\system32\setup.exe" with command line: setup -newsetup
#I140 Installing device class: "Bluetooth" {e0cbf06c-cd8b-4647-bb8a-263b43f0f974}.
#I141 Class install completed with no errors.
[2012/06/30 08:56:21 296.19]
#-199 Executing "C:\WINDOWS\system32\setup.exe" with command line: setup -newsetup
#I140 Installing device class: "CDROM" {4D36E965-E325-11CE-BFC1-08002BE10318}.
#I141 Class install completed with no errors.
[2012/06/30 08:56:21 296.21]
#-199 Executing "C:\WINDOWS\system32\setup.exe" with command line: setup -newsetup
#I140 Installing device class: "Processor" {50127DC3-0F36-415e-A6CC-4CB3BE910B65}.
#I141 Class install completed with no errors.
[2012/06/30 08:56:21 296.22]
#-199 Executing "C:\WINDOWS\system32\setup.exe" with command line: setup -newsetup
#I140 Installing device class: "Enum1394" {C459DF55-DB08-11d1-B009-00A0C9081FF6}.
#I141 Class install completed with no errors.
[2012/06/30 08:56:21 296.23]
#-199 Executing "C:\WINDOWS\system32\setup.exe" with command line: setup -newsetup
#I140 Installing device class: "MTD" {4D36E970-E325-11CE-BFC1-0

END OF 1ST PAGE

START OF LAST PAGE
#I022 Found "PCI\CC_0C0300" in C:\WINDOWS\inf\usbport.inf; Device: "Standard Universal PCI to USB Host Controller"; Driver: "Standard Universal PCI to USB Host Controller"; Provider: "Microsoft"; Mfg: "(Standard USB Host Controller)"; Section name: "UHCI.Dev".
#I023 Actual install section: [UHCI.Dev.NT]. Rank: 0x00002005. Effective driver date: 07/01/2001.
#I022 Found "PCI\VEN_8086&DEV_24D7" in C:\WINDOWS\inf\usbport.inf; Device: "Intel(R) 82801EB USB Universal Host Controller - 24D7"; Driver: "Intel(R) 82801EB USB Universal Host Controller - 24D7"; Provider: "Microsoft"; Mfg: "Intel"; Section name: "UHCI.Dev".
#I023 Actual install section: [UHCI.Dev.NT]. Rank: 0x00002001. Effective driver date: 07/01/2001.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [UHCI.Dev] in "c:\windows\inf\usbport.inf".
#I320 Class GUID of device remains: {36FC9E60-C465-11CF-8056-444553540000}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-124 Doing copy-only install of "PCI\VEN_8086&DEV_24D7&SUBSYS_24D21458&REV_02\3&13C0B0C5&0&EA".
#-166 Device install function: DIF_INSTALLDEVICEFILES.
#W383 "LAYOUT.PNF" migrate: PNF Language = 0409, Thread = 0809.
#-011 Installing section [UHCI.Dev.NT] from "c:\windows\inf\usbport.inf".
#W383 "LAYOUT.PNF" migrate: PNF Language = 0409, Thread = 0809.
#-340 Extracted file "usbport.sys" from cabinet "C:\WINDOWS\Driver Cache\i386\driver.cab" to "C:\WINDOWS\system32\drivers\SET2BC.tmp" (target is "C:\WINDOWS\system32\drivers\usbport.sys").
#-024 Copying file "C:\WINDOWS\system32\drivers\SET2BC.tmp" to "C:\WINDOWS\system32\drivers\usbport.sys".
#E360 An unsigned or incorrectly signed file "C:\WINDOWS\system32\drivers\SET2BC.tmp" for driver "Intel(R) 82801EB USB Universal Host Controller - 24D7" will be installed (Policy=Ignore). Error 0x800b0100: No signature was present in the subject.
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [UHCI.Dev.NT.Interfaces] from "c:\windows\inf\usbport.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of "PCI\VEN_8086&DEV_24D7&SUBSYS_24D21458&REV_02\3&13C0B0C5&0&EA".
#I121 Device install of "PCI\VEN_8086&DEV_24D7&SUBSYS_24D21458&REV_02\3&13C0B0C5&0&EA" finished successfully.
[2012/07/01 07:46:57 296.1091 Driver Install]
#-019 Searching for hardware ID(s): pci\ven_8086&dev_24d5&subsys_a0021458&rev_02,pci\ven_8086&dev_24d5&subsys_a0021458,pci\ven_8086&dev_24d5&cc_040100,pci\ven_8086&dev_24d5&cc_0401
#-018 Searching for compatible ID(s): pci\ven_8086&dev_24d5&rev_02,pci\ven_8086&dev_24d5,pci\ven_8086&cc_040100,pci\ven_8086&cc_0401,pci\ven_8086,pci\cc_040100,pci\cc_0401
#-199 Executing "C:\WINDOWS\system32\setup.exe" with command line: setup -newsetup
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#W059 Selecting best compatible driver failed. Error 0xe0000228: There are no compatible drivers for this device.
#W157 Default installer failed. Error 0xe0000228: There are no compatible drivers for this device.
#I060 Set selected driver.
#-166 Device install function: DIF_INSTALLDEVICE.
#I125 Installing NULL driver for "PCI\VEN_8086&DEV_24D5&SUBSYS_A0021458&REV_02\3&13C0B0C5&0&FD".
#E122 Device install failed. Error 0xe0000219: The installation failed because a function driver was not specified for this device instance.
#E157 Default installer failed. Error 0xe0000219: The installation failed because a function driver was not specified for this device instance.
#-166 Device install function: DIF_INSTALLDEVICE.
#I125 Installing NULL driver for "PCI\VEN_8086&DEV_24D5&SUBSYS_A0021458&REV_02\3&13C0B0C5&0&FD".
#I121 Device install of "PCI\VEN_8086&DEV_24D5&SUBSYS_A0021458&REV_02\3&13C0B0C5&0&FD" finished successfully.
[2012/07/01 07:46:58 296.1093 Driver Install]
#-019 Searching for hardware ID(s): pci\ven_8086&dev_24d4&subsys_24d21458&rev_02,pci\ven_8086&dev_24d4&subsys_24d21458,pci\ven_8086&dev_24d4&cc_0c0300,pci\ven_8086&dev_24d4&cc_0c03
#-018 Searching for compatible ID(s): pci\ven_8086&dev_24d4&rev_02,pci\ven_8086&dev_24d4,pci\ven_8086&cc_0c0300,pci\ven_8086&cc_0c03,pci\ven_8086,pci\cc_0c0300,pci\cc_0c03
#-199 Executing "C:\WINDOWS\system32\setup.exe" with command line: setup -newsetup
#I022 Found "PCI\CC_0C0300" in C:\WINDOWS\inf\usbport.inf; Device: "Standard Universal PCI to USB Host Controller"; Driver: "Standard Universal PCI to USB Host Controller"; Provider: "Microsoft"; Mfg: "(Standard USB Host Controller)"; Section name: "UHCI.Dev".
#I023 Actual install section: [UHCI.Dev.NT]. Rank: 0x00002005. Effective driver date: 07/01/2001.
#I022 Found "PCI\VEN_8086&DEV_24D4" in C:\WINDOWS\inf\usbport.inf; Device: "Intel(R) 82801EB USB Universal Host Controller - 24D4"; Driver: "Intel(R) 82801EB USB Universal Host Controller - 24D4"; Provider: "Microsoft"; Mfg: "Intel"; Section name: "UHCI.Dev".
#I023 Actual install section: [UHCI.Dev.NT]. Rank: 0x00002001. Effective driver date: 07/01/2001.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [UHCI.Dev] in "c:\windows\inf\usbport.inf".
#I320 Class GUID of device remains: {36FC9E60-C465-11CF-8056-444553540000}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-124 Doing copy-only install of "PCI\VEN_8086&DEV_24D4&SUBSYS_24D21458&REV_02\3&13C0B0C5&0&E9".
#-166 Device install function: DIF_INSTALLDEVICEFILES.
#W383 "LAYOUT.PNF" migrate: PNF Language = 0409, Thread = 0809.
#-011 Installing section [UHCI.Dev.NT] from "c:\windows\inf\usbport.inf".
[2012/07/01 08:07:24 296.1]
#-199 Executing "C:\WINDOWS\system32\setup.exe" with command line: setup -newsetup
#W383 "syssetup.PNF" migrate: PNF Language = 0809, Thread = 0409.
#-290 Processing REGISTERDLLS section [CryptoDlls]. Binary: "%11%\rsaenh.dll", flags: 0x0001, timeout: 60s.
#W374 Digital signature verification was skipped for a file being registered ("C:\WINDOWS\system32\rsaenh.dll").
#-290 Processing REGISTERDLLS section [CryptoDlls]. Binary: "%11%\dssenh.dll", flags: 0x0001, timeout: 60s.
#W374 Digital signature verification was skipped for a file being registered ("C:\WINDOWS\system32\dssenh.dll").
#-290 Processing REGISTERDLLS section [CryptoDlls]. Binary: "%11%\initpki.dll", flags: 0x0001, timeout: 600s.
#W374 Digital signature verification was skipped for a file being registered ("C:\WINDOWS\system32\initpki.dll").

[Conners]

Waga heres wot I would try. Download parted magic from here: start Burn the ISO to a cd and boot.
When in parted magic go to system tools and Click on erase disk. A screen will pop up then select internal secure erase command and click continue. Another screen will pop up and select your disk. (should be the only one). Then click ok. Another screen will pop up asking for a password, just leave null and click ok. A few more screen with warnings will pop up just acknowledge those and continue. This will take a while to complete. when done tryingtalling the OS. If it hangs again restart the ststem but don't do anything it should resume where the error occured. If it errors again reboot and do nothing as previously stated. In other words when you reboot DO TO HIT ANY KEY TO BOOT FORM CD. if you do the installation will start all over again.

[waga]

[QUOTE=Conners;431214]Waga heres wot I would try. Download parted magic from here: start Burn the ISO to a cd and boot.
When in parted magic go to system tools and Click on erase disk. etc........

Hi Conners and thanks again for your help,

I have tried to use Parted Magic as suggested but it will not fully install - stops at line: [1.586634] write etc.....

I have tried from 256MB of Ram to 1GB and options to use the Live CD, etc - all won't install.


On another PC it fully installs and the system tools is in accessories etc....

ON THE OTHER LINE OF THOUGHT:

I have just noticed that the last few lines of the setupapi.log file are the same as the first few lines. I will attach them for information:

#W374 Digital signature verification was skipped for a file being registered ("C:\WINDOWS\system32\initpki.dll").



Hopefully this may help to sort out the problem.



Also can you or anyone help me to get setuperr.log etc. When I type it in at the C:\WINDOWS\system32\ cmd.exe box and line C:\WINDOWS\system32> prompt I get a message that the" process cannot access the file because it is being used by another process". But I can get the setupapi.log from the same prompt.






[SetupAPI Log]
OS Version = 5.1.2600 Service Pack 3
Platform ID = 2 (NT)
Service Pack = 3.0
Suite = 0x0000
Product Type = 1
Architecture = x86
[2012/06/30 08:55:15 296.1]
#-199 Executing "C:\WINDOWS\system32\setup.exe" with command line: setup -newsetup
#-290 Processing REGISTERDLLS section [CryptoDlls]. Binary: "%11%\rsaenh.dll", flags: 0x0001, timeout: 60s.
#W374 Digital signature verification was skipped for a file being registered ("C:\WINDOWS\system32\rsaenh.dll").
#-290 Processing REGISTERDLLS section [CryptoDlls]. Binary: "%11%\dssenh.dll", flags: 0x0001, timeout: 60s.
#W374 Digital signature verification was skipped for a file being registered ("C:\WINDOWS\system32\dssenh.dll").
#-290 Processing REGISTERDLLS section [CryptoDlls]. Binary: "%11%\initpki.dll", flags: 0x0001, timeout: 600s.
#W374 Digital signature verification was skipped for a file being registered ("C:\WINDOWS\system32\initpki.dll").
[2012/06/30 08:56:19 296.10]
#-199 Executing "C:\WINDOWS\system32\setup.exe" with command line: setup -newsetup

etc.....

and the last lines:



[2012/07/01 08:07:24 296.1]
#-199 Executing "C:\WINDOWS\system32\setup.exe" with command line: setup -newsetup
#W383 "syssetup.PNF" migrate: PNF Language = 0809, Thread = 0409.
#-290 Processing REGISTERDLLS section [CryptoDlls]. Binary: "%11%\rsaenh.dll", flags: 0x0001, timeout: 60s.
#W374 Digital signature verification was skipped for a file being registered ("C:\WINDOWS\system32\rsaenh.dll").
#-290 Processing REGISTERDLLS section [CryptoDlls]. Binary: "%11%\dssenh.dll", flags: 0x0001, timeout: 60s.
#W374 Digital signature verification was skipped for a file being registered ("C:\WINDOWS\system32\dssenh.dll").
#-290 Processing REGISTERDLLS section [CryptoDlls]. Binary: "%11%\initpki.dll", flags: 0x0001, timeout: 600s.
#W374 Digital signature verification was skipped for a file being registered ("C:\WINDOWS\system32\initpki.dll").

[Conners]

I for got to say one thing it may or may not matter. Run the program from RAM ot load it to Ram. whatever it says...

[waga]

I for got to say one thing it may or may not matter. Run the program from RAM ot load it to Ram. whatever it says...

Thanks Conners for your interest,

Yes I had tried the 3 options to install, including Run on Ram - with varying amounts of Ram.

The install of Parted Magic stops at different lines including once at "unable to open rtcdevice".

I have also tied to install UBUNTU 2012 but it also will not go very far and stops at different lines e.g. "configure keyboard".

The UBUNTU OS installs on the practice PC I use.

Have you or anyone else any thoughts on the setupapi.log file I mentioned in previous posts.

Also how would I get into setuperr.log - when I try the same as setupapi.log the reply is "the process is being used by another....etc".

Thanks for all the help

Regards

Waga

[Conners]

Only thing else I would know too try is put the hd in your other system and use parted magic that way. the setuperr log may noy be generated for view until the sysyem is installed. What format did you use on the HD? Fat Fat 32 ot NTSF? Please use NTSF although XP can be instslled on Fat32. Oh one other thing you might try on that old computer is an older version of parted magic.

[waga]

Only thing else I would know too try is put the hd in your other system and use parted magic that way. the setuperr log may noy be generated for view until the sysyem is installed. What format did you use on the HD? Fat Fat 32 ot NTSF? Please use NTSF although XP can be instslled on Fat32. Oh one other thing you might try on that old computer is an older version of parted magic.

Hi Conners and thanks for your help,

No luck as yet.

I have put the HDD in the old PC and erased the disk using Parted Magic, then reinstalled and tried to install the OS but same result. Also it has been restarted about 30 times without hitting the "hit any key...etc." also I have left it on for about 8 hours to see if it changed.

I agree that setuperr.log is not available at this stage.

I have used NTFS all the time when formatting and done full formats.

There is no need to use an older version of Parted Magic as the current one works fine on the old PC.

Conners do you think anyone else may know about interpreting the setupapi.log (digital signature missing issue) I generated in an earlier post and if so how we could get to ask them? I have tried to find this thread without using the direct link and I can't find it, maybe it is not obvious to others as well - or maybe I am looking in the wrong place.

I certainly appreciate your help, but I guess we may have come to the end at this stage.

Regards

Wagga