Software for Toshiba drives

www.semicon.toshiba.co.jp/eng/event/news/
========================

TOSHIBA Disc Creator 2.1.0.6Toshiba Disc Creator is a program for creating CDs, DVDs and HD DVDs.

• Publisher: TOSHIBA Corporation
• Home page: www.mytoshiba.com.au
• Last updated: June 24th, 2011

NTI Backup NOW! 5.1.5.506
NTI Backup Now Standard Edition a lite version that backs up and restores files.

• Publisher: NewTech Infosystems
• Last updated: April 19th, 2008

NTI Shadow 3.7.7.10
NTI Shadow is an award-winning, easy-to-use backup solution.

• Publisher: NewTech Infosystems
• Last updated: December 7th, 2011

Source

Get the latest NTI updates, downloads and promotions

	NTI Backup Now EZ Download NTI Backup Now EZ update here: Click Here
	NTI Echo No new software updates are available
	NTI Pocket Data Backup No new software updates are available

Take me to the Toshiba Support Home Page


NTI corp 

Software:NTI Backup Now EZ update patch
System: Windows 7 / Vista / XP
For:NTI OEM Versions
From:NTI Backup Now EZ 1.1.2.51
To:NTI Backup Now EZ 1.1.2.77a
Date:February 22 2010

========================
storage.toshiba.com/archived models
Toshiba Portable Hard Drive
320 / 500 / 640GB* / External / USB 2.0  

Quick Install Guide/Limited Warranty Information Technical Support  Service Bulletin  – Important information for NTI's Backup Now EZ To ensure proper installation of NTI's Backup Now EZ software, it is recommended that you install the software to the default directory shown in the software. If you choose to change the default installation directory, you must create a new folder to ensure trouble free operation. Click below to download the latest version of NTI's Backup Now EZ. This service pack includes all the latest feature enhancements, Windows 7 compatibility and critical updates. Backup Now EZ v1.1.2.77.zip NOTE This update is mandatory for all users that have not yet installed Backup Now EZ on their computers. It includes all the latest feature enhancements and is Windows 7 compatible. Backup Now EZ Patch (1.1.2.51 to 1.1.2.77).zip NOTE This is an update for current users of Backup Now EZ. It includes minor feature enhancements and ensures Windows 7 compatibility. This update is recommended for all users that have already installed Backup Now EZ on their computer

Special offers & software patches are specific to the software bundled with Toshiba USB hard drives. Update Patch
------------------------------------
Toshiba STOR.E ART 4 External Hard Drives are pre-loaded with NTI Backup Now EZ, enableing data backup and data protection through 256-bit data encryption.
The STOR.E ART 4 family ships a 500GB model (118.9 x 79 x 13.5mm / 154 grams) with red graphical accents, and 750GB and 1TB drives (118.9 x 79 x 16.5mm / 186 grams) with blue and white trims, respectively. 
====================

storage.toshiba.com/storage-services-support/software-utilities
----------------------
Partition Alignment Tool for Toshiba Generation One Advanced Format HDDs
Most recent computer operating systems (OSs) have been designed to work effectively with Generation One AF HDD supporting 512 emulation. Generation One AF HDD may deliver superior performance as compared to legacy 512 byte per sector drive models when properly configured with the host file system,. In PC applications, the host file system is primarily determined by the OS installed on the computer.
Toshiba offers the Paragon Partition Alignment Tool (PAT) to align partitions on Toshiba Generation One AF HDD for optimal system and application performance. To determine if your Toshiba HDD will benefit from alignment, please refer AF table below. The table outlines which OS can benefit from the assistance of PAT.
This downloadable tool is available to licensed single system users of Toshiba HDDs.
Recommended reading:

• Advanced Format Overview
• Frequently Asked Questions (FAQ) on PAT for Toshiba Generation One AF HDD (28kB)

Refer table of OS to PAT usage (Do not use for encryptedpartitions.)

