http://gparted-forum.surf4.info/viewtopic.php?id=2892
Sun, 10 Mar 2013 22:50:28 +0000PunBBhttp://gparted-forum.surf4.info/viewtopic.php?pid=30699#p30699
Hi!Kudo's to original posters for the tips!Here is what worked for me when I had clone a partition with Windows 7 Pro from a 60 GB SSD to a 120 GB SSD:

delete HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices keycopy/resize partitionmark new partition as bootdisconnect original disk from the systemrepair MBR on new disk using Windows install disk

Cheers!

]]>Sun, 10 Mar 2013 22:50:28 +0000http://gparted-forum.surf4.info/viewtopic.php?pid=30699#p30699http://gparted-forum.surf4.info/viewtopic.php?pid=24594#p24594
Sorry, can you clarify your massive instruction-- does one delete that registry key before you clone the drive or disc on the OLD drive, or on the NEW drive before you change any other partitions??? You delete the whole key (named MountedDevices in the left window of the Registry) or the info in the right box? --Is this entire problem a function of XP on NTFS- if you have it on Fat32 copied to Fat 32, is it an issue?? --I've copied the XP C drive onto bigger partition on an external USB new drive Fat32 to Fat32 , with different other partitions from external drives, then changed and moved several partitions with Eassus and GParted. So I might have a problem, but I haven't booted up the new drive yet.

--Can one delete that key on an external USB drive somehow- is there a registry editor that works without Windows, or works on an externally connected drive's registry???

IMPORTANT : READ THIS FIRST IF YOU WANT TO WORK ON WINDOWS XP OR VISTA

Can I work in windows 7 With it?

]]>Sun, 31 Oct 2010 01:50:07 +0000http://gparted-forum.surf4.info/viewtopic.php?pid=24414#p24414http://gparted-forum.surf4.info/viewtopic.php?pid=23961#p23961
Good material thanks.лазерная коррекция зрения]]>Sun, 15 Aug 2010 16:49:24 +0000http://gparted-forum.surf4.info/viewtopic.php?pid=23961#p23961http://gparted-forum.surf4.info/viewtopic.php?pid=22615#p22615
I shrunk my XP NTFS (single) partition and created a new one at the empty space 4 hours ago, which rendered it unbootable. 4 hours later, what do I find out? That it comes back to life by deleting the new partition and filling the empty space with the XP partition again.

Anyone had the same experience?

]]>Fri, 15 Jan 2010 02:24:58 +0000http://gparted-forum.surf4.info/viewtopic.php?pid=22615#p22615http://gparted-forum.surf4.info/viewtopic.php?pid=21872#p21872
I have a couple of suggestions for the resize-windows.txt file, in the section for how to manually resize a Vista partition. When I followed the instructions therein I rendered my Vista installation unable to boot. The problem was that I had used the default setting in fdisk for the units, and the partition was being moved slightly to be on a cylinder boundary, while the filesystem stayed in the same place. (Thankfully I had taken a note of the position of the partition (in sectors) before I resized it, so I could restore the original partition table.) I suggest that the instructions include a step to issue the "u" command to fdisk before anything else to avoid this problem.

I also suggest that the presence of this file is made more clear. I only stumbled upon it by accident, and had been trying to use the GParted graphical utility to do the job. Unless the user looks in "/root" for some reason they won't see it.

the problem is, that fragmentation is a Windows issue. Linux filesystems generally need no defragmentation, so the "level of suffering" isn't high enough to develop a "cross-system" defragmentation tool. A big problem also is, that M$ doesn't publish specified details of its present filesystems. So it's rather difficult to always "stay tuned", and therefore it might be risky to use such a hypothetical Linux tool. On the other hand, Windows API offers (safe!) defragmentation commands for all its filesystems, so why looking elsewhere ? I didn't yet test it, but it's possible, that "jkdefrag" works from a free "Vista Recovery CD", so that even systemfiles (e.g. pagefile.sys) get defragmented, which are always blocked, when Windows is running. BTW, there is also a recommendable Windows commandline tool "pagedefrag.exe", which does the job ! And to complete the list, you should know "contig.exe", which defragments one or a smaller group of files. As you might know, Linux bootmanager Grub4DOS is able to boot a CDROM image ... and it complains, if the image isn't contiguous. Use "contig.exe", and it runs ! Keep in mind, that EVERY total defragmentation tool needs 15 to 20% of unused volume space as a minimum for its work.

