As far as I can gather, the Windows XP installation disc via Repair Console, MS ERD Commander 2007, and Windows PE all utilize the same or nearly the same method of determining exactly what is a functional WINDOWS mount point.

May I hear from a happenstance guru on this topic exactly what exactly the criteria are for this determination? I imagine that comparing it to the Windows 98 -> XP upgrade check is a valid analogy, in that there is a minimally defined list of files and/or attributes which will qualify them for acceptance in this matter.

Incidentally, on a XP installation, I have run into a related problem where I cannot access the repair console on the XP installation disc through the XP boot disc, and cannot select C:\WINDOWS through MS ERD Commander 2007. I suspect I would run into the same problem with Windows PE. Ironically, I experience no problems in booting said Windows XP, and do not have any trouble mounting the Windows partition through KNOPPIX.

What might the fix be?

TIA

--

Could you please expand a bit your question, possibly adding more details?

I seem not to be able to understand what do you mean by "mountpoint"?

As well, what do you mean by "cannot access" recovery Console from the boot disc?

Would it be possible that you have something even losely connected to CATCH22 trick here?
http://www.911cd.net/forums//index.php?showtopic=20983
http://www.911cd.net/forums//index.php?sho...20983&st=25

If this is the case, you can try making a "fake" \winsomething\ structure and see if RC can access it, then , if it works it must be something connected to NTFS, file permissions, ACL or a somehow "malformed" Registry, really cannot say.

This thread may also contain something of interest for you:
http://www.boot-land.net/forums/index.php?showtopic=5316

jaclaz

ld-50

I believe those apps check for a licenced version of Windows and if the version is not they stop support for it. Is that what you're trying to overcome?

I posted too soon. I shot from the hip. It turns out that the problem actually lies in the fact that I apparently need a 3rd party driver for my hard drive. I actually did not believe that was the case, since I could not recall a time when that was actually necessary.

--