Hi
I need help -- I followed the multiboot tutorial for http://flyakite.msfn.org/ and it's bootable and everything but when set up reboots it's looking for files on the root of the cd drive for i386 but it's not located there!!!!!!
I only did xp pro and home on it and I tried a few things but they didn't work (like moving one of the i386 to the root of the cd)
has anyone else ran into this issues, is there a fix for this? if there's a thread already made for this then could you point me to it? I don't know what I'm doing wrong but all the issues have to do with after set up reboots!!!!!
thanks!!!!!

Check the flag files win51* again.

I'm using oem sp2 xp cd's and the professional one is an hp oem, I don't know if that would have to do with anything but the win51 file I placed on the AIO-DVD folder is the one from the professional cd because if I use the home one it will try to replace it since they have the same name

when I did the tutorial for the first time it came out bootable and even the cd shell menu came out fine and all the choices work, erd commander 05 works fine and if you choose between pro and home it runs the setup for you to format the hdds and then copies windows files but when the computer reboots and setup continues it'll ask for windows files on the root of the cd (D: = my cd drive letter) D:\I386 just like a regular installation would look for the files but is there a way to override or tell it to look for it on the xp\home\I386 folder where the files are? and what should I check on the win51 file? should I edit it? should I try using one from a regular oem, I have pro corporate too...

Tag files has to be twice at multiboot CD: at root and setupsourcepath

I started the tutorial from scratch again and now it works, both pro and home install with no issues, I guess a missed a few things like there was a section that said copy files not move them ( I usually like moving files because I noticed it takes less time) I guess I might have done that at some point and the version of cd shell I used I guess had something to do because the link on the tutorial is broken and I had to google cd shell myself and after some research I found out someone was having issues with the most updated one and it had some bugs then he got the right one an it worked for him, it works for me now......

I need help when reducing the size of source, I thought that was why it kept asking for files after reboot but let me give it a shot and see how it goes now......

Hi again

I did trim down the source and it works fine now, I guess it probably had to do with the version of cd image (I was using the latest one which appeared to have some bugs)

what I did was I copied the i386 folder from the $WIN_NT$.~LS folder (that getz created copying the set up files) to the setup\xp\professional or home, it works fine it it and it trims at least 100MB for each i386.

now I need help integrating some sort of memory and hard drive diagnostic tool -- do you think you could help on that one or forward me any links that have to do with it?

I will highly appreciate................

Hi again
ok so Ultimate Boot CD has both memory and hard drive diagnostics but I tried to put it on the cd and it didn't work, on the tutorial it says to replace /CDHS with /UBCD on the UBCD.DAT file and I saw it listed at the top without the / and I changed it and it didn't work, it would reboot and I chose to launch it from the menu then I saw at the bottom a line /BOOT and I changed it to /UBCD and when chosen from the menu it tried to load it but it said it can't run from or load from cd......

for the integrating it to the menu, I didn't see a cdshell.ini file on the boot folder on the ubcd.iso -- help please...... this would be a great tool to include to the cd and I really need help....

if there's another thread regarding this could you please direct me to it...........

CD-shell amd the flyakite's guide are a bit "dated" (no offence intended ).

Particularly if you want to add UBCD, you may want to try using grub4dos and its .iso to (hd32) mapping capabilities, latest-latest UBCD is also fully compatible with grub4dos.

The reference thread is here:
http://www.boot-land.net/forums/index.php?showtopic=6119

Though I never tried it, I guess that grub4dos grldr can be chainloaded by CDshell, just like any NTLDR/SETUPLDR.BIN, if this applies, you can leave the Cd/DVD as-is and simply add the option to CDshell, the UBCD .iso and the grldr.

Grub4dos Whereto:
http://www.boot-land.net/forums/index.php?showtopic=14

Grub4dos guide:
http://www.boot-land.net/forums/index.php?showtopic=5187

Grub4dos reported to be working .iso's mapped as (hd32):
http://www.boot-land.net/forums/index.php?showtopic=5041

jaclaz

