|
|
I have a Dell (bought it last October) and it's been great.
All she does on her laptop is play WoW (I keep trying to get her to move to her desktop for gaming, but she ain't havin' it).
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Now to play WoW I think you can't make a lot wrong, also with a Dell. And by the way I also had Dell's in the past and they where not that bad at all. I only have the feeling if it comes to higher price level, that HP performs something better... but yes, only a feeling.
It does not solve my Problem, but it answers my question
modified 19-Jan-21 21:04pm.
|
|
|
|
|
Playing WoW on a laptop, that explains the going up in smoke.
modified 20-Oct-19 21:02pm.
|
|
|
|
|
It seemed to play okay, but her old laptop was six years old. The new one should play WoW a lot better (quad-core I5, DDR4, GTX1050ti). I don't know what her old machine has.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
I used to play wow on a laptop, but with monitor and mouse and you could fry eggs on that thing. You better buy her a top of the line cooling pad.
modified 20-Oct-19 21:02pm.
|
|
|
|
|
#realJSOP wrote: All she does on her laptop is play WoW
That answers my question, which was going to be, "why aren't you trying to get her on Linux", given that you're a fan yourself.
So the next question is, are you enough of a Linux fan to take it upon yourself to try to get WoW going on Wine for her? This (my first search result) seems to indicate it's supported well enough...
|
|
|
|
|
If it has a medium-high DPI screen (which is common enough these days), W10 by defailt uses blurry scaling that makes things look like you forgot to put on your glasses. This can be fixed to make it look like W8 DPI-scaling again but it takes some special effort.
|
|
|
|
|
|
|
|
On my wife's Dell laptop there is only one thing dell added - it is some update watcher... It didn't bothered her till now so I didn't had to remove it, however W10 pooped up endless promotions and ads (some of them really no fit our way of life and the age of the kids, who also use the laptop occasionally), so I went setting-by-setting, and add some entries to the hosts file to block all that crap... I found the needed with a simple Google search...
"The greatest enemy of knowledge is not ignorance, it is the illusion of knowledge". Stephen Hawking, 1942- 2018
|
|
|
|
|
#realJSOP wrote: I wanna prep it for her. Is there anything I should be aware of or or should know?
I'd leave Dell Command Update on there.
I have Dell Latitude's and they run them in house and for customers where I contract. Dell Command Update doesn't popup and annoy, but run it every couple of months to keep BIOS and drivers up to date.
Michael Martin
Australia
"I controlled my laughter and simple said "No,I am very busy,so I can't write any code for you". The moment they heard this all the smiling face turned into a sad looking face and one of them farted. So I had to leave the place as soon as possible."
- Mr.Prakash One Fine Saturday. 24/04/2004
|
|
|
|
|
I ended up with a new Microsoft Surface Pro6. Very nice as either a laptop or tablet.Some of the Dells aRE REAL NICE WITH THE TOUCH SCREEN, TOO.
CQ de W5ALT
Walt Fair, Jr., P. E.
Comport Computing
Specializing in Technical Engineering Software
|
|
|
|
|
Install a halon fire suppression system? 
|
|
|
|
|
Yes, I'm bringing that one up again.
No matter how many times MS tweaks the "reboot automatically after updates" options, I've still gotten bitten. I left my work VM absolutely loaded with all sorts of items before the weekend, and came back to a mostly empty desktop this morning. Turns out the machine rebooted at around 5:35pm yesterday (a Sunday). I hadn't looked at/logged into it since I had left it on Friday.
I'm seriously considering using a server OS for my next development VM (which I'm going to be putting together when we switch over to VS2019). Primarily because the user still has the final say as to when to reboot the OS for server versions. At least that's the case with Server 2012 R2 (my VM host is still patiently waiting for me to tell it to reboot after installing the April patches). I'm hoping 2016/2019 haven't changed in that respect. It might be overkill, but seems like the simplest solution to me. I'm not gonna mess around with group policies to try to override default behavior. It's gotten so complicated these days even the dedicated policy experts can't make heads or tails of everything that needs to be overridden, and in what order (or so I'm told).
Any caveats I should know about running a server OS for a development box?
|
|
|
|
|
dandy72 wrote: Any caveats I should know about running a server OS for a development box?
I've had behavior differences between the ordinary retail OS and server versions, usually due to default privileges, elevation, UAC, and so on. Since you're using VM's anyway, this shouldn't be a big deal.
Software Zen: delete this;
|
|
|
|
|
I'm not terribly concerned about that. I have plenty of server OSes in various VMs and I'm used to their behavior as far as permissions/privileges/elevation/UAC go. It's using VS on a server OS that's the big unknown for me.
|
|
|
|
|
We use several editions of Visual Studio (2003.NET to 2015) on our build servers, which are running Windows Server 2003, 2008, and 2012. We've had no issues based on it being a server OS.
Yeah, I know we're running old stuff. It takes an act of God here to be able to upgrade a product from one compiler to the next.
Software Zen: delete this;
|
|
|
|
|
One thing you can do with Windows 10 updates is to delay them for max 35 days under advanced options.
I'm doing this with our Gitea GIT server, it shows the date the update will take place and you can do the update manually before that in a timeframe that suits you.
|
|
|
|
|
Here's the thing: I don't always want to pause updates altogether; more often than not, I'll install updates and tell Windows within a short amount of time to go ahead and reboot, so I don't have the option selected.
Some update probably got itself installed (say, Friday or Saturday), it showed the reboot prompt, then by Sunday late afternoon, it figured it waited long enough and, given that updates weren't "paused", went ahead.
If I pick that option, does Windows stay quiet about available updates? If so, that's not a good thing. I want to be told updates are available as soon as they're pushed out; it's the rebooting I want to delay.
|
|
|
|
|
dandy72 wrote: Any caveats I should know about running a server OS for a development box?
Not from the development side, but for Server 2016 good luck.
Got it installed at a load of customers here at work and it's just working and I've looked no deeper than I have to. Installed it for a customer of mine and found that the Active Hours can only be set to 12 hours where as Windows 10 allows for 18 hours. Pretty faarrrkkkked for a Server OS Microsoft thinks it will only be activvely used for 12 hours a day.
Michael Martin
Australia
"I controlled my laughter and simple said "No,I am very busy,so I can't write any code for you". The moment they heard this all the smiling face turned into a sad looking face and one of them farted. So I had to leave the place as soon as possible."
- Mr.Prakash One Fine Saturday. 24/04/2004
|
|
|
|
|
Michael Martin wrote: Active Hours can only be set to 12 hours where as Windows 10 allows for 18 hours
Not sure what that means in the greater context. I have Server 2016 in a few VMs, and after installing updates, they all seem to wait for as long as I tell them (which is what I'm after).
The feedback I'm after has more to do with installing/running/debugging with VS on a server OS than anything else. What I've seen as far as update behavior is concerned for 2016/2019 seems to indicate the user still has a lot more control over the reboot process than any of the client OSes.
|
|
|
|
|
I've been running server 2016 for about a year now and have never had it reboot on it's own. (maybe I've been lucky!) What does annoy me, though not nearly as much as an automatic restart, is that when remoting into it, I get a dialogue that 'Updates are available'. This dialogue has only 1 button for 'View updates' and is modal, meaning that I am unable to do anything else until I actually click the button.
Once again this morning, there is the same defender (KB2267602) update that has been showing up for the last month and a half. It has 'installed' a dozen times but keeps coming back. 
"Go forth into the source" - Neal Morse
|
|
|
|
|
kmoorevs wrote: I've been running server 2016 for about a year now and have never had it reboot on it's own. (maybe I've been lucky!) What does annoy me, though not nearly as much as an automatic restart, is that when remoting into it, I get a dialogue that 'Updates are available'. This dialogue has only 1 button for 'View updates' and is modal, meaning that I am unable to do anything else until I actually click the button.
I've seen that, and I can live with it.
Well, that does it. My next dev VM will be running some version of Windows Server.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
