How to use iView (ABC Australia) downloaders

[RvG]

No problems watching ABC videos on line.

I run XP 32bit SP3.

[Anywho]

Originally Posted by RvG

No problems watching ABC videos on line.

I run XP 32bit SP3.

It's starting to sound like a firewall or "internet security program" that is not allowing iViewNapper.exe access to the internet. Have you got anything like that running on both machines that would do that?

[RvG]

I run an AVG Firewall but don't think that is the problem.

Just tested with the firewall turned off, same result. And don't forget that SBSnapper is running fine.
What happens with the AVG fire wall is that if a program wants to access the internet, it comes up with a window where you have to give the software permission to access the internet. It doesn't reach that stage before the error message shows up.

[Anywho]

Originally Posted by RvG

don't forget that SBSnapper is running fine.

Irrelevant. iViewNapper and SBSnapper are totally different programs. They each do things differently.

Try this...

1. Download a fresh copy of iViewNapper.
2. Install it in another directory inside your "My Documents" folder.
3. Rename the fresh copy of iViewNapper to "Napper".
4. Disable your firewall.
5. Try the "new" Napper.

Did that work? If it does, then rename the "Napper" back to "iViewNapper". Still working?

If the above doesn't work, then:
1. Turn on your firewall
2. You're screwed

[RvG]

OK, installed a fresh copy in a new directory.
Turned off the firewall and it went through!

Turn firewall back on, stuck again.

Now, what is odd is that when I add Napper.exe to the firewall with full permissions, it still hangs.

Not real keen on turning off my firewall, what is causing this problem?
And why didn't I have this problem with older versions of IviewNapper?

[pcspeak]

Hi.
Maybe come at it from the other direction?
Turn off your modem.
Uninstall AVG.
Delete any files/folders belonging to AVG.
Run TWO registry cleaners over your system.
Set up iViewNapper again.
Reinstall a clean AVG.
Turn on the modem.
Let AVG update.
Try iViewNapper.

[Yansky]

Originally Posted by RvG

OK, installed a fresh copy in a new directory.
Turned off the firewall and it went through!

Turn firewall back on, stuck again.

Now, what is odd is that when I add Napper.exe to the firewall with full permissions, it still hangs.

Not real keen on turning off my firewall, what is causing this problem?
And why didn't I have this problem with older versions of IviewNapper?

You might have to open a port for rtmpdump. I don't remember the port number offhand. Anywho prolly knows.

Edit: wikipedia says it's port 1935
http://en.wikipedia.org/wiki/Real_Ti...aging_Protocol

[RvG]

Originally Posted by Yansky

You might have to open a port for rtmpdump. I don't remember the port number offhand. Anywho prolly knows.

Edit: wikipedia says it's port 1935
http://en.wikipedia.org/wiki/Real_Ti...aging_Protocol

Thank you for that suggestion but at the moment I don't even get to RTMP....
Current workaround I use is:
1 - Turn off firewall
2 - Start iViewNapper
3 - Once a link is established, turn firewall back on
Somehow that allows me to run iViewNapper behind my firewall and download the files I want.

[assy]

Hi.
I know this forum is for the iview, but is anyone having problems with the SBSnapper? I am getting a message "cannot open channel 94" when I try to run it.

I understand that there was a virus at SBS, do we have to wait until they fix that? Or should we be doing something else to fix our "napper"?

Thanks

[blood.eaglz]

Well a check with the sbs site shows that they are streaming their shows though apppears they are delayed in starting, but all else looks normal the channel data is still at http://player.sbs.com.au/video/playl.../standalone/94 as far as I can tell the xml structure hasn't changed, so it looks like a server issue or they've altered their security blocking the napper as is (new port or new check in swf, etc).

Anywho, mce or the others with better knowledge than me will be able to tell for sure, my best guess at the moment is on a server issue choking the retrieval of the xml data