The Official "ZTNet Sucks" Thread
Moderators: mahlemiut, seymour, QRS
I should have said that MARP scripts were run on a seperate server.
There has been a problem with hung scripts in the past, but these usually only stop database related scripts from working. Although I do see that the news script (http://marp.retrogames.com/news.cgi) is still working.
I have noticed that Zwaxy had logged on to the server at some point this morning, so I presume that he is aware of the problem too. It's a wonder ZTNet hasn't noticed yet, either.
There has been a problem with hung scripts in the past, but these usually only stop database related scripts from working. Although I do see that the news script (http://marp.retrogames.com/news.cgi) is still working.
I have noticed that Zwaxy had logged on to the server at some point this morning, so I presume that he is aware of the problem too. It's a wonder ZTNet hasn't noticed yet, either.
- Barry Rodewald
MARP Assistant Web Maintainer

MARP Assistant Web Maintainer

Go to:diabolik wrote:I'll try that.Try a different ISPWhat do you mean by this? Can you give any instructions?or going through babelfish?
http://babelfish.altavista.com/tr
type http://marp.retrogames.com
in the "translate this webpage" box.
Choose to translate Japanese to English. Since it won't find any Japanese on the site, it will keep the english almost intact. If babelfish (or any other proxy) can hit it, the problem is probably with your DNS .
Also: try adding the line:
Code: Select all
64.237.35.231 marp.retrogames.com
c:\windows\hosts
If XP:
c:\windows\system32\drivers\etc\hosts
John Cunningham (JTC)


Thanks. I can connect through babelfish. I'll contact my ISP and ask them what's going on.
Didn't help.Also: try adding the line:to your hostfile.Code: Select all
64.237.35.231 marp.retrogames.com
- destructor
- MARPaholic
- Posts: 1972
- Joined: Fri Sep 20, 2002 9:38 am
- Location: Poland
Fixed.
For whatever reason, the pre-compiled Python scripts become incompatible and unable to run. It's fixed by simply deleting them, forcing the system to re-compile them the next time they are run. This is something that might occur when Python is updated, but it's not something that should happen as often as it does.
For whatever reason, the pre-compiled Python scripts become incompatible and unable to run. It's fixed by simply deleting them, forcing the system to re-compile them the next time they are run. This is something that might occur when Python is updated, but it's not something that should happen as often as it does.
- Barry Rodewald
MARP Assistant Web Maintainer

MARP Assistant Web Maintainer
