radhx

Cannot access CD containing Windows XP installation files

21 posts in this topic

Hi,

I have a Sony Vaio laptop with WinXP Pro (SP2) OS which came pre-loaded with it.

Recently I tried to create an Installable CD using I386 folder and nLite using hotfixes

from RVM Integrator site.

(I found the I386 folder under C:\Windows directory on my laptop and not under C:\)

The CD creation got over without any problems.

The Installation went on properly till the hard-disk formatting & checking.

(I am using MS Virtual PC 2004 for emulating another PC.)

After this point, I am getting the following message:

========================================================

Setup cannot access CD containing the Windows XP Installation files.

To retry, press ENTER. If you are not successful after several tries,

quit Setup. Then, to restart Setup, copy the Windows XP installation files

to your hard disk.

To quit Setup, press F3.

========================================================

I tried to use physical CD drive as well as ISO image, but got the same error.

All the files seem to be on the CD/ISO but still the error is displayed.

CD contents are as follows:

F:\$OEM$\

\$$\

\System32\

\1365VidChng.exe

\CDR.exe

\cmdow.exe

\sleep.exe

\cmdlines.txt

\Royale.exe

\RunWPI.cmd

\DrvBackup\

\...driver folders + files

\I386\

\ASMS

\COMPDATA

\DRW

\FONTS

\INF

\LANG

\NLDRV

\SVCPACK

\SYSTEM32

\WINSXS

\... files

\WPI\

\...folders + files

\WIN51

\WIN51IP

\WIN51IP.SP2

What could be the probable cause (any missing files) for the same?

I am not sure how I should proceed from this point.

Any help will be greatly appreciated.

Thanks & Regards,

Rad.

0

Share this post


Link to post
Share on other sites

i'm facing the same problem....so i just use the original cd to get the windows installed..i wonder what cause the problem...need help too.... :}

0

Share this post


Link to post
Share on other sites

so no one are willing to give advice? we are still waiting..... :o

0

Share this post


Link to post
Share on other sites

Hi,

After going through many posts under nLite forum, I experimented a little, but without any success.

Still stuck at the same point.

The registry entry in HKEY_Local_Machine\Software\Microsoft\Windows NT\CurrentVersion\

SourcePath is E:\i386

My CD ROM is at F:

Memory Stick is at E:

I am using ImgBurn to create boot image which uses "Rem. Drive (E:)" to create image.

Does this affect the setup in any way?

===================================================

My Recovery CD has the following:

Volume in drive F is RECOVERYDISC

Volume Serial Number is 271F-5EA2

Directory of f:\

2004/09/17 07:14 49,152 AUTORUN.EXE

2002/06/08 10:48 49 AUTORUN.INF

2004/12/13 13:00 <DIR> I386

2004/12/13 13:00 <DIR> RCD_CSTM

2004/12/13 12:57 0 RDVD1

2004/12/13 13:00 <DIR> SONY

2004/12/13 12:24 671,130,628 SONY.I01

2004/12/13 12:27 671,142,405 SONY.I02

2004/12/13 12:27 5,240,840 SONY.I03

2004/12/13 12:27 545,289,327 SONY.IMG

2004/12/13 11:17 607,212,082 SONY.PAC

2004/12/13 11:16 190,544,319 SONY2.PAC

2004/04/22 14:31 530,217 SONYDNT.IMG

2004/12/13 13:00 <DIR> SUPPORT

2004/12/13 12:57 <DIR> VAIO

2004/12/13 13:00 <DIR> VALUEADD

2004/08/04 17:30 10 WIN51

2004/08/04 17:30 10 WIN51IP

2004/08/04 17:30 10 WIN51IP.SP2

2002/08/29 17:30 167 WINBOM.INI

14 File(s) 2,691,139,216 bytes

6 Dir(s) 0 bytes free

The size of I386 directory on Recovery CD is only 93 MB, AFAIK it has to be 400+ MB.

(The I386 directory under C:\Windows was 450+ MB which I am currently using.)

Can any of the above files be used to create proper installation disk?

Any help/suggestions will be greatly appreciated.

Thanks & Regards,

Rad.

0

Share this post


Link to post
Share on other sites

It seems to me as TWO different problems:

trying to build from the C:\Windows\i386 directory and failing should mean you are missing one or more files.

Have a look at this thread:

