Dark_Nemesis

Thinking of replacing my keyboard and mouse in a bit, but thanks for the info! Good to know for future modding projects as I will probably come up with something fun to do with with my next keyboard as well

Thanx bro! Glad I could help It's been so long since I made this, I thought the tread died a long time ago... (sorry for extremely late reply) Hope you were satisfied with the result! Still use mine still no problem with it, adhesive still holds up nicely after 2 years. Hope you're having a nice weekend!

Yeah, me too.... Tried wrapping a keycap just for fun, didn't end up looking very pretty tho

Oh yeah lol, accelereation increased significantly

mayby 45 minuts, removing all the buttons and cleaning the keyboard takes half the time

.... Soo CHDSK just viped my 3tb mass storage drive ... I was backing up some data, moved a HDD from my NAS to my PC, disconnected one drive to be able to connect another drive. Restarting my PC to get the drive I just connected to show up, and when the PC booted up CHKDSK wanted to check the drive (I didn't watch it closely enough to cancel in time). When PC booted up after running CHKDSK, the WD 3Tb I just connected, had been assigned the drive name of the drive previously connected to that SATA port. In short -> I disconnected ":1TB#1" -> connected ":WD3Tb" -> restarted the PC -> the 3TB drive previously named ":WD3Tb" had now been renamed to ":1TB#1" and the drive was empty. Already tried some free data recovery tools, but to no avail. I have kept the drive disconnected since the incident. Log file found on the drive: _______________________________________________________________________________________ Checking file system on Q: The type of the file system is NTFS. Volume label is 1 TB # 1. One of your disks needs to be checked for consistency. You may cancel the disk check, but it is strongly recommended that you continue. Windows will now check the disk. CHKDSK is verifying files (stage 1 of 3)... Attribute record of type 0x80 and instance tag 0x8 is cross linked starting at 0xb68a9 for possibly 0x41 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x8 in file 0x9 is already in use. Deleting corrupt attribute record (128, $SDS) from file record segment 9. 256 file records processed. File verification completed. 0 large file records processed. 0 bad file records processed. 0 EA records processed. 0 reparse records processed. CHKDSK is verifying indexes (stage 2 of 3)... 276 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 3)... The security data stream is missing from file 0x9. The security data stream size 0x0 should not be less than 0x40000. Deleting an index entry with Id 256 from index $SII of file 9. Deleting an index entry with Id 257 from index $SII of file 9. Deleting an index entry with Id 258 from index $SII of file 9. Deleting an index entry with Id 259 from index $SII of file 9. Deleting an index entry with Id 260 from index $SII of file 9. Deleting an index entry with Id 261 from index $SII of file 9. Deleting an index entry with Id 262 from index $SII of file 9. Deleting an index entry with Id 263 from index $SII of file 9. Deleting an index entry with Id 264 from index $SII of file 9. Deleting an index entry with Id 265 from index $SII of file 9. Deleting an index entry with Id 266 from index $SII of file 9. Deleting an index entry with Id 267 from index $SII of file 9. Deleting an index entry with Id 268 from index $SII of file 9. Deleting an index entry with Id 260 from index $SDH of file 9. Deleting an index entry with Id 267 from index $SDH of file 9. Deleting an index entry with Id 262 from index $SDH of file 9. Deleting an index entry with Id 258 from index $SDH of file 9. Deleting an index entry with Id 266 from index $SDH of file 9. Deleting an index entry with Id 256 from index $SDH of file 9. Deleting an index entry with Id 257 from index $SDH of file 9. Deleting an index entry with Id 261 from index $SDH of file 9. Deleting an index entry with Id 263 from index $SDH of file 9. Deleting an index entry with Id 264 from index $SDH of file 9. Deleting an index entry with Id 265 from index $SDH of file 9. Deleting an index entry with Id 259 from index $SDH of file 9. Deleting an index entry with Id 268 from index $SDH of file 9. Replacing invalid security id with default security id for file 0. Replacing invalid security id with default security id for file 1. Replacing invalid security id with default security id for file 2. Replacing invalid security id with default security id for file 6. Replacing invalid security id with default security id for file 8. Replacing invalid security id with default security id for file 9. Replacing invalid security id with default security id for file 11. Replacing invalid security id with default security id for file 24. Replacing invalid security id with default security id for file 25. Replacing invalid security id with default security id for file 26. Replacing invalid security id with default security id for file 27. Replacing invalid security id with default security id for file 29. Replacing invalid security id with default security id for file 30. Replacing invalid security id with default security id for file 31. Replacing invalid security id with default security id for file 32. Replacing invalid security id with default security id for file 33. Replacing invalid security id with default security id for file 34. Replacing invalid security id with default security id for file 35. Replacing invalid security id with default security id for file 36. 256 file SDs/SIDs processed. Security descriptor verification completed. 10 data files processed. The MFT mirror is different from the MFT. Correcting errors in the Master File Table (MFT) mirror. Correcting errors in the Volume Bitmap. Windows has made corrections to the file system. 2861586 MB total disk space. 21588 KB in 6 files. 16 KB in 12 indexes. 0 KB in bad sectors. 155371 KB in use by the system. 65536 KB occupied by the log file. 2861414 MB available on disk. 4096 bytes in each allocation unit. 732566271 total allocation units on disk. 732522028 allocation units available on disk. Internal Info: 00 01 00 00 1d 00 00 00 1c 00 00 00 00 00 00 00 ................ 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ _______________________________________________________________________________________ It is not a life or death situation, I have my personal stuff backed up, but a loss of 2.5Tb still stings somewhat :wacko: Any suggestions for software that (doesn't cost a fortune) that could solve this problem? Or any other possible solution? Or should I just suck it up and reformat the drive Appreciate any input from you guys and girls! Hope you all are having a nice weekend!

