Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


delicatepc

Member
  • Content Count

    24
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

0 Neutral

About delicatepc

Recent Profile Visitors

1,298 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 is that usb sticks are not super friendly to partitioning (especially in windows). But in any case would appreciate if you posted your config/grub files. as for the reason you cant install win7 except off partition one is likely because win7 installer only mounts the first partition for data. thanks, dpc
  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. by the way is there a mismatch between your windows bootmgr files (ie you are using the files all from the same source like windows vista x86?). I think i encountered this issue when attempting use Win7 bootmgr and win vista other files (or something along those lines). dpc
  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 this partition first). Partition 2 is a simple ntfs partition with Win7X64 ISO extracted to it. So what I would want to do is one of two things: A ) Add Entry to Partition 1 BCD file specifying BOOTMGR on partition 2 OR B ) (this one makes easy sense to me) Add entry to Partition 1 BCD telling it to Load Partition 2 (partition 2 could be anything at that point couldn’t it?) The commands that I would envision doing this are below but I don’t know how to fill the highlighted parts. bcdedit /store %BCD-File% /create /d “Boot to Partition 2” (is there another parameter to go here like /application BOOTSECTOR or similar?) # It creates entry in BCD file on partition 1 of USB HDD, # gives description/name of entry as “Boot to Partition 2”, # Automatically generates a GUID for entry bcdedit /store %BCD-File% /set %GUID-of-created-entry% DEVICE ?????? # Sets the DEVICE parameter of entry we just created to ????? # bcdedit /store %BCD-File% /set %GUID-of-created-entry% OSDEVICE ?????? # Sets the OSDevice Parameter of entry we created to ????? # bcdedit /store %BCD-File% /displayorder %GUID-of-created-entry% /addlast # Adds our entry as the to the end of the list. Some online examples show “bcdedit /set {GUID} device partition=D:”. I would then theoretically need to do “bcdedit /set {GUID} PATH \BOOTMGR” and “bcdedit /set {GUID} /application BOOTSECTOR”? Once again the goal would be to chainload the BOOTMGR from the second partition (or just chainload partition 2 period – option B above) from within the first BOOTMGR. any ideas appreciated. thanks, dpc
  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\syslinux\reboot.c32 C:\ubcd-stripped\BOOT\syslinux\syslinux.cfg C:\ubcd-stripped\BOOT\syslinux\vesamenu.c32 Yes see above. I downloaded the Vista Recovery Environment ISO from here: http://neosmart.net/blog/2008/windows-vist...-disc-download/I downloaded the 32bit edition, extracted with 7zip and properly renamed the files and folders to all caps (see above). I confirmed that the plain ISO boots to Vista Recovery environment. BCD file is default one from this ISO and not modified. etfsboot.com was not included on this iso so I downloaded it from here: http://www.mydigitallife.info/wp-content/u...01/etfsboot.com isolinux.cfg entry DEFAULT main LABEL main KERNEL /boot/syslinux/menu.c32 APPEND /ubcd/menus/syslinux/main.cfg and then ubcd/menus/syslinux/main.cfg looks like this: MENU INCLUDE /ubcd/menus/syslinux/defaults.cfg DEFAULT /boot/syslinux/menu.c32 PROMPT 0 LABEL - MENU LABEL BOOTMGR COM32 /boot/syslinux/chain.c32 APPEND boot ntldr=/BOOTMGR MENU SEPARATOR LABEL - MENU LABEL Boot next device TEXT HELP Boot next device in the boot sequence. Supporting BIOS required. May not work with all systems. ENDTEXT LOCALBOOT -1 LABEL - MENU LABEL Reboot TEXT HELP Reboot the PC ENDTEXT KERNEL /boot/syslinux/reboot.c32 APPEND - MENU SEPARATOR ISO size is 385mb with ubcd and the Vista Recovery environment. With the ubcd files and BOOT.WIM stripped out its 5MB. I am using the one included with UBCD 5.0b12 = mkisofs 2.01-bootcd.ru (i386-pc-mingw32) I tried both the those mkisfofs lines and the result is still the same (File: \Boot\BCD Status: 0xc000000e Info: An error occurred while attempting to read the boot configuration data.) The way I create the iso is run administrator command prompt, CD c:\ubcd-stripped\ubcd\tools\win32\ubcd2iso\, and then run either ubcd2iso or ubcd2iso1 or ubcd2iso2. the script variables are: (script) (ubcdfileslocation eg. c:\ubcd-stripped) (location/name of what i want the ISO to be eg. c:\ubcd-stripped.iso) ubcd2iso = original build script from ubcd 5.0b12 ubcd2iso1 = modified mkisofs line to look like first one in quote: "%~p0\mkisofs.exe" -iso-level 4 -l -R -J -joliet-long -D -V %VOLUME_ID% -o "%a2%" -b "BOOT/isolinux/isolinux.bin" -c "BOOT/isolinux/boot.catalog" -hide "BOOT/isolinux/boot.catalog" -hide-joliet "BOOT/isolinux/boot.catalog" -no-emul-boot -boot-load-size 4 -boot-info-table -graft-points /BOOT/etfsboot.bin=BOOT/etfsboot.com . ubcd2iso2 = modified mkisofs line to look like your second one in quote: "%~p0\mkisofs.exe" -iso-level 4 -r -joliet-long -D -V %VOLUME_ID% -o "%a2%" -b "BOOT/isolinux/isolinux.bin" -hide "boot.catalog" -hide-joliet "boot.catalog" -no-emul-boot -boot-load-size 4 -boot-info-table -graft-points /BOOT/etfsboot.bin=BOOT/etfsboot.com . Please feel free to download the files I provided in the beginning of the thread. They are the same files I am using. What do I seem to be missing? thanks, dpc
  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 install.wim specifically in SOURCES folder and there is no easy way to change this without modifying boot.wim (to get access to the setup.exe within it). Also its one thing to add a entry to BCD... its quite another to slipstream images (WAIK install, learning the specifics etc.). Quite a bit of overhead. The only real compromise I have found is multiple partition and chainloading the other paritions. This solution still has several problems so I will not be using it. dpc
  15. SOLVED!! - See cdbob post in thread for explanation and workarounds. Issue was with design assumption in chain.c32 Original Post
×
×
  • Create New...