http://www.msfn.org/board/index.php?showtopic=70301

and links therein

trying to build from recovery CD appears like better, but again you have to check the contents of f:\I386 (i.e. make a DIR /S) and compare as per above

it looks like some additional files are packed in archives....

Check this also:

http://www.911cd.net/forums//index.php?showtopic=16381

jaclaz

Edited by jaclaz
0

Share this post


Link to post
Share on other sites

Hi jaclaz,

Thanks for the useful info.

I compared the files in \I386 directory with the links provided.

All the mentioned files for XP Pro seem to be in place except the following-

.\readme.htm(different/identical times)

.\setup.exe (different/identical times)

.\i386\win9xupg\migdb.inf (different/identical times)

.\i386\win9xupg\vscandb.inf (different/identical times)

.\i386\win9xupg\win95upg.inf (different/identical times)

.\valueadd\msft\mgmt\ias\iasnt4.exe

.\valueadd\msft\mgmt\ias\readme.htm

.\valueadd\msft\mgmt\pba\pbainst.exe

.\valueadd\msft\mgmt\pba\readme.htm

Are these files mandatory?

Is there any way to know whether the source (C:\Windows\I386) is original

or one slipstreamed with SP2?

What is the approx. size of XP Pro with SP2 slipstreamed?

(The F:\I386 directory on Recovery CD is of size 93 MB only, where as the

one under C:\Windows\I386 is of size 428 MB)

Assuming my pre-installed XP Pro system was already slipstreamed with SP2

(as the source was under C:\Windows and not under C:\), I am skipping

slipstreaming part (as I will have to download SP2 using my dial-up connection)

and only integrating hotfixes & WPI.

nLite recognizes the source as XP Pro with SP2.

Do you recommend downloading SP2 and slipstreaming with 428 MB source? or I

should use 93 MB source?

Also, one more difference which I observed is-

the links specify all the directory/file names in lower case,

************************************************************************

Differences between Windows XP Professional vs. Home Versions

************************************************************************

.\readme.htm(different/identical times)

.\setup.exe (different/identical times)

.\i386\1394.in_ (different/identical times)

.\i386\1394vdbg.in_ (different/identical times)

.\i386\61883.in_ (different/identical times)

.\i386\acerscan.in_ (different/identical times)

.\i386\acpi.in_ (different/identical times)

.\i386\apcompat.in_ (different/identical times)

.\i386\apps.in_ (different/identical times)

.\i386\avc.in_ (different/identical times)

.\i386\battery.in_ (different/identical times)

.\i386\bda.in_ (different/identical times)

.\i386\brmfcmdm.in_ (different/identical times)

.\i386\brmfcmf.in_ (different/identical times)

.\i386\brmfcsto.in_ (different/identical times)

.\i386\brmfcumd.in_ (different/identical times)

.\i386\brmfcwia.in_ (different/identical times)

.\i386\brmfport.in_ (different/identical times)

.\i386\camdsh20.in_ (different/identical times)

where as on my laptop these directory/file names appear in upper case.

2007/01/23 18:26 <DIR> .

2007/01/23 18:26 <DIR> ..

2004/08/04 17:30 331 _DEFAULT.PI_

2004/08/04 17:30 843 12520437.CP_

2004/08/04 17:30 885 12520850.CP_

2004/08/04 17:30 1,721 1394.IN_

2004/08/04 17:30 29,992 1394BUS.SY_

2004/08/04 17:30 765 1394VDBG.IN_

2004/08/04 17:30 6,259 1394VDBG.SY_

2004/08/04 17:30 3,827 3DFXVS2K.IN_

2004/08/04 17:30 280 3DGARRO.CU_

2004/08/04 17:30 340 3DGMOVE.CU_

2004/08/04 17:30 280 3DGNESW.CU_

2004/08/04 17:30 310 3DGNO.CU_

2004/08/04 17:30 268 3DGNS.CU_

2004/08/04 17:30 280 3DGNWSE.CU_

2004/08/04 17:30 272 3DGWE.CU_

2004/08/04 17:30 342 3DSMOVE.CU_

Does this matter in any way? If yes, is there any way to convert all the

directory/file names in lower case using some command/utility?

Thanks & Regards,

Rad.

0

Share this post


Link to post
Share on other sites

