The symptoms are as follows.

The page uses standard compliance mode and fore the most part housemenus exept for in containers where i am forced to rely on solpart menu.

(at leat visitors get the clean page)

the problem is that in 2 out of 5 of the computers we tested the page on the soulpart menus start its little animated gif and then gives up.

and refreshing the page on those computers causes it to log out.

on of these two computes was a WInXP with IE6 the othere a Win Vista with IE7

the other three computers where WinXP and had IE6, IE7, firefox, Safari and worked

the two where it dident work did work on dnn demo sites... which leads me the suscept standard compliance mode...

anyone know a solution?

The solpart action menu isn't standards compliant, but there is a menu called dropdownnavigationprovider or DropDownActions.ascx for making the action menu display as a dropdown list, which is compliant.

There's also a populate on demand feature that only loads the menu on request or mouseover. This is where you're supposed to see a small animated loading gif indicating the menu is loading. It sounds to me as if it or some other piece is missing or not being served properly and this is causing the 404. I have seen this on a cheapie shared hosting account that was unreliable. You can switch the populatenodesfromclient attribute to false in the menu section of your skin and that should make it work better.

Check the first document download on this page: http://www.dotnetnuke.com/Products/Development/Forge/CoreWebControls/Downloads/tabid/874/Default.aspx
It has info on all the included menus and things just mentioned.

There is a lot of info on DNNCreative about compliance, but I think it's mostly on subscription (which is worth getting). Personally I would just pass on certain standards and use what actually works right now.

Rob