Help - Search - Members - Calendar
Full Version: Build Errors
UBCD4Win Forums > Main Forum: UBCD4Windows - Support > General Questions
coolio
Hi,

I am using Bart PE v 3.1.10
I downloaded UBCD4WINV26 , its about 84.4mb and also UBCD4WinDriversV18FINAL about 16.1mb
I followed the instructions under the How to Build Link and even watched the video(its pretty cool).
I am using a win xp sp2 cd copied to my HD
I am getting the following errors after going through the build process

Checking for missing files
Error: File "vmscsi.sys" not found
Error: File "Si3124r.sys" not found
Error: File "PnP680r.sys" not found
Error: File "Pnp680.sys" not found
Error: File "PnP649r.sys" not found
Error: File "ql2200.sys" not found
Error: File "ql2100.sys" not found
Error: File "aftx2k.sys" not found
Error: File "MegaIDE.sys" not found
Error: File "raidsrc.sys" not found
Error: File "hptmv6.sys" not found
Error: File "hpt366.sys" not found
Error: File "hptmv.sys" not found
Error: File "rhpt3xx.sys" not found
Error: File "atiide.sys" not found
Error: File "atiide2k.sys" not found
Error: File "arcm_x86.sys" not found
Error: File "amdbusdr.sys" not found
Error: File "m5287.sys" not found
Error: File "m5281.sys" not found
Error: File "m5228.sys" not found
Error: File "cda1000.sys" not found
Error: File "AADPU320.SYS" not found
Error: File "aar1210.sys" not found
Error: File "ahpt3xx.sys" not found
Error: File "AEC671X.SYS" not found
Error: File "AEC67160.SYS" not found
Error: File "aec6897.sys" not found
Error: File "AEC6880.SYS" not found
Error: File "aec68X5.sys" not found
Error: File "AEC6280.SYS" not found
Error: File "aec6260.sys" not found
Error: File "aec6210.sys" not found
Builder has stopped because there are 33 build errors
ISO image is not created, you must fix the errors!
Building done...
There where 33 errors and 0 warnings
Use the [<<] and [>>] buttons to jump to Error/Warning.

i found that all of those files are on the cd but compressed as" .sy_ " files. I extracted them and put them in the same directory as my xp cd and even tried putting them into the i386 directory and ran the build again and same errors.

