Soon after installing Windows-10 Pro 64bit on my Aurora, I noticed that my LaserJet Pro 400 Color (m451dn) was printing in what appeared to be 150dpi for most print-jobs. I thought it might be a setting on the bundled HP driver, and dismissed it. Then I noticed that even some things (those not using printer fonts as it turned out) printed from my other Win-7 machine … also now looked poor. As I started trouble-shooting, I got worried when printing the full-color picture Demo page from the printer’s front control-panel … it also appeared to be in 150dpi (you could easily see the individual dots). Also, the printer’s built-in Print Quality Diagnostic page was also printing poorly. The problem was inside the printer itself ... it had nothing to do with computers or network.
I found no setting in the printer itself (by its Control Panel or Print-Server login menu) that controlled resolution, DPI, ImageRET3600, or draft mode … especially not for built-in functions.
The fixed turned out to be relatively simple. - Print the Config Report (for current settings) - From the printer’s front Panel menu, press OK (arrow to) Service / Restore Defaults This apparently resets some hidden setting and fixes the printer’s output at a core level - The built-in Diags Print and Demo Page now printed fine. - In my case, I simply set the printer’s Fixed-IPv4 back as before. This has always been the only non-default setting ever made. This printer is connected to LAN by Ethernet cable. - It should also be noted that this “Restore Defaults” does not reset any toner page-counts (it has 4 toner cartridges) or other similar stored counts.
I thought I would put this here because it was evidentially caused my Win10 install (just too much of a coincidence). This printer has been rock-solid and never a problem, since purchased new 4-2012. Also, (by design) Win-10’s basic Printer Test page no longer uses built-in Printer Fonts. Anyway, I thought maybe a Dell user with this color laser printer (or similar) or maybe a Google search user … might find this info helpful in the future.
I just updated my R2 laptop and had some minor issues. I'll post on a separate thread.
I am thinking about updating my R1 W7 sp1 to Creators but I can't seem to figure out what significant benefits there would be. The W7 R1 runs great and would hate to introduce a bunch of challenges.
What benefits did you gain by updating the W7? Do the CC lights work and if I went back to W7 would that cause any MIO/MB issues? Didn't you install W8 on your R1 earlier and replace the 5870 with a 1080 before installing W10?
I have a complete clone of R1. If I went back to W7 the Clone route would it send MS any "whats-going-on" with our OS and block updates, etc..?
I just updated my R2 laptop and had some minor issues. I'll post on a separate thread.
I am thinking about updating my R1 W7 sp1 to Creators but I can't seem to figure out what significant benefits there would be. The W7 R1 runs great and would hate to introduce a bunch of challenges.
1. What benefits did you gain by updating the W7?
2a. Do the CC lights work
2b. and if I went back to W7 would that cause any MIO/MB issues?
3. Didn't you install W8 on your R1 earlier and replace the 5870 with a 1080 before installing W10?
4. I have a complete clone of R1.
5. If I went back to W7 the Clone route would it send MS any "whats-going-on" with our OS and block updates, etc..?
1.
The general stuff. I guess the difference between your Aurora-R1 and your laptop.
I can now get to the Store and run Metro Apps (oh boy ). More secure. DirectX-12 gaming now possible. To get latest OS on my main work machine (not being two Windows versions behind).
I already skipped Win-8 on this machine, but had Win-8 on some laptops, so felt like I was falling behind.
Seems new and current (not old).
I did it before Summer-2016 free-upgrade cut-off. Needed to know if it would work or should start thinking of new machine. AMD-5870 was another hurdle or question but it worked (I got the impression of barely). It all worked fine on Aurora-R1 in the end.
All 8 of my Win-Tel machines are on Windows-10/64bit now.
2a. Yes . AW-CC is fully functional
2b. No, it shouldn't
3.
2013-04 Samsung 830 256gb SSD
2016-07 Windows-7 64bit Pro -to- Windows-10 64bit Pro
2017-01 AMD-5780 upgraded to GTX-1070. 6 year-old AMD-5870 still worked fine for everything (even 95% of games) but not Fallout-4 beyond medium/low settings.
With GTX-1070, I now run Fallout-4 with Ultra-Max settings (and steady 60 FPS or better at 1200p) even in heavy action and complicated scenes
4. Good. You can always revert back
5. Once you go forward (and it activates) ... you can run either version on your machine legit. At least I did for a while. Actually, I cloned my Win-7 to a dual boot and did a test in-place/overlay Win-10 upgrade (with testing) before I did it for real. Only programs I found to be truly incompatible were QuickSFV-64 v2.36, Samsung Magician v3.2, and Acronis-2010.
Looking back at notes ... had a bit of trouble getting drivers for Alienware 19-in-1 Card Reader to load and work, but they finally did. According to my notes, I had to disconnect it, start Win-10 without it, shut-down and reconnect it, and then proper drivers loaded (from Windows Update). General USB-flash drive "Mass Storage" Drivers also went weird for a while during all that. I think it had something to do with it being an upgrade instead of a clean-install. I think I had to delete those "Portable Devices" from Device Manager and let them re-PnP. Eventually, it all cleared up.
Alienware Bluetooth module never recovered but that is covered above. Now, I think that's the highlights or anything truly important from my notes.
9-26-2016 Upgraded to Windows 10, version 1607 (Anniversary Update ). Took about an hour on its SSD C: - Seems to be working fine. - However, Notifications say that iCloud and ClassicShell were removed because they don't work with this version of Windows.
ClassicShell was updated to v4.3.0 .
iCloud for Windows was updated and tested as working.
===============================================
7-28-2017 Windows is finally prompting me to install Creators Update v1703 on this machine.
Snoozed at first and ran my monthly full-system Macrium Reflect backup Image a little early (just in case).
Currently installed: Windows-10 Pro (64 bit) v1607 Classic-Shell v4.3.0. I checked and it's still the latest version. Exported current Classic-Shell config to XML.
Started Install/Update from Update & Security. At Privacy Screen, I'm feeling brave, so left them all on/defaults except I took Diagnostic Level Send down to Basic. At "Use Cortana Screen" clicked "not now". Signed-in with my usual (Local) account. After Windows finished upgrading and desktop appeared, there is a prompt that Classic Shell "needs to reconfig for new OS". I let it and it said Successful.
Observations: Everything seems to be working so far Alienware Command Center v2.8.11.0, AlienFX, and Thermal Control are loaded and working. Device Manager is clean and "Devices and Printers" looks normal
No alarming Notification messages. Classic Shell seems to be working fine. iCloud for Windows seems to be working. Google Chrome is still my default browser and still has its usual 18 of 21 defaults. As usual, Reliability Monitor Report gets reset. The one new entry will show all the migrated drivers.
Tesla1856
8 Wizard
•
17.1K Posts
1
May 10th, 2016 23:00
Soon after installing Windows-10 Pro 64bit on my Aurora, I noticed that my LaserJet Pro 400 Color (m451dn) was printing in what appeared to be 150dpi for most print-jobs. I thought it might be a setting on the bundled HP driver, and dismissed it. Then I noticed that even some things (those not using printer fonts as it turned out) printed from my other Win-7 machine … also now looked poor. As I started trouble-shooting, I got worried when printing the full-color picture Demo page from the printer’s front control-panel … it also appeared to be in 150dpi (you could easily see the individual dots). Also, the printer’s built-in Print Quality Diagnostic page was also printing poorly. The problem was inside the printer itself ... it had nothing to do with computers or network.
I found no setting in the printer itself (by its Control Panel or Print-Server login menu) that controlled resolution, DPI, ImageRET3600, or draft mode … especially not for built-in functions.
The fixed turned out to be relatively simple.
- Print the Config Report (for current settings)
- From the printer’s front Panel menu, press OK (arrow to) Service / Restore Defaults
This apparently resets some hidden setting and fixes the printer’s output at a core level
- The built-in Diags Print and Demo Page now printed fine.
- In my case, I simply set the printer’s Fixed-IPv4 back as before. This has always been the only non-default setting ever made. This printer is connected to LAN by Ethernet cable.
- It should also be noted that this “Restore Defaults” does not reset any toner page-counts (it has 4 toner cartridges) or other similar stored counts.
I thought I would put this here because it was evidentially caused my Win10 install (just too much of a coincidence). This printer has been rock-solid and never a problem, since purchased new 4-2012. Also, (by design) Win-10’s basic Printer Test page no longer uses built-in Printer Fonts. Anyway, I thought maybe a Dell user with this color laser printer (or similar) or maybe a Google search user … might find this info helpful in the future.
AAA737flyer
2 Intern
•
757 Posts
0
April 20th, 2017 15:00
I just updated my R2 laptop and had some minor issues. I'll post on a separate thread.
I am thinking about updating my R1 W7 sp1 to Creators but I can't seem to figure out what significant benefits there would be. The W7 R1 runs great and would hate to introduce a bunch of challenges.
What benefits did you gain by updating the W7? Do the CC lights work and if I went back to W7 would that cause any MIO/MB issues? Didn't you install W8 on your R1 earlier and replace the 5870 with a 1080 before installing W10?
I have a complete clone of R1. If I went back to W7 the Clone route would it send MS any "whats-going-on" with our OS and block updates, etc..?
Tesla1856
8 Wizard
•
17.1K Posts
0
April 20th, 2017 18:00
1.
The general stuff. I guess the difference between your Aurora-R1 and your laptop.
I can now get to the Store and run Metro Apps (oh boy
). More secure. DirectX-12 gaming now possible.
To get latest OS on my main work machine (not being two Windows versions behind).
I already skipped Win-8 on this machine, but had Win-8 on some laptops, so felt like I was falling behind.
Seems new and current (not old).
I did it before Summer-2016 free-upgrade cut-off. Needed to know if it would work or should start thinking of new machine. AMD-5870 was another hurdle or question but it worked (I got the impression of barely). It all worked fine on Aurora-R1 in the end.
All 8 of my Win-Tel machines are on Windows-10/64bit now.
2a. Yes . AW-CC is fully functional
2b. No, it shouldn't
3.
2013-04 Samsung 830 256gb SSD
2016-07 Windows-7 64bit Pro -to- Windows-10 64bit Pro
2017-01 AMD-5780 upgraded to GTX-1070.
6 year-old AMD-5870 still worked fine for everything (even 95% of games) but not Fallout-4 beyond medium/low settings.
With GTX-1070, I now run Fallout-4 with Ultra-Max settings (and steady 60 FPS or better at 1200p) even in heavy action and complicated scenes
4. Good. You can always revert back
5. Once you go forward (and it activates) ... you can run either version on your machine legit. At least I did for a while. Actually, I cloned my Win-7 to a dual boot and did a test in-place/overlay Win-10 upgrade (with testing) before I did it for real. Only programs I found to be truly incompatible were QuickSFV-64 v2.36, Samsung Magician v3.2, and Acronis-2010.
Looking back at notes ... had a bit of trouble getting drivers for Alienware 19-in-1 Card Reader to load and work, but they finally did. According to my notes, I had to disconnect it, start Win-10 without it, shut-down and reconnect it, and then proper drivers loaded (from Windows Update). General USB-flash drive "Mass Storage" Drivers also went weird for a while during all that. I think it had something to do with it being an upgrade instead of a clean-install. I think I had to delete those "Portable Devices" from Device Manager and let them re-PnP. Eventually, it all cleared up.
Alienware Bluetooth module never recovered but that is covered above. Now, I think that's the highlights or anything truly important from my notes.
Tesla1856
8 Wizard
•
17.1K Posts
1
July 28th, 2017 23:00
9-26-2016
Upgraded to Windows 10, version 1607 (Anniversary Update ). Took about an hour on its SSD C:
- Seems to be working fine.
- However, Notifications say that iCloud and ClassicShell were removed because they don't work with this version of Windows.
ClassicShell was updated to v4.3.0 .
iCloud for Windows was updated and tested as working.
===============================================
7-28-2017
Windows is finally prompting me to install Creators Update v1703 on this machine.
Snoozed at first and ran my monthly full-system Macrium Reflect backup Image a little early (just in case).
Currently installed:
Windows-10 Pro (64 bit) v1607
Classic-Shell v4.3.0. I checked and it's still the latest version. Exported current Classic-Shell config to XML.
Started Install/Update from Update & Security. At Privacy Screen, I'm feeling brave, so left them all on/defaults except I took Diagnostic Level Send down to Basic. At "Use Cortana Screen" clicked "not now". Signed-in with my usual (Local) account.
After Windows finished upgrading and desktop appeared, there is a prompt that Classic Shell "needs to reconfig for new OS". I let it and it said Successful.
Observations:
Everything seems to be working so far
Alienware Command Center v2.8.11.0, AlienFX, and Thermal Control are loaded and working.
Device Manager is clean and "Devices and Printers" looks normal
No alarming Notification messages.
Classic Shell seems to be working fine.
iCloud for Windows seems to be working.
Google Chrome is still my default browser and still has its usual 18 of 21 defaults.
As usual, Reliability Monitor Report gets reset. The one new entry will show all the migrated drivers.