ok
I appreciate your help but I don't really understand it -- I'm a computer technician and my knowledge is limited but it seems on the first link they're just posting code and not really telling you how to do it. is that a file that needs to be edited or does it have to be run from command prompt..... if this sounds like a stupid question please forgive me but I guess when you don't understand something the best thing is to put you head down and ask for help.......

is there a way you could explain it or what do I need to follow this tutorial....... where should I edit the code on the initial post at http://www.ultimatebootcd.com/forums/viewtopic.php?t=1635

or where should I paste it, I'm sorry I'm kind of lost but thanks in advance!!!!!

Hmmm, it won't be easy.

I thought you were familiar (besides the flyakite guide) with the way CDshell works, and more generally XP setup works.

If you are looking for a full tutorial like the flyakite one, I don't think that there is one.

You need to read the grub4dos guide.

And browse/search the grub4dos forum to "get the hang of it".

Then, "translate" your current CD/DVD to grub4dos way of working. (guessing that this should be easier than adding grldr to CDSHELL)

Basically, you should get latest UBCD, here:
http://www.ultimatebootcd.com/forums/viewtopic.php?t=1786

Prepare a menu.lst with the various options, a typical entry for an install or PE (when booted from CD) is:


Then add to menu.lst the suggested entry for UBCD.

Be aware that grub4dos is CaSe SeNsItiVe.

Then, without changing the source for your "flyakite" CD/DVD (except adding the menu.lst, grldr and the UBCD .iso) , build a new one with grldr as no-emulation bootsector.

Suitable .cmd can be found here:
http://www.911cd.net/forums//index.php?sho...18045&st=25

Another option would be to chain from CDSHELL a floppy image .ima containing grldr and menu.lst, or a plain DOS one with grub.exe and menu.lst.

I am wondering now if this is a bit "too advanced" for your current knowledge of the matter (NO offence intended ).

Let me know if you are willing to invest some time on the project, I can try and help you, but you will have to do most of the work/studying.

It's possible that some other member can come out with another, simpler idea for UBCD....

jaclaz

Edit:
removed double forward slash in sample menu entry.

This post has been edited by jaclaz: Feb 21 2009, 04:34 AM

Definitively, I'll work on it -- I mean I do have an understanding of how xp setup works (since I'm a technician), not so much the way cd shell works ( I do understand the code for the cdshell.ini file) but when it comes to the isolinux and grub4dos I don't really know much cuz I haven't really used them...... and it is a bit advanced but I have no problem looking at it from scratch. so I guess I'll have to start with the guide, let me look into it or if you know of a link with a more understandable one let me know.....

Once you have read the guide, things should be already much clear.

Then simply browse the Forum:
http://www.boot-land.net/forums/index.php?showforum=66

There are lots of examples, from which you can "inspire".

Also, the very good thing about grub4dos is that it supports command line mode, in which you can enter commands or edit existing menu.lst entries and see how it behaves, thus you can freely experiment with any set of commands and only write the corresponding menu entry once you are sure it works.

jaclaz

Hi
I have a question, I looked up ubcd4windows 3.22 and it's built on a PE enviroment so I tried integrating it like bart PE but here's the deal:

the cd itself or iso loads a sort of command/dos interface which I believe is isolinux and you have options to choose from and one of them is the PE interface....
I edited setupldr.bin, txt setup.sif and extracted the boot sector from the iso, saved it as a .dat file and edit the fixbootbin1386 to BPE1....

so when I load the whole multiboot at the menu I can choose it and it goes to the pretext menu from the ubcd4windows but when I try to load the ubcd4windows pe enviroment and gives me an error regarding the i386 folder......

so I can extract the iso files, integrate them to the multiboot then i loads multiboot menu then it loads ubcd4windows menu but when I choose to load the PE enviroment it gives the error.

any suggestions, I think I came pretty close to that one since it loads the first UBCD interface, so from the multiboot menu it loads to the ubcd4win text menu but it I choose to launch the ubcd4win option wich is the pe based one it gives the error.......

any help? I already started reading on the grub4dos guides....
thanks......

