On May 17, 11:02 pm, "Pegasus \(MVP\)" <I....@fly.com.oz> wrote:
> "TomYoung" <tgyo...@yahoo.com> wrote in message
>
> news:286e8a6d-4c7d-478d-9ec4-(E-Mail Removed)...
>
>
>
> > On May 17, 1:12 pm, "Pegasus \(MVP\)" <I....@fly.com.oz> wrote:
> >> "TomYoung" <tgyo...@yahoo.com> wrote in message
>
> >>news:e7a862e1-f86f-4a6a-9069-(E-Mail Removed)...
>
> >> > Hi all:
>
> >> > Trying to do a fresh install on an older Thinkpad Laptop. It's a IBM
> >> > Thinkpad 2647-AMU with the following specs: PIII 700MHz (256KB), 256MB
> >> > RAM, 12.0GB HDD, 14.1 TFT 1024x768 LCD, 6x-2.3x DVD drive, 3Com combo
>
> >> > Setup hangs with either 35 or 34 minutes to go. It's got to be some
> >> > hardware issue and I was just wondering if anybody knew offhand what
> >> > it is.
>
> >> > Thanks
>
> >> > Tom Young
>
> >> Have a look here:
> >> WinXP Setup stops responding with 34 minutes
> >> remaining:http://support.microsoft.com/default...b;en-us;828267
>
> > I've looked at the Help and Support page but, once I restart the
> > computer doesn't the install program start fresh .txt and .log files?
> > How do you get the install program to load windows enough to open the
> > command prompt without the program running off and re-writing what
> > you're trying to look at?
>
> > Tom Young
>
> The page I quoted requires you to restart the installation process several
> times. Apparently the process skips certain devices each time it gets
> restarted. The page also says to press Shift+F10 after the first restart,
> which apparently opens a Command Prompt so that you can examine
> pnplog.txt. If you are unable to do this then you could boot the machine
> with a Win98 boot disk fromwww.bootdisk.comand run ntfsdos.exe
> fromwww.sysinternals.comso that you can examine pnplog.txt even
> if it resides on an NTFS partition.
I've rebooted dozens of times and haven't made any progress. By
ejecting the Windows CD I can "stall" the install program and look at
the hard drive. There *is* no pnplog.txt on the drive, thought
there's a setuplog.txt file which doesn't show any obvious errors.
I've also view the setupapi.log file that shows all sorts errors,
variations of "#E077 Could not locate a non-empty section
[iis_common_install] when calculating disk space in 'C:\WINDOWS\INF
\iis.inf'. Error 0xe0000102: The required line was not found in the
INF."
All too much for me.
Thanks.
Tom Young