Operating System	PAT Usage Guidelines for Toshiba Generation One AF HDD
Windows® 7 (32- or 64-bit) - factory installed	Not necessary
Windows® 7 (32- or 64-bit) - non-factory installed pre-Service Pack 1 (SP1) versions	Recommended
Windows® 7 (32- or 64-bit) - non-factory installed Service Pack 1 (SP1) or above	Not necessary
Windows Vista®, SP1 and above 1 partition drive configurations	Not necessary
Windows Vista®, SP1 and above 1 partition drive configurations	Recommended
Windows Vista®, without SP	Recommended
Windows® XP (32- or 64-bit)	Recommended
Windows Server® 2003	Recommended
Windows Server® R2 2003	Recommended
Windows Home Server® version 1	Recommended
Windows Home Server®	Recommended
Windows Server® 2008	Not necessary*
Windows Server® 2008 R2	Not necessary*
Windows® PE 3.0 and below	Recommended
Other Windows® OSs not listed above	Upgrading to an newer OS if using AF drives.
Apple Mac OS X 10.4 and above	Not necessary
Linux Ubuntu 8.04 and below	Recommend using a Linux partition utility; (see FAQ)   (47kB)
Linux kernel 2.6.34 and below	Recommend using a Linux partition utility; (see FAQ)   (47kB)
Open SuSE Linux	Recommend using a Linux partition utility; (see FAQ)   (47kB)

Note: PAT may not be suitable for Toshiba Generation One AF HDDs alignment activities involving multiple client systems or disk image cloning; (see FAQ).   (47kB)
Preparation before download PAT
see more at link
PAT Download
Multi-language software will allow you to select one of ten languages during install.

Recommended reading:

• Advanced Format Overview
• Frequently Asked Questions (FAQ) on PAT for Toshiba Generation One AF HDD  (47kB)

http://www.toshibastorage.com/
 ===========================
Toshiba and Security
While consumers continue to amass "digital valuables" and recognize the need for privacy protection, Toshiba enables convenience, performance and security with backup software and self-encrypting drives. Learn more 

Pre-loaded software

Whether backing up your entire system, or packing up the pictures, files, music and videos you need to bring, our portable hard drives can help. They come with pre-loaded software (Canvio 3.0 models only) to save you the time and expense of buying the right back-up app. And they make restoring data just as easy.

Enabling Cloud Storage
Cloud computing is an important and compelling new tool for IT managers. Click the Learn more  to watch the video: "Storage in the Age of Cloud Computing".  

Extremely Accurate

Make sure VSSVC.EXE is running

runtime.org/driveimage_faq.htm#vss

Q. Why am I getting a VSS error when I try to backup a drive?

A. This error can occur if VSS (Volume Shadow Services) is not running properly on your system. This is not a DriveImage error. It is usually caused by poorly configured Windows systems.
inicio - ejecutar: services.msc
Please verify in Settings->Control Panel->Administrative Tools->Services that the following services are enabled:

MS Software Shadow Copy Provider
Volume Shadow Copy

Also make sure you are able to stop and start these services.
Possible reasons for VSS failures:
For VSS to work, at least one volume in your computer must be NTFS. If you use only FAT drives, VSS will not function.
The required NTFS volume does not need to be identical with the volume you want to image.
You should make sure that VSSVC.EXE is running in your task manager. If the problems persist, registering "oleaut.dll" and "oleaut32.dll" using "regsvr32" might help.
Without VSS you still can make images with locking or without locking.
Source
DriveXML is returning:

Could not initialize Windows Volume Shadow Service (VSS). ERROR C:\Program Files (x86)\Runtime Software\Drivelmage XML\vss64.exe failed to start. ERROR TIMEOUT Make sure VSSVC.EXE is running in your task manager. Click Help for more information.

VSSVC.EXE is running in Task Manager, as is VSS64.exe. Looking at the FAQ on the Runtime webpage this turned up:

Please verify in Settings->Control Panel->Administrative Tools->Services that the following services are enabled:

MS Software Shadow Copy Provider
Volume Shadow Copy

Also make sure you are able to stop and start these services.

