View Single Post
  #31  
Old 09-24-2017, 15:35
TechLord TechLord is offline
Banned User
 
Join Date: Mar 2005
Location: 10 Steps Ahead of You
Posts: 759
Rept. Given: 384
Rept. Rcvd 247 Times in 112 Posts
Thanks Given: 789
Thanks Rcvd at 2,022 Times in 571 Posts
TechLord Reputation: 200-299 TechLord Reputation: 200-299 TechLord Reputation: 200-299
Quote:
Originally Posted by sendersu View Post
then your way is to 16 (8!?) bit SW
it much more coolier taking into account your great posts
You do remember that in the good old days, many of us have had to use Windows 98 (rather than Win XP ) when we needed to use the SOFTICE debugger, as SOFTICE was quite unstable on Windows 2000 and Win XP (until they finally released a patch after more than an year at that time).

Also, for the jump from 16-bit to 32-bit, mostly the issues addressed were related to STABILITY, in teh various releases of Windows, rather than mainly focussing on SECURITY.

Whereas in the transition from 32-bit to 64-bit versions of Windows, mainly for Windows 10 releases, the focus is now more on SECURITY rather than on stability, as the stability (BSODs etc) were not the main issue from XP onwards on properly configuerd systems.

That is why, in my practical experience, driver debugging is a nightmare on the 64-bit versions of Windows 10 due to its numerous security features, compared to its 32-bit counterpart.

Cheers
Reply With Quote
The Following 2 Users Say Thank You to TechLord For This Useful Post:
memo-5 (09-29-2017), niculaita (09-25-2017)