Sprite Backup or SPB Backup - warnings - Touch HD General

When I backed up my HD using Sprite Backup 6.5.2
I got few warnings
File could not be included: \Windows\System\SQM\Sessions\Global
File could not be included: \Windows\System\SQM\Sessions\PMWeek
File could not be included: \mxip_notify.vol
File could not be included: \mxip_swmgmt.vol
File could not be included: \cemmail.vol
When I backup it using SPB Backup 2.0.0 (I disabled stopping processes before backup) I'm getting lots of warnings like this:
Unable to read from file: "\Windows\BPSD\PictureMate_2005.bpsd"
Unable to read from file: "\Windows\BPSD\PictureMate_500.bpsd"
....
Unable to read from file: "\Windows\BPSD\Stylus_C63.bpsd"
....
lots of .bpsd files which look like they are from JetCet
My question is - what you guys use for backup and is it safe to ignore them ?
Did somebody try to hard reset and restore from backup ? Any issues ? What programs ?

Well, first of all, you shouldn't disable stopping processes before backup as you risk to get corrupt/irrelevant data. The reason why processes are stopped I think is to prevent them writing to files that are backed up, and sometimes to unlock these files. That's why you could get the "Unable to read" warnings.
Sprite warnings look more scary, as the .vol files are important system database files, and I'm not sure you'll be able to restore your device without them.

vangrieg said:
Well, first of all, you shouldn't disable stopping processes before backup as you risk to get corrupt/irrelevant data. The reason why processes are stopped I think is to prevent them writing to files that are backed up, and sometimes to unlock these files. That's why you could get the "Unable to read" warnings.
Sprite warnings look more scary, as the .vol files are important system database files, and I'm not sure you'll be able to restore your device without them.
Click to expand...
Click to collapse
Problem is that with SPB Backup if I DO NOT stop processes - it does not start at all, allows me to choose backup directory and file name, but when STOPPING processes - crashes and asks if I want to send notes to Microsoft

bogdatov said:
When I backed up my HD using Sprite Backup 6.5.2
I got few warnings
File could not be included: \Windows\System\SQM\Sessions\Global
File could not be included: \Windows\System\SQM\Sessions\PMWeek
File could not be included: \mxip_notify.vol
File could not be included: \mxip_swmgmt.vol
File could not be included: \cemmail.vol
When I backup it using SPB Backup 2.0.0 (I disabled stopping processes before backup) I'm getting lots of warnings like this:
Unable to read from file: "\Windows\BPSD\PictureMate_2005.bpsd"
Unable to read from file: "\Windows\BPSD\PictureMate_500.bpsd"
....
Unable to read from file: "\Windows\BPSD\Stylus_C63.bpsd"
....
lots of .bpsd files which look like they are from JetCet
My question is - what you guys use for backup and is it safe to ignore them ?
Did somebody try to hard reset and restore from backup ? Any issues ? What programs ?
Click to expand...
Click to collapse
Interesting. I use that version of Sprite and only get the first two warnings i.e. no *.vol warnings.

Steve James said:
Interesting. I use that version of Sprite and only get the first two warnings i.e. no *.vol warnings.
Click to expand...
Click to collapse
Did you try to restore using Sprite ? How was it ?

SPB: No problem
I use SPB back/up without problems.
Just use task manager to kill of unneeded processes, and disable tf3d.

bogdatov said:
Did you try to restore using Sprite ? How was it ?
Click to expand...
Click to collapse
Restored multiple times both system and data without problems.

zSpinner said:
I use SPB back/up without problems.
Just use task manager to kill of unneeded processes, and disable tf3d.
Click to expand...
Click to collapse
Disable tf3d ?!!! So, no scheduled backups, right ?

arisg said:
Restored multiple times both system and data without problems.
Click to expand...
Click to collapse
Have you had any of warnings I mentioned in 1st post ?

sprite backup
i have a same problèms ith sprite

bogdatov said:
Did you try to restore using Sprite ? How was it ?
Click to expand...
Click to collapse
Unfortunately not!