==========================
Source
As part of the problem with MS Software Shadow Copy Provider service.
Symptoms:
Component Service woudn't expand.
MS Provider service woudn't start.
Error error 0x8000ffff when trying to run regsvr32 /i swprv.dll or vssadmin list providers
-------------------
Here is how I fixed it.
1) Deleted registry entry for SwPrv. (In fact some application deleted the service before, but I've imported it from the other computer). This is to allow COM+ app import later.
2) Deleted com3 key and COM+ folders as per messages and links above. Rebooted. This is to re-install COM+
3) Re-installed COM+ as per links above and MS recommendations. Now I was able to expand Component Services down to My Computer, but there was no MS Provider application there.
4) From the working computer with the same OS version I've exported MS Software Shadow Copy Provider application. To do so, Start Component Services, expand to "COM+ Applications", right-click on "MS ... Provider" name and choose "Export" from the menu. On the next screen choose "Export user identities with roles"
It will ask you for file name and location and it will create MSI package.
Copy the package to the troubled computer.
5) On the computer-in-need:
- start component services
- expand to "my computer" node
- right-click on "COM+ Applications" and choose "new" --> "Application"
- choose "Install pre-built application" button and navigate to the MSI package. Keep all defaults.
After the process completes, there is proper COM+ application as well as the service installed.
If there is any errors during the process, there is some left-over running and it is necessary to clean the registry and reboot then repeat COM+ install.

At this point you should be able to start both Shadow Copy-ralated services.
I had correct reply yto vssadmin list providers (it was error 0x8000ffff before)
I was getting an error 0x8000ffff in reply to vssadmin list writers and Event ID 8193 was logged in the App log. Backup was working at this point but without Shadow Copy.

Then I followed the steps from
http://blogs.technet.com/sdoakes/archive/2.../03/418722.aspx

www.msfn.org/board/index...?showtopic=70962
At command prompt::
Cd windows\system32
Net stop vss
Net stop swprv
regsvr32 ole32.dll
regsvr32 vss_ps.dll
Vssvc /Register
regsvr32 /i swprv.dll ---- I was able to register it, before Iwas getting error 0x8000ffff
regsvr32 /i eventcls.dll
regsvr32 es.dll
regsvr32 stdprov.dll
regsvr32 vssui.dll --- I had XP, I guess this should work for 2003 only.
regsvr32 msxml.dll --- the last 3 depend on what XML versions you have installed.
regsvr32 msxml3.dll --- if you get error here, re-install corresponding XML version
regsvr32 msxml4.dll
If errors, navigate to
C:\Windows\System32 directory and try the regsvr32 commands again.
2. After completing the registration of the DLL’s  type:
vssadmin list writers
3. You should see the writers listed.
4. Open Ntbackup and attempt to backup file or systemstate.
VSS needs NT Backup to work, if I remember correctly and its twin service MS Software Shadow Copy Provider (SwPrv)
You need NT Backup, too. For services, VSS and MVSC need to be Manual. Also, don't screw with anything that toasts MMC, or you're in a world of potential hurt here. Indexing is totally unneeded as an explicit service (I haven't used ot for over year in my installs)--but there are inter-component aspects extant (that's why you keep coming across references): we can remove it, but parts we keep that we need still imprint it on various interfaces--and it's one of these part you most likely made angry. Shadow Copy would certainly qualify...

=====================
Source2
groups.google.nl/group/microsoft.pu...9a95c0ac4a7a9b2
msfn.org/board/topic/70962-restore-volume-shadow-copy-vss-and-ms-software-sha/
backupassist.com/KnowledgeBase/...olumeShadowCopy
They also indicate that I need more files (stdprov.dll, eventcls.dll) which are not on the partition with the new install.
Performing the steps of the 1st link I am able to restore and start the "MS Software Shadow Copy Provider" on my own system (where it was not installed either as I discovered today), but not the "Volume Shadow Copy" (VSS).
Furthermore "vssadmin list providers" output is OK.

"your original record reports 244 heads...

while your new target drive reports 255 heads drive image"

DriveImageXML command line parameters

A. For the backup there are the following commands:

/bx	Backup drive x, e.g. /bc
/tx	Write backup files to x, e.g. /td:\backups\drive_c
/r	Raw mode, e.g. /r or /r-
/s	Split image, e.g. /s or /s-
/c	Compression (fast), e.g. /c or /c-
/c1	Compression (fast), e.g. /c1
/c2	Compression (good, but slow), e.g. /c2
/v	Try VSS first, e.g. /v, do not use with /l
/l	Try locking first, e.g. /l, do not use with /v

