zamarac

I've a dual boot system: Windows 7 and XP. I can boot normally in WinXP in AHCI SATA mode and also IDE Emulation Mode. But in Windows 7 I can boot only in AHCI SATA mode, but when IDE Emulation is switched ON in BIOS of my ASUS P5Q mobo, the PC hangs at boot with 0x7B BSOD? It started happening after some Windows Update fixes were installed a while back - don't know exactly, since use IDE Mode only seldom, when connecting old IDE extra drive. Please suggest, how to troubleshoot and fix?

JFX You posted that your prog now use this Diskpart script: create vdisk file="C:\Windows7.vhd" maximum=25600 type=(fixed|expandable) select vdisk file="C:\Windows7.vhd" attach vdisk online disk noerr attributes disk clear readonly noerr create partition primary align=(32|64|128|256|512|1024|2048) online volume noerr attributes volume clear readonly noerr active format quick fs=ntfs label="Win7 VHD" unit=(512|1024|2048|4096|8192|16K|32K|64K) assign letter=X: Could you explain, what benefits gives using ALIGN and NOERR options? Also, how ALIGN and UNIT commands choose block size from the list - should a user type it manually when formatting a drive? If yes, which size would you recommend for which OS? If not, how the size is chosen - based on output of FILESYSTEMS command?

Hi JFX, Thanks for the useful tool. Before I try it, could you clarify a few things: - does the latest version support install of WES7 or Thin Client to HD or VHD? If not - why exactly? - should your program run from a hard drive (for what OSs) or WinPE (for what OSs) to install the OS? - after an unsigned driver is integrated into the OS during install, will the OS still require to boot it only in Test mode (64-bit )? - what BCD commands do you use to enable install to a VHD (suppress error)? Thanks for clarification. Also, I'm trying to run WES7 installed onto VHD on my real machine, inside a VM, and it gets 07b BSOD. What would you suggest to do possibly during install or now to make it run in both environments? Is this issue related to your tool not supporting Embedded?

That's always interesting, when an author offers a method to do something, he believe is better that others, but "forget" to explain in simple words the sequence how his method actually works. Even when repeatedly asked to explain verbally, he refuses, suggesting to look inside his files, read multiple lengthy threads. etc. Is that a lack of intellect, or people skills, or what? Especially keeping in mind, how many people would be glad to follow this method if they only were able to find a simple explanation, how it works, in addition to instruction how to run it. I will definitely not use it, until I understand the first part - how it works. And then write the whole sequence in 5-10 simple sentences for others, who are just passing by because such explanation is missing. Is that YELLING or what?On every forum there are a few guys who believe they are somehow smarter or better then other, having privilege to teach everyone instead of communicate on equal terms. We all are visitors here. Don't waste your time trying to teach me for life. I look only for information, not suggested actions. And the question is the same: at what point and where ImDisk and FiraDisk are installed, since they should be installed before they can work IMHO.

Thanks for the explanation and numerous suggestions. The only thing still missing for me to write a one post Cave Man Synopsis is to get in plain text, at what point and where ImDisk and FiraDisk are installed, since they should be installed before they can work IMHO. Is that so hard to explain? It may be that these drivers are integrated into the ISO during boot process - anything is fine for me, if explained in 1-2 plain sentences. Once we accomplish that part, I promise to copy the whole thread with a pencil.

Still ImDisk and FiraDisk must be installed somewhere to work. Where, and at what point(s) in install process? ImDisk will mount loaded into RAM floppy at 1-st reboot - is that where SATA drivers are usually added? And then FiraDisk will mount Install ISO in text mode, which I guess immediately follows 1-st reboot - sounds about right? So ImDisk and FiraDisk are installed before reboot onto the same HD where XP is being installed (or ImDisk installed on DOS Floppy), so after reboot already almost installed XP mounts the Floppy and Installation ISO on its own? But why use both, if FiraDisk can do it all? See, we are almost there...compiling a Cave Man Synopsis to Installing Windows XP from USB. Giving detail explanation is not equal to suggesting doing something... So, no risk in explaining without suggestions, comments about the poster, and other smart a** staff.

Thanks guys! To work, ImDisk and FiraDisk must be installed in Windows - correct? So, the WinXP Install ISO must be placed onto a USB disk with Windows already installed on it? Sorry, cdob if I didn't understand your 1-st post completely. Thanks for your efforts to make it work! Xmmm... Third party drivers (ImDisk / FiraDisk) are also required to install WinXP from ISO - isn't it? So, what makes Win7 install from ISO so different? Sorry, want to finish this Synopsis with some logic even a cave man can understand. Note, when I ask for information, some of you guys try to give unrelated advice to do something... Does it make any sense?

