Holy crap this has been a hassle and a half. So I got a new hard drive, and I wanted to reinstall windows on it, run my new OS on it, basically make it my new system drive and wipe the old drives and start fresh because everything was so messy and I had a lot of crap on my old drives. They even used to have an old windows installed on it on a smaller partition due to me having only one harddrive and going through some real dumb upgrade processes.
Anyways, so I'm nearly finished and all and I reach this massive roadblock that I cannot figure a way around. I have two drives, one is in in two parts, a 10gb partition, and 990~gb of unallocated space. My other drive, the new one, is a full clean 1tb with a fresh windows install (and all my main programs and a few games installed, getting through that list of stuff to reinstall slowly)
Obviously, they both had to have boot functionality on them, as they're both a system drive and I don't want one to rely on the other with the new windows install. So that's fine, I worked through that and got the new one to have a boot setup. I can run this drive with the other drive unplugged entirely. All good. However, the old drive, whenever plugged in, will commandeer the boot process, as well as create a page file on itself for my windows 7. What the fuck is that? I've butchered the shit out of the drive, it's literally empty now. Except there's 8-10gb of untouchable drive space (the page file is 8gb) and I can't format or remove this partition, not with dskpart, nor with windows recovery tools. I literally cannot touch that 8-10gb no matter what I do because that drive no longer has an OS to run independantly, as well as reserves itself if I boot with the other drive.
When I manually select my new OS drive in my bios, it doesn't make a difference. msconfig only lists the old bootable when they're both plugged in. I even tried plugging the old drive in while the other was already booted as I read that sata supports hotswappability, but nothing was detected in device manager or dskpart or anything at all when I tried it. Does anyone have any ideas on what I can do in this situation? And yes finally, I have tried just setting the page file to be on the new drive. I've tried system decided, I've tried manual. I've tried a 16mb pagefile and no pagefile on the old drive, it just boots windows and says we made a temp page file for you cause you suck! Good luck have fun deleting this last 10gb of space.
I just want my page file on my main OS drive, and everything to be neat and tidy. This is dumb as fuck.
Also can I take a minute to criticize msoft? Why would you have booting from any boot install be the default install setting? I mean I understand having it as an option. But if you install a new OS on a new drive, why on earth would it by default rely on previous hard drive OS installs. That's just, creating a destructive dependancy that's going to necessitate a recovery process for people who don't know what the hell they're doing. It was such a baffling issue I had no idea why my drive wasn't working when I was trying to get rid of my old drive.
Anyways, so I'm nearly finished and all and I reach this massive roadblock that I cannot figure a way around. I have two drives, one is in in two parts, a 10gb partition, and 990~gb of unallocated space. My other drive, the new one, is a full clean 1tb with a fresh windows install (and all my main programs and a few games installed, getting through that list of stuff to reinstall slowly)
Obviously, they both had to have boot functionality on them, as they're both a system drive and I don't want one to rely on the other with the new windows install. So that's fine, I worked through that and got the new one to have a boot setup. I can run this drive with the other drive unplugged entirely. All good. However, the old drive, whenever plugged in, will commandeer the boot process, as well as create a page file on itself for my windows 7. What the fuck is that? I've butchered the shit out of the drive, it's literally empty now. Except there's 8-10gb of untouchable drive space (the page file is 8gb) and I can't format or remove this partition, not with dskpart, nor with windows recovery tools. I literally cannot touch that 8-10gb no matter what I do because that drive no longer has an OS to run independantly, as well as reserves itself if I boot with the other drive.
When I manually select my new OS drive in my bios, it doesn't make a difference. msconfig only lists the old bootable when they're both plugged in. I even tried plugging the old drive in while the other was already booted as I read that sata supports hotswappability, but nothing was detected in device manager or dskpart or anything at all when I tried it. Does anyone have any ideas on what I can do in this situation? And yes finally, I have tried just setting the page file to be on the new drive. I've tried system decided, I've tried manual. I've tried a 16mb pagefile and no pagefile on the old drive, it just boots windows and says we made a temp page file for you cause you suck! Good luck have fun deleting this last 10gb of space.
I just want my page file on my main OS drive, and everything to be neat and tidy. This is dumb as fuck.
Also can I take a minute to criticize msoft? Why would you have booting from any boot install be the default install setting? I mean I understand having it as an option. But if you install a new OS on a new drive, why on earth would it by default rely on previous hard drive OS installs. That's just, creating a destructive dependancy that's going to necessitate a recovery process for people who don't know what the hell they're doing. It was such a baffling issue I had no idea why my drive wasn't working when I was trying to get rid of my old drive.
Facebook
Twitter
Instagram