Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
General
GeneralPortable MacsHardwareNetworking
Applications
Mac ApplicationsEudoraFirefox / MozillaInternet ExplorerOutlook ExpressMS OfficeEntourageExcelPowerPointWordVirtual PCMedia PlayerOther MS Products
Programming
Mac ProgrammingCodeWarriorPerl
Country Specific
Australian Mac GroupUK Mac Group

Mac Forum / Programming / Mac Programming / June 2007



Tip: Looking for answers? Try searching our database.

system problems?

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Santa Claus - 21 Jun 2007 23:10 GMT
i know this isn't the proper place to ask this but i'm going to ask
anyway.

this latest server (10.4.10) update brought it back into focus so i
thought i may as well ask.  i'll give my system specs and test results
below.

when i reboot after installing something or somehow corrupting or
changing the prebinding information (installing system updates) or
resetting the NVRAM (option-command-o-f while rebooting and typing what
apple told me "reset-NVRAM" and "reset-ALL") or resetting the parameter
ram (option-command-r-p while booting), it takes 2 reboots to get the
computer running smoothly again.  after the first reboot, it doesn't
recognize the dvd eject button and when rebooting, the dialog box is
centered on the top left pixel of the screen allowing me to only see the
blue "reboot" button.  several other odd things happen if this reboot is
left to run and all of them are too odd to mention or remember.

after i reboot the second time, everything is running flawlessly.

i have reinstalled the system software that came with the system and the
same problems occur.

i ran the apple test dvd and it told me everything is fine.

quad core g5, 4 gb ram, dual 500 gig drives in non-raid configuration,
osx server 10.4.10 build 8R218

maybe one of you folks out there can either tell me
 a) this is normal and shouldn't upset you
 b) something is really messed up and you need a new set of system
disks or something
 c) just use program "xxx" from the terminal mode to fix it right back
up, you should have known about it.
Gregory Weston - 22 Jun 2007 13:44 GMT
> i know this isn't the proper place to ask this but i'm going to ask
> anyway.

I know I'm just going to end up encouraging the behavior by rewarding
it, but if you know this is the wrong place to post why don't you post
to the _right_ place? The number of groups that start 'comp.sys.mac.'
isn't so huge that you're likely to miss 'comp.sys.mac.system' when
you're posting a message with the subject "system problems."

> maybe one of you folks out there can either tell me
>   a) this is normal and shouldn't upset you

This is absolutely not normal. As you've been told before.

Also not normal is any ongoing need to reset the NVRAM on any Mac ever
shipped.

>   b) something is really messed up and you need a new set of system
> disks or something

That one is my guess, leaning toward the "or something." I don't imagine
that defective installation media would exhibit the behavior you're
seeing and if there was a bad run of install disks we'd probably have a
second report of this behavior at Macintouch or MacFixit or someplace.

Here's a question in two parts:
1. How long have you had your machine and,
2. Does it spend a significant amount of time not connected to a live
electrical outlet? (Do you unplug it or turn off a power strip every
night, or do you often lose power for extended periods of time?)
Santa Claus - 23 Jun 2007 12:05 GMT
> > i know this isn't the proper place to ask this but i'm going to ask
> > anyway.
[quoted text clipped - 4 lines]
> isn't so huge that you're likely to miss 'comp.sys.mac.system' when
> you're posting a message with the subject "system problems."

thanks for posting the group i should subscribe to.  i won't bother this
group again with questions of this sort (unless you want to ask specific
questions about THIS problem).

> > maybe one of you folks out there can either tell me
> >   a) this is normal and shouldn't upset you
[quoted text clipped - 17 lines]
> electrical outlet? (Do you unplug it or turn off a power strip every
> night, or do you often lose power for extended periods of time?)

1) a little over a year.
2) it operates s a server and is on all the time.  we had a power
failure for 5 hours once during the time i had this machine and i also
noticed we must have had a power failure yesterday but that one didn't
even make my account log out. (i have a relay with a sealing circuit
-where the contacts connect across the power on contacts to seal the
circuit on, an industrial wiring normal- and that supplies power to my
tv.  my tv wouldn't turn on last night and i found out the relay needed
to be reactivated therefore i must have had a power failure sometime)

could "too close to the power lines" be the problem?  walking around the
house with the "fox and hound" looking for a specific wire in the walls
gives me an extremely loud background hum until i get about 20 feet away
from the house then it goes silent as it normally acts.  i'm thinking
the power main lines running ten feet behind my house may be inducing
electrical currents within my machine in a similar way as an electrical
transformer and if that's the case, i'll be able to do absolutely
nothing about that.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.