Jump to content

mok

Members
  • Content count

    12
  • Joined

  • Last visited

Community Reputation

0 Neutral

About mok

  • Rank
    Occasional Forum Poster
  1. OK, Dave! I admit it. You were right about the Mac OS fix. Good guru! However, the caveat you refer to: "I don't have the Retrospect license handy, but most software licensing agreements explicitly point out that the product _may_ contain bugs, and that the software publisher is not responsible for problems arising from the use of the product." is a license for scoundrels to market vaporware, and a full frontal reflection of the dotcom bubble stance. I fully expect bugs... maybe I have made noises otherwise.... but I think most of us realize that the cyberworld is a work in progress like the rest of human endeavor. But when software companies STOP talking to their customers, make it hard for them to find meaningful help, and just plain sell and bail, that is not being part of a cooperative effort. Too many software, hardware, anyware companies these days try to avoid involving live humans in the problem-solving process. These INCLUDE venerable names like Adobe, Apple, Microsoft, Dantz, SmithMicro, and more. The sell us the stuff with hot promise, partially deliver, partially communicate about the problems involved with surviving that partial birth, and then withdraw behind a fortress of $$$$$$$, and make it hard for working people (as opposed to the geek aristocracy) to find solutions for their everyday CRISES. The software companies need to make money, but they also need to make human contact more possible than they seem to be willing to try. I totally appreciate the value of this forum. I came back today after being out of town, saw the notices about 10.2.4, downloaded it, and... no more fix_prebinding errors.... even when I approached the scripts. So, thanks, Dave, and Amy. You do good work. And thanks, Dantz, for providing the forum platform. I just wish it hadn't taken me 2 months to find it.
  2. Dave! So how much are you betting? Does this mean we just wade through the fix_prebinding.crash.logs like so many alligators? Granted... there is a lot funky stuff going on in OS X... some things get fixed, some things get worse. Does this mean that we all qualify as geeks, albeit not of the aristocracy, whether we want to or not? I don't believe I signed up anywhere to debug Dantz/OSX/Adobe/SmithMicro/Microsoft/YouNameIt software. I signed up to buy software that works. I try to make a living in the world that Dantz/OSX/Adobe/SmithMicro/Microsoft/YouNameIt created, but they make it very hard. And like the arrogant market bubble, their attitude toward their customers is ghostly, to say the least, and downright supercilious at best. There are a few software companies that respond to the customer: Alsoft, Extensis, Smiles Software to name some. They extend a certain amount of handholding to the customer when he needs it - a must when the product is iffy, persnickity, buggy, and mostly unfinished, like a lot of what is going around now. This fix_prebinding mess is a minor thing, an annoyance - like coming out every morning and finding [censored] in the same spot on your brand new Beemer. On my machine, it only happens with Retrospect, and only when scripts are scratched.
  3. The fix_prebinding crashes that had been occuring have reappeared. So, as you replied, AmyC, perhaps I had deleted those scripts when I uninstalled Retrospect 5.0.205 preperatory to installing the update. Just now, I started Retrospect to recreate those scripts, and ...... BAM! As soon as I hit the Scripts button under Automate, the following fix_prebinding.crash.log appeared: Date/Time: 2003-02-08 10:17:08 -0600 OS Version: 10.2.3 (Build 6G30) Host: Patrick-McKelveys-Computer.local. Command: fix_prebinding PID: 732 Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000054 Thread 0 Crashed: #0 0x000152a4 in 0x152a4 #1 0x0000c3d8 in 0xc3d8 #2 0x0000c0ec in 0xc0ec #3 0x0000b3ac in 0xb3ac #4 0x00007b20 in 0x7b20 #5 0x00004250 in 0x4250 #6 0x0000290c in 0x290c #7 0x00002414 in 0x2414 #8 0x00002a2c in 0x2a2c #9 0x90031c44 in mach_msg_server #10 0x00002c40 in 0x2c40 #11 0x00002f48 in 0x2f48 #12 0x00002188 in 0x2188 #13 0x00002008 in 0x2008 PPC Thread State: srr0: 0x000152a4 srr1: 0x0200d030 vrsave: 0x00000000 xer: 0x00000000 lr: 0x00015254 ctr: 0x90000f00 mq: 0x00000000 r0: 0x000017e8 r1: 0xbffff430 r2: 0x00000000 r3: 0x00172a78 r4: 0x00000003 r5: 0x00000001 r6: 0x00000040 r7: 0x00032230 r8: 0x00001680 r9: 0x00000014 r10: 0x00032230 r11: 0x0016c428 r12: 0x90000f00 r13: 0x000321b8 r14: 0x00032234 r15: 0x0000003f r16: 0x00001770 r17: 0x00001f80 r18: 0x00170c00 r19: 0x00000010 r20: 0x00032234 r21: 0x000321b8 r22: 0x00172630 r23: 0x00000030 r24: 0x00032230 r25: 0x01857c60 r26: 0x00032234 r27: 0x00172a48 r28: 0x00000033 r29: 0x00032230 r30: 0x00001680 r31: 0x00014914 I don't know what it means, but I usually try to avoid msg, no matter who is serving it - it's bad for you. Maybe this set of circumstances will provide a clue.
  4. Just had a thought. Can it be that when I uninstalled Retrospect 5.0.205, I also uninstalled the scripts I had created with it?
  5. Right! I looked in the trash and there was the discarded 5.0.205 application. I emptied the trash, started Retrospect 5.0.238 and NO CRASH LOGS APPEARED! THANKS! But........ I installed the 5.0 drivers - dialog asked about accessing old 4.3 scripts (wouldn't recognize these in the past under OSX) - I said SURE!............. and now I can't access the scripts I created under OSX with 5.0.205. The error message is the same one I used to get for 4.3 driver scripts created with OS9 - "? Retrospect version 5.0.238 launched at 2/7/2003 9:20 AM + Retrospect Driver Update, version 3.1.105 Run document Run 03 pvc Backup failed: Script 03 pvc Backup is not defined" How can I get Retrospect to AGAIN recognize these scripts defined in OS 10.2.3 with Retrospect 5.0.205? Not only that.... when I tried to launch Help for Retrospect 5.0.238, Classic booted and opened Navigator 4.7 - which I never use. Of course the help files accessed by this method were non-relevant. In fact, NOWHERE in the forums can I find a reference to "scripts not defined" or "undefined scripts". Nobody else seems to be having a problem with scripts not defined, but I have a lot of them, so I must be doing something dumb and obvious. But I have no idea what it is. WHAT IS GOING ON?
  6. I just installed Retrospect 5.0.238 English thusly: Uninstalled 5.0.205 with the installer, removed danz.plist pref, emptied trash, rebooted, installed 5.0.238, and before I could enter the serial number I got the following: RetroRun.crash.log Date/Time: 2003-02-06 17:51:15 -0600 OS Version: 10.2.3 (Build 6G30) Host: Patrick-McKelveys-Computer.local. Command: RetroRun PID: 512 Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_INVALID_ADDRESS (0x0001) at 0x001e8c4c Thread 0 Crashed: #0 0x00003950 in GetPID (main.c:258) #1 0x000045c0 in main (main.c:577) #2 0x000031c8 in _start #3 0x00002ff8 in start PPC Thread State: srr0: 0x00003950 srr1: 0x0000d030 vrsave: 0x00000000 xer: 0x00000000 lr: 0x0000394c ctr: 0x90073c40 mq: 0x00000000 r0: 0x0000394c r1: 0xbffffad0 r2: 0x00143010 r3: 0x00000000 r4: 0x00000003 r5: 0x00000028 r6: 0x0000002c r7: 0x00000703 r8: 0x00000000 r9: 0x001e8c34 r10: 0x00000001 r11: 0xa0004894 r12: 0x90073c40 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000 r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x00000000 r20: 0x00000000 r21: 0x00000000 r22: 0x00000000 r23: 0x00000000 r24: 0x00000000 r25: 0x00000000 r26: 0xbffffeb0 r27: 0x00000008 r28: 0x00000001 r29: 0xbffffebc r30: 0xbffffad0 r31: 0x000037c0 console.log Mac OS X Version 10.2.3 (Build 6G30) Feb 6 17:47:46 Patrick-McKelveys-Computer /sbin/autodiskmount[205]: disk2s1s2 hfs no no Ozark Wilderness Works [not mounted] Feb 6 17:47:47 Patrick-McKelveys-Computer /sbin/autodiskmount[205]: disk2s1s2 hfs no no Ozark Wilderness Works /Volumes/Ozark Wilderness Works Feb 6 17:47:49 Patrick-McKelveys-Computer DMProxy: theErr=-4200 [line 787, file DMProxy.c] Feb 6 17:47:49 Patrick-McKelveys-Computer DMProxy: theErr=-4200 [line 367, file DMProxy.c] Feb 6 17:47:49 Patrick-McKelveys-Computer DMProxy: theErr=-4200 [line 286, file DMProxy.c] 2003-02-06 17:47:50.050 iCal[468] unable to find Helvetica Neue font, using helvetica instead 2003-02-06 17:47:50.472 iCal[468] unable to find Helvetica Neue font, using helvetica instead 2003-02-06 17:47:57.894 QuicKeysKeyPressDaemon[484] QuicKeys keypress daemon running Feb 6 17:48:29 Patrick-McKelveys-Computer authexec: executing /Users/moky/.Trash/Retrospect/Contents/MacOS/AuthenticateUser.app/Contents/MacOS/../../../LaunchRetro Feb 6 17:48:52 Patrick-McKelveys-Computer authexec: executing /System/Library/Frameworks/Carbon.framework/Versions/Current/Support/LaunchCFMApp kill: usage: kill [-s sigspec | -n signum | -sigspec] [pid | job]... or kill -l [sigspec] Feb 6 17:49:43 Patrick-McKelveys-Computer crashdump: Crash report written to: /Library/Logs/CrashReporter/fix_prebinding.crash.log Feb 6 17:51:15 Patrick-McKelveys-Computer crashdump: Crash report written to: /Library/Logs/CrashReporter/RetroRun.crash.log fix-prebinding.crash.log Date/Time: 2003-02-06 17:49:43 -0600 OS Version: 10.2.3 (Build 6G30) Host: Patrick-McKelveys-Computer.local. Command: fix_prebinding PID: 472 Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000054 Thread 0 Crashed: #0 0x000152a4 in 0x152a4 #1 0x0000c3d8 in 0xc3d8 #2 0x0000c0ec in 0xc0ec #3 0x0000b3ac in 0xb3ac #4 0x00007b20 in 0x7b20 #5 0x00004250 in 0x4250 #6 0x0000290c in 0x290c #7 0x00002414 in 0x2414 #8 0x00002a2c in 0x2a2c #9 0x90031c44 in mach_msg_server #10 0x00002c40 in 0x2c40 #11 0x00002f48 in 0x2f48 #12 0x00002188 in 0x2188 #13 0x00002008 in 0x2008 PPC Thread State: srr0: 0x000152a4 srr1: 0x0200f030 vrsave: 0x00000000 xer: 0x00000000 lr: 0x00015254 ctr: 0x90000f00 mq: 0x00000000 r0: 0x000017e8 r1: 0xbffff430 r2: 0x00000000 r3: 0x036baa78 r4: 0x00000003 r5: 0x00000001 r6: 0x00000040 r7: 0x00032230 r8: 0x00001680 r9: 0x00000014 r10: 0x00032230 r11: 0x036b4428 r12: 0x90000f00 r13: 0x000321b8 r14: 0x00032234 r15: 0x0000003f r16: 0x00001770 r17: 0x00001f80 r18: 0x036b8c00 r19: 0x00000010 r20: 0x00032234 r21: 0x000321b8 r22: 0x036ba630 r23: 0x00000030 r24: 0x00032230 r25: 0x05a5fc60 r26: 0x00032234 r27: 0x036baa48 r28: 0x00000033 r29: 0x00032230 r30: 0x00001680 r31: 0x00014914 NOTE: One of these - can't remember which - popped up AFTER Retrospect started up - the other two popped up before i coul;d even re-enter the serial number - i think console was one of these first.
  7. Dave - if I have to call you something, I think I'll be conservative and call you patronizing. I, too, have the fix_prebinding problem with Retrospect (which I described elsewhere). I finally caught on and did the search for "fix_prebinding" (with the dash instead of the space) and got this mess. Essentially, my fix_prebinding problem exhibits behavior almost identical to the French version, as delineated by Bernard. I do not get this crash performance with any other application. US English version of Retrospect 5.0.205, recently re-installed to no affect for the fix_prebinding problem. Machine configuration: US English MacOS 10.2.3 - G4 QuickSilver 867mhz - 1.5GB RAM - Apple-installed, partitioned IBM-IC35L060AVER07-0 60 GB HD - 120 GB Barracuda ST3120023A IDE single partition "slave" - 120 GB partitioned external FireWire Drive (fix_prebinding problem occurs also when this last drive is not mounted).
  8. I have to agree that the Greed approach to tech support (such as is practiced by Dantz and many other software companies, including Apple) is not only rude, but also arrogant. And I think the eventual result for these companies will be negative - at least I hope so. It is implicitly not fair to abandon customers after selling them software that is buggy, poorly-manualed, overly finicky, and actually still in development that requires frequent upgrades. Most people don't have clue as to how to get even half of what their computer is capable of out of the machine. That they may deserve such treatment is perhaps true, but only as long as they are not lured to the product with the promise that it's use is easy. The stampede for market share and profitability should not leave the customer behind.
  9. A search for "fix prebinding" returned my own post - nothing else.
  10. Its hard to tell what is being represented by the crash log. I do not know how to interpret the logs - the language might as well be Martian. Usually, I will have clicked on a "Run" document - Retrospect opens - the crash logs appear - and fix prebinding is part of the log suite that appears. If this has been covered previously I have yet to see it. I close the logs. Then I click, for example, on the Main Dialog Box for Retrospect - the crash log reappears. These logs do not appear unless I start Retrospect. Thanks for your response, but I still don't get it.
  11. This is new behavior that started when I tried to duplicate a Backup File by dragging it to a new HD to change the storage space. At first the HD was not correctly installed and everything I put on it whether dragged to, saved to or newly created CRASHED the finder. I finally got that little problem straightened out, but thereafter, every time I start Retrospect the Console crash log appears with a new entry - but Retrospect itself does not crash. I close the console log and click on some other Retrospect function and the Console crash log reappears. This ALWAYS happens now. Retrospect seems to run, backup and retrieve normally, except for this annoying crash log behavior. Anybody got a clue? admaniac@swbell.net
  12. On the Macintosh: I have at least 2 scripts created with Retro 4.3 under OS 9.2.2 that I wish to continue using in OSX 1.1.4+, but Retrospect 5.0.203 doesn't see them as scripts. I can "open" them in R5-OSX but they will not run. Anyone have an answer to this conundrum. Dantz provided me no documentation with my upgrade, but they will be happy to answer this question on the phone for seventy bucks.
×