But lately it feels like I see him all the time and there is something off with the guy. Can’t name what it is. Feels like he’s trying to milk whatever fame he got around the nerd circles as much as possible.
The port of the Windows 95 Start Menu was not all it seemed
11–20 of 56 posts
Re: The port of the Windows 95 Start Menu was not all it seemed
#12The first page is shows you with the "reject all" is only for the page of options you're on to start with - the "legitimate uses" page has a ton of stuff opted-in by default, and to turn those off, you have to click on every company, one by one.
Also, once you've hit "reject all", I can find no way to get that permissions dialog back again.
It's a deliberate UI approach to trick you into accepting a ton of cookies without knowing you've done so.
Re: The port of the Windows 95 Start Menu was not all it seemed
#13Software rotation of test is cool but cpu heavy (at the time) Given the lag the current wx11 start menu animations illicit in slower machines, I'm not surprised they used to value speed over complexity.
I write this from memory so its possible that i misremember :)
Re: The port of the Windows 95 Start Menu was not all it seemed
#14I’ve seen a couple videos of Dave Plummer and they were fun. Gave some insight to internals of Windows etc. I even followed him on YT back then. But lately it feels like I see him all the time and there is something off with the guy. Can’t name what it is. Feels like he’s trying to milk whatever fame he got around the nerd circles as much as possible.
Re: The port of the Windows 95 Start Menu was not all it seemed
#15Orthogonal : I have to say I really dislike the cookie permissions dialog El Reg now use. The first page is shows you with the "reject all" is only for the page of options you're on to start with - the "legitimate uses" page has a ton of stuff opted-in by default, and to turn those off, you have to click on every company, one by one. Also, once you've hit "reject all", I can find no way to get that permissions dialog…
Re: The port of the Windows 95 Start Menu was not all it seemed
#16WinNT task manager is not the same as Win9x. I doubt it was "ported". In Win9x calling the task manager (CTRL-ALT-DEL) instantly stopped all tasks except the Task Manager itself, and the Task Manager was always in memory. Most mis-behaving apps could be closed that way. Only a system that was frozen on I/O would not respond to CTRL-ALT-DEL with the Task Manager, and open a blue screen instead (the "system is busy: pr…
Re: The port of the Windows 95 Start Menu was not all it seemed
#17Re: The port of the Windows 95 Start Menu was not all it seemed
#18Earlier quoted context omitted.
I'd think for a relatively modest use case like the menu title bar, you could rotate the necessary glyphs once and cache them.
then you have to deal with cache invalidation, you need to have triggers in all places that change the look of the menu, for example when you install a new program, change the OS language, etc.
Re: The port of the Windows 95 Start Menu was not all it seemed
#19Otherwise depending on your processes you'll either get what davepl got, or you'll be playing whack-a-mole in code reviews trying to protect your design; neither of those situations is a good use of your time.
Re: The port of the Windows 95 Start Menu was not all it seemed
#20WinNT task manager is not the same as Win9x. I doubt it was "ported". In Win9x calling the task manager (CTRL-ALT-DEL) instantly stopped all tasks except the Task Manager itself, and the Task Manager was always in memory. Most mis-behaving apps could be closed that way. Only a system that was frozen on I/O would not respond to CTRL-ALT-DEL with the Task Manager, and open a blue screen instead (the "system is busy: pr…
Do you see any feasible way of re-fitting a modern OS with similar capability? It would likely require a lot of vertical integration between the kernel, display server, task manager, etc
I belive it is first a conflict of policy: the USER needs to have more privileges than SYSTEM in order to suspend execution of all (including system's) processes. WinNT is a multi-user OS. Nobody would allow the user to DDoS the system, even when that user has direct access to the reset button.
A second problem is that WinNT probably can't even open the Task Manager if some system processes are suspended (csrss?, lsass?).
It probably works in Linux console. Sysvinit has two keyboard signals (CTRL-ALT-DEL and CTRL-UP, I think), that can run any command, exec'd directly by init with root privileges, and both are configurable in inittab. It also has the SysRq.