Sunday, January 9, 2011

Seagate GoFlex TV “Logon Failed”

goflex_tv_screen_320x340

I just recently got my hands on Seagate’s GoFlex TV. In combination with my existing 32” LG TV, this device would allow the playbacks of the movie files, in so many supported formats, from the USB storage device directly to my 1080p TV. This sounds very perfect to me as I often find it’s not very easy to turn on my desktop PC just to watch movies. The device comes with LAN adapter which allows it to connect to your home network, and view YouTube, Picasa, or playback from network’s shared folder. Moreover, to my surprise, it also supports USB keyboard! This was beyond my expectation.

Enough for the introduction.

Playing back from USB storage was fine and good, and it works nicely with my Buffalo portable HDD out of the box. The real pain kicks in when I tried to play my *.mkv file sitting on my Windows 7 PC’s shared folder. The GoFlex keeps asking for username and password which I entered numerous times over few hours, and without success. It keep showing “Logon Failed” message on the screen! This is pretty annoying.

Search from Google didn’t give much help, but the search on Seagate’s user forums itself revealed a thread containg instructions which fix the problem! Original post at http://forums.seagate.com/t5/FreeAgent-Theater/FREEAGENT-A-Guide-to-get-the-most-out-of-your-FAT/td-p/48382

WINDOWS 7, NETWORK PROBLEMS:

So, you have Windows 7, but you can't get your FAT+ to log on to the network.  Well here's some instructions to help you get around that:

 

First go to the Control Panel, then select Network & Sharing Center, then on the left pane select "Change advanced sharing settings".

  • Then select in the settings:
  • Turn on network discovery
  • Turn on file & printer sharing
  • Turn on sharing so anyone with network access can read & write files in the Public folders
  • on Media Streaming  (I'll come back to that)
  • Enable file sharing for devices that use 40 -or 56-bit encryption
  • Turn off password protected sharing
  • Now make sure you have the same setting for both Home or Work & Public profiles
  • For the Media Streaming, select "Chose media streaming options...",  the on the "Show devices on:" dropdown box select "All networks".  You should then see something that says "Unknown Device", make sure that it has "Allow" beside it.

 

IF that doesn't work, try this:

 

Click Start and type Regedit in the search and click Regedit.exe
Navigate to the following location in the registry editor.


HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa\

1. On the right side Double Click on everyoneincludesanonymous and in the window that pops up, change the value data from a 0 value to a 1

2. Double Click on NoLmHash and in the window that pops up, change the Value Data from a 1 value to a 0

3. Now navigate to the following location in the registry editor
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanManServer\Parameters


Double Click on restrictnullsessaccess and change the 1 value to a 0

Reboot your pc and you should now be able to connect to your pc from you Freeagent Theater+

This works for me, I also have my drives shared with full access on my LAN

You will still see the Login screen  just click OK and you should have access to your drives.

(Originally submited by ColinK)

This should also work with Vista.

Here a link for WINDOWS XP network problems.  (Give a few Kudos to bodhi78 for this one)

This took so much time from me that I would like to share this with other GoFlex TV users. I lived happily, enjoyed 1080p, the last 12 hours ever since the fix :)

Thursday, May 28, 2009

DLL problem with Wise Installation System and 8.3 filenames

This is from one the action item I deal with at the workplace. The user can install our software but when he tried to use one of the functions, the Visual Basic 6.0 application shows a message box indicating “Automation error.” This is a well-known Windows DLL problem which can be fixed easily using regsvr32 MyDLL.dll command. But I have to dig into the reason why the installer can’t get it job done correctly on the customer’s machine.

From what I known, the installer is created with Wise Installation System. I don’t know the precise version the development team used. But there is a known issue floating around the internet about the installer’s incompatibility problem with systems that disabled the generation of 8.3 filename.

I tried to reproduce the problem at work. The steps started with fresh installation of Windows Server 2003 and running fsutil behavior set disable8dot3 1 command. You can also check the current value of disable8dot3 by fsutil behavior query disable8dot3.The important thing to note that you have to restart the machine once for this changes to make effect.

After that, I installed the product. And the problem is reproduced! The fix is easy. Just uninstall the software, set disable8dot3 option to 0, restart, reinstall, and everything works!

The disable8dot3 option is set to 0 on a default installation of Windows. But there is a well-known tweak to disable this 8.3 name generation to improve directory browsing performance. This would break the Wise installer from working correctly.

I can’t reproduce the issue in the first place because I don’t know I have to restart the machine :(

Tuesday, March 17, 2009

.NET Parallel Computation Made Easy : System.Threading.Parallel

I had conduct a simple experiment for some time ago. It's about the performance of .NET program running on a multi-core processor versus the same program running on the single-core one. The result from my experiment shows that if you have a normal .NET program implemented without multi-threading, there will be no significant performance difference between running it on multi-core and single-core system.

I found it hard to create a multi-thread version of my classic old "Prime Generator" program. The hardest part is I don't know the appropiate number of thread to create since I had no information about the system the program is runnning on. And the threading code just looks ugly .. developers with no multi-threading background will find it hard to understand and maintain. Take my old code for example.


The Rescue
This is where Microsoft Parallel Extensions to .NET Framework 3.5 comes in handy. It simplify the process of constructing the multithread code yourself. There are many useful stuffs under System.Threading.Parallel. But I find System.Threading.Parallel.For is the easiest to understand and utilize :)


Here is the plotting between the data set size and time used in millisecond on my machine with Intel(R) Core(TM)2 Duo CPU E6750 @ 2.66GHz. The System.Thread.Parallel.For actually takes extra computation time on the first call which makes me wonder why an ordinary for-loop outperforms parallel version at very first version of my benchmark. However, after the first call, the parallel version outperforms ordinary for-loop as expected.

I believe the results will be different on a quad core machine too :)


Hope this helps.