Infamous ASMS error

[573310]

Hi all,

I used to post on this forum before under another nick, but for some reason that does'nt work anymore - loong story - wont bore you!

The reason i'm posting is that i recall a while ago, seeing information around the infamous ASMS error mesage.

Installation failed.

D\I386\asms. Error message

The parameter is incorrect

Fatal error

Most posts returned on searching here, suggest that this is CD burner related issue, but i recall seeing another post ( which i cannot find any more ) which suggested a relationship between the use of cdimage.exe to create the image, and the image size exceeding a typical CD size. In the past this was the cause of my build showing this error message, but i cannot recall the resolution!

My image is greater than 2GB with Office VS etc etc - and this was the problem before.

Can anyone else remember the issue, and the workaround?

Thanks

573310

[573310]

^top

Anybody?

[573310]

Ok, let me phrase this differently;

Has anybody come across the following error during unattended setup of Windows XP :

Error:

Installation Failes: D:\i386\asms. Error Message: The parameter is incorrect.

***

Fatal Error:

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

The parameter is incorrect.

***

[573310]

OK!

Well after trawling across half the web, I think I finally found one of the threads I was vaguely recalling. Here

The link between CDimage, and using iso's to boot are discussed here, in relation got the specific error I am seeing.

Now, the strange thing is, or at least one strange thing, is that the google search feature on this site did not return this post. It was only when i googled this site specifically for from www.google.com, using the same search terms, that this post came back - so just fyi dont rely on the built in search feature on this site - it seems somewhat limited.

Some more information, I am testing the build using Virtual Server. Ring any bells anybody?

Now, I need to find that other post I recall which actually gave a resolution, if I recall correctly.

Just thought I would update, in case *anyone else* is actually out there and runs past this post! ...ever...

<tumbleweed rolls past>

.....

573310

[Alanoll]

Well, since you say CDIMAGE creates the problem (and since I vaguely remember posting in the thread you linked to ) Have you tried using mkisofs ? nLite uses a modified version I believe to create the same effect CDIMAGE does. Could be worth a shot

I'm surprised no one every noticed the relationship with the switch taht actually LETS you build an iso past 650mb. lol. Oh well.

[573310]

Hey Alanoll,

thanks for the response. I've not yet tried the utility you mention, will attempt that later. I have found however, that a large iso built using cdimage, tested in MS Virtual Server, exhibits this error message. Use the same image in VMware, and hey presto, it all works fine!

Very strange. Now i haven't yet attempted this with a real DVD build, so not sure whether the problem is with CDimage, Virtual server, or a combination of both. Will test that later and post back.

Many thanks for the suggestions, there is life out there after all ;-)

573310

[donbi]

Hi,

I had got the same error message and it was caused by a integration of raid drivers.

I had a clean slipstreamed sp2 nlited in witch i add the ryan raid pack and in some config i had the same error than you...

after searching some poeple succed to integrate ryan pack on a clean sp2 and nlite after...

hopes it helps

[big_gie]

I already had the same error, but was caused by a dirty CD drive. Switching to a DVD drive solved the problem.

[Alanoll]

well, I personally want to put the blame on CDIMAGE The only time I dont'g et the error is when I don't tell it to optomize the CDIMAGE (mine are usually over 2 gig)