Jump to content

nasty assertion error


Recommended Posts

Guest George Hester
Posted

Here it is

 

 

 

I tried to open Windows Media Player Classic. This isn't right. I am noticing that no media files open here although the correct codecx are installed. If I hit ignore I just keep getting these types of "Expressions." Any ideas on this issue? Thanks

 

--

George Hester

________________________________

  • Replies 25
  • Created
  • Last Reply
Guest George Hester
Posted

Re: nasty assertion error

 

What is even more impressive I don't even have dbgheap.c on this machine

 

--

George Hester

________________________________

"George Hester" <hesterloli@hotmail.com> wrote in message news:eXNznvhyHHA.4276@TK2MSFTNGP05.phx.gbl...

Here it is

 

 

 

I tried to open Windows Media Player Classic. This isn't right. I am noticing that no media files open here although the correct codecx are installed. If I hit ignore I just keep getting these types of "Expressions." Any ideas on this issue? Thanks

 

--

George Hester

________________________________

Guest Sid Elbow
Posted

Re: nasty assertion error

 

I don't know if you inserted something after that "Here it is" but if

so, it sure didn't survive the trip to my machine.

 

 

George Hester wrote:

> Here it is

>

>

>

> I tried to open Windows Media Player Classic. This isn't right. I am noticing that no media files open here although the correct codecx are installed. If I hit ignore I just keep getting these types of "Expressions." Any ideas on this issue? Thanks

>

Guest Alex Blekhman
Posted

Re: nasty assertion error

 

"George Hester" wrote:

> I tried to open Windows Media Player Classic. This isn't

> right. I am noticing that no media files open here

> although the correct codecx are installed. If I hit

> ignore I just keep getting these types of "Expressions."

> Any ideas on this issue? Thanks

 

Why do you ask here? Ask developers of Media Player Classic.

Guest George Hester
Posted

Re: nasty assertion error

 

Really that is interesting. Are you viewing this newsgroup over the Web

interface? To explain this issue would have required alot of verbage and it

would really have been way over the top. Try to view the message with OEX

you will find if you set it up right it works quite well. Here is the

address for this newsgroup:

 

msnews.microsoft.com

 

--

George Hester

________________________________

"Sid Elbow" <mevagissey@gmail.com> wrote in message

news:25094$469f9a54$cef889ca$26929@TEKSAVVY.COM...

> I don't know if you inserted something after that "Here it is" but if

> so, it sure didn't survive the trip to my machine.

>

>

> George Hester wrote:

> > Here it is

> >

> >

> >

> > I tried to open Windows Media Player Classic. This isn't right. I am

noticing that no media files open here although the correct codecx are

installed. If I hit ignore I just keep getting these types of

"Expressions." Any ideas on this issue? Thanks

> >

Guest George Hester
Posted

Re: nasty assertion error

 

Hi Alex good point but something tells me this is going to happen with a

vaiety of applications on this machine. In other words this issue is not

restricted to just Windows Media Player Classic. It has to do with anything

which is going to try to access a .ax file at startup. You know when

Windows starts it accesses .ax files at startup also. Oh well when I find

my op sys disk I'll just redo this system just thought it was somewhat

interesting this error since there is no development software on this

system. But one thing that is interesting is I went to

http://www.microsoft.com/directx and just went quickly through the directx

for Window 2000 download and when it installed I nocticed it was installing

a piece of DirectxX SDK. I was wondering about that but just let it go.

I kind of think that is the problem since Windows Media Player Classic

didn't have this issue starting before that install. That install is not in

Add\Remove so I am stuck with it.

 

--

George Hester

________________________________

"Alex Blekhman" <tkfx.REMOVE@yahoo.com> wrote in message

news:uczhLCiyHHA.4712@TK2MSFTNGP04.phx.gbl...

> "George Hester" wrote:

> > I tried to open Windows Media Player Classic. This isn't

> > right. I am noticing that no media files open here

> > although the correct codecx are installed. If I hit

> > ignore I just keep getting these types of "Expressions."

> > Any ideas on this issue? Thanks

>

> Why do you ask here? Ask developers of Media Player Classic.

>

Guest Ben Voigt [C++ MVP]
Posted

Re: nasty assertion error

 

 

"George Hester" <hesterloli@hotmail.com> wrote in message

news:u3lqC$iyHHA.484@TK2MSFTNGP06.phx.gbl...

