View Single Post
  #2  
Old February 3rd 19, 02:50 PM posted to alt.windows7.general
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default Convert laptop to Windows 7

Art Todesco wrote:
I have a Dell Latitude 7350 touch screen laptop with Windows 10. I
really hate Windows 10. Can it be converted to Windows 7? Will I be
able to get the touch screen working? I've tried to make it look like
Windows 7, but there are many things that just don't work well. Am I
nuts to do something like this? I appreciate any comments.


If you right-click Start, there is a "Device Manager".
Otherwise known as "devmgmt.msc".

A touchscreen, I would hope there'd be at least an
"unknown device" if it hasn't been discovered yet.

When you first install Windows 10, it takes a while for
the drivers to get downloaded and installed. One thing I
find annoying, is my chipset drivers take their sweet sweet
time showing up.

The video driver is reasonably aggressively pursued. You
usually see a "Notification" that the system is "searching
for a video driver". It's less ambitious and won't say
something like "searching for touchscreen driver". Any of the
Mickey Mouse stuff might not have a notation.

You can check the manufacturer site for a touchscreen driver.

*******

The OS is likely to have tablet and desktop modes.

https://www.tenforums.com/tutorials/...dows-10-a.html

I did an experiment once with that (on a system not intended
for switching!) and it was not a pretty sight. I would think
you'd want some proof the touchscreen was running before going further.

https://www.tenforums.com/tutorials/...dows-10-a.html

Windows 7 would likely only have a desktop mode.

You could get slightly more of a Windows 7 look, with a menu replacement
software. Maybe Start10 is still under development by its owner.

https://www.infoworld.com/article/29...sic-shell.html

https://en.wikipedia.org/wiki/Classic_Shell

"Development by Ivo Beltchev has ceased, and the projects
source code has been released. A team has picked up development
on GitHub, where the project can now be found."

I think part of the reason the original developer dropped Classic Shell,
is it's pretty expensive for any developer to track changes
in Windows 10. I know there was one furious burst of activity
on VirtualBox, due to Microsoft fooling around with some
kernel or similar files. And Microsoft broke my webcam under
Win10, which I won't forgive them for. Only my ****ty $10
640x480 webcam still works (it has no microphone). Microsoft
added "frameserve" to the webcam hardware stack, but busted
some stuff for fun. To keep an impressive project like
Classic Shell running, when Microsoft is removing legacy support,
would be a daunting task.

The hardware/software ecosystem today is pretty fractured.
Old equipment pushed towards the bin, by less than reasonable
web browser design. Microsoft not supporting Windows Update on
Win7, when it detects the presence of a newer processor.
You don't have quite the same amount of freedom to experiment
as you once did. Intel doesn't write drivers for Windows 7 any
more as far as I know (even though officially Windows 7 is
still in Extended Support). Microsoft hasn't put as much
work as they should have, into making AMD processors work well.
It means end-users are kinda stuck. "In a W10 cross-hairs".

Paul
Ads