Comments on: XP Installation – The 34 minute hiccup http://techtracer.com/2007/03/12/xp-installation-the-34-minute-hiccup/ Tracing the course of Web Technology Sun, 13 May 2012 05:47:02 +0000 hourly 1 http://wordpress.org/?v=3.0.4 By: R81984 http://techtracer.com/2007/03/12/xp-installation-the-34-minute-hiccup/comment-page-9/#comment-41425 R81984 Mon, 30 Apr 2012 03:37:59 +0000 http://techtracer.com/2007/03/12/xp-installation-the-34-minute-hiccup/#comment-41425 Everyone left out one key function of the "pnplog.txt" You can add entries to the "pnplog.txt" file to exclude from trying to install. This way you dont have to delete anything. I ended up with 17 entries in the pnplog.txt but then it worked. My entries in "pnplog.txt" were like this: (lines added to signify start and end of text file, not really in the file) ----------------------------------- [EnumeratedDevices] Root\DNI_DNEMP016=Deterministic Network Enhancer Miniport ------------------------------------ I did that entry 17 times by counting the number down per entry 0016, 0015, ...., 0003, 0002, etc as every time I blocked it the next file was 1 number lower. You need to find what is being stuck, basically te the last few lines in the "setupapi.log" file and fit it into this syntax. The "pnplog.txt" is the access list to bypass hardware for installation. It would be nice if they just had a prompt for items that "timeout" asking if you want skip that piece of hardware. What moron programmers. Everyone left out one key function of the “pnplog.txt”
You can add entries to the “pnplog.txt” file to exclude from trying to install.
This way you dont have to delete anything.
I ended up with 17 entries in the pnplog.txt but then it worked.
My entries in “pnplog.txt” were like this: (lines added to signify start and end of text file, not really in the file)
———————————–
[EnumeratedDevices]
Root\DNI_DNEMP016=Deterministic Network Enhancer Miniport
————————————
I did that entry 17 times by counting the number down per entry 0016, 0015, …., 0003, 0002, etc as every time I blocked it the next file was 1 number lower.

You need to find what is being stuck, basically te the last few lines in the “setupapi.log” file and fit it into this syntax.

The “pnplog.txt” is the access list to bypass hardware for installation. It would be nice if they just had a prompt for items that “timeout” asking if you want skip that piece of hardware. What moron programmers.

]]> By: Bob http://techtracer.com/2007/03/12/xp-installation-the-34-minute-hiccup/comment-page-9/#comment-41370 Bob Sat, 24 Mar 2012 04:36:33 +0000 http://techtracer.com/2007/03/12/xp-installation-the-34-minute-hiccup/#comment-41370 @moltres rider: The original instructions do work but they assume you know how to navigate in DOS. I will try to clarify for you: # goto C:/Windows and type setupapi.log, hit enter To do that, you type "cd Windows" it should look like: C:\> cd Windows C:\Windows> setupapi.log ... # Close the notepad and go to the folder C:/windows/inf in command prompt To "go to the folder" you use the cd command again. It should look like this: C:\Windows> setupapi.log (this is still there from before) C:\Windows> cd inf C:\Windows\inf> # Browse through the files to find the “.inf” which was related to the faulty device. To do this, use the dir command: C:\Windows\inf> dir # Straightaway delete the inf file (eg: del mdmcxpt.inf) C:\Windows\inf> del mdmcxpt.inf (for example) I covered the other DOS commands you'll need a few posts back. Good luck! @moltres rider: The original instructions do work but they assume you know how to navigate in DOS. I will try to clarify for you:

# goto C:/Windows and type setupapi.log, hit enter

To do that, you type “cd Windows” it should look like:
C:\> cd Windows
C:\Windows> setupapi.log
…

# Close the notepad and go to the folder C:/windows/inf in command prompt

To “go to the folder” you use the cd command again. It should look like this:

C:\Windows> setupapi.log (this is still there from before)
C:\Windows> cd inf
C:\Windows\inf>

# Browse through the files to find the “.inf” which was related to the faulty device.

To do this, use the dir command:

C:\Windows\inf> dir

# Straightaway delete the inf file (eg: del mdmcxpt.inf)

C:\Windows\inf> del mdmcxpt.inf (for example)

