New
#61
I seem to have difficulties 'interpreting' your posts, probably due to their indirectness, lack of punctuation, and superfluous verbiage..
So, (I think that this is what you mean, for sake of discussion) :
Yes, I understand that. The simple answer is that it WILL NOT install to USB or Firewire (IEEE_1394?)
I've posted many pictures of my attempts to install to External USB HDD.
And, warned others that 7 Setup will NOT install to USB or Firewire.
You can mount the iso from almost anywhere that the file exists, however,You can see 7 install by simply mounting the iso stored on an external drive rather then burning it to disk. The Windows installer however will halt itself when attempting a direct install onto any usb drive or device.
Win7 Setup will NOT install to USB or Firewire.
It might be wise, in testing, to have the iso on an "internal" partition, since
Setup/Install doesn't seem to 'like' USB/Firewire.
HDD from enclosure, into mainframe chassis, W7 installed there, HDD back into enclosure...If you pull a drive from the external enclosure to see Windows installed on it while inside the case and then returned to the usb enclosure you run right into the exact same problem of no longer seeing the same hardware configurations as well as boot information leading to problems again.
Then,
The "exact same problem" as what? There was no definition of any other problem, so which "exact same"?
Concerning "hardware configurations" - this could indeed be a factor for Win7, depending upon what was removed (P3 for Ext USB), what was inserted (HDD_1, from enclosure), etc.
I don't know the "testing algorithm" for Win7.
I've seen stuff on XP from Germany and it seemed pretty lax.
Certainly, an added P3 for Ext USB does not bother the XP algorithm for installation or "Activation".
The "boot information" SEEMS to always be gotten from what we usually call the normal ( C:\) drive/partition, prior to the Win7 install.
This is a real 'can-of-worms', and if one really "needs-to-know", one can (with major interpretation difficulties) find lotsa data on this, via the Information_Super-Highway.
The words to search for are:
---------------------------
MBR = Master Boot Record,
Partition table,
Active bit,
Boot sector,
Boot loader,
Boot manager,
BCD (or BCD-store), and much more.
---------------------------
Any competent "virtual environment" (which is nothing more than running an 'executable' .exe file [application software]) must allow for software OS installation - That is, in fact, the only reason for its existence.The virtual environment easily allows for the installation while still only being recommended for evaluation and temporary application
To emulate an "installed" operating system, and carry out the required functions of that particular OS (memy mgnt, disk alloc, time-slices, network, "services", etc).
A program, running another program.
Don't understand and can't interpret...unless you consider how the XP mode works by allowing old programs to run there avoiding compatibility issues. For running Windows as a main form of dual boot like 7 with Vista or Vista with 7? Not so good!
Sorry, too '****-faced' to carry on...
edit: last gasp (til tomorrow)
Win 7 will not INSTALL to USB/Firewire,
However, we can PUT the FILES there, w/o installation.
Then, the problem is to make it work,
i.e. Make it BOOTABLE -- this is the only 'real' problem... (?Piece of Pie...)