Posted 13 October 2011 - 02:43 AM
I am a newbie in programming or building a multi-boot CD. I downloaded UBCD4Win and set it up with WinXP and further tools. The CD/DVD of this ISO works fully.
When using XBOOT to make a multi-boot USB, the same UBCD4Win which worked flawlessly gives a BSOD.
If I add UBCD4Win.ISO using "PE - WinXP" the Xboot aborts with an error. If added via "Grub4DOS ISO emulation" XBoot finishes the process and then I get a BSOD on booting up UBCD4Win.
Please guide me.
Posted 13 October 2011 - 12:39 PM
Basically you are falling in the assumption that all .iso's are:
Please guide me.
- the same
- can be booted through grub4dos .iso mapping (or Syslinux memdisk)
You have to realize that this is not the case :
You need to build a RAMDISK booting UBCD4WIN if you want to boot it from a .iso on USB stick or the like.
Otherwise you will need a "flat" build and add it as "PE-WinXP", and not a .iso.
Posted 13 October 2011 - 02:36 PM
Point well taken.
I read the other topics and I still don't understand what is a flat build and how do I make it.
Posted 13 October 2011 - 03:13 PM
title UBCD4Win 3.6 map --mem (md)0x800+4 (99) map /images/firadisk.ima (fd0) map /images/firadisk.ima (fd1) map /images/UBCD4WinBuilder.iso (0xff) map --hook write (99) [FiraDisk]\nStartOptions=cdrom,vmem=find:/images/UBCD4WinBuilder.iso;floppy,vmem=find:/images/firadisk.img;\n\0 chainloader (0xff)Files are continuous, defrag files if necessary.
Posted 13 October 2011 - 03:16 PM
(though it is "BartPE related" it applies to *any* PE 1.x build)
you have a \minint\ (or \I386\ see here ):
directory containing the actual XP/2003 files, a directory \Programs\ and (normally) a SETUPLDR.BIN+NTDETECT.COM in the root of the stick.
(by using a bootmanager like grub4dos or similar you may have multiple \minint\ directories for different PE's - by means of a number of hexedited SETUPLDR.BIN's, each one renamed to something else and hex-edited to point at a different directory containing the XP\2003 files, but as you might easily imagine multibooting "flat" builds is more complex and more prone to conflicts than having a number of completely separate .iso's or .img's)
A flat build in other words is easier as a single boot option (and needs less memory/RAM of a .iso or .img RAMDISK one) but is more complex in a multi-boot PE stick.
Posted 13 October 2011 - 03:32 PM
Hi @ rafale_777
During some "free time" I created a script dedicated to USB devices (USB stickThumb-drive also working for USB harddisk unit).
Script is able to launch "normal ISO" ("normal" in respect ISO can be launched directly by grub)
However as Wonko the Sane point to, not all ISO's can be launched directly (or fully work correctly) without some "specially treatments" (using "frugal solution" or whatever)
Anyway, script is able to launch ISO build by UBCDWIN in a breeze.
As UBCDWIN is build from NT5-source (winXP or similar) you must in script check: Run ISO from RAM
Note: you need at least 1 GB RAM (2 GB recommended)
Attention! In script you have a button "Help" - please use it
Download script HERE
Note: Script is using WinBuilder-082 (included in download as script is optimized to run with that version of WinBuilder)
Posted 14 October 2011 - 05:42 AM
Thanks for explaining a flat build and the process of making it. I have made single boot USB before using flat build via a different process, but I did not know the jargon.
I would not be able to manage a multiboot environment with multiple flat builds.
I tried your script as well, my bootable USB is up and running but I am unable to multi-boot it.
Would I get a BSOD if I try to boot this USB in a system with 1gb RAM or less ?
But ... let me go back to basics and list my basic requirements.
A multi-boot swiss army USB with these tools in ISO
UBCD For Dos
Acronis True Image
Easeus Partition Master 9.0 (Optional)
Using XBoot I am able to boot into all tools except UBCD4win which gives a BSOD upon boot.
Posted 14 October 2011 - 07:04 AM
Quote: "Would I get a BSOD if I try to boot this USB in a system with 1gb RAM or less ?"
Let me put it this way:
Available RAM must have a size of at least more than 50% of your UBCD4Win build.
To be on the safe side, you are recommended to have twice the size of your UBCD4Win build.
This is recommended, as you load ISO to RAM and UBCD4Win itself need some RAM to work correctly.
However if you only have 1 GB RAM it still might work depending of what size UBCD4Win is
How about testing a much smaller UBCD4Win
Test disconnect most of plug-in to build a smaller UBCD4Win.ISO
This is mainly to check if it works at all
Posted 14 October 2011 - 12:54 PM
This is an excellent suggestion. I really do not need all the plugins included in the default build.
I have pared down my original 850mb build to 350mb. I need to deploy this mostly on computers with 512/1gb RAM.
I will try this on tonight with XBoot and report on the results.
Posted 14 October 2011 - 01:47 PM
Quote: "I need to deploy this mostly on computers with 512/1gb RAM"
You are close to get BSOD if having that low amount of RAM
Quote: "I will try this on tonight with XBoot and report on the results"
You don't need to wait
Simply test with your new sized 350mb UBCDWIN.ISO directly in my script
Script has a "Manually section" where you at least can test basic functionality to USB driver
Don't forget to check "Allocate 512 MB RAM" when testing USB driver!
Attention! You must run test in computer with at least 1 GB of RAM
Run test in computer with only 512 MB RAM is impossible
Posted 14 October 2011 - 02:17 PM
Then don't RAM load the ISO image.
in a system with 1gb RAM or less ?
Just map the ISO file. Read previous message.
Which bootloader does use XBoot?
Which UBCD4Win ISO file name exist at USB stick?
Create two boot options:
one with RAM load
antoher witout RAM load
Posted 14 October 2011 - 03:01 PM
Posted 13 October 2013 - 02:21 PM
Just in case you might ever want to support UBCD4WIN, Here is the error log i am getting.
i downloaded an used the most current version and tried both syslinux Grub options.
it did recognize that i had a utility ISO and did not ask me to identify it.
Posted 13 October 2013 - 04:13 PM
Please read here (those errors have NOTHING to do with UBCD4WIN specifically):
Just get the right dll package and they will go away .
Unfortunately there is NO way the tool can be updated, see :
Posted 13 October 2013 - 06:49 PM
I fixed the problem, i downloaded UBUSB, scrapped xboot, edit menu files, and everything is working great with multi distros. thanks and bye all.
Also tagged with one or more of these keywords: ubcd4win, winpe
Windows Extreme →
Windows PE →
Boot methods & tools →
Boot from LAN →
Project forge →
Community forum →
Boot methods & tools →
PE Bakery →
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users