Tripredacus

I put the .cmd in the image, or deploy it after it but before the first reboot, then just put the path to the .cmd in the XML.

I am working to fill that partition with the same data also put onto the main partition so that I can do a diff on it for comparison reasons. It is taking a long time to copy the files. I've only got 170GB onto it so far. So it might be a couple of days before I can get to the other tests.

Here is the Drive D in explorer. Now I am seeing what you are getting at here...

I have a drive D: in Explorer now. If I try to open it, it asks to format.

Regular testing, without the use of grub or other tools. WinPE 3.0 x86 and Windows 7 Pro SP1 32-bit. Only using Diskpart for disk manipulation. Example where I create 1 14GB partition for the OS, then "remainder" for data. The second partition still ends within the 2.2TB boundary. Unallocated space cannot be manipulated. The same instance, Diskpart cannot create a partition here, the reasons it gives do not match with the current situation: Creating a smaller partition for the OS (or shrinking a 2.2TB partition) results in a divider between the usable Unallocated space and the not usable, in Disk Management. You can create a partition with Diskpart, only in the 195.31GB portion of the screenshot, or create new Simple volume with Diskmgmt, but the same issue with the 746.52GB Unallocated portion as before. However, there is this situation now with this testing environment. I can boot Windows 7 on a 2.2TB partition created with Diskpart, but not if created by Grub4DOS. I can work on this again next week starting Monday. If you want me to do any tests on the disk after being manipulated with Diskpart vs with Grub, I should be able to do that also.

Diskpart in WinPE 4, 5 and 10 will automatically convert the 3TB disk to GPT if not initialized. It does this after just these commands: sel disk 0 clean create part pri size=300 Or any size, it doesn't matter. With a smaller disk, it does not convert to GPT. I have now used WinPE 3.0 x86. Diskpart there lets you create a partition without automatically converting the disk. I have also changed to an older motherboard, the Intel D410PT with 2GB RAM. Because you said this is for OS that doesn't support GPT, then I can test with Windows 7 Pro SP1 x86, which does not support GPT or EFI booting. I cleaned the disk in diskpart in WinPE 3, then reboot into DOS and run the Grub commands from before. I then boot back into WinPE 3 and I check with diskpart and the two partitions are there and Part 1 is active. Format that part with NTFS and then apply the Windows 7 Pro SP1 32bit image onto it. What I get is the flashing cursor. I have still not formatted the second partition. I will now repeat the test but leave out creating the second partition in grub to see if the OS will boot.

It is not booting, or the motherboard is not seeing the volume as being bootable, so it doesn't even attempt it. I have tried different images, my regular Win7 images are designed to have the recovery partition and do not normally boot on a single partition, or where the boot volume is on the first partition. However, my System Builder images are, but they do not boot either. When using my normal process, on a 3+ TB disk (in the past) there would end up having a partially formatted disk, the OS would boot but there would be an unallocated portion "at the end" in Disk Management that wouldn't let you do anything. Currently, that is not even working because Diskpart is converting the disk to GPT automatically. This means the usual Win7 deployment will fail entirely. My DOS image fails to deploy also. It may be due to this version of PE being an issue. Have an older one I will try using for deployment instead.

The error you see, the "subsystem needed" indicates you are using the wrong architecture version of imagex.exe for your PE. It means you have a 32bit WinPE and your imagex.exe is 64bit, or your WinPE is 64bit and your imagex.exe is 32bit.

I could have rechecked it with RPM after cleaning the disk in diskpart but did not. Alas, Windows 7 64bit doesn't even boot, with and without BCDboot being used. Meaning, the board boots directly into the BIOS/Setup, no errors from the OS itself. I have attached the disk into from Diskpart after running the commands posted above in Grub. Drive letter was N in the information due to a script that is run in my PE to change the C drive to N drive. You see I change it later on after formatting, and before I imaged that partition. diskpart_info.txt

