With the 5.2.8 update, i would get an error about the file not being found. I did some research, and found that it could be because of how i was referencing the disk and\or partition. I tried different options where i was using different variations of the following:

Using different variants of the above, i get one of three problems.1.) The original error that i mentioned (where it cant find the file)2.) An error about the partition not existing*3.) bootmgr would kick off, but then it cant find BCD* (Like mentioned in OP)

*If you need exact error messages i can provide them tomorrow when i am back in front of my dev machine.

If i copy chain.c32 from the previous version of UBCD and overwrite the one in 5.2.8, the problem goes away. This would seem consistent with the 5.2.8 changelog mentioning an update to chain.c32

I hope that is a little more information to help with troubleshooting.

The first error (file not found) is somehow confusing, as the location of chain.c32 has not changed. This error wouldn't change by just replacing the file. Is this error displayed only when selecting chain.c32? Is this happening with any other (kernel) selection too? Is the error mentioning chain.c32 specifically? Or is it pointing to some other filename?

I would like to repeat my previous request:1_ Boot your USB disk up until the initial Syslinux menu;2_ From the Syslinux menu, press ESC so to see the Syslinux "boot:" prompt;3_ Press ctrl+v. Which version of Syslinux is shown in the resulting message? Could you please copy the whole exact message here?

Additionally, are you using Syslinux as your main initial boot loader? Or are you first booting with some other method (e.g. grub4dos) and chainloading to Syslinux?

A relevant detail: How exactly (which method) have you used so to write UBCD 5.2.8 to the USB disk?

The first error (file not found) is somehow confusing, as the location of chain.c32 has not changed. This error wouldn't change by just replacing the file. Is this error displayed only when selecting chain.c32? Is this happening with any other (kernel) selection too? Is the error mentioning chain.c32 specifically? Or is it pointing to some other filename?

I would like to repeat my previous request:1_ Boot your USB disk up until the initial Syslinux menu;2_ From the Syslinux menu, press ESC so to see the Syslinux "boot:" prompt;3_ Press ctrl+v. Which version of Syslinux is shown in the resulting message? Could you please copy the whole exact message here?

Additionally, are you using Syslinux as your main initial boot loader? Or are you first booting with some other method (e.g. grub4dos) and chainloading to Syslinux?

A relevant detail: How exactly (which method) have you used so to write UBCD 5.2.8 to the USB disk?

TIA,Ady.

Let me see if I can answer your questions in order:

I don't believe the "file not found" error is because it cant find chain.c32 I believe this happens because it cant find bootmgr. This would explain why if I change the last line to use say for example "APPEND boot 0 ntldr=/bootmgr" it will load bootmgr, but then bomb on BCD. Where as pre 5.2.8 I could get away with using "boot 1". Hopefully that clears up that confusion.

If I understand correctly, you have formatted (fat32) your USB drive for UBCD 5.2.8, and then you *only* replaced the chain.c32 file from the one from UBCD 5.2.6 (as oppose to "also" installing SYSLINUX from UBCD 5.2.6. ). Am I understanding correctly?

If that's the case, you are now using SYSLINUX v.4.07 (from ubcd2usb 5.2.8. ) and chain.c32 v. 4.05 (from ubcd2usb 5.2.6. ).

Now, you boot your system with your USB drive, and you want to chainload to your HDD and partition where 'bootmgr' is installed. Am I correct? Is there any OS other than Windows installed in this HDD? Is Windows installed in your "C:" drive (as it is the most common case)?

I would like for you to confirm the above details so to be able to suggest a possible solution (and/or to replicate your case).

ctschantz wrote:

"APPEND boot 0 ntldr=/bootmgr" it will load bootmgr, but then bomb on BCD.

I don't quite understand your intention with that 'append' line. Are you initially booting Syslinux from the *same* drive where Windows is installed?

ctschantz wrote:

Where as pre 5.2.8 I could get away with using "boot 1".

Well, this is why I need confirmation whether I am understanding your case correctly or not (i.e. the questions I posted in this same post). Using 'boot' for chain.c32 indicates "the drive syslinux was booted from". But what I previously understood was that you are booting with one (USB) drive and then chainloading to a *different* drive (where Windows is installed, in one of its partitions).

Please help me understand your situation, so to post a relevant suggestion.

Sorry if I am not explaining things very well. I will again do my best to answer your questions as I understand them.

If I understand correctly, you have formatted (fat32) your USB drive for UBCD 5.2.8, and then you *only* replaced the chain.c32 file from the one from UBCD 5.2.6 (as oppose to "also" installing SYSLINUX from UBCD 5.2.6. ). Am I understanding correctly?

