Start .xml

On Mon, 29 Dec 2014 10:59:52 -0800 (PST), Andy
wrote:

On Monday, December 29, 2014 12:08:27 PM UTC-6, Ken Blake, MVP wrote:
On Sun, 28 Dec 2014 18:33:15 -0800 (PST), Andy
wrote:

I have heard of crossposting, but don't know how to do it.


Please do not send the same message separately to more than one
newsgroup (called multiposting). Doing so just fragments the thread,
so someone who answers in one newsgroup doesn't always get to see
answers from others in another newsgroup. And for those who read all
the newsgroups the message is multiposted to, they see the message
multiple times instead of once (they would see it only once if you
correctly crossposted instead). This wastes everyone's time, and gets
you poorer help than you should get.

If you must send the same message to more than one newsgroup, please
do so by crossposting -- sending a single message simultaneously to
multiple newsgroups (but only to a *few* related newsgroups).

To crosspost (send a single message simultaneously to multiple
newsgroups) simply address to more than one newsgroup. Separate the
newsgroup names with semicolons. So, for example, instead of sending
it to just microsoft.public.windowsxp.general, you could send it to
microsoft.public.windowsxp.general; alt.windows7.general

I disagree that I am wasting anyone's time.

I have multi-posted for years and only had 3 people complain.

When you do things in Usenet that you shouldn't, not everyone
complains. Many folks just killfile you.


I see multi-posts all the time and it does not bother me.

I will consider cross posting.


Your choice entirely.

Did you check back in the VBS group? I posted
something that may be of help, though I'm
not sure.

On Monday, December 29, 2014 1:59:38 PM UTC-6, Ken Blake, MVP wrote:
On Mon, 29 Dec 2014 10:59:52 -0800 (PST), Andy
wrote:

On Monday, December 29, 2014 12:08:27 PM UTC-6, Ken Blake, MVP wrote:
On Sun, 28 Dec 2014 18:33:15 -0800 (PST), Andy
wrote:

I have heard of crossposting, but don't know how to do it.


Please do not send the same message separately to more than one
newsgroup (called multiposting). Doing so just fragments the thread,
so someone who answers in one newsgroup doesn't always get to see
answers from others in another newsgroup. And for those who read all
the newsgroups the message is multiposted to, they see the message
multiple times instead of once (they would see it only once if you
correctly crossposted instead). This wastes everyone's time, and gets
you poorer help than you should get.

If you must send the same message to more than one newsgroup, please
do so by crossposting -- sending a single message simultaneously to
multiple newsgroups (but only to a *few* related newsgroups).

To crosspost (send a single message simultaneously to multiple
newsgroups) simply address to more than one newsgroup. Separate the
newsgroup names with semicolons. So, for example, instead of sending
it to just microsoft.public.windowsxp.general, you could send it to
microsoft.public.windowsxp.general; alt.windows7.general

I disagree that I am wasting anyone's time.

I have multi-posted for years and only had 3 people complain.

When you do things in Usenet that you shouldn't, not everyone
complains. Many folks just killfile you.

No problem. If someone does not want to cheerfully give, then they should not "pretend" to help others.

Most of the readers gladly help and don't get upset over petty things.

I have better things to do.

Andy

On 29 Dec 2014, Andy wrote in
microsoft.public.windowsxp.general:

No problem. If someone does not want to cheerfully give, then they
should not "pretend" to help others.

Most of the readers gladly help and don't get upset over petty
things.

If you were considerate of others, nobody would "pretend."

I have better things to do.

Like wasting other people's time, since you obviously think yours is
more valuable.

Andy wrote:


Most of the readers gladly help and don't get upset over petty things.

What was the question exactly ?

The original post left everything to the imagination.

1) What are you trying to do. State the objectives.
"I want some disk backup to run, and the software
I'm using is Macrium Reflect."

We need background, to understand why you have a
sudden interest in a file ending in .xml. Such files
are about as exciting as .txt files, and the file has
no "super-powers" of its own.

2) What tools do you intend to use ? Is it Macrium Reflect,
and some VBS script ? Or something else. Paint us a picture
that makes sense.

3) What is your current status ? Where are you stuck ?
Have you written a script ? Will you be writing
a script ? What facilities does the tool provide
so it can be scripted ?

Your post could be quite a bit longer, if you
really expected help.

The more precise the question, the more relevant the answer.

Suitable programs for opening .xml would be Wordpad
or Notepad. They allow you to edit the file, change
some preferences and so on. How other applications
use an .xml, is purely their own business. It would
be silly to make the default for .xml, to have Macrium
Reflect open it. That is unlikely to be the primary
input file format for the program. The .xml file is in
some ways, like the Registry, and contains information
similar to a hive you've put in the Registry.

Some modern document formats, consist of what is
effectively a ZIP file, containing a number of folders,
and an XML file to glue it together. This is all
kept inside the ZIP file, and the extension is changed
to hide the details. This is a technique borrowed from
Apple, in which case Apple uses Disk Images with a whole
environment inside, to launch stuff. A bare XML file
by itself is normally relatively useless. And since XML
files can commonly be used to store program preferences,
"binding" one particular program to always open any
..xml you click, would be a mistake (it's bad enough as
it is, that the OS binds XML to Internet Explorer). There's
got to be a better way than that, using a file extension
custom made for the program itself.

Paul

It's already solved in the VBS group. He was
using a VBScript that wasn't working properly
and apparently got sidetracked into thinking an
XML file might be the problem.

On 29 Dec 2014, "Mayayana" wrote in
microsoft.public.windowsxp.general:

It's already solved in the VBS group. He was
using a VBScript that wasn't working properly
and apparently got sidetracked into thinking an
XML file might be the problem.

And since he rudely declined to crosspost or let anybody else know what
had happened, people in all the other groups he multi-posted to are
still running around, kindly spending their valuable time trying to
resolve his problem, which was never adequately defined in the first
place.

What an inconsiderate, lazy dick.

On 29 Dec 2014, Paul wrote in
microsoft.public.windowsxp.general:

Your post could be quite a bit longer, if you
really expected help.

The more precise the question, the more relevant the answer.

Thank you. That should be obvious to anyone who asks for help in a
technical forum like this... unless someone feels entitled to waste
other people's time and effort.

On Monday, December 29, 2014 8:06:42 PM UTC-6, Nil wrote:
On 29 Dec 2014, "Mayayana" wrote in
microsoft.public.windowsxp.general:

It's already solved in the VBS group. He was
using a VBScript that wasn't working properly
and apparently got sidetracked into thinking an
XML file might be the problem.

And since he rudely declined to crosspost or let anybody else know what
had happened, people in all the other groups he multi-posted to are
still running around, kindly spending their valuable time trying to
resolve his problem, which was never adequately defined in the first
place.

What an inconsiderate, lazy dick.

You have a bad anger problem.

You have made it to my kill file.

On 29 Dec 2014, Andy wrote in
microsoft.public.windowsxp.general:

On Monday, December 29, 2014 8:06:42 PM UTC-6, Nil wrote:
What an inconsiderate, lazy dick.

You have a bad anger problem.

You have made it to my kill file.

I have it on good authority that Google Groups has no kill file.