It seems that you could start the external js with document.open() -- that would clear the original document from the browser window and establish a stream to a new document for your document.write() statements. Then write your frameset code with document.write(), and then use document.close(), so the frameset gets displayed on screen.
The prepackaged meat product fumes are getting to your brain, toolman. (Never heard of using it as goggles before... interesting idea) I thought <noframes> content was becoming less relevant to ranking pretty much across the board?
I guess what I am trying to do, however unethical, is to cheaply cloak the url. In other words the spiders eat five pages but not the js, so the users see the redirected site because the js wrote the frameset.
Now I see -- you don't care about NOFRAMES content or the content of the 0% frame. The frameset is just to present a different domain altogether. Cheap stealth.
Yeah, I guess this will work for a while (until human observation kicks in, anyway, like ggrot said). Then the domain gets banned, and you start over, but what the hey! It's like selling your goods from the back of a van instead of renting a storefront.