I don't have a direct experience with Sony recover CD's, so take the following advice as a simple "attempt" at an explaination:

From what you posted it seems like the Recovery CD is (more or less) made as following:

1) A PE build (probably WinPE, not BartPE) that accounts for the 93 Mbytes in the /i386 folder of the CD

2) Some kind of imaging program (cannot say if Ghost or a similar app), probably present in the \SONY or in another directory

3) a number of images or however compressed setup

The general idea of the working should be that system boots the PE in 1) that loads autmatically the app in 2), which copies the image or files in 3) to the hard disk.

So the CD is NOT an easily usable source for making an install CD.

I compared the files in \I386 directory with the links provided.

All the mentioned files for XP Pro seem to be in place except the following-

.....

Are these files mandatory?

They don't seem like it.

The files in \i386\win9xupg\ are files needed for upgrading from Win9x, you won't need them.

The files in .\valueadd\ should not be mandatory and could however be present in the \VALUEADD directory on the CD

\setup.exe is the file which is invoked by the AUTORUN.INF file on the original windows CD, since you are using this as a bootCD, you can do without it.

.\readme.htm are release notes which should be not necessary.

Is there any way to know whether the source (C:\Windows\I386) is original

or one slipstreamed with SP2?

1) Filedate (04/08/2004) ?

2) Check either SMSS.EXE or NTDLL.DLL in \I386\SYSTEM32 properties, if they are Version 5.1.2600.2180 should be SP2

However it is possible that you have some "post SP2" hotfixes in there....

Do you recommend downloading SP2 and slipstreaming with 428 MB source?
Yes, I would try sliptreaming them, if SP2 is already applied should not make any difference.
Also, one more difference which I observed is-

the links specify all the directory/file names in lower case,

......

where as on my laptop these directory/file names appear in upper case.

Does this matter in any way? If yes, is there any way to convert all the

directory/file names in lower case using some command/utility?

Cannot remember if it matters, however EVERYTHING on XP CD's is in CAPITAL LETTERS, so you are fine, it is probably a "feature" of the CD compare app tacktech used.

About the error you get, it is possible that one or more of the setup files, i.e. TXTSETUP.SIF, UNATTEND.TXT (if present) or one of the .ini files are "custom" made for the Sony setup and point to an additional application, driver or what not, that actually is somewhere in the Recovery CD and on Hard disk, but that it is obviously missing in the nlited CD...

jaclaz

0

Share this post


Link to post
Share on other sites

Hi jaclaz,

Could go up to the "Copying files" step in setup after doing the following:

Compared \I386 (93MB) and \I386(428MB) and moved whatever missing files from 93MB to 428MB.

Checked out DRVINDEX.INF for missing dll/sys/chm files

and modified accordingly-

1] \I386\system32\WINPEOEM.INF

[massstoragedrivers.append]

;mydriver = mydriver.sys

dmidriver = dmicall.sys

entire section was commented out using ;

;[massstoragedrivers.append]

;mydriver = mydriver.sys

;dmidriver = dmicall.sys

as this was causing the "0 value at line in [sCSI] section for dmidriver." error.

This dmicall.sys file is present in I386 folder but how to make use of it?

After commenting this, installation went ahead but reported following missing files.

2] Missing files -

not found on hard disk/Recovery CD and commented out using ; in DRVINDEX.INF / TXTSETUP.SIF

cinemst2.sys

tsbyuv.dll

Where can I get these 2 files? Are they mandatory?

found and copied to \I386 from C:\Windows\System32\ _or_ \System32\drivers

4mmdat.sys (from sp2.cab)

cpqdap01.sys

cyycoins.chm

cyzcoins.chm

digiras.chm

dvdplay.exe

kodak_dc.icm

mdwmdmsp.dll

nikedrv.sys

rio8drv.sys

riodrv.sys

spnike.dll

sprio600.dll

sprio800.dll

srgb.icm

streamci.dll

tosdvd.sys

tsbvcap.sys

usbcamd2.sys

usbcamd.sys

vdmindvd.sys

wowfax.dll

wowfaxui.dll

fsvga.sys

paqsp.dll

usrcntra.dll

usrcoina.dll

usrdpa.dll

usrdtea.dll

usrfaxa.dll

usrlbva.dll

usrmlnka.exe

usrprbda.exe

usrrtosa.dll

usrsdpia.dll

usrshuta.exe

