you can try to re-solder the copper tubing with a plumber portable torch; use the torch to detach the pipes and then, remount the sink heatsinks....or...just cut the pipes close to the heatsink and pinch the tube(s).
Printable View
I have a strange issue. My IP35-E does not seem to be recognizing my sata cd drive. Its a samsung sh-203b.
The board posts, but does not show the drive. I assume it should appear here, but it does not. and i get disk boot failure if I just have the sata drive plugged in and sata cdrom set to boot first. The drive is not the problem, as it worked a few hours ago before i took everything apart for the rebuild
any ideas?
You know I was thinking of doing that but didn't get around to it at the time, but I'll have some free time Wednesday and my meter is still sitting here so I'll see if it changes anything. I doubt it will because I see no change in software voltage readings when the ddr2 vvt is changed.
Thanks again for a reply Ace-a-Rue.
Sounds like a nice project to take on. If im not able to do this id like to maybe get some watercooling gear to cool the northbridge and run the others passive with some antec spot cool fans directing some airflow.
Im not bummed entirely, i know from you guys opinions and results that this board will serve me just fine.
nope, cable was fine. I dumped it though so I wouldn't try using it again.
Now i got another problem. I cant get my xp cd to install on my raptor (74gb). First problem, but has been fixed: The drive would just hang for about 30 seconds connected to port 1. changed to another port and that was fixed, boots up normal speed.
Now when I go to install windows it keeps saying the partition I made is invalid for windows install. and i make a new one and same message. So im stuck. I was hoping to install before bed but i guess not.
i have read about the raptor problems but have not read how to fix them.
The cable might have been fine. I don't think your exact optical drive will show up at the bottom of the first boot device list until the third time you enter BIOS after clearing CMOS. It may depend on how you make the changes in BIOS after clearing CMOS.
One reported "Raptor Cure" is writing zero's to the drive before the OS install.
I remember seeing a similar thing with a couple of boards I have had. As long as you know there is a difference of 8 between what you set & what you get you should be able to work around it.
Tony/Bigtoe (TTR) posted something about this issue a while back being something to do with the BIOS rather than Memset on an ASUS board I think, perhaps if he is still watching he could enlighten us once again.
CN.
I use wipedrive. It boots off cd and then you can write zeros...typically takes me 20-30 minutes on a 74GB raptor.
i should have been more specific...it was Uguru version 3.103 that caused at least one person to burn up some corsair dimms on the Pro board...he thought that he was setting 2.4 or 2.5 Vdimm within Uguru but the actual vdimm was 0.15v higher than "OC Uguru" said it was set to.
I use the WD software, it boots from floppy or CD. Write zeros then install the OS as usual.
Data Lifeguard Diagnostic for DOS
http://support.wdc.com/download/inde...id=999&swid=30
WRITE ZEROS TO DRIVE - The Write Zeros option, wipes any and all data off your drive. This option used when your data is no longer usable or recoverable. If you no longer need any data from your drive and would like to start over, run this option to set your drive to an as new condition. NOTE: Please make sure that you have selected the correct drive to perform this function on as once ran, no data will be recoverable.
first of all, the partition has to be a "primary" partition not an "extended" partition...i presume you knew that.
the other is, you need to set it to be an "active" primary partition...as long as the drive is set to be a primary partition, vista should be able to format it and then install the OS...XP will probably need to have that primary partition designated as "active"...
if you do not have a secondary OS to do this from, then you will have to use MS DOS Fdisk prog or some other variation to get it done within dos environment...the only problem here is that will be done in FAT32...NTFS is the more reliable file system since it can repair itself if it detects an error where FAT32 needs scandisk prog to effect a repair.