Hey guys,

whenever I try to install a customized WinXpSP2 on my notebook, I receive multiple error messages. The error messages state that Setup couldn`t copy a file.

Here is a list of some files setup can not find:

cdaudio.sys
cinemst2.sys
cyycoins.chm
czcoins.chm
digiras.chm
dvdplay.exe
kodak_dc.icm
srgb.icm
streamci.dll
tosdvd.sys
tsbvcap.sys
tsbyuv.dll
usbcamd.sys
usbcamd2.sys
vdmindvd.sys
wowfax.dll
wowfaxui.dll
fsvga.sys
etc....

I have to skip every file to continue the installation. When I look into System after finishing the installation a lot of things like media codecs and battery are not properly intalled.

Does anyone know what the problem is?

Is it generally possible to install a customized WinXp on a notebook?

I would really appreciate your help.

Johann

(Please correct my English if I made mistakes)



Some Background information:

When I create a normal WinXP Pro SP2 without removing components everything works fine.

I tried many times to create a customized version but it never worked properly.

I never remove important components. Only a few that are really safe to remove. (Safer than Safe Mode)

I never integrate anything.

I use a WinXP Pro Corp German CD copy it to my HD and use Nlite to slipstream SP2.

My notebook is an Actebis Peacock mobileAMD 1600+ with 512 MB RAM, ATI Mobile 9000, a Toshiba DVD Recorder and Dlink Wifi.

The battery and the codecs things are drivers that aren't digitally signed. It's just a problem with Driver Signatures. Make sure you are using the latest version of nLite. This glitch was apparently fixed in .7 Beta 2.

Thanks for your reply.

But i am using the latest version. Any idea why its stil not working?

I just made a new cd. This time I put all the files that where missing in the previous installation in the custom file list.

When I tried to install the cd i got the following error: row 608 of INF-File \i386\txtsetup.sif is incorrect.

Please help me!

Johann

Well, I don't really know...I haven't seen so many people report bugs with nLite...everyone's getting invalid lines or BSODs or whatnot. Nuhi has some work to do...

next try:

i made a customized xp cd with minor changes. see what i kicked out:

[Main]
Version = 0.98.8 beta
Framework = 1.1.4322.573
Target = Windows XP SP2 build 2180

[Components]
Briefcase
Games
Internet Games
Pinball
Isdn
FrontPage Extensions
Internet Information Services
Windows Messenger
MSN Explorer
Netmeeting
Arabic
Baltic
Chinese Simplified
Chinese Traditional
Cyrillic
Georgian
Hebrew
Indian
Japanese
Korean
Thai
Turkish
Vietnamese
Multilanguage Support (LANG dir)
Media Center
Movie Maker
Music Samples
Tablet PC
Tour
Error Reporting

[KeepFiles]
msconfig.exe
scrnsave.scr
cdaudio.sys
cinemst2.sys
cyycoins.chm
czcoins.chm
digiras.chm
dvdplay.exe
kodak_dc.icm
srgb.icm
streamci.dll
tosdvd.sys
tsbvcap.sys
tsbyuv.dll
usbcamd.sys
usbcamd2.sys
vdmindvd.sys
wowfax.dll
wowfaxui.dll
fsvga.sys
usrcntra.dll
usrcoina.dll
usrdpa.dll
usrdtea.dll
usrfaxa.dll
usrlbva.dll
usrlmnka.exe
usrprbda.exe
usrtosa.dll
usrdspia.dll
usrshuta.exe
usrsvpia.dll
usrv42a.dll
usrv80a.dll
usrvoica.dll
usrvoica.dll
usrvpa.dll
fetnd5.sys
enum1394.sys
battc.sys
compbatt.sys
modemcsa.sys
audstub.sys

[RemoveFiles]

[Options]
isomaker = -volid "WinLite" -allow-multidot -relaxed-filenames -allow-leading-dots -N -l -d -D -joliet-long -duplicates-once -no-emul-boot -b boot.bin -hide boot.bin -hide boot.catalog



as you can see I put all the files that where missing previously on the keep list.

but again setup asks me for exactly these files.


can anyone explain this to me?


pleeeeeaze

johann/park

I also have some copy errors. Like tosdvd.sys. What to do about it?

I'm getting the same exact problems. Now whenever I load windows, I get a hardware wizard bubble telling me "system" is found and i get prompted for compbatt.sys. This is with the latest .99.9 beta Thanks.

I'm having the same problems, with an XP corp install with slipstreamed SP2. There were a lot of missing files, but I remember I was worried about battc.sys missing, since I installed this on a laptop. The battery worked, but I didn't get any options or settings (the battery in the system tray).

This seems to be a bit of a hit or miss problem on OEM discs used to nlite, I managed to get myself a retail copy of WinXP PRO and nlite'd it lastnight and the only problem I have is the setup hangs after the first reboot at the "Please Wait" screen, but back to the topic at hand. Before I got a Retail version of windows xp I was using an OEM cd and having the same problems, but some of my buddy's to whom i recommended nlite, tweaked they're disc with it using an OEM XP cd and they had no problems at all so it has to be something within the OEM cd giving troubles, I remember it was stated in one post awhile back that the OEM cd's use slightly different .inf files and nlite uses those to adjust your disc accordingly but when it does some things will not match up as they should causing the problems it seems that many of us have. i have found some temporary fixes but they do not fix everything, use ACDzip to replace the files into your driver.cab file that are missing before making the iso and it will fix some problems (credit goes to user "Power350" for pointing out that ACDzip can add the files ) but don't forget this is only a temporary fix, even after replacing the files into the driver.cab file you might come across more things not working correctly.

-D-

Hi,

XPsp2 corp, I don't use nLite to slipstream sp2 do it manually.

Use nLite to reduce XPsp2 corp down to 420MB no problems when install.

When I use RVM hotfixes and nLite to slipstream them thats when I get the missing files thing in setup.

I have no idea how to fix it.

I have the same also, using a Windows XP Home edition SP1a CD (Dell OEM).
I can get it to work (if unmodified sp2 slipstream gives problems) but on my last install it also complained of some missing files.

i get the same error my xp cd's
what i normally end up doing is extracting all the files from the original driver.cab files into a folder but this normally results in errors and only copys like half the files so you need to go back to the driver.cab and select from were it stopped to the end and keep doing this untill u get no errors then I extract my nLited driver.cab to another folder and then copy the nLited files over the original driver.cab files then re-create the driver.cab copy it to the i386 folder and bobs ur uncle it seams to work for me not the best solution but at least a work around.

Opps - Sorry guys didnt see the post above!"

I've had the same problem's since i've been using nLite...

I normally just open up the pre-SP1 driver.cab and copy the files out of it I need for the setup.

Please mr. nlite creator, me and a couple of my friends love nLite but hate how it's ripping out so many files listed earlier in this topic, it's just really annoying!! I love your work but this is enough to make me not even use the software and do everything by hand post-install.

-Joe

erukian, I don't know were you reading this topic carefully but you missed the part where we conclude that it's your CAB, it's corrupted...you can try extracting it yourself and you'll find those files missing.

Unless you experience some other problem then name your files.

How can the cab be corrupted if the files exist on my Pre SP1 XP Professional CD?

EVERY time i start from scratch, download the latest nlite, then the SP2 network install from microsoft.

I copy the files off the CD to C:\XPCD then i slipstream SP2. At this point if I make an .iso image using nlite i get _no missing files_ but if I actually use nlite's features and try to remove say the language pack or integrate RyanVM or anything, it'll rip out those files listed earlier. I just can't see how that's a problem on my end.

I love nlite, but right now i'm forced to manually just pull the .dll's and .sys files that XP requests out of my pre-sp1 driver.cab and then drop them in C:\windows\driver cache\i386 so XP doesn't freak about missing files when i do driver installations.

-Joe

Do me a favor...integrate without nlite, then extract driver.cab to some folder
and sp2.cab to some other...check if you have those files missing in any of those folders.

Use expand.exe

If you confirm that these files are there then we can talk further.

But I'm telling you many people tested it before you and they confirmed that even without nlite it's messed up.
I wish it's nlite and that i can fix it...believe me.

I see what your trying to tell me.

I did as you asked, used expand.exe and yes, the files were missing.

I used expand like this "expand DRIVER.CAB -F:* C:\DRIVER" and it errors out during expanding.

I'm really confused why if I have a corrput driver.cab, then how come all my installations w/o nLite went fine? from pre-sp1, to sp1 slipsreamed, to sp2 slipstreamed? Do i have to contact MS to let them know my copy of XP is bad to get a replacement?

-Joe

I've also had problems. I saw nLite described in the latest Custom PC mag, and as I'm in the process of reinstalling my work PC, I thought it sounded useful.

Optimistically, I decided to:
- start with my MS original "Gold" XP SP1a disk, (OEM variety)
- slipstream SP2
- add a pair of new disk drivers
- integrate a bunch of hotfixes (about 12) relating to IE and Core XP
- disable a couple of programs: windows messenger, novell networks
- do a few tweaks to the registry and general setup.

Things seemed ok, other than not at first realizing that the iso file had merely been created, not written to disk!

However, the first time I tried installing, I left the PC to it for a while, and when I came back there was a message asking for the SP2 Disk for the file "asms". Ther's a directory asms there in the SP2 extract directory, but at that point I had no way of making it available and setup refused to carry on without it.

Following this, I found that the new setup disk would boot as far as disk formatting, etc, but although the new hard drive partition "booted", it didn't start properly - it fails very quickly with a long message about invalid paths and directory contents.

I checked the original driver.cab and the driver.cab that nLite generated, and the generated one has about 4444 files in it, while the original has 4657 files. The missing files seemed fairly basic: stuff like IP connections, atapi drivers etc.

Might it help to do the slipstream "manually"?

Ruth

P.S. My runs of expand.exe both went without a hitch; no bad files, no issues.

@erukian, do you have gold edition, i mean without any service packs...then just apply sp2, don't apply sp1 first.

If you have tried that already then I think that problem lies in that that expand skips all after error while windows during install expand file by file and by that you can get all files around the error.

Thats why some user had idea that i expand file by file which is possible and I may add it into beta 2...if you're interested in testing in 2 days, when i'll be done, send me PM.


@rivimey, uh, if your iso was too small, below 90mb then something was wrong, it would help if you try to make it again, use latest version and delete nlite before second try, reinstall it.
Did you removed any drivers...maybe your cab was corrupted too but lets not think that, your asms error is different. That shouldn't happen, ever...maybe sata/raid integration went bad...which driver is it...

The iso image was about 620MB -- seemed reasonable. I forgot to say earlier that I enabled the "recompress cabs" option.

I didn't remove any drivers, just added two for raid disks (which seemed to work, in that setup could see the raid arrays, and can't otherwise)

I did try again, this time doing only a xp sp1a => xp sp2 translation. This produced a 625MB iso. Sadly I can't persuade setup to load properly from that because it hasn't got the raid drivers, and won't see the USB floppy (Arrrgh!) It seems fairly happy up to that point though (can't find hard disks).

Pretty sure the driver cab wasn't corrupt, either in the original or in the created version. Haven't checked the others.

Dont understand about deleting nlite: why will that help any?

Must do some work now :-(

Ruth

@rivimey

I think he meant for you to uninstall/delete you current copy of Nlite, then reinstall it and begin process from beginning?

GOT IT TO WORK

I found this forum by searching for some of my missing files. I'm just a novice user who was trying to do a fresh install of XP and got errors about missing files. I don't know anything about nLite, so this may/may not apply.

When I first tried to install, it was on an NTFS single-partition hard drive (12GB). That's when I got the errors.

I then reformatted the HD as FAT32 and the installation ran without a hitch.

I hope this helps someone.

Just for informational purposes, i have a retail copy of Windows xp sp2 corp and i am still missing files through the setup process.

Try creatin another .ISO with the same nLited folder. See if the files missing change.

I dont it may not make sense ... But it has happened!

win xp home/pro OEM would not install and I received multiple error messages like the rest of you.

Checked the system. RAM memtest - no fault. Another CD, another HDD, still the same.

The memtest of RAM showed no problems but I changed the RAM block anyway, and now - no problems. Afterwards I installed WIN home on one partition and WIN PRO on another partition (XOSL) - both OEM.

So if you can borrow some RAM try it out.

I also found this forum by searching for info on missing files during Win XP Pro install. I am using the Win XP Pro w/SPK2 OEM CD from the Microsoft Action Pack. The first problem I have when installing on a reformatted drive is the "missing tosdvd.sys" warning. Searching for the missing file in the .CAB files on the disk reveals no file of that name on the disk.

I am not using nlight. It sounds like a great product but what I really need is a solution to the problem above.

Thanks

I finally figured out the problem. A bad memory module. Downloaded and ran "Memtest" from http://www.memtest.org and there were lots of errors. No problems now. I had never seen something like this before. On several of the reformat/reinstalls of Win XP Pro/Spk 2 I did get the install to work. Once installed though other software would report errors from the disk during install just like the Windows install would. Live and learn I guess.

I had the same sympthomes:
at copying setupprog reported missing files which were really present in the driver.cab
some of these were: streamci.dll, toscdvd , tsbcap.sys, usbcamd.sys, wowfax.dll, usrcntra.dll, usr...

Solution: Ram test (http://www.memtest.org/) and a ram-change because of broken rams.

Just like the others, I found this forum via google search. Same issue, I had to format because HALF MY OS just up and dissapeared.

I'll try to run memtest after (if) I get windows installed.

Thanks for a really great tool, please keep up the good work

Problem solved

besides files being driver files.
what files / drivers are you adding within nlite?
and what are you attempting to remove?

Problem solved

UPDATE on my problem

After further investigation, I discovered that a single file in driver.cab was faulty, that was the culprit, I guess my CD is a return to store for a swap.

I could get all the files that was missing, but the file that was faulty was not one of them, so I had to unpack the whole driver.cab to find it

Anyway, sry. if I made to much noice.

there's obviously multiple problems here...

@asflyboy
when memtest finds problems, that doesn't necessarily mean your memory is bad. the timings or voltage could be wrong (i always have to up the voltage in my case or i get errors as well). if you poke around on the web, you'll find the proper settings for your particular memory. just wanted to mention that before you go and buy new modules

@every one else...
as for nLite not copying files from NON-OEM installations, others have evidentially found that their CD/DVD drives may be the problem in some cases. the drives could possibly be getting to hot during the read, or were burned at too slow of a speed. suggestions:

1) update the drives firmware. the codeguys is a great resource for hacked firmware that can fix problems with the manufacturers firmware and enable 'hidden' features for the drive. of course it could potentially create problems as well, though i've had good success with their firmware (in one instance i successfully turned my single layer DVD burner into a double layer burner) . you can always turn to your vendor for firmware as well.

2) this is not the 'final word', but i read a very good article about burning speeds. it states to ALWAYS burn at the MAXIMUM speed supported by your burner/firmware/media and goes on to explain exactly why. one reason is heat - if you run a fast burner at a slow burn speed, you'll heat up the disk which can lead to problems, including data corruption. if i remember right, this is because the laser is more powerful in fast burners, so it doesn't have to sit in one place as long to burn correctly.

3) if setup won't copy files, just stop where you're at and try just letting the drive cool down for several minutes, then click 'retry'. if they copy then, you know the drive got too hot during the read.

4) if you went and bought a bundle of no-name CD's, well, you often get exactly what you pay for. they may work fine for MP3's, but may fail miserably when copying important data. you'll notice that on good media, it says right on the package that it is 'CERTIFIED' to burn at 'x' speed. cheap media doesn't have that certification. who certifies it, i don't know.

5) if you bought a no-name burner... need i say more. the same may hold true if you have an OEM burner that was supplied in an OEM machine.

as for nLite not working properly with OEM installation sources, i can only guess, but my guess would be that OEM installations are often (if not always) modified to suite the desires of the manufacturer. i could see where nLite may have serious problems in this case, though nuhi would be the one to query on this.

as for suspicions of nLite not working on OEM machines in some instances (when using a NON-OEM installation), i wouldn't doubt that at all, though it's probably not the fault of nLite. again, OEM machines often use customized installations of windows. for instance, my box at work is an HP Pavilion (100% piece of JUNK). after i got sick of XP home, i decided to load XP Pro on it. that was the end of the on-board sound chip - i could not get a driver to install to get the sound working and eventually used an extra sound card i had lying around.

A final note.

I got my Faulty XPproRetail swapped to a new, and now I have tested Nlite, and every things works as a treat, thanks again for a truly GREAT tool, now I have a MyPrivateFlavourXP fully updated and tweeked, with size reduce by approx 200MB, witch leaves room for Avast/ZoneAlarm/HWDrivers/Codecs/and a bunch of other things, all this on one CD that runs unattended

I can't get my arms down , NICE work on the Nlite

After having similar problems I started to play around with my driver.cab and noticed, after doing an archive test in winrar that my driver.cab was corrupt. I thought this was suspicious so I checked my driver.cab on my CD and the backup one that is coped over to the windows folder on my C drive during install. Both were corrupt. I believe that nlite was not able to read the entire archive as it should Thus causing missing files in the new compressed driver.cab created by nlite. I got another XP pro CD and copied the driver.cab, same file size as the other corrupt one, over and everything worked fine after that. I tested my new driver.cab and this one passed the archive test in winrar. Hope this will help some of you.

I recently ran into this problem myself. The list provided in the first post of this thread matched mine completely. Just for the heck of it, I decided to re-create the iso using the exact same profile as before - The only difference was that I disabled the "Recompress cab files" option.... I burned another CD with this iso and it installed just fine!

At this point, I am tempted to say that the problem was simply a cd burning issue... However, if this was the case, why would the list of missing files be identical to others in this forum? I'm still suspecting a bug in nLite recompress cab option, but I have enabled it in the past without this problem. I guess the jury is still open...

I hope this helps someone.

i had the problem like the others, but i have some new information and a new question.

how come during installation of nLite customed CD (winxp sp2) on my hp presario 732 i get errors of missing files (not exactly like others) like:
cdaudio.sys
cinemst2.sys
cpqdap01.sys
driver.cab
dvdplay.exe
crusoe.sys
dmutil.dll

*i should say that when installing from an original XP CD - it worked fine!

and when i install this same customed CD on a virtual machine i get no errors at all?
can you explain this?
i mean no memory / no hdd / no cd problems - that leaves us with what??????

i can't even guess why!!

using nlite 1.4 beta I was able to integrate all hotfixes and ie7 into these files:

06/01/2005 12:55 PM 573,765,632 en-home-oem-sp2.iso
05/23/2006 03:24 PM 606,691,328 en-home-rtl-sp2.iso
05/23/2006 03:20 PM 654,419,968 en-pro-oem-sp2.iso
05/23/2006 03:22 PM 656,840,704 en-pro-rtl-sp2.iso
07/03/2007 01:47 PM 609,835,008 en-pro-vlk-sp2.iso

Everything was successful, with no errors. Here are the results:

07/03/2007 08:02 PM 609,331,200 en-home-oem-070307 drivers.iso
07/03/2007 07:58 PM 590,092,288 en-home-oem-070307.iso
07/03/2007 08:51 PM 638,763,008 en-home-rtl-070307 drivers.iso
07/03/2007 08:47 PM 624,070,656 en-home-rtl-070307.iso
07/03/2007 07:04 PM 691,038,208 en-pro-oem-070307 drivers.iso
07/03/2007 07:00 PM 671,772,672 en-pro-oem-070307.iso
07/03/2007 07:41 PM 693,458,944 en-pro-rtl-070307 drivers.iso
07/03/2007 07:23 PM 674,193,408 en-pro-rtl-070307.iso
07/03/2007 05:43 PM 730,003,456 en-pro-vlk-070307 drivers.iso
07/03/2007 03:59 PM 624,150,528 en-pro-vlk-070307.iso


I had a lot of trouble until I got better images. Thanks a lot nuhi. Next step is to tackle x64 xp, then vista!

dhtjdd, maybe on real machine it detected some hardware which files are in the driver.cab.
But it's weird not to have that cab on the CD, never heard about that one.

habys, so I can ignore the IE7 integration problem you had in the other topic? Please post there if it's solved.