Any ideas where I am going wrong please, thanks.
SteelTrepid
Those all look like driver files. I haven't had the time to build with the latest version of the drivers yet, so I can't really offer any assistance.
Where is LittlBUGer when I need him?? smile.gif
LittlBUGer
Can you please explain exactly what you did to build the CD with the driver pack? I know that there weren't any errors when I tested before release and also when a few others tested as well, so I doubt it's my driver pack alone. More information on your system may be helpful too. Thanks. smile.gif
rdsok
Just to second LittlBUGer.. I've also not seen any errors using that driver pack...
coolio
I followed the steps exactly like in the video on the how to build page. For the driver pack i extracted it into the drivers directory in pebuilder. I am trying it on a pentium 4 Dell Latitude Laptop 1.6Ghz with 256mb ram. Running windows xp professional with no service packs. The Cd I am using is a win xp sp2 cd. (haven't had a chance yet to upgrade the service pack on the laptop, low on hd space) I also tried slipstreaming another winxp cd i have with sp2 english and tried to run it with that and got 38 missing files. Both XP cd's that I have tried are not original, one I got from the web and the other one I got from a friend. Do you think it might be a bad copy of xp cd's that I have.
coolio
It turns out to be a cd problem. I got my hands on a media center 2005 cd which I know is original and built it with that and I was fine. Sorry about bringing it up here, I should have thought of it first wall.gif. I ran the cd and tried it and it works great.

Is there a way of booting into dos mode with the cd, I know the cd has dos prompt in windows, but is there a way to actually get to real dos to run programs, that can only be run in dos
SteelTrepid
For DOS, try the original UBCD.

Sorry to jump to conclusions and assume that it might be the driver package. I should have tried asking for more information, instead of trying to pull something out of my ass.
BTW- I finally updated some stuff on the site last night. The download page now lists 1.8, I just need links from the other mirrors, etc.
nom
QUOTE (LittlBUGer @ Mar 26 2006, 08:09 PM) *
Can you please explain exactly what you did to build the CD with the driver pack? I know that there weren't any errors when I tested before release and also when a few others tested as well, so I doubt it's my driver pack alone. More information on your system may be helpful too. Thanks. smile.gif



hello LittlBUger.
thank you for prompt reply.
per your advice, downloded latest verisons.
it worked.

once again thank you.
Cellar Dweller
QUOTE (coolio @ Mar 26 2006, 06:58 AM) *
Hi,

I am using Bart PE v 3.1.10


You need to be using 3.1.10a... This might be the issue but that's odd you had that many errors... Whoops a litle late with my reply... wall.gifGlad you figured out the issue. I had similar issues once with XP SP2 CD and obviously it was having strange READ problems. I now copy the CD to Hard Drive and keep a copy there for Barts and UBCD4WIN and actually always do this for all my OS installs so you never have to pull the CD again once you're up and running a flawless OS...


To LittleBug - just want to say nice job and I see you added Perc 4. I was going to PM you and ask if you wanted a good working set because I actually created them for doing Dell Severs at work and the set I had worked great. Thanks for the addition none the less...
bonobandit4
Easy on the newbie please! I'm getting a similar error during the setup within PE builder... log shows as follows.

Checking for missing files
Warning: File "vmscsi.sys" not found
Warning: File "viapdsk.sys" not found
Warning: File "viamraid.sys" not found
Warning: File "SISRAID2.SYS" not found
Warning: File "sisraid1.sys" not found
Warning: File "sisraid.sys" not found
Warning: File "Si3132r5.sys" not found
Warning: File "Si3132.sys" not found
Warning: File "Si3124r5.sys" not found
Warning: File "Si3124r.sys" not found
Warning: File "Si3124.sys" not found
Warning: File "Si3114r5.sys" not found
Warning: File "Si3114r.sys" not found
Warning: File "Si3114.sys" not found
Warning: File "Si3112r.sys" not found
Warning: File "Si3112.sys" not found
Warning: File "PnP680r.sys" not found
Warning: File "Pnp680.sys" not found
Warning: File "PnP649r.sys" not found
Warning: File "ql2300.sys" not found
Warning: File "ql2200.sys" not found
Warning: File "ql2100.sys" not found
Warning: File "ulsata2.sys" not found
Warning: File "ulsata.sys" not found
Warning: File "sptrak.sys" not found
Warning: File "fastsx.sys" not found
Warning: File "S150sx8.sys" not found
Warning: File "aftx2k.sys" not found
Warning: File "fasttx2k.sys" not found
Warning: File "fasttrak.sys" not found
Warning: File "symmpi.sys" not found
Warning: File "MegaIDE.sys" not found
Warning: File "jahci.sys" not found
Warning: File "iteraid.sys" not found
Warning: File "raidsrc.sys" not found
Warning: File "nfrd960.sys" not found
Warning: File "ipsraidn.sys" not found
Warning: File "rr2310.sys" not found
Warning: File "rr404.sys" not found
Warning: File "rr2320.sys" not found
Warning: File "hptmv6.sys" not found
Warning: File "hpt366.sys" not found
Warning: File "hptmv.sys" not found
Warning: File "hpt374.sys" not found
Warning: File "rhpt3xx.sys" not found
Warning: File "hpt3xx.sys" not found
Warning: File "ati3112r.sys" not found
Warning: File "arcm_x86.sys" not found
Warning: File "amdbusdr.sys" not found
Warning: File "m5289.sys" not found
Warning: File "m5288.sys" not found
Warning: File "m5287.sys" not found
Warning: File "m5281.sys" not found
Warning: File "m5228.sys" not found
Warning: File "cda1000.sys" not found
Warning: File "AADPU320.SYS" not found
Warning: File "ADPU320.SYS" not found
Warning: File "aar1210.sys" not found
Warning: File "ahpt3xx.sys" not found
Warning: File "AEC671X.SYS" not found
Warning: File "AEC67160.SYS" not found
Warning: File "aec6897.sys" not found
Warning: File "AEC6880.SYS" not found
Warning: File "aec68X5.sys" not found
Warning: File "AEC6280.SYS" not found
Warning: File "aec6260.sys" not found
Warning: File "aec6210.sys" not found
Warning: File "3waregsm.sys" not found
Warning: File "3ware78k.sys" not found
Warning: File "3ware9k.sys" not found
Build ISO image
Running external program
C:\UBCD4Winv3.0\mkisofs.exe -iso-level 4 -volid "The Ultimate Boot CD for Windows" -b bootsect.bin -no-emul-boot -boot-load-size 4 -hide bootsect.bin -hide boot.catalog -o "C:\UBCD4Winv3.0\pebuilder.iso" "C:\UBCD4Winv3.0\BartPE"
autobuild.cmd started at
Version: 2.0 beta4
Date: Wed 05/03/2006
Time: 11:42:12.48
-----------------------------------------
PEBuilderDir: C:\UBCD4Winv3.0
ISOfile : C:\UBCD4Winv3.0\pebuilder.iso
OutDir : C:\UBCD4Winv3.0\BartPE
PEUtilsPath : C:\UBCD4Winv3.0\temp
CD Label : UBCD4Windows

NEW flag is set - so preparations are done
Terminated by user...
There where 0 errors and 70 warnings
*************************************************

This appears to be the entire section of .sys files from my txtsetup.sif. What is going on? I'm using BTS driverpacks and running the automated slipstream. Everything seems to work fine, except for the auto file copy. I manually copy the files over. They're there - in the $OEM$\$1\D\ folders, but it's not seeing them. I'm using my company's volume license copy of WinXPSP2. I've re-run the slipstreamer twice, after downloading a new copy of the MassStorage driver pack. I can briefly see a screen echo of some of these files being processed during the slipstreamer, but still no joy. Any suggestions are greatly appreciated.

oh - and OEM Plug and Play drivers path seems to show all paths correctly also...
LittlBUGer
Try just using the standard 1.8 drivers and NOT the BTS ones. Thanks. smile.gif
bonobandit4
QUOTE (LittlBUGer @ May 3 2006, 02:32 PM) *
Try just using the standard 1.8 drivers and NOT the BTS ones. Thanks. smile.gif


I could, but I already know that works. I was just hoping to get my install directory slipstreamed with a comprehensive list of drivers...

I admit that I have 3 versions of Bartsbuilder/UBCD4Win builder on this pc, maybe I should just start from scratch?

Thanks! If anyone thinks of anything else, please post!
mbarnes
Hi bonobandit4

Bart pebuilder looks in \i386 folder for the files it needs, (whats in OEM folder is of no concern)

If the XP CD is non standard such as some recent oem recovey CD's then problems can occur.
(search on DellFix for more information, these are usually designed to incorporate SATA disk drivers to XP CD)
(This can prevent slipstreaming to SP2 in some cases)

PE Builder works better (faster) if the XP CD \I386 is copied to the hard disk. (say c:\XP-CD\i386)
The files WIN51xx and WIN51XX.SP2 are also needed especially if you need to slipstream XP or XP SP1 to XP SP2.

Then check sp2.cab & driver.cab with winRAR or winZIP to see if the contents can be extracted without error
Some XP CD's seem to have a corrupt driver.cab and some faulty:- CD/DVD drives / data cables / DMA settings seem to cause file corruption for large files

regards
Mike Barnes
bonobandit4
Some good suggestions mbarnes. Thank you. I am using a verified volume license XPSP2 installation CD, copied to my HDD. I think that PnP drivers get copied to the $oem$ folder for copy to the destination PC during uA installs. They're definitely there - eg; $oem$\$1\d\m\v\vmscsi.sy_. I assumed that this is where pebuilder was checking also. Are they supposed to also be in i386 for this process? How could I be affecting this portion of the slipstreaming process if that's not happening properly?

Win5.1 files are correctly placed.


I didn't think these were exclusive to the driver.cab since I know that vmware scsi drivers are not part of a stock windows installation. (vmscsi.sys) Plus, the file directories mimic exactly the bts directory structure.

Thanks again everyone!

Could McAfee 'on access' scanner be hosing any of this process?
hilander999
QUOTE
Could McAfee 'on access' scanner be hosing any of this process?
YES

It is always possible that AV software is causing build errors with ubcd4win. There are a number of files in the build that are known to send up "Flags" as "Suspicious" or "Hackware" just because of what they are designed to do.

The best thing to do is UNHOOK form the internet & Disable your Virus Scanner.
After you verify the build is complete, re-enable the AV software & only then re-establish your internet connection.

DO NOT FORGET to re-enable your AV Scanner BEFORE re-connecting to the internet.
bonobandit4
I usually get a McAfee popup when it encounters 'Tightvnc' viewer during the build process, and I hadn't seen it at all during the slipstream. It seems odd that it would kill the first 70 of my .sys files, but I'd try anything at this point.

Thanks!
Jaybee
I have been having similar problems to COOLIO but I do not get errors - I get 44 warnings

This is a portion of the log file that is produced

Checking for missing files
Warning: File "3ware95k.sys" not found
Warning: File "3ware9k.sys" not found
Warning: File "3ware78k.sys" not found
Warning: File "aec6210.sys" not found
Warning: File "aec6260.sys" not found
Warning: File "aec6280.sys" not found
Warning: File "aec68x5.sys" not found
Warning: File "aec6880.sys" not found
Warning: File "aec6897.sys" not found
Warning: File "aec67160.sys" not found
Warning: File "aec671x.sys" not found
Warning: File "ahpt3xx.sys" not found
Warning: File "aar1210.sys" not found
Warning: File "aadpu320.sys" not found
Warning: File "cda1000.sys" not found
Warning: File "amdbusdr.sys" not found
Warning: File "arcm_x86.sys" not found
Warning: File "m5228.sys" not found
Warning: File "m5281.sys" not found
Warning: File "m5287.sys" not found
Warning: File "m5288.sys" not found
Warning: File "rhpt3xx.sys" not found
Warning: File "hptmv.sys" not found
Warning: File "hpt366.sys" not found
Warning: File "hptmv6.sys" not found
Warning: File "rr2320.sys" not found
Warning: File "rr404.sys" not found
Warning: File "rr2310.sys" not found
Warning: File "iastrold.sys" not found
Warning: File "raidsrc.sys" not found
Warning: File "jahci.sys" not found
Warning: File "jraid.sys" not found
Warning: File "megaide.sys" not found
Warning: File "614x.sys" not found
Warning: File "aftx2k.sys" not found
Warning: File "ql2100.sys" not found
Warning: File "ql2200.sys" not found
Warning: File "pnp949r.sys" not found
Warning: File "pnp680.sys" not found
Warning: File "pnp680r.sys" not found
Warning: File "ati3112r.sys" not found
Warning: File "si3124r.sys" not found
Warning: File "vmscsi.sys" not found
Warning: File "ATIIDE.sys" not found
Build ISO image
Running external program

I am using PE Builder 3.1.10a and I produced an ISO file before copying it to a real CD

Unlike COOLIO, I do not think my problem is to do with my XP install disk as the all the
missing files were copied ok to my hard disk before PE Build. The relevant SY_ files were all copied ok to the hard disk (C:\XPCD\I386 etc)

The files in question have SY_ extensions. It looks like PE Builder is not picking up these files.

Can anyone please suggest a fix for this. surrender.gif

The new CD boots ok but when I select the option for a Windows boot it fails with the
message ATIIDE.SYS not found. Then it reboots again and again.

I checked the ISO file and the files are missing from that too wall.gif


Hope someone can help

Jaybee

PS I can post the complete log file if it will help.
LittlBUGer
Did you add any other plugins or driver packs?
Pihahiroth
QUOTE (bonobandit4 @ May 3 2006, 12:36 PM) *
This appears to be the entire section of .sys files from my txtsetup.sif. What is going on? I'm using BTS driverpacks and running the automated slipstream. Everything seems to work fine, except for the auto file copy. I manually copy the files over. They're there - in the $OEM$\$1\D\ folders, but it's not seeing them. I'm using my company's volume license copy of WinXPSP2. I've re-run the slipstreamer twice, after downloading a new copy of the MassStorage driver pack. I can briefly see a screen echo of some of these files being processed during the slipstreamer, but still no joy. Any suggestions are greatly appreciated.

oh - and OEM Plug and Play drivers path seems to show all paths correctly also...


I don't think you can use an $oem$ folder with your build (perhaps someone could confirm this?). You need to rely on a driver pack or plugin.

If you are referring to the txtsetup.sif in the i386 folder on your cd, try copying your i386 folder from the cd to your HDD, remove the offending entries from txtsetup.sif, and build from it. I had a similar problem with an OEM cd. The OEM added some extra drivers to txtsetup.sif in the
[SourceDisksFiles], [HardwareIdsDatabase], [SCSI.Load], and [SCSI] sections. Since I didn't have access to a "clean" XP source at the time, this was my only alternative. PEBuilder doesn't copy OEM files, so they show up as missing during the build.
Jaybee
@ LittleBuger

I have not experimented with plugins yet. I have gone straight for the build as the advice on the how to do file seemed to reccomend this. I have not yet experimented with pugins.

I have been using a fairly modern XP SP2 disk as a file source with WGA built in - I wonder if that could be the cause of the problem.

2 hours ago I tried using an old XP SP1 disk (This one is an OEM) and it worked perfectly apart from 1 warning this time instead of 44 warnings. That one warning was possibly telling me that OEM could cause problems.

The SP2 install disk I tried 1st was apparently a "student issue" and is not OEM

Is there much difference in the result if I use the SP1 OEM or a SP2 "student issue"?
It may be I have no choice if I cant resolve the missing file prob. on the SP2 vers.

Thanks

Jaybee

PS I tried copying files to the hard disk and also direct from the CD drive - same problem.






@ Pihahiroth

It seems very odd to me.. Your comments dont seem to apply here as the only disk I can get to work is an OEM issue

Thanks for the reply though..

Jaybee
Pihahiroth
You can use the SP1 disk, AFAIK, but be sure to go to the plugins section of UBCD4WINBuilder.exe and do the following.

Disable this: !Critical: DComLaunch Service [If a XP SP1 Build-DISABLE]
Enable this: !Critical: LargeIDE Fix (KB331958) [If a XP SP1 Build-ENABLE]

Build, and you should be good to go.

BTW, I receive an OEM warning when I build too. If that is the only warning that you receive, you have a good chance of getting a successful build.

QUOTE (Jaybee @ Nov 30 2006, 05:54 PM) *
@ Pihahiroth

It seems very odd to me.. Your comments dont seem to apply here as the only disk I can get to work is an OEM issue

Thanks for the reply though..

Jaybee


It doesn't have to be OEM to have problems. If it is a custom made CD and not a plain vanilla, you can have problems too. For instance, I have a custom built cd at work with all the drivers for all of the computers along with a bunch of integrated updates. PEBuilder won't know the difference between the two but may report missing files if they were added to txtsetup.sif. So, it is possible that your cd has drivers added there.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2009 Invision Power Services, Inc.