Q: Disk0s4 After Yosemite installation

possibly, i might be able to sort this, if so how do i tell the mac to boot from the USB?

Also because windows is on a seperate partition, will this work with the stick in, im not sure how having that on a usb would work

also any other options for fixing it, im quite limited from the mac side i suppose but im so close! at the windows splash screen, there's obviously something in the boot that its not liking

and i only need a recovery disk for that right? as it looks like apart from repairing it it is reinstalling windows....

if it just repairs and repairs the boot manager then great but if it asks for a windows disk i dont have my image, if all i need is the recovery disc image.... then great

http://maximumpcguides.com/windows-7/create-a-windows-7-system-repair-disc/

it looks like you can download the recovery disc image for free

well i am at a loss now, i managed to find a windows 7 64 bit repair disk ISO and used bootcamp to make a bootable USB. i held the option key and booted from the USB, becuase doing nothing it wasnt booting to the USB. I wonder if this has something to do with it - when i go into the system recovery menu and select the operating system it finds Windows 7, but it says "Windows 7 (location unkown) bootcamp" - anyway same result, it says it cant repair it, and on the log report it says it found no errors.

I wonder if its some kind of hardware that it doesnt like all of a sudden. surely there is a way to fix this without a reinstall.

I am just at a loss, i am pretty sure the ISO is good its 185mb and bootcamp regognised it as a windows repair - when i boot from the USB it loads into the windows recovery shell, but again like i say it cant find a problem to repair, however surely it should just re install the boot portion of windows, or does that require a new install, something at the moment i cant do.

Pieple running windows that are having the same problem on the net of the hanging at the splash screen with safe mode hanging on the loading of CLASSPNP.SYS seem to fix the issue by messing around with hardware.

any ideas?

mabye the RAID settings are wrong?

well i am at a loss now, i managed to find a windows 7 64 bit repair disk ISO and used bootcamp to make a bootable USB. i held the option key and booted from the USB, becuase doing nothing it wasnt booting to the USB. I wonder if this has something to do with it - when i go into the system recovery menu and select the operating system it finds Windows 7, but it says "Windows 7 (location unkown) bootcamp" - anyway same result, it says it cant repair it, and on the log report it says it found no errors.

I wonder if its some kind of hardware that it doesnt like all of a sudden. surely there is a way to fix this without a reinstall.

I am just at a loss, i am pretty sure the ISO is good its 185mb and bootcamp regognised it as a windows repair - when i boot from the USB it loads into the windows recovery shell, but again like i say it cant find a problem to repair, however surely it should just re install the boot portion of windows, or does that require a new install, something at the moment i cant do.

Pieple running windows that are having the same problem on the net of the hanging at the splash screen with safe mode hanging on the loading of CLASSPNP.SYS seem to fix the issue by messing around with hardware.

any ideas?

mabye the RAID settings are wrong?

Also some poeple say it solved switching from AHCI to IDE?

"This happens if Windows cannot find your system partition. It has nothing to do with CLASSPNP.SYS. You probably noticed that right before CLASSPNP.SYS it loaded DISK.SYS, this is the driver that mounts your volumes properly, before that it's using a lower level driver. That's why if you delete or replace CLASSPNP.SYS it hangs on the next driver.

In my case it was caused because I dual boot Windows and Linux and apparently I accidentally changed the type of my Windows parition type to HIDDEN NTFS WINDOWS (Type 27) or morelikely another tool gparted hid it because it has a single bad sector (probably since I got the laptop but I didn't noticed until the  warranty expired but it's been like that forever and not getting worse so the disk is ok). Other programs can do the same in Windows so you don't need to be dual booting for this to happen.

So for me the solution was to boot to Linux and use FDISK to change the the partition type back to HPFS/NTFS/ExFAT (Type 7). You should be able to do the same on the command prompt of the Recovery Console in Windows, if not download KNOPPIX. After that it booted like new."

That was someone elses thread - now in the windows system recovery it says i have windows 7 (location unkown) bootcamp - did we make a mistake in fdisk? because it seems it cant find the windows installation? did we get the right numbers? anyway to check without doing the deep search again?

i think this location unknown might be the issue here

"This happens if Windows cannot find your system partition. It has nothing to do with CLASSPNP.SYS. You probably noticed that right before CLASSPNP.SYS it loaded DISK.SYS, this is the driver that mounts your volumes properly, before that it's using a lower level driver. That's why if you delete or replace CLASSPNP.SYS it hangs on the next driver.

In my case it was caused because I dual boot Windows and Linux and apparently I accidentally changed the type of my Windows parition type to HIDDEN NTFS WINDOWS (Type 27) or morelikely another tool gparted hid it because it has a single bad sector (probably since I got the laptop but I didn't noticed until the  warranty expired but it's been like that forever and not getting worse so the disk is ok). Other programs can do the same in Windows so you don't need to be dual booting for this to happen.

So for me the solution was to boot to Linux and use FDISK to change the the partition type back to HPFS/NTFS/ExFAT (Type 7). You should be able to do the same on the command prompt of the Recovery Console in Windows, if not download KNOPPIX. After that it booted like new."

That was someone elses thread - now in the windows system recovery it says i have windows 7 (location unkown) bootcamp - did we make a mistake in fdisk? because it seems it cant find the windows installation? did we get the right numbers? anyway to check without doing the deep search again?

i think this location unknown might be the issue here

mabye we did the fdisk wrong and it cant find the location..

which commands would you like me to post the outcome of loner

What commands would you like me to post the outome of loner