Tripredacus

Boot into your WinPE, and get to a CMD. Then try to run image_it.exe manually. I wouldn't be surprised if you either have an architecture mismatch or are missing a dependency.

The Autounattend.xml can't do what you want. You'll need to use a programming or scripting language... or maybe even batch. You'll have to change the winpeshl.ini on the DVD to run your app/script instead of setup.exe. So you will need to determine what to be looking for... probably searching for a Windows folder, but remember that WinPE might not see the OS volume as C: every time.

AEN007, submix8c's question was perfectly valid. So everyone needs to settle down and get back to the problem or else this thread will get locked.

You can find release dates for Windows 8 here: http://www.msfn.org/_/windows/windows-8-has-reached-rtm-milestone-r8937

Your best bet is probably going to be in your thread on AutoItscript. http://www.autoitscript.com/forum/topic/143118-autoit-and-windows-8/ There are some people here who use AutoIT, but the response might be better there. I personally have not encountered any problems in Win8 so far and I get worried every time I read that someone has. I have not tried RTM version yet, but I sincerely hope my scripts still work in that version!

It isn't deleted, you just can't see it. As for why, I can't answer that. I rarely even go into that section to begin with ... Anyways, I'll check into it.

Ah there is certainly a difference! A quick glance it appears that the "Physical Drive (MBR)" first sector is the same between the two, but the Logical Disk (Bootsector) is vastly different. I do have a 32bit Make_PE3 I was able to run HDHacker on just fine. Hopefully I didn't capture the USB key's bootsector like I did that other time. Rar file in Skydrive Here is a question I'm not sure about. The testing drive is just that, a testing drive. Previously to me trying to put DOS on it, it had some newer version of Windows on it, 7 or 8... in case that means that something could have been leftover during the imaging process.

The donation tracker does not show all donations either, only ones done through the system. If you made a donation directly, it won't show up in the list.

It was my idea that the original image was in higher resolution than my current avatar, meaning that the original Ravage from that picture would be "larger" and better to use to make a larger image. I agree, I've noticed over the years that the Xenotron font doesn't work well at a small size. For most of my uses I have it fairly large... I don't know exactly what size I use since I haven't made any new images for at least 7 years now. I like how this one looks (and the other one) ... I'll have to think of how to use it since I have to do some formatting changes soon. I'm thinking of something to replace an existing animation that fits nicely next to the w3C CSS badge... unless I rearrange how that is used. Either way, I may consider using the sparkly T as a favicon, since I don't have one of those. This is the old one I made in Photoshop 5, over 10 years ago now! Wow that seems like a long time.

I'm not sure you can boot a FAT32 volume in UEFI mode.

There is a version number in the registry, in this location: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\

I'm fairly certain I have WLE installed someplace but I don't think I use it for anything. As far as messengers go, I actually use Astra for Live IM.

I think I was more having a malfunctioning brain instead. So I withdraw my wish to get a volume larger than 32GB, especially since the client doesn't use nearly even that amount of HDD space.

I'm working on a project to image a DOS hard disk using Imagex in WinPE 3.0 x64. Here is some preliminary steps and testing results. While I have already done a bit of work on this project already, I am "starting over" but using what I have learned already. One problem I've encountered was that I am not quite able to replicate the exact disk properties using Diskpart, so the first thing to do is get some data about the original HDD with the DOS image on it. The original HDD is a 500GB Seagate Barracuda SATA. My testing drive is a 60GB Toshiba HDD2D35. I am using a different sized drive for testing on purpose, since I do not want to lock the deployment method down to a particular hard disk or volume size. Since I am using a 64bit WinPE, there are some inherent limitations to what kinds of programs I can run, since there is no WoW in WinPE. Fortunately, Systemintegrasjon has available a 64bit binary of MbrFix.exe: http://www.sysint.no/nedlasting/mbrfix.htm I found that it is important to get this information first, so I can compare the after-effects to maybe help determine how to properly image with Imagex. First up is what Diskpart can tell us about the original drive. DISKPART> detail disk Disk ID: F0F97B27 Type : SATA Status : Online Path : 0 Target : 0 LUN ID : 0 Location Path : PCIROOT(0)#PCI(1F02)#ATA(C00T00L00) Current Read-only State : No Read-only : No Boot Disk : No Pagefile Disk : No Hibernation File Disk : No Crashdump Disk : No Clustered Disk : No Volume ### Ltr Label Fs Type Size Status Info ---------- --- ----------- ----- ---------- ------- --------- -------- Volume 0 C FAT32 Partition 465 GB Healthy DISKPART> detail part Partition 1 Type : 0C Hidden: No Active: Yes Offset in Bytes: 32256 Volume ### Ltr Label Fs Type Size Status Info ---------- --- ----------- ----- ---------- ------- --------- -------- * Volume 0 C FAT32 Partition 465 GB Healthy DISKPART> detail vol Disk ### Status Size Free Dyn Gpt -------- ------------- ------- ------- --- --- * Disk 0 Online 465 GB 1024 KB Read-only : No Hidden : No No Default Drive Letter: No Shadow Copy : No Offline : No BitLocker Encrypted : No Installable : Yes Volume Capacity : 465 GB Volume Free Space : 465 GB And also what MBRFix says: D:\>mbrfix64 /drive 0 driveinfo Drive 0 Cylinders = 60801 Tracks (heads) per cylinder = 255 Sectors per track = 63 Bytes per sector = 512 Disk size = 500105249280 (Bytes) = 465 (GB) D:\>mbrfix64 /drive 0 listpartitions # Boot Size (MB) Type 1 Yes 476937 12 WIN95 OSR2 32-bit FAT, LBA-mapped D:\>mbrfix64 /drive 0 /partition 1 getpartitiontype 12 So shut down the client, plug in the testing drive, boot back into WinPE. I made a custom Diskpart script to run to format the drive: sel disk 0 clean create part pri size=31000 sel part 1 active format fs=ntfs label="LocalDisk" quick assign letter=c exit Run Diskpart, apply the image with Imagex. Compare the disk information now. DISKPART> detail disk Disk ID: 3F5598B3 Type : SATA Status : Online Path : 0 Target : 0 LUN ID : 0 Location Path : PCIROOT(0)#PCI(1F02)#ATA(C00T00L00) Current Read-only State : No Read-only : No Boot Disk : No Pagefile Disk : No Hibernation File Disk : No Crashdump Disk : No Clustered Disk : No Volume ### Ltr Label Fs Type Size Status Info ---------- --- ----------- ----- ---------- ------- --------- -------- Volume 0 C LOCALDISK FAT32 Partition 30 GB Healthy DISKPART> detail part Partition 1 Type : 0C Hidden: No Active: Yes Offset in Bytes: 1048576 Volume ### Ltr Label Fs Type Size Status Info ---------- --- ----------- ----- ---------- ------- --------- -------- * Volume 0 C LOCALDISK FAT32 Partition 30 GB Healthy DISKPART> detail vol Disk ### Status Size Free Dyn Gpt -------- ------------- ------- ------- --- --- * Disk 0 Online 55 GB 25 GB Read-only : No Hidden : No No Default Drive Letter: No Shadow Copy : No Offline : No BitLocker Encrypted : No Installable : Yes Volume Capacity : 30 GB Volume Free Space : 30 GB And MBrfix: D:\>mbrfix64 /drive 0 driveinfo Drive 0 Cylinders = 7296 Tracks (heads) per cylinder = 255 Sectors per track = 63 Bytes per sector = 512 Disk size = 60011642880 (Bytes) = 55 (GB) D:\>mbrfix64 /drive 0 listpartitions # Boot Size (MB) Type 1 Yes 31000 12 WIN95 OSR2 32-bit FAT, LBA-mapped D:\>mbrfix64 /drive 0 /partition 1 getpartitiontype 12 And time for a reboot... but it boots to: "Remove disks or other media. Press any key to restart." And to compare, all the volume information matches, except for the obvious difference in the two different hard disks. I shall entertain ideas about how to make this disk bootable...

