Blog

My girlfriend has one of these, ethernet-connected to her router and thus available on her home network.  However, in order for any computer, Windows or Mac (what about linux?) to access it, it is necessary (aside from any hacky-workarounds that may possibly exist) to install the Iomega Home Storage Manager.   This makes volume(s) offered by the NAS appear, on the Mac in Finder under SHARED, or on a Windows machine as additional drive letter(s).

To acquire the Iomega Home Storage Manager, go to https://iomega-eu-en.custhelp.com/app/platform/p/1031,1043 or else try https://iomega-eu-en.custhelp.com/ and click on [Desktop Network Storage > Home Media Network Hard Drive].  May need to establish and login-to an iomega support account (free) first.

I wondered at first about enabling the NAS as a Mac OS Time Machine (backup) disk.  An iomega article I saw suggested that should be possible, for iomega firmware 2.0 and above.  But the disk as it stands is NTFS-formatted - because when it was set up we had only Windows machines.  Now that disk contains much material in that NTFS.  I guess it might be possible to partrition the disk e.g. to keep the existing NTFS and add alongside it a HFS+ partition for Time Machine to use.  But it’s guesswork that carries risks (of disruption/damage to existing contents).  We want an easy geeking-minimal life, so maybe better to repurpose that NAS and get a purpose-made Apple Time Capsule instead. Either way, the evening wears on, so I’ll shelve that idea/investigation for now…

(more…)

Following-on from my earlier post, Mobile Video Editing Hardware: Thoughts, Ideas & Dreams, where I considered an eventual migration from my laptop to a luggable PC, my thoughts veered (possibly having spotted cash-icebergs among them) towards an alternative solution:

• Use the laptop for lightweight editing & compositing.
• Use the desktop as a number-crunching RADI-attached server.

The two could be linked by:

• Remote access / remote sessions (some of which via smartphone)
• DropBox, e.g. have an active folder where I can drop Adobe Premiere XML and have it processed remotely by Adobe apps installed there.

Some links:

• http://www.theregister.co.uk/2012/01/11/virtualisation_at_home_part_2/
  • (There’s no equivalent “_part_1″ page.  I guess it’s just “Part 2″ of that guy’s story).
  • DIY virtual machines: Rigging up at home, by Trevor Pott, 11th January 2012 14:33 GMT
  • Personal Virtual Machine (PVM) (in use) for about seven years with retail boxed version of Windows XP.
  • VM has been moved from virtualization platform to virtualization platform over the years … the most recent incarnation … inside Hyper-V.
  • …nothing beats Windows Server 2008 R2. It comes with a top-notch virtualisation platform (Hyper-V), and added RemoteFX support with Service Pack 1. You can still use the desktop operating system for all your HTPC needs, and a single Server 2008 R2 Standard license allows you to run both a host copy and a single virtual instance of Server 2008 R2.
  • In my case, the host instance does little more than play movies on the projector via VLC. The virtual instance of Server runs my Plex media server, and aggregates my many storage devices into a single share using DFS.
    • Presumably “DFS” refers to Microsoft’s Distributed File System.
• Shuttle Inc (Taiwan)
  • (MBR’s suggestion)
  • http://uk.shuttle.com/products/productsDetail?productId=1477
    • Small, quiet, hardware-configurable systems.
    • May be a sensible basis for a modular luggable?
  • http://www.okobe.co.uk/ws/product/Shuttle+SH67H3+Barebones+Personal+Computer+FH67+Socket+1155+Intel+H67+Black/1000065737?ref=1q4bs
    • Shuttle SH67H3 Barebones Personal Computer (FH67 Socket 1155 Intel H67) (Black)

Want a mobile “suitcase” editing system, something more (and more expandable) than a laptop but not too expensive.  Primarily to be used for Adobe CS5.5 for media enhancement / editing / compositing etc.

Nearest I found was NextDimension’s range around $7000 I think (but just guesswork - could be way off - would need to get a quote).   That would (if true) be around £4500 at current rates.  Plus import…  NextDimension call such machines “flextops” (Maybe they coined the term? Google searches on it mostly come up with them.)

Apart from the (mil/broadcast-lite but me-heavy) price, it might possibly be undesirably heavy to lug around much.   If so (just guessing, not assuming), it would make more sense to go for a modular quick-setup system.  So, starting to “think different” in this direction:

