View Single Post
  #5  
Old February 13th 14, 07:02 AM posted to alt.sys.pc-clone.dell,alt.windows7.general
W[_2_]
external usenet poster
 
Posts: 94
Default UEFI Support in Windows 7?

"Dominique" wrote in message
...
"W" écrivait
:

Does Windows 7 support the need UEFI replacement for BIOS? If yes,

does
this require 64-bit Windows 7? Does it require the system partition

and
boot partition to both be on a GPT disk?

I have a Windows 7 Ultimate 64-bit boot partition working on an old Dell
computer. That computer's BIOS says nothing about UEFI. When I try to
copy over the image of the system partition and boot partition to a a

Dell
T7600 system - which DOES offer UEFI boot devices as an option - and try

to
boot in legacy mode, I get a message that I am trying to boot a UEFI

device
in legacy mode. Unfortunately, that device does NOT show up in the

list
of
boot devices. When I select the device 0 on the boot controller, I get

a
message that the partition cannot be booted (without any details).

If I go into the Dell T7600 setup and configure it to use UEFI, that is

more
confusion. If I try to add a UEFI device, it tells me "No file

system".
If I simply enable UEFI without adding a boot device, it finds nothing

on
startup.

So at the end of the day, I have an exact image copy of a bootable

WIndows 7
64-bit OS, and I cannot get it to boot in either legacy mode or in UEFI
mode. Since I have no experience with UEFI, I am just lost here.

P.S., I was copying over the Windows disk image just to bootstrap

install
process, and I was going to relicense the OS once it booted.


Since those are Dell computers which usually have preinstalled

Windows(OEM)
tied to BIOS, I would be very surprised if the original system image

worked
on the new Dell unless they were identical which is isn't the case.


I'm asking a much more general question: how does Windows 7 see a boot
device, and how do you transfer a disk image from one computer to another so
that the new computer will at least *TRY* to boot from the system.

I agree the device drivers probably won't match up. You probably would need
to insert some new device drivers during the startup process to just avoid a
blue screen. That's not the problem I'm trying to solve now.

And in my current situation I am trying to use a retail license - not OEM -
on both source and target systems. People use disk images to install a
base layer of OS and applications all the time. It can be done legally.

--
W


Ads