File Copy error deploying RIPREP image

[Guest]

I'm having a problem with a RIPREP XPSP2 image. When I deploy the image to
certain PCs I get the error message "Setup cannot copy the file:
hccoin.dll...To retry, press Enter...To skip this file, press Esc..." during
the file copy phase.
The image was created on an IBM 6579LBA and so far I've seen the error occur
when installing on an IBM 8183KM4 and an IBM 8305xxx. If I install it on the
6579LBA I don't receive any error. I have recreated the image using different
XP and SP2 media but this has not corrected the problem. All systems are
running the latest BIOS. If Esc is pressed and the image install continues
there don't seem to be any other problems on the above mentioned PCs once a
couple of drivers are updated. I would be grateful if anyone can suggest why
this error might be occurring.

Cheers

Jason

 

[NIC Student]

Hi Jason,

The HCCOIN.DLL is from USB 2.0, perhaps you are having issues with those
drivers and need to update them. I suggest spending sometime reading these
articles on adding new USB2 drivers to your RIS image set (even though the
article says SP1):

How to obtain and to install USB 2.0 drivers in Windows XP Service Pack 1
http://support.microsoft.com/default.aspx?scid=kb;en-us;329632

How to Add OEM Plug and Play Drivers to Windows Installations
http://support.microsoft.com/default.aspx?scid=kb;en-us;254078

 

[Guest]

Thanks for your response.
Because the error is occurring during the file copy phase of setup I didn't
think that the driver file versions would be inspected by the target system -
that would become an issue when XP starts and enumerates the hardware and
tries to load drivers.

Your thoughts?

 

[NIC Student]

Hi Jason,

Hmm, I didn't realize that the error occured during initial file copy before
the first restart in the image process - must have missed that part. So you
can RIS a 6579LBA without error from the an image on the RIS server, but
when you try other models, the RIS fails during initial copy before reboot.
I hope I have it straight this time - sorry.

I found this article, let me know if it is applicable:

When your RIS client installs an image, they are unable to copy some files?
http://www.jsiinc.com/SUBF/TIP2800/rh2841.htm

--
Scott Baldridge
Windows Server MVP, MCSE


"jhanha"

 

[Guest]

Hi Scott, yes that's correct, it's always the same file (hccoin.dll) and it
only occurrs on certain systems (the ones using USB2 it seems). The image was
created on the 6579LBA (because it is the lowest common denominator in the
environment)but installs without issue on a number of other IBM models. I
checked out the link you posted and made sure there were no utility
partitions (dispart clean). I have also followed the procedure in KB 314479
(although this is concerned with the pnp device detection/enumeration process
in desperation I tried it). I have also extracted the hccoin.dll file from
the SP2.cab file and copied it directly into the i386 directory of the source
RIS folder used by the RIPREP image followed by a restart of binlsvc - still
no joy.

Any other suggestions you have would be appreciated.

Jason

 

[NIC Student]

Jason,

This problem is giving me a headache, I bet you are tired of it too. Is the
hccoin.dll file located in the same directory on all of the client machines?
Search for it and let's check that..

Perhaps try to copy the hccoin.dll to the correct RIPREP directory, such as:

\\server\REMINST\Setup\English\Images\image
name\i386\Mirror1\UserData\WINDOWS\system32

--
Scott Baldridge
Windows Server MVP, MCSE


"jhanha"

 

[Guest]

Thanks for the suggestion Scott, I'll give that a try in the next day or two
and let you know how it goes.

Jason

 

[Guest]

I'd like to jump in here, because I'm having the same exact problem.

I created a riprep image using a Dell Optiplex GX300, that had been built
using an install CD of XP Pro with SP2 slipstreamed in.

I'm trying to bring that image down to a Dell Latitude X300, and have the
same exact symptoms with hccoin.dll.

hccoin.dll only exists on the RIS server within sp2.cab. So I doubt that
extracting it and copying it to another folder within the image is going to
help.. it's still going to bomb when it gets to that cab file.

Also, that jsi article that you reference earlier in this thread mentions
that "other files" don't get copied when you select to skip copying a certain
file. I'm concerned that hccoin.dll might not be the only problem. That's
because I also have to manually update drivers after bringing the image down.
Given that I've followed the MS directions for adding OEM drivers to the RIS
image, I'm concerned that something more fundamental is breaking during the
whole process.

So anyways.. I think I'm going to try building an image just with plain old
XP (no service packs) and see how that goes. If it works then I think MS
broke something with RIS/SP2. I'd welcome any other bright ideas too.

 

[NIC Student]

Have either of you had a resolution yet? I may take it to the product
group.

--
Scott Baldridge
Windows Server MVP, MCSE


"Wendy Derman"

 

[Guest]

Nope, not yet. I did get all the driver issues fixed except one, though. I
now set up my image with a Sysprep folder and a sysprep.inf file pointing to
the locations of drivers. They all work except for one.. during the GUI PnP
portion of setup (I run riprep with the -pnp option), it never finds the
Broadcom 570 NIC driver, even though I have it right there with all the other
drivers that it does find. I have to manually select the driver, and then
all is well. However, both the hccoin.dll thing and now this issue make it a
less-than-fully-automated process, and we'd like to have that fixed.
Unfortunately all the computers I had with a Bcom 570 got taken away from me
for emergencies, so I've been stuck not able to work on it for the past few
days. But I should have another one within a week.

 

[Guest]

Well, I do have an answer on this from Microsoft, and I'm afraid it's not a
great one.

The problem described above stems from building the riprep image on a USB 1
machine, and then trying to bring it down to a USB 2 machine.

All of the MS documentation I've seen says that RIS is hardware-independent
as long as you are using the same HAL. Simply put, this is NOT TRUE. These
two machines have the same hal (halacpi.dll), but the riprep image doesn't
transfer properly to the USB 2 machine.

And it's not just limited to USB. I then tried creating the riprep image on
the USB 2 machine (which is a laptop) and bringing it down to the USB 1
machine (which is a desktop). I got a completely different error, something
about not being able to create an /asms folder. The image transfer failed
completely at this point. The Microsoft rep told me that's because the
laptop handles its IDE controllers differently than the desktop does.

The bottom line is, RIS works just fine when transferring images to the same
type of hardware from which you built the image. But if you want to use
riprep for images that have more than the straight CD-based install, you MAY
find that you need to create a different image for the various types of
hardware out there, and NOT just when the HALs differ.

Nope, not yet. I did get all the driver issues fixed except one, though. I
now set up my image with a Sysprep folder and a sysprep.inf file pointing to
the locations of drivers. They all work except for one.. during the GUI PnP
portion of setup (I run riprep with the -pnp option), it never finds the
Broadcom 570 NIC driver, even though I have it right there with all the other
drivers that it does find. I have to manually select the driver, and then
all is well. However, both the hccoin.dll thing and now this issue make it a
less-than-fully-automated process, and we'd like to have that fixed.
Unfortunately all the computers I had with a Bcom 570 got taken away from me
for emergencies, so I've been stuck not able to work on it for the past few
days. But I should have another one within a week.

 

[DavidP]

Add anohter person to the list with this same problem (hccoin.dll RIS issue).
I will post back if I happen to find a solution.