REFORMAT - Computer Help Needed

[h_i_s]

Had this request for help buried in another thread ... figured, what theheck .. i'll post it here, maybe someone who knows, can offer assistance/suggestions/solutions etc ect.



If it helps .... this is what i have done so far (i think ) & this is where i am at right now:

Pri Master=MAXTOR 6Y080P0 Ultra DMA Mode-5, S.M.A.R.T. Capable and enabled
Pri Slave=Quantum Fireball1ct20 20 Ultra DMA Mode-5, S.M.A.R.T. Capable and enabled
Sec Master=CDROM
Sec Slave=CDROM

Hard Drive 1: Int 13h Drive Number 80h, controlled by EZ BIOS, cylinders 9965, heads 255, sectors 63, capacity 81GB, multi-sector transfer 16 sector, 32-bit transfer enabled(i think), floppy boot protection enabled, logical block address enabled, 'no' for 63-sector data offset.
Hard Drive 2: Int 13h Drive Number 81h, controlled by ROM BIOS, cylinders 1025, heads 255, sectors 63, capacity 8423MB

From here i THOUGHT i had installed an orginal XP factory/complete reformat ... but the Cds
turned out to be 'XP's system recovery'... INSIDEYOURMIND can't find/or remember where His full XP Cds are. ... but was attempting to 'locate' them by other means earlier .... He had to step out... i may be all set with them & have them here when He returns.


OK, so ... now my PC, when started in safe mde, and trying to get the pc to start XP windows, i get an error:

Windows could not start because the following file is missing or corrupt
\WINDOWS\system32\config\SYSTEM
Attempt to repair by starting Windows Setup using original Setup CD-ROM.
Select "r" at the first screen to start repair.
i'd only be GUESSING at how to fix this ... .
Does it NEED to be from an XP Setup CD-ROM ??
OR
Can i use the backup of the system folder of files i saved from my WIN 2000 Pro and burned to CD?? -- Does it MATTER which OS the SYSTEM files are from??
Would i even be able to get the PC to install/save or 'grab up' the files if i insert them
in the CDROM player .... and direct the PC to boot from C:?? i dunno ... and as i said, i'm just guessing at the solution at this point.

Greatly appreciativvvvvvvve to anyone who knows the answer/solution etc ect.my next stop is GOOGLE .. Sometimes the solution is as simple as searching the exact error ... and hoping i have replicated an issue that someone else out there has experienced and provided a solution for ..

Thanks ....

 

[catalina_francisco]

Francisco has posted in the other thread here ...hope it works.

Catalina

 

[h_i_s]

Ahh ... thanks Catalina!!! Appreciate it. ... and am off to try what Francisco has suggested there....

 

[Kajira Callista]

Had this request for help buried in another thread ... figured, what theheck .. i'll post it here, maybe someone who knows, can offer assistance/suggestions/solutions etc ect.



If it helps .... this is what i have done so far (i think ) & this is where i am at right now:

Pri Master=MAXTOR 6Y080P0 Ultra DMA Mode-5, S.M.A.R.T. Capable and enabled
Pri Slave=Quantum Fireball1ct20 20 Ultra DMA Mode-5, S.M.A.R.T. Capable and enabled
Sec Master=CDROM
Sec Slave=CDROM

Hard Drive 1: Int 13h Drive Number 80h, controlled by EZ BIOS, cylinders 9965, heads 255, sectors 63, capacity 81GB, multi-sector transfer 16 sector, 32-bit transfer enabled(i think), floppy boot protection enabled, logical block address enabled, 'no' for 63-sector data offset.
Hard Drive 2: Int 13h Drive Number 81h, controlled by ROM BIOS, cylinders 1025, heads 255, sectors 63, capacity 8423MB

From here i THOUGHT i had installed an orginal XP factory/complete reformat ... but the Cds
turned out to be 'XP's system recovery'... INSIDEYOURMIND can't find/or remember where His full XP Cds are. ... but was attempting to 'locate' them by other means earlier .... He had to step out... i may be all set with them & have them here when He returns.


OK, so ... now my PC, when started in safe mde, and trying to get the pc to start XP windows, i get an error:

Windows could not start because the following file is missing or corrupt
\WINDOWS\system32\config\SYSTEM
Attempt to repair by starting Windows Setup using original Setup CD-ROM.
Select "r" at the first screen to start repair.
i'd only be GUESSING at how to fix this ... .
Does it NEED to be from an XP Setup CD-ROM ??
OR
Can i use the backup of the system folder of files i saved from my WIN 2000 Pro and burned to CD?? -- Does it MATTER which OS the SYSTEM files are from??
Would i even be able to get the PC to install/save or 'grab up' the files if i insert them
in the CDROM player .... and direct the PC to boot from C:?? i dunno ... and as i said, i'm just guessing at the solution at this point.

Greatly appreciativvvvvvvve to anyone who knows the answer/solution etc ect.my next stop is GOOGLE .. Sometimes the solution is as simple as searching the exact error ... and hoping i have replicated an issue that someone else out there has experienced and provided a solution for ..

Thanks ....

https://forum.literotica.com/showthread.php?t=354871

 

[h_i_s]

ALL FIXED .... Hurray !!!

i finally tossed in the towel ... it was TOO big & complex of a job.
It was a job for the NAVY.
The Navy fixed my PC.

i'm barely just up and running ( a TON of Microcrap Updates ALL installed ) just a few hardware driver updates needed, and a ton of custom configurations to make ...... and countless programs to reinstall. i should have this PC 100% to my likings, preferences and personal requirements ... err, by maybe next spring ... heh.

BIG thanks to Francisco, Catalina .... and everyone else who offered suggestions. THANKIES !!! THANKIES !!!! THANKIES !!!!!

 

[h_i_s]

The whole problem STARTED with the PC randomly shutting down abruptly.
After trying everything i could think of and find to diagnos and fix ........
i wiped the entire thing out ... installed a new OS ... and started from scratch.
The daymn thing was doing it AGAIN ... two days after starting all over again with the new OS.
Guess what the problem WAS?!!!?
Bad power strip.

.... WHY didn't i think of that!!!@@#$$#@@# ??!?
It wasn't even the computer. Good push for me to finally upgrade to XP though.
Oh, well. lol

 

[FurryFury]

The whole problem STARTED with the PC randomly shutting down abruptly.
After trying everything i could think of and find to diagnos and fix ........
i wiped the entire thing out ... installed a new OS ... and started from scratch.
The daymn thing was doing it AGAIN ... two days after starting all over again with the new OS.
Guess what the problem WAS?!!!?
Bad power strip.

.... WHY didn't i think of that!!!@@#$$#@@# ??!?
It wasn't even the computer. Good push for me to finally upgrade to XP though.
Oh, well. lol

Is this a lap top or a desk top because I'm having the same damn problem.

Fury

 

[h_i_s]

It's a desktop, FurryFury.