Cannot really say, without knowing in detail your exact setup and the exact error you are getting.

It is very probable that /I386 is hardcoded somewhere else, like in a needed plugin or the like.


Please note that UBCD:
http://www.ultimatebootcd.com/

is one thing, and UBCD4WIN:
http://www.ubcd4win.com/
is another.

Up to your last post we (at least myself ) were talking about UBCD, NOT UBCD4WIN.

As a general rule of thumb, when building a multiboot "anything" based on XP/2003 source files, the "proper" way to experiment is:

1. use "normal" /I386 or /minint path
2. test the build by itself
3. try changing the path
4. loop to 1. for each "item"
5. leave the (hopefully just ) one "item" that you cannot make working with a different path, with it's default /I386 or /minint and change all the other ones

UBCD4WIN has an active Forum:
http://ubcd4win.com/forum/index.php?

UBCD4WIN specific problems should be searched for or posted there.

However, if your build contains isolinux, you should have at least an isolinux.cfg and most probably a main.cfg, which need probably to be edited to reflect your paths.

jaclaz

@christianmusicvr

Can you clarify overall DVD:
Which parts did you include in the meantime?
which directories do you use at DVD root now?

Which main boot loader do you use?

UBCD4Win use boot loader BCDW at CD.
Current multiboot solution expect directory I386.

One approach:
Don't use the whole multiboot solution.
Delete file fixboot.bin.
Add single parts to your boot loader.

Another approach:UBCD is another project. http://www.ultimatebootcd.com/
Do you get first UBCD4Win interface?


Try edit bcdw\bcdw.ini: change I386\setupldr.bin to BPE1\setupldr.bin
If this works, there is no need to edit setupldr.bin or txtsetup.sif. BCDW does edit file in RAM.
A XP setupldr.bin is assumed, a 2003 setupldr.bin is different.

@jaclaz
Problem is both: UBCD4WIN specific and global multiboot.

@cdob
Problem is that both of us are guessing due to incomplete/missing reports.

christianmusicvr asked about UBCD, then he "switched" to UBCD4WIN....

...with all due respect , technicians usually have more "organized" mental schemes....

...I was suggesting to engage on a single challenge at the time, as this is the usual approach I use.


jaclaz

This post has been edited by jaclaz: Feb 25 2009, 06:13 AM

I apologize for changing from ubcd to ubcd4win but I'm just trying to get a diag tool on the multiboot, I was downloading an older version of ubcd but it was ubcd4win (which I didn't notice at the time of download) so I tried to integrate it......

do you guys think you could help me out with the ubcd4win I think I'll go for that one since at least I got it to load to the text interface.. -- I'll try the suggested options and
do some more research, I'll post my results here and I'll post my cd layout too (I'm at work right now).

hopefully I'll still get help from you, once again I apologize for switching to ubcd4win

thanks......

I got UBCD4WIN to work!!!!!!!!!!!!!!!!!!!!!

what I did:

extracted all files from ubcd4win_3.22.iso to the aio-dvd folder, change i386 to BPE1, edit setupldr.bin & txtsetup.sif on the bcdw folder edit the bcdw.ini file i386 path

deleted bootfix.bin from i386(BPE1) folder -- extracted the boot sector from ubcd4win with ubcd4win_3.22.iso and saved it as BPE1.DAT and edited the binbootfixi386 to binbootfixBPE1

works for me!!!!!!!!!!!!!!!!!!!!!

now could you guys help me with the regular ubcd? I'm reading the guide already....

any help will be appreciated....

@christianmusicvr
Congratulations to integrate UBCD4Win.

Just to clarify: used approach did disable UBCD4Win mutliboot environment.
Core files are at \I386(BPE1) and \programs. You may delete directory BCDW.
There is no need to edit file txtsetup.sif. A PE does boot anyway.

Which UBCD version do you use?
UBCD use bootloader isolinux nowadays. That's contrary to old flyakite guide.
Load isolinux files at your used boot loader.

UBCD version 5b11 use can use BOTH "standard" isolinux and grub4dos (hd32) .iso mapping.

jaclaz