If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Rate Thread | Display Modes |
#46
|
|||
|
|||
Converting From 1 TB to 2 TB via Macrium Reflect Re-Image: Partitions?
Mayayana wrote:
"bounder" wrote | | 1) Do a restore and then make a disk image. I'm | not talking about a backup by Macrium or some such. | I'm talking about an actual image of C drive. | | Sounds like you might not be familiar with the fact that Macrium is the | clear favorite around the Windows groups for making disk (volume) | images. When you talk about making an image, most people will reach for | their installed copy of Macrium Reflect Free. | See the new posts from John and Ed. Ed seems to think Macrium is for backup rather than imaging. Not everyone knows the difference or agrees on what it is. I've never used Macrium, so I don't know what it can or can't do. I'm just trying to clarify that any system can be imaged. (And as you said, should be.) That seems to be another issue that confuses things. Originally there was the idea of disk images. Then people started making images with incremental updating, which is not really a case of using disk images. It's just a complicated method of backup. I get the impression that these days most people who think they're making disk images are actually just using a backup program -- like a homemade version of System Restore. Imaging means different things to different people. Let's say I'm a detective at the 5th precinct, and a 500GB drive comes in with "evidence" on it. I grab a copy of dd (disk dump) and I record every sector. To copy the 500GB of sectors off the drive, might take two hours. For my trouble, I record present visible files, as well as recently erased files. The recently erased files might be recovered with additional work. This is why forensic grade copies are made, to elicit evidence found in the "white space" of the drive. dd if=/dev/sda of=/dev/sdb # Disk cloning, forensic quality dd if=/dev/sda of=C:\drug_deal_gone_bad.bin # Record image to a file, forensic The file "C:\drug_deal_gone_bad.bin" would be 500GB in size. ******* Macrium on the other hand, includes cloning. It can be done two ways (or claims to have the capability). clone Disk0 to Disk1, using smart copy # Only occupied clusters copied clone Disk0 to Disk1, dumb copy # Copy every sector # Didn't work as advertised, copy # time was too short. Should take # two hours. If I have 20GB of drug files on the 500GB drive, then Macrium typically copies 20GB of stuff. Any deleted files, their clusters are not recorded at the destination. Macrium offers cloning, a disk to disk operation. You can clone a single partitions or a disk full of partitions. For backup purposes, Macrium records backups in a file. We could call this imaging. Except, in the paid version, multiple image files can be used, with some of the files being differentials or incrementals. A Macrium backup of a 20GB partition on a 500GB drive, would end up as a 20GB .mrimg file. That means whatever is on the other 480GB of "white space" is not a concern. Any deleted files are not recorded. The terms they might use, are "backup" or "clone", and you'll have to apply your own translation as to what you think the operations should be called. backup: copy occupied clusters to .mrimg file clone: copy the occupied clusters on a source partition, to an identical destination partition. By not transferring all clusters, only the "visible" part of the disk is copied. Macrium seems to want to copy 20GB in either case. If I could have got the "dumb copy" working years ago, I might be more optimistic of getting a 500GB file from Macrium (the kind a detective would like). Macrium can also do all operations from its Emergency Boot CD. Generally, to avoid problems, the CD should be made on the machine in question, in order that any drivers needed for the job, will be there. Using the disc from my P5E on my X79, doesn't perhaps guarantee that I can use a file share as a destination for the operation - the network driver might be missing. This was more of a problem on older versions of Macrium, and maybe it's getting solved by using WinPE5 or WinPE10 as bases for building the CD. I can't say I've had operational failures lately, so maybe this situation has improved somewhat. Other functions Macrium has: 1) Boot repair function on the CD, good for cases where a cloned disk won't boot. Use Macrium boot repair first, and if that isn't enough, follow it with Windows boot repair. 2) Macrium can convert a .mrimg to a .vhd, for usage in a virtual machine environment. The .vhd cannot have more than 2.2TB of files inside. Since .vhd files can be mounted by "attaching" them in Windows, you can also use .vhd as a "container that works most places". On WinXP, the Microsoft vhdmount utility, plus an NTFS C: for WinXP, would allow that .vhd to be mounted. Some environments have a 137GB limit on a .vhd, others allow the whole 2.2TB. For quantities of files larger than 2.2TB, you'd need a .vhdx recipe (no recipe available). Sysinternals disk2vhd can create .vhd or .vhdx files, if you actually needed to make a 3TB one. But Macrium at the moment, only supports the "smaller" (.vhd) flavor. HTH, Paul |
Ads |
#47
|
|||
|
|||
Converting From 1 TB to 2 TB via Macrium Reflect Re-Image: Partitions?
Ed Cryer wrote:
When you set up a brand new OEM PC, it takes you through account creation before you can do anything (even install Macrium). Your solution would restore that account. Not a clue what you are talking about. WHAT account is forcibly established when you "set up" a new OEM PC? The pre-built (OEM) PC is already setup before you even get it. I've gotten stuck working on several pre-builts and don't remember ever being forced to create some "account" before the PC is usable nor after starting to use it. The OEM uses a sysprep image (by family line and model within family) and ply a sticker on the case whose product key won't match the volume license for the sysprep image they put on that computer and why you should use Magic Jellybean or similar to record the product key for the actual sysprep image on the HDD. We're in the Windows 7 newsgroup. Maybe you were thinking of Windows 10 that has you create a Microsoft account; however, that is optional - you don't have to create an MS account to complete the install but that assumes YOU are doing the install and it isn't a pre-built PC. Even if a pre-built, the OEM obviously cannot predefine an MS account for you. They're reusing the same image to prep all the same model they're selling to every customer, so they cannot create an account. Enlighten us what account you speak of. |
#48
|
|||
|
|||
Converting From 1 TB to 2 TB via Macrium Reflect Re-Image: Partitions?
Mayayana wrote:
"bounder" wrote | 1) Do a restore and then make a disk image. I'm | not talking about a backup by Macrium or some such. | I'm talking about an actual image of C drive. | | Sounds like you might not be familiar with the fact that Macrium is the | clear favorite around the Windows groups for making disk (volume) | images. When you talk about making an image, most people will reach for | their installed copy of Macrium Reflect Free. See the new posts from John and Ed. Ed seems to think Macrium is for backup rather than imaging. Not everyone knows the difference or agrees on what it is. I've never used Macrium, so I don't know what it can or can't do. I'm just trying to clarify that any system can be imaged. (And as you said, should be.) Imaging *is* backup. If it's not for backup, then why are you making an image in the first place? (let's not quibble about 'backup' versus 'archiving'). Imaging is a *type* of backup. I.e. 'image backup' versus 'file backup', for example Macrium Reflect (FREE) versus for example (Windows Vista/7) Backup and Restore. That seems to be another issue that confuses things. Originally there was the idea of disk images. Then people started making images with incremental updating, which is not really a case of using disk images. It's just a complicated method of backup. No, differential/incremental image backup is still 'imaging'. You seem to contrast 'imaging' versus 'backup'. (IMO) That's incorrect, because imaging is (a type of) backup. I get the impression that these days most people who think they're making disk images are actually just using a backup program -- like a homemade version of System Restore. Macrium Reflect (FREE) is clearly an imaging program, because it makes images (.mrimg files) of the (in-use or total) *sectors* (not files) in a partition (or partitions). So yes, they're 'just using a backup program', specifically an *image* backup program. So let's turn this issue around and ask: What do *you* consider to be '[disk] imaging'/'a [disk] image'? And why do you consider '[disk] imaging'/'a [disk] image' not to be 'backup' or/and vice versa? |
#49
|
|||
|
|||
Converting From 1 TB to 2 TB via Macrium Reflect Re-Image: Partitions?
Paul wrote:
[...] For backup purposes, Macrium records backups in a file. We could call this imaging. Except, in the paid version, multiple image files can be used, with some of the files being differentials or incrementals. Minor nit: Starting with version 6 - some 2 years ago -, Macrium Reflect FREE can also make Differential (image) backups (but no Incremental ones). FWIW, I make Differential image backups until the size of the Differential image backup is about 50% of the original Full image backup. Then I make another Full image backup. |
#50
|
|||
|
|||
Converting From 1 TB to 2 TB via Macrium Reflect Re-Image:Partitions?
Paul wrote:
Ed Cryer wrote: J. P. Gilliver (John) wrote: In message , Ed Cryer writes: [] When you set up a brand new OEM PC, it takes you through account creation before you can do anything (even install Macrium). Your solution would restore that account. Ed What if you don't install Macrium, but use a Macrium boot CD that you made earlier on another machine: if you image a brand new OEM PC (imaging all "partitions" that are there), and later restore from that image, will the OEM PC appear as at initial setup (e. g. ask you to choose partition sizes or whatever initial setup does)? (The only time I've ever used the _installed_ version of Macrium was to make the CD in the first place [I think, other than just copying a CD you'd made already, you _have_ to run the software to make the CD]; when making images, I always boot from the CD. I haven't even installed Macrium on this PC.) I really don't know if that would work. Switch on your new OEM PC and it goes straight into its Windows setup; takes all your details and preferences, trundles away, gives you control within the account it's created. Your suggestion means that you'd have to switch on your new OEM PC, change boot sequence, reboot with Macrium disc in. I suppose that if that worked, then yes, you could image the pristine disc. But I don't know if the way the OEM has set it up would allow it. Anyway, I have another suggestion. Do full setup; do whatever else you want to do. Load all your stuff. And then, whenever you want, take an image of just the Recovery partition. Ed Keywords: sysprep generalize sealing oobeÂ*Â*Â* (Out Of the Box Experience) It's possible to put an OS back into a factory state, if you're an IT guy, loaded WADK onto your technician machine and worked on the C: image. I think you can load WADK onto the C: of the technician machine, then bring over a laptop drive and put it back in the OOBE state. I've never done any of this stuff, so can't help with details. If I have my factory restore partition, my DVD set I made when the machine was new, my Macrium backup early in the life of the product, I probably no longer care about the issue. As I have "belt and suspenders", and couldn't give a damn about a 12GB partition still being there. My assumption is, I will drop dead, and if someone picks up the laptop, and sees the factory restore, they can prepare the machine for easy disposal. Now, if it was a tablet with eMMC, that would be an entirely different handling case. One of the reasons I don't own a tablet, is I "don't want to learn how to maintain a tablet". Desktops are just too easy. Â*Â* Paul Here's a version for non-IT-guys. 1. Do the full guided setup. 2. Image the whole lot with Macrium. 3. Do a factory-restore with the OEM-provided software. 4. Image that with Macrium, and keep safe. 5. Restore image 2 above. 6. Duplicate image 2 for safety. Ed |
#51
|
|||
|
|||
Converting From 1 TB to 2 TB via Macrium Reflect Re-Image:Partitions?
VanguardLH wrote:
Ed Cryer wrote: When you set up a brand new OEM PC, it takes you through account creation before you can do anything (even install Macrium). Your solution would restore that account. Not a clue what you are talking about. WHAT account is forcibly established when you "set up" a new OEM PC? The pre-built (OEM) PC is already setup before you even get it. I've gotten stuck working on several pre-builts and don't remember ever being forced to create some "account" before the PC is usable nor after starting to use it. The OEM uses a sysprep image (by family line and model within family) and ply a sticker on the case whose product key won't match the volume license for the sysprep image they put on that computer and why you should use Magic Jellybean or similar to record the product key for the actual sysprep image on the HDD. We're in the Windows 7 newsgroup. Maybe you were thinking of Windows 10 that has you create a Microsoft account; however, that is optional - you don't have to create an MS account to complete the install but that assumes YOU are doing the install and it isn't a pre-built PC. Even if a pre-built, the OEM obviously cannot predefine an MS account for you. They're reusing the same image to prep all the same model they're selling to every customer, so they cannot create an account. Enlighten us what account you speak of. You're right about Win10. I use Win7 but I haven't done an OEM setup on ones for decades. Win10, OTOH, many. I must enlighten you about "account". An account is necessary; that's the "a" in UAC. Are you overlooking the fact that that "a" can be a "local" one? Ed |
#52
|
|||
|
|||
Converting From 1 TB to 2 TB via Macrium Reflect Re-Image: Partitions?
"Frank Slootweg" wrote
| So let's turn this issue around and ask: What do *you* consider to be | '[disk] imaging'/'a [disk] image'? And why do you consider '[disk] | imaging'/'a [disk] image' not to be 'backup' or/and vice versa? I thought I explained that. There's always been backup of various kinds. Disk imaging is, of course, one form. I think of disk image backup as making a copy of a partition that can be reinstalled to the same or a different hard disk, as opposed to data backup, and distinct from System Restore. I think of disk image backup as a specific practice of maintaining such images, especially OS partitions, so that Windows doesn't have to be reinstalled from scratch if a hard disk dies or an OS is badly damaged. Images also make it easy for Pro versions to be moved to a new computer. And such images are also used in corporate IT, to put a pre-configured system on new computers. (Norton Ghost started that way, I think.) Over time, the idea of disk image backup became more popular and software began to arrive that was a kind of hybrid, designed for ease of use and usable by people who might not understand the idea of disk partitions, or the idea of OS vs data. But they'd heard about the importance of backup. People would run their backup "disk image" software in Windows, maintaining on-disk image backups that would frequently update. Perhaps the first transitional product was when Drive Image was changed from a bootable, disk imaging utility to a .Net-based backup program. Then there were a lot of people using Acronis. Those people seemed to be using it specifically because they could have real-time image backup, on-disk, without needing to understand how it all worked. To my mind that's closer to a RAID array than disk image backup. It's in the same category as System Restore, with the restore "point" being constantly updated. That ends up being a very different approach from what I'm calling disk image backup. It's a copy of OS+data that's stored on-disk. It is, of course, an image. But the way it's used differs fundamentally from what I described. I was trying to clarify the difference because several people, such as Ed Cryer, seemed to think I was talking about an on-disk, incremental, System Restore-esque backup technique when I suggested making a disk image of a freshly restored OEM system so that the restore partition could be deleted. I'm not sure how many people actually understand what myself and John were detailing: a bootable program that makes a restorable image of a partition that can be stored remotely and restored to any hard disk. With *that* kind of disk image backup, if such an image is made of a newly restored OEM system, there's no need to save OEM restore partitions. The disk image copied to external storage is a more secure substitute. |
#53
|
|||
|
|||
Converting From 1 TB to 2 TB via Macrium Reflect Re-Image: Partitions?
VanguardLH wrote:
Ed Cryer wrote: When you set up a brand new OEM PC, it takes you through account creation before you can do anything (even install Macrium). Your solution would restore that account. Not a clue what you are talking about. WHAT account is forcibly established when you "set up" a new OEM PC? The pre-built (OEM) PC is already setup before you even get it. I've gotten stuck working on several pre-builts and don't remember ever being forced to create some "account" before the PC is usable nor after starting to use it. The installation process asks for a 'Username' and a 'Password'. *That* 'creates' the account. (At least that's the case for XP, Vista and 8.1, so assume 7 is similar.) So my (local) account is 'Frank'. The OEM (HP) didn't know that when it shipped the laptop. So yes, an account is created or at least named, which - in this context - amounts to the same thing. [...] Enlighten us what account you speak of. The one with your name! :-) |
#54
|
|||
|
|||
Converting From 1 TB to 2 TB via Macrium Reflect Re-Image: Partitions?
"Frank Slootweg" wrote
| Not a clue what you are talking about. WHAT account is forcibly | established when you "set up" a new OEM PC? | The installation process asks for a 'Username' and a 'Password'. | *That* 'creates' the account. (At least that's the case for XP, Vista | and 8.1, so assume 7 is similar.) | | So my (local) account is 'Frank'. The OEM (HP) didn't know that when | it shipped the laptop. | I think that's something that most people are not really aware of. There's no requirement to have a password or boot screen. That's mostly a corporate thing. When I set up a system for someone I just name the user Admin, Def, or some such. For the sake of privacy. Since it won't matter to them and they generally won't see it, it's best not to use real names. Current user name can show up in all kinds of places. (Frank should be OK, though. No one will know which Frank you are. But all of this was also a red herring issue. There's no need to boot into the new setup and configure it before making a disk image. What I can't figure out is why so many people want to give away their computer with an official HP logo booting to the desktop. Maybe those are the people who want the computer to log them in as "Xavier T. Winterbottom" so they can feel their computer is personalized, and they assume the next person will want similar "personalization"? Little do they know that it serves no purpose other than to provide more personal data for "telemetry" collection. In fact, it can sometimes be much better not to provide any info at all, since it's not relevant in the first place on a single-user, SOHo computer. I have a brother who once bought a scanner for his Mac that came with a full, free version of Photoshop 4. When he went to buy the update to PS5, Adobe refused. He had entered his company name in setup and Adobe thus claimed that he didn't own the license, even though he'd never actually used the software at work, had registered it at install, and had bought the scanner himself! In the meantime, he'd left the company he'd been working for. Fortunately, they were nice enough to write a letter for Adobe, attesting that they had not bought the scanner or provided the software. So eventually the update went through. I avoid dealing with the likes of Adobe. But since that time I'm all the more careful to avoid entering info during setup. It's none of their business. If forced I'll enter something like name: default company: none I wouldn't put it past Adobe to say I can't have an update because "none, inc" owns my computer. On the other hand, Adobe no longer has updates, anyway. It's the rental way or the highway now with them. |
#55
|
|||
|
|||
Converting From 1 TB to 2 TB via Macrium Reflect Re-Image:Partitions?
J. P. Gilliver (John) wrote:
In message , Ed Cryer writes: J. P. Gilliver (John) wrote: In message , Ed Cryer writes: [] When you set up a brand new OEM PC, it takes you through account creation before you can do anything (even install Macrium). Your solution would restore that account. Ed What if you don't install Macrium, but use a Macrium boot CD that you made earlier on another machine: if you image a brand new OEM PC [] Your suggestion means that you'd have to switch on your new OEM PC, change boot sequence, reboot with Macrium disc in. Ah, you may be right: I was assuming that new machines defaulted to boot-from-CD-if-there's-one-there; I may be well wrong about that. (And yes, you would have to turn it on briefly to use the eject button so you could actually put the CD in, unless you used the paperclip hole.) I suppose that if that worked, then yes, you could image the pristine disc. But I don't know if the way the OEM has set it up would allow it. Me neither. Anyway, I have another suggestion. Do full setup; do whatever else you want to do. Load all your stuff. And then, whenever you want, take an image of just the Recovery partition. That's the more normal situation. I was thinking about people who might want to sell/give away PCs in "as new" condition; I can't see me ever doing that (in much the same way as I run my cars into the ground, rather than selling them). Ed John It would work if the thing POSTed; if it went into the normal pre-boot sequence, gave you the choice of enter BIOS, change boot order, boot from current setting. But (and this is where I can't be 100% certain) I don't think they do; they go straight into boot from C and pick up in the Win setup sequence where the sysprep has left off. If they did POST, then you could change to boot from DVD or USB, and do whatever you wanted. You could treat your new OEM machine as a bare-bones computer; completely format C, load chosen OS, bypass all the crapware removal that we hate so much. You'd have the hardware and a Win10 licence; so you could get the very latest Win10 downloaded elsewhere and set it up with all updates. Ed |
#56
|
|||
|
|||
Converting From 1 TB to 2 TB via Macrium Reflect Re-Image: Partitions?
Mayayana wrote:
"Frank Slootweg" wrote | So let's turn this issue around and ask: What do *you* consider to be | '[disk] imaging'/'a [disk] image'? And why do you consider '[disk] | imaging'/'a [disk] image' not to be 'backup' or/and vice versa? I thought I explained that. There's always been backup of various kinds. Disk imaging is, of course, one form. I think of disk image backup as making a copy of a partition that can be reinstalled to the same or a different hard disk, as opposed to data backup, and distinct from System Restore. If you change 'data backup' to 'file backup' (i.e. also backing up files which do not contain 'data', i.e. programs, etc., etc.), I think everyone in this thread is in full agreement. BTW, please let's leave System Restore out of this discussion, because it's something completely different (and it's broken by design, so it's not backup in any shape or form). I think of disk image backup as a specific practice of maintaining such images, especially OS partitions, so that Windows doesn't have to be reinstalled from scratch if a hard disk dies or an OS is badly damaged. Images also make it easy for Pro versions to be moved to a new computer. And such images are also used in corporate IT, to put a pre-configured system on new computers. (Norton Ghost started that way, I think.) Not only Windows doesn't have to be re-installed, but neither does all other software, all updates, all (re-)configuration, etc.. IOW, the *system* does not have to be re-installed. Re-installing Windows is relatively simple. It's the rest, which is very time consuming and a major nightmare. Over time, the idea of disk image backup became more popular and software began to arrive that was a kind of hybrid, designed for ease of use and usable by people who might not understand the idea of disk partitions, or the idea of OS vs data. But they'd heard about the importance of backup. People would run their backup "disk image" software in Windows, maintaining on-disk image backups that would frequently update. Perhaps the first transitional product was when Drive Image was changed from a bootable, disk imaging utility to a .Net-based backup program. Then there were a lot of people using Acronis. Those people seemed to be using it specifically because they could have real-time image backup, on-disk, without needing to understand how it all worked. Indeed many people in these newsgroups use image backup that way, because - for them - such backup is fast enough, (external) disk storage is cheap enough and such software can often also restore files/folders from the image backup. *I* do not use image backup that way (I use image backup *and* (seperate) file backup), but such use is perfectly OK. FWIW, I think these people are very well aware of the concepts ('disk partitions' and 'OS vs data') involved. To my mind that's closer to a RAID array than disk image backup. It's in the same category as System Restore, with the restore "point" being constantly updated. That ends up being a very different approach from what I'm calling disk image backup. It's a copy of OS+data that's stored on-disk. It is, of course, an image. But the way it's used differs fundamentally from what I described. I was trying to clarify the difference because several people, such as Ed Cryer, seemed to think I was talking about an on-disk, incremental, System Restore-esque backup technique when I suggested making a disk image of a freshly restored OEM system so that the restore partition could be deleted. I'm not sure how many people actually understand what myself and John were detailing: a bootable program that makes a restorable image of a partition that can be stored remotely and restored to any hard disk. With *that* kind of disk image backup, if such an image is made of a newly restored OEM system, there's no need to save OEM restore partitions. The disk image copied to external storage is a more secure substitute. FWIW, AFAICT everybody understood perfectly what you meant. |
#57
|
|||
|
|||
Converting From 1 TB to 2 TB via Macrium Reflect Re-Image: Partitions?
"Ed Cryer" wrote
| It would work if the thing POSTed; if it went into the normal pre-boot | sequence, gave you the choice of enter BIOS, change boot order, boot | from current setting. | But (and this is where I can't be 100% certain) I don't think they do; | they go straight into boot from C and pick up in the Win setup sequence | where the sysprep has left off. That's hard to believe. I have seen awkward designs, where you have to set it to boot from CD and even then it will ask approval before it does. And it can be hard to get into BIOS when you have to press a certain key at exactly the right moment. But I've never heard of such a thing as a computer with no BIOS access at all. Usually there are things in there you might need to adjust on occasion. |
#58
|
|||
|
|||
Converting From 1 TB to 2 TB via Macrium Reflect Re-Image: Partitions?
"Mayayana" on Fri, 22 Jun 2018 10:41:22
-0400 typed in alt.windows7.general the following: "Frank Slootweg" wrote | So let's turn this issue around and ask: What do *you* consider to be | '[disk] imaging'/'a [disk] image'? And why do you consider '[disk] | imaging'/'a [disk] image' not to be 'backup' or/and vice versa? I thought I explained that. There's always been backup of various kinds. Disk imaging is, of course, one form. I think of disk image backup as making a copy of a partition that can be reinstalled to the same or a different hard disk, as opposed to data backup, and distinct from System Restore. As I recall it, "images" are bitwise copies, so that everything (including the "blank" part is copied. Very useful for Discovery in legal cases. Because it is a bitwise copy, it takes a long time to accomplish, and you need to copy it to a larger drive. -- pyotr filipivich Next month's Panel: Graft - Boon or blessing? |
#59
|
|||
|
|||
Converting From 1 TB to 2 TB via Macrium Reflect Re-Image:Partitions?
On 19/06/2018 01:16, (PeteCresswell) wrote:
I want to replace a 1 TB drive that's on it's last legs with a 2-TB drive. I imaged the sick drive with Macrium Reflect, creating a single file. Here's what the drive looked like in Disk Manager: https://photos.app.goo.gl/rEFsF2H9F7mNJXjRA When I just restore the image to the 2 TB file, I get a system that works, but the additional space is unavailable for expansion of the "Data" partition because "HP_RECOVERY" sits in the middle - between existing "Data" and the new unused space. I've tried to fool Mother Nature a number of ways - but with no success. It seems like that HP_RECOVERY is both essential to the day-to-day operation of the system ("Recovery" ????) AND is required to be the third partition because I've tried to force the issue by allocating a beeeeg "Data" and then restoring HP_RECOVERY at the end - but to no avail. Is this a fool's errand? My agenda is to make that extra TB available as part of the "Data" partition so I have almost 1.5 TB available for "Data". Is there no way to move the HP_RECOVERY partition to the end of the drive before trying to expand the Data partition? Usually that's what you have to do. I'm pretty certain I remember doing it fairly easily somehow. If not with the Windows Disk Management perhaps with PartedMagic or something similar. -- Brian Gregory (in England). |
#60
|
|||
|
|||
Converting From 1 TB to 2 TB via Macrium Reflect Re-Image: Partitions?
Ed Cryer wrote:
VanguardLH wrote: Ed Cryer wrote: When you set up a brand new OEM PC, it takes you through account creation before you can do anything (even install Macrium). Your solution would restore that account. Not a clue what you are talking about. WHAT account is forcibly established when you "set up" a new OEM PC? The pre-built (OEM) PC is already setup before you even get it. I've gotten stuck working on several pre-builts and don't remember ever being forced to create some "account" before the PC is usable nor after starting to use it. The OEM uses a sysprep image (by family line and model within family) and ply a sticker on the case whose product key won't match the volume license for the sysprep image they put on that computer and why you should use Magic Jellybean or similar to record the product key for the actual sysprep image on the HDD. We're in the Windows 7 newsgroup. Maybe you were thinking of Windows 10 that has you create a Microsoft account; however, that is optional - you don't have to create an MS account to complete the install but that assumes YOU are doing the install and it isn't a pre-built PC. Even if a pre-built, the OEM obviously cannot predefine an MS account for you. They're reusing the same image to prep all the same model they're selling to every customer, so they cannot create an account. Enlighten us what account you speak of. You're right about Win10. I use Win7 but I haven't done an OEM setup on ones for decades. Win10, OTOH, many. I must enlighten you about "account". An account is necessary; that's the "a" in UAC. Are you overlooking the fact that that "a" can be a "local" one? And now you bring up UAC as though it were referenced before. Oh, a Windows account aka user account. Okay, so why not either boot using the Macrium CD and do an image of the drive (all partitions) before you load or login to Windows to create an account, or you can delete user profiles; however, deleting a profile only removes it from the registry. You still have to delete (better to permanently wipe) the userprofile folder for each account you have logged into. Despite your mention that lots must be changed in the BIOS to boot from the CD drive, if there is one, or from a USB drive, most PCs that I've worked on already have those as the default boot order. Else, most users wouldn't have a clue why they cannot boot from those sources. For a PC to be configured to list the HDD first and then the other sources or no other sources means someone went into the BIOS to change away from the defaults in an attempt to lockdown that PC. How would users even install Windows from a CD if the BIOS didn't boot from the device before trying the HDD? While the CD or USB drive may be bootable before the HDD, I've seen some that timeout. The BIOS/UEFI presents a prompt asking the user to hit some key if they want to boot from those other sources. If the user doesn't hit the key in, say, 5 seconds then the BIOS/UEFI skips those boot sources and move on to the next one in the boot order list. |
Thread Tools | |
Display Modes | Rate This Thread |
|
|