pksw

I know you don't want to encrypt them, but TrueCrypt would be perfect for this. The folders are hidden unless they are mounted. It's free to try, being open source.

I have found no difference. ST31000333AS SD15 flashed to SD1B OS: WinXp SP3 CPU: Intel Q6600, overclocking turned off for benching HD Tach 3.0.4.0 used I had no issue with my drive - it was only used as a backup disk. Decided to flash it to the new firmware. After flashing, WinXP detected a hardware change, and a new hard disk. During the flashing process, the HDD made a few clicking noises (not unlike the click of death I used to hear from my IBM Deskstar aka Deathstar drives years ago), but it finished ok, and the BIOS detected the new firmware as SD1B. SD15 BIOS Random access 15.3ms CPU utilization 4% Average read: 99.3 MB/s SB1B BIOS Random access 15.2ms CPU utilization 4% Average read: 98.8 MB/s There were a few clicks at the start of the test, which I thought the system had hung, but the bench finished ok. That point is seen in the graph (red line). However, lots of clicking sounds from the drive at random times since I've updated the firmware. I'm not sure if that's a good sign. The system almost seems to pause when that happens.

I think that Telecom New Zealand still will charge me. I can not find landline term. The reference is for mobile phone. Reference: http://www.telecomroaming.co.nz/TermsConditions.aspx Anyway what is the point for Seagate to ask their customer to call them to get a free firmware? It just waste their resource and my time and money. They want to keep their support center's job? That is the only reason I can think of. I heard from tomshardware that seagate got their staff redunant before this hard drive's problem disclosed. My college told me that his hard drive was broken which is the exact model mentioned here and he personally sent back to the shop and waiting for Seagate's assessment and not get the drive back now. My understanding is that the good practise the shop should just simply swap a new hard drive for the customer. The shop should not let the customer waiting the hard drive for months. Stop whinging and just send an email to seagate via their website. I am in Australia, so it's not much different for either of us. What is the point of your colleague getting a new hard disk with the same firmware bug for the old one? It's up to Seagate to fix the problem, not the retail store.

xplorer² is very nice, and freeware for the basic version. I have tried it, and it's not a memory hog and is quick. As I grew up in the DOS era, I still use an XtreeGold clone (www.ztree.com) I use it for everything - moving, copying, renaming, comparing files etc

I use supercat. It can extract comments from archives, catalog JPG resolutions, MPG information etc Give it a go. When I used DOS and floppy disks I used CATDISK. There is a windows version but it hasn't been updated for years.

Thanks, I will try autoit. It sounds perfect for my needs (ability to compile to a stand alone executable).

I have a few applications which pause during the automated installation for a serial number. An example of this would be AdAware Pro, or Partition Magic 8. I have all my serial numbers stored in a text file, and I cut and paste them when installing. Is there a command/program that I can dump data to the clipboard (eg the serial number), so then I can just paste that data to the installation program? I know this is now as elegant as other solutions, but it would allow a bypass of sorts.

Can I force installation of WinXP to my second partition (NTFS) during an unattended installation from my FAT32 C:\ I format my hard drive so I can dual boot between DOS and WinXP. Example: 80 Gig Hard Disk Primary Partition: 5 Gigabytes (FAT32), Win98SE command line, NTFS for DOS Extended Patition: 75 Gigabytes (NTFS) I copy the WinXP CD to the FAT32 primary partition, and boot off that disk. I can successfully do an unattended install but it always goes to the FAT32 "C:". I want to be able to force the installation to the NTFS "D:" ---- These switches automatically install to the C:, which is NOT what I want ---- ;SetupMgrTag [Data] AutoPartition=0 MsDosInitiated="0" UnattendedInstall="Yes" [unattended] UnattendMode=FullUnattended OemSkipEula=Yes OemPreinstall=No TargetPath=\WINDOWS --- Are there any modifications that I can make?

Could you check q824141 I downloaded it twice, and the filesize is 2,223,200 not 2,728,544 The update suggests it is from Oct 29, and on the first page of this thread it is listed as Oct 15. Maybe Microsoft have changed it? Or is it just me? Thanks