You got problems with my online dats and the www profiler since the last ztnet downtime (last view days)? You get a message like "No or bad online dat file..."...Then try this:

- quit clrmamepro
- delete the file 'wwwcache' in your cmpro main folder
- edit 'wwwdats.ini' and remove the timestamp data (after the second ';') for the clrmamepro side. (You can also remove the line completely but you have to resetup the clrmamepro side later then)
- start clrmame and go to the www profiler.

I just did the same and it redownloaded the file from my side and it works fine.

Let me know if you still got issues.

Of course check if you changed any firewall settings. The www profiler needs standard http port 80 transfer....


Roman Scherzer

I tried exactly what you proposed, still got the same issue. Even deleted both files completely and added the URL manually again in the WWW profiler. Did not help.
Checked my firewall settings and they are fine, and the same as ever, when WWW profiler still worked like a charm BTW.
Any idea what else I could try?

> I tried exactly what you proposed, still got the same issue. Even deleted both
> files completely and added the URL manually again in the WWW profiler. Did not
> help.
> Checked my firewall settings and they are fine, and the same as ever, when WWW
> profiler still worked like a charm BTW.
> Any idea what else I could try?
>


Hmm...weird. It could be possible that some ISP's proxy cache holds an invalid mamedats.zip....so this should get fixed within some time by itself. Today I uploaded a new one anyway because the mametitles datfile has been changed. Again I tried the update and it worked like a charm for me.

It may happen that the automatic transfer mode has chosen 'text' instead of 'binary' for the download and so the zip would be corrupt and the error appears.

I put an unzipped version of the xml online, try to use "http://www.clrmame.com/clrmame.xml" for the url string. I've also reuploaded the zip...maybe it works now ;)


Roman Scherzer

> Hmm...weird. It could be possible that some ISP's proxy cache holds an invalid
> mamedats.zip....so this should get fixed within some time by itself.

> It may happen that the automatic transfer mode has chosen 'text' instead of
> 'binary' for the download and so the zip would be corrupt and the error appears.

> I put an unzipped version of the xml online, try to use
> "http://www.clrmame.com/clrmame.xml" for the url string. I've also reuploaded
> the zip...maybe it works now ;)

Tried to use the URL for the unzipped version same problem as before.
I can download both the zipped and unzipped version by entering the URL in the browser without any problems. The XML in the zip file has today's date. So I would think that it is probably not a caching problem on the ISP's side.
I really don't understand it.

I have the same troubles as well... started like a week ago. Have tried all posted suggestions, no luck so far! :|

//CGA

>
> > Hmm...weird. It could be possible that some ISP's proxy cache holds an invalid
> > mamedats.zip....so this should get fixed within some time by itself.
>
> > It may happen that the automatic transfer mode has chosen 'text' instead of
> > 'binary' for the download and so the zip would be corrupt and the error
> appears.
>
> > I put an unzipped version of the xml online, try to use
> > "http://www.clrmame.com/clrmame.xml" for the url string. I've also reuploaded
> > the zip...maybe it works now ;)
>
> Tried to use the URL for the unzipped version same problem as before.
> I can download both the zipped and unzipped version by entering the URL in the
> browser without any problems. The XML in the zip file has today's date. So I
> would think that it is probably not a caching problem on the ISP's side.
> I really don't understand it.
>

If it's any consolation...I recently reformatted and reinstalled Windows XP Home on my machine, and am just now getting around to putting my MAME stuff back on the machine. From a clean install of the latest version of ClrMame, I am also experiencing the same problem. My wwwdata.ini file is a 0-byte file. I downloaded the datafiles separately and installed them in the "datfiles" directory, then tried again to use www mode, and got the same problem.

> I have the same troubles as well... started like a week ago. Have tried all
> posted suggestions, no luck so far! :|
>
> //CGA
>
> >
> > > Hmm...weird. It could be possible that some ISP's proxy cache holds an
> invalid
> > > mamedats.zip....so this should get fixed within some time by itself.
> >
> > > It may happen that the automatic transfer mode has chosen 'text' instead of
> > > 'binary' for the download and so the zip would be corrupt and the error
> > appears.
> >
> > > I put an unzipped version of the xml online, try to use
> > > "http://www.clrmame.com/clrmame.xml" for the url string. I've also
> reuploaded
> > > the zip...maybe it works now ;)
> >
> > Tried to use the URL for the unzipped version same problem as before.
> > I can download both the zipped and unzipped version by entering the URL in the
> > browser without any problems. The XML in the zip file has today's date. So I
> > would think that it is probably not a caching problem on the ISP's side.
> > I really don't understand it.
> >
>

> If it's any consolation...I recently reformatted and reinstalled Windows XP Home
> on my machine, and am just now getting around to putting my MAME stuff back on
> the machine. From a clean install of the latest version of ClrMame, I am also
> experiencing the same problem. My wwwdata.ini file is a 0-byte file. I
> downloaded the datafiles separately and installed them in the "datfiles"
> directory, then tried again to use www mode, and got the same problem.
>
> > I have the same troubles as well... started like a week ago. Have tried all
> > posted suggestions, no luck so far! :|
> >
> > //CGA
> >

Same here. My trusted old system reports a XML error, as does a new system I'm setting up from scratch. Is the latest datfile working for anyone?

It's the header in the file (first line). I played around with it, and by simply removing the first line

?xml version="1.0"? (Brackets removed because board filters them)

...it works.


> > If it's any consolation...I recently reformatted and reinstalled Windows XP
> Home
> > on my machine, and am just now getting around to putting my MAME stuff back on
> > the machine. From a clean install of the latest version of ClrMame, I am also
> > experiencing the same problem. My wwwdata.ini file is a 0-byte file. I
> > downloaded the datafiles separately and installed them in the "datfiles"
> > directory, then tried again to use www mode, and got the same problem.
> >
> > > I have the same troubles as well... started like a week ago. Have tried all
> > > posted suggestions, no luck so far! :|
> > >
> > > //CGA
> > >
>
> Same here. My trusted old system reports a XML error, as does a new system I'm
> setting up from scratch. Is the latest datfile working for anyone?
>

> It's the header in the file (first line). I played around with it, and by
> simply removing the first line
>
> ?xml version="1.0"? (Brackets removed because board filters them)
>
> ...it works.




Ooopsi...you're right 8) the xml header is only correctly parsed with the upcoming 3.90 version...which I already use. Ok...my mistake....sorry for the trouble. I've fixed the xml in the zip, you can use www.clrmame.com/mamedats.zip again....and before you ask....3.90 will come..hmm...either sunday night or within the next week...depends on how much time I got.


Roman Scherzer

Thx!
Works like a charm... :)

//CGA

> > It's the header in the file (first line). I played around with it, and by
> > simply removing the first line
> >
> > ?xml version="1.0"? (Brackets removed because board filters them)
> >
> > ...it works.
>
>
>
>
> Ooopsi...you're right 8) the xml header is only correctly parsed with the
> upcoming 3.90 version...which I already use. Ok...my mistake....sorry for the
> trouble. I've fixed the xml in the zip, you can use www.clrmame.com/mamedats.zip
> again....and before you ask....3.90 will come..hmm...either sunday night or
> within the next week...depends on how much time I got.
>
>
> Roman Scherzer
>

Thanks for the quick fix as always, Roman!

Thanks for fixing the problem, Roman! Works great again.