Re: Placing a program onto a SD or SDHC card to run at bootu

December 28, 2013, 8:48 pm

≫ Next: Re: adding win7 Setup to Ubcd 5.02 doesn't work

≪ Previous: Re: Mirror from Malaysia and USA

UBCD is for diagnostic and computer repair.

What it sounds like you are looking for is autorun.inf. More information: http://www.addictivetips.com/windows-ti ... tom-icons/

↧

Re: adding win7 Setup to Ubcd 5.02 doesn't work

December 30, 2013, 10:49 am

≫ Next: Re: adding win7 Setup to Ubcd 5.02 doesn't work

≪ Previous: Re: Placing a program onto a SD or SDHC card to run at bootu

This was working great for me for the longest time until UBCD 5.2.8 came out. I see that in this latest version there was an update made to chain.c32.

If I revert back to the older version of chain.c32 then booting works fine again. Any suggestions on this one?

Thank you

↧

Re: adding win7 Setup to Ubcd 5.02 doesn't work

December 30, 2013, 12:37 pm

≫ Next: Re: adding win7 Setup to Ubcd 5.02 doesn't work

≪ Previous: Re: adding win7 Setup to Ubcd 5.02 doesn't work

ctschantz wrote:

I see that in this latest version there was an update made to chain.c32.
If I revert back to the older version of chain.c32 then booting works fine again. Any suggestions on this one?

When you say that chain.c32 doesn't work in UBCD 5.2.8, what exactly do you see? Any error? What's the behavior?

In the Syslinux boot prompt, press ctrl+v so to see which version of Syslinux you are actually using. All Syslinux files should come from the same exact version.

↧

Re: adding win7 Setup to Ubcd 5.02 doesn't work

December 30, 2013, 9:28 pm

≫ Next: Re: adding win7 Setup to Ubcd 5.02 doesn't work

≪ Previous: Re: adding win7 Setup to Ubcd 5.02 doesn't work

ady wrote:

ctschantz wrote:

I see that in this latest version there was an update made to chain.c32.
If I revert back to the older version of chain.c32 then booting works fine again. Any suggestions on this one?

So before the update to 5.2.8 i was using the following entry that worked fine:

Code:

LABEL blah
MENU LABEL blah blah
COM32 chain.c32
APPEND boot 1 ntldr=/bootmgr

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:

(only showing the last line)

Code:

APPEND boot x ntldr=/bootmgr
APPEND boot x,x ntldr=/bootmgr
APPEND boot ntldr=/bootmgr
APPEND ntldr=/bootmgr
APPEND fs ntldr=/bootmgr
APPEND hdx,x ntldr=/bootmgr

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.

↧

Re: adding win7 Setup to Ubcd 5.02 doesn't work

December 31, 2013, 4:08 am

≫ Next: Re: adding win7 Setup to Ubcd 5.02 doesn't work

≪ Previous: Re: adding win7 Setup to Ubcd 5.02 doesn't work

@ctschantz,

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.

↧

Re: adding win7 Setup to Ubcd 5.02 doesn't work

December 31, 2013, 10:36 am

≫ Next: Re: adding win7 Setup to Ubcd 5.02 doesn't work

≪ Previous: Re: adding win7 Setup to Ubcd 5.02 doesn't work

ady wrote:

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.

Syslinux shows version 4.07 2013-07-25EDD

Yes I do use syslinux as the main bootloader I hardly ever use grub.

I use the following to create the USB:

Code:

ubcd2usb c:\<ubcdpath> <usbdrive>: /f

↧

Re: adding win7 Setup to Ubcd 5.02 doesn't work

December 31, 2013, 12:51 pm

≫ Next: Re: adding win7 Setup to Ubcd 5.02 doesn't work

≪ Previous: Re: adding win7 Setup to Ubcd 5.02 doesn't work

@ctschantz,

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.

TIA,
Ady.

PS: Happy New Year.

↧

Re: adding win7 Setup to Ubcd 5.02 doesn't work

December 31, 2013, 4:32 pm

≫ Next: Re: adding win7 Setup to Ubcd 5.02 doesn't work

≪ Previous: Re: adding win7 Setup to Ubcd 5.02 doesn't work

Happy new year to you as well.

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:

Code:

LABEL blah
MENU LABEL blah blah
COM32 chain.c32
APPEND boot 1 ntldr=/bootmgr

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.

Thanks.

↧

Re: adding win7 Setup to Ubcd 5.02 doesn't work

December 31, 2013, 7:56 pm

≫ Next: Re: adding win7 Setup to Ubcd 5.02 doesn't work

≪ Previous: Re: adding win7 Setup to Ubcd 5.02 doesn't work

ctschantz wrote:

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.

Code:

