[Shadowpp]

Okay folks I am in need of your assistance.....my unattended cd works beautifully when booting from CD (using the method found here ) but when I use the same cd as source and perform the unattended install in conjunction with a boot diskette I receive the following error for all the files listed :

Setup was unable to copy the following file:

Cyclad-z.inf
Cyclom-y.inf
Headsp~1.wmz
minipl~1.wmz
utopia~1.wav
utopia~2.wav
utopia~3.wav
utopia~4.wav
sv-262e1.png
sv-262e3.png
sv-262e4.png

Press ENTER to retry the copy operation
Press ESC to ignore the error and continue Setup.
Press F3 to exit Setup.

The file is present so I am confused as to why I am getting these errors.....could this be a result of one of the steps found on the page listed above?

I would greatly appreciate any help as I do have a couple of dozen older systems which cannot boot to CD but must be updated to XP.

Thanks in advance for your help

[graf_morpheus09]

Hey. I have some of this errors too. So don`t worry, its a problem of burning. So just burn, or better create a new iso with your files and burn it new. It should work!


Hope it could help

[baliktad]

This is a problem with using an ISO-9660 character set when burning. The only valid characters are a-z, A-Z, 0-9, and the underscore (_). Any special characters like the dash (-) or the tilde (~) are converted to underscores, which is why NT setup cannot find those files. Setup is looking for the file on the left, and all it can find is the file on the right, which of course doesn't count.

Correct filename Borked file name
Cyclad-z.inf     Cyclad_z.inf
Cyclom-y.inf     Cyclom_y.inf
Headsp~1.wmz     Headsp_1.wmz
minipl~1.wmz     minipl_1.wmz
utopia~1.wav     utopia_1.wav
utopia~2.wav     utopia_2.wav
utopia~3.wav     utopia_3.wav
utopia~4.wav     utopia_4.wav
sv-262e1.png     sv_262e1.png
sv-262e3.png     sv_262e3.png
sv-262e4.png     sv_262e4.png

The solution is to make sure you are using Joliet when burning, which allows those other characters like the dash and tilde. Check your cd burning program options.

It's pretty confusing, though, and very error prone, and the settings are different across different programs and even between versions! I could never remember which was was right and wrong. For simplicity's sake, I recommend a tool like cdimage.exe. It's the tool Microsoft uses to build up their own iso images. Google is sure to help you find it.

[Dominix]

I too am having trouble with cyclad-z.inf and cyclom-y.inf, but my story is a little different.

My situation is this, I’ve created a XP Pro Slipstreamed ISO. I used ISOBuster to extract the files from my XP Gold CD. I then applied SP1a. Then I used CDImage for XP Pro to create the ISO. After creating the ISO I loaded it into VMware 4.5 and it installed flawlessly. So I then created a WINNT.SIF file, using setupmgr.exe and moved it into the same i386 folder I used to create the Slipstreamed ISO. To check my progress up to that point, I created an ISO and loaded it into a VM. As it was copying the files to disk, I received this error: Setup cannot copy the file: cyclad-z.inf. I hit retry and got it again. I skipped it and received the same error type for cyclom-y.inf. After skipping it XP finished installing and seemed ok.

I created the XPCD folder with newly extracted files, applied SP1a and added WINNT.SIF. After making another ISO, I got the same errors. So I ran a VM with the Slipstreamed ISO (no WINNT.SIF) and it installed without the errors. So I extracted that ISO and added WINNT.SIF to it, made an ISO and got the errors on install.

I’ve searched the i386 folder and both files are present there. I’ve thought about removing them from the folder and then making an ISO. This is throwing me for a loop. The only difference between the ISO files is the WINNT.SIF file, which does not reference either cyclad-z or cyclom-y.

It can’t be bad CDs as I’ve yet to burn a disc.

Does anyone have any suggestions to fix this?
And what are these files for?

I’ve searched here and on google without finding the answer I need.

[baliktad]

I doubt it has to do with your winnt.sif file either, but go ahead and post it here (remove your product key first!) and we'll see if we can spot anything amiss.

That said, the problem almost certainly lies in the options you are using to create your .iso. If you are using cdimage, please provide the exact command line you are using, as well as the actual size of the files.

On another note, you shouldn't need IsoBuster to extract files from your original XP CD. Just xcopy them over. You may need IsoBuster or another similar program to extract the boot sector however. Please make sure you are starting with a genuine hologrammed CD, not a burned copy or an .iso of suspect origins. These dubious sources are not guaranteed to function identically to genuine Microsoft-mastered originals.

[Dominix]

Nevermind, it's cleared up now.

After extracting the files again from my XP cd and appling SP1a to them, I created an ISO. I loaded it in VMware and it worked fine.

So I then extracted a copy of setupmgr from my XP cd and created a simple winnt.sif file. I placed it into i386 and created an ISO. Then I loaded this ISO into VMware and it worked fine. No more errors.

I had to redo the ISO about 8 times all together. I extracted the files 4 times. The only difference was that I used the setupmgr from my cd instead of the one I downloaded.

[Sonrhah]

I to have the problem and found a section where it said that microsoft uses dos batch creation on its burning. Recommended burning options was everything the same but use character set to dos and iso 1 AND CHECK YOUR DIRECTORY DEPTH AND ALSO CHARACTER LENGTH HOPE THIS WORKS FOR ALL.

[mazin]

A friend of mine has got the same problem with the files
shown in the table below.

Files appear in i386 directory with names as shown in LAYOUT.INF column.
Same names appear in TXTSETUP.SIF.
But names in DOSNET.INF are different. Could this be the cause of copy errors?

|===|===================|===================|===================|
|No.|LAYOUT.INF---------|DOSNET.INF---------|TXTSETUP.SIF-------|
|===|===================|===================|===================|
|-1-|cyclad-z.inf-------|cycladz.inf--------|cyclad-z.inf-------|
|-2-|cyclom-y.inf-------|cyclomy.inf--------|cyclom-y.inf-------|
|---|-------------------|-------------------|-------------------|
|-3-|utopia~1.wav-------|utopia1.wav--------|utopia~1.wav-------|
|-4-|utopia~2.wav-------|utopia2.wav--------|utopia~2.wav-------|
|-5-|utopia~3.wav-------|utopia3.wav--------|utopia~3.wav-------|
|-6-|utopia~4.wav-------|utopia4.wav--------|utopia~4.wav-------|
|---|-------------------|-------------------|-------------------|
|-7-|sv-262e1.png-------|sv262e1.png--------|sv-262e1.png-------|
|-8-|sv-262e3.png-------|sv262e3.png--------|sv-262e3.png-------|
|-9-|sv-262e4.png-------|sv262e4.png--------|sv-262e4.png-------|
|===|===================|===================|===================|

Easy solution is to comment (to put ; in front of lines) those lines in both TXTSETUP.SIF and DOSNET.INF, but not in LAYOUT.INF of course.
That should stop errors from popping up.
But, eventually, this means that those files will not be copied.

Is there a workaround to get those files copied without popping up errors?

I mean, can't we just rename files in DOSNET.INF to resemble
their names in the other INFs? Would this be a working solution?

Thanks.

This post has been edited by mazin: 25 August 2006 - 06:40 AM

[mazin]

mazin, on Aug 25 2006, 02:38 PM, said:

can't we just rename files in DOSNET.INF to resemble
their names in the other INFs? Would this be a working solution?

YES! Tested.

In the first place, incorrect names were due to a bad slipstream.