Jump to content

LordMastodon

Member
  • Posts

    386
  • Joined

  • Last visited

Awards

1 Follower

System

  • CPU
    Core i7-6700HQ
  • Motherboard
    Toshiba L55-C5392 Mobo
  • RAM
    8GB DDR3 (even though I have Skylake)
  • GPU
    Intel HD Graphics 530
  • Case
    Toshiba L55-C5392 Case
  • Storage
    525 GB Crucial MX300 SSD
  • PSU
    Whatever power jack comes with it
  • Display(s)
    Some 1366 x 768 garbage + an OK 1080p monitor
  • Cooling
    Not enough + an external laptop tray
  • Keyboard
    The included keyboard
  • Mouse
    $4 Lenovo 3D Optical Mouse
  • Sound
    The Skullcandy branding right under the power button should clue you in
  • Operating System
    Windows 10 Home
  • PCPartPicker URL

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. That didn't really help. I'm not sure what area of Windows Repair to use, and when I tried Startup Repair it didn't do anything.
  2. I've unhidden the Search bar, but when I click on it, it just doesn't do anything.
  3. Yeah, losing Cortana is not a huge problem. The real problem is losing Search functionality in the Start Menu.
  4. I was fairly certain that Cortana was tied to search and that that was how I was supposed to regain Search functionality. Really what I want is to be able to search from the Start Menu again.
  5. So, I recently was doing some benchmarks, and I decided to end as many background tasks as Windows would let me so that I could get the most accurate results possible. Now, during that process, I somehow managed to end the Cortana service for good (not sure how). At that point, I became unable to use the search bar at all. I've restarted multiple times and tried multiple PowerShell tricks, but no matter what I do it doesn't work. I've tried going to All Apps in the Start Menu and starting the Search app, it doesn't do anything. I've tried poking around "Search & Cortana Settings" in the Settings app, but it won't load. I'm really not sure what to do or how to go about it.
  6. I don't know if it's that bad, but that's probably the troubleshooting step I'd have tried first.
  7. As was previously stated, try a different SATA cable.
  8. Alright, I guess just tape or velcro the Pi to something else. That's probably the easiest way.
  9. I think that while a Raspberry Pi may be spending money wisely, the Unifi CloudKey is spending time wisely. If you've got loads of free time, you may be OK with programming and then bug-fixing and things like that. Otherwise, the CloudKey means you don't have to spend ridiculous amounts of time on it. That's up to you, but if you're hell-bent on a Raspberry Pi, just velcro/double-sided tape it to something else in your rack.
  10. Just go to your local hardware store (I like Home Depot) and grab some double-sided tape. It's not expensive at all. Worst case scenario, order it on Amazon. In all honesty though, check out Linus' PIMP my Wifi EP. 2. He explains all kinds of things, and he demonstrates the Unifi CloudKey, a way better solution to your problem.
  11. It does depend on what features you want. I'd look it up, maybe watch a review, take a look at the specs. It also depends on what case you plan to buy. For instance, the B150M Night Elf is Micro-ATX, so don't buy Mini-ITX cases because it will not fit. You could buy a full ATX case, but if it's got a window it may look odd because the motherboard wouldn't be taking up all the space it needs. Also, if you plan on using Crossfire in the future, don't go with a Mini-ITX motherboard because those only have one PCIe slot. You'll also want to go with Z170 or Q170, because, AFAIK, those are the only ones that support multiple cards. I could be wrong though, that was judging by the article on Puget Systems' website.
  12. Ah, sorry. You're right. I'm not that well-versed in RAM, but I'll keep that in mind in the future. Thanks!
×