Hello all - new to 7 forums. I might have this post in the wrong place
With a default install of Win7, it creates a non-lettered 200Meg "system" partition with about 30 Meg of data.
I have been digging around for an explanation as to its purpose but found no clear explanation. Some say it's for bit locker, but then say that it would need to be at least 1 GIg. Some suggest that it's a way to guarantee an amount of free space for updates and backups (VSS needs a place to place snapshots). Some say it's the actual boot partition. Win7 starts the bootstrap here then moves the C: drive to load the rest of the OS.
If anybody has a clear explanation as to what it's for, I'd like to know.
Thanks
NickDanger
With a default install of Win7, it creates a non-lettered 200Meg "system" partition with about 30 Meg of data.
I have been digging around for an explanation as to its purpose but found no clear explanation. Some say it's for bit locker, but then say that it would need to be at least 1 GIg. Some suggest that it's a way to guarantee an amount of free space for updates and backups (VSS needs a place to place snapshots). Some say it's the actual boot partition. Win7 starts the bootstrap here then moves the C: drive to load the rest of the OS.
If anybody has a clear explanation as to what it's for, I'd like to know.
Thanks
NickDanger
It's the boot partition.
Hi Nick, and welcome to the Seven forums 
As smarty said it's the Boot partition but it's only created if you install to a completely fresh HDD if existing partitions are present then the install follows the form of earlier OS versions, and creates the boot file on an existing partition
As smarty said it's the Boot partition but it's only created if you install to a completely fresh HDD if existing partitions are present then the install follows the form of earlier OS versions, and creates the boot file on an existing partition
Sorry, my post seemed kind of abrupt. It first appeared in build 6801. Odd that it wasn't assigned a drive letter, as 6801 automatically assigned it as D:\
It looks like later builds might be hiding it
It looks like later builds might be hiding it
Yes, it is normally hidden with no drive letter now. It was that way starting with 6936 I do believe.
If you look in Windows Disk Management you should see it listed as the System partition - this is MS speak for what everyone else calls the boot partition.
I believe it's a safety feature to keep it separate from the partitions your operating systems are on - what MS calls boot partitions.
Think the idea is if you hose any of your o/s partitions, you should still be able to boot up any other Windows o/s as the System partition is undamaged. You should also be able to make an image of it to restore in case of disaster.
Don't recommend trying a registry defrag if you have a separate System partition - you may get BCD issues.
Hope it helps
SIW2
I believe it's a safety feature to keep it separate from the partitions your operating systems are on - what MS calls boot partitions.
Think the idea is if you hose any of your o/s partitions, you should still be able to boot up any other Windows o/s as the System partition is undamaged. You should also be able to make an image of it to restore in case of disaster.
Don't recommend trying a registry defrag if you have a separate System partition - you may get BCD issues.
Hope it helps
SIW2
�� Quote: Originally Posted by SIW2 
If you look in Windows Disk Management you should see it listed as the System partition - this is MS speak for what everyone else calls the boot partition.
I believe it's a safety feature to keep it separate from the partitions your operating systems are on - what MS calls boot partitions.
Think the idea is if you hose any of your o/s partitions, you should still be able to boot up any other Windows o/s as the System partition is undamaged. You should also be able to make an image of it to restore in case of disaster.
Don't recommend trying a registry defrag if you have a separate System partition - you may get BCD issues.
Hope it helps
SIW2
I believe it's a safety feature to keep it separate from the partitions your operating systems are on - what MS calls boot partitions.
Think the idea is if you hose any of your o/s partitions, you should still be able to boot up any other Windows o/s as the System partition is undamaged. You should also be able to make an image of it to restore in case of disaster.
Don't recommend trying a registry defrag if you have a separate System partition - you may get BCD issues.
Hope it helps
SIW2
I'll bet this will throw a lot of people for a loop.
Thanks!
Later
Ted Thanks for the heads up SIW2,
As a side note it's good to see M$ thinking of the many users that, for whatever reason, decide to multi-boot operating systems,
A separate "boot" or "system" partition makes so much sense to cover the "OH dear!" situations that all Multi-boot scenarios sometimes cause.
I know it's been an option in Grub for a while now
Hopefully this system will be included in the RTM and later builds of Windows 7 and that they document it properly and perhaps even allow you to set-up this way when an existing partition structure already exists.
I do have a suspicion that this may well stop after the beta builds as M$ will assume that Multi-Boot is not a requirement with anything other than a Beta OS.
As for the use of registry defraggers or cleaners I personally would not advise they are ever used on a Beta operating system. This type of program, tend to be a bit too enthusiastic with what they consider dead links - often deciding that if it is not "normal" then it's not required. with a Beta OS containing many entries that were not "normal" when the Registry program was written it is , in my opinion, asking for trouble
As a side note it's good to see M$ thinking of the many users that, for whatever reason, decide to multi-boot operating systems,
A separate "boot" or "system" partition makes so much sense to cover the "OH dear!" situations that all Multi-boot scenarios sometimes cause.
I know it's been an option in Grub for a while now
Hopefully this system will be included in the RTM and later builds of Windows 7 and that they document it properly and perhaps even allow you to set-up this way when an existing partition structure already exists.
I do have a suspicion that this may well stop after the beta builds as M$ will assume that Multi-Boot is not a requirement with anything other than a Beta OS.
As for the use of registry defraggers or cleaners I personally would not advise they are ever used on a Beta operating system. This type of program, tend to be a bit too enthusiastic with what they consider dead links - often deciding that if it is not "normal" then it's not required. with a Beta OS containing many entries that were not "normal" when the Registry program was written it is , in my opinion, asking for trouble
There will surely be folks who want to know if they can delete that partition to recover the space. Probably some that will just delete the space and then....
Gary
Gary
Yeah Gary, I can hear them now; but it's taking up a whole 200MB of space ... 
Later Ted
Later
Ted Something along the lines of <thread title> "Help! I just deleted a small and useless partition to reclaim space and now my Windows won't start!" ? 
Hi Smarty,
Well they couldn't use " I think I've broken Something " you've got the copyright on that one
Well they couldn't use " I think I've broken Something " you've got the copyright on that one
I appreciate all the input.
I lettered the partition and was able to see the BCD, memtest, bootmgr, etc... It's definitely the boot...er
....system...well...whatever it's called it is has the files that Windows needs to get itself up and going.
I do tech support for small businesses and if it it's not lettered most users won't ever even know it's there. It's the "power" users that will decide that it's not needed and try to mess with it. Fortunately, the only way to delete the partition is to remove the drive and do it from another system or boot to knoppix or erd, and kill it. Still, there is nothing to prevent someone from just deleting all the files in it.
I think this fits in with MS move towards componentization. It also might be a sign of MS moving even further towards virtualization. It seems conceivable that Hyper-V could be dropped into that partition and everything runs as a VM � albeit unknown to most users. Also, moving the bootstrap out of the core OS is required if you are going to boot to a VHD, which is one of the new Win7 features. It all makes sense now.
I lettered the partition and was able to see the BCD, memtest, bootmgr, etc... It's definitely the boot...er
....system...well...whatever it's called it is has the files that Windows needs to get itself up and going.I do tech support for small businesses and if it it's not lettered most users won't ever even know it's there. It's the "power" users that will decide that it's not needed and try to mess with it. Fortunately, the only way to delete the partition is to remove the drive and do it from another system or boot to knoppix or erd, and kill it. Still, there is nothing to prevent someone from just deleting all the files in it.
I think this fits in with MS move towards componentization. It also might be a sign of MS moving even further towards virtualization. It seems conceivable that Hyper-V could be dropped into that partition and everything runs as a VM � albeit unknown to most users. Also, moving the bootstrap out of the core OS is required if you are going to boot to a VHD, which is one of the new Win7 features. It all makes sense now.
�� Quote: Originally Posted by Barman58 Hi Smarty,
Well they couldn't use " I think I've broken Something " you've got the copyright on that one
Well they couldn't use " I think I've broken Something " you've got the copyright on that one
lol. I'll be looking for royalties....
�� Quote: Originally Posted by NickDanger It's the "power" users that will decide that it's not needed and try to mess with it.
�� Quote: Originally Posted by garysgold There will surely be folks who want to know if they can delete that partition to recover the space. Probably some that will just delete the space and then....
Gary
Gary
I don't think it will allow you to do that - at least not if you are using Disk Management.
Anybody got one of those little System partitions and would like to try deleting it to see if it lets you? (Don't try this unless you're an advanced user)
Hi NickDanger:
Quote:
Still, there is nothing to prevent someone from just deleting all the files in it.
SIW2
Yes and now we'll get to explain 2 partitions instead of one. If they can't delete it, that's just gonna make 'em mad and they'll want to know how to get rid of it. But then that is *one* of the reasons for hanging around here. To try to prevent tragedies when we can and to help people recover from tragedies when it's tooooo late.
Gary
Gary
If they are stupid enough to think that 200 MB is going ot help their systemin anyway, good luck to them trying to delete it.
Even on a small 40 GB HD, 200 MB amounts to less than 1% of space....
Even on a small 40 GB HD, 200 MB amounts to less than 1% of space....
For many, it's not really about *how much* space it is, they tried to delete it and couldn't. They tried to format it and couldn't. That will just piss some off. "What do you mean I can't delete it, it's my &^$$#%# computer. Some, like myself, would say 'OK what am I not understanding here? I have one on my dell that I can't assign a driver letter to. 55MB. The space is nothing, but until I found out what is in there-the whats, whys, and wherefores- I was not satisfied.
Gary
Gary
Again, if they are not savvy enough to understand that the 200 MB space might be there for a reason, then they really have no business poking around the computer's innards.
I cannot count the number of times someone with less then techie skills has gone in and done something just as you are hypothesizing - that is what gets users into trouble in the first place,. Yes, it may be *your* computer, but give the developers of the OS *some* credit - that is there for a reason, why try to mess with it? Give your OEM some credit for setting up the system as they do - that extra partition at the end is there for a *reason* why try to mess with it?
In the grand scheme of things it would be a lot better if tools like Disk Management used pretty accurate representations, so that a 200 MB sized partition does not appear to be 1/2 the size of a 400 GB partition. Then again, there are always going to be those people who have only a little knowledge, but think it is their right to do anything they want to their systems.
I cannot count the number of times someone with less then techie skills has gone in and done something just as you are hypothesizing - that is what gets users into trouble in the first place,. Yes, it may be *your* computer, but give the developers of the OS *some* credit - that is there for a reason, why try to mess with it? Give your OEM some credit for setting up the system as they do - that extra partition at the end is there for a *reason* why try to mess with it?
In the grand scheme of things it would be a lot better if tools like Disk Management used pretty accurate representations, so that a 200 MB sized partition does not appear to be 1/2 the size of a 400 GB partition. Then again, there are always going to be those people who have only a little knowledge, but think it is their right to do anything they want to their systems.
I love the little dell partition!! I boot to it all the time on systems for hardware troubleshooting. My biggest complaint is that they don't provide an easy way to create the partition when the drive dies and you have to reload the OS.
As for the new system partition, if someone has the knowledge to access it and mess with it but lacks the common sense to find out what it's for before they mess with it, then they disserve whatever trouble they get. The best way to learn is to break something.
As for the new system partition, if someone has the knowledge to access it and mess with it but lacks the common sense to find out what it's for before they mess with it, then they disserve whatever trouble they get. The best way to learn is to break something.
�� Quote: Originally Posted by NickDanger The best way to learn is to break something.
...Sometime I learn it more than once.Later
ted �� Quote: Originally Posted by Bare Foot Kid That's the way I learn just about everything; the hard way!......Sometime I learn it more than once.
Later ted
...Sometime I learn it more than once.Later
tedIt's the best way! Doing it more than once just strengthens those neural pathways
If your still doing it past the ten mark however....
�� Quote: Originally Posted by NickDanger The best way to learn is to break something
Gary
Hello Smartey, good point!
Though usually by the 7th or 8th time, I just about have it figured out....
Hello Gary!
Later Ted
Though usually by the 7th or 8th time, I just about have it figured out....
Hello Gary!
Later
Ted �� Quote: Originally Posted by Bare Foot Kid Hello Smartey, good point!
Though usually by the 7th or 8th time, I just about have it figured out....
Later Ted
Though usually by the 7th or 8th time, I just about have it figured out....
Later
Ted "just about" is better than "not at all" Hi Ted,
Most of what I 'just about' have figured out changes with the next release. I've gotten used to just about having stuff figured out. Reaching the goal is nice, but the real fun is in the journey, IMHO.
Gary
Most of what I 'just about' have figured out changes with the next release. I've gotten used to just about having stuff figured out. Reaching the goal is nice, but the real fun is in the journey, IMHO.
Gary
�� Quote: Originally Posted by garysgold Most of what I 'just about' have figured out changes with the next release. I've gotten used to just about having stuff figured out. Reaching the goal is nice, but the real fun is in the journey, IMHO.
So true; it's a journey not a destination.
Later
Ted I have some news about this matter, which I came up with yesterday.
I appeared that I needed to see the partition, cause I wanted to write a boot record from BCD into that, so I had to assign a drive letter from DiskManagement. Afterwards, disk management does not allow you to "hide" the drive letter again, but DISKPART does. From within Windows, no boot-from-install-disk required.
So, to unassign the drive letter once you've assigned it, you must enter an elevated CMD and...:
The drive letter is removed and the partition is hidden again.
I appeared that I needed to see the partition, cause I wanted to write a boot record from BCD into that, so I had to assign a drive letter from DiskManagement. Afterwards, disk management does not allow you to "hide" the drive letter again, but DISKPART does. From within Windows, no boot-from-install-disk required.
So, to unassign the drive letter once you've assigned it, you must enter an elevated CMD and...:
Code:
DISKPART {enter} DISKPART> list disk {enter} disk 0 disk 1 etc. DISKPART>select disk 0 (where "0" is your hard disk no. with the 200mb partition on it) {enter} DISKPART> list partition (to find your 200mb partition) {enter} DISKPART> select partition 1 (or your 200mb partition number.) {enter} DISKPART> remove {enter} DISKPART> exit {enter} Thanks limneos,
Good to know.
Gary
Good to know.
Gary
I noticed that everyone is talkin gabout the system partition, well if you already have a partition larger then 200 megs then it will not set a boot partiton
I have 2 parttitons both 125 gigs
disk 0 part 0 is my vista partiton and the windows 7 system
disk 0 part 1 is my windows 7 partition.
after i installed i just went to disk manager and assigned adrive letter and have access to my vista files.
I have 2 parttitons both 125 gigs
disk 0 part 0 is my vista partiton and the windows 7 system
disk 0 part 1 is my windows 7 partition.
after i installed i just went to disk manager and assigned adrive letter and have access to my vista files.
Hello CPappas,
Welcome to the Seven Forums.
Apparently if you have partitioned the hard drive then the 200 meg partition is not created. Also if you have another OS installed, it will update the MBR that has already been created as there cannot be 2 of them and it must go on the first sector of the first drive to be found at startup. If I understand correctly.
Gary
Welcome to the Seven Forums.
Apparently if you have partitioned the hard drive then the 200 meg partition is not created. Also if you have another OS installed, it will update the MBR that has already been created as there cannot be 2 of them and it must go on the first sector of the first drive to be found at startup. If I understand correctly.
Gary
�� Quote: Originally Posted by garysgold Yes and now we'll get to explain 2 partitions instead of one. If they can't delete it, that's just gonna make 'em mad and they'll want to know how to get rid of it. But then that is *one* of the reasons for hanging around here. To try to prevent tragedies when we can and to help people recover from tragedies when it's tooooo late.
Gary
Gary
I agree completely. Biggest reasons I hang around here (or similar places) is so that I don't cause those tragedies, and so that I may help those that I can... But also to point and laugh when someone goes:
"wtfomg?!! i jus fked ma hdd!!!! won bewt no more.... fkin mcriosfot!"
I can't believe how long it takes to type like that.
�� Quote: Originally Posted by HikerRemastered I can't believe how long it takes to type like that.
I using Dual Windows XP and Vista..Now i want to install Windows 7 beta....
And i m using Intel Core2due...
Will this 3 OS made Any harmful to my Computer Performance
And i m using Intel Core2due...
Will this 3 OS made Any harmful to my Computer Performance
Hello HikerRemastered and zainravian,
Welcome to the Seven Forums. Lots of great info and people here and always room for more. Enjoy.
Gary
Welcome to the Seven Forums. Lots of great info and people here and always room for more. Enjoy.
Gary
Thanks a lot
Thanks mate.
I like it here.
*plops down a chair*
I like it here.
*plops down a chair*
200Meg!! That is over 5% of my hard drive (4Gb SSD). It must be eliminated. What is the advantage of having it as a separate partition instead of boot er directory/file/thingy? Is it mounted read-only? Is it the core of the OS that tends to stay memory resident or get paged back in frequently?
It is a big skip for small disk's head to have to lurch over 200Mb every time it accesses it.
I am thick I need to know about the disk, does it reset the head to off-disk between reads or de-energize the head and leave it lurking in position to resume reading?
It is a big skip for small disk's head to have to lurch over 200Mb every time it accesses it.
I am thick I need to know about the disk, does it reset the head to off-disk between reads or de-energize the head and leave it lurking in position to resume reading?
This is an old thread and the partition has since been reduced to 100mb. It is explained in this thread what the purpose of the partition is.
Hello.
How can I manually create that hidden system partition?
I've got to install Windows 8 on an external disk. It cannot be done automatically. Thus I created a primary partition manually, leaving 100MB of unallocated space.
And then I installed Windows there with the deploying tool imagex.
And it works right but the installation hasn't automatically created the 100MB System reserved partition.
Everything has been installed on to the C: partition instead.
How could I force Windows to install the boot files to that sytsem partition?
I couldn't find (in any partition application) the option to tag that area of the disk as system/boot/reserved partition.
thanks
How can I manually create that hidden system partition?
I've got to install Windows 8 on an external disk. It cannot be done automatically. Thus I created a primary partition manually, leaving 100MB of unallocated space.
And then I installed Windows there with the deploying tool imagex.
And it works right but the installation hasn't automatically created the 100MB System reserved partition.
Everything has been installed on to the C: partition instead.
How could I force Windows to install the boot files to that sytsem partition?
I couldn't find (in any partition application) the option to tag that area of the disk as system/boot/reserved partition.
thanks
�� Quote: Originally Posted by skan Hello.
How can I manually create that hidden system partition?
I've got to install Windows 8 on an external disk. It cannot be done automatically. Thus I created a primary partition manually, leaving 100MB of unallocated space.
And then I installed Windows there with the deploying tool imagex.
And it works right but the installation hasn't automatically created the 100MB System reserved partition.
Everything has been installed on to the C: partition instead.
How could I force Windows to install the boot files to that sytsem partition?
I couldn't find (in any partition application) the option to tag that area of the disk as system/boot/reserved partition.
thanks
How can I manually create that hidden system partition?
I've got to install Windows 8 on an external disk. It cannot be done automatically. Thus I created a primary partition manually, leaving 100MB of unallocated space.
And then I installed Windows there with the deploying tool imagex.
And it works right but the installation hasn't automatically created the 100MB System reserved partition.
Everything has been installed on to the C: partition instead.
How could I force Windows to install the boot files to that sytsem partition?
I couldn't find (in any partition application) the option to tag that area of the disk as system/boot/reserved partition.
thanks
For Legacy BIOS.
Clean Install - Windows 8
or
For UEFI/BIOS firmware.
UEFI (Unified Extensible Firmware Interface) - Install Windows 8 with
�� Quote: Originally Posted by theog Windows 8 will make a 350mb partition when installing to a unpartitioned HDD.
That's why we have to use deployment tools such as imagex.exe, but previously the partition has to be created, and later we have to use BCDboot.
I did all that, but I would also like to have the hidden system partition.
I left unallocated space to let Windows to use it, but it didn't take any automatically.
That's why I'm wondering how can I do it manually.
regards
Why do you want the System Reserved partition which is only needed for Bitlocker?
The normal method is to resize the front of C by 100mb using Partition Wizard CD Resize Partition - Video Help,
Then Mark Partition as Active and run Startup Repair - Run up to 3 Separate Times
However as Win7 is not meant to be installed upon an external HD this may not work without first installing it internally with all other HD's unplugged during operations.
The normal method is to resize the front of C by 100mb using Partition Wizard CD Resize Partition - Video Help,
Then Mark Partition as Active and run Startup Repair - Run up to 3 Separate Times
However as Win7 is not meant to be installed upon an external HD this may not work without first installing it internally with all other HD's unplugged during operations.
�� Quote: Originally Posted by gregrocker Why do you want the System Reserved partition which is only needed for Bitlocker?
The normal method is to resize the front of C by 100mb using Partition Wizard CD Resize Partition - Video Help,
Startup Repair - Run up to 3 Separate Times
However as Win7 is not meant to be installed upon an external HD this may not work without first installing it internally with all other HD's unplugged during operations.
The normal method is to resize the front of C by 100mb using Partition Wizard CD Resize Partition - Video Help,
Startup Repair - Run up to 3 Separate Times
However as Win7 is not meant to be installed upon an external HD this may not work without first installing it internally with all other HD's unplugged during operations.
I already have the partition resized. (and left 300MB unallocated at the beginning)
But the Startup repair won't work there because, as you said, it's an external USB disk.
Anyway I got to install windows on the primary partition with alternative methods (imagex.exe and bcdboot).
What I cannot get it's that it gets installed to the hidden system/boot partition.
I don't know if it has to be unallocated or if has to create a primary or logical partition and later transform or tag it as system partition. ANyway I need to know the name of the command line or program that Windows installation uses to manage that things.
regards
I asked you why you need Win7 on an external HD which throttles it via the USB controller.
You can give a Primary NTFS Active SysReserved partition you created a letter and copy the System boot files onto it.
Then install EasyBCD (click Download - no Name or Email required).
In EasyBCD click "Useful Utilities" then Power Console ( the black box like command window), type:
bootsect /nt60 <whatever the System Reserved drive letter is>
Reboot and see if Sys Reserved will boot Win7. Make sure a Dual Boot has not been configured with your onboard OS, that its own SysRserved or C is still marked System Active. You will want to boot the external HD Win7 using the BIOS Boot Menu key so it is independent and portable.
You can give a Primary NTFS Active SysReserved partition you created a letter and copy the System boot files onto it.
Then install EasyBCD (click Download - no Name or Email required).
In EasyBCD click "Useful Utilities" then Power Console ( the black box like command window), type:
bootsect /nt60 <whatever the System Reserved drive letter is>
Reboot and see if Sys Reserved will boot Win7. Make sure a Dual Boot has not been configured with your onboard OS, that its own SysRserved or C is still marked System Active. You will want to boot the external HD Win7 using the BIOS Boot Menu key so it is independent and portable.
�� Quote: Originally Posted by gregrocker I asked you why you need Win7 on an external HD which throttles it via the USB controller.
You can give a Primary NTFS Active SysReserved partition you created a letter. Then install EasyBCD (click Download - no Name or Email required).
In EasyBCD click "Useful Utilities" then Power Console ( the black box like command window), type:
bootsect /nt60 <whatever the System Reserved drive letter is>
You can give a Primary NTFS Active SysReserved partition you created a letter. Then install EasyBCD (click Download - no Name or Email required).
In EasyBCD click "Useful Utilities" then Power Console ( the black box like command window), type:
bootsect /nt60 <whatever the System Reserved drive letter is>
The question is that I know how to create a primary partition but I don't know how to create a "SysReserved
partition".
At the moment I have a "normal" primary partition and an unallocated space.
What should I do next?
Mybe I don't need to create anything and bootsect is enough?
I have the Easeus program and I can also use diskpart.exe
PS:I used EasyBCD before to deploy the boot menu to the external disk.
regards
Try the steps I gave you.
Those steps normally make the System Reserved bootable once the boot files are copied there, but there are many other parameters that need checking and additional steps which Startup Repair takes when run 3 separate times.
For example, even if it writes the System files and flag to your home-made SysReserved and it boots Win7 on its own, you'll not have WinRe on the F8 menu for that HD since it is only written using Startup Repair. There is however a way to hotlink it. F8 System Recovery options restore commands
Those steps normally make the System Reserved bootable once the boot files are copied there, but there are many other parameters that need checking and additional steps which Startup Repair takes when run 3 separate times.
For example, even if it writes the System files and flag to your home-made SysReserved and it boots Win7 on its own, you'll not have WinRe on the F8 menu for that HD since it is only written using Startup Repair. There is however a way to hotlink it. F8 System Recovery options restore commands
OK, I'll try.
But do I have to create any kind of partition on the unallocated space before using reagentc or visualbcd editor?
But do I have to create any kind of partition on the unallocated space before using reagentc or visualbcd editor?
As stated you need an NTFS Primary partition marked Active, with the Win7 boot files copied into it.
Leave the other steps to hotlink F8 menu until you see if you can get SysReserved functioning on an external with the bootsect command.
Leave the other steps to hotlink F8 menu until you see if you can get SysReserved functioning on an external with the bootsect command.
Are you doing a clean install on your PC, or making a Windows to Go?
Windows 8 To Go - Setup on a USB Flash Drive or USB Disk
�� Quote: Originally Posted by skan
Windows 8 To Go - Setup on a USB Flash Drive or USB Disk
�� Quote: Originally Posted by skan Hi
I got it, though I also needed to use Easybcd to be able to boot from the external disk.
But I have a question:
The way you explain we install Windows to a primary partition.
But we don't get the 100MB boot/recovery partition (that is automatically created when you install windows on a internal blank disk, and it's usually hidden).
How can I get that "recovery" partition created?
I cannot find the option with easeus, diskpart, nor other applications I've tried.
Nor can I get it created whit imagex, bcdboot or after rebooting.
regards
I got it, though I also needed to use Easybcd to be able to boot from the external disk.
But I have a question:
The way you explain we install Windows to a primary partition.
But we don't get the 100MB boot/recovery partition (that is automatically created when you install windows on a internal blank disk, and it's usually hidden).
How can I get that "recovery" partition created?
I cannot find the option with easeus, diskpart, nor other applications I've tried.
Nor can I get it created whit imagex, bcdboot or after rebooting.
regards
�� Quote: Originally Posted by gregrocker As stated you need an NTFS Primary partition marked Active, with the Win7 boot files copied into it.
Leave the other steps to hotlink F8 menu until you see if you can get SysReserved functioning on an external with the bootsect command.
Leave the other steps to hotlink F8 menu until you see if you can get SysReserved functioning on an external with the bootsect command.
What I want to know is what I have to do with the unallocated area.
Do I have to create another primary partition there?
Please post back a screenshot of Disk Management - Post a Screen Capture Image - Windows 7 Forums
I thought you were trying to construct a System Reserved partition on the HD. Is this not the case? I was giving you steps to construct a SysReserved partition, obviously.
I thought you were trying to construct a System Reserved partition on the HD. Is this not the case? I was giving you steps to construct a SysReserved partition, obviously.
In EasyBCD forum I got the solution.
I first have to create a partition on the unallocated space too (besides the primary partition), assign a letter to it and use it to install the boot files.
And later I can remove the letter and hide it.
I'm trying but I don't like the fact that I "loose" a primary partition, because I also want to install other operating systems.
I first have to create a partition on the unallocated space too (besides the primary partition), assign a letter to it and use it to install the boot files.
And later I can remove the letter and hide it.
I'm trying but I don't like the fact that I "loose" a primary partition, because I also want to install other operating systems.
I gave you the steps to create a System Reserved partition. They couldn't have been more clear.
Why did you keep asking back how to do this, and go to another forums when I was giving you the steps?
�� Quote: Originally Posted by gregrocker
Why did you keep asking back how to do this, and go to another forums when I was giving you the steps?
�� Quote: Originally Posted by gregrocker You can give the Primary NTFS Active SysReserved partition you create a letter and copy the System boot files onto it.
Then install EasyBCD (click Download - no Name or Email required).
In EasyBCD click "Useful Utilities" then Power Console ( the black box like command window), type:
bootsect /nt60 <whatever the System Reserved drive letter is>
Reboot and see if Sys Reserved will boot Win7. Make sure a Dual Boot has not been configured with your onboard OS, that its own SysRserved or C is still marked System Active. You will want to boot the external HD Win7 using the BIOS Boot Menu key so it is independent and portable.
Then install EasyBCD (click Download - no Name or Email required).
In EasyBCD click "Useful Utilities" then Power Console ( the black box like command window), type:
bootsect /nt60 <whatever the System Reserved drive letter is>
Reboot and see if Sys Reserved will boot Win7. Make sure a Dual Boot has not been configured with your onboard OS, that its own SysRserved or C is still marked System Active. You will want to boot the external HD Win7 using the BIOS Boot Menu key so it is independent and portable.
�� Quote: Originally Posted by gregrocker I gave you the steps to create a System Reserved partition. They couldn't have been more clear.
Why did you keep asking back how to do this, and go to another forums when I was giving you the steps?
Why did you keep asking back how to do this, and go to another forums when I was giving you the steps?
I told you that I had a primary partition and also unallocated space and I wanted to install the boot files not to the main primary partition but to that unallocated space instead.
Several times I told you to create an NTFS Primary Partition, mark it Active, copy the Win7 boot files into it from C, then run the bootsect command I gave you to make that partition bootable and transfer the System flag. If you had questions you only needed to ask.
You kept referring to unallocated space on the HD but didnt' make clear it was the intended System Reserved partition. I thought you could read the steps to see clearly what was involved with creating one.
You kept referring to unallocated space on the HD but didnt' make clear it was the intended System Reserved partition. I thought you could read the steps to see clearly what was involved with creating one.
Thanks for your help.
skan, you can`t apply anything to unallocated space. You are making a mountain out of a molehill. You were also asked to start your own threads instead of reviving old ones. You will get more help that way.
Không có nhận xét nào:
Đăng nhận xét