RIS install problem, pci.sys missing or corrupt

[jatkinson]

Hi

I've created a RIS image, installed my software and then ran RiPrep, created my full image and then installed it to several PCs (all of same spec)the image seems to have installed OK but then XP reboots and then complains of a missing or corrupt PCI.sys file.

I've seen posts of this as a problem but not in relation to RIS or RiPrep, any ideas on how I can solve this and why has it happened. The logs show that my image was created fine.

Thanks

 

[bcastner]

You are using the wrong version of XP for the base image. You need to create an image for identical, or very nearly identical, license and hardware aspects of the base system to those you intend to RIS.

Your error message most commonly comes from BIOS-locked OEM distributions that are attempted on other computers that are not BIOS compliant for the base image.

 

[jatkinson]

OK, the base image, license and hardware are identical. I'm using a Win XP VLP CD to create the base and then installed software and updates (could it be updates changing kernal etc?).

Can you elaborate on the BIOS and OEM bit please? The PCs are 8 new identical Fujitsu-Siemens PCs, which obvioulsy come with their OEM Windows pre-installed, are you saying that somethin in the BIOS could be causing a problem?

Thanks for replying so promptly

 

[bcastner]

Just to clarify the base image:

. what was the source of the VLK image? Microsoft?
. have you slipstreamed the hotfixes and service packs, or how are you applying them to the image? By just a re-seal?
. For SLP issues, see my FAQ entry: faq779-4004
And the late (and very much missed) article by Alex Nichol:

http://www.aumha.org/win5/a/wpa.htm

Was the RIS image created on an identical Fujitsu-Siemens PC?

Is there anything in this machine that requres the use of the F6 during install to load RAID or SATA drivers?

 

[jatkinson]

Hi again, thanks for you continued help

The source is a Microsoft CD from a MYO license. I copied the CD to a folder on the hard drive and then using a 2nd CD that has SP1 on it slipstreamed SP1 into the directory.

I then used this on my RIS server to create my base image.

After pre-staging the computer in AD I then used PXE boot to install the base image via RIS to a fujitsu machine. I then installed hotfixes, then installed MS Office 2000 Ent Ed VLP, and then installed my other software. I then ran RiPrep and all went OK. I then connected the remaining identical Fujitsu PCs to my LAN, pre-staged them all in AD, ran PXE boot, F12, chose my new full install image and left them to it, all went well and then all of them rebooted to the pci.sys error.

None of the machines required the use of F6.....

Cheers,

 

[bcastner]

Your steps sound darn good.

Now, since this is a batch of machines all from the same production line, lets get out of the box:

. Create a floppy boot image for a memory tester, either of these will serve:

http://oca.microsoft.com/en/windiag.asp

http://public.planetmirror.com/pub/memtest86/

Boot from the created floppy and do an extended test of system RAM. Other than true PCI buss issues, the error is thrown for memory reasons. (Go figure).

. While that chugs away, repeat your steps as a manual install on one of the known bad machines. If it boots and acts normally, reseal and update the RIS image. It is possible something flaked out in the original upload.

Let us know if it continues as an issue.

 

[jatkinson]

Hmm... interesting, as I'm rushing to meet a deadline I decided to simply redo 6 of the machines using the base image, use Group Policy to install most of my software afterwards and then simply run between to install legacy software that doesn't work in AD (ie. no msi file)

Anyway, the 1 remaining PC I decided to boot with the CD go into the Recovery console, and then run chkdsk /r, it hung at 100% so I was CTRL+ALT+DEL'd and was going to boot to PXE again but mis-timed it and hey presto it continued to load into windows!!! I then configured time, admin account, network details etc and it loaded OK!

Shame I didn't try that with more of them! Any ideas from that experience? I take it the image must be corrupt or something?

 

[bcastner]

My gut tells me that there is a hardware device it is having an issue resolving.

As you have a workaround, let the sleeping dog lie.

But keep an eye on it.

True gut guess: this is a BIOS issue, and if these are brand new machines there unlikely is a fix at the moment. ACPI is very fussy under Windows XP.

The fact that chkdsk /r under Recovery Console hung is indicative and important. There is a PCI buss issue there somewhere. Whether the hard disk drives (unlikely, but possible); the optical drives (more likely, including a firmware upgrade to them); or anything else attached is hard to say. But I think there is an unresolved issue. I would talk to Tech Support at Siemens to see if there is a possible BIOS issue.

Good work, by the way on your issue. Please keep us informed.

Best regards,
Bill Castner

 

[jatkinson]

Hi Bill,

Thanks for your efforts, knowledge and experience on this problem. I'll keep investigating and post back when a little less rushed

Cheers,

James