usrsvpia.dll

usrv42a.dll

usrv80a.dll

usrvoica.dll

usrvpa.dll

Afte copying all the files to windows folder I get following error -

=====================================================

Setup cannot set up the required Windows XP configuration information.

This indicates an internal Setup error.

Contact your system administrator.

=====================================================

only F3=Quit option is available at this point.

What could be the reason for this error?

Thanks & Regards,

Rad.

0

Share this post


Link to post
Share on other sites

Well, no, I think you cannot just copy files extracted from Sp2.cab, you need to slipstream it.

About the two missing files:

http://www.msfn.org/board/index.php?showtopic=26419

http://www.pennskog.com/cinemaster/hardwar...ers_details.htm

http://www.pcfixtool.com/dll/5850/cinemst2.html

http://www.liutilities.com/products/wintas...library/tsbyuv/

http://www.dlldump.com/download-dll-files_...0/download.html

You cannot remove a driver by ; if the line was there, most probably there is a reason.

Check the other file (WINNT.SIF?,TXTSETUP.SIF?,UNATTEND.TXT) for references to that file, it is possible that it must be put in a subdirectory....

jaclaz

0

Share this post


Link to post
Share on other sites

Hi jaclaz,

In the 428MB source, most of the files have date 2004/08/04, except few INF's

which I modified and drivers downloaded from net like cinemst2.sys and tsbyuv.dll.

SMSS.EXE as well as NTDLL.DLL in \I386\System32 are with version 5.1.2600.2180.

So I can safely assume that the source is already slipstreamed with SP2.

BTW, I could create BARTPE bootable CD from the same source and it boots MS Virtual PC 2004.

How do I slipstream selective drivers with source?

I tried slipstream option in nLite but it expects Service Pack EXE.

Or do you mean using missing files in Drivers option?

About Product Key-

Now there are 3 different Product keys available to me.

1] From the WinXP Pro Label on back of my laptop

2] From CDReader which is different from above and

3] From UNATTEND.TXT which is again different from above 2.

Which Product Key should I use?

Going further.....

Downloaded cinemst2.sys and tsbyuv.dll from the Net. Thanks for the links.

Restored all previously commented references of these files in -

DRVINDEX.INF / TXTSETUP.SIF / DOSNET.INF / LAYOUT.INF

Also, restored dmidriver reference in WINPEOEM.SIF

Now, WINPEOEM error is resolved.

But Still getting stuck at same place in the setup.

If I try to boot from VPC hard disk, getting following errors -

=====================================================

Invalid BOOT.INI file

Booting from C:\windows\

.

.

.

Windows could not start because the following file is missing

or corrupt:

\windows\SYSYTEM32\CONFIG\SYSTEM

You can attempt to repair this file by starting Windows Setup

using the original Setup CD-ROM.

Select 'r' at the first screen to start repair.

=====================================================

Following files are in \I386\SYSTEM32\CONFIG\

DEFAULT

SAM

SAM.LOG

SECURITY

SECURITY.LOG

SOFTWARE

SOFTWARE.LOG

Under CONFIG directory in laptop, there are -

SYSTEM (7.5MB)

SYSTEM.LOG,

SYSTEM.SAV files.

Are above files required in source?

How can I copy these files in source \I386\SYSTEM32\CONFIG?

At present copying these files is not allowed as they are being used

by the system.

Thanks & Regards,

Rad.

0

Share this post


Link to post
Share on other sites

Maybe you are trying to make more things together and one interferes with the other.

Files like UNATTENDED.TXT are not "standard".

What I would do:

1) Leave alone (for the moment) nlite and any other software

2) Recreate a duplicate \I386 directory with EXACTLY the same files listed in the file attached here:

http://www.msfn.org/board/index.php?showtopic=25362

http://www.msfn.org/board/index.php?showtopic=25362&st=8

for the full XP version, this is Professional, use the Tacktech link given before for differences if you have Home, DELETE any file that is not in that list, ignore anything that is not in \I386 or one of its sub-folders

3) Manually apply the XP SP2 as detailed here:

http://www.winsupersite.com/showcase/windo..._slipstream.asp

4) Add the missing "root" files, as in here:

http://www.911cd.net/forums//index.php?sho...16381&st=18

This way you should be able to make a "generic" or "standard" CD.

