a9 Unable to scan networked drives?

signe

11-03-2010 05:53:14

My scan directories are both on remote servers (my torrents and HTPC are different systems), but immediately upon loading a9, scanning always says "T:\Television is unavailable". The message is inaccurate, of course, because I can simultaneously browse the directory and the connection's working fine.

sstteevvee

11-03-2010 10:21:01

I'm using it with mapped paths, without any problems. What is the full path name of one of your show folders?

When scanning says it is unavailable, is that an error dialog that is coming up, or something else? (can you easily take a screenshot?)

rip

12-03-2010 06:18:17

I'm using TVrename with mapped paths on a remote drive (i.e. remote D: is shared, and another disk is path mapped on the remote to D:\SERIES; I've mounted the remote D: to local Y:) and both a7 and a9 crash if I add Y:\SERIES to the search folders list in options. The crash report I get is:

Fault bucket 1034033670, type 5
Event Name: CLR20r3
Response: Not available
Cab Id: 0

Problem signature:
P1: tvrename.exe
P2: 1.0.0.0
P3: 4b9777cd
P4: mscorlib
P5: 2.0.0.0
P6: 4a27471d
P7: 349e
P8: 9a
P9: System.IO.IOException
P10:



I can normally scan the Y:\SERIES and add TV shows etc, but as long as this path is not being searched for missing episodes. Any ideas?
K

signe

12-03-2010 14:12:57

It just gave me the standard unavailable error, same as if you put in a path that doesn't exist.

It didn't work yesterday, either, but when I gave it a try now, it worked fine. Bah, I say. Bah.

sstteevvee

12-03-2010 15:19:41

Bah indeed. :)

I know that when Windows first boots up, it "reconnects" network drives.. but they're not really totally reconnected. If you look at them in My Computer, they'll have a small red "X" on their icon, and stay that way until you go into them in explorer. While they have the red X, TVRename won't be able to use them. Other programs have this problem, too (e.g. WInamp). I'm not sure if there is an easy way for TVRename to force a real reconnection, either.

signe

13-03-2010 17:07:41

In my case, it definitely wasn't bootup. I was running A7, ran a scan, exited, installed A9, ran a scan. Failed consistently for 24 hours, even while I was browsing the "inaccessible" folder, but... it's working now. Who knows.

rip

13-03-2010 19:46:06

Mine is not bootup as well. I can normally work with shares, but only if a shared folder that is a mapped path is not listed in search folder list. Could someone try and reproduce my error?

on a remote machine:
map a drive to a folder on another drive (e.g. map hdd2 to D:\SERIES on hdd1 without defining drive letter for hdd2)
share hdd1 (e.g. D:\)

on a local machine:
assign network drive to a shared remote drive (e.g. assign Y:\ to networked drive)
start tvrename, go to options
insert Y:\SERIES to the list of search folders
scan series

thanks!