|
pc
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
SATA saga - resolved
problem with my Asus motherboard. Before I changed mobos, I installed the new RAM (DDR 400) in my old (Asus) motherboard - and guess what? The fecking thing worked. So it looks like my problem was dodgy memory. It certainly felt like that - but I had two memory sticks (512Mb and 256Mb) and I used them independently and still got BSODs. So it was logical to assume that it wasn't RAM. But this new RAM module seems to have cured the problem. So it must have been. But how could flashing a BIOS screw-up *two* DIMMs? Computers never fail to surprise me. Thanks to everyone who helped. I still say that some mobos, SATA and XP don't mix very well. Bobby Glad to hear you got it resolved.
Curious as to why flashing the BIOS would damage mem chips. I, for one, resist the temptation to flash the BIOS until I absolutely need some advanced functionality. If it ain't broke, don't fix it is my motto. Show quoteHide quote "Bobby" <bo***@aventuremail.com> wrote in message news:3b7b4cF6dveqeU1@individual.net... >I bought a new motherboard and memory yesterday to resolve my on-going SATA > problem with my Asus motherboard. > > Before I changed mobos, I installed the new RAM (DDR 400) in my old (Asus) > motherboard - and guess what? The fecking thing worked. > > So it looks like my problem was dodgy memory. It certainly felt like > that - > but I had two memory sticks (512Mb and 256Mb) and I used them > independently > and still got BSODs. So it was logical to assume that it wasn't RAM. > > But this new RAM module seems to have cured the problem. So it must have > been. But how could flashing a BIOS screw-up *two* DIMMs? > > Computers never fail to surprise me. > > Thanks to everyone who helped. > > I still say that some mobos, SATA and XP don't mix very well. > > Bobby > > > Believe, I would not now flash the BIOS if I needed a BIOS upgrade to find
next week's lottery numbers. Show quoteHide quote "BP" <replyto***@only.net> wrote in message news:vICdnUHpqIjaGtPfRVn-iA@conversent.net... > Glad to hear you got it resolved. > Curious as to why flashing the BIOS would damage mem chips. I, for one, > resist the temptation to flash the BIOS until I absolutely need some > advanced functionality. If it ain't broke, don't fix it is my motto. > > "Bobby" <bo***@aventuremail.com> wrote in message > news:3b7b4cF6dveqeU1@individual.net... >>I bought a new motherboard and memory yesterday to resolve my on-going >>SATA >> problem with my Asus motherboard. >> >> Before I changed mobos, I installed the new RAM (DDR 400) in my old >> (Asus) >> motherboard - and guess what? The fecking thing worked. >> >> So it looks like my problem was dodgy memory. It certainly felt like >> that - >> but I had two memory sticks (512Mb and 256Mb) and I used them >> independently >> and still got BSODs. So it was logical to assume that it wasn't RAM. >> >> But this new RAM module seems to have cured the problem. So it must have >> been. But how could flashing a BIOS screw-up *two* DIMMs? >> >> Computers never fail to surprise me. >> >> Thanks to everyone who helped. >> >> I still say that some mobos, SATA and XP don't mix very well. >> >> Bobby >> >> >> > > I'm pleased you've fixed it too. Interesting that the fault happened only
after you were installing the SATA drive in your machine and not before - perhaps ESD do you think? You'd think that running the machine in a minimal configuration while attempting to install windows (as I suggested earlier in one of the threads) would have surely picked up a dodgy DIMM if you'd tried them one at a time. The only possible explanation is that whatever happened affected both DIMMs. Memory modules are extremely sensitive to electrical damage so it wouldn't take much (e.g. just touching them without using a properly grounded wrist strap could do it). This is also another reason why its best to flash motherboards in a minimal configuration too - everything unnecessary unplugged/removed (including only having one DIMM installed if the mobo will run like this). Having said that I doubt the actual flashing process caused this problem - probably something else around the same time. It would be worth testing out the memory modules in another board before deciding they're faulty - they may have just developed an "incompatibility" with that mobo. I've had that happen to me when I installed unapproved (but correct spec) Micron memory in my Tyan S2460 - eventually I started getting memory errors which Samsung memory showed no sign of producing yet the Micron modules tested fine in another board. 3 years on the Samsung modules are still going perfectly. Its true that some configurations are less compatible than others but as you've proven with your replacement memory module, it wasn't the combination of mobo, SATA and XP that caused your problem. As long as people choose their components after some research looking at "manufacturer recommended lists" for compatibility, it shouldn't be a problem. Paul So now that you've ascertained it was the memory all along are you Show quoteHide quote "Bobby" <bo***@aventuremail.com> wrote in message news:3b7b4cF6dveqeU1@individual.net... >I bought a new motherboard and memory yesterday to resolve my on-going SATA > problem with my Asus motherboard. > > Before I changed mobos, I installed the new RAM (DDR 400) in my old (Asus) > motherboard - and guess what? The fecking thing worked. > > So it looks like my problem was dodgy memory. It certainly felt like > that - > but I had two memory sticks (512Mb and 256Mb) and I used them > independently > and still got BSODs. So it was logical to assume that it wasn't RAM. > > But this new RAM module seems to have cured the problem. So it must have > been. But how could flashing a BIOS screw-up *two* DIMMs? > > Computers never fail to surprise me. > > Thanks to everyone who helped. > > I still say that some mobos, SATA and XP don't mix very well. > > Bobby On Sat, 2 Apr 2005 14:40:33 +0100, "Paul Murphy"
<p_murphynothanks@tospamhotmail.com> wrote: Show quoteHide quote >I'm pleased you've fixed it too. Interesting that the fault happened only Memory timings could have easily gotten changed in a BIOS flash and>after you were installing the SATA drive in your machine and not before - >perhaps ESD do you think? You'd think that running the machine in a minimal >configuration while attempting to install windows (as I suggested earlier in >one of the threads) would have surely picked up a dodgy DIMM if you'd tried >them one at a time. The only possible explanation is that whatever happened >affected both DIMMs. Memory modules are extremely sensitive to electrical >damage so it wouldn't take much (e.g. just touching them without using a >properly grounded wrist strap could do it). This is also another reason why >its best to flash motherboards in a minimal configuration too - everything >unnecessary unplugged/removed (including only having one DIMM installed if >the mobo will run like this). Having said that I doubt the actual flashing >process caused this problem - probably something else around the same time. >It would be worth testing out the memory modules in another board before >deciding they're faulty - they may have just developed an "incompatibility" >with that mobo. I've had that happen to me when I installed unapproved (but >correct spec) Micron memory in my Tyan S2460 - eventually I started getting >memory errors which Samsung memory showed no sign of producing yet the >Micron modules tested fine in another board. 3 years on the Samsung modules >are still going perfectly. > >Its true that some configurations are less compatible than others but as >you've proven with your replacement memory module, it wasn't the combination >of mobo, SATA and XP that caused your problem. As long as people choose >their components after some research looking at "manufacturer recommended >lists" for compatibility, it shouldn't be a problem. > >Paul > >So now that you've ascertained it was the memory all along are you >"Bobby" <bo***@aventuremail.com> wrote in message >news:3b7b4cF6dveqeU1@individual.net... >>I bought a new motherboard and memory yesterday to resolve my on-going SATA >> problem with my Asus motherboard. >> >> Before I changed mobos, I installed the new RAM (DDR 400) in my old (Asus) >> motherboard - and guess what? The fecking thing worked. >> >> So it looks like my problem was dodgy memory. It certainly felt like >> that - >> but I had two memory sticks (512Mb and 256Mb) and I used them >> independently >> and still got BSODs. So it was logical to assume that it wasn't RAM. >> >> But this new RAM module seems to have cured the problem. So it must have >> been. But how could flashing a BIOS screw-up *two* DIMMs? >> >> Computers never fail to surprise me. >> >> Thanks to everyone who helped. >> >> I still say that some mobos, SATA and XP don't mix very well. >> >> Bobby > what worked in one config didn't work in another.
Show quote
Hide quote
On Sat, 2 Apr 2005 11:40:11 +0100, "Bobby" <bo***@aventuremail.com> It could very well be that you inadvertantly damaged the new memorywrote: >I bought a new motherboard and memory yesterday to resolve my on-going SATA >problem with my Asus motherboard. > >Before I changed mobos, I installed the new RAM (DDR 400) in my old (Asus) >motherboard - and guess what? The fecking thing worked. > >So it looks like my problem was dodgy memory. It certainly felt like that - >but I had two memory sticks (512Mb and 256Mb) and I used them independently >and still got BSODs. So it was logical to assume that it wasn't RAM. > >But this new RAM module seems to have cured the problem. So it must have >been. But how could flashing a BIOS screw-up *two* DIMMs? > >Computers never fail to surprise me. > >Thanks to everyone who helped. > >I still say that some mobos, SATA and XP don't mix very well. > >Bobby > > through ESD. It could also have been that the memory timings set in the bios were the problem and needed to be adjusted after the BIOS flash/reset. In either event, if you had ran Memtest86 like we recommended, you could have found this out without wasting the money on a new motherboard. I am glad it is all working for you though. I bypassed SATA driver load issues by including the SATA controller drivers from various manufacturers in my XP cd so that they will load without having to use the floppy
Show quote
Hide quote
"NoneOfBusiness" <NoneOfBusin***@nob.net> wrote in message I know how to create a slipstreamed SP2 inclusive XP CD but where did you news:k7it411blr1urfb4bs4atsuvthrki8q6lu@4ax.com... > On Sat, 2 Apr 2005 11:40:11 +0100, "Bobby" <bo***@aventuremail.com> > wrote: > >>I bought a new motherboard and memory yesterday to resolve my on-going >>SATA >>problem with my Asus motherboard. >> >>Before I changed mobos, I installed the new RAM (DDR 400) in my old (Asus) >>motherboard - and guess what? The fecking thing worked. >> >>So it looks like my problem was dodgy memory. It certainly felt like >>that - >>but I had two memory sticks (512Mb and 256Mb) and I used them >>independently >>and still got BSODs. So it was logical to assume that it wasn't RAM. >> >>But this new RAM module seems to have cured the problem. So it must have >>been. But how could flashing a BIOS screw-up *two* DIMMs? >> >>Computers never fail to surprise me. >> >>Thanks to everyone who helped. >> >>I still say that some mobos, SATA and XP don't mix very well. >> >>Bobby >> >> > It could very well be that you inadvertantly damaged the new memory > through ESD. It could also have been that the memory timings set in > the bios were the problem and needed to be adjusted after the BIOS > flash/reset. In either event, if you had ran Memtest86 like we > recommended, you could have found this out without wasting the money > on a new motherboard. > > I am glad it is all working for you though. I bypassed SATA driver > load issues by including the SATA controller drivers from various > manufacturers in my XP cd so that they will load without having to use > the floppy put the drivers - or was it a case that you still had to point the installation program to their location on the CD when it asked for the floppy disk to be inserted into A:? Paul On Sat, 2 Apr 2005 17:52:15 +0100, "Paul Murphy"
<p_murphynothanks@tospamhotmail.com> wrote: Show quoteHide quote >"NoneOfBusiness" <NoneOfBusin***@nob.net> wrote in message Take a look at http://unattended.msfn.org/>news:k7it411blr1urfb4bs4atsuvthrki8q6lu@4ax.com... >> On Sat, 2 Apr 2005 11:40:11 +0100, "Bobby" <bo***@aventuremail.com> >> wrote: >> >>>I bought a new motherboard and memory yesterday to resolve my on-going >>>SATA >>>problem with my Asus motherboard. >>> >>>Before I changed mobos, I installed the new RAM (DDR 400) in my old (Asus) >>>motherboard - and guess what? The fecking thing worked. >>> >>>So it looks like my problem was dodgy memory. It certainly felt like >>>that - >>>but I had two memory sticks (512Mb and 256Mb) and I used them >>>independently >>>and still got BSODs. So it was logical to assume that it wasn't RAM. >>> >>>But this new RAM module seems to have cured the problem. So it must have >>>been. But how could flashing a BIOS screw-up *two* DIMMs? >>> >>>Computers never fail to surprise me. >>> >>>Thanks to everyone who helped. >>> >>>I still say that some mobos, SATA and XP don't mix very well. >>> >>>Bobby >>> >>> >> It could very well be that you inadvertantly damaged the new memory >> through ESD. It could also have been that the memory timings set in >> the bios were the problem and needed to be adjusted after the BIOS >> flash/reset. In either event, if you had ran Memtest86 like we >> recommended, you could have found this out without wasting the money >> on a new motherboard. >> >> I am glad it is all working for you though. I bypassed SATA driver >> load issues by including the SATA controller drivers from various >> manufacturers in my XP cd so that they will load without having to use >> the floppy > >I know how to create a slipstreamed SP2 inclusive XP CD but where did you >put the drivers - or was it a case that you still had to point the >installation program to their location on the CD when it asked for the >floppy disk to be inserted into A:? > >Paul > All sorts of neat stuff here. I did a full unattended install of xp sp2 with office, av, many little apps, reg tweaks, etc. Of course i about filled a DVD up in the process but it beats loading software manually.. The directions for including SATA/RAID drivers are there.
Show quote
Hide quote
"NoneOfBusiness" <NoneOfBusin***@nob.net> wrote in message Thanks for that link (and Sunny), I've bookmarked it. It sure looks news:n7st41h3o6g431330uftfuk6dkdqiq656v@4ax.com... > On Sat, 2 Apr 2005 17:52:15 +0100, "Paul Murphy" > <p_murphynothanks@tospamhotmail.com> wrote: > >>"NoneOfBusiness" <NoneOfBusin***@nob.net> wrote in message >>news:k7it411blr1urfb4bs4atsuvthrki8q6lu@4ax.com... >>> On Sat, 2 Apr 2005 11:40:11 +0100, "Bobby" <bo***@aventuremail.com> >>> wrote: >>> >>>>I bought a new motherboard and memory yesterday to resolve my on-going >>>>SATA >>>>problem with my Asus motherboard. >>>> >>>>Before I changed mobos, I installed the new RAM (DDR 400) in my old >>>>(Asus) >>>>motherboard - and guess what? The fecking thing worked. >>>> >>>>So it looks like my problem was dodgy memory. It certainly felt like >>>>that - >>>>but I had two memory sticks (512Mb and 256Mb) and I used them >>>>independently >>>>and still got BSODs. So it was logical to assume that it wasn't RAM. >>>> >>>>But this new RAM module seems to have cured the problem. So it must have >>>>been. But how could flashing a BIOS screw-up *two* DIMMs? >>>> >>>>Computers never fail to surprise me. >>>> >>>>Thanks to everyone who helped. >>>> >>>>I still say that some mobos, SATA and XP don't mix very well. >>>> >>>>Bobby >>>> >>>> >>> It could very well be that you inadvertantly damaged the new memory >>> through ESD. It could also have been that the memory timings set in >>> the bios were the problem and needed to be adjusted after the BIOS >>> flash/reset. In either event, if you had ran Memtest86 like we >>> recommended, you could have found this out without wasting the money >>> on a new motherboard. >>> >>> I am glad it is all working for you though. I bypassed SATA driver >>> load issues by including the SATA controller drivers from various >>> manufacturers in my XP cd so that they will load without having to use >>> the floppy >> >>I know how to create a slipstreamed SP2 inclusive XP CD but where did you >>put the drivers - or was it a case that you still had to point the >>installation program to their location on the CD when it asked for the >>floppy disk to be inserted into A:? >> >>Paul >> > > Take a look at http://unattended.msfn.org/ > > All sorts of neat stuff here. I did a full unattended install of xp > sp2 with office, av, many little apps, reg tweaks, etc. Of course i > about filled a DVD up in the process but it beats loading software > manually.. The directions for including SATA/RAID drivers are there. > interesting although allot of work! I suspect it would be easier for me to just keep using a floppy disk at the required moment and save an image of my final setup to a restore DVD. If I wanted a master CD (or DVD) that I could use to perform a "common" install on a wide variety of hardware that'd be ideal though. It sure would have been helpful to know when I used to work as a computer tech! Paul On Sat, 2 Apr 2005 21:30:46 +0100, "Paul Murphy"
<p_murphynothanks@tospamhotmail.com> wrote: Show quoteHide quote >"NoneOfBusiness" <NoneOfBusin***@nob.net> wrote in message Once you have it built, its worth it, plus you can add all your>news:n7st41h3o6g431330uftfuk6dkdqiq656v@4ax.com... >> On Sat, 2 Apr 2005 17:52:15 +0100, "Paul Murphy" >> <p_murphynothanks@tospamhotmail.com> wrote: >> >>>"NoneOfBusiness" <NoneOfBusin***@nob.net> wrote in message >>>news:k7it411blr1urfb4bs4atsuvthrki8q6lu@4ax.com... >>>> On Sat, 2 Apr 2005 11:40:11 +0100, "Bobby" <bo***@aventuremail.com> >>>> wrote: >>>> >>>>>I bought a new motherboard and memory yesterday to resolve my on-going >>>>>SATA >>>>>problem with my Asus motherboard. >>>>> >>>>>Before I changed mobos, I installed the new RAM (DDR 400) in my old >>>>>(Asus) >>>>>motherboard - and guess what? The fecking thing worked. >>>>> >>>>>So it looks like my problem was dodgy memory. It certainly felt like >>>>>that - >>>>>but I had two memory sticks (512Mb and 256Mb) and I used them >>>>>independently >>>>>and still got BSODs. So it was logical to assume that it wasn't RAM. >>>>> >>>>>But this new RAM module seems to have cured the problem. So it must have >>>>>been. But how could flashing a BIOS screw-up *two* DIMMs? >>>>> >>>>>Computers never fail to surprise me. >>>>> >>>>>Thanks to everyone who helped. >>>>> >>>>>I still say that some mobos, SATA and XP don't mix very well. >>>>> >>>>>Bobby >>>>> >>>>> >>>> It could very well be that you inadvertantly damaged the new memory >>>> through ESD. It could also have been that the memory timings set in >>>> the bios were the problem and needed to be adjusted after the BIOS >>>> flash/reset. In either event, if you had ran Memtest86 like we >>>> recommended, you could have found this out without wasting the money >>>> on a new motherboard. >>>> >>>> I am glad it is all working for you though. I bypassed SATA driver >>>> load issues by including the SATA controller drivers from various >>>> manufacturers in my XP cd so that they will load without having to use >>>> the floppy >>> >>>I know how to create a slipstreamed SP2 inclusive XP CD but where did you >>>put the drivers - or was it a case that you still had to point the >>>installation program to their location on the CD when it asked for the >>>floppy disk to be inserted into A:? >>> >>>Paul >>> >> >> Take a look at http://unattended.msfn.org/ >> >> All sorts of neat stuff here. I did a full unattended install of xp >> sp2 with office, av, many little apps, reg tweaks, etc. Of course i >> about filled a DVD up in the process but it beats loading software >> manually.. The directions for including SATA/RAID drivers are there. >> >Thanks for that link (and Sunny), I've bookmarked it. It sure looks >interesting although allot of work! I suspect it would be easier for me to >just keep using a floppy disk at the required moment and save an image of my >final setup to a restore DVD. If I wanted a master CD (or DVD) that I could >use to perform a "common" install on a wide variety of hardware that'd be >ideal though. It sure would have been helpful to know when I used to work as >a computer tech! > >Paul > updates, patches, whatnot to it for next time so that you don't have to update your image. I tell you its worth it. I use images too, but i also keep this updated Paul Murphy wrote:
Show quoteHide quote > "NoneOfBusiness" <NoneOfBusin***@nob.net> wrote in message http://unattended.msfn.org/intermediate/drivers/raid.htm> news:k7it411blr1urfb4bs4atsuvthrki8q6lu@4ax.com... > >>On Sat, 2 Apr 2005 11:40:11 +0100, "Bobby" <bo***@aventuremail.com> >>wrote: >> >> >>>I bought a new motherboard and memory yesterday to resolve my on-going >>>SATA >>>problem with my Asus motherboard. >>> >>>Before I changed mobos, I installed the new RAM (DDR 400) in my old (Asus) >>>motherboard - and guess what? The fecking thing worked. >>> >>>So it looks like my problem was dodgy memory. It certainly felt like >>>that - >>>but I had two memory sticks (512Mb and 256Mb) and I used them >>>independently >>>and still got BSODs. So it was logical to assume that it wasn't RAM. >>> >>>But this new RAM module seems to have cured the problem. So it must have >>>been. But how could flashing a BIOS screw-up *two* DIMMs? >>> >>>Computers never fail to surprise me. >>> >>>Thanks to everyone who helped. >>> >>>I still say that some mobos, SATA and XP don't mix very well. >>> >>>Bobby >>> >>> >> >>It could very well be that you inadvertantly damaged the new memory >>through ESD. It could also have been that the memory timings set in >>the bios were the problem and needed to be adjusted after the BIOS >>flash/reset. In either event, if you had ran Memtest86 like we >>recommended, you could have found this out without wasting the money >>on a new motherboard. >> >>I am glad it is all working for you though. I bypassed SATA driver >>load issues by including the SATA controller drivers from various >>manufacturers in my XP cd so that they will load without having to use >>the floppy > > > I know how to create a slipstreamed SP2 inclusive XP CD but where did you > put the drivers - or was it a case that you still had to point the > installation program to their location on the CD when it asked for the > floppy disk to be inserted into A:? NoneOfBusiness wrote:
Show quoteHide quote >On Sat, 2 Apr 2005 11:40:11 +0100, "Bobby" <bo***@aventuremail.com> How did you do that with the drivers?>wrote: > > > >>I bought a new motherboard and memory yesterday to resolve my on-going SATA >>problem with my Asus motherboard. >> >>Before I changed mobos, I installed the new RAM (DDR 400) in my old (Asus) >>motherboard - and guess what? The fecking thing worked. >> >>So it looks like my problem was dodgy memory. It certainly felt like that - >>but I had two memory sticks (512Mb and 256Mb) and I used them independently >>and still got BSODs. So it was logical to assume that it wasn't RAM. >> >>But this new RAM module seems to have cured the problem. So it must have >>been. But how could flashing a BIOS screw-up *two* DIMMs? >> >>Computers never fail to surprise me. >> >>Thanks to everyone who helped. >> >>I still say that some mobos, SATA and XP don't mix very well. >> >>Bobby >> >> >> >> >It could very well be that you inadvertantly damaged the new memory >through ESD. It could also have been that the memory timings set in >the bios were the problem and needed to be adjusted after the BIOS >flash/reset. In either event, if you had ran Memtest86 like we >recommended, you could have found this out without wasting the money >on a new motherboard. > >I am glad it is all working for you though. I bypassed SATA driver >load issues by including the SATA controller drivers from various >manufacturers in my XP cd so that they will load without having to use >the floppy > > George Justice wrote:
> HTML/mime - ignored.> Part 1.1 Type: Plain Text (text/plain) > Encoding: 7bit -- "If you want to post a followup via groups.google.com, don't use the broken "Reply" link at the bottom of the article. Click on "show options" at the top of the article, then click on the "Reply" at the bottom of the article headers." - Keith Thompson "George Justice" <Crossb***@netscape.net> wrote in message <snip and HTML turned off for newsgroup>news:%23e30v69OFHA.3156@TK2MSFTNGP15.phx.gbl... NoneOfBusiness wrote: On Sat, 2 Apr 2005 11:40:11 +0100, "Bobby" <bo***@aventuremail.com> wrote: How did you do that with the drivers? See NoneofBusiness's reply to that same question earlier in this thread. Paul PS in case your newserver doesn't have that post the link you need is http://unattended.msfn.org/ If you read the OP's posts carefully, you'll realize
all his troubles started with his using the wrong pair of SATA connections on his mobo. There are 2 sets, somewhat confusingly labeled and it takes careful reading of the manual to sort this out. Show quoteHide quote "George Justice" <Crossb***@netscape.net> wrote in message news:%23e30v69OFHA.3156@TK2MSFTNGP15.phx.gbl... > NoneOfBusiness wrote: > >>On Sat, 2 Apr 2005 11:40:11 +0100, "Bobby" <bo***@aventuremail.com> >>wrote: >> >> >> >>>I bought a new motherboard and memory yesterday to resolve my >>>on-going SATA >>>problem with my Asus motherboard. >>> >>>Before I changed mobos, I installed the new RAM (DDR 400) in my old >>>(Asus) >>>motherboard - and guess what? The fecking thing worked. >>> >>>So it looks like my problem was dodgy memory. It certainly felt like >>>that - >>>but I had two memory sticks (512Mb and 256Mb) and I used them >>>independently >>>and still got BSODs. So it was logical to assume that it wasn't RAM. >>> >>>But this new RAM module seems to have cured the problem. So it must >>>have >>>been. But how could flashing a BIOS screw-up *two* DIMMs? >>> >>>Computers never fail to surprise me. >>> >>>Thanks to everyone who helped. >>> >>>I still say that some mobos, SATA and XP don't mix very well. >>> >>>Bobby >>> >>> >>> >>> >>It could very well be that you inadvertantly damaged the new memory >>through ESD. It could also have been that the memory timings set in >>the bios were the problem and needed to be adjusted after the BIOS >>flash/reset. In either event, if you had ran Memtest86 like we >>recommended, you could have found this out without wasting the money >>on a new motherboard. >> >>I am glad it is all working for you though. I bypassed SATA driver >>load issues by including the SATA controller drivers from various >>manufacturers in my XP cd so that they will load without having to use >>the floppy >> >> > How did you do that with the drivers? > 
Other interesting topics
Modem development question...
how to install XP on password locked Sony Vaio with 2000 installed? Abit + p4 for gaming?? memtest86... bit of help Are they making Hard Disks out of lighter material? USB distance limits? boot up Finding cause of random crash. Largest Hard Disk size with Promise Ultra66? Need info about Pocket PCs and similar handheld devices |
|||||||||||||||||||||||
