• Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Aroth

Profile Information

  • OS
    Windows 7 x64
  1. I have a few questions before I attempt my next idea for this image. I know that the basic Windows 7 Setup can run run with just the folllowing DVD: BOOTen-usbootsect.exe.muibcd boot.sdi bootsect.exe SOURCES boot.wim install.wim BOOTMGR Does that mean that the rest of the contents of the \sources\ directory are simply for installing windows from inside another operating system?
  2. Out of memory, back then at Windows 7 gold WAIK: A folder XHOM\ is ignored. You have to specifiy each single file. And wildcards are not supported. Which file size goes to current ISO image? Not sure exactly what you are asking. The image totals out at about 6.7 GB right now. I have used it to install XP Pro to VirtualBox once already without any issues, so it's probably ok.
  3. I don't know you case fully. I'm not used to this approach anymore. I guess: Add all file from XHOM, XPRO folders and files from sub folders And all files below WinXP_Home_SP3 and WinXP_PRO_SP3 ASMS folders. And I386\$OEM$\ - \$OEM$\TEXTMODE, if you use this. Yes, simplified approach: the entire contents of all four XP related folders To clarify: This is not required, if relating files are within first 4GB of DVD media by chance. So would the following work, or would just just give an error? boot\bcd boot\boot.sdi boot\bootfix.bin boot\bootsect.exe boot\ boot\memtest.exe boot\en-us\bootsect.exe.mui boot\fonts\chs_boot.ttf boot\fonts\cht_boot.ttf boot\fonts\jpn_boot.ttf boot\fonts\kor_boot.ttf boot\fonts\wgl4_boot.ttf Win7_x64\boot.wim Win7_x86\boot.wim XHOM\ WinXP_Home_SP3\ XPRO\ WinXP_Pro_SP3\
  4. Setupldr.bin reads first 4GB of DVD. Sort all XP textmode boot files too. So basically the entire contents of all four XP related folders? (XHOM, XPRO, WinXP_Home_SP3, and WinXP_PRO_SP3 in my case)?. Ok, so I did some tests. I took the official Windows 7 x86 Home Premium disk (named X15-65732, labeled GRMCHPFRER_AN_DVD) and made three test images from it. I then booted each disk in VirtualBox In test1.iso, I renamed install.wim to install.gag. This resulted in an error that closed setup.exe In test2.iso, I deleted the entire contents of /Sources/, excepting boot.wim, install.wim, and setup.exe. This image booted into the install and OS Setup select screen with no problems (good way to shave a few hundred MB at the expense of update and possibly repair capability) In test3.iso, I took test2.iso and moved the Sources folder into a new folder titled Win7_x86_SP1 and then copied my bcd file from C:\Win_Installer\boot into the boot folder of test3. This image gave me the missing driver error. Based on this I would believe that the problem lies in it expecting to find \Sources\ on the root of the drive, but that doesn't make any sense. It obviously can find install.wim without any problems, likely by looking relative to boot.wim (i.e. ".\install.wim"), and the only files present in \sources\ were boot.wim, install.wim, and setup.exe. If found the first two or it wouldn't have booted or setup would have crashed out, and I see no reason why setup.exe would have drivers inside it (though I guess it IS possible). I have one last thing to try and thing I will start thinking of other ways to lay out this disk. Folder structure isn't as important to me as having it install x64 windows from inside the x64 PE and x86 Window from the x86 PE, and I think I know how to do that.
  5. Ok, so I am creating an image now using the following line of code: oscdimg -u1 -bC:\Win_Installer\boot\ -l"WINDOWS_AIO_SETUP" -yoC:\TEST\BootOrder.txt -h -m C:\Win_Installer C:\TEST\WIN_AIO_TEST2.ISO BootOrder.txt contains the following boot\bcd boot\boot.sdi boot\bootfix.bin boot\bootsect.exe boot\ boot\memtest.exe boot\en-us\bootsect.exe.mui boot\fonts\chs_boot.ttf boot\fonts\cht_boot.ttf boot\fonts\jpn_boot.ttf boot\fonts\kor_boot.ttf boot\fonts\wgl4_boot.ttf Win7_x64\boot.wim Win7_x86\boot.wim XHOM\ XHOM\SETUPLDR.BIN XPRO\ XPRO\SETUPLDR.BIN The first half of the BootOrder file is from the example on the technet page, minus the file that isn't present in my source. The last six entries are an attempt to make sure all the loaders are at the front of the disk. It just finished creating the image as I typed this, so I will go test it and hope for the best. Update: No go, but I remember now what I was going to try before I ended up working all day yesterday. In the guide I followed to force the boot.wim image to to load install.wim from a different location, steve6375 only copied the boot.wim and install.wim files from the original discs for Windows 7 (Vista he used the entire sources folder). In addition, his mysetup.cmd script that he injects into boot.wim runs X:\Setup.exe in the event that there is not an entire sources folder used (i.e. Win7). The other person in the thread you linked me,, has his script run X:\sources\setup.exe. I will try removing all files except boot.wim and install.wim from the install directories and see where that gets me, and if it still doesnt work, try running sources\setup.exe from the boot image. Update#2: Just had an epiphany.... Does any one know the exact process that is used by the windows 7 PE to load a installer? I was thinking about what you said about odd errors being an indication to just start from scratch, and it made me wonder if the issue is with boot.wim or install.wim. I am going to play with an original disk and see what happens when I cut it down to just the boot and install .wims in the sources folder., also, see what happens when i remove the install.wim file. Basically try to get a normal win7 disk to give me this driver error.
  6. There are TWO things that seems to me "not kosher" though cannot say if they can make a difference. is not a "valid" name (or there is a typo for .\boot\ Usually the switch -u2 is used for Windows 7 install disks. In other words, if I were you I would try full paths and -u2 (though canot say if this will create issues with the XP setup, in which case you can try with -u1 ): oscdimg -u2 -bC:\Win_Installer\boot\ -l"WINDOWS_AIO_SETUP" -h -m C:\Win_Installer C:\WIN_AIO_TEST.ISO jaclaz Heh, yeah that was a typo on my part in the post. Should have been .boot\ When I get home I will try your code line with the -u1 switch, as it creates a disk with both UDF and ISO9660 file systems. (Pretty sure ntdetect, ntldr, and setupldr.bin expect ISO9960 as they run off of a CD normally.
  7. How EXACTLY do you create the.iso? With WHICH tool? With WHICH EXACT command lines? (BTW, and as a "general" advice, sometimes when these "queer" errors start inexplicably to appear, it makes a lot of sense to start again from scratch) As a side note, maybe - if the use of grub4dos is "allowed" - you can replicate what has been done for USB disk/sticks installs: jaclaz Any time I make major changes to the content or file structure, I make a new ISO image from the Win_Installer directory everything is in. I create new ISO files with oscdimg.exe from the Windows 7 AIK. Specifically, I launch an elevated Deployment Tools Command Prompt (it adds the paths for dism, oscdimg, and imagex to the environment) and navigate to C:\Win_Installer. The exact set of commands ran after launching the prompt is cd C:\Win_Installer oscdimg -lWINDOWS_AIO_SETUP -n -h -m -b.\ . C:\WIN_AIO_TEST.ISO As for using Grub4DOS, if it comes down to it, I may not have a choice. I just prefer to have to deal with scripting things to get the disk to boot. Also, I think I am more or less using the same method to force it to grab the install.wim from the right location. The tutorial I adapted is here, and appears to be a final product by steve6375.
  8. Ok so I fixed that odd error I was getting (apparently if \boot\ is the first directory on the rood of the disc, it it cant find or read bcd), but I am still getting the missing driver error. I'm starting to think it hates me...
  9. I am not familiar with 7, but I think it works like Vista or you can try this approach (HUGE .wim): Or this one : Check also this (i presume you might need Google Translate): jaclaz Those all describe the method I used (with slight variations) to make the original Windows 7 AIO + XP Pro disk. While It was able to install any version of 7 from the x86 PE, and I could boot into the x64 PE to repair an existing install, I was looking for a somewhat cleaner install method that didn't require merging install.wim files. That said, I have found a method of altering boot.wim to load a install.wim from a different location. Will test and report back what come of it. UPDATE: Well I have no idea what caused it, but now I cant even boot into the DVD. I keep getting an 0xc000014c error about BCD being corrupted or something. Lovely.
  10. I will certainly do my best to describe the steps I took in deviation from the standard guide if everything works as needed. As for why I wish to use a DVD to do this, it is because they are much cheaper and easier to mail than USB drives. Once I finish the disk I need to ship it to my brother who lives several states away so he can fix his install of XP, and I have neither the funds nor the inclination to purchase and ship a USB drive just for this. Besides, I have an abundance of CDs, DVDs, and DVD9s that I will probably never end up using otherwise. In the off chance I start to run short, I can easily test the ISO in a VM before burning to make sure it will boot properly. UPDATE: The new image with all four setup environments boots and all four environments load with no issues. XP Pro is installing to the VM now. Will test Home and then 7 Ultimate and 7 Ultimate x64 (as those two should give a decent approximation of whether the 7 installs work) afterwards.. UPDATE #2: So XP installs without any issues, and even a slight bit faster than what it did for the original install to the VM. When attempting to install Windows 7, however, I get a most grievous error. It apparently wants a driver that is seemingly missing from the disc I created. That said, all of the files are present on the disk that were on the original Win7 disks. Those images will install to the VM, as will the original merged x86x64 image I created that has all the Windows 7 install.wim images merged into a single large file. It is only appearing on the newer disk. The official Windows 7 w/ SP1 images do not give any errors at all when used to install to the VM, either from boot or from inside the existing OS (XP Pro at the time of attempt). They also load up to the OS Select options without issues when booted from on the physical machine, and they reach the same point when launched from inside my current install of Win7 x64. Have not tested beyond the point of asking for the partition to install to on the physical machine for obvious reasons. The first Multi-boot disk I created, which merged the images from the two (32 and 64-bit) install.wim files, as well as including the 64-bit setup environment for making OS/startup repairs and XP Pro setup files also does not give any errors. I strongly suspect the error stems from the way I have the files set up, with the entire contents of Win7 x86 in one folder (minus BOOT and EFI files) and the contents of Win7 x64 in another. Likely the WinPE is searching for the driver and expecting to look in D:\Sources\, not D:\Win7_x86_SP1\Sources\. Though why it would look there I have no idea as I have not found any drivers in the sources folders, and the environment is running from X:\ and resembles a rudimentary Windows install complete with \Windows\System32\Drivers\ and \System32\DriverStore\, which DO contain driver files. At this point I am lost as all suggestions I find via Google point back to the same two solutions, a bad ISO download or a BIOS issue, neither of which seem to apply here. Suggestions would be much welcomed. UPDATE #3: Looks like I was on the right track with my suspicions before. When boot.wim is loaded, it is hard coded to look for install.wim in D:\Sources\, much the same way that the XP Setup is (was) hard coded to look for SETUPLDR.BIN in D:\I386\. The difference being that we can edit the XP files to place SETUPLDR where we want, with limitations, but changing the location of install.wim is just not possible afaik. This sucks...
  11. That's what I was thinking. Not sure if it was because I was running an x64 system, or if it was because I was running NT 6.1 (Windows 7) and trying to install NT 5.1 (XP). Sometimes it doesn't like that lol. Anyways, so far it has worked. Was able to get the files I needed for the boot directories, and the test CD with Pro and Home worked without any issues. Fixing to try integrating those files with my main disc and see if bootmgr will load what I need it to. Just not sure if I need the PRO1 and HOM1.DAT files, and if so what to do with them...
  12. Naah : IC=Home IP=Pro jaclaz *facepalm* I've been working on this every night for a week and somehow I didn't see that... wow..... Well crap. Had a feeling this would happen, but it seems I cannot follow that guide without some tricks. Right off the bat I encounter an issue with trying to run winnt32.exe /noreboot as the system I am working on (as well as all other systems I have access too) are running Windows 7 x64. Compatibility issues abound.
  13. Yes. BUT .....(isn't there always a but? ) The idea (that you are strongly advised to follow, though most probably seemingly more complex) is: FORGET (temporarily) whatever you have read, here an elsewhere, on the XP install topic FOLLOW (to the T) the given guide (adapting it to the various XP's you may have) and "to the T" means DO NOT introduce ANY change of ANY type to the given procedure hopefully you should be able to have a separate DVD capable of booting ONLY the XP's THEN, (only once you have succeeded in replicating the guide) introduce your own variation (making use of the 7 BOOTMGR) It is seemingly longer, but since quite a few steps are involved in replicating what is explained on the cited guide, IF - by any chance - you commit a mistake in any of the step (and/or anything needs to be tweaked for XP SP3) AND add to it your variation in one go, noone will be able to help you as the possible issue cannot be "traced" back to either the guide, your replicating it or your introdiced variation. jaclaz That makes sense. Time is not an issue for me, though I'm sure my step-brother would like this done sooner rather than later. That said I would much rather send him something that I know 100% will work, so testing each step individually is what I will do. One last question before I get started tonight though. Do you know of a guide for integrating setup for both Pro and Home onto a single disk, and if so, could you link it for me? From what I read, the WIN51, WIN51IC, and WIN51IC.SP3 files need to be on the root of the drive, but doing so while attempting to have both Home and Pro would result in one set overwriting the other.
  14. Every guide I read describing that process also goes into using CD Shell and the .dat boot sector files from the original XP disks. I wasn't sure if that was the only way, or if I could still have bcd and bootmgr loading SETUPLDR.BIN once I do that. Will try it tonight when I start working on the disk again. Just to clarify from what I read, if I wish to use the Boot Configuration Data file (BCD) and BOOTMGR from the Windows 7 installers I already incorporated, I would need to use a HEX editor to change all instances of I386 in SETUPLDR.bin to whatever 4 character folder I use, then edit txtsetup.sif to point to the location of the remaining install files. Then have BOOTMGR load SETUPLDR.BIN from, say, /XPRO/, instead of WINXP_PRO_SP3/I386? (as it would no longer be there). Corrrect?
  15. Plenty of them. The XP Setup is HARDCODED to <root>\I386. BUT, the solution to this issue has been found since several years, you evidently missed the good ol' guide: jaclaz So there is no way to make a multiboot that has both XP Home and XP Pro without using a custom shell like CD Shell and BartPE?