Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit. Sed posuere consectetur est at lobortis. Vestibulum id ligula porta felis euismod semper. Donec ullamcorper nulla non metus auctor fringilla. Aenean lacinia bibendum nulla sed consectetur. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Cras mattis consectetur purus sit amet fermentum. Morbi leo risus, porta ac consectetur ac, vestibulum at eros. Sed posuere consectetur est at lobortis. Etiam porta sem malesuada magna mollis euismod. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Aenean eu leo quam. Pellentesque ornare sem lacinia quam venenatis vestibulum. Curabitur blandit tempus porttitor. Sed posuere consectetur est at lobortis.
Yes, I have a pc with Windows XP sp3, and had exactly the same problem, including the occasional blue screen. I originally got SystemWorks for GoBack ONLY! I am uninterested in the rest of the stuff they wrapped around it. I am a long time user of GoBack, when it was still stand alone. It was the only thing that could keep my Windows ME system running, way back when that system still ran. Now, the whole GoBack package is just broken. I tried disabling all of the pieces except for GoBack and even updated to the latest that LiveUpdate could find and it still locks up or crashes. The only way I could get past this and get the system to boot is to disable GoBack. I finally had to uninstall the whole package and put it on the shelf in search of a replacement to GoBack. I finally found something that is an adequate substitute, but does not take real-time snapshots as GoBack does. It only takes scheduled system snapshots. I am very disappointed that GoBack no longer exists as a stand alone entity, and it never conflicted with anything, like someone elses’ internet security package.
In order to help with either of these issues, we’ll need more information on the Norton products you have installed. Please provide the versions and Operating Systems installed. Thanks!
Moved message from djmalisk to its own thread for better exposure.
My system stats are:
1. Alienware Mobile Desktop with 3.2GHz Hyperthreaded CPU
2. 1Gb DDR2 ram
3. 2 60Gb internal hard drives w/ RAID controller configured for non-raid configuration in the BIOS
4. Windows XP sp3 with all latest Windows update patches
5. Nvidia 6800 GPU
6. Up to date device drivers
7. Panda Internet Security 2008
8. Norton SystemWorks Basic
9. Diskkeeper set to defrag on screensaver mode (which so far has not kicked in while GoBack was running). I have not been away from the system long enough for it to kick in.
I originally purchased SystemWorks exclusively for GoBack because it contains the only version that is supposedly compatible with XP sp2/sp3. I am not interested in the rest of the package since I have other things that can accomplish the same basic thing built into Panda. Unfortunately there is no way to install just GoBack. I have used Norton Internet Security in the past as well as McAfee Internet Security and Computer Associates Internet Security. All took too many resources and/or pulled too heavily on the CPU even when idle, dug themselves far too deeply into the system, and were too inaccurate for virus removal. Panda is far better with a much smaller footprint and is much less demanding on the system, and updates far more often than the others (usually 2 to 3 times a day), and even had rootkit detection and removal. The fact that we use Norton corporate at work (Bank of America) just confirms to me how much of a hog it is since I have to reboot every day to recover resources lost in the overnight scans that run daily, and it never updates the signatures more than once a week. I am hardly aware Panda is even running, so I will not swap. If is a choice between Panda and GoBack, I'll go with Panda. Before it was integrated with SystemWorks, GoBack use to work fine with any Internet Security package I used, so I only assume it is SystemWorks that will not cooperate with other packages.
After installing GoBack, I first tried to run it as is and it would run for a few hours, and then lock up or blue screen. Then I would restore from a Ghost image I made with the version of Ghost that came with my Alienware system, and then reinstalled GoBack again. Then, I would use the configuration to turn off all SystemWorks processes, go through the services and disable all of the SystemWorks related services except the GoBack service, and used msconfig to stop the autostart tooltray process from starting on startup, and reboot and the system seems to run ok for a short time until I get a blue screen or lockup again. When restarting, the system just freezes most of the way up. I eventually found the only way to get it to start up fully is to disable GoBack from the boot menu. The system works fine after that. No messages are logged to the system logs at any time. At one point after the umpteenth reinstall, I even tried to use GoBack to roll back to a point before the crash with no luck. I even tried to roll back to the start of the history and still no luck. So, I just disabled to get it up, and then uninstalled. The system has been running fine ever since.
I also have had GoBack 4 running on my Windows XP sp1 Toshiba for the last 5 years and have had no problems. I really wanted to get it running on my Alienware but have been unable. I have pretty much stopped pushing it at work because I just can't get it to work reliably at home. I also have Diskkeeper running on this system and never got any conflicts, even when it is running a defragment job.
Stand alone GoBack was not tested on SP3 (it was tested and certified on SP2). I understand that your wish is to use GoBack, but keep in mind that high disk actiivity can cause problems with GoBack. Have you tried installing stand alone GoBack onto the system? What RAID controller are you using? Is it set as AHCI or JBOD?
I originally purchased SystemWorks over 6 months ago because I knew that GoBack 4 would not work with sp2+, but the one with SystemWorks supposedly does/did. At the time, I was running sp2 and Panda, and it was working the very same way it is working on sp3... the whole nine yards, though at the time I did not attempt to disable all but GoBack. I then uninstalled it and did not touch it again until now, because I was needing to reload the clean ghost image I made back before I bought SystemWorks.
Since I have been using GoBack with my older system for many years, I am aware of its problems/limitations. I know that high disk activity causes it to suspend its history until the activity ceases, and this usually causes it to loose all history to that point. However, this is an acceptable risk since it keeps a real time history, which has helped me recover the system without loss of information many times. It was the only thing that kept my old Win ME system running without having to rebuild it every week.
There appears to be no way to install just GoBack since it is integrated into SystemWorks. The installer does not provide any options that just install GoBack. There are some SystemWorks components that install regardless. This time, I did try to install as little of SystemWorks as the installer would allow, but it apparently does not strip it down enough.
I am not absolutely sure which RAID controller I have other than the fact it is a SATA controller, because this Alienware system was custom built at the time I bought it, and they used their preferred RAID controller at the time. However, the device driver shows the following info...
WinXP Promise SATA378(tm) IDE Controller
Manufacturer: Promise Technology
I had them configure it for standard ATA mode in the BIOS rather than RAID I or RAID II. This makes it work like an ordinary 2 drive configuration, meaning the C and D drives are treated as separate drives, rather than one huge drive or a mirrored drive setup. I do not know what AHCI or JBOD means. Never heard those terms before. I believe they chose this controller because this system is originally designed as a high performance gaming system (and I do play some games on it as well), with 2 high speed 7200 rpm 60 GB drives, and they used the fastest and most cost effective controller that was available for the time (about 3 years ago).
NSW does not allow you to install a subcomponent without the top level application. Where did you see that GoBack 4 does not work on SP2?
JBOD is Just a Bunch of Disks. It's a RAID level that isn't used that often.
AHCI is Advanced Host Controller Interface, which is an Intel proprietary way of doing what you are. This is only in a limited number of controllers.
Promise cards are pretty good. Let me check something out for you. Either myself or Tony will be sending you a Private Message.
Basically, since it always worked on my sp1, and on my earlier (now deceast) Win ME, systems without incident, but would not work reliably on my sp2 system, then I fealt that it was reasonable to deduct that it does not work on sp2. The only thing I could think of that could cause this to be false reasoning was if it does not work with RAID configured hard drives. I did find information online that said specifically that RAID configurations, particularly with SATA, are not officially supported, likely causing crashes, lockups and other nasty problems. Since my system is not configured for RAID, but rather a standard ATA 2 drive setup, then this SHOULD not be an issue. Further, the size of my hard drives were well within the terabyte limitation. Also, since I found one message board site that had a posting from someone who had a SATA based RAID setup configured for ATA, and he stated he had no problems with his configuration, then I fealt this further supported my assumption of sp2 incompatibility. Additonally, I also tried to setup GoBack to only protect my C: drive, and not the D: drive, with the same erratic results. This is why I abandoned the attempt to get GoBack 4 working and when I found SystemWorks a year or so later with GoBack integrated, I guessed this version did finally support sp2+, and so I bought it, but still got the crashes, lockups and startup difficulties. When I upgraded to sp3 a few weeks ago, I tried again to give GoBack another try, making sure that I did a LiveUpdate to get the latest version (though I noticed GoBack was the only component that did not have an update) thinking it should support sp2/sp3 by now. Still got the same crashes and lockups however, this time thinking it was a conflict with SystemWorks and not GoBack.
Strange thing though. It would work fine for a few hours after installing it, but after several reboots, the problems started. At no time while it appeared to work did I make any configuration changes or hard drive configuration changes. It just started to crash and lockup mysteriously, the last time while I was online checking email. Once this started, there was no way to get past the problems until disabling GoBack.
One other thing I do have is DiskKeeper to periodically defragment the hard drive. However, I also have this on my older sp1 system and they have lived together without incident for several years. By defragmenting on a scheduled basis, the defragment jobs go fairly quick and do not cause excessive disk activity. I have very rarely seen GoBack suspend operations because of a defragment operation on the older system, and then only if the hard drive has excessive fragmentation causing a lengthy defragment process. But, even this has never caused erratic behavior (crashes and lockups) on the older system.
The lockups/freezes/etc are not related to SP2. I have a test machine that runs GoBack 4.0 on XP SP3. Have you checked the Windows Event logs for errors/faults/hung apps? That would be a usefull starting point to figure out what is going on with GoBack.
Yes I did check both the application and system logs… no messages were logged related to GoBack. This makes sense because when the system freezes, it is a hard freeze forcing me to turn the power off… no chance to properly shut down. When starting up afterward, it hard freezes just after presenting the Windows XP logo screen, causing me to power it off. The system logging has not had a chance to start up at this point apparently. The only way to get past and get a successful startup is to disable GoBack from the GoBack boot menu. At no time did it log any messages. Also, the DrWatson was never triggered so no message info was collected and sent to Microsoft. I know that DrWatson is turned on because it frequently comes up after a blue screen of death, and it was not getting triggered.
I'll send you a Private Message.