I cannot download the Tweak UI for Win xp. I rececive an error message:
-- My Documents\TweakUIPowertoySetup_ia64.exe is not a valid Win32
application.

What do I do to resolve this?

Thanks so much for any help,
Diane

Download the version for your OS.

--
--------------------------------------------------------------------------------------------------
Goodbye Web Diary
http://margokingston.typepad.com/har....html#comments
=================================================
"fancydouble" <fancydouble@discussions.microsoft.com> wrote in message news:6481A5E3-5D7F-4E95-92CC-B2D9ABDDA8C6@microsoft.com...
>I cannot download the Tweak UI for Win xp. I rececive an error message:
> -- My Documents\TweakUIPowertoySetup_ia64.exe is not a valid Win32
> application.
>
> What do I do to resolve this?
>
> Thanks so much for any help,
> Diane

Apparently, you downloaded the 64-bit version.
You need to download the 32-bit version.

Microsoft PowerToys for Windows XP (TweakUI) (147 KB).
http://www.microsoft.com/windowsxp/d...powertoys.mspx

--
Carey Frisch
Microsoft MVP
Windows - Shell/User
Microsoft Community Newsgroups
news://msnews.microsoft.com/

-------------------------------------------------------------------------------------------

"fancydouble" wrote:

| I cannot download the Tweak UI for Win xp. I rececive an error message:
| -- My Documents\TweakUIPowertoySetup_ia64.exe is not a valid Win32
| application.
|
| What do I do to resolve this?
|
| Thanks so much for any help,
| Diane

Carey Frisch [MVP] wrote:
> Apparently, you downloaded the 64-bit version.
> You need to download the 32-bit version.
>
> Microsoft PowerToys for Windows XP (TweakUI) (147 KB).
> http://www.microsoft.com/windowsxp/d...powertoys.mspx
>
IMO: such an error may be a good indication that TweakUI may be too
tricky for you to use.

Are you really sure?

"deebs" <deebs@xyzlaernot999.bogus> wrote in message
news:u9l6xpxBGHA.3796@TK2MSFTNGP11.phx.gbl...
> Carey Frisch [MVP] wrote:
>> Apparently, you downloaded the 64-bit version.
>> You need to download the 32-bit version.
>>
>> Microsoft PowerToys for Windows XP (TweakUI) (147 KB).
>> http://www.microsoft.com/windowsxp/d...powertoys.mspx
>>
> IMO: such an error may be a good indication that TweakUI may be too tricky
> for you to use.
>
> Are you really sure?


I'm pretty sure TweakUI is not too tricky for Carey, the poster to whom you
replied rather than to fancydouble.

It is probably far safer that fancydouble use TweakUI than delve into the
registry.

Vanguard wrote:
> "deebs" <deebs@xyzlaernot999.bogus> wrote in message
> news:u9l6xpxBGHA.3796@TK2MSFTNGP11.phx.gbl...
>
>> Carey Frisch [MVP] wrote:
>>
>>> Apparently, you downloaded the 64-bit version.
>>> You need to download the 32-bit version.
>>>
>>> Microsoft PowerToys for Windows XP (TweakUI) (147 KB).
>>> http://www.microsoft.com/windowsxp/d...powertoys.mspx
>>>
>> IMO: such an error may be a good indication that TweakUI may be too
>> tricky for you to use.
>>
>> Are you really sure?
>
>
>
> I'm pretty sure TweakUI is not too tricky for Carey, the poster to whom
> you replied rather than to fancydouble.
>
> It is probably far safer that fancydouble use TweakUI than delve into
> the registry.
>
Yes tru - and please accept my apologies Carey

My reply was intended for the OP and - silly mee!

That's what happens when you use a stupid name.