Once you have done that and it works in Virtual PC, (with the key on the back of your laptop), you can start thinking about integrating drivers and what not with nlite, RVM Integrator, making it Unattended, etc.

jaclaz

Edited by jaclaz
0

Share this post


Link to post
Share on other sites

Hi jaclaz,

Well, looks like there is no escape from 266 MB SP2 download with my dial-up connection...

Before starting that download, one more query....

I compared the directories/files on WinXP CD and my I386.

All the files seem to be there but this time I noticed the difference in driver.cab

CD List shows 73+MB size for driver.cab where as my I386 has only 17.8 MB driver.cab

more over this size is same as that for sp2.cab. They are identical.

Where can I get this driver.cab?

Thanks & Regards,

Rad.

0

Share this post


Link to post
Share on other sites
Hi,

I have a Sony Vaio laptop with WinXP Pro (SP2) OS which came pre-loaded with it.

Recently I tried to create an Installable CD using I386 folder and nLite using hotfixes

from RVM Integrator site.

(I found the I386 folder under C:\Windows directory on my laptop and not under C:\)

The CD creation got over without any problems.

The Installation went on properly till the hard-disk formatting & checking.

(I am using MS Virtual PC 2004 for emulating another PC.)

After this point, I am getting the following message:

========================================================

Setup cannot access CD containing the Windows XP Installation files.

To retry, press ENTER. If you are not successful after several tries,

quit Setup. Then, to restart Setup, copy the Windows XP installation files

to your hard disk.

To quit Setup, press F3.

========================================================

I tried to use physical CD drive as well as ISO image, but got the same error.

All the files seem to be on the CD/ISO but still the error is displayed.

CD contents are as follows:

[...]

What could be the probable cause (any missing files) for the same?

I am not sure how I should proceed from this point.

Any help will be greatly appreciated.

Thanks & Regards,

Rad.

Hi,

Here is a trick that worked with my Vaio VGN-TX3XP/B, but which will probably work also with other Vaio's - see the following (German) link:

http://www.pcwelt.de/forum/ihre-meinung-zu...recover-cd.html

In addition to the "normal" i386 folder present on most laptops (on my Vaio, it was under C:\Windows\i386), newer Vaio's have a further i386 folder under "Driver Cache\i386" (on my Vaio it was under C:\Windows\Driver Cache\i386, but the location may differ somewhat from model to model). You need to put the complete content of both 1386 folders into a new i386 folder, and then build the Windows install CD from this new i386 folder.

It seems particularly important that you get the file driver.cab (present in "Driver Cache\i386"). If you build your install CD using only the first ("normal") i386 folder, Windows will complain during installation that this file is missing, and at reboot, you get the message described in your post (I experienced exactly the same as you).

In other words, it seems that Sony has split the i386 folder into two parts (only the devil knows why ;-), and that you have to join them again to build a working installation CD.

After this, installing Windows worked like a charm on my TX3XP/B. Actually, I made an unattended install under DOS (booted from a CD), with the files from the installation CD in a folder on the D: partition (you need to have C: and D: formatted as FAT32). But there is no reason that it should not work when you install directly from the CD (e.g. if you want to format your partitions as NTFS).

I'd be glad to know if it worked for your Vaio too.

Regards

Albi

0

Share this post


Link to post
Share on other sites

Hi jaclaz / razhar / Albi,

266 MB SP2 downloaded and integrated using nLite with bare minimum I386 as specified in WinXP CD list.

Integration got completed successfully creating the following files/folders in destination C:\XPCD

C:\XPCD \ cmpnents\

docs\

I386\

support\

valueadd\

README.HTM

SETUP.EXE

SETUPXP.HTM

WIN51

WIN51IP

WIN51IP.SP2

Created Bootable ISO for WinXP+SP2 only (without any Hotfixes) for the time being, and tried to use

the same on MS Virtual PC.

But ... still getting stuck at same point with same message-

========================================================

Setup cannot access CD containing the Windows XP Installation files.

To retry, press ENTER. If you are not successful after several tries,

quit Setup. Then, to restart Setup, copy the Windows XP installation files

to your hard disk.

To quit Setup, press F3.

========================================================

I had compared the directories/files on WinXP CD List and my I386.

All the files were there, except the difference of size for driver.cab

CD List shows 73+MB size for driver.cab where as my I386 has only 17.8 MB driver.cab