• Standard tower, capable of taking new CUDA etc. graphics cards etc. as they emerge, but no need for more than say a couple of disks, maybe if SSD could even get away with just a single disk? (For system and media - inadvisable for traditional disks of course, what about for SSD’s?  I have much to learn about SSD’s though).
• “Laptop-Lite” to talk to it.  With robust shuttered-stereoscopic HD monitor.
• Gigabit network to NAS fast storage (SSD and/or RAID ?).

Maybe in that case it would be far more logical/affordable to use an existing laptop as a client working together with a luggable tower server, sufficiently light and robust for frequent dis/re -connection and travel.  And remote access of course (no heavy data to be exchanged, assume that’s already sync’d).  And some means to easily swap/sync applications and projects (data) between laptop and tower, giving the option to use just the (old) laptop on its own if needed.  All such options are handy for the travelling dude (working on train, social visits etc.) who also occasionally has to do heavy processing.  Then would just need a protective suitcase for the tower, plus another one for a decent monitor for grading etc.

I certainly won’t be spending anything just yet, but it’s good to have at least some kind of “radar”.

(more…)

This is a problem I encountered some time ago, when I was running Boot Camp v3.1 on my MacBook Pro.  Since then I upgraded to v3.2.  I know there’s a v3.3 around but before upgrading I thought it worthwhile to see whether v3.2 had fixed that problem (especially since I couldn’t rule out the possibility of v3.3 reintroducing it).   Only one thing to do: prevaricate test.

• Copy file from GRaid Mini (GRm) to Desktop:
  • 2GB fine
  • 12GB appears ok initially but then fails (to zero b/s transfer rate, then the Grm device “no longer exists”, at least until reboot)
• Reverse: 2GB fails (same way) almost immediately.

OK not good thus far…

Next tried an alternative approach: run W7 as a Virtual Machine on Mac Os via Parallel.  I have Parallels v6.  Forum search revealed that there is no FW support in either v6 or v7, though the developers seem interested in knowing why people want it.

• 2GB GRm to W7 Desktop: ok
• The reverse: ok.

Had to stop there due to other work - and a very full W7 disk.

The next workaround to consider is attaching a NAS.  Ethernet bandwidths can be 1Gbps, hence more than FW800’s 0.8 Gbps, though I wonder if there could be any issues of lag / latency in this approach.  I’ll do some research and put up another post about this idea.

Just for the record, currently this works:

