Build Errors relating to following files, 1394bus.sys enum1394.sys ohci1394.sys Options

[robakam]

I have had no problems with any versions of the UBCD for Windows (previous).

I have deleted all old pebuilder folders prior to trying this version.

I am trying the default setup.

My build fails with 3 errors:

Error: SetupDecompressOrCopyFile "R:\i386\C:\WINDOWS\system32\drivers\1394bus.sys" to "E:\Software Repository\UBCD4Win\pebuilder313\BartPE\i386\system32\drivers\C:\WINDOWS\system32\drivers\1394bus.sys" returned error 3: The system cannot find the path specified.

Error: SetupDecompressOrCopyFile "R:\i386\C:\WINDOWS\system32\drivers\enum1394.sys" to "E:\Software Repository\UBCD4Win\pebuilder313\BartPE\i386\system32\drivers\C:\WINDOWS\system32\drivers\enum1394.sys" returned error 3: The system cannot find the path specified.

Error: SetupDecompressOrCopyFile "R:\i386\C:\WINDOWS\system32\drivers\ohci1394.sys" to "E:\Software Repository\UBCD4Win\pebuilder313\BartPE\i386\system32\drivers\C:\WINDOWS\system32\drivers\ohci1394.sys" returned error 3: The system cannot find the path specified.

All other files have without the c:\windows (example):
"R:\i386\OLEAUT32.DLL" to "E:\Software Repository\UBCD4Win\pebuilder313\BartPE\i386\system32\OLEAUT32.DLL"

Any help would be appreciated . Thanks in advance.

[stidyup]

Is R your CDRom?

If it is try copying the contents of your XP CD to your HDD.

It's very odd it's sticking a C: in your file path, I've not seen that before. Have you added any other non-ubcd4win plugins?

[robakam]

Yes R is my CD ROM.
No extra plugins or drivers added.
I have used the same PC and folders, but emptying them first, with all other builds and no errors until now.
As always I first do a default install.

[SteelTrepid]

It's the new USB plugin. I forgot to modify a few things in it before sending out the new version. However, I don't understand why it's changing the path like that. I'm sorry I don't have more time to figure out a fix for this, I'm running late for work. At least wanted to let everyone know where the problem was.

[stidyup]

As a quick fix

;\WINDOWS\system32\drivers\
;only for IEEE1394
C:\WINDOWS\system32\drivers\1394bus.sys=4
C:\WINDOWS\system32\drivers\arp1394.sys=4
C:\WINDOWS\system32\drivers\enum1394.sys=4
C:\WINDOWS\system32\drivers\nic1394.sys=4
C:\WINDOWS\system32\drivers\ohci1394.sys=4

Add ; to the above so it appears like this or just cut and paste the below into the relevant section in the usb1394.inf

;\WINDOWS\system32\drivers\
;only for IEEE1394
;C:\WINDOWS\system32\drivers\1394bus.sys=4
;C:\WINDOWS\system32\drivers\arp1394.sys=4
;C:\WINDOWS\system32\drivers\enum1394.sys=4
;C:\WINDOWS\system32\drivers\nic1394.sys=4
;C:\WINDOWS\system32\drivers\ohci1394.sys=4

The above is for firewire so I don't think they'll have any impact on USB functionality, I not going to swear on that but at least doing this should get the CD to build until Steel can find a solution to the problem.

Have you got a firewire port installed on your PC?

Please post back if this fix has any unintended problems.

I've now found the 3 missing files.

All 3 files are in the drivers.cab file in the I386 folder, updated ohci1394.sys and 1394bus.sys can be found in sp1.cab and sp2.cab

If you want to extract the missing 3 files and place in the plugin\usb folder then mod the inf in the USB plugin to look like this:

;\WINDOWS\system32\drivers\
;only for IEEE1394
1394bus.sys=4
C:\WINDOWS\system32\drivers\arp1394.sys=4
enum1394.sys=4
C:\WINDOWS\system32\drivers\nic1394.sys=4
ohci1394.sys=4

Hopefully this should correct the problem.

[robakam]

That did the trick.
Thank you for the quick and direct responses.
I did the first option of commenting out the files. I will try the other option of extracting the files later.
No firewire installed.

Again thanks.

[stidyup]

Not having a firewire port is what's caused the problem as to why the build failed, windows won't install drivers for something it doesn't need so that's why pebuilder can't find the files. You won't be the only one who suffers from this problem (I'll probably change the title of your post).

If you try using the CD you may get a couple of error messages whilst loading relating to the above files, not sure if that will make the ubcd4win unusable.

Glad we could help.

[cap]

From instructions to this plugin (http://www.anwald.com/)

This plugin reads out all necessary registry-entries from the user-registry to avoid
complications with different languages or different hardware-configurations!


After building the REG-file, the windows-path within the file (e.g. "C:\\Windows")
has to be changed to "%systemroot%" - you can replace it using the windows-editor (Notepad).

At least you can delete all of the "Windows Registry Editor Version 5.00"-entries, except the
first one - this is ABSOLUTELY necessary! For this you can also use Notepad, just leave the
the second line empty when replacing
Good luck!

cool400.

This post has been edited by cap: Apr 11 2005, 04:54 AM

[phuqmnb]

I had the same 3 errors. Commenting did the trick for those, but I have an additional 4 errors. They are with the following files:

iastor.sys
a320raid.sys
aarich.sys
aac.sys

[stidyup]

Are you using a Dell Recovery CD?

See this topic here

If you have the latest ubcd4win V2.5 enable the Dell Fix plugin, this should solve your problem.

Which will find the following files

iastor.sys=4
a320raid.sys=4
aarich.sys=4
aac.sys=4

[phuqmnb]

No, I did have the Dell fix on by mistake. I turned it off and I was able to build the ISO. Thanks.

[robakam]

Just to follow up, I have tried the new build and was able to create the iso without any errors.

[stidyup]

Thanks for the feedback. (IMG:http://www.ubcd4win.com/forum/style_emoticons/default/smile.gif)