Nice job. I definately like the 100x100 one, mostly because the Ravage image isn't distorted. It may be an idea to refind where that picture came from instead of artificially inflating its resolution. I'll search around, I'm sure I can find it. Here it is: http://farm4.staticflickr.com/3400/3603383893_3af4760d8b_o.jpg This is the wrap-around cover of Dreamwave's Transformers #1, which (iirc) is a special cover.

WinPE 3.0 Diskpart can only format a FAT32 volume if under 32GB.

Simon would be a good name for Vista... maybe. Windows 8 is definately a Rubix Cube!

All my PEs are x64 but.... it may end up being true that using some other method of imaging would be better off.... since it takes 1 second (no lie, the wim is 708KB) to image, and 2-3 minutes to boot the PE. The 32GB format limitation is also a concern, since the client gets 500GB drives due to cost considerations... EDIT: MBRfix now has a 64bit version: http://www.sysint.no/products/Download/tabid/536/language/nb-NO/Default.aspx

Is there any native 64bit Windows apps that can write MBR code using command line? I have a side-project where I need to deploy a DOS image from a WinPE x64, and I have everything done except all of my MBR tools are x86 applications.

That is normal to see the System Reserved get a drive letter in WinPE when booting on a system with an existing OS.

I'll be nice and fix your title this time.... but next time I might have to go read the forum rules again.

I had an idea you'd see that .sys file. If you haven't determined already, that is a DirectX (dxgmms1.sys) file, which means you now have a direction to look at for your issues: The graphics card. There was a video card testing program I once used (and posted about here) but I can't find it now. So until I can remember that one, let's get back to your question. You say you have this problem, but have revealed little about what you are doing at the time. Then you do mention watching a video online. So here are some ideas and questions. - Update your video drivers (use manufacturer not Windows Update) - What browser are you using? - Does it only do this when the video card is being used? (videos, flash, games, etc)

While I presume that the Metro Store has its own documentation, I don't have that atm, and (to be honest) don't think I care enough about it to find it. But I can say a few things about it. To start, I do know that all apps need to be approved (and digitally signed) before they can show up in the App Store. This means that there must be some (hopefully large) amount of people that tries all these apps before making them available. This doesn't mean that you can't just make an app and toss it in your Win8, you can do this for sure. But back to why I quoted your post. There is a vision about Metro Apps (that ties into the removal of the Start Menu and the phasing out of the desktop experience) that lets Apps run without the (potential) ability to corrupt the operating system. This is yet another layer of "security" to keep users from hurting themselves as discussed many pages ago in this thread. That being said, Metro Apps aren't allowed into those protected OS areas that our advanced thingies are likely to go. Want an app to format a USB key? Too bad. Want an app to read or write an MBR to something? Nope, sorry. Want an app that can read a thread's memory contents? Yeah right. This would make me presume that even an app that could take a screenshot wouldn't actually be able to save it to your hard drive as a JPG, instead off to the cloud it goes? Other things not allowed? enabling DVD playback, access the registry, replaces the Metro store or the Metro interface (or possibly add a Start Menu).... Oh and they can't launch other apps. So to summarize, those 200 advanced type apps do not appear replaceable by a Metro app.

That was the story for me with Google + but the problem was Google then banned me because they didn't allow "aliases" at the time.

I had an idea... and I blew it out of the water halfway through. I don't know if I will be keeping this sig for that long (we'll see, I do like my old one) so I'll post it here for posterity.