And sorry to mods if this is in any way found offensive, I assure you I have only the best intentions. And what is being said in the video is what I am trying to find out, this being the only means I have of translating and thus understanding.

Hey guys! So, a FB friend (unfortunately a Christian fundamentalist) posted a picture that I traced back to this video: https://www.youtube.com/watch?v=6ihbhbhFo7c Could one of you LTT-forum members that speak Arabic tell me what is happening in the video, as I don't understand anything. He seems to have something against Muslims, and I am trying to convince him that we are all equal. But in order to do so I am trying to understand wether or not the picture he posted is a hoax, and since I have the video I tought I'd try asking you guys for help. Thx in advance!

Thank you for taking the time man! Really appreciate it! I'm interested in a card for gaming and not mining, but I assume what you wrote about crashing, overheating etc. still applies if an old mining card would be used for gaming? (even tough the GPU load when gaming usually is not as high as when mining) Have you (or anyone you've heard of) ever tried re-applying thermal paste, pads etc, to see if the artifacts crashes and so on, are realted only to the card runnig too hot? Or is it material fatigue, caused by high temp over long periods of time? Don't know the first thing about mining I'm afraid (sry ), does the ASIC reduction matter for gaming performance too, or does it just apply to mining? thx again

Hi guys! So I haven't been in the market for a graphics card in a while, so if theese questions have already been answered here, let me know (tried searching on the forum). 1. Would the 290x DCii waterblock, fit the a 290 DCii? (At least) EK makes a block, but I haven't been able to sort out if both cards have the same PCB layout etc. Read somewhere that the DCii cooler for 290x DCii, was recycled from the gtx 780, don't know if it's the same for the 290 non-x... 2. Found a good deal on 290 DCii, been used for mining a couple of months, hence the low price (cheaper than second hand 770 2gb)... Now the obvious risk of failure aside, has anyone actually heard of a graphics card dying as a result of mining? Every thread I've read has been the usual "BEWARE" of buying second hand mining cards, but so far I haven't found a single comment of a card actually dying, which made me sort of curious Thx in advance! :lol:

You, as a content creator could give a different perspective on the video quality of the gopro, perhaps a side by side comparison between the gopro and some of the cameras you guys have on hand. This is something I would be interested to see, in terms of color accuracy, sharpness etc.

Any conductive material will do (steel, copper, iron, aluminum...), the "cage" term used, is what throws people off

Was running Thermochill EC6 for about 2 years, clear tubing and clear coolant, no gunk, and nothing to clean out. Unless your loop runs EXTREMELY hot, I can see no reason why you'd need to change the tubing every 6 months, (unless maybye, if you buy the worst quality cheapo-tubing you can find). Aftet the 2 years the Masterkleer tubing I was using was still in cherry condition. Just my 2 cents...

Ah, I see Still at 18W max including fans, I see no issue running pump with above mentioned adapter. At 12V( a relatively speaking "low voltage"), both the length of the wire, and the actual continous power draw decides the appropriate gauge, not the power draw alone. U = R*I (voltage= Resistance*Current) Considering how short the adapter wire is, at ~1.5 amps max, I hardly believe the resistance of the wire to be a security risk, even if the startup current would be greater than 1.5 amps. If the length if the adapter wire were longer, say 3 feet, or the power draw was the same, but at lower voltage, then it would be a different sceanrio.

I assumed the OP would run the pump with a molex connection if it had one? Then that cable would not be needed. And if he's running prefilled, than the gauge of that cable can hardly be "way under gauged" comapred to the copper on the mobo supplying the current to the pump and fan(s) under normal use. IF however OP's running say a Laing D5, the situation would be different, but to my knowledge there has never been any D5 or any other high performance pumps with 3-pin fan connectors, since they'd instantly fry the mobo fan header. // as always, feel free to prove me wrong