the command is like so: cat --hex--skip=446 (hd1)+1 an error you've made in the past, however I found the correction here: http://reboot.pro/topic/18611-vista-wont-boot-error-17-file-not-found/#entry173322 Of course, no one is immune from the scourge of typos: PS: the HDD shows as Disk 2 (or Disk 1) because my DOS is on a USB key. There was something up with how Fdisk deleted the partitions, which is why it was showing up as 782GB or so. When I booted into WinPE, Diskpart also showed no partitions and with that ~782GB as free space. I ran the CLEAN command and it returned to the 2700GB that is expected. I will go about putting both Windows 7 Pro 64bit and 32bit on this disk, but it may be a bit of time because I may need to add a storage driver.

The delay to upload these images was making me nuts. Here is how Ranish Partition Manager sees this disk: I had removed the existing partition with FDisk. I am not sure what to put into these fields to make the partition you want.

Is it required to "install" an OS or can I just lay one onto it using DISM or Imagex? I am going to be mainly limited by the board I have available for doing the testing, which is currently going to be in the current 100 series (150/250) Intel Chipset. So if I use existing images, I may be able to boot Windows 7 or Windows 10. If I am to install an OS using the setup media, I can install any Windows version. If the hardware being used is a problem, I may be able to borrow an older (like 3 years or so) chipset board for testing. I will look into this on Monday, and will see if I can get the sector count of the disk. For which tools to use, my primarily operating environments are WinPE v10 x64 or DOS 7.10. If something needs to be done in Windows then I would likely use Windows 7 to do it.

I have a 3TB Seagate Barracuda XT, ST33000651AS. If you want, and if this is the correct type of disk, I can do any specific testing on it if you provide the commands I should use.

Hey Jan, MSFT = Microsoft, we are MSFN

There is certainly a difference. I am using Firefox 55 on Windows 7. It shows like this: Here it is with 400% zoom: The IPB CSS fails validation. Would it kill them to fix their syntax errors before pushing new software updates?

What is the hardware required? A 4TB+ disk or virtual disk? Or do you think such testing should only be performed on a single physical disk and not on RAID arrays or VM disks?

Locking this thread. Use the pinned thread for discussion on this topic. http://www.msfn.org/board/topic/176950-msfn-will-be-taken-offline-12-august-2017/

Yes, Xper had been wanting to sell the site, but I do not know of any details regarding price or if anyone was interested or what.

It is a longstanding issue and Xper has said it is not only the financial burden but also there is no time he has to put into the forum. You can see from this post how long it has been known publicly about this: http://www.msfn.org/board/topic/162548-multiple-messenger-recipients/?do=findComment&comment=1044695

Well we're not going to stop doing our mod duties until then. There are enough entries into that announcement topic now with it being in General Discussion. Do not create additional topics of this, you can post into this one: http://www.msfn.org/board/topic/176950-msfn-will-be-taken-offline-12-august-2017/

On some pages you can see this announcement by Xper regarding the MSFN forum. http://www.msfn.org/board/announcement/33-msfn-will-be-taken-offline-12-august-2017/ Changed title, formerly: "MSFN will be taken offline 12 August 2017." New announcement: http://www.msfn.org/board/topic/176958-msfn-will-be-online-one-more-month/

I had a similar experience from buying a cheap notebook AC Adapter on ebay. It melted also. I had taken details pictures of the issue and sent them to the manufacturer. They thanked me for them, but IDK if they ever redesigned their product as I never bought from them again.

Merged

Setup can give this message for a variety of reasons. It shows it in the "image selection" page. On a normal installation of anything Vista or newer, the usual cause of this message is a incorrect XML, pointing to a wim location that is incorrect, having wrong install key, etc. 99.999% of the time, a person wouldn't use Setup to install XP at all, except for that one minuscule case of some Vista beta version allowing for you to install an XP image... *supposedly* as I've only read it and never tried it myself. So with such a generic post as OP made (no details about the PE, the Setup version, media type, etc) I can make a generic response also. And the numbers are on my side that they aren't using some obscure Vista Setup+WinPE combo. PS: jaclaz could have said "why not use imagex.exe to install it?" and I would have had to post this emoticon:

That thread is in the Win9x section, so Win XP and newer content for that area is not supposed to be there. I moved the two posts from the Win9x thread to this thread in the Windows 7 section. If you have any more questions about this change, you can PM me instead of posting a reply.