• On Mac Pro, in Windows (XP):
  • Choose any folder. For example:
    • On the RAID, this could be either of the two partitions:
      • NTFS_RAID (an NTFS partition)
      • RAID_ProAVIO (an HFS+) partition
  • Then [RtClk > Sharing and Security… > Sharing > Network sharing and security:
    • Share this folder on the network: YES
    • Allow network users to change my files: YES
      • Because some tools create “sidecar” files e.g. audio peaks or video indexes.
• On Mac Book, in Windows 7:
  • From a file-browser, be it Windows Explorer or part of the File>Open feature of an application, go to [ Network > aComputer > aFolder ]
    • Tested by playing file in Windows Media Player and in Sony Vegas (video NLE).  Worked fine.  Latter added a [.sfk] sidecar-file to the RAID-folder.
    • Worked both for source on NTFS partition and for source on HFS+ partition, except the latter gave rise to prolonged “hourglass” delays before the file was accessed/linked, following which the video played smoothly.
• What doesn’t work:
  • Unable to see Mac Book from Mac Pro.
  • Also, when MacPro is in Mac OS, MacBook W7 Windows Explorer > Network lists the MacPro as [MACPRO-2E4124] yet cannot connect to it, blaming a firewall (presumably the one on MacPro).
    • Network Error: Windows cannot access \\MACPRO-2E4124
    • Tried exiting Kapersky (on the MacPro>MacOS) but no change.
    • Tried stopping MacPro firewall (via Preferences > Security) but no change.

http://meanderingpassage.com/2007/07/18/how-to-installing-an-airport-extreme-card-in-an-intel-mac-pro/

Here, I set up a home network.  <<Actually this happened about a year ago but only just publishing it now>>.  Already I have a small bunch of machines (of various ages) linked either physically (ethernet cable) or wirelessly (WiFi) to a WiFi router-modem onto ADSL.  Currently these machines simply use that arrangeent for their own individual internet access.  What I want to do is enable some resource-sharing, in particular onto a WiFi hub to be connected to a printer and a hard disk, but also to allow (temporary) access between machines for occasional ad hoc file transfers.

• First, ensure all PCs have easily identifiable names and belong to the same Workgroup (the typical method is to leave this at default i.e. “WORKGROUP” but note that XP’s Network Wizard defaults instead to “MSHOME”).
  • For XP:
    • From [http://windows.microsoft.com/en-US/windows7/Add-a-device-or-computer-to-a-network]
      • Log on to the computer as an administrator.
      • Click Start, right-click My Computer, and then click Properties.
      • Click the Computer Name tab, and then click Change.
      • If the workgroup name is not WORKGROUP, change the name to WORKGROUP, and then click OK. Otherwise, click Cancel to close the Computer Name Changes dialog box.
      • If you have to change the workgroup name, you will be prompted to restart your computer.

• Next, established whether TCP/IP communication was working OK:
  • Gathered a small bunch of computers together for testing.
  • From CMD, obtain IP numbers of each computer.
  • From each computer, try pinging each of the others.
    • Initially had some problems here:
      • None of the Windows computers were pingable from any other computer, but that the non-work Windows computers could ping the MacBook Pro.
      • The work Windows computer was unable to ping anything.
      • On the other hand, they could all ping certain external internet sites e.g. www.grc.com.  Some others, such as CNN, reject pings (as possible attacks).
      • The problem was in the Firewalls.
        • Initially tried the crude solution of disabling the software firewalls.
          • Still protected by router firewall. A grc.com test showed all was still well.
          • Nevertheless, looked for a more finely-tuned solution…
        • Old Compaq: Disabled Windows Firewall.  Now it was pingable.  Re-Enabled Windows Firewall.  It was still pingable.  Maybe I succeede in unblocking something?
        • Newer desktop with Kapersky: [Firewall > Filtration System > Zones > Settings]
          • Delete duplicate entry for 192.168.0.0, then for the remaining such entry, set it to Local Network (default was Internet)and disable Stealth mode.
          • OK or APPLY the whole settings panel, else the settings don’t take effect.
          • Got the idea from [http://forum.kaspersky.com/index.php?showtopic=80725]
          • Some other good ideas, not required here, were at [http://forums.speedguide.net/showthread.php?t=190294] and [http://www.velocityreviews.com/forums/t363292-cannot-ping-local-ip-address.html] and [http://support.microsoft.com/kb/308007], the latter pointed out that the Guest account needed to be enabled also.
    • Now the pings worked OK.
• On PCs, in Windows Explorer, check out My Network Places to see if the other machine showed up.
  • Desktop: My Network Places > SharedDocs on OldCompaq
  • OldCompaq: My Network Places > Entire Network > Microsoft Windows Network > Workgroup
    • It could see itself and the other machine.
    • However the other machine required a password.  What password?
      • Solution: re-run the Network Wizard on the Desktop, this time (unlike before), enable File & Printer Sharing.  Now it worked fine.
• Also the PCs were visible on a Mac.
  • Mac: Finder > Shared
• Now to make the Mac share to the PCs:
  • Enable Windows Sharing on macintosh.
    • http://articles.techrepublic.com.com/5100-10878_11-6127492.html
• Finally, looking at Windows 7 as a Virtual Machine under Parallels 5 on a Mac:
  • Its default WorkGroup name is WORKGROUP, hence it sees the other machines OK.  And it can access their shared folders.  But those machines cannot see its files.  Solving this problem does not seem so trivial, so I will work on it later and post its solution separately.

D-Link’s gigabit router, 802.11n (”up to 14x faster speeds* and 6x farther range* than 802.11g while staying backward compatible with 802.11g devices”):

• http://www.dlink.com/products/?pid=530

Can use Wester Digital’s MyBook drive on a network featuring multiple OSs, such as Mac OS as well as Windows, provided one does not install MioNet (bundled with the drive).  My instincts were right then (I did not install it).

• http://raoulpop.com/2007/06/25/hardware-review-wd-my-book-world-edition-ii/
• http://forums.macrumors.com/archive/index.php/t/t-300586.html (which references the above)

In my case, the drive is formatted as NTFS, on a Mac it simply appears automatically in Finder then Mac OS is able to read it (Mac OS is able to read NTFS).  In retrospect, maybe would have been better to format it as HFS+ since then Windows could use MacDrive to not only read but write to it.  Meanwhile on Windows I found it necessary to run the “Discover” application bundled with MyBook, which configures the network drive mapping (to a drive letter).

Need to establish a better home network, e.g. so Parallels on my Mac can see my Windows laptop, so it can suck the XP out of it.  Also want shared printer etc. (I have a node for that).   Just a question of setting it all up…