[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.