HELP! Partition size causing error with license checking.

[calmius]

Today I run my second OS which is installed on same harddrive as my first OS but in different partition. Then I get a message that "A problem is preventing Windows from accurately checking the license for this computer. Error Code: 0x80090006"
I look up that number in windows knowledge base and find some article pasted here:

"If, when logging into the runtime, you receive the error "A problem is preventing Windows from accurately checking the license for this computer. Error Code: 0x80090006", then this indicates you did not correctly set the partition size in Target Designer. Within Target Designer, you need to inform the tools what size your destination partition is going to be. If it's grossly incorrect, then the runtime will fail. The default setting is for 1024 MB. To change this, click on "Settings" of your config in the center pane of Target Designer. Then select "Target Device Settings" and locate "Boot Partition size" configurable setting. Change this value to the true partition size that the runtime will reside on. IMPORTANT: Re-run check dependency before rebuilding the runtime. "

what happens is that windows doesn't start and nothing happens except that error message. Please elaborate to me what is meant by this explanation above because I am really eager to have this problem fixed because I have some vital software installed in this second OS

I think this is related to some settings I set after installing my new harddrive about 1 months ago.

Please if you don't know how to help me say so but don't ignore this plea for help!

[bailey]

I can't think of anything in the partition size that would have anything to do with what your saying.

[reboot]

It sounds like "target designer" is a piece of 3rd party partitioning software, and nothing to do with windows.

[calmius]

But last time I installed my new harddrive I didn't use any 3rd party software, really. I just used what was with windows XP partion thing.

[jeresimo]

If you could go to SAFE MODE and log in as Administrator. Then try RESTORE in a a previous date before this problem came. I encountered this kind of problem before and that move resolved it. I hope you CREATED A GOOD RESTORE POINT though. HTH.