UBCD4Win Forums: USB boot without bios support - UBCD4Win Forums

Jump to content

  • (46 Pages)
  • +
  • « First
  • 44
  • 45
  • 46
  • You cannot start a new topic
  • You cannot reply to this topic

USB boot without bios support beta-testers needed

#676 User is offline   anmg Icon

  • Newbie
  • Pip
    • Group: Members
    • Posts: 2
    • Joined: 13-September 10

    Posted 14 September 2010 - 01:34 AM

    Flash drive is Transcend JF 168 2 GB
    After all flash failed to boot.as there was no boot record.
    For what the utility comperssing ISO image? And why it do it on USB drive but not on HDD and after copy compressed image to Flash?

    View Postpcuser, on 13 September 2010 - 07:39 PM, said:

    Can you please post your UBUSB.log file?

    Here it is


    #677 User is offline   LeMOGO Icon

    • Newbie
    • Pip
      • Group: Members
      • Posts: 2
      • Joined: 27-December 10

      Posted 30 December 2010 - 07:10 AM

      First let me say that the professionalism and courtesy in this thread encouraged me to do something that was difficult for me: understanding what was going on while not being a programmer. Thank you all for your contributions, and thank you for a great software.

      I may not have understood some things, but this is a summary of the past 46 pages that I wrote to the best of my abilities:

      Please keep in mind that the preferred build environment is still XP 32-bit using Grub4dos as the bootloader because selecting "PE-Boot (Compatibility Mode / Memory Mapped) when booting seems to be the fastest and most compatible boot method. You should consider using Grub4dos as the bootloader so you can REALLY take advantage of the benefits that UBUSB has to offer.

      This is a utility to boot PE from usb. It is capable of booting the following:
      • UBCD4Win
      • BartPE
      • ISO images of the above

      When a pc does not support booting from usb or can not boot from usb for certain reasons, the boot process can be started from a cd and handed off to the usb drive.

      Because of its capabilities, it can be used to:
      • Boot PE to do repairs
      • Install XP from usb

      A few things that can interfere with its operation are:
      • Security software
      • windows explorer

      The nuts and bolts of how UBUSB works:
      • All prior releases are archived and are still available for download. For example, v1.0.46 is at http://www.ezpcfix.n...BUSB-1.0.46.exe and v1.0.48 is at http://www.ezpcfix.n...BUSB-1.0.48.exe
      • Starting an XP installation from UBCD4Win used to fail with a 0x7B error (INACCESSIBLE_BOOT_DEVICE) BSOD after first reboot because the mass controller driver for the controller to boot would not be available (because it is on the cd and we're booting from usb). The way around this was to integrate (splitstream) the drivers in ubcd4win. That issue has been resolved and UBUSB now works on all post 2000 windows versions.
      • The "special-files" folder is still used to include the "Win2k3" files as with earlier builds, and the folder has to be called "win2k3-files". That's done to keep support for it, but there hasn't been a single computer yet that needed those files and wouldn't boot with the compatibility mode.
        Is this "\parent\win2k3-files"?
      • The .BSS files (UBCD4Win.bss - backup of the usb drive's boot sector, and, cmdc.bss - used for booting UBCD4Win and the Recovery Console with Syslinux) are still created from the boot sector of the usb drive for possible future use but are not used for now.
        Starting at v1.0.47, UBUSB chain loads ntldr and no longer uses .BSS files
        mkdosfs.exe is now used to format the drive. mkdosfs.exe does not produce a bootable boot sector. Because it does not produce a bootable boot sector, there is no boot sector for UBUSB to copy as a UBCD4Win.BSS . [More]
        This had a temporary down side that in Syslinux (unlike Grub4dos which does the required edit directly in memory), the XP Recovery Console was no longer supported since that required a hacked version of ntldr. Luckily syslinux was updated and v3.85 supported recovery console cmldr. Recovery console which had stopped working prior to UBUSB v1.0.48 has been reenabled with the inclusion of Syslinux 3.85
        For reference: UBUSB pulls the bootsector from your usb drive to create UBCD4Win.bss and cmdc.bss (used for booting UBCD4Win and the Recovery Console with Syslinux) so they'll always match the filesystem you're currently using on your usb drive. cmcd.bss does not use the hacked setupldr.bin/rcldr method, it uses the method of renaming the CMDC directory to CMDCONS and changing MSDOS5.0 in cmdc.bss to CMDCONS(0).

      • If you run UBUSB.exe from the command line and use a /verbose switch then lots of debug info will be printed in the log file including information on all open handles for every running process on the system.
      • When launched, UBUSB will wait for a usb to be plugged in and make its options available as soon as detects a usb drive. Make sure that you don't have any explorer windows open to the drive and that the drive's not in use. If nothing else then unplug the drive then plug it back in and run UBUSB again, also make sure that the autorun dialog is closed before trying to format it.
      • When starting, it looks in its parent directory to load the following:

        • grldr
        • grubinst.exe
        • syslinux.exe
        • vdk.exe
        • vdk.sys

        You can place updated files in the directory before launching ubusb so that the program will use them instead of the ones it came with. This makes it easy to test new versions of these programs without having to wait for me to release a new UBUSB.

      • The program creates a MBR on the usb stick. Only BIOSes that have support of USB hard disk booting will be able to boot the flash drives directly.
        Since there is no generic BIOS USB implementation, some BIOSes that support usb booting might still not boot your stick. Upgrade your BIOS to the latest available, it might solve some problems.
        Some computers support booting from usb only on certain specific ports, not all of them. Try them all.
        Some BIOSes will need to be placed in OS install mode.
        Some BIOSes only work with specific file systems. Use FAT16 boot partitions for the most compatibility.
        Many ( if not most ) systems use USB 1.1 by default at boot for compatibility reasons... but the kicker CD enables the USB 2 speed if available. On some machines, usb boot with the kicker CD will use usb2.0 but direct usb boot without CD in drive will be 1.1
        You are limited to specific file systems depending on the size of the stick:

        • From 0 to 2gb , format with fat. FAT16 limits partition to to 2GB . Type 06 (FAT16 - BIGDOS). Type 0E (FAT16 - LBA mapped).
        • From 2 to 4gb , format with fat or NTFS.
        • From 4 to ?gb , format with fat32. Type 0B (FAT32 - CHS mapped). Type 0C (FAT32 - LBA mapped)".

        Always try FAT16 first and only later try FAT32. (in compatibly with size of the stick)
        With Mkdosfs.exe used to format the drive, Fat32 partitions can be larger than 32GB.

      • To use multiple partitions: run UBUSB first, then use another partition utility (XP disk management included) to create up to three partitions (there's not enough unused bytes in the mbr to support four), then run UBUSB again with "Don't Modify MBR Boot Code" and "Don't Modify Partition Table" checked and the new mbr from your usb drive should now be syncronized with with the kicker image.
        Remember that if you create additional partitions (or modify the partition table in any way) after running UBUSB then you'll need to run UBUSB again and atleast select "Tools"->"Create Kicker CD Only" to syncronize your kicker images with the new mbr/partition table.
        Also, remember that Windows/PE/UBCD4Win/BartPE will only "see" and be able to use the first partition on a removable type drive. So you'll only be able to see additional partitions from UBCD4Win if you're using a usb hard drive - Linux doesn't have this limitation.

        With Tools > Set First Partition Size, The menu option to set the partition size has been removed since it's part of the main interface now, there's a new textbox where you can specify a custom size (in MB) for the partition and there's also a new "AutoSize" checkbox (which is checked by default) that assumes the largest capacity for the drive/file system.

        ???if you want to use multiple partitions, use the built in backup/restore functions. Before restoring to the destination drive, you can set the partition size you want. Just make it a little smaller than the default value that's displayed in the textbox so there's some free space at the end of the drive then do "Tools -> Restore USB Drive From Backup". Now you can use linux cfdisk (or any other utility that supports multiple partitions on a flash drive) to create your extra partition(s).

      • The default settings are preconfigured to result in a bootable USB drive with the most compatible features and the fastest boot options.
        To use them, make sure that nothing is checked (except for Create CD Image): choose Grub4dos as the bootloader, and make sure "Create CD Image..." is selected (don't uncheck "Create CD image for USB Boot with No Bios Support"). This will create boot options called "Compatibility Mode" and "Compatibility Mode (Memory Mapped)" in your boot menu entries when grub4dos is selected as the bootloader.
        Booting with either of these options usually cures the 0x7B BSOD problem and the "PE-Boot (Memory Mapped)" boot option is usually the most compatible and the fastest of the boot options because it loads kicker.img into ram before booting it instead of booting it directly from usb.
        The "PE-Boot (Compatibility Mode)" is created if Grub4dos is selected for the bootloader, and %USB%\images\kicker.img doesn't already exist.
      • The "Create CD Image..." option of the program creates a cd image called "NoUSB.iso" that can be burned to cd to be used to initiate usb booting on older systems that can't natively boot from usb[15].
      • The program creates NoUSB.iso in the root of your build folder, and places a copy on your usb drive so a matching kicker cd will always be available for the stick when you need it. You'll always be able to burn a new one and know that it matches the usb drive.
      • The "kicker.img" and "memkick.gz" files that are created in the build folder with the ISO are the same files that are used for NoUSB.iso but you can also add them to your own multiboot cd/dvd or place them in the "Kicker" plugin to add them to your UBCD4Win cd/dvd.
        The .img only consists of the boot and initial startup files of the UBCD4WIN environment. UBUSB parses the same txtsetup.sif file and uses the same boot drivers for the kicker image as PE/UBCD4Win does when it boots. You can look in UBUSB.log to see what txtsetup.sif sections are being parsed and what drivers are being copied to the image. Only the required boot files and drivers are copied to the image and it would be pointless to include anything more since the image disappears from ram when control is passed to the usb drive.
      • Use ImgBurn and burn the file NoUSB.iso to a CD. When burning disks, we recommend using ImgBurn which is also included with the project or can be downloaded and installed from their website.
        If using a USB flash drive or hard drive... check it for errors. Errors are usually not from the included files themselves but usually from either a poor quality disk ( CD/DD ), disks that are incompatible with the burner, burning the disk at to fast of a speed, bad CD/DVD burner drive... or the software used to burn them to the drive.
      • When booting, the "kicker" boot options are only available if Grub4dos is used.
        The kicker image is booted using Grub4dos not Syslinux, which means that you can use the kicker cd to boot your usb drive, but you can't add the kicker image to your drive and use Syslinux to boot it. Syslinux can now be used on XP, Vista and Win7, but Grub4dos is still suggessted so the fast booting kicker images will be added to your USB boot menu as well as the cd iso image boot menu. "Memory Mapped" is usually the fastest.
      • The kicker image can boot straight to ubcd4win.
      • UBUSB uses the following for the kicker image if it exists in the same directory that it's running from:

        • menu.lst (Grub4Dos boot menu options)
        • direct.lst

      • v1.0.46 added support for manually customizing your kicker cd.
        select "Customize Kicker CD" and when prompted you can add your own images and menu entries:
        There's a new option to add custom boot options to your kicker cd. When enabled, it will display a message box just before creating the iso telling you to add your customizations now and click OK when you're finished. This is handy for customizing menu.lst or syslinux.cfg and adding other multiboot options like memtest, spinrite, dban, etc... (why waste the other 660mb?). To change the default, edit /menu.lst and change "default 0" to "default 11" or whichever selection you want to be the default.
      • You can modify the contents of the drive and even switch between Syslinux, Standard and Grub4dos bootloaders without having to create a new cd, as long as you don't switch between Fat16 and Fat32.
        Kicker.img is fixed to the MBR. The USB drive and kicker.img need to have the EXACT same checksum for the MBR so any changes done to your USB drive MBR need to be done to the kicker.img MBR as well. Changing partition result to another MBR, and this gives another checksum. Checksum is not valid anymore, hence the BSOD 0x7b which creates the need to adjust kicker.img checksum again. Your kicker cd only has to match the MBR of your USB drive so the only time you should have to make a new cd is if you change between Fat16 and Fat32.
        You can now run UBUSB, then add partitions, then select Create Kicker CD Only now, and it'll syncronize your kicker image with your usb drive (no need to format and copy files again).
      • You should be able to create a kicker cd without disturbing your existing usb drive. Before doing this, I strongly recommend making a backup image of your usb drive with one of the utilities included in UBCD4Win like SelfImage so you can restore it if things don't go as expected.
        Run UBUSB again and select "Tools -> Create Kicker CD Only". This will (re)create and sync kicker.img, memkick.img and NoUSB.iso in the root of the folder that it's running from then copy NoUSB.iso to the root of the usb drive and both kicker.img and memkick.gz to the images folder on the usb drive. I designed it this way so that all images would match at all times and a working NoUSB.iso will always exist on the usb drive and can be burned to cd at any time if needed.
        Technicalities of adjustments needed to mbr are here.
      • When kicker cd creation was not supported on Vista, the only configurations that could work under Vista were Fat16 or Fat32 using Grub4dos as the bootloader and a kicker cd could not be made.
        From 1.0.47, UBUSB could create a kicker cd on 32-bit versions of XP, Vista and Win7.
        You could not create the kicker cd on win 7 64bit. Its option was greyed out. That was because UBUSB used VDK to mount the kicker image so that it could be formatted and have files copied to it. VDK is 32-bit but even if it were 64-bit, it's not digitally signed which 64-bit versions of Vista/Win7 REQUIRE. Your only option to create a kicker cd was to install XP Compatibility Mode but that requires Win7 Pro or Ultimate.

        With the new UBUSB v1.0.48 you can now do almost everything UBCD4WIN/UBUSB Related within Windows 7 without having boot into XP.
        ImDisk by Olof Lagerkvist is now used to mount the kicker image. It has a signed 64-bit driver. ALL functions of UBUSB which did not work prior to UBUSB v1.0.48 should be COMPLETELY compatible with all 32 and 64-bit versions of windows from Win2k through Win7.
        UBUSB installs ImDisk as a system service/driver and then starts it. After the kicker image is mounted and files copied to it and then unmounted, ImDisk is stopped and uninstalled. If ImDisk was already installed before running UBUSB then it won't be uninstalled and the running state will be preserved.
      • The 1.0.50 option opens a new window where you can select UBCD4Win/BartPE ISO images that will be booted directly from RAM using FiraDisk (File/RAM Disk driver for Windows).
        The UBCD4Win plugin Ramboot-Config.cmd creates a compressed copy of your existing UBCD4WinBuilder.iso (%UBCD4Win%\plugin\RamBoot\files\RamBoot.iso). All other added iso images are also compressed to about half of their original sizes to save space on your usb drive. You add the images through the "ISO Images" section and a corresponding entry will be added in the boot loader menu. You can have as many (compressed or uncompressed) UBCD4Win iso images as you have room for on your (cd/dvd/usb) media, and you can edit the boot menu text for each image.
        Using Grub4dos, you can boot an ISO image of BartPE/UBCD4Win and remove the usb drive after it's booted because it runs completely from RAM. Since the images are booted from ram, you'll need about 1GB of ram to boot a 700MB iso image (this will leave about 300MB for UBCD4Win). You will need enough RAM to cover the image+UBCD combination you want to load. You are only limited by the amount of ram and the size of your drive.

      • USB Drive backup / restore has been implemented: The backup function simply archives the contents of the drive into a zip file and the restore function uses the currently selected options (partition/format/bootloader) but then unzips the archive to the drive instead of copying the contents of the BartPE folder. You should be able to restore to any usb drive of any size.
        - To backup your drives, go to "Tools -> Create Backup of USB Drive". This will prompt you to enter a name (without extension) for the backup and will create a zipped file with that name in the same directory that you're running UBUSB from that contains the contents of your usb drive. The backup function simply archives the contents of the drive into a zip file. It only backs up files and folders so it can be restored on different size drive, with a different filesystem and even using a different bootloader.
        I added "open" and "save as" dialogs for the restore/save usb drive functions so you can restore/save from any location and not just the current directory.
        - To restore your usb drive from a backup, go to "Tools -> Restore USB Drive From Backup". This will prompt you to enter the name of the backup (without the .ZIP extension and is expected to be in the same directory that UBUSB is running from).
        This will partition and format your usb drive with the currently selected filesystem and bootloader options then extract the contents of the backup file to your usb drive and make the required modifications to the mbr and boot sector.
      • You do not need a valid source/BartPE folder to restore a drive
      • UBUSB uses the txtsetup.sif file and drivers from the usb drive itself it they exist. This means that all you need to create a complete usb drive is UBUSB.exe and the backup zip file.

      • UBUSB only creates a new syslinux.cfg if it doesn't already exist so you can adjust this value yourself be editing the syslinux.cfg that the USB-Boot plugin uses.
        UBUSB only appends and does not overwrite any entries in syslinnux.cfg

      • UBUSB copies itself to the USB drive after it's finished. This makes it easy to test boot it a virtual machine on any computer (using the "Test USB" function) after making changes.
        Qemu is used for the virtual machine.
        1.0.51 has an option to adjust the amount of ram allocated to Qemu when test booting the usb drive: Tools -> Test Boot With Qemu -> Adjust Qemu RAM . The default was/is 256 which is enough to boot the original and kicker methods but a default UBCD4Win iso is about 700mb which requires about 1024mb when using the new option to boot the iso directly from ram. NOTE* that If you click "Cancel" then it will be reset to the default value of 256mb
      • You can save the settings you used so they are pre-loaded at next invocation of UBUSB: File -> Save Options to File

      This post has been edited by LeMOGO: 30 December 2010 - 07:13 AM


      #678 User is online   pcuser Icon

      • Project Programmer
      • PipPipPipPipPipPipPip
        • Group: Moderator & Development
        • Posts: 4276
        • Joined: 20-November 04
        • Gender:Male
        • Location:Kneebrasskee

        Posted 31 December 2010 - 01:51 AM


        THANK YOU!!
        If you're afraid of taking any chances then the chances are great that you will never learn anything

        Multiboot Plugins - UBUSB (Ultimate Boot USB) - EzPcFix - RootKitty - Network Configuration Utility - UnIsoFS - A Small Linux Distro - SELogger - HashME - WSock - My Paypal

        #679 User is offline   Bandung Icon

        • Newbie
        • Pip
          • Group: Members
          • Posts: 2
          • Joined: 30-October 08

          Posted 02 January 2011 - 05:00 AM

          I am getting the run-time error "6" Overflow consistently. I get it on my vista computer. It used to create the bootable usb drive but no more. It started after I installed a second copy of UBCD4Win in another folder called UBCD4Win2003. But even if I delete that directory and start afresh, the problem remains. I am building from a Windows XP SP2 disk and the resulting iso works ok within VirtualBox.

          I have downloaded vbrun60sp6 thinking it might be something with my vbasic 6 runtime but that doesn't help.

          I have uninstalled and re-installed UBCD4Win several times, including all copies. I am using the latest UBUSB. If I go all the way back to ver 1.0.47 the problem still occurs. IF I use version 1.0.43, the UBUSB.exe program hangs after the format.

          I have changed to another USB Drive and the problem still occurs. Reformatted the drives, problem still occurs. I have pointed the BartPE directory setting to any directory on the C drive to see if the BartPE directory was the problem and if the utility would copy anything over to the USB drive and still I get the error. I have set the don't modify, don't format options and turned off the cd image creation so that I could just see if the UBUSB.exe would copy, but the run time error "6" keeps occurring.

          So I pulled out my netbook, copied over the UBCD4Win folder on my desktop vista machine which was having the run-time error to the netbook's c drive (this is an XP machine) and ran UBUSB from within that directory. To my surprise, I still got the run-time error "6" overflow. I am now in the process of re-installing UBCD4Win onto the netbook, creating the BartPE folder and the UBCD4WinBuilder.iso so that I can see if my XP machine will run UBUSB.exe to completion.

          I have pulled out the usb drive and clicked on UBUSB.exe to see what happens. I get run-time rror "9" subscript out of range error. This does not occur when I click on UBUSB.exe on my XP machine. The program waits for a USB key to be plugged in.

          I have run a registry cleaner and gotten rid of any empty registry keys plus a few other anomalies due to previously removed programs and file associations. Still the problem remains.

          The log file from the Vista desktop machine shows the program stopping at the copy function. The drive is formatted correctly and I can manually copy files into it. Windows Explorer shows that the freshly formatted USB drive is properly mounted but for whatever reason, UBUSB.exe doesn't think its there after the format and MBR creation. I am at a loss as to what to do next. Here is the log.

          02/01/2011 4:34:25 AM - UBUSB Version 1.0.51

          02/01/2011 4:34:25 AM - Windows Vista/Server 2008 Service Pack 2 (6.0.6002)
          02/01/2011 4:34:25 AM - Platform ID = 2
          02/01/2011 4:34:25 AM - 64-bit

          02/01/2011 4:34:27 AM - Current Options...

          02/01/2011 4:34:27 AM - [Options]
          02/01/2011 4:34:27 AM - Don't Modify MBR Boot Code=0
          02/01/2011 4:34:27 AM - Don't Modify Partition Table=0
          02/01/2011 4:34:27 AM - Don't Format Partition=0
          02/01/2011 4:34:27 AM - Filesystem=Fat32 - LBA
          02/01/2011 4:34:27 AM - BootLoader=Grub4dos
          02/01/2011 4:34:27 AM - BartPE-Folder=C:\UBCD4Win\BartPE
          02/01/2011 4:34:27 AM - Don't Copy BartPE Folder=0
          02/01/2011 4:34:27 AM - Create CD Image for USB Boot with No Bios Support=1

          02/01/2011 4:34:27 AM - Drive Type : Fixed Drive (HDD)
          Total Cylinders are : 38913
          Tracks per Cylinder are : 255
          Sectors per Track are : 63
          Bytes Per Sector are : 512

          02/01/2011 4:34:27 AM - WARNING!!! YOU ARE ABOUT TO WIPE OUT ALL DATA ON DISK

          Drive Letter: D:

          A single Fat32 - LBA partition will be created
          Standard XP boot code will be written to the MBR
          D: will be formatted as Fat32 - LBA
          Grub4dos bootsector/bootloader will be used
          All files/folders from C:\UBCD4Win\BartPE will be copied to D:
          A 40MB image file will be created and mounted on drive letter Z: then formatted as Fat32 - LBA


          02/01/2011 4:34:27 AM - Writing boot code to the MBR
          02/01/2011 4:34:28 AM - Clearing Partition Table... (writing 0x00 to bytes 446 through 512 of MBR)
          02/01/2011 4:34:28 AM - Clearing 0x55,AA signature from first 63 sectors... (writing 0x00,00 to bytes 511 and 512 of first 63 sectors)

          02/01/2011 4:34:29 AM - Writing new partition...

          02/01/2011 4:34:29 AM - Setting active/bootable flag for first partition (writing 0x80 to byte 447 of MBR)
          02/01/2011 4:34:29 AM - Setting starting head for first partition to 1 (writing 0x01 to byte 448 of MBR)
          02/01/2011 4:34:29 AM - Setting starting sector for first partition to 1 (writing 0x01 to byte 449 of MBR)
          02/01/2011 4:34:29 AM - Setting starting cylinder for first partition to 0 (writing 0x00 to byte 450 of MBR)
          02/01/2011 4:34:29 AM - Setting partition type for first partition to Fat32-LBA (writing 0x0C to byte 451 of MBR)
          02/01/2011 4:34:29 AM - Setting ending head for first partition to 254 (writing 0xFE to byte 452 of MBR)
          02/01/2011 4:34:29 AM - Setting ending sector for first partition to 63 and ending cylinder to 0 (writing 0x3F,98 to bytes 453 and 454 of MBR)
          02/01/2011 4:34:29 AM - Setting first sector of first partition to 63 (writing 0x3F,00,00,00 to bytes 455 through 458 of MBR)
          02/01/2011 4:34:29 AM - Partition Length = 8188000 (4072 MB)
          02/01/2011 4:34:29 AM - Setting total length for first partition (writing 0x60,F0,7C,00 to bytes 459 through 462 of MBR
          02/01/2011 4:34:29 AM - Updating cached partition table...

          02/01/2011 4:34:29 AM - Partition Table Successfully Updated.
          02/01/2011 4:34:29 AM - Running C:\UBCD4Win\touchdrv.exe
          02/01/2011 4:34:29 AM - Extracting mkdosfs.exe

          02/01/2011 4:34:29 AM - Formatting volume D: as Fat32 - LBA

          02/01/2011 4:34:29 AM - C:\UBCD4Win\mkdosfs.exe -v -F 32 -n UBUSB D: 8188000

          02/01/2011 4:34:39 AM - Copying files/folders from C:\UBCD4Win\BartPE to D:

          This post has been edited by Bandung: 02 January 2011 - 05:16 AM


          #680 User is offline   Bandung Icon

          • Newbie
          • Pip
            • Group: Members
            • Posts: 2
            • Joined: 30-October 08

            Posted 02 January 2011 - 06:30 AM

            I tried one other thing. I disabled the option to copy the BartPE folder over to the USB drive and to my surprise the program continued onto the next stage. It created the kicker.img and eventually finished after asking if it should create some missing directory. So thinking that the problem might be with the size of the BartPE folder, (it was 2.28 GB) I kept deleting apps within the BartPE until it was under 2 GB and the run-time error "" overflow disappeared. The problem is not with the iso or some visual basic programming restriction as I originally thought. Its a copy size limitation. UBCD4Win created the DVD sized iso and it works within VirtualBox.

            Using FAT32 LBA to create a 4 GB usb partition does not imply that the utility can copy 4 GB of BartPE files into the partition. I guess the work around would be to add the additional files after UBUSB creates the bootable usb drive with a down sized BartPE folder.

            Any chance that this folder size limitation could be overcome. IF the workaround `works` then it won`t be the end of the world for me since the added weight`` came from the many PortableApps applications that I had added and they can be easily removed and added back to the usb drive without any plugin modifications.

            #681 User is offline   LeMOGO Icon

            • Newbie
            • Pip
              • Group: Members
              • Posts: 2
              • Joined: 27-December 10

              Posted 02 January 2011 - 06:14 PM

              View Postpcuser, on 31 December 2010 - 01:51 AM, said:


              THANK YOU!!


              I'm surprised you monitor this thread, I thought it was dead.
              Thank you so much for your work and help. I will surely make a donation. You've convinced me that free software developpers DESERVE the $.

              I'm still reading everywhere, trying to understand what to look for, It's beginning to take too much time. I'm writing as I go, a manual would surely have been profitable. I spent sooo much time on this because I think it is worth it.

              Thank you for everything!

              • (46 Pages)
              • +
              • « First
              • 44
              • 45
              • 46
              • You cannot start a new topic
              • You cannot reply to this topic

              1 User(s) are reading this topic
              0 members, 1 guests, 0 anonymous users