I covered the other DOS commands you’ll need a few posts back. Good luck!

]]> By: moltres rider http://techtracer.com/2007/03/12/xp-installation-the-34-minute-hiccup/comment-page-9/#comment-41367 moltres rider Fri, 23 Mar 2012 21:44:32 +0000 http://techtracer.com/2007/03/12/xp-installation-the-34-minute-hiccup/#comment-41367 you all are LYING!!! THIS DOES NOT WORK!!!!!!!!!!!!!! THE DIRECTORY COMMANDS DO NOT WORK!!!!! you all are LYING!!! THIS DOES NOT WORK!!!!!!!!!!!!!! THE DIRECTORY COMMANDS DO NOT WORK!!!!!

]]> By: moltres rider http://techtracer.com/2007/03/12/xp-installation-the-34-minute-hiccup/comment-page-9/#comment-41366 moltres rider Fri, 23 Mar 2012 21:41:33 +0000 http://techtracer.com/2007/03/12/xp-installation-the-34-minute-hiccup/#comment-41366 this DOES NOT work!!! when I put the directory specified in the command prompt it errors out as CWINDOWSinf is not recognized as an internal or external command, operable program or batch file it ALWAYS error out to that!!!!!!!!!! this DOES NOT work!!! when I put the directory specified in the command prompt it errors out as CWINDOWSinf is not recognized as an internal or external command, operable program or batch file

it ALWAYS error out to that!!!!!!!!!!

]]> By: WDK http://techtracer.com/2007/03/12/xp-installation-the-34-minute-hiccup/comment-page-9/#comment-41348 WDK Fri, 16 Mar 2012 17:38:09 +0000 http://techtracer.com/2007/03/12/xp-installation-the-34-minute-hiccup/#comment-41348 Yes, what a terrific post. The best I've ever seen! I was very skeptical at first, however, I decided to give it a try. My system was originall stuck on the welcome screen, so I tried to run the XP repair to correct the problem. I then was getting stuck on the 39th minute. I followed the instructions outlined by Nitinpai. I ran the repair again and it worked! Honestly, I still don't believe it. Thanks again Yes, what a terrific post. The best I've ever seen! I was very skeptical at first, however, I decided to give it a try. My system was originall stuck on the welcome screen, so I tried to run the XP repair to correct the problem. I then was getting stuck on the 39th minute. I followed the instructions outlined by Nitinpai. I ran the repair again and it worked! Honestly, I still don't believe it. Thanks again Nitinpai, I can't express how grateful I am, you deserve a metal! WDK, I can't express how grateful I am. WDK Yes, what a terrific post. The best I’ve ever seen!

I was very skeptical at first, however, I decided to give it a try. My system was originall stuck on the welcome screen, so I tried to run the XP repair to correct the problem.

I then was getting stuck on the 39th minute. I followed
the instructions outlined by Nitinpai. I ran the repair again and it worked! Honestly, I still don’t believe it.

Thanks again Yes, what a terrific post. The best I’ve ever seen!

I was very skeptical at first, however, I decided to give it a try. My system was originall stuck on the welcome screen, so I tried to run the XP repair to correct the problem.

I then was getting stuck on the 39th minute. I followed
the instructions outlined by Nitinpai. I ran the repair again and it worked! Honestly, I still don’t believe it.

Thanks again Nitinpai, I can’t express how grateful I am, you deserve a metal!

WDK, I can’t express how grateful I am.

