Jump to content


  • Content Count

  • Joined

  • Last visited

  • Donations


Community Reputation

0 Neutral

About delicatepc

Recent Profile Visitors

1,474 profile views
  1. Hey Jbolsen, thanks for the heads up. I actually ended up doing this on a USB HDD and using the syslinux as a bootloader and chainloading partition 1, 2, 3, and so on. But the problem is still the same: setup/boot.wim needs to reference the INSTALL.WIM from more than one location (or at least be dynamic). Unfortunately its hard coded to look for the install.wim in the sources folder and thats it. There is several work around (one of them is yours, another one is combining the install.wims into one big install.wim) but they dont address the root problem. The reason the root problem is important
  2. Still working on edge with this but i think i know what is happening... Sandisk or specifically usb sticks with the U3 software may be causing the issue with their multiple partitions kind of setup. I believe U3 would have to be removed BOOTMGR to successfully located the BCD. I have tried edge's build and works normally for me. dpc
  3. Nope not anymore. ill see what i can do. dpc
  4. good work randalldale.... i like what I see here. One alternate suggestion is to create the xp image to a WIM file. Then u can use the bootmgr/winre/imagex to deploy. This is possible to do but rather requires a bit of prep work (much of which I am not familar with). dpc
  5. hey edge, goldstick 1.41 should work with syslinux 3.83. Im fairly sure i tested with it. are you running goldstick command after you update the syslinux.exe file? this should be irrelevant but thought I would ask. out of curiousity what changes are you trying to get into goldstick? a month or so ago I sent an updated set of files to add to goldstick to the share. have you tried a complete fresh install of gs onto a usb stick? and are you using usb stick or hdd? dpc
  6. Two things. 1. Can you upload a stripped version of your build? Should be able to fit into 5mb remove all the apps just need the syslinux menu, bcd, bootmgr files etc.? 2. Create a working iso (with update syslinux.exe), burn it, test to make sure it works, and then run (cdrive)\ubcd\tools\win32\ubcd2usb.cmd (cddrive) (usbdrive).... like this "ubcd2usb d: f:" where d: is where my files are located and F: is my usb stick. Ive seen this same issue on my own during testing (several times actually) and it always was a stupid small thing I missed and never thought of posting about once i fixed it.
  7. Did you update the chain.c32 and the syslinux.exe and run the install script again? Possible bad usb stick but less likely. see this thread: http://www.ultimatebootcd.com/forums/viewt...&highlight= dpc
  8. NO I do not want a multiboot DVD - Looking multi-partition USB hdd/stick. If you had READ THE THREAD you would already know that several times. Simply want to tell BOOTMGR to chainload the second partition on a USB HDD at this point.~ dpc
  9. Did you even read the thread? you wrote a super long post fro nothing. Adding another BOOT.wim is easy (this what you describe). How about adding a second INSTALL.wim??? ~ dpc
  10. Reviving slightly old thread.... Before jumping in just want to mention I know that I can chainload a second partition using syslinux. This is more of a question on how to add chainloading of second partition/bootmgr on second partition from within first partition BOOTMGR/BCD I cannot seem to find this documented (or I may not be comprehending what I am reading) in the BCD white paper or the technet reference. I would really appreciate any help you can provide. So scenario is a USB HDD with Win7 X86 (or any vista+ install) ISO extracted to partition 1 which is fat32 and is active (mbr boots th
  11. It works!!! Thank you! I am going to use the patched chain.c32 for now and maybe in the future I will switch to the classic approach you mentioned (but I dont want an extra menu item just for when booting ISO). For my USB installs they are using latest chain.c32 from syslinux and the iso uses all the same files except the script replaces the chain.c32 with the patched one for the iso. Thank you very much,
  12. I downloaded UBCD 5.0b12 and updated the syslinux/isolinux files from syslinux 3.82. I am using Sun Virtual Box to test these ISOs. C:\ubcd-stripped\BOOT\BCDC:\ubcd-stripped\BOOT\BOOT.SDI C:\ubcd-stripped\BOOT\BOOTFIX.BIN C:\ubcd-stripped\BOOT\etfsboot.com C:\ubcd-stripped\BOOT\isolinux C:\ubcd-stripped\BOOT\syslinux C:\ubcd-stripped\BOOT\isolinux\isolinux.bin C:\ubcd-stripped\BOOT\isolinux\isolinux.cfg C:\ubcd-stripped\BOOT\syslinux\chain.c32 C:\ubcd-stripped\BOOT\syslinux\ldlinux.sys C:\ubcd-stripped\BOOT\syslinux\memdisk C:\ubcd-stripped\BOOT\syslinux\menu.c32 C:\ubcd-stripped\BOOT\syslinu
  13. I have been trying to get this to work for a while now and so far nothing I seem to be doing can get it to work properly. On USB it works great but as soon as I get it into ISO format the BOOTMGR cannot find the BCD file it seems. Can anyone give me a hand? Alternatively is there another place I could ask? thanks, dpc
  14. Sry about delayed reply. Logically combining the images into one big one makes good sense when using the stock images. However I am in environment where the images change very constantly (can be biweekly or monthly). I am authorized to deploy said images but combining them is manipulating the image which to a techie is no biggie but to the folks who sign my checks this would be a problem. Dont get me wrong - we do have images that contain multiple images but those are not created by me (or my group). The basic flaw in within setup.exe (that is located in boot.wim) - it looks for setup.exe and
  15. SOLVED!! - See cdbob post in thread for explanation and workarounds. Issue was with design assumption in chain.c32 Original Post
  • Create New...