G
Gnarlodious
Now my TiBook has crashed hard for the second time while Entourage was in
the front, once while it was asleep and once while I was typing a Usenet
post.
In the latter case nothing moved except the pointer. Not even the clock, and
ForceQuit also didn't do its job, I had to pull the plug.
Strange thing, upon rebooting the email window opened WITH THE CURSOR IN THE
EXACT TEXTUAL POSITION AS WHEN IT CRASHED! Seems a little ironic that this
"improvement" is causing the crash yet allowing me to recover where I left
off.
It seems Office has undergone a fundamental change this update, another
major change is that when I run script:
tell application "Finder"
activate
set msdbdPID to do shell script ¬
("/bin/ps -auwwx | grep -v /usr/bin/awk | /usr/bin/awk '/Microsoft
Database Daemon/ {print $2;}'")
do shell script ("kill -9 " & msdbdPID)
end tell
I no longer get the message "Office database Daemon has unexpectedly quit"
which makes automating the compacting easier.
-- Gnarlie
the front, once while it was asleep and once while I was typing a Usenet
post.
In the latter case nothing moved except the pointer. Not even the clock, and
ForceQuit also didn't do its job, I had to pull the plug.
Strange thing, upon rebooting the email window opened WITH THE CURSOR IN THE
EXACT TEXTUAL POSITION AS WHEN IT CRASHED! Seems a little ironic that this
"improvement" is causing the crash yet allowing me to recover where I left
off.
It seems Office has undergone a fundamental change this update, another
major change is that when I run script:
tell application "Finder"
activate
set msdbdPID to do shell script ¬
("/bin/ps -auwwx | grep -v /usr/bin/awk | /usr/bin/awk '/Microsoft
Database Daemon/ {print $2;}'")
do shell script ("kill -9 " & msdbdPID)
end tell
I no longer get the message "Office database Daemon has unexpectedly quit"
which makes automating the compacting easier.
-- Gnarlie