SPB Backup V2.0.0 Warnings
I too have the same problem with SPB Backup and de "\Windows\BPSD\" directory in my Blackstone. It logs like this:
2009-02-17 16:35:30 Backup process started...
2009-02-17 16:35:30 Backup file name: "\Storage Card\Backup_20090217.exe"
2009-02-17 16:37:47 Unable to read from file "\Windows\BPSD\PictureMate_2005.bpsd".
2009-02-17 16:37:47 Unable to read from file "\Windows\BPSD\PictureMate_500.bpsd".
2009-02-17 16:37:48 Unable to read from file "\Windows\BPSD\PictureMate_Deluxe.bpsd".
2009-02-17 16:37:48 Unable to read from file "\Windows\BPSD\Stylus_C43.bpsd".
2009-02-17 16:37:49 Unable to read from file "\Windows\BPSD\Stylus_C44.bpsd".
2009-02-17 16:37:49 Unable to read from file "\Windows\BPSD\Stylus_C45.bpsd".
2009-02-17 16:37:50 Unable to read from file "\Windows\BPSD\Stylus_C46.bpsd".
2009-02-17 16:37:50 Unable to read from file "\Windows\BPSD\Stylus_C60.bpsd".
2009-02-17 16:37:50 Unable to read from file "\Windows\BPSD\Stylus_C63.bpsd".
2009-02-17 16:37:51 Unable to read from file "\Windows\BPSD\Stylus_C64.bpsd".
2009-02-17 16:37:51 Unable to read from file "\Windows\BPSD\Stylus_C65.bpsd".
2009-02-17 16:37:52 Unable to read from file "\Windows\BPSD\Stylus_C66.bpsd".
2009-02-17 16:37:52 Unable to read from file "\Windows\BPSD\Stylus_C67.bpsd".
2009-02-17 16:37:53 Unable to read from file "\Windows\BPSD\Stylus_C68.bpsd".
2009-02-17 16:37:53 Unable to read from file "\Windows\BPSD\Stylus_C80.bpsd".
2009-02-17 16:37:53 Unable to read from file "\Windows\BPSD\Stylus_C83.bpsd".
2009-02-17 16:37:54 Unable to read from file "\Windows\BPSD\Stylus_C84.bpsd".
2009-02-17 16:37:54 Unable to read from file "\Windows\BPSD\Stylus_C85.bpsd".
2009-02-17 16:37:55 Unable to read from file "\Windows\BPSD\Stylus_C86.bpsd".
2009-02-17 16:37:55 Unable to read from file "\Windows\BPSD\Stylus_C87+.bpsd".
2009-02-17 16:37:55 Unable to read from file "\Windows\BPSD\Stylus_C87.bpsd".
2009-02-17 16:37:56 Unable to read from file "\Windows\BPSD\Stylus_C88+.bpsd".
2009-02-17 16:37:56 Unable to read from file "\Windows\BPSD\Stylus_C88.bpsd".
2009-02-17 16:37:57 Unable to read from file "\Windows\BPSD\Stylus_CX3100.bpsd".
2009-02-17 16:37:57 Unable to read from file "\Windows\BPSD\Stylus_CX3200.bpsd".
2009-02-17 16:37:58 Unable to read from file "\Windows\BPSD\Stylus_CX3500.bpsd".
2009-02-17 16:37:58 Unable to read from file "\Windows\BPSD\Stylus_CX3600.bpsd".
2009-02-17 16:37:59 Unable to read from file "\Windows\BPSD\Stylus_CX3650.bpsd".
2009-02-17 16:37:59 Unable to read from file "\Windows\BPSD\Stylus_CX3700.bpsd".
2009-02-17 16:37:59 Unable to read from file "\Windows\BPSD\Stylus_CX3800.bpsd".
2009-02-17 16:38:00 Unable to read from file "\Windows\BPSD\Stylus_CX3805.bpsd".
2009-02-17 16:38:00 Unable to read from file "\Windows\BPSD\Stylus_CX3810.bpsd".
2009-02-17 16:38:01 Unable to read from file "\Windows\BPSD\Stylus_CX4100.bpsd".
2009-02-17 16:38:01 Unable to read from file "\Windows\BPSD\Stylus_CX4200.bpsd".
2009-02-17 16:38:01 Unable to read from file "\Windows\BPSD\Stylus_CX4800.bpsd".
2009-02-17 16:38:02 Unable to read from file "\Windows\BPSD\Stylus_CX4900.bpsd".
2009-02-17 16:38:02 Unable to read from file "\Windows\BPSD\Stylus_CX5000.bpsd".
2009-02-17 16:38:03 Unable to read from file "\Windows\BPSD\Stylus_CX5100.bpsd".
2009-02-17 16:38:03 Unable to read from file "\Windows\BPSD\Stylus_CX5200.bpsd".
2009-02-17 16:38:03 Unable to read from file "\Windows\BPSD\Stylus_CX5300.bpsd".
2009-02-17 16:38:04 Unable to read from file "\Windows\BPSD\Stylus_CX5400.bpsd".
2009-02-17 16:38:04 Unable to read from file "\Windows\BPSD\Stylus_CX6300.bpsd".
2009-02-17 16:38:05 Unable to read from file "\Windows\BPSD\Stylus_CX6400.bpsd".
2009-02-17 16:38:05 Unable to read from file "\Windows\BPSD\Stylus_CX6500.bpsd".
2009-02-17 16:38:05 Unable to read from file "\Windows\BPSD\Stylus_CX6600.bpsd".
2009-02-17 16:38:06 Unable to read from file "\Windows\BPSD\Stylus_CX7700.bpsd".
2009-02-17 16:38:06 Unable to read from file "\Windows\BPSD\Stylus_CX7800.bpsd".
2009-02-17 16:38:07 Unable to read from file "\Windows\BPSD\Stylus_D68.bpsd".
2009-02-17 16:38:07 Unable to read from file "\Windows\BPSD\Stylus_D88+.bpsd".
2009-02-17 16:38:08 Unable to read from file "\Windows\BPSD\Stylus_D88.bpsd".
2009-02-17 16:38:08 Unable to read from file "\Windows\BPSD\Stylus_DX3800.bpsd".
2009-02-17 16:38:08 Unable to read from file "\Windows\BPSD\Stylus_DX3850.bpsd".
2009-02-17 16:38:09 Unable to read from file "\Windows\BPSD\Stylus_DX4200.bpsd".
2009-02-17 16:38:09 Unable to read from file "\Windows\BPSD\Stylus_DX4250.bpsd".
2009-02-17 16:38:10 Unable to read from file "\Windows\BPSD\Stylus_DX4800.bpsd".
2009-02-17 16:38:10 Unable to read from file "\Windows\BPSD\Stylus_DX4850.bpsd".
2009-02-17 16:38:10 Unable to read from file "\Windows\BPSD\Stylus_DX5000.bpsd".
2009-02-17 16:38:11 Unable to read from file "\Windows\BPSD\Stylus_Photo_810.bpsd".
2009-02-17 16:38:11 Unable to read from file "\Windows\BPSD\Stylus_Photo_820.bpsd".
2009-02-17 16:38:12 Unable to read from file "\Windows\BPSD\Stylus_Photo_825.bpsd".
2009-02-17 16:38:12 Unable to read from file "\Windows\BPSD\Stylus_Photo_830.bpsd".
2009-02-17 16:38:12 Unable to read from file "\Windows\BPSD\Stylus_Photo_900.bpsd".
2009-02-17 16:38:13 Unable to read from file "\Windows\BPSD\Stylus_Photo_915.bpsd".
2009-02-17 16:38:13 Unable to read from file "\Windows\BPSD\Stylus_Photo_925.bpsd".
2009-02-17 16:38:14 Unable to read from file "\Windows\BPSD\Stylus_Photo_950.bpsd".
2009-02-17 16:38:14 Unable to read from file "\Windows\BPSD\Stylus_Photo_960.bpsd".
2009-02-17 16:38:14 Unable to read from file "\Windows\BPSD\Stylus_Photo_R200.bpsd".
2009-02-17 16:38:15 Unable to read from file "\Windows\BPSD\Stylus_Photo_R210.bpsd".
2009-02-17 16:38:15 Unable to read from file "\Windows\BPSD\Stylus_Photo_R220.bpsd".
2009-02-17 16:38:16 Unable to read from file "\Windows\BPSD\Stylus_Photo_R230.bpsd".
2009-02-17 16:38:16 Unable to read from file "\Windows\BPSD\Stylus_Photo_R260.bpsd".
2009-02-17 16:38:16 Unable to read from file "\Windows\BPSD\Stylus_Photo_R265.bpsd".
2009-02-17 16:38:17 Unable to read from file "\Windows\BPSD\Stylus_Photo_R270.bpsd".
2009-02-17 16:38:17 Unable to read from file "\Windows\BPSD\Stylus_Photo_R300.bpsd".
2009-02-17 16:38:18 Unable to read from file "\Windows\BPSD\Stylus_Photo_R310.bpsd".
2009-02-17 16:38:18 Unable to read from file "\Windows\BPSD\Stylus_Photo_R320.bpsd".
2009-02-17 16:38:19 Unable to read from file "\Windows\BPSD\Stylus_Photo_RX500.bpsd".
2009-02-17 16:38:19 Unable to read from file "\Windows\BPSD\Stylus_Photo_RX510.bpsd".
2009-02-17 16:38:19 Unable to read from file "\Windows\BPSD\Stylus_Photo_RX600.bpsd".
2009-02-17 16:38:20 Unable to read from file "\Windows\BPSD\Stylus_Photo_RX620.bpsd".
2009-02-17 16:38:20 Unable to read from file "\Windows\BPSD\Stylus_Photo_RX630.bpsd".
2009-02-17 16:38:50 Started verifying backup file
2009-02-17 16:38:56 Total storing time: 3:19.79
Found any solution yet to this problem?
Thanks.