> Hi Alex good point but something tells me this is going to happen with a

> vaiety of applications on this machine. In other words this issue is not

> restricted to just Windows Media Player Classic. It has to do with

> anything

> which is going to try to access a .ax file at startup. You know when

> Windows starts it accesses .ax files at startup also. Oh well when I find

 

I wasn't aware of any such thing as a .ax file.... looks like a renamed DLL,

Dependency Walker opens it just fine. That might help you track down the

problem.

 

Also, have you tried disabling the various codecs (Device Manager -> Sound

and audio -> Audio Codecs -> Properties -> Properties tab) to see if a

particular one is causing the problem?

Guest George Hester
Posted

Re: nasty assertion error

 

Hi again. I wish to apologize to all and sundry to those that think I violated newsgroup etiquette with this post. I didn't mean to do that. It is probably because I have lost my W2K Network in a move to a new location everything seems to be falling apart here. I lost my domain controller and this client is now on the fritz. Seems only my XP clents survived the change in location. Again sorry to have taken frustration out here really I apologize.

 

--

George Hester

________________________________

"George Hester" <hesterloli@hotmail.com> wrote in message news:u7MLz1hyHHA.5964@TK2MSFTNGP04.phx.gbl...

What is even more impressive I don't even have dbgheap.c on this machine

 

--

George Hester

________________________________

"George Hester" <hesterloli@hotmail.com> wrote in message news:eXNznvhyHHA.4276@TK2MSFTNGP05.phx.gbl...

Here it is

 

 

 

I tried to open Windows Media Player Classic. This isn't right. I am noticing that no media files open here although the correct codecx are installed. If I hit ignore I just keep getting these types of "Expressions." Any ideas on this issue? Thanks

 

--

George Hester

________________________________

Guest George Hester
Posted

Re: nasty assertion error

 

Thanks for that avenue of attack here. I am going to see if I can find a

hole in this error using that advice. So far I been stuch trying to figure

out a highway to investigate this issue.

 

Maybe this issue is having [a] debug directx file in this system. I will

be looking at that also. Don't have Dependency Walker here but I think I

can find it on the Net.

 

--

George Hester

________________________________

"Ben Voigt [C++ MVP]" <rbv@nospam.nospam> wrote in message

news:#aGrNDjyHHA.1212@TK2MSFTNGP05.phx.gbl...

>

> "George Hester" <hesterloli@hotmail.com> wrote in message

> news:u3lqC$iyHHA.484@TK2MSFTNGP06.phx.gbl...

> > Hi Alex good point but something tells me this is going to happen with a

> > vaiety of applications on this machine. In other words this issue is

not

> > restricted to just Windows Media Player Classic. It has to do with

> > anything

> > which is going to try to access a .ax file at startup. You know when

> > Windows starts it accesses .ax files at startup also. Oh well when I

find

>

> I wasn't aware of any such thing as a .ax file.... looks like a renamed

DLL,

> Dependency Walker opens it just fine. That might help you track down the

> problem.

>

> Also, have you tried disabling the various codecs (Device Manager -> Sound

> and audio -> Audio Codecs -> Properties -> Properties tab) to see if a

> particular one is causing the problem?

>

>

Guest George Hester
Posted

Re: nasty assertion error

 

Hi Ben check this out:

 

 

 

I cannot run dxdiag anymore. Eerie. Yikes this op sys is dead eh? All I can do here is Abort. If I just keep hitting Ignore after a while dxdiag will quit and write an error log (Dr Watson?) but I don't know where that file is being placed. Haven't done the disabling of codecs yet but will.

 

--

George Hester

________________________________

"Ben Voigt [C++ MVP]" <rbv@nospam.nospam> wrote in message news:#aGrNDjyHHA.1212@TK2MSFTNGP05.phx.gbl...

>

> "George Hester" <hesterloli@hotmail.com> wrote in message

> news:u3lqC$iyHHA.484@TK2MSFTNGP06.phx.gbl...

> > Hi Alex good point but something tells me this is going to happen with a

> > vaiety of applications on this machine. In other words this issue is not

> > restricted to just Windows Media Player Classic. It has to do with

> > anything

> > which is going to try to access a .ax file at startup. You know when

> > Windows starts it accesses .ax files at startup also. Oh well when I find

>

> I wasn't aware of any such thing as a .ax file.... looks like a renamed DLL,

