|
If you eliminate the glass, you have room for 3 bottles.
|
|
|
|
|
Now that's efficiency!
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
One bottle, two mouths. I hate doing dishes.
|
|
|
|
|
Go away. Don't bother me.
73
|
|
|
|
|
Warning : Upgrade your primary desktop/laptop at your own peril!
Driver support is phenomenally sub-par at the moment.
|
|
|
|
|
Don't.
Mention.
Drivers.
:GrittedTeethSmiley:
I spent a load of time yesterday trying to flash a friends Nexus 7 from Android 5.1 to Android 4.4 so it worked as a computer instead of battery powered doorstop. Finally worked out around 21:00 while watching a movie with Herself that it was the USB ADB drivers. Sure enough, when I checked this morning my good drivers had been silently replaced with MS cr@p. One quick download of the Universal ADB Driver - GitHub - koush/UniversalAdbDriver[^] - later and "fastboot oem unlock" can talk to the bootloader ... 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
I have a Nexus 7 lying around here that was perfect when we bought it. After 2-3 OS updates it's slow and unusable. I did not know you could force downgrade it.
|
|
|
|
|
Yes - it's not difficult - though you lose all your data as the flash needs to be erased.
Have a look here: Installing Android 5.1 directly on your Nexus 7 2012 Wifi[^] - it works exactly the same in reverse to wipe out 5.1 and reinstall an earlier version. I use 4.4 as it's the last "totally stable" Nexus 7 release. Just make sure you have good USB ADB drivers, or the "adb reboot bootloader" works fine, but that's that last communications you get with the tablet, and the unlock command just sits there with "waiting for device"...
Downgrade takes about ten minutes and a USB cable.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
|
You're welcome!
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Drivers do become available - however it is a bit of a gamble.
I bought an HP mini PC[^](which, by the way, I think is a fantastic computer and really good value) to replace my security computer and installed Windows 10.
I rolled back the changes to Windows 7 out of frustration.
7 days later I tried again and everything worked perfectly - I put it down to webcam drivers having been fixed in the meantime or something connected with webcam drivers.
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
|
|
|
|
|
Quote: Go away.
You talking to me, or to Windows 10? 
Get me coffee and no one gets hurt!
|
|
|
|
|
|
If you're going to go to Win10 DO NOT DO THE UPGRADE! Trust me. Bad things can and will happen and you will probably end up with an unstable system.
Instead, backup everything you want to keep and do a wipe and clean install of Win10 from the LATEST image you can get your hands on. The process will go much nicer and use the latest drivers. Then, when it's done, go to the vendor sites for all of your hardware and download and install the OEM's drivers for your hardware and get off Microsoft drivers. Yes, those are supplied by the manufacturer but they are usually a bit behind the latest from the vendor version.
|
|
|
|
|
Dave,
I was told here on CP to do the upgrade first, and follow that up with a clean install, for the following reason:
Quote: It is important to do the upgrade first, then follow up with a clean install. When you upgrade your machine is registered with Microsoft as eligible for Win 10, and you won't need an expensive activation code later - during the clean install. Just skip the parts where a clean install asks for the activation code.
I have done this on a few machines, including one that was totally messed up by the upgrade, and after the upgrade I formatted the systems drive and did a clean install. This worked for me every time. Windows 10 was activated immediately after a clean install.
Also: I believe the 10586 build is the latest Win 10 version. Using this ISO will spare you a later, lengthy upgrade.
Get me coffee and no one gets hurt!
modified 14-Feb-16 12:24pm.
|
|
|
|
|
The one big assumption there is that the machine actually makes it through the upgrade! Mine didn't. The upgrade bricked and I could not get it to restore back to Win7. I had no choice but to wipe the machine and install from DVD.
|
|
|
|
|
Did Win 10 activate after your clean install?
Get me coffee and no one gets hurt!
|
|
|
|
|
Yes, but only because I used the image off of MSDN.
|
|
|
|
|
|
My machine boots UEFI mode, and I had no issues after any of the updates. Go figure! 
Get me coffee and no one gets hurt!
|
|
|
|
|
I am the original poster. I have windows 7. When I said
'go away' to windows 10, I meant the continual annoying
interfering push when updating 7 to switch to 10!
My Linux box is standing by for 2020...
73
|
|
|
|
|
Dude, Windows 7 is over a decade old now. Let go already! There is no point in holding onto antediluvian technology.
|
|
|
|
|
Quote: antediluvian
Wow! A new word for me. I had to look it up, since I only know little words.
Get me coffee and no one gets hurt!
|
|
|
|
|
'antediluvian' as in 'before the flood' is a good adjective!
I installed windows 10 and uninstalled it after about one day.
It has been described as a privacy nightmare but what also annoyed
me was no pop3 mail client, only imap (perhaps there is now)
[^]
[^]
73
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
