Forum: EasyBoot
Topic: UBCD4Win conflict
started by: norman
Posted by norman on Aug. 08 2011,07:27
In the I386 directory of UBCD4Win, several files with the same name occur in different subdirectories. When I run 'Make ISO', I am asked whether to keep the file(s) or replace it (them); either way, the CD that is subsequently burned (even when UBCD4Win is the only bootable program in the ISO) does boot from UBCD4Win, but stalls after loading Windows.
 UBCD4Win is a very popular utility and many people use it with EasyBoot. What am I doing wrong? (I  used UltraISO to extract the original UBCD4Win iso file which, incidentally, works just fine as a standalone bootable CD.)
Posted by balder on Aug. 08 2011,07:43
@norman

As it seems you are a new member I say welcome @norman :)

Quote: "What am I doing wrong?"

Well I'm a little bit confused here ???
Do you already have a folder I386 with other files and folders (setup folder to WinXP or whatever) in folder disk1 (folder disk1 is the "root" for EasyBoot if you wonder) and trying to replace similar files and folders?

Hmmm I'm confused :O

Quote: "(I  used UltraISO to extract the original UBCD4Win iso file which, incidentally, works just fine as a standalone bootable CD.)"
And now you goal is to create a new ISO with files you extracted from ISO
Why this detour ???
Or do I totally miss the picture :O

balder
Posted by norman on Aug. 08 2011,09:10
1. Now I know the answer to my question "What am I doing wrong?": Everything! But with such a distinguished guide, I'm sure I'll figure it out, eventually.
2. Some time ago I downloaded (XP-SP3 slipstream) UBCD4Win according to instructions on their website and burned a CD from the iso file; the CD works just fine.
3. In keeping with many others, I now want to combine that and other bootable CDs into a multi-boot DVD.
4. I launched UltraISO, loaded the UBCD4Win iso file and extracted it into EasyBoot\disk1.
5. During the extraction process, I got the message: 'keep or replace' for I386\WINSXS\MANIFESTS\CAT and again for I386\WINSXS\MANIFESTS\ST.
6. I choose what I choose and the extraction completes.
7. I also save the boot file to disk1\ezboot.
8. I then launch EasyBoot, make the appropriate choices in the 'Menu' tab and 'Save As' an .ezb file.
9. I then 'Make ISO'.
10. I use Active ISO Burner to burn a test CD.
11. The burning and verification completes uneventfully and I boot my system from the CD.
12. The EasyBoot screen opens, I choose UBCD4Win, it launches, Windows begins to load and, near the end, stops: no more progress, juat a responsive mouse cursor.
13. I'm sorry I was so obscure last time, but I learn fast.
14. Thank you for your offer to help.
Posted by balder on Aug. 08 2011,10:19
@norman

Quote: "Everything!"
He, he same as I did in the beginning of using EasyBoot :D

Quote: "I now want to combine that and other bootable CDs into a multi-boot DVD"

Okay, so you have already folder I386 in easyboot\disk1 and obviously you can only have one folder I386!

This can be solved in several different ways.

One solution is to run ISO-file as it is (not extracting anything to folder disk1)
In fact you can run any WinPE from RAM that is built from source of NT5 or NT6 (NT5=WinXP etcetera NT6=Vista/Win7/Server-2008).
Note: NT6-systems doesn't even need the RAM-approach!

But you also mentioned (if I understand right) that you build UBCD4Win using WinXP_sp3 as source - correct?
If this is the case, you can test renaming folder I386 to any uppercase 4-letters name (typically UBCD or 4WIN or whatever 4-letters name you prefer).
Then use menu command in EasyBoot:  bcdw /UBCD/setupldr.bin  (where"UBCD" is the name you prefer).

Another way is to hex edit (change name to folder I386 and hex edit some files to make it work.
This can be done using my script "easyboot-live.script"
Script change name and automatically make necessary hex edit to source files with a breeze :p

In case you have setup folder in your build (setup folder I386 for WinXP_sp3 in your build) then you can also change name to this folder using script "easyboot-AIO.script".

I have a link to my "old" script collection < HERE >
Note: script collection for download that you can localize below in every post I write in this forum, doesn't have "easyboot-live.script" as it is not that common to launch WinPE-systems this "old" way.
Instead we tend to launch ISO-file as the are from RAM.
Run ISO from RAM also make it extremely easy to launch EasyBoot menu from USB device and in this way launch ISO-files as the are (not extracting any files or folders any where).

It would be helpful if you could give some more details what you have in your "multiboot-project" ???

Quote: "I use Active ISO Burner to burn a test CD"
How about using "Virtual PC" or similar?
In fact you have in script "easyboot-live.script" a button "run ISO from qemu" that can test you built ISO before you burn it to any CD/DVD :;):

