[cyberdiamond]

Has anyone else had this failure?
XPC new boots properly and installs fine until the T-39 stage just after reboot into GUI.

The proper error given is below

Error
Installation failed F:\I386\asms       Error Message: The parameter is incorrect
xxx

Fatal Error:
One of the components that Windows needs to continue setup could not be installed.

The parameter is incorrect.
xxx

Background
This is a XPPro CD with sp1a then ran xpcreate and nothing else (eg just wanted an updated version)

EDIT: Double checked all hotfixes are in all the correct directories (checked by 2 people)

[GreenMachine]

I've never seen that ... Can you verify that it is the CD/ISO by testing on another PC/Emulator? If so, can you email or post the XPCREATE.LOG file.

What is it with you all down under? First czaja74, then Wraith, now you?!?!

[cyberdiamond]

Will test on an emulator soon as I have the cd on me.

I Cann't get to the log until Tuesday (Monday for you?)
As I only visit that site twice a week.

[likuidkewl]

I have had this error before, can you verify your media is good? I got this on both a plain XP pro with no SP, and a XP pro with SP1, I suggeste ripping your media and then going at it again.

[cyberdiamond]

I always verify the cd straight after buning with Nero.
The source CD is a brand new original and it installed from it fine manually.

It failed in the virtual environment as well.

Oh well, I'll download XPC again try it plain then install hotfixes 1 by one till I find the culprit.


Edit: It was to be a OEM install but I couldn't get any promise raid drivers to work.
So I set oempreinstall=no as I know oem and f6 floppy drivers don't play nice

P.S. Don't spose you have a MD5 for the download?

[GreenMachine]

XPCREATE will try to add SATA drivers if you place SATA drivers in $OEM$. A work around is to delete the XPCREATE.CAB file. I suggest you do that, just in case.

You might try the 50/50 method. Add half the fixes at a time. If no error, add half of the remaining. If an error, remove half.

[ElMonty]

Im having this problem:

http://www.MSFN.org/...showtopic=15753

with the new XPCreate, the files of the XPSource are working flawlessly, but when i run XPCreate to slipstream the SP1, rollup and some other hotfixes it creates a CD with that error :S

What i dont understand is that the ASMS error is given at 39 minutes left, my question is: does XPCreate changes something affecting at this point of the installation?

Anyone had this problem and solved it?

[GreenMachine]

No, I have not seen more than these two reports on this error. XPCREATE does nothing special that should happen at T-39. Now that there is more than one report, i will be looking into it. I may be PMing you in the next day or two for more information, and possible testing.

Thanks!

[cyberdiamond]

I redownloaded and tested last night and did not get the error again.
Using XPCreate 27th Feb.
Although I was adding different raid drivers and different oem folder setup?

I can also do testing but I am very busy atm.

[GreenMachine]

I believe the RAID drivers should be loaded around the T-39 mark ... What RAID drivers were present? cyberdiamond? ElMonty?

[ElMonty]

Didnt use any raid drivers.

[GreenMachine]

All I see about ASMS errors indicate problems communicating with the CD drive. Can (either of) you confirm this is NOT the case?

[cyberdiamond]

I was trying to get the promise drivers to work for pdc 20276 motherboard chipset.
But it also gave that error in VMWare (no raid present of course )

When I got the error it was the version before 27 Feb.

The cdrom/burner works fine
Also verified the burning proccess as soon as it was finished

[GreenMachine]

Thanks for clearing that up, cyberdiamond. (I was not doubting you!)

Time to dig deeper ...

[ElMonty]

The CD is being read with no problems.

I tried replacing the files with the ASMS folder from a working iso=same problem... ill try removing some hotfixes:

First try: rollup
More news soon

[ElMonty]

I got it!

It works without the rollup, you should review the slipstream of the rollup GreenMachine. Will it work if i slipestream the rollup with the gosh method? Well, better if i try

@ Cyberdiamond: try removing only the roll up to confirm this

[GreenMachine]

The rollup, which is nothing more than a big hotfix, is slipstreamed just like the others: according to MS specs. Also, there have been hundreds of XPCREATE installations, and this is the first two error reports about ASMS I've seen. I would gladly look into it, but without being able to reproduce the error myself, there is not much I can do. I will, however, make a note for future reference. Unfortunatly, I would consider an XPCREATION without the "rollup" a failure ... Were there any on-screen errors? Does the "bad" CD have the same symptoms on all hardware? On VPC? cyberdiamond, can you think of anything different between your successful attempt and your failure?

I'm a bit stumped on this one, though we have pinpointed it to one hotfix.

[ElMonty]

No more ASMS error for me.

I redo the source slipstreming the rollup with gosh method (didn't work first time i tried, i was using a wrong dosnet.inf ), apply XPCreate and everything is fine now.

@GreenMachine Did the slipstreming of rollup with XPCreate use the dosnet.inf? The source i was using didn't have that file (after reduction size of source stage), could that be the problem?

@Cyberdiamond, if the above is the problem, try copying the dosnet.inf from the CDsource (without reducing the size) and applying XPCreate, i didnt try for myself it is just an idea i have just had now. If it doesnt work try what i did.

Thnkx pple

P.S. If i didnt tell before: congratulations for the XPCreate project, it is a really good app

EDIT: Something is wrong! The rollup is not working :S It is prompting me to install the hotfixes joined in the rolup (not the rollup, the hotfixes in it... )

[GreenMachine]

ElMonty, on Mar 3 2004, 05:35 PM, said:

...
@GreenMachine Did the slipstreming of rollup with XPCreate use the dosnet.inf? The source i was using didn't have that file (after reduction size of source stage), could that be the problem?
...

Hmmm... Look HERE

[ElMonty]

What about if I reduce the size AFTER running XPCreate? (to the CDROOT folder)