Tripredacus

I should have four-five notebooks but I can only find two at the moment. Compaq LTE 5150 Compaq Armada 1592DMT I know I have a more "modern" Armada somewhere. I did used to have an Elite LTE 440/CX (my notebook from college) but it went underwater. I am not 100% certain, but the HDD from the LTE 440 might be in the LTE 5150. Alas that 440 went into the trash. I also believe a Toshiba Tecra was lost to the same fate. The only one I had kept that went underwater was a GRiD 1520. I've been meaning to do a proper PC part inventory and I hope to find those other systems then.

Need to know what the STOP code is, not speculation about what it is. You should still be able to disable the automatic restart on system failure, even on an install, using F8 menu. This will make it so the error remains on the screen until you manually shutdown or reboot the system.

@Roffen took the text from your (edited) duplicate topic and put into your post on this topic. Deleted the duplicate topic.

I was at a gas station on Saturday and saw that the ATM screen was showing that Windows XP was shutting down.

I still have some feeling that the ability to get music from Youtube isn't as "legal" as these websites indicate.

Welcome to the MSFN!

Yes I had moved the INFs to different folders because it specifically says to use one vs the other depending on the controller. So I moved the H to a different folder so Windows could only pick the INF I wanted. So since this is a "VIA SATA RAID" controller, I didn't want Windows to try to use the uata_xph.inf so I took it out of the folder. direct link: http://i.imgur.com/IQoS5Wkl.jpg FWIW, I did also try to use the xph driver on there, but it added about 6 flagged devices and all of them had the "not enough free resources" message in device properties.

Ok for this one, I followed the instruction to update the VIA SATA RAID controller device in Device manager and browsed to the folder that only has uataxp.inf in it. It did not change the VIA device but instead put a flagged device into Other devices. I then installed the driver for that, and now under System there is a UATA Virtual Communication Device. That driver is in the root of the Release folder of the driver download. The instructions do not mention having to install this device. This particular computer does have the IDE controller also, but the only thing connected to it is a DVD drive. Now having rebooted with this UATA driver installed, it doesn't seem to make any difference. It still shows the inaccessible drive (now E) in My Computer, and the same "healthy" extent sized volume in Disk Management.

I am now to another board now. I had also tired to use an ECS board but I couldn't activate XP. So now I am on an MSI PM8PM-V. It has the same issue in IDE mode with the Microsoft driver, the VIA IDE driver and the VIA RAID driver, as downloaded from MSI's website. For RAID, I have it just in JBOD, but the VIA Tool program opens and shows this information about the disk: I will try that UNIATA thing out. Regarding the XP OS, I can easily reimage it without an issue.

Same result with Intel D2700MUD.

Ok there are some other old systems here currently I can test XP on.

Shutdown and unplugged the XP disk. Was able to boot into the Win7 and the partitions are all the same as before. Back in XP, Changing to the Microsoft driver instead of Intel for the PCI IDE controller doesn't change how the disk is seen. There is no newer storage driver for this board, I installed the latest chipset and it says everything was up to date. This board is a SFF board, it doesn't support RAID, so there is no IRST for it. I can try to install an old version to see if it matters. It does seem right now that this XP install doesn't see the disk properly because of drivers. PS: for reference. This PC has 2 disks in it. A 160GB with XP on it, and the 3TB with Win7 32bit on it. The 3TB was not used as a secondary disk in a different Win7 system. Win7 32bit is installed on to the 1.8GB partition. Still want me to try that TinyHexer from within XP? For older OSes like 2000 or NT4, I do not think I have any hardware that support that OS and also have SATA ports.

You can't rebuild that array now because you have changed the data on one of the disks. Usually in the case of a failed mirror, I would ghost (sector copy) one of the drives to a blank disk of the same size. Then erase both of the original HDDs, and recreate the mirror. Then ghost the backup drive to the raid array. But you say "the recovery utility" which makes me thing you didn't do a repair of the existing installation. Usually the case for IRST is that you can't create the mirror after the fact, say using 1 blank disk, because that is a feature not in "cheap" desktop boards, but more a feature in more expensive controllers. Some do apparently have the ability to do it, but typically the IRST will erase your FAT when it makes the mirror. You could use the outlined step from last paragraph to get your OS onto the RAID, but you would need the storage driver in your OS. You can experiment on getting that to work by changing the SATA mode in the BIOS to RAID and then boot your single disk. If it can boot, then the image should work on an actual array. I can't say about your Office key. A pre-install Office doesn't have a product key only in the software. The only reason it would be there is if you put it there. It should be on a COA on the machine, or on your original disk packaging that came with the computer.

I have Win 98FE with 768MB RAM and a 256MB video card. The OS is modified but I do not believe it has a RAM patch installed.

Last bits from Win7 testing. How Explorer sees the partition: Diskpart info: Chkdsk results: Fragmenting worked, Windows defrag analyze and defragmenter worked without errors. Also no errors, warning or info relating to the disk in Event Viewer at all. Will work on putting XP on this (or something) and see how that likes the disk. Windows XP Pro SP3 x86 on same hardware. D410PT. BTW SATA mode in BIOS is set to IDE, as it was for the Win7 testing. There is definately a problem here, so I'll presume I get to run some other tests. XP detects the disk alright, but the volume it shows is 764GB, which is not a size of either partition on the disk, nor the unallocated: It does not show a file system in Disk Management. If you try to open it from Explorer, it says it is not formatted. EDIT: The Size of D: it sees being 746.52GB "partition" is a partition that doesn't exist. BUT this size is the same size you can see as unallocated in a previous screenshot. This is the amount of space that would be unallocated past the 2.2TB boundary. Note that this PC does not see the 1.8TB partition at all.

I was wondering if behaviours would be different if there was more than 2.2TB data total on the disk, with the partitions/volumes laid out like it is. That is why I made the comment about adding more to C: Would it be enough to just put this disk as a secondary on an XP system, or do you have the same requirement that the OS be booted from it?

I have copied some files and then did a compare to the same on C: and it is the same. There is one difference, a recycler is on the D: drive. If I should put more files on either, LMK. I was using a 167GB set. I am running Chkdsk now.

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.