--
--------------------------------------------------------------------------------------------------
Goodbye Web Diary
http://margokingston.typepad.com/har....html#comments
=================================================
"deebs" <deebs@xyzlaernot999.bogus> wrote in message news:%23Am0eczBGHA.3572@TK2MSFTNGP14.phx.gbl...
> Vanguard wrote:
>> "deebs" <deebs@xyzlaernot999.bogus> wrote in message
>> news:u9l6xpxBGHA.3796@TK2MSFTNGP11.phx.gbl...
>>
>>> Carey Frisch [MVP] wrote:
>>>
>>>> Apparently, you downloaded the 64-bit version.
>>>> You need to download the 32-bit version.
>>>>
>>>> Microsoft PowerToys for Windows XP (TweakUI) (147 KB).
>>>> http://www.microsoft.com/windowsxp/d...powertoys.mspx
>>>>
>>> IMO: such an error may be a good indication that TweakUI may be too
>>> tricky for you to use.
>>>
>>> Are you really sure?
>>
>>
>>
>> I'm pretty sure TweakUI is not too tricky for Carey, the poster to whom
>> you replied rather than to fancydouble.
>>
>> It is probably far safer that fancydouble use TweakUI than delve into
>> the registry.
>>
> Yes tru - and please accept my apologies Carey
>
> My reply was intended for the OP and - silly mee!

When you are following up on an earlier post keep all replies in the same
thread.

Composing a New Message

To compose a new message, click the New Post button in the lower-right
frame. In
the window that appears, a form will allow you to compose a new message with
fields
for the sender's name, sender's e-mail, subject, and body. By default, the
currently
selected newsgroup will appear in the Newsgroups field. You can also attach
a file to
your new message. Once you have filled out the message fields and clicked
the Send
link, your message will be processed and posted to the newsgroup.

Composing a Reply

You can reply to individual messages by clicking the Post Reply button in
the lower-
right frame. In the new message window, a form will allow you to compose a
reply
with fields for the sender's name, sender's e-mail, subject (already filled
in), and body.
You can also attach a file to your new message and quote the original
message. Once
you have filled out the message fields and clicked the Send link, your
message will be
processed and posted.



~~~~~~


Hope this helps.

Gerry
~~~~~~~~~~~~~~~~~~~~~~~~
FCA

Stourport, Worcs, England
Enquire, plan and execute.
~~~~~~~~~~~~~~~~~~~~~~~~

"deebs" <deebs@xyzlaernot999.bogus> wrote in message
news:%23Am0eczBGHA.3572@TK2MSFTNGP14.phx.gbl...
> Vanguard wrote:
>> "deebs" <deebs@xyzlaernot999.bogus> wrote in message
>> news:u9l6xpxBGHA.3796@TK2MSFTNGP11.phx.gbl...
>>
>>> Carey Frisch [MVP] wrote:
>>>
>>>> Apparently, you downloaded the 64-bit version.
>>>> You need to download the 32-bit version.
>>>>
>>>> Microsoft PowerToys for Windows XP (TweakUI) (147 KB).
>>>> http://www.microsoft.com/windowsxp/d...powertoys.mspx
>>>>
>>> IMO: such an error may be a good indication that TweakUI may be too
>>> tricky for you to use.
>>>
>>> Are you really sure?
>>
>>
>>
>> I'm pretty sure TweakUI is not too tricky for Carey, the poster to whom
>> you replied rather than to fancydouble.
>>
>> It is probably far safer that fancydouble use TweakUI than delve into the
>> registry.
>>
> Yes tru - and please accept my apologies Carey
>
> My reply was intended for the OP and - silly mee!

"David Candy" <.> wrote in message
news:OfUKh9zBGHA.3572@TK2MSFTNGP14.phx.gbl...
That's what happens when you use a stupid name.


--- REPLY SEPARATOR ---
(required only due to poster using quoted-printable format)

