Quote:
|
Originally Posted by Dead Mans Hand
Erm, maybe a noob question but could you provide more information on the starforce CD? Unless it's overly personal, then, I really don't need to hear it.
|
Sorry, I don't quite understand what you mean?
ok, keeping it technical, I'm going to try leaving different disks in the drive and boot up when I get home from work and see what happens.
I don't really want to change the bios boot order if I can help it, as I set it that way for a reason...
All I will say on this so far is that when the drive 'spinns-up' when I first boot the computer, it's not the normal quick 'buzz' you get from the drive when windows is checking for something to load from- in that case usually the drive will spin for a couple of seconds, the little light will come on then it stops. What I am talking about here (and experimenting with trying to prevent/alter) is my optical drive constantly spinning for about 20 minutes non-stop at what sounds (and feels through vibration/resonance in the case- how I noticed it in the first place) like higher revolutions than normal; it's like it's constantly cycling at very high revs, a completely different sound to when the drive is reading or writing at 52x speed. So far the drive 'works' in all respects, but I am certain it never made the strange spinning noise until I installed the two games mentioned in my posts
here(starts posts on page 3) ok, just noticed that topic is open again
I'm trying to keep a fairly open mind as to the cause of the problem here, but this sounds all too familiar to what some other people are reporting in connection with this software. I'm fairly tech savvy when it comes to using computers, but that doesn't mean I have micro$oft certification or whatever
suffice to say if it ain't broke, then I don't try and fix it. The issue here is wheather or not something is broken and what, if anything, I can to to remedy it. So far, the only solution (mentioned in the other topic) is to remove any disk from the drive before shutting down and any subsequent rebooting of the machine, and whilst this in itself is a straightforward suggestion, it still does not answer to the root cause of this 'problem' I and others appear to be suffering from.