Jump to content

McTavish

Member
  • Posts

    74
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United Kingdom

Posts posted by McTavish

  1. You can only extend a partition from its ending point on a disk and only if there is free space that you can extend into. In your case you cannot extend D: because it is already at the end of the drive. If you deleted D: then you could extend C: into the new free space. The Vista tools can also shrink partitions, but again only from the same side. You cannot move the starting point of an existing partition.

    Many third-party tools can move partitions the other way on a drive, but I am not an advocate of such things because it is a complex operation that can be prone to errors. If you need to move partitions in that direction it is safer and quicker to delete the partition and create a new one at the desired position.

  2. The Vista tools can only extend partitions the other way on a drive. To move the starting sector of a partition you will need third-party software, but be aware that this type of operation is risky and not something I would recommend. You would be better making an image or a clone of the Windows partition, then delete the original and restore to the new location. Safer and probably much quicker.

    Of course Vista’s starting sector on a hard drive (its offset) is used in the boot process so if you move the beginning of the partition it will render Vista unbootable. You would either have to know how to repair Vista after the move, or be sure any third-party software you use is fully Vista compatible and capable of making the necessary adjustments for you. The only third-party tools I can vouch for at the moment are those from Paragon.

  3. Hi os2fan2 – I'm sorry but you have some common misconceptions surrounding all of this.

    You should not generally install boot managers from vista, if vista is not in the boot volume

    I assume when you say 'Boot volume' you mean what Microsoft calls the System volume.

    http://homepages.tesco.net/%7EJ.deBoynePol...em-volumes.html

    I can't remember for Partition Commander, but with OSL it does not matter, it will always target the correct drive no matter where you install it from.

    Vista changes the system volume (the one where windows is installed) to c:, and programs expecting c: to hold the MBR will invariably not work.

    Vista does not 'change' the drive letter of the system volume or any volume because volumes do not have drive letters to change. Drive letters are simply the labels that each Windows install gives to the volumes it sees. They are not fixed to the volume in any way and when you are not in that Windows there is no letter to a volume. When you install a second Windows and use the Microsoft boot manager, the second Windows will look to see what the first is calling a volume, and then simply say to itself “I'll call it that as well”. When you install Vista by booting the computer from the DVD it will not follow this old convention but simply label volumes in the default order as it sees them. So XP might see a volume as one letter and Vista as another – both are right.

    Not sure about the second part or your comment. The MBR is not connected in any way to volumes or drive letters. The muddling of drive letters and the installing of programs to the C: volume when it is not the volume that Windows is running from, is a feature and an old problem of using the Microsoft bootmanager. When using OSL none of this applies.

  4. It's rock solid and dependable and if anything does overwrite it a 10 second reinstall brings everything back. The only slight feature shortcomings are the minimal partition hiding options, and that you can only rename 30 bootmenu items – but not many people run into that one.

  5. You can't change the Windows XP drive letter I'm afraid. Well, not quite can't, but it's not worth the effort, easier reinstalling. I've not tried Vista on this front yet and it may prove more possible, but I doubt it. http://www.msfn.org/board/Change_Boot_Driv...iti_t90495.html

    Because you just have a simple setup of only XP and Vista OSes you don't really need partition hiding turned on in OSL. Turn it off and then just unmount the partitions you don't want visible by removing their drive letters in Disk Management in each install.

  6. What OS is on each of the first two partitions? In what order did you install all three OSes? What changes have you made so far?

    I'm assuming that partition two is the second Vista install that you mentioned. That you installed XP first and then two installs of Vista. All your boot files would have then been inside XP on the first partition – the System Partition.

    You now have the third partition Vista booting all by itself, so you moved bootmgr and BCD from XP into that install and can now boot it with OSL. Did you replace the PBR in your XP install so that it now boots directly by OSL?

    If that's how it is, then copy the bootmgr file and boot folder from the Vista that has them to the one that does not. You will need to do this from XP as the BCD will be in use in Vista. If you have not yet removed all the boot options from the Vista menu then you can now boot the second partition Vista by the entry in the menu that always booted it. If you have removed the other boot entries then you will need to fix the BCD.

    Set the second partition as the Active one on the disk, make sure it's not hidden, then boot the computer from the Vista DVD and proceed with a normal install until you get to the point where it asks for the product key. Press Shift-F10 to open the command prompt. Run bootrec /rebuildbcd and it will find OSes and ask which ones you want added. Only accept to add the C: \Windows install. (It does not matter what drive letters Windows see themselves as, the DVD will see the Active partition as C:) If you get other options then decline them and exit and reboot.

  7. Your denial of access to the hard disk in Vista I would guess is because of access restrictions. Try opening the command prompt as Administrator, (right click on the CP shortcut and choose that option). If that does not work then turn off UAC.

    Just looked at the OSL docs and it does say to make the partitions Active.

    If you are happy reinstalling Vista in the correct manner then that should fix things for you. You will of course have to reinstall OSL afterwards as Vista will overwrite it. Make sure you can install OSL from floppy or CD, just in case you can't get to the desktop. It should be possible to fix your current install, but you would need to get it correct. I would have to know your exact setup to help.

  8. You haven't grasped it yet 0sync0. Only one of your Windows installs will have their own boot files on their own partition. Trying to directly boot any of the others won't work. If you had XP installed before Vista, then your Vista boot files are inside XP.

  9. Getting rid of the Vista bootmanager could be tricky depending on your setup. You would need to post me a screenshot of your drives in Disk Management. This page should explain to you the possible problems. www.multibooters.co.uk/multiboot.html

    Don't know why OSL only seen one USB drive. I've never had 2 connected.

    Most of OSL's configuration can be done from the bootmenu screen. Once set you should never need to adjust it. You can do some things from inside Windows, but I've only ever played with these options, a long time ago. You'll need to read the manual I'm afraid.

  10. I can't get it to run from a Vista command prompt

    Sorry, but why do you want to?

    I then also get the Vista boot loader

    Were you using the Vista bootmanager before? Any third party bootmanager will not replace the Vista one. If you already allowed the installation of the Vista bootmanager it will mean that one or more of your OSes do not have their own boot files on their own partition and so you will have to continue to use the Vista bootmanager to be able to boot them. You will need to remove the Vista bootmanager yourself, but of course make all you OSes independently bootable before you do so. It kinds of defeats the purpose of using a third party bootmanager if your OSes have already been linked together by the Windows one.

    It hid the other primary partitions which is good. But it thinks there is an OS installed on one of my USB hard drives. It found an MBR on there for some reason. So it hid that partition which I don't want.

    All it's seeing is the partition table in the MBR, it does not mean that there is any bootcode in there. By default it lists all formatted partitions, if they are not bootable you can remove them from the boot menu with F5.

    I've used OSL for so long - several years - that I have just got used to its partition hiding options and I configure the system to work with them. I forgot that if you have a data partition that is on a primary partition it could be a problem. When you set partition hiding in OSL it will mean all primary partitions but the one you are booting into will be hidden. There are two ways round it, you can turn off partition hiding and then use Disk Management in each NT OS to remove the drive letters from just the partitions you don't want to see. Or the other way is to make your data partitions logical ones. Personally I do this from the outset, but it is possible to convert them later if you have a trustworthy partitioning tool. I'm not a fan of such operations and consider them risky, so I can't recommend conversion.

    The free Gag has the same partition hiding options as OSL, but both XOSL and Boot-us have options to hide only the partitions you want.

  11. Bootmagic changed the MBR of the hard drive, and the PBR of the partition that it was installed on. The excellent free XOSL works in the same way and was far superior to BootMagic. There is however a small issue with it and Vista if they are both on the same drive. It changes the Disk Signature in the MBR and so causes Vista boot problems. www2.arnes.si/%7Efkomar/xosl.org

    I would recommend a boot manager that resides entirely in the MBR and does not touch any partitions. These three all work fine with Vista.

    www.osloader.com

    http://gag.sourceforge.net

    www.boot-us.com

    The first one is my personal favourite because it builds the boot menu for you on every boot – not free however.

    EDIT: I can't get links to work in this post and the GAG link always gets a comma added to disable it. Remove the comma from the end of the link in your browser.

  12. How did you get Vista back once you had formatted the XP partition? If you had just let Vista set up the dual boot for you then the Vista boot files should have been on the XP partition.

    Are you now saying you want to reinstall XP? If so, you need to know where your Vista boot files are (bootmgr and BCD). If they are on the Vista partition then I would recommend leaving them there and doing an independent install of XP to the other partition and using another bootmanager. www.multibooters.co.uk/multiboot.html

  13. It’s got nothing to do with boot files or anything on a boot sector. It is in the partition table. One primary partition on a drive will always be marked as Active, and this is only so that if that drive is booted then the bootcode in the MBR will know what partition to go for. It makes no difference what-so-ever whether partitions on second/third hard drives are marked Active or not. It is merely a marker and can have no affect on anything. It is certainly not the cause of any problems you are having.

  14. With NT before Vista it was not possible to do what you want. Too many registry paths such as - E:\Windows, E:\Documents and Settings, etc. are required on bootup so you would never get to the desktop. http://support.microsoft.com/kb/249321

    There has definitely been a change in Vista because now you do get to the desktop, but your account/profile is of course gone and you need to create a new one so you can login to Windows. I have not gone past this point so can’t tell you if Vista will then be ok and usable. If you don’t have a backup image of your Vista install then it will be a gamble.

    If you are sure bootmgr and BCD are now on the Vista partition and it is the Active partition on the hard drive, then the easiest way to force a drive letter change and get it to become C: would be to clear the list of mounted devices in the registry. About halfway down this page http://www.multibooters.co.uk/cloning.html

  15. Sure it’s no big deal jaclaz if you know what you are doing. If you just take your time with a disk sector editor and understand where the disk signature is, you can zero out everything before it. But as you said, what’s the point. Personally I always have a bootmanager installed in the first track of every drive, so that I can swap drives around and still boot all my OSes straight away.

    The Disk Signature has been around since NT3.5 and has been a component of every WinNT OS ever since – even Vista. In fact it has a new significance in Vista.

    http://www.multibooters.co.uk/mbr.html

  16. A4Proxy will route secure connections, but the header filter gets bypassed, so does not work.

    Do you really understand what I said earlier? Unless you have stopped all leaks of personal information out of your computer, then you are wasting your time just hiding your IP. It would be like making an anonymous phone call from a stolen phone and then saying your name and address. Your IP address is not used in any way to gather information about you – it can’t be because it means nothing. You get profiled by your computer ‘saying you name and address’ across the connection, even if that connection is being bounced around the world through anonymous proxies.

  17. You have to config your browser to use A4Proxy/Proxomitron as a local host proxy. Did you follow these instructions, http://www.proxomitron.info/45/help/Installation.html

    Just remembered, A4Proxy won’t work with secure connections, where as Proxomitron will.

    The forwarded header is the last one on the list in the Header Filters. Just tick the Out box. Then click to edit it and put any IP address you want in the ‘replacement test’ field.

×
×
  • Create New...