Windows re-install copy problem

[Guest]

Hi!

I have been facing this problem so many times, and now once again! ... so,
now I decided to write some story on this to these forums.

When trying to do a Win2000 or WinXP re-install onto an existing system, I
have been facing many times problems on copying certain files from the
original or slipstreamed and/or copied install-CDs. Most of the times the
copying has been failing on some 100 files, but sometimes just on some 2-5
files.

The basic corrective action, found on the net to overcome this problem, is
to try with other install-CDs, other CD-devices, checking the
IDE-cables/jumpers etc. etc., but these has been proving not to help at all
....

The more expertise advice has been ripping off for the re-install procedure
all unnecessary components from the machine, incl. PCI-cards, USB-devices
etc., and disabling the onboard audio, USB etc. devices, and, also removing
any suspectable memory modules. This last hint mainly points to non-paired
modules, but also to the need for thorough module testing by Memtest86 or
some other test program to see if there is even a slight problem on any
paired or single modules. If none of the above hints would help, it's said
that the problem is probably residing somewhere on the mobo ... uuuu-uuh,
where there ... And, noting also that all this is not so easy to apply to a
laptop ...

OK, sometimes I have been lucky enough to get the re-install done despite of
these copy problems just ignoring them, but sometimes it has proven
impossible to get the re-installed system in good enough shape running up.

This last case of mine was a WinXPPro re-install trial with the original SP1
install-CD on a ripped-off AMD/1133MHz desktop/floor machine. With two
non-paired 256MB memory-modules there were appearing copy problems on some
100 files, but after trying with a tested single good 256MB module the
copying did fail only on 3 files, migregdb.ex_, icwconn1.ex_ and phone.ic_.

After some 2-3 trial rounds, some 2 hours each, always facing the same 3
copy problems, both from CD and a hard disk copy of it, ignoring them and
continuing, and getting WinXP up and running, but limping, even after SP2
upgrade, I decided to make a fresh clean install instead ...

This clean install with SP2 upgrade, some 100 updates, user folder/file
transfers from back-ups, some 20 software installs, desktop etc.
re-organizings, system optimizings a.s.o., I did get the system up, OK, new
born and virgin, during some 3-4 days with some 15 hours work ...

OK, OK, maybe it's good to get this work, and the cleaning included, done
forced once in two years or so ...

But, my questions are
- why this problem is arising/existing at all?
- why can't it be overcome, or totally eliminated by MS?

The re-install procedure should of course be all fluent any time on any
machine! The need of it may arise anytime even for a quite fresh machine,
from a virus attack or unlucky install/support task or erroneous user
handling etc.


Best regards,

Pete V.

 

[Guest]

Your copy problems are probably caused by the CD drive's driver. I would try
running setup from a copy of the i386 folder that had been copied to the hard
drive from the CD, (eliminating the cd driver issue by not using the cd
during the setup copy phase.)

 

[Guest]

Hi!

Thanks Mark for your reply.

OK, after some trial round I did copy the install-CD in full to the
re-install hard drive, with Windows Explorer under another WinXP system with
no problems at all, and begun a new re-install trial regularly from the
install-CD.

Everything went OK and smoothly until the copying phase at the point 28
minutes left when the migregdb.ex_ was in turn to be copied from the
install-CD, but it did fail. Then I browsed to the hard disk \i386 folder
and opened the file from there and got one step ahead, now the unpacked
migregdb.exe was noted to be failing ...

Then I continued ignoring this copy failing and got once again smoothly a
few minutes to the point 18 minutes left when the icwconn1.ex_ was in turn to
be copied and just the same steps as above were happening and done with this
one.

Then I continued ignoring also this copy failing and got once again smoothly
a few seconds until the phone.ic_ was in turn to be copied, but this copying
wasn't successfull not even from the hard disk \i386.

Once again I continued ignoring also this copy failing and got now smoothly
to the end of the re-install procedure.

Anyway, as this re-installed system seemed not to be feeling so well, I
didn't go on with this re-install anymore after the SP2 upgrade. Sorry, I
couldn't get any evidence, if this limping problem was due to the copy
failings or some other things inside the old system needing this re-install
to be done.

So, there is something strange involved in all this copying problem, which
should be on MS's interest to be investigated and cured somehow. One idea
for a solution is to produce some kind of test program, which would
investigate the system hardware and pinpoint the real problem point when this
type of problem situation is faced. It's too hard work for support people to
do case by case such thorough troubleshooting component by component, as the
problem may be residing/hiding even on some unreachable/untouchable component
on the mobo ...


Best regards,

Pete V.

 

[Poprivet]

Hi!

I have been facing this problem so many times, and now once again!
... so, now I decided to write some story on this to these forums.

When trying to do a Win2000 or WinXP re-install onto an existing
system, I have been facing many times problems on copying certain
files from the original or slipstreamed and/or copied install-CDs.
Most of the times the copying has been failing on some 100 files, but
sometimes just on some 2-5 files.