This size is same as that for sp2.cab.

razhar, could you please check for this driver.cab and it's size on your machine?

Could this be the actual problem?

Albi, thanks for the info about second i386 directory.

But in that directory, I have few other files along with sp2.cab but no driver.cab.

Can anybody direct me to a link for downloading driver.cab if it is available on the net?

Maybe I will have one last shot at WinXP CD creation after this 73+MB download.....

My ISP is smiling from ear to ear!!

Thanks & Regards,

Rad.

0

Share this post


Link to post
Share on other sites

Hi Albi,

I merged all the files from C:\Windows\Driver Cache\i386\ and C:\Windows\i386 but with no success.

Can you please let me know the files present under C:\Windows\Driver Cache\i386\ on your machine?

I have only following files under the same directory-

aec.sys

http.sys

kmixer.sys

mrxsmb.sys

ntkrnlmp.exe

ntkrnlpa.exe

ntkrpamp.exe

ntoskrnl.exe

processr.sys

sp2.cab

splitter.sys

wdmaud.sys

It will help me to find the missing files (if any) in other directories on my machine.

Regards,

Rad.

0

Share this post


Link to post
Share on other sites

Hi Rad,

Here is the file list in my C:\Windows\Driver Cache\i386\

04.08.2004 13:00 63.174.124 driver.cab

29.09.2005 00:35 134.272 halmacpi.dll

09.10.2004 00:48 262.400 http.sys

19.01.2005 05:26 451.584 mrxsmb.sys

20.04.2005 00:54 14.592 ndisuio.sys

29.09.2005 19:27 2.138.624 ntkrnlmp.exe

29.09.2005 19:28 2.059.776 ntkrnlpa.exe

29.09.2005 19:28 2.018.304 ntkrpamp.exe

29.09.2005 19:28 2.182.528 ntoskrnl.exe

16.03.2004 10:58 136.960 portcls.sys

27.08.2004 22:57 39.552 processr.sys

04.08.2004 13:00 18.782.319 sp2.cab

05.11.2005 01:55 48.768 stream.sys

20.04.2005 20:30 52.736 wzcsapi.dll

20.04.2005 20:30 474.624 wzcsvc.dll

Obviously, you are missing driver.cab, which seems to me to be a very important, if not the most important file (before I merged both i386 folders, Windows installation complained that driver.cab was missing, and at reboot I got the same error message as you).

Maybe you should search for driver.cab in the original Vaio installation of your machine (possibly after a fresh restore of the initial installation). You might also try a driver.cab from another source (all "regular" XP install CD's have a driver.cab in their i386 folder, but I'm not sure it is the same as on Vaios, or even from one Vaio to another).

Regards

Albi

0

Share this post


Link to post
Share on other sites

Hi Albi,

Thanks for the list of files in Driver Cache\i386.

Looks like driver.cab was the main missing file.

After copying all the missing/required files from system32 and system32\driver, and

getting hold of driver.cab from some other source, the installation cd worked.

But now I have this peculiar problem.

I am using MS Virtual PC to try out this new XP image (only SP2 slipstreamed - no hotfixes).

WinXP gets installed and after asking for product key, setting network, and copying files,

and boots to complete the installation.

After booting, the system hangs at Windows XP startup screen (with blue progress bar).

At this stage -

1] I can reset the VPC, start in Safe mode, where I can log in properly and move around

in new environment. But if I boot again in normal mode, system hangs at startup screen.

2] If I use cd image again while booting and select to Repair existing installation, after

going through setup process for second time, VPC boots properly after completing installation.

How can I find out what's going wrong on first install?

Thanks & Regards,

Rad.

0

Share this post


Link to post
Share on other sites

Quite strange.

You should have a look (while in safe mode) if there is any device with problems and if there is any event registered in the event log.

Next attempt would be to modify boot.ini to add an entry booting with LOGging enabled, try to boot normally, then reboot once stuck in safe mode and examine the log.

/BOOTLOG

Causes Windows to write a log of the boot to the file %SystemRoot%\Ntbtlog.txt.

jaclaz

0

Share this post


Link to post
Share on other sites

Hi jaclaz,

As suggested, checked both Event Log and Boot Log.

The System Log shows Error on following 2 events-

1] DCOM

2] Server Control Manager

The Application Log shows Error on PerfNet.

