15/Apr/2010 PA
12/Apr/2009 Sunrise Circus
15/Mar/2009 Lego
08/Mar/2009 Moomba
13/Feb/2009 Car Smokey Sunset
26/Jan/2009 Fireworks
26/Oct/2008 Synchrotron
07/Jun/2008 Model Trains
06/Jun/2008 Wedding
04/Jun/2008 Central Coast Trip
more photos...
06/Sep/2010 yuvtshot
06/Sep/2010 yuvhsync
06/Sep/2010 yuvfade
06/Sep/2010 yuvdiff
06/Sep/2010 yuvdiag
more lavtools...
The TRIP is the mental projection of my digital self. Including all areas of digital work I have been involved with, including Music, video, photography...
All good web pages must have the collection of absolutely useless pictures. Designed for no purpose other than to consume kilobits. And hopefully show off some of my Photographic skills. Web design skills, and uses one php script to drive the whole index. Also see the Photography section of the Silicontrip Website.
The Creative section of the TRIP is my imagination trying to run free. I have a fascination with sexual, spiritual and meta physical abilities, and these stories show it.
Part of the images directory contains some of my digital artwork. These images have been created or enhanced by myself, with the help of the 1s and 0s machine.
17/Jan/2010 Food
30/Oct/2009 Airbrush
18/Jun/2009 Focal
01/Jun/2009 Transport
01/Jun/2009 Misc
31/May/2009 Artwork
24/Apr/2009 AirbrushScales
18/Apr/2009 Probe
10/Jan/2009 Scanimation
09/Jul/2008 325
more album...
08/Dec/2009 Time machine on non HFS drives
21/Oct/2009 My Strengths
27/Aug/2009 Train Hitchiking
11/Jul/2009 A litre of onions
19/Jun/2009 FSCK for NTFS
18/Jun/2009 Automated Focal Deconstruction
12/Jun/2009 Perl code to write BMPs
07/Jun/2009 More Lego
01/Jun/2009 Latest Airbrushing
30/May/2009 Happy Birthday to me
24/May/2009 Comments Engine
09/May/2009 Skills Matrix
24/Apr/2009 Airbrush simulator
19/Apr/2009 Ben 10 Board game
29/Mar/2009 How fresh is your fresh food?
15/Mar/2009 Lego
08/Mar/2009 Moomba
13/Feb/2009 Cars and Smokey Sunsets
02/Feb/2009 Libav does audio
30/Jan/2009 Free travel?
more blog...
Some days I love being a unix geek. Especially when commercial products spend all their effort securing their GUI tools and leave all their ancillary unix support tools open.
NTFS is becoming a pain in the ass. FAT is getting too old and hard disks are getting too large for it to remain the de-facto filesystem standard. However as Windows is blind to everything but Microsoft, so NTFS is becoming the new de-facto standard, except...
NTFS is a tightly closed standard, controlled by a company that claims open standards stifle their innovation. We are unlikely to see documentation on how to correctly read NTFS from the filesystem developer. All work on how to read NTFS has been by reverse engineering. Microsoft has a known habit of taking legal action against people who reverse engineer their products.
NTFS is a complex beast and has been difficult to reverse engineer so these implementations are incomplete.
Read Write is a recent feature of these open source NTFS drivers. Filesystem repair is still being developed.
Windows users have a mind set of simply pulling out their disks, without the thought of correctly unmounting them. Mac and Sun hardware used to enforce the correct mentality of Ejecting your disk before pulling it out, by making floppy disks power eject, controlled by the OS. CDrom drives have a command to lock the tray so the eject button doesn't work. Until the disk is safely unmounted.
USB has no locking mechanism. Disks can be pulled out without being properly unmounted. Windows users don't feel that it is important to correctly remove their hardware. Windows will check an uncleanly mounted filesystem silently upon next mount, so users don't know anything was wrong and have no reason to do it correctly.
3rd party implementations of NTFS need to work with a clean filesystem. As there implementations are walking on a tight rope at the best of times. Working on an unclean filesystem WILL lead to filesystem corruption and loss of data. In this case the 3rd party implementation can mount the filesystem read only, or not mount the filesystem at all. As there is no 3rd party tool to repair an NTFS drive the only solution is to return the drive to a Windows machine and run chkdsk. So how can NTFS be the de-facto standard if it is impossible for me to guarentee reading an arbitrary NTFS disk left in an arbitrary state? It simply is not.
This is why NTFS becoming a de-facto standard is a pain.
I know that eventually tools will become available, as long as Microsoft doesn't sue the tool manufacturers.
Of course this does leave a commercial opportunity to sign an NDA with Microsoft for the documentation to NTFS and release a binary only version. A company called Paragon has done this.
This product is commercial, so would have a complete implementation of the standard, chkdsk (or fsck) and all. For all us non Microsoft users we have to pay a premium for someone else saying one Microsoft way or the highway.
The OSX version is made up of GUI tools, preference panel, the kernel driver, registration file, user space library, command line admin tool and mount, newfs and fsck tools. These command line tools are no use to someone who wants a drop and go solution to read NTFS disks but are extremely useful for unix geeks who are using a different NTFS kernel driver, but have no solution to repair disks.
sudo /sbin/fsck_ufsd_NTFS -y /dev/disk9s1 Verifying files... Attribute 0x80 has AllocatedSize not multiple of frame size 8192. Deleting attribute 0x80 . File 0x56a. File "_____padding_file_30_if you see this file, please update to Bit" does not contain data attribute Files verification completed. Verifying meta files... Meta files verification completed. Veryfing $AttrDef. Veryfing $Boot. Verifying $UpCase. $UpCase file is formatted for use in Windows NT/2K/XP Verifying $LogFile. Verifying $Volume. Verifying folders... Correcting error in index 0x30 ($I30) for file 0x5. Folders verification completed. Inserting empty data to files. Inserting empty data completed. Verifying security descriptors... Verifying files security... Security verification completed Verifying $MFT. Correcting $MFT bitmap data. Verifying $MFTMirr. Verifying $Bitmap. Cluster 0x20f0caa is free but marked as used. Cluster 0x1e07ab00 is free but marked as used. Cluster 0x1f2c3580 is free but marked as used. Correcting $Bitmap data attribute.
And the disk shows:
/dev/disk9s1 on /Volumes/MONOLITH (ntfs, local, nodev, nosuid, read-only, noowners)