Help - Search - Members - Calendar
Full Version: Creating UBCDWin was working, now won't... help pls.
UBCD4Win Forums > Main Forum: UBCD4Windows - Support > General Questions
grindy
I sucessfully created a couple of UBCDWin boot CD's, but now it won't. At the end of the log it mentions that it can't find 'BOOTSECT.BIN' if that's the reason... here's that part.

QUOTE
sysid ""Win32"" -no-emul-boot -boot-load-size 4 -hide boot.catalog -allow-lowercase -R -b BOOTSECT.BIN -hide BOOTSECT.BIN -o "C:\ubcd4win\UBCD4WinBuilder.iso" . 2>&1 | mtee /+ C:\ubcd4win\autobuild.log
Warning: creating filesystem that does not conform to ISO-9660.
Warning: Creating ISO-9660:1999 (version 2) filesystem.
Warning: ISO-9660 filenames longer than 31 may cause buffer overflows in the OS.
/cygdrive/c/ubcd4win/temp/mkisofs: Uh oh, I cant find the boot image 'BOOTSECT.BIN' !
ISO succesfully created


My directory structure is:
C:\ubcd4win
and the BOOTSECT.BIN is located in C:\ubcd4win\BartPE

thx
rdsok
Did you recently install or update cygwin? Is cygwin in your system path?
cdob
@grindy

Does file C:\ubcd4win\BartPE\BOOTSECT.BIN or C:\ubcd4win\BartPE\bootsect.bin exist?
Case is importand.

Post some more lines, include the hole mkisofs command line.