Referring maybe to deebs being a dweeb (as I don't see deeb means anything)?
Hey, we're all prone to being a dweeb before that first cup of coffee and,
for some of us, it takes 2 cups of coffee.

Hell, you post using quotable-printable format which is a pain in the ass
for lots of users using webnews interfaces or old newsreaders that don't
understand the format. Even OE doesn't know how to reply to
quoted-printable. Well, to be fair, the RFCs describe how to use format and
even later described format=flowed but they don't define how to *handle*
that format when replying. Like HTML, quoted-printable should also not be
used in Usenet posts.

But links break.

--
--------------------------------------------------------------------------------------------------
Goodbye Web Diary
http://margokingston.typepad.com/har....html#comments
=================================================
"Vanguard" <vanguard.code@comcastNIX.net> wrote in message news:%23TMfrP2BGHA.1312@TK2MSFTNGP09.phx.gbl...
> "David Candy" <.> wrote in message
> news:OfUKh9zBGHA.3572@TK2MSFTNGP14.phx.gbl...
> That's what happens when you use a stupid name.
>
>
> --- REPLY SEPARATOR ---
> (required only due to poster using quoted-printable format)
>
> Referring maybe to deebs being a dweeb (as I don't see deeb means anything)?
> Hey, we're all prone to being a dweeb before that first cup of coffee and,
> for some of us, it takes 2 cups of coffee.
>
> Hell, you post using quotable-printable format which is a pain in the ass
> for lots of users using webnews interfaces or old newsreaders that don't
> understand the format. Even OE doesn't know how to reply to
> quoted-printable. Well, to be fair, the RFCs describe how to use format and
> even later described format=flowed but they don't define how to *handle*
> that format when replying. Like HTML, quoted-printable should also not be
> used in Usenet posts.
>

And most users can't reconstruct the link.

--
--------------------------------------------------------------------------------------------------
Goodbye Web Diary
http://margokingston.typepad.com/har....html#comments
=================================================
"Vanguard" <vanguard.code@comcastNIX.net> wrote in message news:%23TMfrP2BGHA.1312@TK2MSFTNGP09.phx.gbl...
> "David Candy" <.> wrote in message
> news:OfUKh9zBGHA.3572@TK2MSFTNGP14.phx.gbl...
> That's what happens when you use a stupid name.
>
>
> --- REPLY SEPARATOR ---
> (required only due to poster using quoted-printable format)
>
> Referring maybe to deebs being a dweeb (as I don't see deeb means anything)?
> Hey, we're all prone to being a dweeb before that first cup of coffee and,
> for some of us, it takes 2 cups of coffee.
>
> Hell, you post using quotable-printable format which is a pain in the ass
> for lots of users using webnews interfaces or old newsreaders that don't
> understand the format. Even OE doesn't know how to reply to
> quoted-printable. Well, to be fair, the RFCs describe how to use format and
> even later described format=flowed but they don't define how to *handle*
> that format when replying. Like HTML, quoted-printable should also not be
> used in Usenet posts.
>

"David Candy" <.> wrote in message
news:Oxandi2BGHA.1124@TK2MSFTNGP10.phx.gbl...

And most users can't reconstruct the link.

--- REPLY SEPARATOR ---
(needed only due to poster using quoted-printable format)

And many users can't even figure out how to use the Shift key, period
character, or have a clue that they are asking someone ELSE their question
(if they even pose a question) and should make it intelligible to someone
other than themself. Quoted-printable breaks more than it fixes. You end
up infuriating more users than kowtowing to the boobs that cannot figure out
how to copy/paste a URL. Besides users that complain quoted-printable
doesn't display correctly in their NNTP client, I've also been told by some
webnews users that the line ends up being as one really long line instead of
a line-wrapped paragraph. Some newsreaders don't know how to handle the
encoded characters used when quoted-printable is used. Just because a
format works for e-mail doesn't mean it is good in Usenet.

Just look at how much more difficult it becomes to insert in-body replies
(i.e., instead of of one huge disconnected reply at the end, you insert a
reply next to whatever it pertains). You can't tell where the original
content ends and the inserted reply begins unless you use clumsy and message
separator lines, like I have to use in replying to your posts (even when I'm
not inserting in-body replies but just one reply at the end). I don't know
how other NNTP clients handle delineating original from reply, and since you
are also using OE, the problem (in OE) is that there is no automatic
differentiation between who said what. Because we are still stuck with
using plain-text for Usenet posts (to remain compliant and compatible with
most users), we cannot use formatting, colors, auto-indents, blockquote,
indented tables with borders, or other visually appealing means to
differentiate who said what. Yes, there are add-ons or other NNTP clients
that will color-code, indent, or whatever but that is NOT what is actually
*in* the post and obviously not every user are using the same NNTP client.

Actually I got into several arguments with old farts and Usenet wizards
about the use of quoted-printable. I liked it because of the line-wrapping
when posting (and when reading it provided your newsreader supports it, and
not all do) but it really does suck when replying (because there is no
distinguishable separation between the original and reply content). I
didn't have a vested interest in using quoted-printable other than as a
preference. After considerable debates, the other side has repeatedly
convinced me it was a bad format for Usenet.

Yes, the multiple indentation using quote characters is messy. It's been 6
years since quoted-printable got published in an RFC and yet there are many
NNTP clients or webnews interfaces that don't support it. Although non-OE
users will remark that their NNTP client handles quoted-printable
"correctly", I really haven't found an RFC that dictates or suggests how any
client should handle the quoted-printable content when replying. The RFCs
define how it is constructed but not how to handle it in replies, so every
NNTP client could do it differently.

If an RFC ever gets written or updated that specifies how NNTP client should
or must handle logical paragraphs that are physically encoded within the
quoted-printable format, and after some time has passed to let the NNTP
clients time to catch up, then I see it as an okay format in Usenet. I can
find the RFCs that define how to encode using quoted-printable format. Do
you know of any that specify how NNTP client will encode their replies when
the original content used quoted-printable?

I really don't think arguing in favor of quoted-printable because of a few
boobs that cannot figure out how to copy/paste a URL (and for a sender that
doesn't take this into consideration before submitting their post) doesn't
make much of a rational argument for its use. It is stupid that there
is(are) RFC(s) to define quoted-printable but none to define how to handle
it in a reply.

Flowed is supposed to handle the probs of QP. I haven't used it because it was new. But I did intend changing to flowed one day after other NRs caught up (specifically older OE versions people may be using). Flowed acts like plain text to old readers and flowed to new readers.

Still OE is heaps better than Netscape 2, my previous reader while I waited for MS to get their finger out and write MS Internet Mail and News.

--
--------------------------------------------------------------------------------------------------
Goodbye Web Diary
http://margokingston.typepad.com/har....html#comments
=================================================
"Vanguard" <vanguard.code@comcastNIX.net> wrote in message news:%23dLR6F4BGHA.2040@TK2MSFTNGP14.phx.gbl...
> "David Candy" <.> wrote in message
> news:Oxandi2BGHA.1124@TK2MSFTNGP10.phx.gbl...
>
> And most users can't reconstruct the link.
>
> --- REPLY SEPARATOR ---
> (needed only due to poster using quoted-printable format)
>
> And many users can't even figure out how to use the Shift key, period
> character, or have a clue that they are asking someone ELSE their question
> (if they even pose a question) and should make it intelligible to someone
> other than themself. Quoted-printable breaks more than it fixes. You end
> up infuriating more users than kowtowing to the boobs that cannot figure out
> how to copy/paste a URL. Besides users that complain quoted-printable
> doesn't display correctly in their NNTP client, I've also been told by some
> webnews users that the line ends up being as one really long line instead of
> a line-wrapped paragraph. Some newsreaders don't know how to handle the
> encoded characters used when quoted-printable is used. Just because a
> format works for e-mail doesn't mean it is good in Usenet.
>
> Just look at how much more difficult it becomes to insert in-body replies
> (i.e., instead of of one huge disconnected reply at the end, you insert a
> reply next to whatever it pertains). You can't tell where the original
> content ends and the inserted reply begins unless you use clumsy and message
> separator lines, like I have to use in replying to your posts (even when I'm
> not inserting in-body replies but just one reply at the end). I don't know
> how other NNTP clients handle delineating original from reply, and since you
> are also using OE, the problem (in OE) is that there is no automatic
> differentiation between who said what. Because we are still stuck with
> using plain-text for Usenet posts (to remain compliant and compatible with
> most users), we cannot use formatting, colors, auto-indents, blockquote,
> indented tables with borders, or other visually appealing means to
> differentiate who said what. Yes, there are add-ons or other NNTP clients
> that will color-code, indent, or whatever but that is NOT what is actually
> *in* the post and obviously not every user are using the same NNTP client.
>
> Actually I got into several arguments with old farts and Usenet wizards
> about the use of quoted-printable. I liked it because of the line-wrapping
> when posting (and when reading it provided your newsreader supports it, and
> not all do) but it really does suck when replying (because there is no
> distinguishable separation between the original and reply content). I
> didn't have a vested interest in using quoted-printable other than as a
> preference. After considerable debates, the other side has repeatedly
> convinced me it was a bad format for Usenet.
>
> Yes, the multiple indentation using quote characters is messy. It's been 6
> years since quoted-printable got published in an RFC and yet there are many
> NNTP clients or webnews interfaces that don't support it. Although non-OE
> users will remark that their NNTP client handles quoted-printable
> "correctly", I really haven't found an RFC that dictates or suggests how any
> client should handle the quoted-printable content when replying. The RFCs
> define how it is constructed but not how to handle it in replies, so every
> NNTP client could do it differently.
>
> If an RFC ever gets written or updated that specifies how NNTP client should
> or must handle logical paragraphs that are physically encoded within the
> quoted-printable format, and after some time has passed to let the NNTP
> clients time to catch up, then I see it as an okay format in Usenet. I can
> find the RFCs that define how to encode using quoted-printable format. Do
> you know of any that specify how NNTP client will encode their replies when
> the original content used quoted-printable?
>
> I really don't think arguing in favor of quoted-printable because of a few
> boobs that cannot figure out how to copy/paste a URL (and for a sender that
> doesn't take this into consideration before submitting their post) doesn't
> make much of a rational argument for its use. It is stupid that there
> is(are) RFC(s) to define quoted-printable but none to define how to handle
> it in a reply.
>

David

http://snipurl.com/

I agree with you but the protagonists eventually wore me down.


--

Regards.

Gerry
~~~~
FCA
Stourport, England

Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~


"David Candy" <.> wrote in message
news:OQTCLi2BGHA.1008@TK2MSFTNGP12.phx.gbl...
But links break.

--
--------------------------------------------------------------------------------------------------
Goodbye Web Diary
http://margokingston.typepad.com/har....html#comments
=================================================
"Vanguard" <vanguard.code@comcastNIX.net> wrote in message
news:%23TMfrP2BGHA.1312@TK2MSFTNGP09.phx.gbl...
> "David Candy" <.> wrote in message
> news:OfUKh9zBGHA.3572@TK2MSFTNGP14.phx.gbl...
> That's what happens when you use a stupid name.
>
>
> --- REPLY SEPARATOR ---
> (required only due to poster using quoted-printable format)
>
> Referring maybe to deebs being a dweeb (as I don't see deeb means
> anything)?
> Hey, we're all prone to being a dweeb before that first cup of coffee and,
> for some of us, it takes 2 cups of coffee.
>
> Hell, you post using quotable-printable format which is a pain in the ass
> for lots of users using webnews interfaces or old newsreaders that don't
> understand the format. Even OE doesn't know how to reply to
> quoted-printable. Well, to be fair, the RFCs describe how to use format
> and
> even later described format=flowed but they don't define how to *handle*
> that format when replying. Like HTML, quoted-printable should also not be
> used in Usenet posts.
>

I have a great problem with those types of links. They don't say where they go. I never click them. It's hard to get me to click anything but an unknown link as no chance. Not for security reasons (at least not in MSNews) but most links aren't worth my time and an unknown link just makes it no reason to click. I lot of users are like me (I know this because I read a lot of usuability reports).

--
--------------------------------------------------------------------------------------------------
Goodbye Web Diary
http://margokingston.typepad.com/har....html#comments
=================================================
"Gerry Cornell" <gcjc@tenretnitb.com> wrote in message news:%23euSTK5BGHA.344@TK2MSFTNGP11.phx.gbl...
> David
>
> http://snipurl.com/
>
> I agree with you but the protagonists eventually wore me down.
>
>
> --
>
> Regards.
>
> Gerry
> ~~~~
> FCA
> Stourport, England
>
> Enquire, plan and execute
> ~~~~~~~~~~~~~~~~~~~
>
>
> "David Candy" <.> wrote in message
> news:OQTCLi2BGHA.1008@TK2MSFTNGP12.phx.gbl...
> But links break.
>
> --
> --------------------------------------------------------------------------------------------------
> Goodbye Web Diary
> http://margokingston.typepad.com/har....html#comments
> =================================================
> "Vanguard" <vanguard.code@comcastNIX.net> wrote in message
> news:%23TMfrP2BGHA.1312@TK2MSFTNGP09.phx.gbl...
>> "David Candy" <.> wrote in message
>> news:OfUKh9zBGHA.3572@TK2MSFTNGP14.phx.gbl...
>> That's what happens when you use a stupid name.
>>
>>
>> --- REPLY SEPARATOR ---
>> (required only due to poster using quoted-printable format)
>>
>> Referring maybe to deebs being a dweeb (as I don't see deeb means
>> anything)?
>> Hey, we're all prone to being a dweeb before that first cup of coffee and,
>> for some of us, it takes 2 cups of coffee.
>>
>> Hell, you post using quotable-printable format which is a pain in the ass
>> for lots of users using webnews interfaces or old newsreaders that don't
>> understand the format. Even OE doesn't know how to reply to
>> quoted-printable. Well, to be fair, the RFCs describe how to use format
>> and
>> even later described format=flowed but they don't define how to *handle*
>> that format when replying. Like HTML, quoted-printable should also not be
>> used in Usenet posts.
>>
>
>

David

Yep. I know others who feel as you do.

--

Regards.

Gerry
~~~~
FCA
Stourport, England

Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~


"David Candy" <.> wrote in message
news:OdqeWP5BGHA.3580@TK2MSFTNGP11.phx.gbl...
I have a great problem with those types of links. They don't say where they
go. I never click them. It's hard to get me to click anything but an unknown
link as no chance. Not for security reasons (at least not in MSNews) but
most links aren't worth my time and an unknown link just makes it no reason
to click. I lot of users are like me (I know this because I read a lot of
usuability reports).

--
--------------------------------------------------------------------------------------------------
Goodbye Web Diary
http://margokingston.typepad.com/har....html#comments
=================================================
"Gerry Cornell" <gcjc@tenretnitb.com> wrote in message
news:%23euSTK5BGHA.344@TK2MSFTNGP11.phx.gbl...
> David
>
> http://snipurl.com/
>
> I agree with you but the protagonists eventually wore me down.
>
>
> --
>
> Regards.
>
> Gerry
> ~~~~
> FCA
> Stourport, England
>
> Enquire, plan and execute
> ~~~~~~~~~~~~~~~~~~~
>
>
> "David Candy" <.> wrote in message
> news:OQTCLi2BGHA.1008@TK2MSFTNGP12.phx.gbl...
> But links break.
>
> --
> --------------------------------------------------------------------------------------------------
> Goodbye Web Diary
> http://margokingston.typepad.com/har....html#comments
> =================================================
> "Vanguard" <vanguard.code@comcastNIX.net> wrote in message
> news:%23TMfrP2BGHA.1312@TK2MSFTNGP09.phx.gbl...
>> "David Candy" <.> wrote in message
>> news:OfUKh9zBGHA.3572@TK2MSFTNGP14.phx.gbl...
>> That's what happens when you use a stupid name.
>>
>>
>> --- REPLY SEPARATOR ---
>> (required only due to poster using quoted-printable format)
>>
>> Referring maybe to deebs being a dweeb (as I don't see deeb means
>> anything)?
>> Hey, we're all prone to being a dweeb before that first cup of coffee
>> and,
>> for some of us, it takes 2 cups of coffee.
>>
>> Hell, you post using quotable-printable format which is a pain in the ass
>> for lots of users using webnews interfaces or old newsreaders that don't
>> understand the format. Even OE doesn't know how to reply to
>> quoted-printable. Well, to be fair, the RFCs describe how to use format
>> and
>> even later described format=flowed but they don't define how to *handle*
>> that format when replying. Like HTML, quoted-printable should also not
>> be
>> used in Usenet posts.
>>
>
>

Thank you for the info on 64 bit versus 32. I can download it now.

Happy Holidays to all and a BIG thanks to all who responded.
--
Diane


"fancydouble" wrote:

> I cannot download the Tweak UI for Win xp. I rececive an error message:
> -- My Documents\TweakUIPowertoySetup_ia64.exe is not a valid Win32
> application.
>
> What do I do to resolve this?
>
> Thanks so much for any help,
> Diane

Gerry Cornell wrote:
> David
>
> Yep. I know others who feel as you do.
>
Plus there is the chance that a link may be to one contrary to policies
if you know what I mean.

"Suck eggs" comes to mind!

--

Hope this helps.

Gerry
~~~~
FCA
Stourport, England

Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~


"deebs" <deebs@xyzlaernot999.bogus> wrote in message
news:u13UEh%23BGHA.1288@TK2MSFTNGP09.phx.gbl...
> Gerry Cornell wrote:
>> David
>>
>> Yep. I know others who feel as you do.
>>
> Plus there is the chance that a link may be to one contrary to policies if
> you know what I mean.
>

Hi,

This will occur, if you get a bad
download.

Sometimes, Windows will interpret
a download as complete, when it's not
all there; and will reject it with
this error message.

Re-download it.

Ken .





On Thu, 22 Dec 2005 07:19:02 -0800,
"fancydouble"
<fancydouble@discussions.microsoft.com>
wrote:

>I cannot download the Tweak UI for Win xp. I rececive an error message:
>-- My Documents\TweakUIPowertoySetup_ia64.exe is not a valid Win32
>application.
>
>What do I do to resolve this?
>
>Thanks so much for any help,
>Diane