-
March 1st, 2006 03:48 PM
#21
Well, oddly enough, it did turn out to be a HDD issue. I know someone said earlier that it had to be memory related given the error code, but a complete wipe of the drive resolved the issue. I presume there was just some sort of data left over on that HDD that was preventing a Windows install. Wierd eh?
-
March 1st, 2006 03:49 PM
#22
From a friend many years ago:-
Sometimes Tiger, this **** is just voodoo....
Don\'t SYN us.... We\'ll SYN you..... 
\"A nation that draws too broad a difference between its scholars and its warriors will have its thinking done by cowards, and its fighting done by fools.\" - Thucydides
-
March 1st, 2006 05:40 PM
#23
Well, oddly enough, it did turn out to be a HDD issue. I know someone said earlier that it had to be memory related given the error code, but a complete wipe of the drive resolved the issue. I presume there was just some sort of data left over on that HDD that was preventing a Windows install. Wierd eh?
*cough, cough*.............
Originally posted here by Nokia
It is a problem with your hard disc or your RAM.
.......
If Windows starts to install, then BSOD's you will still have files on your HDD, format , run a scandisc (surface) before trying to re-install anything to check your harddrive is ok.
The error codes are memory or HDD read errors not CD-ROM read errors ........
Hope it helps!
Why does no-one listen....
-
March 1st, 2006 05:51 PM
#24
Why does no-one listen....
Maybe because of this
I'm sorry... I just couldn't resist....
Don\'t SYN us.... We\'ll SYN you.....
\"A nation that draws too broad a difference between its scholars and its warriors will have its thinking done by cowards, and its fighting done by fools.\" - Thucydides
-
March 1st, 2006 06:01 PM
#25
Alright, you got me! Ya bastard! Am I ever going to live this one down???!!!? 
No, im not am I! Bet you've got that bookmarked so you can bring it up in 2 years time!!
*nokia goes in search of all TS's posts from 2002!*
-
March 1st, 2006 06:02 PM
#26
I promise that will be the last time I use that against you.....
But you did ask why people might not listen.... It could be a valid answer... 
Don\'t SYN us.... We\'ll SYN you.....
\"A nation that draws too broad a difference between its scholars and its warriors will have its thinking done by cowards, and its fighting done by fools.\" - Thucydides
-
March 3rd, 2006 04:52 AM
#27
Well, oddly enough, it did turn out to be a HDD issue. I know someone said earlier that it had to be memory related given the error code, but a complete wipe of the drive resolved the issue. I presume there was just some sort of data left over on that HDD that was preventing a Windows install. Wierd eh?
Most of us were assuming you already did that ...
-
March 3rd, 2006 03:02 PM
#28
Yeah yeah...But really, I've never heard of data on the HD actually preventing an install. Doesn't a fresh Windows install end up overighting all the data anyway, good or bad as it were?
Well, it made sense at the time anyway...
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
Forum Rules
|
|
Reply With Quote
Bookmarks