I'm using SPB Backup ... and I do have those warnings, but restored HD multiple times - it does work.
May be because I do not use JetSet (those files are from JetSet) ... so I do not care

Hi
Im using SPRITE BACKUP V 6.5.4 Build 8 and it works brilliantly, No errors or files that cant be backed up etc..
SPB has always missed out some file for me so I changed..
Hope this helps
Jon

bogdatov said:
May be because I do not use JetSet (those files are from JetSet) ... so I do not care
Click to expand...
Click to collapse
I use SPB BackUp, no warnings during backup, but when I restore I get a warning "can't create directory BPSD"
The directory is inWindows directory and after restore it is still there and I have no problems running the phone.
So what is JetSet?

spb backup problems with BPSD ... but Sprite is worse!
Since I had the same problem with spb backup I googled the issue and came across an official statement:
"You are not the first user of HTC Touch HD, who contacted us with such problem. We have contacted HTC and got the answer that the files contained in the "\windows\bpsd\" folder are drivers for different Epson printers. For more information about printing from your device, please refer to the User Manual.
Also, we have done some tests and they showed that these files are not critical to the overall quality and consistency of the created backup file. So, they can be ignored for now. In future version we will fix this problem."
(http://www.pocketpc.ch/htc-touch-hd/45277-spb-backup-sind-bpsd-dateien.html)
However, I restored several backups without any problem which was not the case with Sprite. So many errors until I finally managed to create a backup. But it was not possible to restore it. Really bad. Besides, no reply from my distributor when I reported the issue. I would never install Sprite again. With the spd issue I can live until it will be resolved in the next update.
Michael

me too. I installed Sprite-Backup on my Computer and after it found my Device HD. Since than it helps me a lot of my backups.
This Tool is an must have.

SPB Backup V2.0.0 Warnings
Thanks love2travel for the research!
Indeed it seems like they are Epson Stylus drivers. So I won't mind them... As a matter a fact I use an HP printer, so...
I'll be waiting for the next version available of SPB Backup...
Once again thank you all...

Be very careful of Sprite Backup. It doesn't backup the 'Object Store' which some third party applications such as Cash Organizer 2008 use for database storage.
Just trying to find out why this is the case with Customer Support (apparently it's a known issue acording to another thread I read).

Same error log here with SPB Backup ... but need to restore (RPMContacts problem after installed Resco Contacts Beta) and everything works fine (despite some error logs again).
That nice to hear its a common issue ... hope they'll fix it soon !!

Related

XDA tools nearly there but can't understand, any help plse

I have installed jeff summers version of xda tools. And though I think I understand what I am doing I am not totally convinced. Before I embark on cooking roms and upgrading etc I would like to be able to do the following:
1: Dump my current rom from my device to my PC I can do this using XDAtools OSImage but can only Can this only be NB1(windows CE(*.nb1) type files if I try to call this NBF I get the following error:
error opening C:\program files\xdatools\bootloader_v5_15.nb0ea for reading. the system cannot find the file specified.
error opening source bootloader from C:\program files\xdatools\bootloader_v5_15.nb0ea. error opening target device.
Can I dump my device memory into a file called ‘xxxx.NBF’?
2: When I try to upgrade my ROM by:
Start OSImage tool and select source as:
‘C:\PROGRAM FILES\XDATOOLS\BINARIES\ATT160204.NB1’
Select destination as ‘device memory (via programmeA) ‘
When attempting to load an ‘NB1’ ROM from my PC to my device memory (via programmeA) I always get the following message:
ProgrammeA not found - run with --register error opening target device.
I originally ran the programmeA with --register when first installed.
I have tried searching for a solution but to no avail. Any help appreciated.
Thanks John.
If you're trying to burn your original ROM back to the device that shouldn't be a problem. Use the [...] button to locate your .nb1 ROM for the source, and select Device Memory (via Programme A) as your destination.
Have you installed ProgrammeA.exe into the binaries folder of XDATools? That's the only thing I can think of.
Thanks I have tried this but believe the problem is the ProgrammeA file but it is definetly in the binaries folder. I am running win98SE but don't think this should be a problem. When you run jeffs tools it extracts itself out under program files and places all the required files in the right directories. Would appreciate it if any one out there can supply some help ?
Thanks John
I think I know what the problem is...
I have the same problem. If you look at the dos box that pops up you see that programmeA.exe looks in to the \\Binaries\English\ folder for a *.nbf file. It looks like you will have to provide it a *.nbf file in stead of a *.nb1

PushRouter Corrupted Files

Hi all, I recently moved to SPB Backup for my regular backup, but it is reporting that it is not able to fully backup the content of the following directory: \Windows\System\PushRouter\.
I had a look to such directory and I noticed that - close to the "clientqueues.vol" file that in my understanding is as it should be - also apparently corrupted files are available.
In detail, a directory & a file (very big size) that have names composed with strange characters. I tried to delete such files, but I failed both with Resco Explorer and Total Commander.
Do I need an hard-reset to recover from this situation or such "strange files" are instead welcome as part of Windows Mobile OS ?
Many thanks in advance

SPB Backup 2.02 / $UNINST$ file

SPB backup reports that it is unable to back up "windows\$UNINST$" file. Happens everytime, no other errors reported. When I tried to copy out the "windows\$UNINST$" file manually, windows explorer gives me an error that the file cannot be found. What actually is this file???? Does it exist at all or in ROM? Sprite Backup does not give any error message. Tried posting to SPB form whether this error would post a problem but as usual no reply after weeks.
Thanks

Copy protected files

Hi,
I'm trying to copy a dll in windows\ folder but get access denied. I tried to find a solution by searching the forum and google but had no luck.
Any suggestions?
I doubt it would work, but you could try using sprite backup to copy everything and then find some way to open the resulting sprite backup file ! afaik it is effectively a zip file !

Still errer after hard reset

Ho,i very afraid.
After hard reset I install spb backup,when process complete It show a lot of error,plz see below
2011-01-07 17:55:52 Backup process started...
2011-01-07 17:55:52 Backup file name: "\Storage Card\Backup_20110107.exe"
2011-01-07 17:55:52 Unable to read from file "\cemail.vol".
2011-01-07 17:58:06 Unable to read from file "\Windows\System\SQM\Sessions\PMWeek" because it is blocked by the following processes: "NK.EXE".
2011-01-07 17:58:07 Unable to read from file "\Windows\System\SQM\Sessions\Global" because it is blocked by the following processes: "NK.EXE".
2011-01-07 17:58:34 Unable to read from file "\Documents and Settings\default.vol".
2011-01-07 17:58:34 Unable to read from file "\mxip_notify.vol".
2011-01-07 17:58:34 Unable to read from file "\mxip_swmgmt.vol".
2011-01-07 17:58:34 Unable to read from file "\mxip_system.vol".
2011-01-07 17:58:34 Unable to read from file "\mxip_lang.vol".
what can I do to solve this,
and I think my phone now ;(,....sometime it shutdown itself when run any app......
thank you

Categories

Resources