balder

Posted by norman on Aug. 09 2011,04:52
Dear Balder,
   I see where this is going to take some time. I hope you have the patience for me.
   I have begun going over your reply, trying to figure out what I am supposed to do. But I noticed that you write "One solution is to run ISO-file as it is...". Great! That would do me just fine, for now—if I knew how.
  Let's say I have 4 ISO-files: A.iso, B.iso, C.iso, D.iso, each with its bootable CD.  How do I setup EasyBoot so that its 4 menus contain these 4 entries and that when I choose one of them, the corresponding X.iso program executes? Please be as specific as you can.
  There is a program called Xboot that runs iso-files in this manner, but not all iso-files are supported.
Posted by balder on Aug. 09 2011,05:57
@norman

Quote: "I hope you have the patience for me"
Sure :;):

Quote: "That would do me just fine, for now—if I knew how"

Solution is to use my script collection - look below and download zip-file
Scripts are free for private use - completely royal-free  to non-commercial use :laugh:

Extract zip-file "balder" to the root (C:\) and read "READ_ME.html" inside folder balder.
Then open folder "WinBuilder_complete" and double-click to WinBuilder.exe

If you have carefully read the "READ_ME.html-document" you now can activate script; "easyboot-iso.script" by simply click once on it in the left part of WinBuilder window (there are several more scripts to chose from).

Now when you have "easyboot-iso.script" up and ready you push on "help-button".
At this point I find it hard to belive that you don't understand what to do ???
Test and reply your results.

Quote: "Let's say I have 4 ISO-files: A.iso, B.iso, C.iso, D.iso, each with its bootable CD.  How do I setup EasyBoot so that its 4 menus contain these 4 entries and that when I choose one of them, the corresponding X.iso"

Note: not all ISO-files can be launched directly - but surprisingly many of them.
As mentioned in post nr, 4 And I quote: "In fact you can run any WinPE from RAM that is built from source of NT5 or NT6 (NT5=WinXP etcetera NT6=Vista/Win7/Server-2008)."
This means all kinds of Windows-PE-ISO-files can be launched this way - including UBCDWIN

Quote: "There is a program called Xboot that runs iso-files in this manner, but not all iso-files are supported"
Yes I'm acquainted with this kind of program - but I'm not satisfied - and further more, it doesn't at all support Easyboot in the right way - which my scripts to 100% do :D
--------------------------------------
Read below what I did as test:

Did some test using an "old" Retogobuild from the "good old times" created with WinXP_sp2 as source (basically the same as UBCDWIN).
The build is in the neighbourhood of 300 MB in size.

I used my script "easyboot-iso.script to integrate ISO into EasyBoot.
Note: I checked "Run ISO from RAM" as this WinPE is build from NT5-source (WinXP or similar).
I used the name REATOGO in script text-box as name to ISO-file.
I also used recommended menu command given by script in EasyBoot menu:  memdisk reatogo.img.gz

To compare I used my script "easyboot-live.script" and changed name in text-box in script to REAT
I used recommended menu command given by script in EasyBoot menu:  run reat.bin

I created ISO and finally burned ISO to an CD-RW and tested.

Test came out this way:

1. The winner is the "new method", run ISO from RAM, as it was up and running Reatogo in less than 90 seconds
And as the system run from RAM it was super fast in reaction - no delay - faster than a "real" Window system.

2. The loser is the "old fashion method" with folders and files as it was up and running after 3 minutes and 20 seconds
That is what I call a genuine looser

    Sensmoral: Use my script easyboot-iso.script to integrate and run all different ISO,s typically;  UBCDWIN or ERD or BartPE or MsDart60/65 ghost14 rescue ISO, active-boot-cd (ISO) etcetera

balder

Posted by norman on Aug. 14 2011,08:29
Dear Balder,
Last Wednesday I posted a reply, but when I came to check today, I couldn't find it. I don't know what went wrong, but I'll try again.
I downloaded your script collection and read the READ_ME file. (Actually, I was already familiar with your collection and had read the file in question before my first post.)