Q. What about command line parameters for restoring a drive?

A. There currently are not any.

READ

Source
Remember that DriveImageXML images drives , NOT disks!
----

Indeed; I wouldn't want it to image the entire disk, just the drives on the disk that I specify.

And indeed, without ALSO the MBR and DISK SIGNATURE you won't be able to boot the restored "backup" easily.

DriveImage XML FAQ excerpts

http://www.runtime.org/

Q. What files are created by DriveImage?

A. It depends on whether you create a multi-file image or not. A multi-file image will have a .xml file and a .dat file and files beyond that are numbered .001, .002, .003,… until the end of the drive. If you do not create a multi-file image, there will be a .dat file and a .xml file.

Q. Where are these files stored?

A. You will be prompted for a location in the software and you can choose where ever you like (not on the source drive though), however the default location is My Documents.

Q. Are there any command line parameters?

A. For the backup there are the following commands:

/bx	Backup drive x, e.g. /bc
/tx	Write backup files to x, e.g. /td:\backups\drive_c
/r	Raw mode, e.g. /r or /r-
/s	Split image, e.g. /s or /s-
/c	Compression (fast), e.g. /c or /c-
/c1	Compression (fast), e.g. /c1
/c2	Compression (good, but slow), e.g. /c2
/v	Try VSS first, e.g. /v, do not use with /l
/l	Try locking first, e.g. /l, do not use with /v

Q. How do I restore an image back to a working state?

A. Note that you must put the image into an existing partition. If necessary create a new partition with Windows Disk Management first. You do not need to format the drive. The size of the partition you create will determine the size of the drive - for example if you create a 20GB partition and then restore a 10GB size image to it, the size of the drive will still be 20GB.

To start Windows Disk Management click:

Start>Control Panel>Administrative Tools>Computer Management>Disk Management

If Windows Disk Management does not start, you can use the following commands from the command prompt:

net start dmserver

net start dmadmin

diskpart

To restore an image to an existing partition, click Restore in the main program window.

Note on boot drives: If you want your computer to boot from the new partition you must set it to "active" with Windows Disk Management.

Q. Why am I getting a VSS error when I try to backup a drive?

A. This error can occur if VSS (Volume Shadow Services) is not running properly on your system. This is not a DriveImage error. It is usually caused by poorly configured Windows systems.

Please verify in Settings->Control Panel->Administrative Tools->Services that the following services are enabled:

MS Software Shadow Copy Provider

Volume Shadow Copy

Also make sure you are able to stop and start these services.

Possible reasons for VSS failures:

For VSS to work, at least one volume in your computer must be NTFS. If you use only FAT drives, VSS will not function. The required NTFS volume does not need to be identical with the volume you want to image.

You should make sure that VSSVC.EXE is running in your task manager. If the problems persist, registering "oleaut.dll" and "oleaut32.dll" using "regsvr32" might help.

Without VSS you still can make images with locking or without locking.

Q. I restored my boot drive, why does it not boot?

A. To boot from a drive:

• The boot partition should be located on the first drive (DISK0), which is usually the master drive.
• The boot partition should be the first partition on the drive.
• The boot partition must be a "primary" partition.
• The boot partition must be "active".

If your drive still does not boot you can try to set a new "Disk ID". Windows remembers old drive letter assignments which can cause problems when trying to boot from a cloned drive. You can force the removal of old drive letter assignments by setting a new Disk ID. Click Tools->Set new Disk ID and read the instructions.

Vista Boot Problem:

If your cloned Vista drive refuses to boot with a "winload.exe is missing or corrupt" message, you might need to change the BCD store.

Fix automatically

- In DriveImage click on Tools->Fix Vista boot problem. 

- Select the BCD Store of the new (cloned) drive.

- Click "Update BCD Store".

Your drive should now boot.

Fix manually

- Boot from your Vista installation DVD and start the command prompt. If your Windows directory is on C: navigate to c:\windows\system32.

