FreeAgent Theater and GoFlexTV

[prairiedog]

---

randomgal wrote: 

also, i saw somewhere that some files have to be removed from hdd after it was first connected to fat+ otherwise they intervene somehow; i can't find the tread

---

If you attach the hdd to a computer and browse to it, you will see a .theater folder there.  This is an index of the movies on the drive created by the FAT+.  There have been reported issues where the hdd is not recognized, or all the movies are not listed, and this can be resolved by deleting that folder from a pc and reattaching the drive to the FAT.  Then let it reindex.  Probably a good thing to do every once in a while after you add/remove movies from the drive.

[ancaster]

Somehow related to the last post. If the external drive is an ext2/ext3 formatted one, the FAT+ mounts it as RO (read only). In this case, Ι do not think the .theater file can be created. I have not seen any problems with that yet. It may take some longer time every time the drive is connected, because it will try to re-index it again (if it were smarter, it should bypass that step) and the movie listing will be empty, but I do not use that one, anyway. I go through the folders usually. 

(Having said that, one may be able to create that same file by oneself)

[randomgal]

---

prairiedog wrote:

If you attach the hdd to a computer and browse to it, you will see a .theater folder there.  This is an index of the movies on the drive created by the FAT+.  There have been reported issues where the hdd is not recognized, or all the movies are not listed, and this can be resolved by deleting that folder from a pc and reattaching the drive to the FAT.  Then let it reindex.  Probably a good thing to do every once in a while after you add/remove movies from the drive.

---

right, i remember seeing this folder thru my pc.

I normally acces my library via folders just like ancaster does. I didn't have any problems with fat+ recognizing hdd, but I'll keep it in mind, i also remember seen something that looked as a recycle bin, does it need to be removed or just cleaned?

Speaking of this index folder on hdd : somehow my xbox refused reading from this same hdd once; i can bet i didn't have this problem before, i attached it only once or twice before; i haven't tried again since and currently access my library on pc from xbox thru a network; nevertheless, i just think it might be that  this index folder created on hdd by fat+ somehow prevents xbox from reading from hdd. xbox is ok and I eliminated the possibility of a cable issue; it just stopped reading from this hdd, not a big deal , just curious if this folder might be the reason.

[bodhi78]

---

randomgal wrote:

---

Speaking of this index folder on hdd : somehow my xbox refused reading from this same hdd once; i can bet i didn't have this problem before, i attached it only once or twice before; i haven't tried again since and currently access my library on pc from xbox thru a network; nevertheless, i just think it might be that  this index folder created on hdd by fat+ somehow prevents xbox from reading from hdd. xbox is ok and I eliminated the possibility of a cable issue; it just stopped reading from this hdd, not a big deal , just curious if this folder might be the reason.

---

If other PCs do not recognize it, or have problem with it, then It's likely there are some files cross-indexed (caused by the FAT+) and need to be fixed. If you have Windows, plug it in to the Windows PC. Win 7 will detect it and tell you to fix the errors. Win XP ignore it until you run Error Checking.

[randomgal]

---

ancaster wrote:

Somehow related to the last post. If the external drive is an ext2/ext3 formatted one, the FAT+ mounts it as RO (read only). In this case, Ι do not think the .theater file can be created. I have not seen any problems with that yet. It may take some longer time every time the drive is connected, because it will try to re-index it again (if it were smarter, it should bypass that step) and the movie listing will be empty, but I do not use that one, anyway. I go through the folders usually. 

(Having said that, one may be able to create that same file by oneself)

---

my pc had tried to index hdd whenever i attached it, then i found how to stop that;

my movie listing is full of fragmented rubbish that's probably sitting in hdd's garbage bin; i have to really look into it; i don't see this "bin" from my pc;

i guess i have to work with hdd's properties to see it, or should this be a pc's properties that responsible for hidden files and folders including those on hdd?

[randomgal]

---

bodhi78 wrote:

If other PCs do not recognize it, or have problem with it, then It's likely there are some files cross-indexed (caused by the FAT+) and need to be fixed. If you have Windows, plug it in to the Windows PC. Win 7 will detect it and tell you to fix the errors. Win XP ignore it until you run Error Checking.

---

my pc recognizes hdd just fine, it's the xbox that doesn't (stopped). It just doesn't see it anymore, like nothing's attached.I have windows vista and so far it didn't show any error messages related to hdd whenever i attach it.

I wonder whether that happend after one of xbox updates or fat+ "footprint".

[flacnvinyl]

Let me clarify a few things about my setup. First off, I am not using rechargeable batteries. Brand new energizer industrial strength batteries. Also tried other brands, no change. Secondly, this is not a hard drive issue. I am not using a drive. Was only using it to stream movies from my server. Worked fine until this crud. lastly, I am using the most current firmware. Did the cold update method, changed nothing. So what's the next step? How do I get hold of seagate to fix this thing? At this point I am seriously regretting selling my modded xbox. Xbmc or boxeebox are both looking very pleasant again.

[prairiedog]

Hi Flac,

I dont' know how many more solutions are available to you - still trying to narrow down a software or hardware issue.  The only thing I could see you doing at this point is trying the 1.55 rescue firmware, you have already went down the traditional avenues.  However, I am unclear if you can do this, per this thread.  Can someone help out here?  Would it be worth a try to flash the rescue then flash 1.55 standard? I am assuming Flac is using 2.20 now per his posts.

This all for naught if it's a hardware issue.  Then you would need to obtain a replacement remote OR a new FAT, depending on which hardware is broken.

At the same time, I would recommend sending Alan a PM and asking him directly what Seagate can do, short of calling their customer support.  Hopefully he has just been lurking here, but it's been a while since he has posted.  Alan, are you there!? 

thanks for bringing your topic back on topic

[flacnvinyl]

I apologize, who is Alan?

[prairiedog]

He's a Seagate rep - forum moderator.  He is still posting, just not in the FAT forum.

Your device is out of warranty, right?

I was thinking, since I have 4 FAT's and one of them I use a Harmony remote with, I could send you a remote to see if it was that.  May be quicker than waiting on Seagate.