[SilentCode]

Hi,

I just solved a problem where by the following registry entry was causing an
application to fail.

HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList\

Under XPe the value is:
"ProfilesDirectory"=D:\Documents and Settings

Under full XP the value is:
"ProfilesDirectory"=%SystemDrive%\Documents and Settings

This is a subtle difference between XPe and XPPro but it was enough to break
a commercial application. Is anyone else having issues like this? Is it
documented anywhere that this nuances exist?

Meanwhile I'll add this fix my ever growing list of workarounds and hacks.
Just thought I share my findings.

Thanks,
Ed.

[Andy Allred [MS]]

Hmm, weird.
Ed, that reg key is owned by the windows subsystem component but it's
probably the platform script adding that drive letter via the destination
entry you made in TD, but i'd need to look into it further to know for sure.
In any case it's a good catch. I'll file a bug for now and if I find
something interesting will let you know. What would really help is if you
e-mail this issue to wecrt @ microsoft.com so others in the team can see it
and also i'll have your e-mail address to contact you for more information.

Thanks Ed.
Andy
--
Embedded team blog: http://blogs.msdn.com/embedded/

This posting is provided "AS IS" with no warranties, and confers no rights.



"SilentCode" <SilentCode@discussions.microsoft.com> wrote in message
news:D050F18C-E069-4514-9E93-214E870901AC@microsoft.com...
> Hi,
>
> I just solved a problem where by the following registry entry was causing
> an
> application to fail.
>
> HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList\
>
> Under XPe the value is:
> "ProfilesDirectory"=D:\Documents and Settings
>
> Under full XP the value is:
> "ProfilesDirectory"=%SystemDrive%\Documents and Settings
>
> This is a subtle difference between XPe and XPPro but it was enough to
> break
> a commercial application. Is anyone else having issues like this? Is it
> documented anywhere that this nuances exist?
>
> Meanwhile I'll add this fix my ever growing list of workarounds and hacks.
> Just thought I share my findings.
>
> Thanks,
> Ed.
>

[SilentCode]

I just sent the email.

Thanks,
Ed.

"Andy Allred [MS]" wrote:

> Hmm, weird.
> Ed, that reg key is owned by the windows subsystem component but it's
> probably the platform script adding that drive letter via the destination
> entry you made in TD, but i'd need to look into it further to know for sure.
> In any case it's a good catch. I'll file a bug for now and if I find
> something interesting will let you know. What would really help is if you
> e-mail this issue to wecrt @ microsoft.com so others in the team can see it
> and also i'll have your e-mail address to contact you for more information.
>
> Thanks Ed.
> Andy
> --
> Embedded team blog: http://blogs.msdn.com/embedded/
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
>
> "SilentCode" <SilentCode@discussions.microsoft.com> wrote in message
> news:D050F18C-E069-4514-9E93-214E870901AC@microsoft.com...
> > Hi,
> >
> > I just solved a problem where by the following registry entry was causing
> > an
> > application to fail.
> >
> > HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList\
> >
> > Under XPe the value is:
> > "ProfilesDirectory"=D:\Documents and Settings
> >
> > Under full XP the value is:
> > "ProfilesDirectory"=%SystemDrive%\Documents and Settings
> >
> > This is a subtle difference between XPe and XPPro but it was enough to
> > break
> > a commercial application. Is anyone else having issues like this? Is it
> > documented anywhere that this nuances exist?
> >
> > Meanwhile I'll add this fix my ever growing list of workarounds and hacks.
> > Just thought I share my findings.
> >
> > Thanks,
> > Ed.
> >
>
>
>