1. When I run EasyBoot-ISO WITH 'Run ISO from RAM', use the information-window prompt 'memdisk UBWIN.img.gz' in EasyBoot, and burn a CD, the CD boots, UBCD4WIN executes, Windows loads, the 'Start Shell' window appears, and then nothing more happens, ever.
2. When I run EasyBoot-ISO WITHOUT 'Run ISO from RAM', use the information-window prompt 'memdisk UBWIN.img.gz' in EasyBoot, and burn a DVD, the DVD boots, UBCD4WIN executes, Windows loads, and a BSOD appears.

I am stuck, completely, and desperately await your advice.
Posted by balder on Aug. 14 2011,10:34
norman

Quote: "I am stuck, completely, and desperately await your advice."

Help is on it's way :D

Quote: "1. When I run EasyBoot-ISO WITH 'Run ISO from RAM', use the information-window prompt 'memdisk UBWIN.img.gz' in EasyBoot, and burn a CD, the CD boots, UBCD4WIN executes, Windows loads, the 'Start Shell' window appears, and then nothing more happens, ever."

How much RAM do you have in computer?
You need at least twice amount RAM as your original UBCD4WIN-ISO-file is in size, otherwise computer freeze as not enough RAM is available to full-fill the process :O
If your build is, let's say 680 MB, you need at least 1,536 (1,5GB) GB RAM and if you have a graphic card that consumes RAM (integrated RAM dedicated to graphic-card) then you need at least 2,024GB (2GB) RAM
Please take notice to that these kinds of builds are large in size and consumes pretty much RAM ???
You can download "MobaLive" and test your ISO-file (no need burn to CD/DVD before tested ISO is working correctly)
Download < HERE >
Note: Push NO when MobaLive is asking "create hard disk image". You don't need to create such one to test ISO-file.
-----------------------------------------
It would be of great interest if you could explain what kind of build you are creating.

I understand that UBCDWIN is involved but what more NT5-system are we dealing with?
Is it setup of WinXP or similar?


regards balder