WDK

]]> By: Solid Backup http://techtracer.com/2007/03/12/xp-installation-the-34-minute-hiccup/comment-page-9/#comment-41344 Solid Backup Tue, 13 Mar 2012 13:21:00 +0000 http://techtracer.com/2007/03/12/xp-installation-the-34-minute-hiccup/#comment-41344 I am surprised that this is still happening. This was similar to the situation I was in prior to repairing my Windows install. I searched for blue screen loading xp in google to find articles that gave a list of steps (this is because a blue screen flashes by before restarting). I couldnt even get safe mode going so I had a different fix, but the following seems to be a good fix from safe mode: http://www.pcstats.com/articleview.cfm?articleid=1647&page=4 I am surprised that this is still happening. This was similar to the situation I was in prior to repairing my Windows install. I searched for blue screen loading xp in google to find articles that gave a list of steps (this is because a blue screen flashes by before restarting). I couldnt even get safe mode going so I had a different fix, but the following seems to be a good fix from safe mode: http://www.pcstats.com/articleview.cfm?articleid=1647&page=4

]]> By: aek http://techtracer.com/2007/03/12/xp-installation-the-34-minute-hiccup/comment-page-9/#comment-41302 aek Sun, 19 Feb 2012 13:49:59 +0000 http://techtracer.com/2007/03/12/xp-installation-the-34-minute-hiccup/#comment-41302 its work, thanks so much! its work, thanks so much!

]]> By: Matthew http://techtracer.com/2007/03/12/xp-installation-the-34-minute-hiccup/comment-page-9/#comment-41275 Matthew Sat, 14 Jan 2012 20:02:51 +0000 http://techtracer.com/2007/03/12/xp-installation-the-34-minute-hiccup/#comment-41275 I had this same problem this past week when trying to install Windows 2003 R2, SP2, x64 Enterprise on a Dell PE 905. This server had been in production since 2009 running W2K3 Ent w/ MSSQL with no problems when we decided to re-purpose with a clean build to assist in migrating all of our MSSQL clusters to W2K8R2. Given the server had a PERC 6/i controller, I used the Dell Build & Install CD given the 2003 media didn't include these drivers natively. Although the Linux-based GUI loaded, the system would freeze (no mouse/keyboard input) at various points throughout the setup. I tried everything under the sun from different CDs, different CD/DVD drive hardware, creating various Virtual Disk configurations using different drive selections and RAID levels, using USB Boot media, removing all Fibre Channel and PCI NICs, removing and trying various memory configs (it has 256GB RAM). Still being under warranty, I called Dell for assistance. Working with the first tech, I tried creating a boot CD with 2003 source files to include the PERC 6/i drivers using nLite. It was during this install attempt that I experienced the 34 minute hiccup. Actually my screen would freeze at 33 minutes with loss of mouse and keyboard on the Regional and Language settings menu. Working with a second tech the next day, within 15 minutes of the call, he found this post stating, "This is similar and appears to happen mainly to XP, but let's give it a shot". In my case, when I opened the .inf log, the last entry was a wave.inf that installed successfully. However, as I worked my way up the log, I eventually found were "msports.inf" had failed. I navigated to the inf directory and via command line renamed this file to msports.zip. Rebooting and reinserting the 2003 boot CD media, it worked...successful install! I had this same problem this past week when trying to install Windows 2003 R2, SP2, x64 Enterprise on a Dell PE 905. This server had been in production since 2009 running W2K3 Ent w/ MSSQL with no problems when we decided to re-purpose with a clean build to assist in migrating all of our MSSQL clusters to W2K8R2. Given the server had a PERC 6/i controller, I used the Dell Build & Install CD given the 2003 media didn’t include these drivers natively. Although the Linux-based GUI loaded, the system would freeze (no mouse/keyboard input) at various points throughout the setup. I tried everything under the sun from different CDs, different CD/DVD drive hardware, creating various Virtual Disk configurations using different drive selections and RAID levels, using USB Boot media, removing all Fibre Channel and PCI NICs, removing and trying various memory configs (it has 256GB RAM).

Still being under warranty, I called Dell for assistance. Working with the first tech, I tried creating a boot CD with 2003 source files to include the PERC 6/i drivers using nLite. It was during this install attempt that I experienced the 34 minute hiccup. Actually my screen would freeze at 33 minutes with loss of mouse and keyboard on the Regional and Language settings menu. Working with a second tech the next day, within 15 minutes of the call, he found this post stating, “This is similar and appears to happen mainly to XP, but let’s give it a shot”.

In my case, when I opened the .inf log, the last entry was a wave.inf that installed successfully. However, as I worked my way up the log, I eventually found were “msports.inf” had failed. I navigated to the inf directory and via command line renamed this file to msports.zip. Rebooting and reinserting the 2003 boot CD media, it worked…successful install!

]]> By: Bob http://techtracer.com/2007/03/12/xp-installation-the-34-minute-hiccup/comment-page-9/#comment-41262 Bob Sun, 08 Jan 2012 04:02:07 +0000 http://techtracer.com/2007/03/12/xp-installation-the-34-minute-hiccup/#comment-41262 The restore console puts you at the DOS prompt, Joe. Whenever you see "C:>" (or anything else that ends in a greater-than sign) on a Windows machine, you are at the DOS prompt. The restore console puts you at the DOS prompt, Joe. Whenever you see “C:>” (or anything else that ends in a greater-than sign) on a Windows machine, you are at the DOS prompt.

]]> By: joe http://techtracer.com/2007/03/12/xp-installation-the-34-minute-hiccup/comment-page-9/#comment-41261 joe Sun, 08 Jan 2012 02:35:23 +0000 http://techtracer.com/2007/03/12/xp-installation-the-34-minute-hiccup/#comment-41261 how do you get into DOS prompt? my computer says nothing about that when i boot it how do you get into DOS prompt? my computer says nothing about that when i boot it

]]>