Thanks for your understanding of my situation. I suspect, many people who read this are in the same bot. So from your code its clear that during setup: 1) Floppy image is read to RAM; 2) WinXP ISO is read to RAM; 3) SETUPLDR.BIN runs from unmodded WinXP ISO. Remains unclear, how the floppy image takes part in the install process, since nothing is called to run from Floppy. I guess, SETUPLDR.BIN will look for that Floppy and take extra code from it, but its kind of weird since SETUPLDR.BIN is not modded and would look for a floppy only if F6 is pressed by a user, usually to install SATA drivers. So the user must hit F6, and in addition to SATA drivers other staff will run from that Floppy automatically or by user's choice? But at what point(s) ImDisk and FiraDisk play their roles, and where each installed? And, this Grub4DOS code above is used only after reboot, or before AND after, or there is no PC reboot in this case? Since you said there is no similar solution for Win 7 ISO install, is there an exact understanding Synopsis what is the show stopper? Thanks again, very helpful, I can learn the whole "very advanced" story fast from this Synopsis.

I guess I need to clarify, no disrespect to cdob. I'm just getting lost in what they were trying to do by reading this thread, and completely vanish if attempting to read more of the same in all other threads. Possibly because its too technical for me and presented without explaining much. I can obvious try this method, but want to get some simple idea first, how it works. The Install ISO is not modified - this is great! Instead they boot F6 Floppy after half-way WinXP installation reboot to mount the Install ISO second time via batch running from that floppy - right? How they boot the F6 Floppy - manually via Grub4DOS Menu? So, FiraDisk eventually substituted ImDisk here completely - right? Because its usable for booting the Install ISO second time? Then the Install ISO must be copied to a USB Stick with WinXP already installed on it - right? Or they add FiraDisk into ISO RAM copy after loading the Install ISO to RAM upon reboot? Is it used at 1-st boot of the ISO? Any thread on this forum about using FiraDisk? You mentioned that this approach doesn't work for installing Win7 from an unmodded factory ISO? Then what approach works? Thanks a lot again, no offense please. Just want brief and simple, but with clear idea how it works at large, no small details. May be they call it Synopsis?

Thanks, now its more clear. Still unclear, why this thread is so lengthy, and what exactly these guys were trying to accomplish, if the only thing required is to substitute Setup.exe in the ISO with its fake copy, and it was already done in another thread? Is that the only thing required? Does it work the same exact way for Win7 ISO install as for XP ISO? You mentioned FiraDisk - is it a better choice compare to ImDisk for this app (to load an ISO to RAM before installing Win from it) - why? How and why using FiraDisk (instead or in addition to ImDisk ?) changes the install process? Instead of modding the original installation ISO, is it possible to setup Grub4DOS menu item that will automatically mount second time and/or mod the ISO in RAM at install time after its mounted by adding the fake Setup.exe to it, or play similar role in loading the ISO to RAM again after reboot, so that a user don't have to mod the original Win ISO?

I'm confused. The threads you mentioned don't even talk about installing Win from ISO, even less explain what exactly happens after reboot during install that prevents it from being finalized. May be a couple of simple sentences will do?

Thanks. Is there a summary in any post anywhere on this forum that briefly explains what prevents WinXP from being installed from unmodified ISO (non necessarily using a USB Stick, but even from an ISO on USB HD with XP already installed, via Grub4DOS)? What happens after reboot that makes it impossible to complete install? And a similar summary for Win7 install from ISO, which I assume has different reasons preventing finishing install after reboot?

This thread seems to explain how to overcome a problem of Win XP not installing from MS ISO. That's interesting, but first I want to know why this problem exists to begin with? Can someone point to a thread that explains what are the exact issues that prevent Win XP and also Win 7 from being installed from an unmodified downloaded from MS site Win Install ISO? What exactly goes wrong, at what point and why? Why don't start from explaining the problem first, research why exactly it occurs, and only then offer a solution? Or at least give a link that explains the beginning.

Its off topic in this thread. But try to read SMART data and generate error code for drive exchange with SeaTools.

I am using FastCopy program to copy large files from a Win98SE laptop to a USB2.0 NTFS-formatted hard drive, mounted in Win98SE (UnSP2.1a) via Paragon NTFS for Win98 driver. FastCopy can only copy from FAT32 to NTFS drive indirectly via OS Buffer, but usually 2-3 times faster than Win Explorer, and with much less drive head movement & overheating. It also allows to Pause / Resume via Stop / Cancel Button. However, if I set a max file size bigger than 2Gb (2048000 Kb) in NTFS OS Buffer Options, Copy operation fails even if actual file is very small. The error logs: Insufficient disk space. Files smaller than 2Gb are copyed without a problem with that settings. I can't copy 4Gb file in Win Explorer either due to overheating and system locking, so can't check if the same problem shows up. Files to FAT32 up to 4Gb are copyed normally in FastCopy, which probably pinpoints to flows in NTFS Driver. How to fix it? Any suggestings for a different fast & low on resources File Copy utility able to copy 4Gb files to NTSF under Win98SE with Pause / Resume?

I've a Win98SE Sony laptop with UnSP2.1a installed. Please help with some persistant problem: - Can't normally disconnect a USB2.0 Cardbus PC Card (Dynex DX-UC202). Win98SE confirms Unplug / Eject from Tray, but the card remains listed in Device Manager. If I try to Remove it from there, system locks. Without properly removing it I can't exchange it for a Network Card. Its not properly recognized due to "can't allocate enough memory". So I have to reboot every time, when exchanging the Cards. How to fix? Update: Problem fixed - installed updated driver, which includes own Unplug Utility.