Thanks to every one for the replies !
Well, I'm not trying anything doggy & I don't intend to defeat the Windows software registration ...etc, cracks for Windows are widely availabe on the net & I don't need to get in that kind of business.
If I succeed in solving this "little" problem, It'll be possible to use an install of windows & register it as usual, transparently in the system I'm designing, If for some reasons I can't solve this problem then, my system will require a corporate version of windows that doesn't need registration...The wrong thing about the corporate version, is that it will narrow the use of my system to the owners of a corporate version of Windows, making my system away from the reach of the common people.
On the sysinternals forum I've been told that the paths are coded in the "configuration manager" which is not explained in the "Windows internals 4th edition"...but on a website I've found that it's Ntldr that locates & reads the registry/hives.
I've found an old post on a forum, talking about reverse engineering ntldr, it said that inside ntldr there's an "embeded" exe, osloader.exe...it would be cool if I could change the paths to suite my needs, but i'm not sure it's doable.
I would also need to somehow read the mac address of the NIC 0 & include it in the path...it'd be perfect....yea but will require a lot of old programming skills to do it in asembler.
Ok, if i'll have to reverse ntldr then, my project will remain experimental until Microsoft agrees to make an official patch to implement this freature.
Any ideas ?
Thanks !
cnc2.