Windows 7 won't load anymore

[vezril]

Hello all. not sure I'm in the right forum but whatever.

I'm running a dual boot system with Slackware Linux and Windows 7 Ultimate 64-bit. Using the LILO boot manager to switch between things. Everything was working fine, just did a fresh install of both OS's. I was fiddling around under windows 7 in disk manager because I essentially needed to created a new partition because I had split my 500 gig hdd into the following: 100 gig, for Windows, 100 gigs for Slackware and the rest for NTFS data. I had not set up that final partition which was what i was doing under disk management. So i set it up as NTFS and say ok then all my partitions switched from blue to orange and it assigned some drive letters to my linux paritions (OS and the Swap) which it had not done previously... as expected. Now being the old tech that I am, i didn't take the time to read any messages that popped up as well... windows does that a lot so so i don't remember if anything popped up before or after this happened.

Now the big problem, i reboot my system, Linux works fine and I can access the windows partition no problem and even modify things in it. Then i load windows again and it just hangs at the "Windows Loading" screen (all black with white text). It's not frozen as the little cursor is blinking. But it just hangs there.

If anyone has any idea what happened and if there's a fix it would be a great help, I really don't feel like re-installing.

Also, if anyone can tell me what process that part of the bootup sequence is (i.e. NTKRNL.exe, NTDETECT.com, etc) guys at microsoft thought it was a good idea to redo/rename all of that again. Also, if anyone could point me where the equivalent of the boot.ini would be... that is if they had the brilliant idea to put one in.

Well that pretty much sums it up

Cheers

 

[gregrocker]

I am not familar with old technology like Linux, but Windows 7 will configure the boot menu correctly when installed last and if drives other than OS's are unplugged in case one is wrongly marked active.

When Win7 has its boot sidetracked, it is normally recoverable by booting into the Win7 installer Repair console and running Startup Repair repeatedly, in case there are multiple issues. All former command fixes are automated there.

 

[vezril]

I am not familar with old technology like Linux, but Windows 7 will configure the boot menu correctly when installed last and if drives other than OS's are unplugged in case one is wrongly marked active.

When Win7 has its boot sidetracked, it is normally recoverable by booting into the Win7 installer Repair console and running Startup Repair repeatedly, in case there are multiple issues. All former command fixes are automated there.

Old technology? You're a funny guy

Anyway, the problem is not the boot loader, and under a dual boot install you must install windows first otherwise windows will right it's own boot loader and not take the Linux partition in consideration so it will appear as a windows only system. Now my active drive is my Linux system as that's where the MBR is and where i can access windows. That is not the problem, i can access windows up to the point where it has to actually load. Also I did forget to mention about that fix you suggested. I did try that but for some unkown reason, the recovery console is telling me that my windows 7 installation is not compatible with the recovery console... which i find quite hilarious that microsoft could have fracked something up like that... i mean I've loaded the recovery with the same disk i used to install. Finally, I don't like microsoft automated fixes... it usually involves making sure i can't access my linux partition. Also, i did not remove any drives.

Wow seriously... old technology? lol...