LABEL blah
MENU LABEL blah blah
COM32 chain.c32
APPEND ntldr=/bootmgr

Code:

LABEL blah
MENU LABEL blah blah
COM32 chain.c32
APPEND hd0 ntldr=/bootmgr

Code:

LABEL blah
MENU LABEL blah blah
COM32 chain.c32
APPEND hd0,1 ntldr=/bootmgr

Code:

LABEL blah
MENU LABEL blah blah
COM32 chain.c32
APPEND fs ntldr=/bootmgr

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.

TIA,
Ady.

↧

Re: adding win7 Setup to Ubcd 5.02 doesn't work

December 31, 2013, 9:06 pm

≫ Next: Re: adding win7 Setup to Ubcd 5.02 doesn't work

≪ Previous: Re: adding win7 Setup to Ubcd 5.02 doesn't work

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.

I will report back again once i have that information.

↧

Re: adding win7 Setup to Ubcd 5.02 doesn't work

December 31, 2013, 9:29 pm

≫ Next: UBCD launch tools

≪ Previous: Re: adding win7 Setup to Ubcd 5.02 doesn't work

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:

Code:

LABEL blah
MENU LABEL blah blah
COM32 /boot/syslinux/chain.c32
APPEND ntldr=/bootmgr

Code:

LABEL blah
MENU LABEL blah blah
COM32 /boot/syslinux/chain.c32
APPEND hd0 ntldr=/bootmgr

Code:

LABEL blah
MENU LABEL blah blah
COM32 /boot/syslinux/chain.c32
APPEND hd0,1 ntldr=/bootmgr

Code:

LABEL blah
MENU LABEL blah blah
COM32 /boot/syslinux/chain.c32
APPEND fs ntldr=/bootmgr

TIA,
Ady.

↧

UBCD launch tools

January 1, 2014, 3:47 am

≫ Next: Re: UBCD launch tools

≪ Previous: Re: adding win7 Setup to Ubcd 5.02 doesn't work

Hello,
I am running windows xp professional on my desktop.
When I boot the computer and the UBCD main window loads with a list of options. I press enter to launch the tools then it will go to a blank screen with a cursor blinking in the top corner. After a time I will get prompted to remove all media and press any key to start. Once I press any key I then get prompted to strike F1 to retry boot or press F2 for setup utility.
If I press F1 it beeps at me and wants me to either press F1 or F2 again. I press F2 and it will take me to the setup menu where I am prompted a password (that I do not know).
My question is I can not load or launch and of the tools on the UBCD. If and when I do press launch I get the remove all media and press any key.
Much help would greatly appreciated.

↧

Re: UBCD launch tools

January 1, 2014, 7:45 pm

≫ Next: UBCD and TrueCrypt

≪ Previous: UBCD launch tools

Take a look at the main picture located down the middle of the official download page http://www.ultimatebootcd.com/download.html which currently includes a title text as "Ultimate Boot CD V5.2.8".

If you don't get to see that initial boot menu, then either you downloaded something else (do you actually know what you want to achieve? Do you actually need UBCD for such goal?), or you are seeing something related to the BIOS, or a mix of the two.

There might be some problem to boot UBCD in your system, but before getting into troubleshooting, let's be sure that you actually need/want UBCD and not something else.

↧

UBCD and TrueCrypt

January 1, 2014, 8:23 pm

≫ Next: Re: adding win7 Setup to Ubcd 5.02 doesn't work

≪ Previous: Re: UBCD launch tools

I has a flashdrive created using YUMI with a bunch of utilities, including UBCD 5.2.8. I am using TrueCrypt on a system partition. I was wondering if anyone knew of a way to mount the partition using truecrypt from YUMI or UBCD and then running whatever program from YUMI menu or UBCD menu? I know that I can run the TC Rescue Disk to decrypt the partition, but wanted to avoid that. It would be nice to be able to mount the partition and then run whatever application desired.

I know this is a long shot, but giving the popularly of TC, I thought someone may have figured out a solution.

↧

Re: adding win7 Setup to Ubcd 5.02 doesn't work

January 2, 2014, 3:24 pm

≫ Next: Re: adding win7 Setup to Ubcd 5.02 doesn't work

≪ Previous: UBCD and TrueCrypt

Here are my results after using absolute paths as you last posted:

5.2.8 chain.c32

Using fs (APPEND fs ntldr=/bootmgr) resulted in the following error:

Code:

Insane primary (MBR) partition.
Can't find myself on the drive I booted from.

Using hd0,1 (APPEND hd0,1 ntldr=/bootmgr) resulted in the following error:

Code:

Insane primary (MBR) partition.
Requested disk / partition combination not found.

Using hd0 (APPEND hd0 ntldr=/bootmgr) resulted in the following problem:

(bootmgr loaded but BCD bombed)

Code:

File: \Boot\BCD
Status: 0xc0000225
An error occurred while attempting to read the boot configuration data.

Using (APPEND ntldr=/bootmgr) resulted in the following error:

Code:

Couldn't read the boot file.

5.2.6 chain.c32

Using fs (APPEND fs ntldr=/bootmgr) worked as expected.

Using hd0,1 (APPEND hd0,1 ntldr=/bootmgr) worked as expected.

Using hd0 (APPEND hd0 ntldr=/bootmgr) resulted in the following problem:

(bootmgr loaded but BCD bombed)

Code:

File: \Boot\BCD
Status: 0xc0000225
An error occurred while attempting to read the boot configuration data.

Using (APPEND ntldr=/bootmgr) resulted in the following error:

Code:

Couldn't read the boot file.

All tests were ran on the same hardware using the same USB port and USB drive. Additionally, the ONLY difference was using a different chain.c32 file as noted above.

Thanks

↧

Re: adding win7 Setup to Ubcd 5.02 doesn't work

January 3, 2014, 12:31 am

≫ Next: Access Denied when creating bootable USB stick

≪ Previous: Re: adding win7 Setup to Ubcd 5.02 doesn't work

@ctschantz,

Thank you for the useful feedback.

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.

↧

Access Denied when creating bootable USB stick

January 3, 2014, 7:25 am

≫ Next: Re: Access Denied when creating bootable USB stick

≪ Previous: Re: adding win7 Setup to Ubcd 5.02 doesn't work

I'm trying to create a bootable USB stick with UBCD on it. I have run ubcd2usb, but it gives me the error:

C:\Users\rbradley.ADC\Downloads\ubcd528\ubcd\tools\win32\ubcd2usb>ubcd2usb C:\Us
ers\rbradley.ADC\Downloads\ubcd528 e: /f

UBCD2USB: Creating bootable UBCD memory stick ...
UBCD2USB: *WARNING* YOUR USB KEY IS ABOUT TO BE REFORMATTED!
UBCD2USB: *WARNING* YOUR USB KEY CONTENTS WILL BE LOST!
Press any key to continue, press 'Ctrl+C' to abort.
UBCD2USB: Formatting USB KEY...
Insert new disk for drive E:
and press ENTER when ready...
The type of the file system is FAT.
The new file system is FAT32.
QuickFormatting 241M
Initializing the File Allocation Table (FAT)...
Format complete.
237.8 MB total disk space.
237.8 MB are available.

2,048 bytes in each allocation unit.
121,729 allocation units available on disk.

32 bits in each FAT entry.

Volume Serial Number is E886-AC25
UBCD2USB: Making USB KEY bootable...
Accessing physical drive: Access is denied.
Did not successfully update the MBR; continuing...
UBCD2USB: Copying files to USB KEY...

Insufficient disk space on current disk.
Insert another disk and type <Return> to continue...

------------------

I know the USB stick is probably too small (it's 512MB), but why am I getting Access Denied?

Thanks - Rowan

↧

Re: Access Denied when creating bootable USB stick

January 3, 2014, 12:30 pm

≫ Next: Re: adding win7 Setup to Ubcd 5.02 doesn't work

≪ Previous: Access Denied when creating bootable USB stick

You need to run the command prompt in Administrator mode.

Right-click on "Command Prompt" and select "Run as administrator".

↧

Re: adding win7 Setup to Ubcd 5.02 doesn't work

January 3, 2014, 1:20 pm

≫ Next: Re: Access Denied when creating bootable USB stick

≪ Previous: Re: Access Denied when creating bootable USB stick

ady wrote:

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.

The original USB Drive I was testing with:

Code:

USB Device
Disk ID: C3072E18
Type   : USB
Status : Online
Path   : 0
Target : 0
LUN ID : 0
Location Path : UNAVAILABLE
Current Read-only State : No
Read-only  : No
Boot Disk  : No
Pagefile Disk  : No
Hibernation File Disk  : No
Crashdump Disk  : No
Clustered Disk  : No

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
  Volume 3     E   UBCD5281     FAT32  Removable   1849 MB  Healthy

The secondary USB Drive I tested with:

Code:

SanDisk Cruzer USB Device
Disk ID: 00000000
Type   : USB
Status : Online
Path   : 0
Target : 0
LUN ID : 0
Location Path : UNAVAILABLE
Current Read-only State : No
Read-only  : No
Boot Disk  : No
Pagefile Disk  : No
Hibernation File Disk  : No
Crashdump Disk  : No
Clustered Disk  : No

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
  Volume 3     E   UBCD5281     FAT32  Removable   7633 MB  Healthy

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?

It is listed as a USB-HDD.

↧