- Type "bcdedit" (without quotes) and press Enter. You should see the following screen:

Windows Boot Manager

--------------------

identifier {bootmgr}

device partition=C:

description Windows Boot Manager

locale en-US

inherit {globalsettings}

default {current}

displayorder {current}

toolsdisplayorder {memdiag}

timeout 30

Windows Boot Loader

-------------------

identifier {current}

device partition=C:

path \Windows\system32\winload.exe

description Microsoft Windows Vista

locale en-US

inherit {bootloadersettings}

osdevice partition=C:

systemroot \Windows

resumeobject {d96b9513-83c6-11db-8615-bcd1a0f0502e}

nx OptIn

If under "Windows Boot Loader", "device" or "osdevice" do not contain your boot partition's name but display "unknown", you need to correct this. Type:

bcdedit /set {default} osdevice "partition=C:

bcdedit /set {default} device "partition=C:

Read a good article about Vista cloning problems here:

http://www.multibooters.co.uk/cloning.html

This link points to a techforum that discusses the Vista boot problem:

http://forums.microsoft.com/TechNet/ShowPost.aspx?PageIndex=2 &SiteID=17&PostID=1343608

Windows 7 Boot Problem:

Windows 7 provides all the challenges mentioned above. In addition, a Window 7 standard installation provides a boot manager that is located in a small partition preceding the Winows 7 partition. However, we found the Windows 7 installation DVD very helpful with fixing boot problems. If you do not get the drive to boot, put in the installation DVD and initiate a startup repair. Here is a comprehensive article on how to do that: http://pcsupport.about.com/od/toolsofthetrade/ss/windows-7-startup-repair.htm

Q. Can I backup and restore a RAID?

A. Yes, as long as it is a hardware RAID. If it is a Windows software RAID, you can back it up, but you can not restore it back to the software RAID. You can restore it to an individual drive or hardware RAID, though.

VSS Error 80042316 in DriveImageXML

Getting Past VSS Error 80042316 from DriveImage XML
by Mark Berry 24/03/2008
I'm using Runtime Software's free DriveImage XML to back up several XP machines over a network to Windows 2003 server. Scheduled tasks run DriveImage XML in command-line mode and are set to try VSS before drive locking. Another scheduled task collects logs and emails them to me.
Today I noticed that one of the backups did not complete. When I tried to run the backup interactively, DriveImage XML told me that it "Could not initialize Windows Volume Shadow Copy Service (VSS)" and that the error code was 80042316. The Volume Shadow Copy service was running. I tried stopping and starting the service and re-running the backup, but it still could not proceed.
Some Google research turned up the meaning of 80042316 as "another snapshot creation is in progress. Please retry later your snapshot creation." However to the best of my knowledge there are no other backups or other VSS-aware processes running.

I thought perhaps the recent change from Trend CS 3.6 to NOD 32 2.7 might have caused a problem, but DriveImage XML completed fine on several other machines running NOD32.
Finally I remembered that there is a command-line utility to look into VSS on a machine. I typed

vssadmin list shadows

at a command prompt and it showed that there is a shadow copy on some kind of virtual volume (\\?\Volume{2eb5f062-fd3d-11d8-8bb5-806d6172696f}\). Stopping and starting the Volume Shadow Copy service did not remove the shadow copy.
Maybe this is a remnant from an old backup? I don't know how to directly delete shadow copies under Windows XP, but let's see if a reboot helps...
Bingo! After the reboot, the "vssadmin list shadows" command showed "No shadow copies present in the system," and DriveImage XML was able to create a new shadow copy and do the backup.
Not Fixed
Alas, when DriveImage XML completed and exited, I still had a volume shadow copy on the volume, and the next time I ran DriveImage XML, it gave me the same message but a slightly different error code: 80042317. Google isn't so helpful in finding a description for 80042317. But rebooting the machine again killed the shadow copy and let DriveImage XML run, so I'm assuming it's the same issue.
Bummer! So why can't DriveImage XML release/delete its shadow copies on this machine? The Microsoft storage team lists three recommended hotfixes for VSS in this blog entry, but they are all for Windows Server 2003, not XP.
Excluding the C:\System Volume Information folder (where volume shadow copies are stored, I believe) from NOD32 didn't help.
Excluding dixml.exe (the DriveImage XML executable) from NOD32 didn't help.
I'll update this if I find a solution (other than rebooting the machine after every backup!).