That is correct. I created the USB using everything from 5.2.8. Everything works for me except for trying to boot to some wims. This worked in the past by using the following as also shown above:

In order to get this to work correctly, the ONLY thing I have to do is copy chain.c32 from the older version of UBCD (I used 5.2.6) to my usb in the proper directory. I don't re-create the USB or anything like that.. all I do is overwrite the file. Then the above line works to load my WIM.

The bootmgr file that I want to chainload as shown above resides on the root of the USB drive. Using the APPEND line as shown above with 5.2.8 will result in a "not found" error which points to the bootmgr file.

If I change the APPEND line to something like "APPEND boot 0 ntldr=/bootmgr" (I need to confirm exactly what I used again) then I get passed bootmgr (meaning it finds bootmgr and loads it) but then it stops (bombs or whatever you want to call it) with an error about not finding the BCD file. The ONLY way I can get it to work properly is to change my APPEND line back to what I was using prior to 5.2.8 and copy over the chain.c32 file.

Please let me know if that is a better explanation or if there is still any confusion.

The bootmgr file that I want to chainload as shown above resides on the root of the USB drive.

Does you USB drive contain more than one partition?

The reason I ask is because the adequate 'append' line for your case might depend on this detail.

Now, *assuming* your 'bootmgr' and your BCD *both* reside in the same partition as the boot loader (SYSLINUX, and the rest of UBCD too), I would expect for at least one of the following alternative codes to work with both versions of chain.c32.

Those 'append' lines are not exactly equivalent, and some versions of chain.c32 might behave slightly differently than others.

The version of chain.c32 included in UBCD 5.2.6 comes from Syslinux 4.05, and there were patches introduced after that release.

Could you please try chain.c32 from UBCD 5.2.8 with the 'append' lines I am suggesting here? That is, if my assumption ('bootmgr' and BCD are *both* located in the same partition as the boot loader) is correct. If not, then please clarify where exactly (drive and partition) are each of them located.

You are correct in stating that bootmgr and bcd are on the same partition as the rest of ubcd. Additionally, it is the only partition that is on the USB.

I believe i already did try some of the variations you posted, but i will try them again and i will post the EXACT messages i receive using those variations. I will be able to do this when i am again back in front of one of my DEV machines after the holiday.

Just to avoid some additional potential path issues, I would also suggest using "absolute" paths for the location of chain.c32. Assuming that 'bootmgr' is located in the root directory of the booting fat32 partition, and that chain.c32 is located in

/boot/syslinux/

(the same directory where ldlinux.sys is located), then the aforementioned suggested codes would be:

I'd like to have more info about your USB disk. Could you please try the following procedure:

1_ Connect your USB drive to your system. Wait enough time so Windows can recognize it. Can you access its contents using Windows Explorer?

2_ Close any and all unnecessary programs, specially if they have access to your USB drive (including the aforementioned window of Windows Explorer).

3_ Open a cmd prompt with right-click -> Run as Administrator.

4_ In the cmd prompt, Run the following commands:4.1_ "diskpart"4.2_ "list disk"

5_ From the resulting list, is your USB disk included / listed? Please be completely sure you are interpreting the resulting list correctly.

6_ Is the USB disk is listed?6.A_ If it is not, then run “exit” so to quit from diskpart. By this command you would be getting back to the cmd prompt; run “exit” so to close the cmd prompt too.6.B_ If your USB disk is indeed included in the resulting list, please take note of the adequate disk “number” for your USB disk as shown in the list.

7_ Run "Select Disk N" Where N is the number for your USB drive according to the aforementioned list. Make sure to select the adequate disk number.

8_ Run “detail disk”. It should provide information about your selected Disk. Please take note of (copy) all the resulting information.

9_ Run “exit” so to quit from diskpart. By this command you would be getting back to the cmd prompt; run “exit” so to close the cmd prompt too.

10_ Please post here the information obtained from the above step #8.

There are some other tools that might be capable of providing the information (perhaps bootice?). The point is to look at the whole “device”, beyond of what Windows is normally capable of showing (e.g. non-hidden volumes).

Additionally, I'd like to know how is your BIOS identifying / booting that USB drive. Is you BIOS seeing it as USB-HDD? Or as HDD, listed in the BIOS together in the same category as your internal HDD? Other way?

I'd like to have more info about your USB disk. Could you please try the following procedure:

1_ Connect your USB drive to your system. Wait enough time so Windows can recognize it. Can you access its contents using Windows Explorer?

2_ Close any and all unnecessary programs, specially if they have access to your USB drive (including the aforementioned window of Windows Explorer).

3_ Open a cmd prompt with right-click -> Run as Administrator.

4_ In the cmd prompt, Run the following commands:4.1_ "diskpart"4.2_ "list disk"

5_ From the resulting list, is your USB disk included / listed? Please be completely sure you are interpreting the resulting list correctly.

6_ Is the USB disk is listed?6.A_ If it is not, then run “exit” so to quit from diskpart. By this command you would be getting back to the cmd prompt; run “exit” so to close the cmd prompt too.6.B_ If your USB disk is indeed included in the resulting list, please take note of the adequate disk “number” for your USB disk as shown in the list.

7_ Run "Select Disk N" Where N is the number for your USB drive according to the aforementioned list. Make sure to select the adequate disk number.

8_ Run “detail disk”. It should provide information about your selected Disk. Please take note of (copy) all the resulting information.

9_ Run “exit” so to quit from diskpart. By this command you would be getting back to the cmd prompt; run “exit” so to close the cmd prompt too.

10_ Please post here the information obtained from the above step #8.

There are some other tools that might be capable of providing the information (perhaps bootice?). The point is to look at the whole “device”, beyond of what Windows is normally capable of showing (e.g. non-hidden volumes).

Additionally, I'd like to know how is your BIOS identifying / booting that USB drive. Is you BIOS seeing it as USB-HDD? Or as HDD, listed in the BIOS together in the same category as your internal HDD? Other way?

TIA,Ady.

FYI I just ran all my tests using a different USB device with the same results.

I will try and answer your questions above:

1_ Connect your USB drive to your system. Wait enough time so Windows can recognize it. Can you access its contents using Windows Explorer?

Yes

2_ Close any and all unnecessary programs, specially if they have access to your USB drive (including the aforementioned window of Windows Explorer).

3_ Open a cmd prompt with right-click -> Run as Administrator.

4_ In the cmd prompt, Run the following commands:4.1_ "diskpart"4.2_ "list disk"

5_ From the resulting list, is your USB disk included / listed? Please be completely sure you are interpreting the resulting list correctly.

Yes

6.B_ If your USB disk is indeed included in the resulting list, please take note of the adequate disk “number” for your USB disk as shown in the list.

7_ Run "Select Disk N" Where N is the number for your USB drive according to the aforementioned list. Make sure to select the adequate disk number.

8_ Run “detail disk”. It should provide information about your selected Disk. Please take note of (copy) all the resulting information.

Additionally, I'd like to know how is your BIOS identifying / booting that USB drive. Is you BIOS seeing it as USB-HDD? Or as HDD, listed in the BIOS together in the same category as your internal HDD? Other way?

could, in theory, indicate that the USB device has some potentially conflicting or unsupported partitioning / volumes (I happen to have a USB flash drive which diskpart and bootice keeps identifying as 2 separate devices, instead of 1 device with 2 volumes).

Information such as partition alignments and CHS values in the MBR, in the VBR and as seen by the BIOS might be relevant too.

I wonder if the same USB devices could use chain.c32 v4.07 successfully when plugging them in other systems / other USB ports.

Having more details might provide a clue to the source of the issue.

Whichever the case, the newer chain.c32 seems to be more "picky". I have reported the issue upstream and I'll post here if I get some relevant info.

Thanks for the information. FWIW, i did try the two USB's on multiple systems (6 different model HP's) all with the same result. The only thing so far that i can do to get it to work is to revert back to the older chain.c32.

There are cases where the above error message is valid, not related to potential bugs in chain.c32.

One reason for such error messages can be a BIOS bug. Typically, a USB drive plugged in one system might work correctly, while using the same exact USB drive plugged into a completely different system (different system brand, different BIOS brand) might result in an error message.

So updating the BIOS whenever possible should be a first step, and by testing the same USB drive in different systems could indicate whether the problem is related to BIOS or to chain.c32 (or to something else).

Some (newer) versions of chain.c32 include an optional "relax" parameter. This might be also helpful for testing. But beware that the intention of this parameter is to help testing (narrowing down the reasons for some problems), and should not be used as a workaround. In other words, if the only way to successfully boot with chain.c32 is by means of "relax", then the user takes the risk of screwing the data. No complaints should be directed to anyone else.

Who is online

Users browsing this forum: No registered users and 2 guests

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot post attachments in this forum