Marc Zeedar wrote:
Okay, I've had a long last five hours tearing my hair out trying to figure
out what's going on. Here's the scenario. Earlier today I was working on a
simple app in RB2006r1. I hit "Run" and got the compile progress bar and a
"rainbow cursor" that would not go away. I switched to other programs and
though they were initially responsive, within seconds they too had the
same eternal rainbow cursor. Then I noticed the Dock was dead (app names
not showing up when you point at the icons). So I had to a hard reset to
reboot.
After rebooting, I continued to have the same problem with the eternal
rainbow cursor showing up. At first it seemed random, then I figured out
it was happening every time I opened the folder that contain the project
I'd been working on.
Figuring that folder was damaged, I ran Disk Utilities and DiskWarrior to
no avail. Finally I resorted to Terminal and navigated to that project
folder and deleted the "My Application.debug" file. Once that file was
deleted, everything worked fine again. I could view the folder in the
Finder, etc.
Now here's the problem: I can't seem to compiled ANYTHING in RB2006 any
more! I downloaded and installed r3 and it does the exact same thing. Even
starting with a brand new empty project and hitting "Run" or "Build"
causes the same eternal rainbow cursor!
Even worse, the half-created (I'm assuming it's only half there)
application file is apparently deadly to the Finder and OS as any attempts
to look at the folder it is in causes the rainbow cursor problem. I have
to use Terminal to delete the file just to get my OS working again!
Obviously, this is not a viable work situation. I basically cannot compile
in RB and if I do, it hoses the folder I compile into and locks up my Mac
with an eternal rainbow cursor and forces a hard reboot (I cannot get
Force Quit or anything to work once the rainbow cursor takes over).
But I'm at a loss as to how to fix this or where to even troubleshoot. I
installed a whole new version of RBr3 during this process and that didn't
help, so it's not specific to a particular version of RB. That makes me
think it's some sort of conflict with an OS library or something else on
my system that that RB uses during compiling that might have become
corrupted or something, but I don't even know where to begin to look.
Does anyone out there have any ideas? Should I reinstall something (and if
so, what)? What in the world is RB doing during compilation that might
cause this kind of thing?
This is a fresh install of RB2006r3 dragged right off the Disk Image with
no additional plugins or anything. I'm running Mac OS X 10.4.4 on a 1Gz
PowerBook G4 with 1GB of RAM.
Ideas? Anyone?
I've not experienced this on the Mac, but have had a very similar
experience on Windows twice in the last year (most recently last week).
Everything seems to be working OK. A click on 'Run' starts the compile
process as usual. Then, for some unknown reason, the progress bar just
stops. Clicking the 'x' on the 'run' tab to stop the process does
nothing, trying to close RB does nothing. Using the Task Manager to shut
down RB will usually work, but sometimes have to reboot machine.
Any attempt to compile with RB afterwards causes lock-up. Whatever
happens effects all installations of RB, not just the one that 'flaked
out'. (The last 'crash' happened while using 2006r3. After, r3, r2, r1,
2005r4 were all broken. The compile that crashed was on a project that
had just compiled and run fine and was being run again with no changes
made in the code -?)
I've tried uninstalling all versions and reinstalling. Have uninstalled
all versions, removed everthing on the hard drive that searching for
REALbasic or Real Software will find, removed everything in the registry
that searching finds, tried doing a 'repair Windows installation', tried
reinstalling Windows over existing installation - every possible
combination I can think of to try to get rid of the 'gremlin', but
nothing helps.
The only thing I've found that gets me back up is wiping the hard drive
clean and doing a fresh OS install and then reinstall everything.
(...which ain't a bad idea to do once a year anyway with Windows ;-) )
*having good back-ups of everything comes in handy here* (Restoring from
'full system back-up' might work too, but I don't have facility for that
here at work)
Hope you can find a less drastic solution - if you do let us know -
maybe its the same problem on both platforms.
Good luck...
Ken
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