Acronis True Image vs Symantec Ghost

Source (Review) [Excerpts]
A regular Ghost user tries out True Image V9 and concludes that Ghost V10 has met its match

---

Foreword from Gizmo
A drive imaging program is a utility that creates a backup snapshot or image of your disk drives, most commonly your system drive. Imaging programs differ from data backup programs in that they can backup the Windows Operating system itself. You can use that backup image to recover from system failures, spyware infections, installations gone wrong or any of the dozens of other things that can seriously mess up your PC.
Imaging programs can be used to backup data as well as your operating system but are not ideal for that task. Recent versions of imaging programs have improved in this area but many folks, myself included, prefer to use imaging programs to back up Windows and data backup programs like Genie, to backup regularly changing data.
Every PC I own has a drive imaging utility installed and I use these regularly to make image backups of the C: drives. I simply can't tell you just how many times I've been able to use these backup images to restore a non-working PC to perfect health. Restoring from an image only takes me minutes while a full Windows re-install can take many hours or even days when you take into account re-installing application programs. That's why I recommend the system drive of every PC should be imaged regularly using a reliable imaging program.
Now let me tell you the harsh truth: when it comes to the best imaging program it's a two horse race between the commercial products Acronis True Image and Norton Ghost with the freeware contenders trailing by a couple of miles. Not that there aren't some usable freeware products; it's just they aren't in the same league when it comes to function, features and reliability. Choosing between True Image and Ghost is tough because they are both quality programs. That's why I asked regular Support Alert contributor J.W. to review the latest versions of these products.
Acronis True Image vs. Norton Ghost
When Gizmo asked me to review Acronis True Image V9, I was delighted. I had been using Norton Ghost V9 and wasn't happy with the product due to on-going problems with corrupted images. Additionally I had never used True Image so the review provided me with an opportunity to look at the how Ghost compared to its main competitor in a live system, doing real work.
Installation Woes
Life was not meant to be easy.
Right from the start I had problems with both Norton Ghost and Acronis True Image on my PC. The problems as it turned out were partly caused by Process Guard, a security application that runs on my PC. However this problem proved to be a blessing in disguise as it allowed me to test out the support provided by Symantec and Acronis. Symantec support for Ghost was abysmal; an odyssey of condescending replies, canned responses and the apparent inability of the Indian support staff to understand the English language. Eventually, I wrote a personal letter to the Chairman & CEO of Symantec, John W. Thompson, asking for his help and assistance. My plea worked and I was put in contact with an “Executive Support” group. They seemed much more anxious to help and started off well by sending me the latest version of Ghost 10. I was optimistic that with the receipt this new version that the problems I had been experiencing with corrupted Ghost image backups would disappear. Sadly, that was not to be. Even with the latest V10 release I had more invalid backup’s, completely baffling the “Executive Support” group. After a number of emails back and forth, they adamantly pronounce that not one but BOTH of my U320 SCSI hard drives were broken and needed to be immediately replaced! After expressing my incredulity with this diagnosis, they decided to try blaming the problem on my CPU processor. Anything it seemed other than their product. Their last email to me was pure bathos:
“Do not bother responding to this email as there is nothing else I can help you with and it will not be responded to.”
So much for Symantec "executive" level support. I was clearly on my own. The experience with Acronis support was much better. Their support team was also baffled, but at least they maintained their composure, didn’t make any nonsensical recommendations such as replacing my hard drives and were civil. Eventually I solved the problem myself; another application, Process Guard, was interfering with the operation of the programs. Once Process Guard was uninstalled, the immediate difficulties were resolved allowing me to move forward with my comparative review. But a vital lesson about support was learned and not to be forgotten. Furthermore some serious problems with Ghost remained.
Corrupted Images
Even after removing Process Guard from my PC, I continued to have on-going problems with Ghost V10 with corrupted image files.
...
My recommendation and personal choice going forward for a disk-imaging program is Acronis True Image.