Regardscmdr

]]>Thu, 08 Oct 2009 19:14:25 +0000http://gparted-forum.surf4.info/viewtopic.php?pid=21530#p21530http://gparted-forum.surf4.info/viewtopic.php?pid=21524#p21524
Cool! I was not aware of any other defragmenters. This one appears to run under Windows. If you happen to come across one that runs under GNU/Linux I would like to know. It could be a useful tool on the GParted-Live CD.]]>Thu, 08 Oct 2009 10:19:01 +0000http://gparted-forum.surf4.info/viewtopic.php?pid=21524#p21524http://gparted-forum.surf4.info/viewtopic.php?pid=21511#p21511
nice topic. thanks for the material.]]>Tue, 06 Oct 2009 12:03:56 +0000http://gparted-forum.surf4.info/viewtopic.php?pid=21511#p21511http://gparted-forum.surf4.info/viewtopic.php?pid=16232#p16232
A link to this post has been added from the GParted web site FAQ

Thank goes to cmdr for writing the detailed resize-windows.txt instructions found at the beginning of this forum post.

Dream fulfilled : I found Portable JKDefrag Version 3.36, a GNU project. It's a fool-proof (background) defragmenter for Windows, which uses Windows API functions and is therefore very safe. It works with some limitations on VISTA, too.

Cool! I was not aware of any other defragmenters. This one appears to run under Windows. If you happen to come across one that runs under GNU/Linux I would like to know. It could be a useful tool on the GParted-Live CD.

Dream fulfilled : I found Portable JKDefrag Version 3.36, a GNU project. It's a fool-proof (background) defragmenter for Windows, which uses Windows API functions and is therefore very safe. It works with some limitations on VISTA, too.

Advantages versus Windows Defragger are :

- Much faster. - Totally automatic, extremely easy to use. - Optimized for daily use. - Disk optimization, several strategies ( parameter driven ). - Directories are moved to the beginning of the disk. - Reclaims MFT reserved space after disk-full. - Maintains free spaces for temporary files. - Can defragment very full harddisks. - Can defragment very large files. - Can defragment individual directories and files. - Can be run automatically with the Windows Scheduler. - Can be used from the commandline. - Can be used as a screen saver. - Can be run from cdrom or memory stick. - Sources available, can be customized.

I tried to change MBR's 4-Byte drive ID (address 0x1B8 to 0x1BB) with "fdisk" console ( key/command sequence : x i 0x1234ABCD p w ), which worked well within fdisk, but did not get written to real MBR, neither on a harddisk, nor on an USB Stick, I tested. (Detailed description, see "Variant A" in my draft).Command "i" seems to be very new ! If there is a writing convention to distinguish a bash script commandline parameter "i" of a program and the "i" key within its console state, I don't know it up to now. I thought that ("sheltered") "(i)" would be understandable.

Which version of fdisk and on what platform (operating system) is this new "(i)" option available?

Did you use the (w) write to disk option before you exited from fdisk? If so then perhaps there is a bug that should be logged with the fdisk team.

cmdr wrote:

Does "Gparted" move fragments of files, that would else block shrinking the partition to a wanted size ? Or limits the first detected file fragment the offered space for shrinking (as it is in VISTA) ?

In the case of a move operation, gparted simply moves the partition block by block. No additional processing is performed to determine the content of the block.In the case of a resize operation, the ntfsresize command is called. To find out how the file system is shrunk, you could either review the source code, or perhaps contact the ntfsprogs team. Personally I have not reviewed the ntfsprogs source code.