Added /BOOTLOG in boot.ini

In the Ntbtlog.txt -

Following initial drivers get loaded up to mup.sys -

ntoskrnl.exe

hal.dll

kdcom.dll

bootvid.dll

acpi.sys

wmilib.sys

pci.sys

isapnp.sys

intelide.sys

pciidex.sys

mountmgr.sys

ftdisk.sys

dmload.sys

dmio.sys

partmgr.sys

volsnap.sys

atapi.sys

disk.sys

classpnp.sys

fltmgr.sys

sr.sys

dmboot.sys

ksecdd.sys

ntfs.sys

ndis.sys

mup.sys

From this point onwards "Did not load driver" messages start and get repeated many times-

Advance Configuration and Power Interface (ACPI) PC

Audio Codecs

Legacy Audio Drivers

Media Control Devices

Legacy Video Capture Devices

Video Codecs

WAN Miniport (L2TP)

WAN Miniport (IP)

WAN Miniport (PPPOE)

WAN Miniport (PPTP)

Packet Scheduler Miniport

Packet Scheduler Miniport

Direct Parallel

Communication Port

Printer Port

S3 Trio32/64

Intel 2114-Based PCI Fast Ethernet Adapter (Generic)

Sound Blaster 16 or AWE32 or compatible (WDM)

Standard Game Port

lbrtfdc.sys

sfloppy.sys

i2omgmt.sys

changer.sys

cdaudio.sys

mnmdd.sys

rdpcdd.sys

rasacd.sys

ipsec.sys

tcpip.sys

Inbetween some drivers get loaded like -

i8042prt.sys

kbdclass.sys

mouclass.sys

fdc.sys

cdrom.sys

rdpdr.sys

termdd.sys

swenum.sys

update.sys

mssmbios.sys

flpydisk.sys

fs_rec.sys

null.sys

beep.sys

vga.sys

msfs.sys

mpfs.sys

cdfs.sys

But surprisingly same CD image works if I use it again to Repair the existing installation.

Any clues? What can be done for this?

Thanks & Regards,

Rad.

0

Share this post


Link to post
Share on other sites

I am not an expert in this, but judging from the number of posts you can find by googling "mup.sys" it must be one of the most common errors that happen.

I cannot find a definite answer, it seems like that right after mup.sys a service or device driver fails to load, and this service or driver can be almost anything.

I suspect that it is something related with timing of plug'n play or something like it, but it can be virtually anything.

Here are a couple of threads that appear to be informative:

http://www.msfn.org/board/index.php?showtopic=72146

http://www.cyberiapc.com/forums/index.php?showtopic=5288

jaclaz

0

Share this post


Link to post
Share on other sites

Hi all,

Afer all this R&D, success at last!!!

Took a chance (should have tired it earlier), as I don't know much about updating

bios or changing HDD as discussed in the forum links......

Went ahead with integrating RVM Hotfixes (Jan.2007 release) and WPI using the Gold+SP2

version which was giving this first time boot error.

And VIOLA....!!!

CD image worked just fine!

May be Gold+SP2 had this glitch somewhere, which MS rectified in one of the down the

line hotfixes.

Thanks to everybody for guiding me all along.

----------------------

Few more Q's..... hopefully last ones before I burn my Installation CD :-)

For Windows Activation, MSFN Unattended pdf has given 3 procedures:

1] WINNT.SIF method:

I have my WinXP activated with the current product key for my laptop.

If I Activate a Virtual Machine with same product key using Internet,

will it create any problems? Like my valid product key getting junked by MS?

2] Backup Activation method:

As I am using Virtual Machine, this method can not be used I assume.

If not so, then how to use wpa.dbl file?

(I copied wpa.dbl file under \$OEM$\$$\System32 directory, but still got the

Activation Screen.)

3] OEMBIOS.BIN method:

I copied 4 OEMBIOS.* (bin, cat, dat, sig) files to \I386 directory on installation cd.

While in the midst of installation, WPI got started and installed some of the software

and giving errors for other.

Timer was of very short period, 5 seconds or so (not set by me).

After rebooting, Activation Screen was displayed which I skipped.

Then the same WPI screen came up for installation with the proper timer of 30 seconds.

So, does this method of OEMBIOS work? Or how to make it work?

Thanks & Regards,

Rad.

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.