> Dependency Walker opens it just fine. That might help you track down the

> problem.

>

> Also, have you tried disabling the various codecs (Device Manager -> Sound

> and audio -> Audio Codecs -> Properties -> Properties tab) to see if a

> particular one is causing the problem?

>

>

Guest Sid Elbow
Posted

Re: nasty assertion error

 

No, I'm pulling it from regular nntp servers. If what you included was

an imbedded/attached graphic, it was probably stripped on the nntp

circuit since most servers don't allow such attachments in non-binary

groups (another netiquette problem I'm afraid).

 

George Hester wrote:

> Really that is interesting. Are you viewing this newsgroup over the Web

> interface? To explain this issue would have required alot of verbage and it

> would really have been way over the top. Try to view the message with OEX

> you will find if you set it up right it works quite well. Here is the

> address for this newsgroup:

>

> msnews.microsoft.com

>

> --

> George Hester

> ________________________________

> "Sid Elbow" <mevagissey@gmail.com> wrote in message

> news:25094$469f9a54$cef889ca$26929@TEKSAVVY.COM...

>> I don't know if you inserted something after that "Here it is" but if

>> so, it sure didn't survive the trip to my machine.

Guest Alex Blekhman
Posted

Re: nasty assertion error

 

"George Hester" wrote:

> Really that is interesting. Are you viewing this

> newsgroup over the Web

> interface? To explain this issue would have required alot

> of verbage and it

> would really have been way over the top. Try to view the

> message with OEX

> you will find if you set it up right it works quite well.

 

Usually people read (and write) Usenet posts in plain text.

Many of them have configured teir newsreaders to filter

attachments out, as well. Asking them to switch to HTML view

is considered impolite.

 

Most of the time developers already know about different

kinds of error message boxes. So, it's enogh to say that it

was "CRT assert message box" or whatever. Then just post

relevant part of it (like name of a function or source file

with number of a line).

 

However, if you need to post entire content of message box,

then press Ctrl+C when message box window is active. Then

press Ctrl+V in any text editor. You'll get full content of

the message box. Almost every MS product (including Windows)

supports this feature.

 

Alex

Guest Alex Blekhman
Posted

Re: nasty assertion error

 

"George Hester" wrote:

> [...] It has to do with anything

> which is going to try to access a .ax file at startup.

> You know when

> Windows starts it accesses .ax files at startup also.

 

It looks like installed codecs are all messed up. Sometimes

this happens when people install so called "codec packs".

These packs are usually prepared by amateurs and bring a lot

of outdated esoteric codecs, which cause instability. Not to

mention botched installations of these packs, which can do

all sorts of evil things.

 

Sometimes it helps to pinpoint codec problems with GSpot

utility (http://www.headbands.com/gspot/). You can open any

multimedia file and see what are the codecs involved, steps

of decoding process etc.

 

Alex

Guest Ben Voigt [C++ MVP]
Posted

Re: nasty assertion error

 

 

"George Hester" <hesterloli@hotmail.com> wrote in message

news:ecQ2BajyHHA.3908@TK2MSFTNGP05.phx.gbl...

Hi Ben check this out:

 

 

 

I cannot run dxdiag anymore. Eerie. Yikes this op sys is dead eh? All I

can do here is Abort. If I just keep hitting Ignore after a while dxdiag

will quit and write an error log (Dr Watson?) but I don't know where that

file is being placed. Haven't done the disabling of codecs yet but will.

 

 

http://www.dependencywalker.com

 

If you think one of the system dlls has been replaced by a debug version

that should help you find it. Especially try the profiling mode.

 

--

George Hester

________________________________

"Ben Voigt [C++ MVP]" <rbv@nospam.nospam> wrote in message

news:#aGrNDjyHHA.1212@TK2MSFTNGP05.phx.gbl...

>

> "George Hester" <hesterloli@hotmail.com> wrote in message

> news:u3lqC$iyHHA.484@TK2MSFTNGP06.phx.gbl...

> > Hi Alex good point but something tells me this is going to happen with a

> > vaiety of applications on this machine. In other words this issue is

> > not

> > restricted to just Windows Media Player Classic. It has to do with

> > anything

> > which is going to try to access a .ax file at startup. You know when

> > Windows starts it accesses .ax files at startup also. Oh well when I

> > find

>

> I wasn't aware of any such thing as a .ax file.... looks like a renamed

> DLL,

> Dependency Walker opens it just fine. That might help you track down the

> problem.

>

> Also, have you tried disabling the various codecs (Device Manager -> Sound

> and audio -> Audio Codecs -> Properties -> Properties tab) to see if a

> particular one is causing the problem?

>

>

Guest Sid Elbow
Posted

Re: nasty assertion error

 

Alex Blekhman wrote:

> Usually people read (and write) Usenet posts in plain text. Many of them

> have configured teir newsreaders to filter attachments out, as well.

 

Many (most?) nntp servers strip attachments in non-binary groups these

days. (In fact many don't carry binary groups either but that's another

story).

Guest Alex Blekhman
Posted

Re: nasty assertion error

 

"Sid Elbow" wrote:

> Many (most?) nntp servers strip attachments in non-binary

> groups these days. (In fact many don't carry binary groups

> either but that's another story).

 

I subscribed directly with "msnews.microsoft.com" server. I

can read HTML posts and see all attachments.

 

Alex

Guest Sid Elbow
Posted

Re: nasty assertion error

 

Alex Blekhman wrote:

> "Sid Elbow" wrote:

>> Many (most?) nntp servers strip attachments in non-binary groups these

>> days. (In fact many don't carry binary groups either but that's

>> another story).

>

> I subscribed directly with "msnews.microsoft.com" server. I can read

> HTML posts and see all attachments.

 

Great! It's nice to know there's at least one server that will do it :-)

Guest George Hester
Posted

Re: nasty assertion error

 

Right this ntp server does support graphics it is only your client that

keeps you from seeing the html and to be honest with you there is a time and

place when a picture speaks a thousand words and I really didn't want to do

all the writing. Now I posted it at a gif so that even a dial-up would have

no problem downloading the post. So I was considerate there I can only hope

that some people have the courtesy to grin and bear it. If not again I

apologize to all that don't want to enable the ability to read html posts.

The post itself would have been atrociously hard for me to explain the issue

mostly because I didn't even know what it was other than it's and error.

Writing I had the error would not have helped to explain the error since the

error itself is really not a good explanation what is happening. Haven't

you ever got an error and knew right off the bat the error was wrong?

 

Let me give you an example of such an error it is very easy to do. Remove

all NTFS security on the file tftp.exe in C:\WINNT\system32. It won't hurt

anything you can operate this way if you want and is really a good security

measure. Anyway install your Service Pack again. Of course if you have IE

6 in Windows 2000 DON'T DO THIS. Watch what happens. You will find your

service pach install fails because with error mesage tftp is being used.

WRONG. That is NOT the error. So you see my error is the similar to this.

 

I found out my DirectShow is now wasted because this is a Pentium 3 computer

and you can check out the article on it:

 

http://support.microsoft.com/kb/234620/en-us

 

Granted this is for Windows 98 but then look at this article:

 

http://support.microsoft.com/kb/183351/en-us

 

Notice it applies to IE 5.5 which is what I am using here. Notice the error

title in my picture says Visual C++ Debug Library. See that is why a

picture can speak a thousand words. The error itself is not giving us any

valid information it is the title of the MessageBox widow that is pertinent

here.

 

Anyway thanks for any help on this issue but it really looks like I hosed

this system trying to update its DirectX. Live and learn. I don't know how

I could have avoided this since the link at Microsoft leading to an update

for DirectX in Windows 2000 was wrong. It lead to a piece of the DirectX

SDK and therein is why I am in this predicament. I guess the moral of the

storry here is be careful trying to update products at Microsft that aren't

current products. Otherwise things like this can happen. Thanks.

 

--

George Hester

________________________________

"Sid Elbow" <mevagissey@gmail.com> wrote in message

news:73d9c$46a0b9f8$cef889ca$29173@TEKSAVVY.COM...

> Alex Blekhman wrote:

> > "Sid Elbow" wrote:

> >> Many (most?) nntp servers strip attachments in non-binary groups these

> >> days. (In fact many don't carry binary groups either but that's

> >> another story).

> >

> > I subscribed directly with "msnews.microsoft.com" server. I can read

> > HTML posts and see all attachments.

>

> Great! It's nice to know there's at least one server that will do it :-)

Guest George Hester
Posted

Re: nasty assertion error

 

Hi Ben. I am able to get dxdiag to work there are no debug dlls in the

system. What has happend is the DirectShow on my system has been corrupted.

The dxdiag will succeed if I answer Yes to a prompt I now get using it. As

it gets about three quarters done a box comes up that says I have a problem

with DirectShow do I want to continue without doing that test. If I day Yes

it completes. If I say No well you see the error I get.

 

--

George Hester

________________________________

"Ben Voigt [C++ MVP]" <rbv@nospam.nospam> wrote in message

news:O0BLW9kyHHA.748@TK2MSFTNGP04.phx.gbl...

>

> "George Hester" <hesterloli@hotmail.com> wrote in message

> news:ecQ2BajyHHA.3908@TK2MSFTNGP05.phx.gbl...

> Hi Ben check this out:

>

>

>

> I cannot run dxdiag anymore. Eerie. Yikes this op sys is dead eh? All I

> can do here is Abort. If I just keep hitting Ignore after a while dxdiag

> will quit and write an error log (Dr Watson?) but I don't know where that

> file is being placed. Haven't done the disabling of codecs yet but will.

>

>

> http://www.dependencywalker.com

>

> If you think one of the system dlls has been replaced by a debug version

> that should help you find it. Especially try the profiling mode.

>

> --

> George Hester

> ________________________________

> "Ben Voigt [C++ MVP]" <rbv@nospam.nospam> wrote in message

> news:#aGrNDjyHHA.1212@TK2MSFTNGP05.phx.gbl...

> >

> > "George Hester" <hesterloli@hotmail.com> wrote in message

> > news:u3lqC$iyHHA.484@TK2MSFTNGP06.phx.gbl...

> > > Hi Alex good point but something tells me this is going to happen with

a

> > > vaiety of applications on this machine. In other words this issue is

> > > not

> > > restricted to just Windows Media Player Classic. It has to do with

> > > anything

> > > which is going to try to access a .ax file at startup. You know when

> > > Windows starts it accesses .ax files at startup also. Oh well when I

> > > find

> >

> > I wasn't aware of any such thing as a .ax file.... looks like a renamed

> > DLL,

> > Dependency Walker opens it just fine. That might help you track down

the

> > problem.

> >

> > Also, have you tried disabling the various codecs (Device Manager ->

Sound

> > and audio -> Audio Codecs -> Properties -> Properties tab) to see if a

> > particular one is causing the problem?

> >

> >

>

>

Guest George Hester
Posted

Re: nasty assertion error

 

yes I know. Been there done that. But it wasn't codecs I installed it was

an update to DirectX I got at Microsoft that was the instigator of the

issue. Everything fine before it not all bad after the install. I can

still use Windows Media Player on mpgs usually and VLC Player on everything

else. Sucks but oh well thanks for your and Ben's help. It was the

suggestions here that lead me to what looks like the culprit here.

 

--

George Hester

________________________________

"Alex Blekhman" <tkfx.REMOVE@yahoo.com> wrote in message

news:O1l8D6kyHHA.1184@TK2MSFTNGP04.phx.gbl...

> "George Hester" wrote:

> > [...] It has to do with anything

> > which is going to try to access a .ax file at startup.

> > You know when

> > Windows starts it accesses .ax files at startup also.

>

> It looks like installed codecs are all messed up. Sometimes

> this happens when people install so called "codec packs".

> These packs are usually prepared by amateurs and bring a lot

> of outdated esoteric codecs, which cause instability. Not to

> mention botched installations of these packs, which can do

> all sorts of evil things.

>

> Sometimes it helps to pinpoint codec problems with GSpot

> utility (http://www.headbands.com/gspot/). You can open any

> multimedia file and see what are the codecs involved, steps

> of decoding process etc.

>

> Alex

>

Guest George Hester
Posted

Re: nasty assertion error

 

There is only one circuit if you are using msnews.microsoft.com. They do

not strip out the graphics. Normally ntp servers do not "strip" out

anything but the post itself. In other words ntp servers that do not

support binaries will just not "Serve" the entire post. But I guess some

can do that but that is not the case here. If you are usng

msnews.microsoft.com and NOT seeing the message than the issue is at your

client pretty sure about that. But absolutely sure msnews.microsoft.com

supports binaries as I can see the image.

 

--

George Hester

________________________________

"Sid Elbow" <mevagissey@gmail.com> wrote in message

news:e23cf$469fdd15$cef889ca$6969@TEKSAVVY.COM...

> No, I'm pulling it from regular nntp servers. If what you included was

> an imbedded/attached graphic, it was probably stripped on the nntp

> circuit since most servers don't allow such attachments in non-binary

> groups (another netiquette problem I'm afraid).

>

> George Hester wrote:

> > Really that is interesting. Are you viewing this newsgroup over the Web

> > interface? To explain this issue would have required alot of verbage

and it

> > would really have been way over the top. Try to view the message with

OEX

> > you will find if you set it up right it works quite well. Here is the

> > address for this newsgroup:

> >

> > msnews.microsoft.com

> >

> > --

> > George Hester

> > ________________________________

> > "Sid Elbow" <mevagissey@gmail.com> wrote in message

> > news:25094$469f9a54$cef889ca$26929@TEKSAVVY.COM...

> >> I don't know if you inserted something after that "Here it is" but if

> >> so, it sure didn't survive the trip to my machine.

Guest George Hester
Posted

Re: nasty assertion error

 

Hey I didn't know I could do that. Thanks heaps for that information.

Learn something new all the time. Let me try that and see if what you said

puts the title of the messagebox in...wowwee

 

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

Microsoft Visual C++ Debug Library

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

Debug Assertion Failed!

 

Program: C:\Program Files\Media Player Classic\mplayerc.exe

File: dbgheap.c

Line: 1044

 

Expression: _CrtIsValidHeapPointer(pUserData)

 

For information on how your program can cause an assertion

failure, see the Visual C++ documentation on asserts.

 

(Press Retry to debug the application)

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

Abort Retry Ignore

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

 

Nice one. I will do that in the future title of box is in there. Great man

you have made my day.

 

--

George Hester

________________________________

"Alex Blekhman" <tkfx.REMOVE@yahoo.com> wrote in message

news:uLAcx1kyHHA.1776@TK2MSFTNGP03.phx.gbl...

> "George Hester" wrote:

> > Really that is interesting. Are you viewing this

> > newsgroup over the Web

> > interface? To explain this issue would have required alot

> > of verbage and it

> > would really have been way over the top. Try to view the

> > message with OEX

> > you will find if you set it up right it works quite well.

>

> Usually people read (and write) Usenet posts in plain text.

> Many of them have configured teir newsreaders to filter

> attachments out, as well. Asking them to switch to HTML view

> is considered impolite.

>

> Most of the time developers already know about different

> kinds of error message boxes. So, it's enogh to say that it

> was "CRT assert message box" or whatever. Then just post

> relevant part of it (like name of a function or source file

> with number of a line).

>

> However, if you need to post entire content of message box,

> then press Ctrl+C when message box window is active. Then

> press Ctrl+V in any text editor. You'll get full content of

> the message box. Almost every MS product (including Windows)

> supports this feature.

>

> Alex

>

Guest Alex Blekhman
Posted

Re: nasty assertion error

 

"George Hester" wrote:

[...]

> Nice one. I will do that in the future title of box is in

> there.

 

Yes, it's a nice feature. Suicidal rate in MS support

department was extremely high before copyable message boxes

were introduced.

> Great man you have made my day.

 

You're welcome. :)

 

Alex

Guest Alex Blekhman
Posted

Re: nasty assertion error

 

"George Hester" wrote:

> [...] I can

> still use Windows Media Player on mpgs usually and VLC

> Player on everything

> else.

 

Yes, one of VLC's strengths is that it doesn't use anything

from the system. VLC has all its codecs embedded within a

player.

 

Alex

Guest Sid Elbow
Posted

Re: nasty assertion error

 

George Hester wrote:

> Right this ntp server does support graphics it is only your client

> that keeps you from seeing the html

 

 

 

I don't really want to prolong this but the Microsoft nntp server may

well support all kinds of things. But this is Usenet. People pull

messages in this group from any of a gazillion servers worldwide.

 

In fact, my reader does support html - it was my understanding that you

had attached a graphic file (or that you had embedded a graphic which

was seen as an attachment when your message was propagated through usenet).

 

The fact that you are adding a graphic, doesn't imply that any html is

involved. And actually, html messages are generally preferred on usenet

because of the possibility of embedding malicious code in html. Not that

that stops a lot of people and most servers will actually allow html.

But not graphics. No matter how useful they are in individual cases,

their unrestricted use simply takes up too much capacity on the nntp

servers.


×
×
  • Create New...