Jump to content

palter

Members
  • Posts

    31
  • Joined

  • Last visited

Everything posted by palter

  1. Strange. The 6.5 client works fine for me on RHEL 3. (For that matter, the 6.0 client seemed to work as well before I upgraded to 6.5.) What kind of problem are you experiencing?
  2. I have the same type drive. First, the drive doesn't support hardware compression. Use software compression. Second, the quoted maximum rate is for a SCSI controller. On IDE, it won't be as fast. (Further, I believe the 240 MB/min presumes software compression as well which means the real hardware maximum speed is 120 MB/min.)
  3. The Linux client only works on x86 (i.e., Intel, AMD) based systems. It will not work on Macs. - Gary
  4. [i can't reply to this post directly in its original forum and I figured that this was the most appopriate alternate forum.] Thanks for the fix. But, for completeness sake, I think you should fix the permissions on the "Retrospect Client" folder and its contents in /Applications as well. They appear to be world-writable by default which isn't good. (Forutnately, the permissions on pitond are secure enough to prevent an unprivileged user from replacing it with something malicious that could run as root.) - Gary Palter Quote: Run this AppleScript on computers installed with Retrospect's Mac OS X Client software to fix the following bug: Incorrect permissions are assigned to the RetroClient folder and, in some cases, to the StartupItems folder. Note: The following permissions will be set: drwxrwxr-x root admin /Library/StartupItems drwxrwxr-x root admin /Library/StartupItems/RetroClient -rwxrwxr-x root admin /Library/StartupItems/RetroClient/RetroClient -rwxrwxr-x root admin /Library/StartupItems/RetroClient/StartupParameters.plist Filename: client_security_patch.sit Supported versions: 5.x client System's supported: Mac OS X only
  5. STT3401A-ED is a Travan 40GB drive, right? (Based on the model numbers listed at Seagate's site, this appears to be the most likely candidate.) You need at least Retrospect 5.6 with Driver Update (RDU) 3.1.102, Retrospect 6.0 with RDU 3.3.105, or Retrospect 6.5 to use this drive. - Gary
  6. I ran some tests over the weekend using the new Mac OS X client referenced above. The new client successfully backed up my Mac OS X client without the assertion failure. Further experimentation showed that the client now explicitly excludes the named UNIX pipes created by Norton Personal Firewall 2.0. Presumably, it excludes all named pipe files, right? I originally reported this assertion failure in August 2002 and found the cause and a workaround about a month later. At the time, Robin Mayoff told me that an report (#893000) had been filed with engineering. Yet, I was never informed that you had resolved the problem. Why not? Also, I note that the updates page still lists the previous version (5.0.540) of the Mac OS X client. Is this new version (5.1.106) not officially released yet? And, is there a list of bug fixes and improvements for the new version? (I noticed that the download didn't include a ReadMe file.) Finally, I noticed that I no longer get the error File "Herman:Applications:Retrospect Client:Retrospect Client.app:Contents:Resources:retropds.22": can't read, error -1105 (improper seek) while backing up my Mac OS X client and said file is, in fact, copied to the backup set. Thanks for that fix! - Gary
  7. I just received a copy of the latest PC Connection catalog. Much to my surprise, I found a listing for Retrospect Professional 6.5 which claims "Now supports Windows Server 2003". Any comment? - Gary
  8. Just for the record ... I spoke with a friend who had the same tape drive as myself and was using Retrospect for backup. He reported that he never got an error when switching tapes. So, it became obvious that there was something wrong with my system. Well, about three weeks ago, my tape drive died. It would refuse to recognize any tapes. (I.e., I'd insert a tape and the drive would just sit there. Normally, on insertion, a TR-5 drive spins the tape a bit to verify that it's OK.) Of course, this happened the day after the warranty expired. I have upgraded to a Seagate Hornet 40 (Travan TR-7) internal ATAPI drive. It's working flawlessly so far. Thanks for putting up with me through all this, - Gary
  9. I upgraded my Linux client to Red Hat 8.0 earlier this week. Retrospect had no trouble backing up said client after the upgrade.
  10. Yes, it still works for me. You might want to use the volume browser to look at your Macintosh client's boot volume. You can then apply the selector in the browser window to see if it's properly selecting the files.
  11. Thanks to some information in another thread, I was able to discover the cause of the assertion failure. It occurs whenever Retrospect tries to backup a UNIX named pipe. (You can tell that a file is a named pipe in that the 'ls' command will display a 'p' as part of its mode string (e.g., 'prw-rw-rw-').) In particular, I am running Norton Personal Firewall 2.0. It creates three UNIX named pipes with the pathnames /private/var/log/Npfkernel.log.fifo /private/var/tmp/NpfCmds.fifo /private/var/tmp/NpfResponse.fifo Any attempt to backup these files produce the assertion failure at "hfslvtree.cpp-278". I created a selector to exclude these files (and other named pipes) and was able to successfully backup my Mac OS X client. The selector I used is Mac OS regular file flag is not set and Mac OS symbolic link flag is not set and Mac OS hard link flag is not set (In theory, this selector would also exclude device files but they reside in /dev which is automatically excluded by the Mac OS X client anyway.) I hope this information is helpful. - Gary Palter
  12. Thanks for the information; it allowed me to discover the reason my backup attempts failed. I am running Norton Personal Firewall 2.0. It creates three UNIX named pipes with the pathnames /private/var/log/Npfkernel.log.fifo /private/var/tmp/NpfCmds.fifo /private/var/tmp/NpfResponse.fifo Any attempt to backup these files produce the assertion failure at "hfslvtree.cpp-278". I created a selector to exclude these files (and other named pipes) and was able to successfully backup my Mac OS X client. The selector I used is Mac OS regular file flag is not set and Mac OS symbolic link flag is not set and Mac OS hard link flag is not set (In theory, this selector would also exclude device files but they reside in /dev which is automatically excluded by the Mac OS X client anyway.) I hope this information is helpful to anyone else having this problem. - Gary Palter
  13. Any response to my previous post dated August 19th? For the record, I've also tried all the trouble shooting tips listed in Melissa's original reply. They make no difference; I still get the 104 error whenever I fill a tape. - Gary Palter
  14. [i'm just a long-time Retrospect user; I don't work for Dantz] I'm the one who first reported the problem with backing up a Mac OS X client with Retrospect 6.0. For the record, I received the following note from Retrospect back on the 14th of August: "We have logged a bug for this problem and our engineers will be investigating the cause of this error in more detail." I can easily believe that they're still working on the problem; I suspect it's not an easy one. For JamieG: You say that you've successfully backed up a OS X client. I'm curious. How many files are on the OS X volumes that were backed up? How many files were backed up? Have you used any disk utilities (e.g., Norton Disk Doctor, DiskWarrior) on the OS X volumes or used any optimization software (e.g., Norton Speed Disk). What kind of backup medium are you using? [i'm just looking for differences between your situation and ours that might explain your success.] - Gary Palter
  15. [i don't work for Dantz; I'm just a long time Retrospect user.] The hardware compatibility database says that the HP SureStore T20 isn't qualified for use with Retrospect on a Macintosh; it is qualified for Retrospect on Windows. - Gary Palter
  16. [i don't work for Dantz; I'm just a long time Retrospect user.] There is no Retrospect Express updater yet. What you've downloaded is the new version of Retrospect Client. Retrospect Client is installed on systems that are to be backed up remotely over the network from another system (either Mac or Windows) running Retrospect. Dantz hasn't yet announced an update for Retrospect Express to support OS X 10.2 (Jaguar). - Gary Palter
  17. Windows 2000 Professional with Service Pack 3. The Device Manager reports that a driver for "HP T20 SCSI Sequential Device" is loaded. When I click on Driver Details, the Device Manager lists the following file: C:\WINNT\System32\DRIVERS\hpt4qic.sys (Version 5.00.2159.1) However, as soon as I do anything in Retrospect that actually accesses the drive (e.g., opening the Devices window), the status in the Device Manager changes to Disabled. I asked this in my original post but I guess it was missed: What does Retrospect mean when it says it's "Writing index"? Is this something written to the tape and, if so, where on the tape? - Gary Palter
  18. Melissa (or anyone else from Dantz), Any response to my latest update above posted on Tuesday, 8/13? - Gary Palter
  19. [i'm just a Retrospect user; I don't work for Dantz.] Given that one of your clients is running OS X Server, you need the Multi-Server edition of Retrospect. (See http://www.dantz.com/products/wincompare.html for a detailed comparison of the various editions.) If none of your clients are servers, you could use the Professional edition. You'd have to buy additional clients as Professional only supports 2 clients out of the box. - Gary Palter
  20. Let me try a more detailed explanation ... The problem occurs whenever Retrospect fills any and all tapes I use. It is not limited to any one tape or backup set. It also doesn't matter whether the tape was empty before Retrospect fills it (i.e., whether Retrospect is appending to an existing member of a backup set or completely fills a new member during a single backup operation.) After Retrospect reports the error, it asks for a new tape to be added to the backup set. It then proceeds to finish the backup operation that was in progress. Retrospect doesn't report any problems during its verification pass. Further, if I retrieve the file that was being copied to tape when the 104 error occurs, Retrospect is able to restore it without problem. (A bit-by-bit comparison with the original file shows that it is identical.) And, Retrospect asks for both tapes in order to retrieve the file. - Gary Palter P.S., I had the same problem with Retrospect 5.6.
  21. Thanks for the information but ... I'm not getting error 105; I'm getting error -104 (unexpected end of media). - Gary Palter
  22. I am using Retrospect Professional, version 6.0.206. I am using an HP SureStore T20 tape drive connected via an Adaptec AHA-2930CU PCI SCSI controller. I am using Travan TR-5 media (10GB native, 20GB compressed capacity). The drive doesn't support hardware compression; so, I've enabled Retrospect's software compression. When Retrospect nears the end of the tape, it stops copying files and switches to "Writing index...". However, it always generates an "unexpected end of media" error while writing the index. Is there anything I can do to avoid this problem? - Gary Palter
  23. According to the web site, http://www.dantz.com/support/support_matrix.html, a support incident for Retrospect Express is $40; a support incident for other editions of Retrospect is $70. Now that the Windows version no longer has an Express edition and Professional is the lowest level edition available for Windows, that leads to my question. What is the price for a support incident for Retrospect Professional? Thanks, - Gary Palter
  24. I just sent the following message to tech_support@dantz.com as suggested in the assertion log. Can anyone here help? (I have no idea if I'll receive a reply to that email.) [For the record, I reported this problem during the 6.0 beta test.] I am using Retrospect Professional 6.0, version 6.0.206. I am running a script that backs up the local machine (Windows 2000 Pro) and a single Mac OS X client to a tape (Travan TR-5) backup set. The Macintosh is running Mac OS X 10.1.5 and Retrospect Client version 5.0.536. The Macintosh client's startup volume contains approximately 200K files. After successfully backing up the local machine's two volumes (70K and 400K files, respectively), Retrospect gets the error reported shown below while copying files from the Macintosh client. (I can't say exactly how far into the copy operation or what file was being copied as I wasn't in the room at the time of the failure.) Clearly, this error means I have no means to backup my Macintosh system. Help! - Gary Palter _______________________________________________________________________________ 1028957132: PmcOpen: connect() failed with error 61: Connection refused 1028957132: ipludAddMembership: adding membership for 0.0.0.0 1028957132: iplud: bound to address 28.192.177.208 1028957138: IPNSRegister(0): registered: "Herman"/"679b0fc2b4f94685" 1028957145: IPNSRegister(0): registered: "Herman"/"679b0fc2b4f94685" 1028957145: bindToValidBootPort: gServerPID has been initialized to 70 1028957146: bindToValidBootPort: task_set_special_port succeeded 1028979724: Connection established by 31.192.177.208:1064 1028985036: ConnReadData: Connection with 31.192.177.208:1064 was reset _______________________________________________________________________________ 1028942181: fscStatFSRef: FSRefMakePath failed, error -2110 1028942181: fscStatFSRef: FSRefMakePath failed, error -2110 1028942181: fscStatFSRef: FSRefMakePath failed, error -2110 1028979807: fscStatFSRef: FSRefMakePath failed, error -2110 1028979807: fscStatFSRef: FSRefMakePath failed, error -2110 1028979807: fscStatFSRef: FSRefMakePath failed, error -2110 _______________________________________________________________________________ Retrospect detected a failure: This report documents an unusual condition detected by Retrospect's internal integrity checking. This might be caused by a software bug, but can also be the result of an incompatibility, hardware malfunction, damaged system software, or other problems. Details on possible causes and troubleshooting advice are given in Technical Note 307, Internal Consistency Check Failed, which can be found on Dantz's website: http://www.dantz.com/support For more information and assistance, please send this report to Dantz Technical Support. You should include a brief note describing the steps that led to this failure along with your name, address, and registration number. Internet: Electronic mail: tech_support@dantz.com Telephone: Voice: 925/253-3050 FAX: 925/253-9099 Mailing address: Dantz Development Corporation Attn: Technical Support 4 Orinda Way, Building C Orinda, CA 94563 USA XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX OS: Windows 2000 version 5.0 (build 2195), Service Pack 3 Application: C:\Program Files\Dantz\Retrospect\Retrospect.exe, version 6.0.206 Exception occurred on 8/10/2002 at 8:56:41 AM Error info: Assertion failure at "hfslvtree.cpp-278" Exception code: E0000000 ASSERTION Fault address: 77E9E8BB 0001:0001D8BB KERNEL32.dll Thread ID: 000004C0, Name: Execution thread EAX:10D972F8 CS:001B EIP:77E9E8BB EFlags:00000206 EBX:C0000000 SS:0023 ESP:10D972F0 EBP: 10D97348 ECX:00000000 DS:0023 ESI:10D97388 FS: 003B EDX:6007367C ES:0023 EDI:10D97318 GS: 0000 Module Fn (symbol or seg:offset in DLL) Args =============== ================================= ======================================================================= KERNEL32.dll 0001:0001D8BB E06D7363 1 3 10D9737C 10D977A8 10D97824 E06D7363 1 MSVCR70.dll 0001:0001AA05 0 0 10D977A8 10D97824 C0000000 60073690 10D97398 10D96F38 bedrock.dll DebugHandler::Throw +53 E0000000 1 1 10D973EC 10D974EC 60044E0D E0000000 1 bedrock.dll assertLog +1B E0000000 1 10D973EC 'essA' 'oitr' 'af n' 'ruli' 'ta e' bedrock.dll Debug +59 605440F4 00000116 10D986D0 1068A064 '9N_t' 6020161B 0 0 MACVOL.DLL mltrUpInfo +150 137540C4 1385600C 10D986D0 0000B723 13754400 10D977EC 60609BE1 137540C4 MACVOL.DLL osxhfslvUpInfo +29 137540C4 10D986D0 0000B723 0 0 10D98448 'FILE' 10D98448 meson.dll ModuleData::send +652 137540C4 'Tupi' 10D986D0 0000B723 0 0 10D98448 'FILE' ENGINELO.DLL xenReadBegin +2D8 136CC2DC 10D98448 10D986D0 10D98A04 10D98A80 000081A4 0 0 meson.dll ModuleData::send +652 136CC2DC 'VRdB' 10D98448 10D986D0 10D98A04 10D98A80 000081A4 0 MACVOL.DLL mvrmFchProc +300 138842A4 137A1BEC 1 'RdBg' 13A7A0B0 000002A8 138842C4 10D98A48 MACVOL.DLL mvrtNetAvail +3F 138842A4 137A1BEC 1 'RdBg' 13A7A0B0 000002A8 137A1C04 10D98F1C meson.dll ModuleData::send +652 138842A4 'nTAv' 137A1BEC 1 'RdBg' 13A7A0B0 000002A8 137A1C04 NETWORK.DLL tranAvail +44 137A1BEC 13A7A00C 'RdBg' 13A7A0B0 000002A8 'dsi.' 01000100 1 NETWORK.DLL necoIncoming +48F 13A7A00C 107EF144 000002AC 107EF210 0000000C 000002B8 10D98FCC 607207AB meson.dll ModuleData::call +50B 13A7A00C 60710175 107EF144 000002B8 107EF210 0000000C 000002B8 10D98FCC NETWORK.DLL soccDispatch +89 107EF144 0 107EF210 -1 3 13896A1E 00006E02 10D98FF4 NETWORK.DLL soccRecv +195 107EF144 000001C0 1 10D98FF4 60721CA8 00000010 107EF15C 107EF210 NETWORK.DLL soccCallback +182 107EF144 1 0 0000040C 00000401 107EF15C 0 1 NETWORK.DLL soctCBFlush +BE 107EF144 10D99098 10D99114 C0000000 10D99060 77E1711F 107EF15C 0 NETWORK.DLL soctCallback +B5 107EF144 001E02E8 00000401 0000040C 1 107EF144 10D99120 77E11D0A meson.dll ModuleData::send +652 107EF144 'ntCB' 001E02E8 00000401 0000040C 1 107EF144 10D99120 NETWORK.DLL soctWindCallback +71 001E02E8 00000401 0000040C 1 10D99210 DCBAABCD 10D991AC 77E11BC8 USER32.dll 0001:00000D0A 607222F8 001E02E8 00000401 0000040C 1 10D99254 10D9973C 007647F0 USER32.dll 0001:00000BC8 10D99208 0 6004C651 10D99208 0 10D991D8 6060F185 10D99208 USER32.dll 0001:00000CEF 10D99208 0 10D99224 6060EF04 1078808C 10D99208 0 10D994B8 meson.dll msgDispatch +6B 1078808C 10D99208 0 10D994B8 107EF144 1068A064 1 1 meson.dll msgHelper +375 1078808C 1 10D997E4 10D99838 007647F0 10D997CC 6003AEB7 1078808C meson.dll doTask +21E 'MsgR' 6060EB8F 0 0 10D99714 10D99714 1 10D99750 meson.dll TThread::TaskCall +21 1078808C 'MsgR' 6060EB8F 1078808C 1 10D997E4 10D99838 007647F0 meson.dll TThread::MsgBlock +96 'MsgR' 10D997E4 10D99838 007647F0 -1 10D997A8 0 1078808C meson.dll TSynch::Block +86 107EF15C 10D99800 6060B40B 107EF144 0 0 0 107EF210 NETWORK.DLL soctWait +40 107EF144 0 0 0 107EF210 107EF160 0 0 meson.dll ClassData::pass +1FB 002032E4 'nsWt' 0 0 0 107EF210 107EF160 0 NETWORK.DLL soccWait +138 107EF144 13A7A02C 0 10D998F0 60722B1F 13A7A00C 0000001C 1 meson.dll ModuleData::call +50B 107EF144 607204A5 13A7A02C 0 10D998F0 60722B1F 13A7A00C 0000001C NETWORK.DLL necoTranWait +42 13A7A00C 0000001C 1 137A1C04 0 10D99968 60609BE1 137A1BEC NETWORK.DLL tranWaitResp +4A 137A1BEC 13885304 0 138842C4 10D999FC 60609BE1 138842A4 0 meson.dll ModuleData::send +652 137A1BEC 'nTWR' 13885304 0 138842C4 10D999FC 60609BE1 138842A4 MACVOL.DLL mvrmFchPoll +4A 138842A4 0 0 10781A14 0 0 0 0 meson.dll ModuleData::send +652 138842A4 'VFPo' 0 0 10781A14 0 0 0 ENGINELO.DLL xenDoExec +4D6 136CC2DC 10D9A404 60609BE1 136CC2DC 10D9A41C 10D9A41C 0000000D 0 meson.dll doTask +21E 'TEnu' 60320698 0 0 10D9A388 10D9A388 1 10D9A38C meson.dll TThread::TaskCall +21 1078808C 'TEnu' 60320698 136CC2DC 10D9A404 60609BE1 136CC2DC 10D9A41C ENGINELO.DLL xenExec +1E 136CC2DC 10D9A41C 10D9A41C 0000000D 0 0 000004E4 0 meson.dll ModuleData::send +652 136CC2DC 'Arex' 10D9A41C 10D9A41C 0000000D 0 0 000004E4 ENGINELO.DLL arxGo +A5 1381F26C 10D90006 00650072 0FF6FFDC 0 0 0 0 meson.dll ModuleData::send +652 1381F26C 'arxg' 10D90006 00650072 0FF6FFDC 0 0 0 meson.dll doTask +299 'Eng1' 0 1381F26C 'arxg' 10D9ABC4 10D9ABC4 0 10D9B918 meson.dll TThread::TaskSend +23 1078808C 'Eng1' 1381F26C 'arxg' 10D90006 00650072 0FF6FFDC 0 ENGINELO.DLL arxTask +759 1381F26C 10D9CEC8 001ED26C 'pgEx' 10D9BF10 60609BE1 001ED254 10D9CEC8 meson.dll ModuleData::send +652 1381F26C 'arxt' 10D9CEC8 001ED26C 'pgEx' 10D9BF10 60609BE1 001ED254 meson.dll doTask +299 'EnOp' 0 1381F26C 'arxt' 10D9BE8C 10D9BE8C 1 10D9BE98 meson.dll TThread::TaskSend +23 1078808C 'EnOp' 1381F26C 'arxt' 10D9CEC8 001ED26C 'pgEx' 10D9BF10 ENGINELO.DLL arxEngineBlock +66 001ED254 10D9CEC8 10D9DCE8 10D9DD64 10D9BF68 60012786 10D9C09C 1067F904 meson.dll ModuleData::send +652 001ED254 'EnBk' 10D9CEC8 10D9DCE8 10D9DD64 10D9BF68 60012786 10D9C09C ENGINEHI.DLL extoBegin +823 10803694 108036AC 0 10D9E6E8 6062B461 10803694 0014C2F4 108036AC meson.dll ModuleData::send +652 10803694 'ExBg' 108036AC 0 10D9E6E8 6062B461 10803694 0014C2F4 meson.dll doTask +299 'ExOp' 0 10803694 'ExBg' 10D9E228 10D9E228 10375604 10D9E230 meson.dll TThread::TaskSend +23 1078808C 'ExOp' 10803694 'ExBg' 108036AC 0 10D9E6E8 6062B461 ENGINEHI.DLL execDoRun +1EE 10803694 0014C2F4 108036AC 61B00000 10D9E7A8 60609BE1 10803694 0014C2F4 meson.dll doTask +21E 'EScr' 60226BB2 0 0 10D9E720 10D9E720 2 10D9E730 meson.dll TThread::TaskCall +21 1078808C 'EScr' 60226BB2 10803694 0014C2F4 108036AC 61B00000 10D9E7A8 ENGINEHI.DLL execRun +33 10803694 0014C2F4 0014C3B4 10803694 0 0012DC04 60609BE1 0014C2F4 meson.dll ModuleData::send +652 10803694 'ExRu' 0014C2F4 0014C3B4 10803694 0 0012DC04 60609BE1 meson.dll TMesonMsg::Do +89 10D9E82C 0 1078808C 10D9F958 007647F0 0 0 61B3A2C0 meson.dll TThread::mesonDoOne +139 1078808C 10D9EADC 6060EBBC 0 10D9ED84 0 0 10D9ED56 meson.dll TThread::mesonQFlush +3E 0 10D9ED84 0 0 10D9ED56 1 0 0 meson.dll msgHelper +2D 1078808C 1 10D9F044 10D9F52C 007647F0 0 0 1078808C meson.dll doTask +21E 'Msg ' 6060EB8F 0 0 10D9EFCC 10D9EFCC 1 10D9F008 meson.dll TThread::TaskCall +21 1078808C 'Msg ' 6060EB8F 1078808C 1 10D9F044 10D9F52C 007647F0 meson.dll TThread::MsgBlock +96 'Msg ' 10D9F4CC 6062B461 10D9F9BC 6062B461 'LopT' 1078808C 6003AEB7 meson.dll msgInTask +1F 10D9F9BC 6062B461 'LopT' 1078808C 6003AEB7 0 0012D7C8 10D9FED0 meson.dll doTask +21E 'MsgT' 6060FAFD 0 0 10D9F504 10D9F504 1078808C 10D9F504 meson.dll TThread::TaskCall +21 1078808C 'MsgT' 6060FAFD 10D9F9BC 6062B461 'LopT' 1078808C 6003AEB7 meson.dll loopInTask +27 'LopT' 1078808C 6003AEB7 0 0012D7C8 10D9FED0 606323DF 0 meson.dll doTask +21E 'LopT' 6060FAD1 0 0 10D9F9F4 10D9F9F4 10D9FED0 10D9FA14 meson.dll TThread::TaskCall +21 1078808C 'LopT' 6060FAD1 'LopT' 1078808C 6003AEB7 0 0012D7C8 meson.dll TThread::MsgLoop +45 'LopT' 10803694 10D9FEDC 6062B461 001DBB44 1067EE54 00000567 0000037B ENGINEHI.DLL execMakeThreadProc +63 001DBB44 1067EE54 00000567 0000037B 0012D8AC 0012D8AC 00000010 0 meson.dll doTask +21E 'Task' 602241F9 0 0 10D9FF14 10D9FF14 60631D2E 10D9FF80 meson.dll TThread::TaskCall +21 1078808C 'Task' 602241F9 001DBB44 1067EE54 00000567 0000037B 0012D8AC meson.dll modThreadRoot +14F 0012D7F4 0012D298 77FCB740 007647F0 8422A280 10D9FF8C 80430F47 10D9FFDC MSVCR70.dll 0001:0000312F 007647F0 0012D298 77FCB740 007647F0 7FFD4000 0 10D9FFC0 0 KERNEL32.dll 0001:000077DD Thread ID: 00000434, Name: driver_thread EAX:001E46B4 CS:001B EIP:77F83786 EFlags:00000297 EBX:10C9E470 SS:0023 ESP:10C9E454 EBP: 10C9E478 ECX:00000010 DS:0023 ESI:77F8377B FS: 0038 EDX:00000000 ES:0023 EDI:00000358 GS: 0000 Module Fn (symbol or seg:offset in DLL) Args =============== ================================= ======================================================================= ntdll.dll 0001:00002786 00000358 000493E0 0 6061B4EE 00000358 000493E0 0 0 KERNEL32.dll 0001:00006837 0000000C 00178950 1 10C9E605 0000000C 0017800C 10C9E590 60143E39 meson.dll ScsiTrans +EE 00178950 1 6 001789EC 00178024 0 00178950 10C9E5BC DEVICES.DLL dsixTrans +2B6 0017800C 60140000 6 00010000 46450000 000493E0 6014705B 001789EC DEVICES.DLL dsixBeginRW +EC 0017800C 0 46450000 00010000 6014705B 001789EC 00178024 46450000 DEVICES.DLL dsixQStart +119 0017800C 0 001789EC 00178024 10C9E6F8 60609BE1 0017800C 0 meson.dll ModuleData::send +652 0017800C 'DVQS' 0 001789EC 00178024 10C9E6F8 60609BE1 0017800C DEVICES.DLL dsixUDoIO +136 0017800C 0 10C9E784 60609BE1 0017800C 0 10D981E4 10D981D8 meson.dll ModuleData::send +652 0017800C 'DVDI' 0 10C9E784 60609BE1 0017800C 0 10D981E4 DEVICES.DLL dsixUStart +46 0017800C 0 10D981E4 10D981D8 10D982E0 0 1 139C9884 meson.dll ModuleData::send +652 0017800C 'DVSt' 0 10D981E4 10D981D8 10D982E0 0 1 meson.dll TMesonMsg::Do +89 0 0 10799D04 0 0 0 0 0 meson.dll TThread::mesonDoOne +139 10799D04 10C9EAB8 6060EBBC 0 10C9ED60 0 0 10C9EA90 meson.dll TThread::mesonQFlush +3E 0 10C9ED60 0 0 10C9EA90 1 00024006 0 meson.dll msgHelper +2D 10799D04 1 10C9F020 10C9F508 007647F0 0 0 10799D04 meson.dll doTask +21E 'Msg ' 6060EB8F 0 0 10C9EFA8 10C9EFA8 1 10C9EFE4 meson.dll TThread::TaskCall +21 10799D04 'Msg ' 6060EB8F 10799D04 1 10C9F020 10C9F508 007647F0 meson.dll TThread::MsgBlock +96 'Msg ' 10C9F4A8 6062B461 10C9F998 6062B461 'LopT' 10799D04 'poAd' meson.dll msgInTask +1F 10C9F998 6062B461 'LopT' 10799D04 'poAd' 0 10C9FA08 10C9FA18 meson.dll doTask +21E 'MsgT' 6060FAFD 0 0 10C9F4E0 10C9F4E0 10799D04 10C9F4E0 meson.dll TThread::TaskCall +21 10799D04 'MsgT' 6060FAFD 10C9F998 6062B461 'LopT' 10799D04 'poAd' meson.dll loopInTask +27 'LopT' 10799D04 'poAd' 0 10C9FA08 10C9FA18 606323DF 0 meson.dll doTask +21E 'LopT' 6060FAD1 0 0 10C9F9D0 10C9F9D0 0 10C9F9F0 meson.dll TThread::TaskCall +21 10799D04 'LopT' 6060FAD1 'LopT' 10799D04 'poAd' 0 10C9FA08 meson.dll TThread::MsgLoop +45 'LopT' 10C9FA54 10C9FF3C 00178024 000003E8 0017800C 'Timr' 0017800C DEVICES.DLL devThread +15A 001E2E3C 10A60CFC 10A609D8 10A60CAC 1 0 00000038 0000000C meson.dll doTask +21E 'Task' 6014D40C 0 0 10C9FF14 10C9FF14 60631D2E 10C9FF80 meson.dll TThread::TaskCall +21 10799D04 'Task' 6014D40C 001E2E3C 10A60CFC 10A609D8 10A60CAC 1 meson.dll modThreadRoot +14F 10A608F4 0 0 007647F0 8422AC20 10C9FF8C 80430F47 10C9FFDC MSVCR70.dll 0001:0000312F 007647F0 0 0 007647F0 7FFD5000 0 10C9FFC0 0 KERNEL32.dll 0001:000077DD Thread ID: 00000268, Name: driver_thread EAX:107AB00C CS:001B EIP:77E11D6B EFlags:00000246 EBX:007647F0 SS:0023 ESP:10B9EA30 EBP: 10B9EA48 ECX:00000113 DS:0023 ESI:10B9EA9C FS: 0038 EDX:00000000 ES:0023 EDI:10B9EAE8 GS: 0000 Module Fn (symbol or seg:offset in DLL) Args =============== ================================= ======================================================================= USER32.dll 0001:00000D6B 10B9EA9C 0 0 0 107AB00C 10B9EAB8 6060EDDD 10B9EA9C bedrock.dll UGetMessage +25 10B9EA9C 0 0 0 0 10B9ED4C 0 0 meson.dll msgHelper +24E 107AB00C 1 10B9F020 10B9F508 007647F0 0 0 107AB00C meson.dll doTask +21E 'Msg ' 6060EB8F 0 0 10B9EFA8 10B9EFA8 1 10B9EFE4 meson.dll TThread::TaskCall +21 107AB00C 'Msg ' 6060EB8F 107AB00C 1 10B9F020 10B9F508 007647F0 meson.dll TThread::MsgBlock +96 'Msg ' 10B9F4A8 6062B461 10B9F998 6062B461 'LopT' 107AB00C 'poAd' meson.dll msgInTask +1F 10B9F998 6062B461 'LopT' 107AB00C 'poAd' 0 10B9FA08 10B9FA18 meson.dll doTask +21E 'MsgT' 6060FAFD 0 0 10B9F4E0 10B9F4E0 107AB00C 10B9F4E0 meson.dll TThread::TaskCall +21 107AB00C 'MsgT' 6060FAFD 10B9F998 6062B461 'LopT' 107AB00C 'poAd' meson.dll loopInTask +27 'LopT' 107AB00C 'poAd' 0 10B9FA08 10B9FA18 606323DF 0 meson.dll doTask +21E 'LopT' 6060FAD1 0 0 10B9F9D0 10B9F9D0 0 10B9F9F0 meson.dll TThread::TaskCall +21 107AB00C 'LopT' 6060FAD1 'LopT' 107AB00C 'poAd' 0 10B9FA08 meson.dll TThread::MsgLoop +45 'LopT' 10B9FA54 10B9FF3C 00176024 000003E8 0017600C 'Timr' 0017600C DEVICES.DLL devThread +15A 001568FC 10A60CFC 10A60704 10A60CAC 10A609D4 0 02000024 2 meson.dll doTask +21E 'Task' 6014D40C 0 0 10B9FF14 10B9FF14 60631D2E 10B9FF80 meson.dll TThread::TaskCall +21 107AB00C 'Task' 6014D40C 001568FC 10A60CFC 10A60704 10A60CAC 10A609D4 meson.dll modThreadRoot +14F 10A60620 000570AB 0004D423 007647F0 843DB9A0 10B9FF8C 80430F47 10B9FFDC MSVCR70.dll 0001:0000312F 007647F0 000570AB 0004D423 007647F0 7FFDC000 000005E9 10B9FFC0 000005E9 KERNEL32.dll 0001:000077DD Thread ID: 0000060C, Name: RetroFrameThread EAX:10A6C0DC CS:001B EIP:77E11D6B EFlags:00000246 EBX:007647F0 SS:0023 ESP:10A6EA54 EBP: 10A6EA6C ECX:10A6C0C4 DS:0023 ESI:10A6EAC0 FS: 003B EDX:00000000 ES:0023 EDI:10A6EB0C GS: 0000 Module Fn (symbol or seg:offset in DLL) Args =============== ================================= ======================================================================= USER32.dll 0001:00000D6B 10A6EAC0 0 0 0 106C125C 10A6EADC 6060EDDD 10A6EAC0 bedrock.dll UGetMessage +25 10A6EAC0 0 0 0 0 10A6ED70 0 0 meson.dll msgHelper +24E 106C125C 1 10A6F044 10A6F52C 007647F0 1043D3DC 10A6F4EC 106C125C meson.dll doTask +21E 'Msg ' 6060EB8F 0 0 10A6EFCC 10A6EFCC 1 10A6F008 meson.dll TThread::TaskCall +21 106C125C 'Msg ' 6060EB8F 106C125C 1 10A6F044 10A6F52C 007647F0 meson.dll TThread::MsgBlock +96 'Msg ' 10A6F4CC 6062B461 10A6F9BC 6062B461 'LopT' 106C125C 6003AEB7 meson.dll msgInTask +1F 10A6F9BC 6062B461 'LopT' 106C125C 6003AEB7 0 0012E56C 10A6FED0 meson.dll doTask +21E 'MsgT' 6060FAFD 0 0 10A6F504 10A6F504 106C125C 10A6F504 meson.dll TThread::TaskCall +21 106C125C 'MsgT' 6060FAFD 10A6F9BC 6062B461 'LopT' 106C125C 6003AEB7 meson.dll loopInTask +27 'LopT' 106C125C 6003AEB7 0 0012E56C 10A6FED0 606323DF 0 meson.dll doTask +21E 'LopT' 6060FAD1 0 0 10A6F9F4 10A6F9F4 'retr' 10A6FA14 meson.dll TThread::TaskCall +21 106C125C 'LopT' 6060FAD1 'LopT' 106C125C 6003AEB7 0 0012E56C meson.dll TThread::MsgLoop +45 'LopT' 1071D5FC 10A6FEDC 6062B461 104539B4 0012E55C 1067EE54 0012E330 UIPROD.DLL rfThread +CB 104539B4 0012E55C 1067EE54 0012E330 0012E330 0 00000010 0 meson.dll doTask +21E 'Task' 6194ADBD 0 0 10A6FF14 10A6FF14 60631D2E 10A6FF80 meson.dll TThread::TaskCall +21 106C125C 'Task' 6194ADBD 104539B4 0012E55C 1067EE54 0012E330 0012E330 meson.dll modThreadRoot +14F 0012E27C 0064002D 00000072 007647F0 84284220 10A6FF8C 80430F47 10A6FFDC MSVCR70.dll 0001:0000312F 007647F0 0064002D 00000072 007647F0 7FFD6000 0 10A6FFC0 0 KERNEL32.dll 0001:000077DD 7C0040E2 007647F0 0 '\\\\' '\\\\' '\\\\' '\\\\' '\\\\' Thread ID: 00000218, Name: Volume tracker thread EAX:00000023 CS:001B EIP:77E11D6B EFlags:00000246 EBX:007647F0 SS:0023 ESP:1096EA58 EBP: 1096EA70 ECX:1070CEE4 DS:0023 ESI:1096EAC4 FS: 0038 EDX:00000000 ES:0023 EDI:1096EB10 GS: 0000 Module Fn (symbol or seg:offset in DLL) Args =============== ================================= ======================================================================= USER32.dll 0001:00000D6B 1096EAC4 0 0 0 1070D01C 1096EAE0 6060EDDD 1096EAC4 bedrock.dll UGetMessage +25 1096EAC4 0 0 0 0 1096ED74 0 0 meson.dll msgHelper +24E 1070D01C 1 1096F048 1096F530 007647F0 0 0 1070D01C meson.dll doTask +21E 'Msg ' 6060EB8F 0 0 1096EFD0 1096EFD0 1 1096F00C meson.dll TThread::TaskCall +21 1070D01C 'Msg ' 6060EB8F 1070D01C 1 1096F048 1096F530 007647F0 meson.dll TThread::MsgBlock +96 'Msg ' 1096F4D0 6062B461 1096F9C0 6062B461 'LopT' 1070D01C 6003AEB7 meson.dll msgInTask +1F 1096F9C0 6062B461 'LopT' 1070D01C 6003AEB7 0 1066D5F0 1096FED0 meson.dll doTask +21E 'MsgT' 6060FAFD 0 0 1096F508 1096F508 1070D01C 1096F508 meson.dll TThread::TaskCall +21 1070D01C 'MsgT' 6060FAFD 1096F9C0 6062B461 'LopT' 1070D01C 6003AEB7 meson.dll loopInTask +27 'LopT' 1070D01C 6003AEB7 0 1066D5F0 1096FED0 606323DF 0 meson.dll doTask +21E 'LopT' 6060FAD1 0 0 1096F9F8 1096F9F8 007647F0 1096FA18 meson.dll TThread::TaskCall +21 1070D01C 'LopT' 6060FAD1 'LopT' 1070D01C 6003AEB7 0 1066D5F0 meson.dll TThread::MsgLoop +45 'LopT' 1096FEDC 6062B461 1066D6CC 1066D6CC 1068B68C 1068B9A4 00000015 PCVOL.DLL vtloVolTrakThread +3A 1066D6CC 1066D6CC 1068B68C 1068B9A4 00000015 0 0 00130178 meson.dll doTask +21E 'Task' 60956454 0 0 1096FF14 1096FF14 60631D2E 1096FF80 meson.dll TThread::TaskCall +21 1070D01C 'Task' 60956454 1066D6CC 1066D6CC 1068B68C 1068B9A4 00000015 meson.dll modThreadRoot +14F 1066D61C 007647F0 0 007647F0 84237020 1096FF8C 80430F47 1096FFDC MSVCR70.dll 0001:0000312F 007647F0 007647F0 0 007647F0 7FFD7000 0 1096FFC0 0 KERNEL32.dll 0001:000077DD Thread ID: 00000630, Name: Controller thread EAX:00000001 CS:001B EIP:77E11D6B EFlags:00000246 EBX:007647F0 SS:0023 ESP:1066E81C EBP: 1066E834 ECX:1066EDC4 DS:0023 ESI:1066E888 FS: 0038 EDX:00000000 ES:0023 EDI:1066E8D4 GS: 0000 Module Fn (symbol or seg:offset in DLL) Args =============== ================================= ======================================================================= USER32.dll 0001:00000D6B 1066E888 0 0 0 1046D304 1066E8A4 6060EDDD 1066E888 bedrock.dll UGetMessage +25 1066E888 0 0 0 0 1066EB38 0 0 meson.dll msgHelper +24E 1046D304 1 1066EE0C 1066F2F4 007647F0 -1 000001B4 1046D304 meson.dll doTask +21E 'Msg ' 6060EB8F 0 0 1066ED94 1066ED94 1 1066EDD0 meson.dll TThread::TaskCall +21 1046D304 'Msg ' 6060EB8F 1046D304 1 1066EE0C 1066F2F4 007647F0 meson.dll TThread::MsgBlock +96 'Msg ' 1066F294 6062B461 1066F784 6062B461 'LopT' 1046D304 6003AEB7 meson.dll msgInTask +1F 1066F784 6062B461 'LopT' 1046D304 6003AEB7 0 0012E2A4 1066FA18 meson.dll doTask +21E 'MsgT' 6060FAFD 0 0 1066F2CC 1066F2CC 1046D304 1066F2CC meson.dll TThread::TaskCall +21 1046D304 'MsgT' 6060FAFD 1066F784 6062B461 'LopT' 1046D304 6003AEB7 meson.dll loopInTask +27 'LopT' 1046D304 6003AEB7 0 0012E2A4 1066FA18 606323DF 0 meson.dll doTask +21E 'LopT' 6060FAD1 0 0 1066F7BC 1066F7BC 1066F7C8 1066F7DC meson.dll TThread::TaskCall +21 1046D304 'LopT' 6060FAD1 'LopT' 1046D304 6003AEB7 0 0012E2A4 meson.dll TThread::MsgLoop +45 'LopT' 0000000C 0 0 000004E4 0 1066F800 006F0063 Retrospect.exe controllerThread +2D5 0014D084 0012EF24 0012E380 0012E380 00000011 0 0 0012E65C meson.dll doTask +21E 'Task' 61106144 0 0 1066FF14 1066FF14 60631D2E 1066FF80 meson.dll TThread::TaskCall +21 1046D304 'Task' 61106144 0014D084 0012EF24 0012E380 0012E380 00000011 meson.dll modThreadRoot +14F 0012E2D0 0 60609E98 007647F0 84368320 1066FF8C 80430F47 1066FFDC MSVCR70.dll 0001:0000312F 007647F0 0 60609E98 007647F0 7FFD8000 0012E15C 1066FFC0 0012E15C KERNEL32.dll 0001:000077DD 7C0040E2 007647F0 0 00000008 00000102 FFEEFFEE 0 00130000 Thread ID: 00000578, Name: Quit handler thread EAX:0019F39C CS:001B EIP:77E11D6B EFlags:00000246 EBX:00763D38 SS:0023 ESP:1020E3A8 EBP: 1020E3C0 ECX:0015CFC8 DS:0023 ESI:1020E414 FS: 0038 EDX:00000000 ES:0023 EDI:1020E460 GS: 0000 Module Fn (symbol or seg:offset in DLL) Args =============== ================================= ======================================================================= USER32.dll 0001:00000D6B 1020E414 0 0 0 0019F39C 1020E430 6060EDDD 1020E414 bedrock.dll UGetMessage +25 1020E414 0 0 0 0 1020E6C4 0 0 meson.dll msgHelper +24E 0019F39C 1 1020E998 1020EE80 00763D38 0 0 0019F39C meson.dll doTask +21E 'Msg ' 6060EB8F 0 0 1020E920 1020E920 1 1020E95C meson.dll TThread::TaskCall +21 0019F39C 'Msg ' 6060EB8F 0019F39C 1 1020E998 1020EE80 00763D38 meson.dll TThread::MsgBlock +96 'Msg ' 1020EE20 6062B461 1020F310 6062B461 'LopT' 0019F39C 6003AEB7 meson.dll msgInTask +1F 1020F310 6062B461 'LopT' 0019F39C 6003AEB7 0 0012EEE4 1020FA18 meson.dll doTask +21E 'MsgT' 6060FAFD 0 0 1020EE58 1020EE58 0019F39C 1020EE58 meson.dll TThread::TaskCall +21 0019F39C 'MsgT' 6060FAFD 1020F310 6062B461 'LopT' 0019F39C 6003AEB7 meson.dll loopInTask +27 'LopT' 0019F39C 6003AEB7 0 0012EEE4 1020FA18 606323DF 0 meson.dll doTask +21E 'LopT' 6060FAD1 0 0 1020F348 1020F348 0 1020F368 meson.dll TThread::TaskCall +21 0019F39C 'LopT' 6060FAD1 'LopT' 0019F39C 6003AEB7 0 0012EEE4 meson.dll TThread::MsgLoop +45 'LopT' 1020F37C 1020F37C 00000011 0 0 0 0 meson.dll QuitWindowStart +174 0012EFC0 0012EFC0 0012F1E4 0012F1E4 00000013 0 0 0012F2D0 meson.dll doTask +21E 'Task' 60613EA0 0 0 1020FF14 1020FF14 60631D2E 1020FF80 meson.dll TThread::TaskCall +21 0019F39C 'Task' 60613EA0 0012EFC0 0012EFC0 0012F1E4 0012F1E4 00000013 meson.dll modThreadRoot +14F 0012EF10 00130000 00186720 00763D38 83C66280 1020FF8C 80430F47 1020FFDC MSVCR70.dll 0001:0000312F 00763D38 00130000 00186720 00763D38 7FFDA000 77FCB3E3 1020FFC0 77FCB3E3 KERNEL32.dll 0001:000077DD 7C0040E2 00763D38 0 000000C8 00000100 EEFFEEFF 00001002 0 Thread ID: 0000062C, Name: Server thread EAX:00190B74 CS:001B EIP:77E11D6B EFlags:00000246 EBX:00763D38 SS:0023 ESP:1010EA54 EBP: 1010EA6C ECX:1010F2A8 DS:0023 ESI:1010EAC0 FS: 0038 EDX:00000000 ES:0023 EDI:1010EB0C GS: 0000 Module Fn (symbol or seg:offset in DLL) Args =============== ================================= ======================================================================= USER32.dll 0001:00000D6B 1010EAC0 0 0 0 00190B74 1010EADC 6060EDDD 1010EAC0 bedrock.dll UGetMessage +25 1010EAC0 0 0 0 0 1010ED70 0 0 meson.dll msgHelper +24E 00190B74 1 1010F044 1010F52C 00763D38 0 0 00190B74 meson.dll doTask +21E 'Msg ' 6060EB8F 0 0 1010EFCC 1010EFCC 1 1010F008 meson.dll TThread::TaskCall +21 00190B74 'Msg ' 6060EB8F 00190B74 1 1010F044 1010F52C 00763D38 meson.dll TThread::MsgBlock +96 'Msg ' 1010F4CC 6062B461 1010F9BC 6062B461 'LopT' 00190B74 6003AEB7 meson.dll msgInTask +1F 1010F9BC 6062B461 'LopT' 00190B74 6003AEB7 0 0012EEE4 1010FED0 meson.dll doTask +21E 'MsgT' 6060FAFD 0 0 1010F504 1010F504 00190B74 1010F504 meson.dll TThread::TaskCall +21 00190B74 'MsgT' 6060FAFD 1010F9BC 6062B461 'LopT' 00190B74 6003AEB7 meson.dll loopInTask +27 'LopT' 00190B74 6003AEB7 0 0012EEE4 1010FED0 606323DF 0 meson.dll doTask +21E 'LopT' 6060FAD1 0 0 1010F9F4 1010F9F4 1010FCB8 1010FA14 meson.dll TThread::TaskCall +21 00190B74 'LopT' 6060FAD1 'LopT' 00190B74 6003AEB7 0 0012EEE4 meson.dll TThread::MsgLoop +45 'LopT' 0015CCB4 1010FEDC 6062B461 -1 0012EFD8 0012F1E4 0012F1E4 meson.dll serverThread +6B -1 0012EFD8 0012F1E4 0012F1E4 77F8320B 00000024 0012F2D0 0012F2D0 meson.dll doTask +21E 'Task' 60608474 0 0 1010FF14 1010FF14 60631D2E 1010FF80 meson.dll TThread::TaskCall +21 00190B74 'Task' 60608474 -1 0012EFD8 0012F1E4 0012F1E4 77F8320B meson.dll modThreadRoot +14F 0012EF10 0012E908 00130688 00763D38 8428CA20 1010FF8C 80430F47 1010FFDC MSVCR70.dll 0001:0000312F 00763D38 0012E908 00130688 00763D38 7FFDB000 00130000 1010FFC0 00130000 KERNEL32.dll 0001:000077DD Thread ID: 00000644, Name: Main thread EAX:0015700C CS:001B EIP:77E11D6B EFlags:00000246 EBX:00000000 SS:0023 ESP:0012DF58 EBP: 0012DF70 ECX:0012E288 DS:0023 ESI:0012DFC4 FS: 003B EDX:00000000 ES:0023 EDI:0012E010 GS: 0000 Module Fn (symbol or seg:offset in DLL) Args =============== ================================= ======================================================================= USER32.dll 0001:00000D6B 0012DFC4 0 0 0 0015700C 0012DFE0 6060EDDD 0012DFC4 bedrock.dll UGetMessage +25 0012DFC4 0 0 0 0 0012E274 0 0 meson.dll msgHelper +24E 0015700C 1 0012E548 0012EA30 0 0 0 0015700C meson.dll doTask +21E 'Msg ' 6060EB8F 0 0 0012E4D0 0012E4D0 1 0012E50C meson.dll TThread::TaskCall +21 0015700C 'Msg ' 6060EB8F 0015700C 1 0012E548 0012EA30 0 meson.dll TThread::MsgBlock +96 'Msg ' 0012E9D0 6062B461 0012EEC0 6062B461 'LopT' 0015700C 1073A5A8 meson.dll msgInTask +1F 0012EEC0 6062B461 'LopT' 0015700C 1073A5A8 0 0012F3D8 0012F3D8 meson.dll doTask +21E 'MsgT' 6060FAFD 0 0 0012EA08 0012EA08 0015700C 0012EA08 meson.dll TThread::TaskCall +21 0015700C 'MsgT' 6060FAFD 0012EEC0 6062B461 'LopT' 0015700C 1073A5A8 meson.dll loopInTask +27 'LopT' 0015700C 1073A5A8 0 0012F3D8 0012F3D8 606323DF 0 meson.dll doTask +21E 'LopT' 6060FAD1 0 0 0012EEF8 0012EEF8 0 0012EF18 meson.dll TThread::TaskCall +21 0015700C 'LopT' 6060FAD1 'LopT' 0015700C 1073A5A8 0 0012F3D8 meson.dll TThread::MsgLoop +45 'LopT' 0 0000000B 0012F3E4 6062B461 0 0012FF1C 61110C9F meson.dll mesonGo +122 0 0012FF1C 61110C9F 0 0 0014F6C0 0012F424 01000200 meson.dll doTask +21E 'Prog' 606084E3 0 0 0012F41C 0012F41C 00000648 0012F420 meson.dll TThread::TaskCall +21 0015700C 'Prog' 606084E3 0 0012FF1C 61110C9F 0 0 meson.dll Meson +2C 0 0 0014F6C0 0012F424 01000200 00000009 0 0 Retrospect.exe _WinMain +2AF 61100000 0 00133223 1 0 0 7FFDF000 00000246 Retrospect.exe _WinMainCRTStartup +191 0 0 7FFDF000 0 0012FFC8 0 -1 77EA1856 KERNEL32.dll 0001:0001BA90 61110DCD 0 000000C8 00000100 EEFFEEFF 2 0 0000FE00
  25. Go to http://www.dantz.com/upgrades/ to get upgrade pricing. Disaster Recovery is built into Professional; it says so on the product comparison page, http://www.dantz.com/products/wincompare.html. Also, if you upgrade from 5.6 to either server, Dantz claims you'll get Disaster Recovery as part of the upgrade. (See http://forums.dantz.com/ubbthreads/showflat.php?Cat=&Board=professional&Number=11862 for more details.) - Gary Palter (Just another Retrospect user)
×
×
  • Create New...