Posted by norman on Aug. 16 2011,05:18
Dear Balder,
   Thank you! The problem with UBCD4WIN has been solved. (It wasn't a shortage of RAM—I have 4GB.) It turns out that the UBCD4WIN.iso file I was using is corrupt. I suspected something like that and reran the LiveCD had I burned from it, but that worked fine. Apparently, the corruption occurred after the burning, and I never thought to burn it again. But with the QEMU program you suggested, I tried it directly, and found the problem. I used an old backup of UBCD4WIN.iso and everything was fine.
   I now have 3 bootable programs on my LiveCD, but the fourth is giving me trouble. I want to add Partition Wizard, which is a free replacement (only 37.5MB) for the no-longer-supported Partition Magic, but when I run your EasyBoot-ISO script (with or without the RAM option), Partition Wizard boots into a DOS screen with the prompt: grub>.
   I tried extracting the Partition Wizard iso file (using UltraISO) directly into EasyBoot\disk1 but  when I then boot it from the EasyBoot screen, I receive a checksum error for its bif file.
   Do you have any ideas or should I just quit while I'm ahead?
  Thank you again.
Posted by balder on Aug. 16 2011,07:27
@norman

Quote: "I now have 3 bootable programs on my LiveCD, but the fourth is giving me trouble. I want to add Partition Wizard"

Quote: "3 bootable programs on my LiveCD"
Great :D

Anyway... Hopefully it is this "Partition Wizard" we are dealing with ???  < HERE >
Full Download < HERE >

Sometimes these ISOLINUX-distro's is a pain in the *** :angry:
But can mostly be solved - and I'm pretty sure solution below is to your fully satisfaction (I hope :;): )
Do it this way:

1. Extract folder "BOOT" from ISO-file to folder disk1 in EasyBoot
2. Use my script "easyboot-iso.script" to integrate Partition-Wizard.iso-file into easyboot (do not have spaces in ISO-name). And you don't need to check "Run ISO from RAM".
3. Use menu command given by script. You don't need to check "Joliet" to make it work.
4. Use "MobaLive" (read Post Number: 8) to test ISO created by EasyBoot.
And yes I know - this takes up some space (38MB+ISO-file) but we cannot, in this case, fully take advantages of the "frugal solution" to this ISO-build.
We need to have files on both the "root" (folder disk1 in EasyBoot) as in the ISO-file itself.
This is a little weird but needed

Please also read about changes to EasyBoot-version-6
Read < HERE >
And read < HERE >

I you have updated EasyBoot to version-6 you don't need to do step 2 in tutorial above.
You can simply copy "wizard.ISO-file" to folder ezboot and use menu command in EasyBoot:
run wizard.ISO (or what ever name you use to ISO-file.
Basically the solution given by my script "easyboot-iso.script" is built-in to EasyBoot from EasyBoot version-6.
But not the "RAM"-approache needed to WinPE built using NT5-system as source (your UBCDWIN is such example, it still needs the "RAM"-approach to work correctly)

Note: You must download my updated scripts (replace old folder "balder" with updated folder "balder") if you update Easyboot to version-6

regards balder
Posted by norman on Aug. 16 2011,08:08
Dear Balder,
  Worked like a charm! I have decided to purchase EasyBoot and add more bootable programs, now that you have shown me how to use it properly.
  Thank you very, very much.
Posted by norman on Aug. 18 2011,08:02
Dear Balder,
   I'm back. I managed to build a LiveCD with 6 of the 7 bootable utilities I want (thanks in large measure to your help). I thought the seventh would be the easiest of all, but I am stuck.
   I would like to add UBCD (the DOS version). I tried using EasyBoot-ISO with and also without the RAM option. The utility boots and some of its programs run but the main one (called UBCD) does not load completely. I also tried other methods suggested in this forum, but none worked. What have I misunderstood now?
   I am using the latest version of your scripts with EasyBoot 6 under Windows XP Pro-SP3.
Posted by balder on Aug. 18 2011,09:46
@norman

Quote: "I thought the seventh would be the easiest of all, but I am stuck"

First of all, ubcd-dos-version is a well known trouble-maker :angry:

I downloaded ubcd511.iso
Funny is that parted magic didn't work when testing original ubcd511.iso-file in virtual pc :(
It's possible ubcd511.iso needs to be run in "real mode" ???

Anyway, this seems to work as far as I have tested:
1. Extract folder "boot", folder "pmagic" and folder "ubcd" to folder disk1 in EasyBoot
2. In EasyBoot menu use menu command:  bcdw /boot/isolinux/isolinux.bin
3. You don't need to check anything to make this work (but you can test checking "Joliet" and not have "Joliet" checked)

Notes: It's possible folder "boot" must be merged with an already existing folder "boot" - I'm not acquainted with what you have in your build (in folder disk1) ???

EDIT:

I think I have found what could cause this problem with UBCD511.iso
The UBCD511.iso is "Label-sensitive".

When creating ISO in EasyBoot you get the smaller window "Create ISO"
In the lower part you have "CD VOLUME" and a name "myiso" or similar.
Change name to UBCD511 and create ISO.

Attention!
1. You must use my script "easyboot-iso.script" to make it work
2. You don't need to check "Run ISO from RAM"
3. You don't need to extract anything anyware, but I'm unsure about parted magic, you may need to extract folder "pmagic" to folder disk1 (but first test without extracting folder)

regards balder

Posted by norman on Aug. 21 2011,08:08
Dear Balder,
   Switching to ubcd511.iso solved the problem. (I had been using ubcd503 until now.) I did not experience the 'Label-sensitive' effect you describe: changing 'mycd' to 'Test1' didn't seem to make any difference.
   You are correct concerning parted magic: folder 'pmagic' must be extracted to folder 'disk1' for the program to work properly.
   Thank you again.
Posted by norman on Sep. 20 2011,06:22
Dear Balder,
I am back, somewhat sheepish this time. I used EasyBoot to construct a DVD with 7 entries, as you may recall. They all work fine when tested in MobaLiveCD (which you recommended) but at least one (Hiren's) hangs when launched from the actual burned DVD.
I read once that emulators sometimes don't work on a particular iso file and so I should always check the actual burned CD; I never came across the reverse.
You were very helpful before, when I was building the DVD with EasyBoot, and I succeeded (at least in MobaLive) thanks to you. Do you have any ideas this time?
To complicate matters somewhat: I have two XP machines, at home and at work. At work, the burned DVD behaves as it should, the problem is with the DVD at home. Even a DVD burned at work (from an iso file created at home or at work) hangs at home when launching Hiren's. (I have two DVD drives at home, no difference.)
I am aware of Hiren's 14.1 (I use 14.0) and your new WinBuilder, but am hoping for a solution with what I have.
Posted by balder on Sep. 20 2011,06:57
@norman

Quote: "I am aware of Hiren's 14.1 (I use 14.0) and your new WinBuilder, but am hoping for a solution with what I have. "

I too have problem with Hiren14.0 (at least the DOS-utilities) :(
I cannot launch DOS-utilities when using Hiren-14.0 :O
You are highly recommended to instead use Hiren-14.1

It seems there are some kind of bug (or whatever) in Hiren-14.0

Take also in consideration that the "hardware-issue" always is there as a "trouble-maker".
In fact, its amazing it works on so many different "hardware-platforms" as it does ???

Conclusion, test using Hiren-14.1 and see if you can notice any improvements.

Final note: Be proud over what you already have achieved @norman
As an former "old" technician, I can tell you that troubleshooting takes a lot of efforts before you reach 100% success :)

regards balder
Posted by norman on Sep. 24 2011,09:34
Dear Balder,
   I seem to have isolated my problem. I have 7 items in my EasyBoot menu: some work regardless of the state of Joliet during ISO creation, some work only when it is enabled, some work only when it is disabled. I can get 6 of the 7 to work with Joliet enabled but UBCD4DOS (ubcd511) hangs during unpacking (not in MobaLive, just from the burned DVD).
   Is there any solution to that, or am I stuck in principle?
Posted by balder on Sep. 24 2011,12:34
@norman

Quote: "6 of the 7 to work"
Really not bad so far :;):

Quote: "Is there any solution to that, or am I stuck in principle?"

Well I cannot to 100% guarantee anything, as much is related to hardware issues etcetera :O

But how about testing the good "old" menu solution "bootinfotable"?

Open UBCD4DOS.ISO-file and extract folder boot and folder pmagic and finally folder ubcd to folder disk1 as usual (I use UltraIso to this operation).
In EasyBoot use menu command;  bootinfotable;run /boot/isolinux/isolinux.bin

Build works most likely regardless if you check "Joliet" or not.
However this only works from CD\DVD-unit and not from USB.
Strangely using this solution build IS NOT "Label-sensitive" as described in post nr; 14.
It works regardless of what name that is set to label :cool:

Note: I only tested in Virtual PC and not from burned DVD :O

regards balder
Posted by norman on Sep. 24 2011,12:54
Dear Balder,
   Thank you for your quick reply.
   I already have a folder called 'pmagic' in Disk1 but it is the same as the one in UBCD4DOS and probably comes from another item in EasyBoot.
   I also have a folder called 'boot' in Disk1, but that is quite different from the 'boot' in UBCD4DOS. Can I rename it, or perhaps extract its subfolders (grub, isolinux, syslinux) and move them to the 'boot' folder already in Disk1? Would that solve the problem?
   There is no such problem regarding 'ubcd'.
Posted by balder on Sep. 24 2011,14:24
@norman

Quote: " I also have a folder called 'boot' in Disk1"
Yes this is an common problem ???
This is the reason that launching ISO-files as they are should be tested as first solution (without extracting any files or folders to folder disk1).
However sometimes it is indeed needed to extract some folders ("frugal solution" is typical for this).

But as you already have pmagic implemented (from some other software) you can skip parted magic - or at lest you don't need to launch it from UBCDdos.iso :O

Instead use "easyboot-iso.script" and integrate ubcddos-iso-file as it is (no need to check "Run ISO from RAM").
I'm a little bit unsure if all software can be launched this way ???  - but try in "virtual environment" to se how and if it works :cool:
It's also possible pmagic cannot be launched correctly from ubcddos.iso this way.

I did some tests and most of the software seems to work correctly
Give it a try :;):

regards balder
Posted by norman on Sep. 25 2011,12:33
Dear Balder,
   The method you are now proposing, easyboot-iso.script (and extracting pmagic), is what I have been using. With Joliet it works fine in MobaLive but not from a DVD; without Joliet it works fine in both. (I don't see why Joliet should make any difference, do you?)
   I have now found a solution: when running UBCD4DOS from the EasyBoot DVD, choose option 6 or 7 (no UMB). Simple as that.
  Thank you for your continued support.