Do you use a virus scanner?
grindy
Well, I re-downloaded UBCD4Win and re-installed it.
I thought all was fine, because I was able to create an ISO which I burned and made a bootable CD that works just fine.
After that, I went back to do another one ( after updating the virus and malware apps using the config option which went fine as usual ). However, the process failed as below: ( I've copied what I believe are the pertinant areas ).


QUOTE
Processing INF file: "C:\ubcd4win\plugin\Multiboot-003\bcdw\bcdw_logo.inf"
Section: AddLine
Error: cannot find file: U‹ìjÿh½PF
Error: addLine() failed 0: The operation completed successfully. (Line 0 String "BCDW\BCDW.INI,InitOptions,logo")
Processing INF file: "C:\ubcd4win\plugin\Multiboot-003\memtest86\memtest.inf"
Section: Append
Error: cannot find file: BCDW\BCDW.INI
Error: appendFile() "C:\ubcd4win\plugin\Multiboot-003\memtest86\" returned error 87: The parameter is incorrect. ().

Processing INF file: "C:\ubcd4win\plugin\Network\bartpe\bartpe.inf"
Section: Append

Processing OEM file: C:\ubcd4win\drivers\SCSIAdapter\VIA\sata_raid_ide_s\TXTSETUP.OEM
SCSI hardware ID: VIARAID_VT3149_XP, component: VIA Serial ATA RAID Controller(Windows XP)
Adding PnP ID: PCI\VEN_1106&DEV_3149
Processing OEM file: C:\ubcd4win\drivers\SCSIAdapter\Ximeta\ALL_NetDisk\txtsetup.oem
SCSI hardware ID: NetDisk_XP, component: WinXP Ximeta NetDisk Network Drives NDAS
Checking for missing files
Builder has stopped because there are 4 build errors
No CD/DVD is burned, you must fix the errors!
Building done...
There where 4 errors and 0 warnings


Can you give me a hand figuring out what is happening please?
Thx for any input... smile.gif
bengt
For this error:
Error: addLine() failed 0: The operation completed successfully. (Line 0 String "BCDW\BCDW.INI,InitOptions,logo")

Open up the "C:\ubcd4win\plugin\Multiboot-003\bcdw\bcdw_logo.inf"
and have a look at the: AddLine Section:
does it say:
"BCDW\BCDW.INI,InitOptions,logo"

it should be:
"BCDW\BCDW.INI","InitOptions","logo"

the append section in memtest.inf:
BCDW\BCDW.INI,memtest_bcdw.ini
cdob
@grindy
Plugin "!Multiboot: BCDW: Enable Boot Logo" does work.

Did you tested md5sum after download?

Did you disabled plugin "!Multiboot: BCDW (Required for MultiBoot)"?
Disable all MultiBoot plugins or keep this requied one.
James G.
Hello, first time post here.

I am having same error.

story is:
we created a disk to boot up multiple systems and install a ghost image on. it worked fine on one system, then i get viamraid.sys error on the other 5 motherboards we have. i then removed some folders of drivers and now i get an iso of 34kb and a message about 'bootsect.bin' not being found. i do a search of it and there are two instances on my computer in the ubcd or bartpe file structure.

i dont know what else is needed, but if someone has a clue or needs more info to assist with this, i'd appreciate it.
thanks
cdob
QUOTE
i then removed some folders of drivers and now i get an iso of 34kb and a message about 'bootsect.bin' not being found.
Does message read 'BOOTSECT.BIN' or 'bootsect.bin'? Post full command line.

QUOTE
i do a search of it and there are two instances on my computer in the ubcd or bartpe file structure.
Does file bootsect.bin or BOOTSECT.BIN exist?
Strange, ubcd bootsect.bin dosn't sound good.
Where is ubcd and bartpe located? Name full path.
What's your output folder?

Which step did you do? Which files did you deleted?
Did you rerun UBCD4WinBuilder?

Do you use a virus scanner?

Or start again, get UBCD4win files. Expand files and rerun.
James G.
I am having the same errors as the guy above. i have checked all file structures and they are compliant with the 'no spaces' rule. i have one bootsect.bin and it appears in my \bartpe folder after creation of the ubcd4win project.
\ubcd\bartpe
\ubcd

this is getting ridiculous. i make 1 good disk, then on the next project i have to remove the complete file structure, reextract and change all settings again, then hope it works.
i cant be the only one having this problem.
does mcafee have an issue with allowing files to be manipulated within this program? i am out of ideas.



QUOTE(cdob @ Nov 2 2006, 10:03 AM) *

QUOTE
i then removed some folders of drivers and now i get an iso of 34kb and a message about 'bootsect.bin' not being found.
Does message read 'BOOTSECT.BIN' or 'bootsect.bin'? Post full command line.

QUOTE
i do a search of it and there are two instances on my computer in the ubcd or bartpe file structure.
Does file bootsect.bin or BOOTSECT.BIN exist?
Strange, ubcd bootsect.bin dosn't sound good.
Where is ubcd and bartpe located? Name full path.
What's your output folder?

Which step did you do? Which files did you deleted?
Did you rerun UBCD4WinBuilder?

Do you use a virus scanner?

Or start again, get UBCD4win files. Expand files and rerun.

dirkgently42
@James G.
#1 recommendation : please review the "how to build" instructions and the FAQ on the main page

QUOTE(James G.)
I am having the same errors as the guy above.

That's a little vague, please state/post the exact errors you experienced. I doubt that you got all of the same errors reported by grindy. Every computer system is different, so it's kinda silly for anyone to assume that you experienced the exact same scenario and errors as grindy reported.

QUOTE(James G.)
i have checked all file structures and they are compliant with the 'no spaces' rule. i have one bootsect.bin and it appears in my \bartpe folder after creation of the ubcd4win project.
\ubcd\bartpe
\ubcd

Is it possible that you mixed UBCD with UBD4WIN?... just suggesting a possibility

You managed to quote CDOBs' helpful questions, but you didn't provide any relevant answers.

If all else fails due to your particular security software and settings (McAfee)... try a fresh build from scratch in safe mode and follow the "how to build" instructions exactly.
Get at least one "vanilla" build ( don't change any settings and don't add any plugins) under your belt before experimenting.
Master the "vanilla" build and determine whether you need to make adjustments for drivers required for your specific hardware.
If you don't need to add any drivers and have a good bootable disc, then by all means make whatever changes you need to your own custom builds, including adding plugins.
James G.
[color=#FF0000]I have removed the complete UBCD directory and reinstalled UBCD4WIn, before your post. now i am receiving 'mtee' is not a valid internal or external command, error.
as far as vanilla goes, removing all the programs i dont want to install is more vanilla than the default settings.
i have read the howto, and its not explaing jack crap about the plugins. there are some that say !critical, yet arent turned on by default. my previous error about bcdw.ini and bootsect.bin were just as they were posted above, didnt think i had to retype or cut and paste another paragraph. what you saw above was what i had. i also realized, that was my previous post.
I have followed your instructions and believe it may be we mixed UBCD and UBCD4WIN.

but i am not in Ubcd4win and getting the mtee message. can anyone extrapolate what this means??? i thought it was a switch for mkisofs command?

thanks to all.

QUOTE(dirkgently42 @ Nov 21 2006, 10:16 PM) *

@James G.
#1 recommendation : please review the "how to build" instructions and the FAQ on the main page

QUOTE(James G.)
I am having the same errors as the guy above.

That's a little vague, please state/post the exact errors you experienced. I doubt that you got all of the same errors reported by grindy. Every computer system is different, so it's kinda silly for anyone to assume that you experienced the exact same scenario and errors as grindy reported.

QUOTE(James G.)
i have checked all file structures and they are compliant with the 'no spaces' rule. i have one bootsect.bin and it appears in my \bartpe folder after creation of the ubcd4win project.
\ubcd\bartpe
\ubcd

Is it possible that you mixed UBCD with UBD4WIN?... just suggesting a possibility

You managed to quote CDOBs' helpful questions, but you didn't provide any relevant answers.

If all else fails due to your particular security software and settings (McAfee)... try a fresh build from scratch in safe mode and follow the "how to build" instructions exactly.
Get at least one "vanilla" build ( don't change any settings and don't add any plugins) under your belt before experimenting.
Master the "vanilla" build and determine whether you need to make adjustments for drivers required for your specific hardware.
If you don't need to add any drivers and have a good bootable disc, then by all means make whatever changes you need to your own custom builds, including adding plugins.

James G.
This is what i am getting now from ubcd4winbuilder.log

Build ISO image
Running external program
C:\UBCD4WIN\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:\UBCD4WIN\iso\UBCD4Windesktop.iso" "C:\UBCD4WIN\BartPE"
Could Not Find C:\UBCD4WIN\pebuilder.log
'mtee' is not recognized as an internal or external command,
operable program or batch file.
Building ISO image done
Building done...


what now? why does this program take so much headache to run?
before this, i wiped all ubcd folders/files, reinstalled ubcd4win, ran the initial setup config and then ran the build using defaults and got several errors on bcdw.ini, dban, and two others, i removed them from the list of plugins and others i didnt want, then i got the error above.

again, the defaults arent working when i follow the instrucitons for installing, they arent working. i need the errors i have mentioned addressed, if anyone knows the answers.

thanks for trying.


QUOTE(James G. @ Nov 22 2006, 07:38 AM) *

[color=#FF0000]I have removed the complete UBCD directory and reinstalled UBCD4WIn, before your post. now i am receiving 'mtee' is not a valid internal or external command, error.
as far as vanilla goes, removing all the programs i dont want to install is more vanilla than the default settings.
i have read the howto, and its not explaing jack crap about the plugins. there are some that say !critical, yet arent turned on by default. my previous error about bcdw.ini and bootsect.bin were just as they were posted above, didnt think i had to retype or cut and paste another paragraph. what you saw above was what i had. i also realized, that was my previous post.
I have followed your instructions and believe it may be we mixed UBCD and UBCD4WIN.

but i am not in Ubcd4win and getting the mtee message. can anyone extrapolate what this means??? i thought it was a switch for mkisofs command?

thanks to all.

QUOTE(dirkgently42 @ Nov 21 2006, 10:16 PM) *

@James G.
#1 recommendation : please review the "how to build" instructions and the FAQ on the main page

QUOTE(James G.)
I am having the same errors as the guy above.

That's a little vague, please state/post the exact errors you experienced. I doubt that you got all of the same errors reported by grindy. Every computer system is different, so it's kinda silly for anyone to assume that you experienced the exact same scenario and errors as grindy reported.

QUOTE(James G.)
i have checked all file structures and they are compliant with the 'no spaces' rule. i have one bootsect.bin and it appears in my \bartpe folder after creation of the ubcd4win project.
\ubcd\bartpe
\ubcd

Is it possible that you mixed UBCD with UBD4WIN?... just suggesting a possibility

You managed to quote CDOBs' helpful questions, but you didn't provide any relevant answers.

If all else fails due to your particular security software and settings (McAfee)... try a fresh build from scratch in safe mode and follow the "how to build" instructions exactly.
Get at least one "vanilla" build ( don't change any settings and don't add any plugins) under your belt before experimenting.
Master the "vanilla" build and determine whether you need to make adjustments for drivers required for your specific hardware.
If you don't need to add any drivers and have a good bootable disc, then by all means make whatever changes you need to your own custom builds, including adding plugins.


SteelTrepid
Getting frustrated will not solve ANYTHING!
There are THOUSANDS of users that have NO problems creating the project CD. Yes this is an error that has been happening to a few people over the past few weeks maybe months.

This project has been around for almost 3 years now and I have seen and heard just about everything! In most of these cases it is almost always some silly little detail being left out or being messed up by the end user. We are doing the best to help you, however I think in most of these issues here.....we need more information.

I tried to research this problem a little more and can only find posts about mtee being messed up in other language versions of XP. One user fixed this error by using an English copy of XP instead of his native language of XP. I am also thinking that some antivirus software messes with the file too. However that has been suggested and according to at least one person in this post it didn't work for him.

I have to get back to work now though for my paying job. Like I mentioned, please provide more information. What you have tried, what version of XP you have, what language of XP you have, do you have your AV software disabled when building, have you tried safe mode, etc., etc.
James G.
* Please send log file via email or via RapidShare or MegaUpload. It wont allow you to post it all here as its far too large. Thank you and sorry for the inconvenience. :-) *
James G.
i just tried it in safe mode. same error about 'mtee'.
anyone have any ideas? bueller. bueller........
LittlBUGer
QUOTE(James G. @ Nov 22 2006, 10:02 AM) *

i just tried it in safe mode. same error about 'mtee'.
anyone have any ideas? bueller. bueller........


Please read your post I edited above. Thanks.
James G.
if anyone wants to see the logfile or a portion of it. let me know. i am stuck at this point.
thanks though.
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-2006 Invision Power Services, Inc.