The basic corrective action, found on the net to overcome this
problem, is to try with other install-CDs, other CD-devices, checking
the IDE-cables/jumpers etc. etc., but these has been proving not to
help at all ...

The more expertise advice has been ripping off for the re-install
procedure all unnecessary components from the machine, incl.
PCI-cards, USB-devices etc., and disabling the onboard audio, USB
etc. devices, and, also removing any suspectable memory modules.
This last hint mainly points to non-paired modules, but also to the
need for thorough module testing by Memtest86 or some other test
program to see if there is even a slight problem on any paired or
single modules. If none of the above hints would help, it's said
that the problem is probably residing somewhere on the mobo ...
uuuu-uuh, where there ... And, noting also that all this is not so
easy to apply to a laptop ...

Slipstreams and copied installation CDs I can see failing on occasion,
especially if they're used on a different machine than they were created on.
But ... if you're also saying that the original OS CDs are not capable of
giving you a smooth, albeit time-taking installation, then IMO you need to
look elsewhere.
I disagree with reseating cables/plugs/modules or touching memory if a
machine is in known working order and simply has corruption beyond fixing.
I DO agree that it can be important to remove all peripheral connections
except for the monitor keyboard and mouse. IMO you've been going too deeply
into the physicla systems messing with memory, etc., that should have no
reason to be suspect.
Another thing that is important with OS reinstalls is to Start from a
powered down state. Not just the computer power switch off, but power
physically removed from the box. And, boot directly from the CD from a
powered down state: Not from a Restart. I have had the occasional problem
with Restarts but never when I start from the powered down state.
If you have the original CDs and start from power down, and boot directly
to the CD, and you still have problems, then there is something going on in
the hardware. Are these severely bastardized machines? Or overclocked?
Anything unusual at all?

That's about all I can say except that, once you get it figured out, invest
in an imaging program such as Norton Ghost or True Image's Acronis, and next
time this happens you'll have a recovery method available. They're cheap,
and even cheaper the first time they save your butt <g>. TEST it when you
get it of course, so you KNOW it will work when you need it! Testing is
easy to do.

HTH
Pop`

 

[Guest]

Hi!

Thank you Poprivet for your hints, but sorry, no dice either with these ...

I did once again a 5 hours thorough trial session checking the whole
re-install procedure still several times with these hints, everything ripped
off/powered down/cable taken off/booted cold from CD/browsed \i386 from the
hard disk etc. etc., and even more tricks, but nothing seems to help ...
noting, there probably has not ever been any overclocking activity on this
mobo/machine.

The additional tried tricks were
- after power cable taken off pushing the power on button, this would
release all the remaining power from the mobo, instructed some day on some
HP/Compaq pages
- taking the CMOS battery off and emptying the CMOS by the short circuiting
jumper
- changing the CD drive and the IDE cable, once again
- changing also another lower level AGP card

So, the problem is still residing somewhere else on this machine, but where
....?

OK, let's see in few weeks/months after doing some more re-installs on other
machines, probably also on some laptops.


P.S. Sorry, the Ghosting or some other cloning/full back-up copying may not
be an alternative on these some 100 ... uuu-uuh, mainly all different
machines I have to take care ...


Best regards,

Pete V.

 

[Poprivet]

Well, I'm out of ideas then. Sorry.

Pop`

Hi!

Thank you Poprivet for your hints, but sorry, no dice either with
these ...

I did once again a 5 hours thorough trial session checking the whole
re-install procedure still several times with these hints, everything
ripped off/powered down/cable taken off/booted cold from CD/browsed
\i386 from the hard disk etc. etc., and even more tricks, but nothing
seems to help ... noting, there probably has not ever been any
overclocking activity on this mobo/machine.

The additional tried tricks were
- after power cable taken off pushing the power on button, this would
release all the remaining power from the mobo, instructed some day on
some HP/Compaq pages
- taking the CMOS battery off and emptying the CMOS by the short
circuiting jumper
- changing the CD drive and the IDE cable, once again
- changing also another lower level AGP card

So, the problem is still residing somewhere else on this machine, but
where ...?

OK, let's see in few weeks/months after doing some more re-installs
on other machines, probably also on some laptops.


P.S. Sorry, the Ghosting or some other cloning/full back-up copying
may not be an alternative on these some 100 ... uuu-uuh, mainly all
different machines I have to take care ...


Best regards,

Pete V.

 

[LVTravel]

This can happen to Windows XP Home installs that have been updated to
Windows XP Pro. When you get the error swap home/pro CD's until setup
finishes.


--
Zaranthos
------------------------------------------------------------------------
Zaranthos's Profile: http://forums.techarena.in/members/156615.htm
View this thread: http://forums.techarena.in/windows-xp-support/733376.htm

http://forums.techarena.in

Why are you responding to a post from 4-20-07 more than two and a half years
ago.

 

[Roy Smith]

Why are you responding to a post from 4-20-07 more than two and a half
years ago.

Perhaps he's a little behind in reading the newsgroups? ;-)