No i don’t.
Windows 7 64 bit
I have a recurring BSOD that is not CTM related (happens either with or without CTM installed).
But after the BSOD it reboots reindexes while booting and on return there is no Minidump :o.
So I uninstalled and the Minidumps where now written to disk. So wont be testing it till BSOD’S are gone and till i know that the Minidumps will write in the future as it makes it hard with out them to troubleshoot.
But then I don’t plan on more BSOD’S.
Kevin
Hi Guys. Just ran the check tool suggested by Ronny. It came up with an error saying there was a problem with Rundl32 and it had stopped working.This was after having no luck installing Ctm as a message " Removable storage device was detected" popped up.
There was no such device to remove. Ronny directed me to a post where this has happened to other people.I assume this is being looked into and a fix sorted.
Security and Utiliies are:
- Windows Vista 32 bit os. 2) Cis without Av. Avast beta 5, security.3) Iobit System care pro latest version…4) C Cleaner latest version. 5) Firefox browser latest version.
the culprit must be your printer.
this issue will be fixed in next release.
Regards
- Your Operating System (32 or 64 bit) and Service Pack revision Windows 7 RTM 32bit
- Other Security and Utility Software Installed CIS
- Step by step description to reproduce the issue None…just there.
- How you tried to resolve the problem I uninstalled CTM. Back to normal.
- Upload Memory Dumps on crash if you encounter any -
- Attach screenshots to your posts to clarify the issue further
http://i37.tinypic.com/1dg9g.jpg
- Any other information you think that might be useful
Ok, this is the problem: my Windows 7 RTM build was genuine. Then CTM can along (was installed) and now I’m not genuine and have this watermark.
.>
how did you activate your win7?
Regards
Hi, I had same problem (and setup) than you and solved it without re-installing CTM. Just go to CTMs menu at computer bootup and select “compact” and CTM will defragemt snapshots and the problem is gone.
Using the code I got when I bought it…
But why would it make any difference?
I’m on W7 and still can’t install.
It tells me I have a external HDD installed
It should not make any difference.
I have tried your case, it works well.
Regards
I tried this again and the same happened!
Get “insufficient disk space on the boot disk” at install time. I really hope you can get this fixed. I’d love to be able to use this software!
Regards,
Nemis
- Your Operating System (32 or 64 bit) and Service Pack revision
Vista x64 SP2 - Other Security and Utility Software Installed
Windows Home Server Client, Avast!, WinPatrol Plus, Virtualdrive Pro 11.8 (set up with 3 virtual CDs L: M: N: and Ramdrive R:) - Step by step description to reproduce the issue
Attempt to install - How you tried to resolve the problem
Did not attempt to resolve - Upload Memory Dumps on crash if you encounter any
N/A - Attach screenshots to your posts to clarify the issue further
Attached 5 screenshots and a disk info listing showing all available disk info from various utilities - Any other information you think that might be useful:
Single Boot System (NOT dual boot)
physical disk 0 is a RAW volume
physical disk 1 is C: ntfs the single partition system drive with with 26GB free on a 69GB drive
physical disk 2 is partitioned as D: ntfs and F: ntfs
Rosewill RCR-102 52-in-1 USB 2.0 3.5" Internal Card Reader w/ USB port (Drives H: I: J: K:)
DVD-RW Drive S:
Caption: ST3750640A ATA Device
Description: Disk drive
DeviceID: \.\PHYSICALDRIVE0
Index: 0
Manufacturer: (Standard disk drives)
Name: \.\PHYSICALDRIVE0
Size: 750153761280
InterfaceType: IDE
SCSIPort: 0
SCSIBus: 0
SCSITargetId: 0
SCSILogicalUnit: 0
Serial: 2020202020202020202020205135304459384d4e
PNPDeviceID: IDE\DISKST3750640A______________________________3.AAE___\5&1E9E9C82&0&0.0.0
Caption: WDC WD50 00YS-01MPB0 SCSI Disk Device
Description: Disk drive
DeviceID: \.\PHYSICALDRIVE2
Index: 2
Manufacturer: (Standard disk drives)
Name: \.\PHYSICALDRIVE2
Size: 500105249280
InterfaceType: IDE
SCSIPort: 2
SCSIBus: 1
SCSITargetId: 1
SCSILogicalUnit: 0
Serial:
PNPDeviceID: SCSI\DISK&VEN_WDC_WD50&PROD_00YS-01MPB0\4&12A0B57C&0&010100
Caption: WDC WD74 0GD-00FLC0 SCSI Disk Device
Description: Disk drive
DeviceID: \.\PHYSICALDRIVE1
Index: 1
Manufacturer: (Standard disk drives)
Name: \.\PHYSICALDRIVE1
Size: 74348305920
InterfaceType: IDE
SCSIPort: 2
SCSIBus: 0
SCSITargetId: 0
SCSILogicalUnit: 0
Serial:
PNPDeviceID: SCSI\DISK&VEN_WDC_WD74&PROD_0GD-00FLC0\4&12A0B57C&0&000000
Caption: Generic USB CF Reader USB Device
Description: Disk drive
DeviceID: \.\PHYSICALDRIVE4
Index: 4
Manufacturer: (Standard disk drives)
Name: \.\PHYSICALDRIVE4
Size:
InterfaceType: USB
SCSIPort:
SCSIBus:
SCSITargetId:
SCSILogicalUnit:
Serial:
PNPDeviceID: USBSTOR\DISK&VEN_GENERIC&PROD_USB_CF_READER&REV_1.01\18E3312D81B0&1
Caption: Generic USB MS Reader USB Device
Description: Disk drive
DeviceID: \.\PHYSICALDRIVE6
Index: 6
Manufacturer: (Standard disk drives)
Name: \.\PHYSICALDRIVE6
Size:
InterfaceType: USB
SCSIPort:
SCSIBus:
SCSITargetId:
SCSILogicalUnit:
Serial:
PNPDeviceID: USBSTOR\DISK&VEN_GENERIC&PROD_USB_MS_READER&REV_1.03\18E3312D81B0&3
Caption: Generic USB SD Reader USB Device
Description: Disk drive
DeviceID: \.\PHYSICALDRIVE3
Index: 3
Manufacturer: (Standard disk drives)
Name: \.\PHYSICALDRIVE3
Size:
InterfaceType: USB
SCSIPort:
SCSIBus:
SCSITargetId:
SCSILogicalUnit:
Serial:
PNPDeviceID: USBSTOR\DISK&VEN_GENERIC&PROD_USB_SD_READER&REV_1.00\18E3312D81B0&0
Caption: Generic USB SM Reader USB Device
Description: Disk drive
DeviceID: \.\PHYSICALDRIVE5
Index: 5
Manufacturer: (Standard disk drives)
Name: \.\PHYSICALDRIVE5
Size:
InterfaceType: USB
SCSIPort:
SCSIBus:
SCSITargetId:
SCSILogicalUnit:
Serial:
PNPDeviceID: USBSTOR\DISK&VEN_GENERIC&PROD_USB_SM_READER&REV_1.02\18E3312D81B0&2
[attachment deleted by admin]
pls assign a drive letter to the Hard-Disk0 and inject yout removable disks , then try again.
Before my bug report I would like to state that although I am using a dual boot windows server 2008/vista, I am not using time machine on a production machine, and that time machine worked almost flawlessly on the server (I encountered the bug on vista).
My operating system is a dual boot 32 bit vista sp2, windows server 2008 sp1 with comodo firewall 3.11.108364.552 and avast 4.8 home edition.
The first screenshot shows the bug I am most concerned about, time machine showing deleted snapshots still filling the partitions free space.
I used virtual box to create and store large virtual hard drive files on my vista partition and took time machine snapshots, eventually I ran out of free disk space when I attempted to take the final snapshot. The second and third screenshots below show the low disk space warning I got and the 0 MB free space.
I first tried to resolve the problem by deleting all other snapshots except the baseline, unfortunately after deletion time machine still showed 0 MB free space. It showed the same amount of space used by other the deleted snapshots both before and after deletion, the fourth screenshot below clarifies this.
I continually got the low disk space warning shown on the fifth screenshot below even though I had plenty of free space on the C drive.
I then tried to resolve the problem by specifying a restore schedule that removed all other snapshots except the baseline after restoring. The sixth screenshot below clarifies exactly what I did.
This initially appeared to fix the problem, and time machine showed that apart from the baseline only 565 MB was used by other snapshots on my disk, the seventh screenshot below shows this.
What follows may not be a bug but merely be a result of my ignorance of the workings of vista or time machine. I thought it strange any memory was allocated to other snapshots when the baseline was the only snapshot remaining. I therefore left the computer unused and periodically checked the amount of memory used by the other snapshots. The series of screenshots from the eigth to the fourteenth below show that in the space of roughly two and a half hours 63 MB of extra space was used by them. I did nothing else but store less than 3 MB of screenshots on the partition during this time.
After these bugs I restored my system to a point before the installation of time machine using active[at]diskImage, then reinstalled time machine.
Regarding time machine installation on a dual boot machine, I found that the option to choose which operating system to protect was greyed out on the final operating system I installed (the final operating system installed has its C drive protected by default). The fifteenth and sixteenth screenshots below are from two installations, one where vista was installed first, the second where windows server 2008 was installed first.
When I installed the previous beta, the “hidden” vista partition was protected, when installing this current beta no option was given to protect the “hidden” vista partition (as shown on th previous screenshots). After installation it is shown as unprotected.
I tried uninstalling from the pre boot screen, but found I also had to uninstall from the control panel within both operating systems.
When removing external hard drives I routinely had to use unlocker (http://ccollomb.free.fr/unlocker) to unlock processes preventing removal even before I installed comodo time machine. Since installation I have noticed an increase in the number of processes preventing removal, this also happens with pen drives which almost never happened before. The processes preventing removal are usually multiple instances of explorer.exe (between 2 and 8), the seventeenth screenshot below shows this from an unlocker window.
[attachment deleted by admin]
- Assigning a drive letter to Drive 0 is not an option. The CTM software needs to simply ignore RAW devices.
- Inject removable disks? This is a multi-format 52-in-1 card reader with 4 slots for different media types. I don’t even own all the different media types that will fit in all 4 different type slots.
No offense, but your suggestions are not helpful to me at all, nor do they make sense for when this software goes out to thousands, or hundreds of thousands, of users. The CTM software simply needs to take these conditions into consideration and not error out.
“Goback” type software, just like backup/restore software needs to be bullet-proof. I’m happy to report the errors to the best of my ability so the developers can know all the buggy areas ahead of time and account for them before it is released to production. Any software like this that might require you to change the configuration of your machine to make it work would not be ready for prime time. I think there is just some work the devs need to do so that all possible physical/logical drive/partition types are taken into account. And make sure their software does not touch or interact with any drives that are not valid CTM target drives.
Regards,
Nemis
- I think you choose to protect only C partition in pic 1, because the protected space is 70G or so. If your virtual box consumes lots of disk space, it makes sense that ctm reports low space warning.
- All data written to disk before taking a snapshot are counted into “Space used by other snapshots”. So if you write 10G data after installation without taking any snapshot, the “Space used by other snapshots” of baseline will be 10G-12G, which includes page file flush, system writes and your data.
- In latest version, only selected partitions are protected, so vista hidden partition is not protected.
Hello Tupp. Just want to say wow…you really put some time into this bug report.
Im a long time user of Rollback (5 yrs). I’m fairly certain that CTM is a makeover of Rollback with some very nice improvements. But fundamentally they work the same. My point is that I’ve heard many complaints about Rollback (and now CTM) using up harddisk space.
Alot of these complaints were resolved by choosing “Snapshot Defragmenter” or in CTM’s case it will be “Compact” under the “Settings>Protection Settings” tab. Just thought you should give this a try since i didnt read it anywhere in your detailed post. Hopefully its this simple to fix.
If “Compact” is anything like Rollbacks “Snapshot Defragementer”, it performs a very important function of recovering unused space from deleted snapshots and files!
Judging from your bug report I believe this is the case for you. You decribe deleting snapshots all the way back to the baseline and you also described setting up a schedule as a last resort in order to restore back to the baseline. This is the vital clue I needed to suggest a “compact”. If you had chosen to “Reset Baseline” then i believe your harddisk space would have been recovered as expected ( and may still be used even now instead of “compact”).
You see, the purpose of CTM (and Rollback) is to protect the snapshots and the files they contain. This can only be achieved by redirecting any writes or changes to sectors to blank sectors on your HD. Now when you restore back to a snapshot or delete a snapshot, CTM cannot instantly release the previously used sectors for many complicated reasons that are not important for now. Only when you perform a “compact” procedure can CTM look at the “released” sectors and truely release the ones it can, resulting in you getting your free space back as expected. But remember, CTM will release the sector only if its NOT being used by another snapshot. This is an important distinction that many people cant get their heads around.
I hope my reply is conherant and helps you out in your case :SMLR
EDIT: I just reviewed my post and realised that a caution note should be added to “Reset Baseline” feature. “Reset Baseline” will delete all your snapshots and return you to the installation snapshot. Therefore, you’ll lose all current data. Rollback has this feature as well but also has “Update Baseline” which enables you to chose which snapshot you want to make as Baseline snapshot. I guess CTM will introduce this into their beta soon or are keeping it up their sleeve as a ‘new feature’ in an upgrade.
My operating system is a dual boot 32 bit vista sp2, windows server 2008 sp1 with comodo firewall 3.11.108364.552 and avast 4.8 home edition.
There seems to be a contradiction between the total used disk space reported by time machine and windows explorer. The properties of a snapshot states the total used disk space is about 57.8 GB of 70 GB (roughly 13 GB free), whereas windows explorer states there is about 31.8 GB of free space. I have attached a screen shot to show the details.
Thanks for the suggested fix for my previous problem, I have not yet had time to try it out.
[attachment deleted by admin]
13G is the actual number, it shows total free space on your disk. You have no more than that though you have 31.8G in file system view. If free space in explorer is smaller than that in snapshot properties, then you can use up to the explorer value.
Tupp, I still believe once you run “Compact” then these numbers should more closely reflect the actual totals. If they dont then I’m at a loss.
Attached is a shapshot of a fresh install of CTM in aVM running Vista SP1. Just for extra info i also showed the properties for Drive C: as seen by Windows Explorer for further comparison. I dont see any major discrepancies in this VM. I did run the “compact” feature before calling up the shown displays.
Please show us your results after you run “compact” when you have time. 
[attachment deleted by admin]