Jump to content

jeffw_00

Members
  • Content Count

    905
  • Joined

  • Last visited

Community Reputation

37 Excellent

About jeffw_00

  • Rank
    Topic Cop
  1. Update - when I try to download the driver for her MOBO- they have posted only an updated one with a Rev # slightly -higher- than 7701. Go figure... (so, not taking that route)
  2. Hi - I just spent some time with it - that didn't work. The only thing that did work was removing all traces of audio driver and re-installing the driver for this motherboard from the Asus site. Which shows up as Reaktek 6.0.1.7701 dated 12/22/15. I may be SOL until I next upgrade my system :-(. Apparently, only this old driver has the extra "sound manager" component, which appears to be needed to allow me to access a menu that enables/disables Line-in as mentioned in my O.P. With all the newer drivers, this Sound Manager component was absent, line-in was silent, and did not appear on the mixer menu. It's weird, because my wife has a slightly older ASUS MOBO (B85M-G), and similar configuration. Her drivers shows as 6.0.1.7071 dated 10/22/2013 - and she has the line in on the mixer. Maybe I should try downloading the ASUS-sourced Realtek driver for her MOBO Anyway - many thanks /j
  3. Hi - So over the last few months, I transitioned all my machines from W7 to W10. I've swatted down many issues (and actually been impressed as to how googling has found me on-point answers so quickly). BUT - I have one annoying issue left and it's driving me nuts, and I can't find anything on the web. I have a generic desktop PC running W10 Home, latest update, with an ASUS H110M-A motherboard with integrated audio (Realtek HD Audio). I'm running the latest driver I can find (Realtek 6/3/2016 6.0.1.7841). Problem: I cannot get "Line In" to appear on the Sound Mixer. Every time I want to mute my line-in I have to open up the Sound Manager, select Line in, select Playback Volume, and select Mute. (4 steps :-( ) I have gone to the Sound Control Panel -> Recording -> Line In -> Properties -> Listen and checked "Listen to this device" - which is supposed to fix it, but... no luck. Anyone have any ideas as to how to debug? Many thanks! /j
  4. No battery icon. I ended up making another pass through the advanced power options and after I turned off -everything- related to battery issues when Plugged In (which is an odd concept in itself :-), the problems seem to have gone away - thanks everyone!
  5. Hi - I recently started a thread here about Windows 10 putting my Desktop to sleep because of low battery. I got some useful help from it, but today I notice the thread is gone? What's going on? thanks! /j
  6. Thanks Aryeh - although by "control" I was thinking more of the options they took away from you inside the program, rather than revision control. I don't think even the enterprise version gives you all the "knobs" back :-} best /j
  7. Hi Aryeh - Great paper - (admittedly I've read only sections so far - but have put aside to finish later). However, you highlight the problem I have with Window 10. I have little control over my smartphone. Upgrades are forced on me (thank you Verizon), whenever they feel like it. Privacy is problematical, and I learn to do things Android's way. But I'm cool with that, because I don't use my phone for much. I think Microsoft looked at that model (which Apple got everyone acclimated to for phones), and said - "hey - let's use that too. The more we control, the happier most people are". That may indeed be true, while the minority "roots" their phone and has it their way. However, unlike with my phone, with my desktop PC, I'm a fanatical power user, and I'm accustomed to having it set up and run EXACTLY the way I want it to (thank you Perl scripting). So, for example, all updates happen only the morning after the weekly full backup. Windows 10 wants to take some of this control away from me, and there's no easy way to "root" my PC. So I'm staying with Windows 7, where I'm in charge, until they pry it from my cold dead hands (well, until Microsoft stops supporting it, I'm not a total idiot :-}). Anyway- thanks for the paper, and thanks everyone for listening :-} best /j
  8. It's cool. sorry! It's just that this seems like it may mushroom into a big deal and I don't want to dilute the message. :-}
  9. Thanks raymac46, but let's not hijack the post. Microsoft clearly advertises that "If you don't like Windows 10, you can roll back to your old OS easy-peasy", except that they majorly screwed it up for Windows 7. Most people don't use the Task Scheduler for their own stuff, so they'll never notice that, after the rollback, it's 100% broken. However, certain system tasks will fail to run, and that will cause odd and mysterious problems for people. The fix cited is very straightforward, you have to simply rebuild the tasks portion of the registry from the XML files within the tasks file within Windows. My guess is that Microsoft simply FORGOT to do this in their auto-rollback. Until recently, almost no one did the rollback, because most people upgraded because, well, their intent was to move to Windows 10. However, this month, Microsoft has created an situation where many people will upgrade to lock in their free license, and then immediately rollback, if for no other reason that they just don't want to deal with an upgrade right now. Those people, by and large, are -screwed- right now. Their systems will get flakey, they won't know why, and most likely even if they think it was due to the upgrade/rollback, they won't assume that upgrading again is the right fix (they might fear it will cause more issues). Some will roll back to a backup and punt the free license (making it even harder for Microsoft to get them to upgrade in the future), but lots of IT hours are about to get spent because Microsoft did a sloppy job.
  10. Well, it didn't work for me. :-( See my post (reply #27) here http://forums.scotsnewsletter.com/index.php?showtopic=86637
  11. BUT ----- here is the fix! https://repairtasks.codeplex.com/
  12. Yes - I had a full backup available pre-upgrade, but I tried the "revert" within Win10 to keep my license. (otherwise, what was the point? :-})
  13. So I upgraded to WIN10 to secure my license, and then reverted to Win7. After a day I noticed scheduled tasks weren't working. I open the Task Scheduler and it complains that dozens of system tasks as well as all of mine, are corrupted. This means my OS isn't properly configured (since some of the system tasks are important) I search the web (googling "revert to windows 7 task scheduler") and discover this is a well-known, and difficult-to-fix problem. So now I have 5 PCs to go fix :-{ /j ---------------------------------- Be warned - Microsoft doesn't want you to downgrade. It's a trick :-{ Microsoft clearly advertises that "If you don't like Windows 10, you can roll back to your old OS easy-peasy", except that they majorly screwed it up for Windows 7. Most people don't use the Task Scheduler for their own stuff, so they'll never notice that, after the rollback, it's 100% broken. However, certain system tasks will fail to run, and that will cause odd and mysterious problems for people. The fix cited is very straightforward, you have to simply rebuild the tasks portion of the registry from the XML files within the tasks file within Windows. My guess is that Microsoft simply FORGOT to do this in their auto-rollback. Until recently, almost no one did the rollback, because most people upgraded because, well, their intent was to move to Windows 10. However, this month, Microsoft has created an situation where many people will upgrade to lock in their free license, and then immediately rollback, if for no other reason that they just don't want to deal with an upgrade right now. Those people, by and large, are -screwed- right now. Their systems will get flakey, they won't know why, and most likely even if they think it was due to the upgrade/rollback, they won't assume that upgrading again is the right fix (they might fear it will cause more issues). Some will roll back to a backup and punt the free license (making it even harder for Microsoft to get them to upgrade in the future), but lots of IT hours are about to get spent because Microsoft did a sloppy job. [i don't know why the last work "issues" got chomped off the right end of the topic title - my apologies]
  14. Thanks Aryeh - and you're correct. But I hope to be able to do an upgrade to a more stable version when the time comes. We use our PCs for business, and the "clean install" we were forced to do to Windows 7 (first time since Win95) took an entire day :-{.
  15. Ok - the answer is Windows 10 is NOT for me (at least yet). I've tried upgrading a few machines. In all cases i went back to Windows 7. Reasons include a) stronger "rules". I want updates applied on MY schedule, not theirs (I wait until right AFTER a daily image backup). I DON'T want Windows Defender. If I wanted "their way or the highway" I'd use a Mac :-}. b ) Much slower boot. I don't know what it's doing after I get my desktop, but the time from getting the desktop to having all the startup programs (antivirus, etc) running, is much longer than windows 7. (like a minute). c) less stable O/S. In using it for an hour on different machines, I experienced complete hangs and bad process prioritizing (I had a backup validation which used a lot of memory keep me from doing ANYTHING else, including getting to the CTRL/ALT/DEL menu - it hung up preparing the menu until the validate completed. This app (IFW) shares just fine on Win7). Also, seems like there's a lot of busy background processes slowing stuff down, preventing backups from even starting (they need other processes to stop writing to disk). d) On one machine, running my backup program (IFW) in Win 10, it claimed I had bad sectors on my disk. I tried running chkdsk (annoying to use because you can't see details), and it appeared to hang (!). I reverted to Win 7, and both the chkdsk and backup ran clean. Here's hoping W10 is more stable by 2019. I'm sticking to Win7 until then. I have better things to do with my life than wrestle with the O/S. Win 7 just seems less ambitious and so less troublesome. Just my $.02. I respect that others may disagree. :-} /j PS - my main machine is a 64b i5-2500 @3.3GHz - not an old or slow machine
×
×
  • Create New...