The PC is connected to 2 power strips ... both being plugged into in one wall socket (We do have a decent amount of wall sockets, but no matter where i have lived, there never seem to be enough of those when i've had a PC).

i simply swapped one power supply with another that we had here, issue seems solved
..... so far (crosses fingers).



Those 2 power strips supply power to:

All of the PC (Scanner, Printer, PC Power Supply, Monitor, )
A Home Alert Health Box
Lava Lamp
Cordless Phone
Home Networking Box
Desktop Lamp
reptile heating pad

i hope any of the information in this post, and this thread, will help you FurryFury. Wish i had more i could offer that would be helpful.

 

[FurryFury]

Thanks Sinn, I tried a couple of things with the power strip but it was no go. Not even my IT genius husband can figure it out so I'm taking the damn thing back to the shop today. I hate it when my lap top isn't working!

*sniffles*

Fury

 

[h_i_s]

When you say 'no go' .. did you simply attempt to restart the PC (it's a desktop you are speaking of too.. ??) ? ......

When i had the issue:

i had to reset, by the 'reset/power' button on the backside of the PC. i then turned off the power supply strip. Then left it like that for a few minutes ... came back, & clicked the 'reset/power' button on the backside again ..... and turned the power supply strip on again. Then i restarted the PC by the main power button on the front side of the PC tower.

Otherwise ...... it was a 'no go' for me, as in no power to the PC ... it wouldn't restart.


And, 'if that works' .... then try a new power supply strip.

Just a shot in the dark here, but if you haven't tried that already, maybe it will solve things, if the issue is, 'not being able to get the PC to power up at all'.

 

[FurryFury]

Mine is a lap top. And when I say no go I mean the fan sounds like it's going 90 to nothing but the freaking thing either doesn't start up or does and cuts out on my shortly thereafter.

I used the battery, new one, because the old one died. *grr* and took out the ac power cord and so on.

It's back in the shop so now I'm on a desk top which is less comfortable to me in so many ways.

Fury

 

[h_i_s]

Ahh ... i see, but i know nothing, have no experience what so ever with laptops.
Sorry to hear it ... & hope all goes well with the repairs.
Update us please when you find out what the issue was .... i'd be curious to know.

 

[FurryFury]

Will do. This is the third time in the shop for the same problem. So far we've been told it's the fan burning out and that it had to be reset, also that it might be the battery. *grr*

Fury

 

[h_i_s]

It's fubared, royally.

Ahh shit. Crash ... crash .... crash. my Power supply fan is gone ... brokeded, no twirly-go-roundy (everything is tinged in green too ... no friggin idea on that note).
i won't be on much for a while.

 

[FurryFury]

Yikes!

I'm sorry to hear that.

I'm missing my lil baby lap top something awful but I do have three other computers to use.

Fury

 

[HawkEye38]

The whole problem STARTED with the PC randomly shutting down abruptly.
After trying everything i could think of and find to diagnos and fix ........
i wiped the entire thing out ... installed a new OS ... and started from scratch.
The daymn thing was doing it AGAIN ... two days after starting all over again with the new OS.
Guess what the problem WAS?!!!?
Bad power strip.

.... WHY didn't i think of that!!!@@#$$#@@# ??!?
It wasn't even the computer. Good push for me to finally upgrade to XP though.
Oh, well. lol

Lol, bad, almost as bad as the time my brother's network connection went down. He has kind of a black hand for technology, our conversation went as such...

Him: Ummm, my internet's not working
Me: what did you do?
Him: I dunno, it just stopped working
Me: were you downloading porn again?
Him: fuck off
Me: ok then, what happened?
Him: well, a little icon came up saying my connection was down, so i clicked it and went in and changed all these settings and it still won't work...
Me: Since when do you know what the settings are for the network?
Him: I don't
Me: ::Smacks forehead::

Long story short, I wound up re-formatting the comp several times untill i thought to check the network cable... Yup... it was unplugged

 

[FurryFury]

They called and said my lap top was fixed!

Yay!

It's not.

*grr*

Taking it back tomorrow. *sigh*

Fury

 

[h_i_s]

They called and said my lap top was fixed!

Yay!

It's not.

*grr*

Taking it back tomorrow. *sigh*

Fury

It's bad enough when a computer won't work. And when it's finally 'fixed', it's such a relief. There's nothing like it when that 'bubble' bursts, ... yep.
i share your misery.

Oddly enough, my power supply fan was not working. Last night it suddenly decided to work again. i'm gonna leave the pc powered up today, and see if it will continue to overheat over time and then crash (as it has been doing for days now).

So, i start going over it all in my mind, making a mental list of what i have done, and/or what i have changed that may have effected the outcome aka status of the computer at present:

• On a configurative startup, i select 'debug mode'. Never used it before, but it sounded good at the moment. *shrugs* No clue. i need to read up on that ...
• i opened the case. i removed the cpu fan, and heat sink (got all the dust and grime off them, wasn't much though), and removed and inspected the cpu chip too, then replaced all.
• i inspected all interior connections (hard drives, fans etc). Everything seemed ok. i wonder though, was it a bad thing to unplug the cable clip thingy that connects the two hard drives together to inspect them? i dunno if doing that, could have 'upset' something. i gotta read up on that a bit.
• i left the case open and directed a household fan at the power supply unit to help with the overheating so as to buy some time for trouble shooting.

i restarted the PC after all that, and my colors have been all screwy since. Everything is greenish. Like, i see the reds and blues .. but yellows & whites & light purples have been cancelled out .... like a green haze is sitting on top of all of the other colors. The effect would be the same if i put on some sunglasses with green tinted lenses and wore them while at my PC. i have NO idea wtf is up with this new issue or what is causing it. Only thing i am coming up with is 'display adapters' or something .... i dunno. Perhaps i need to check my video card, or drivers for it or something.

Power supply units are not all that expensive, it depends on WHERE/WHO they are purchased from. The one i'd been looking at is available on one site for about $60 (not including shipping costs) ... but a good check of Ebay fround the same exact power supply for only $25.00 (including shipping). i do know one thing. IF i DO need a power supply unit .... i am going with dual fans because whenever i have had a pc that crashes constantly it is almost always related to an issue of something overheating.

Trying to put a finger on the source of the issue when a computer keeps crashing over and over is so ..... frrrrrrrrrrrrustrating, sometimes.

 

[FurryFury]

Heard from the computer dude today. The factory sent it back, saying that an added extended memory cell is overheating that said computer dude put in so he is replacing that. Hopefully I'll have my lap baby back soon!

Fury

 

[FurryFury]

I got my lap top back yesterday. Now all is better in my lil world!

Fury

 

[h_i_s]

Yay! ..for you, FurryFury!! Congrats ..

 

[FurryFury]

Yay! ..for you, FurryFury!! Congrats ..

Thanks SinnOcent!

I see you are back on your account here so that's good for you! How are your computer challenges coming?

Oh he showed me the extended memory module and one little bit had a bad scratch on it. He thinks that is what might have been the problem now. He being the computer dude.

Fury

 

[AngelicAssassin]

* Any given program, when running, is obsolete.
* Any given program costs more and takes longer each time it is run.
* If a program is useful, it will have to be changed.
* If a program is useless, it will have to be documented.
* Any given program will expand to fill all the available memory.
* The value of a program is inversely proportional to the weight of its output.
* Program complexity grows until it exceeds the capability of the programmer who must maintain it.
* Every non- trivial program has at least one bug
Corollary 1 - A sufficient condition for program triviality is that it have no bugs.
Corollary 2 - At least one bug will be observed after the author leaves the organization.
* Bugs will appear in one part of a working program when another 'unrelated' part is modified.
* The subtlest bugs cause the greatest damage and problems.
Corollary - A subtle bug will modify storage thereby masquerading as some other problem.
* Lulled into Security Law
A 'debugged' program that crashes will wipe out source files on storage devices when there is the least available backup.
* A hardware failure will cause system software to crash, and the customer engineer will blame the programmer.
* A system software crash will cause hardware to act strangely and the programmers will blame the customer engineer.
* Undetectable errors are infinite in variety, in contrast to detectable errors, which by definition are limited.
* Adding manpower to a late software project makes it later.
* Make it possible for programmers to write programs in English, and you will find that programmers can not write in English.
* The documented interfaces between standard software modules will have undocumented quirks.
* The probability of a hardware failure disappearing is inversely proportional to the distance between the computer and the customer engineer.
* A working program is one that has only unobserved bugs.
* No matter how many resources you have, it is never enough.
* Any cool program always requires more memory than you have.
* When you finally buy enough memory, you will not have enough disk space.
* Disks are always full. It is futile to try to get more disk space. Data expands to fill any void.
* If a program actually fits in memory and has enough disk space, it is guaranteed to crash.
* If such a program has not crashed yet, it is waiting for a critical moment before it crashes.
* No matter how good of a deal you get on computer components, the price will always drop immediately after the purchase.
* All components become obsolete.
* The speed with which components become obsolete is directly proportional to the price of the component.
* Software bugs are impossible to detect by anybody except the end user.
* The maintenance engineer will never have seen a model quite like yours before.
* It is axiomatic that any spares required will have just been discontinued and will be no longer in stock.
* Any VDU, from the cheapest to the most expensive, will protect a twenty cent fuse by blowing first.
* Any manufacturer making his warranties dependent upon the device being earthed will only supply power cabling with two wires.
* If a circuit requires n components, then there will be only n - 1 components in locally-held stocks.
* A failure in a device will never appear until it has passed final inspection.
* Adding manpower to a late software project makes it later.
* A program generator creates programs that are more buggy than the program generator.
* All Constants are Variables.
* Constants aren't
* Variables won't
* A part dropped from the workbench will roll to a degree of un-reachability proportional to its importance.
* In a transistor circuit protected by a fuse, the transistor will always blow to protect the fuse.
* The best way to see your boss is to access the internet.
Or...
No matter how hard you work, the boss will only appear when you access the internet.
* The hard drive on your computer will only crash when it contains vital information that has not been backed up.
* Computers don't make errors-What they do they do on purpose.
* If Murphy's laws are so true then how come I can log onto this site and submi............
[connection reset - error message 928 ]
* Gumption's Law (?)
Any problem, no matter how complex, can be found by simple inspection.
Corollary: A nagging intruder with unsought advice will spot it immediately.
* Each computer code has five bugs, and tis number does not depend on how many bugs have been already found (it is conservative).
* Profanity is one language all computer users know.
* The number of bugs always exceeds the number of lines found in a program.
* The most ominous words for those using computers: "Daddy, what does 'Now formatting Drive C mean'?"
* When putting something into memory, always remember where you put it.
* Every non-trivial program contains at least one bug.
* Every non-trivial program can be simplified by at least one line of code.
The conclusion of the last two laws: Every non trivial program can be simplified to one line of code, and it will contain a bug.
* An expert is someone brought in at the last minute to share the blame.
* Debugging is at least twice as hard as writing the program in the first place.
So if your code is as clever as you can possibly make it, then by definition you're not smart enough to debug it.
* Bahaman's Law:
for any given software, the moment you manage to master it, a new version appears.
Yakko's addition:
The new version always manages to change the one feature you need most.
* Patches - don't.
* Most computer errors can be attributed to a similar problem - a screw loose behind the keyboard.
* Whenever you need a crucial file from the server, the network will be down.
* Whenever you need a crucial file from your hard drive, your computer will crash.
* E-mailed tasking will always come just before you log off.
* A quarantined virus - will be opened.
* A chain letter - will be sent. To global. A dozen times.
* The chance of a virus infecting your network is directly proportional to the amount of damage it does.
* The chances of getting off work on time is inversely proportional to how much e-mail the boss leaves for until end of the day.
* The faster you need a hardcopy, the more people will be using the only office printer.
* General Fault Errors are the "Check Engine" light of computers. If it can be fixed, chances are it's not by you.
* A patch is a piece of software which replaces old bugs with new bugs.
* The chances of a program doing what it's supposed to do is inversely proportional to the number of lines of code used to write it.
* The probability of forgetting your password is directly proportional to the frequency of changing it.
* No matter how fantastic your latest and greatest PC is, you will be able to buy it for half the price in 12 months.
* The longer it takes to download a program the more likely it won't run.
* Failure is not an option, it's included with the software.
* A program is good when it's bug free - which is impossible.
* If you forget to save you're work every 5 minutes, it will break down after you've been at it for an hour.
* It's not a bug, it's an undocumented feature.
* The amount of time taken to successfully complete a software project is in direct proportion to the amount of Marketing input.
Corollary: Marketing should not be located in the same city - much less on the same campus - as Engineering and/or Programming.
* The only thing worse than an end-user without a clue is an end-user who has a clue - usually the wrong one.
* According to most Tech Support people, the most common user error message (regardless of Operating System) is ID 10T.
End-users' Corollary 1: most application failures occur between the hours of 2 and 4 am on a Sunday night - with a 6 am Monday deadline for the project.
End-users' Corollary 2: On the graveyard shift, there's no Tech Support to hear you scream!
The last four laws and corollaries were sent by Jim Kirk
* Bugs mysteriously appear when you say, "Watch this!"
corollary: If you call another programmer over to see if he knows what's wrong the bug disappears.
* The probability of bugs appearing is directly proportional to the number and importance of people watching.
* An employee rank is in inverse proportion to his use of a computer, and in proportion to its performance.
* The only program that runs perfectly every time, is a virus
* If a project is completed on schedule, it wasn't debugged properly.
* Non Crash Operating System aren't.
* The worst bugs in your program will show up only during the final review.
The last three laws were sent by Kiran
* The people who say that computers are simple to use are the same people who tell you how to build a watch when you ask what time it is.
* Philington's First Law
If it works, it's production. If it doesn't, it's a test.
* Philington's Second Law
Real programmers don't comment their code. If it was hard to write, it should be hard to understand.
* Format C: fixes all
* Law of Computer Generated Aerodynamics
Computers suck.
* Law of Recycling
A computer that has been on the market for 6 weeks is still usable as a boat anchor.
* Law of Anti-security
The best way past a pesky security feature is a 13-year-old.
* Law of Acceleration
A computer that has surpassed its user's frustration capacity (FC) will accelerate downwards at 9.8 meters per second squared.
* Computers let you waste time efficiently
* Make a system even a moron can use and a moron will use it.
* Make one that requires training or intelligence and only a moron will use it, but there will be more help desk calls.
* The likelihood of problems occurring is inversely proportional to the amount of time remaining before the deadline.
* You will always discover errors in your work after you have printed/submitted it.
* 90% of a programmer errors come from data from other programmers.
* 'Illegal Error' messages only happen when you forget to save your work
* If you make the letters in your Word document bigger and then you print it out, you'll have everything on the first page and only one line on the second.
* the OEM did not actually manufacture the part you need to replace
* By the time you learn your new computer you'll need a new one.
* After a software is released, the first bug found will be by a person who normally does not use that portion of the program but was wondering why he can't do something he normally would not do.
* When the Downloading Window says "99% complete", there will be a fluctuation in the voltage and you'll have to start all over again.
* Millions of people believe they are animals, but I have yet to meet one that believe in Windows' stability. Even human stupidity has limits ;-)
* The troubleshooting guide contains the answer to every problem except yours.
* Plugins Law
Whenever you install a group of plugins one by one just to find out which one can make your software work, you either haven't gotten the right one, or have accidentally skipped the right one or it has become the last one installed.
* No matter what problem you have with your computer - Its Always Microsoft's fault
Corollary: If its not their fault - Blame them anyway
* You will get disconnected from the Internet or experience a computer crash when you are downloading. If you don't experience one within 80% completion, then it will happen at 99%. If you do manage to get the file, then it will turn out to be completely useless and/or invalid.
* You'll always receive an e-mail from a web site that you never visit before.
* 75% of the bugs laws in this page can be applied to MS Windows (Any version).
* Auto Correct - isn't
* Microsoft excel- doesn't
* If you need to shutdown your PC ASAP, It will restart.
* The quickest way to shutdown a PC is to unplug it.
Corollary: ACPI shutdown (sometimes faster to get to than the plug) does not always work.
Corollary: ACPI shutdown will fail most frequently when you run the risk of being caught doing something.
* No matter how big a hard drive you buy, you'll need to double it in a year.
the last three laws were sent by Pliaskos
* Complete computer breakdown will happen shortly after the maintenance person has left.
Sent by Jan Wenall
* A virus will be erased when the hard drive crashes, making it useless for antivirus program to fix it.
* The problem always exists between one keyboard and it's respective chair.
(On submission problem was insomnia... zzzzzz)
* A program that compile on the first run has an error in the algorithm
* Edward V. Berard Law
Walking on water and developing software to specification are easy as long as both are frozen.
* The smaller the size of your email account, the more junk mail you will get
* The boss will always come to your workspace when you accidentally open an adult link
* The more pop-up screens you have, the more likely the boss will come by
The last three laws were sent by Mark
* A computer is only as smart as the person using it
* If it ain't broke, Overclock it!
* If you're in a hurry, your computer will crash, a hard drive will become corrupted, or your files will be erased. Any way, you're screwed if you have a deadline.
* Software Reliability:
Investment in software reliability will increase until it exceeds the probable cost of errors.
* Computer sadism: When the computer causes physical or mental damage to a person and can't receive such a return favor (due to management rules).
* Computer masochism: When a computer takes all the abuse you think you can give it and continues working as it should.
* The sound of grinding metal or the sight of smoke coming from a case is a warning that you are trying to do too much with too little.
* The survivability of a system is directly proportional to the price of the cooling system applied to it and inversely proportional to the amount of use it sees.
* Antivirus systems only effectively work on a virus after given virus has passed its prime.
* The most frightening of viruses is the virus you do not know is already there.
* The amount of damage that a string of code can do is inversely proportional to the length of the string
* You only receive instant messaging, when working on a project that's due instantly
* When designing a program to handle all possible dumb errors, nature creates a dumber user

 

[h_i_s]

................................ i restarted the PC after all that, and my colors have been all screwy since. Everything is greenish. Like, i see the reds and blues .. but yellows & whites & light purples have been cancelled out .... like a green haze is sitting on top of all of the other colors. The effect would be the same if i put on some sunglasses with green tinted lenses and wore them while at my PC. i have NO idea wtf is up with this new issue or what is causing it. Only thing i am coming up with is 'display adapters' or something .... i dunno. Perhaps i need to check my video card, or drivers for it or something.

ok, the green suddenly went away. No reason, i wasn't even trying to fix it ... i was actually getting used to it in a way that made it hardly noticable.

All i did was clean my computer desk a bit. And i'd had the tower sitting sideways with one side open with a household fan directed at the interior ...... so i decided today to turn it facing forward as it should be. i'd turned off the PC for a bit (shouldn't matter though as i'd turned it off a hundred times since it went all green). Suddenly i turn it on just now and the green is gone. All of the colors are normal again.

So, in effect, i fixed my PC by simply turning it about 90 degrees to the left.

 

[greenmands]

You jiggled a wire or connection maybe?