Re: Windows 3.1
Back in the mid nineties I had a whole lab of 64+ PCs booting entirely from the LAN and using my PCs three channel SCSI RAID adapter as the source. Oh the joys of working for a NIC vendor (sadly long gone).
23 posts • joined 16 Sep 2009
In the early 90s early token release was invented so there could be multiple data packets going round the ring at once. By the mid 90s token ring switches existed and did go to 100Mb/s, before then there was FDDI for 100Mb/s and of course ATM at 155 in the early 90s.
So, you've never had a remote that wasn't ergonomically perfect, never had a saucepan where water got under the handle on the lid when you washed it, like the silly dock on OSX that gets over full once you have more than a few applications etc.
Win 8 was better than 7 and now 8.1 has a few good tweaks.
Totally agree, been using 8 since the launch on non touch multi screen PCs and the only things that annoyed me were:
No start button, the bit to get to it at the corner of the screen was too small - FIXED
Apps took up the whole screen even if it was a 27" monitor - FIXED
Only one app visible at a time (you can have as many as you like running and use win+tab to switch) - FIXED
I'm very happy now!
12Mb Token Ring, er 16Mb I think! Also Early Token Release fixed the lost token issue but really it was all down to cost once the PC CPU had enough spare cycles to do in software what the TR NIC did in hardware. Funny there was no mention of ATM, that was a great technology with LAN/WAN QoS/COS all built in at layer 2 and the chips were much more like an Ethernet chip in production costs. Also there was no mention of Madge networks a British company who at one time were nearly as big as 3Com and had over 80% of the Token Ring market. They also pioneered switched TR and 100Mb TR in the early 1990s. Finally Type 1 is alive and well in some of our older buildings running 100Mb FDX Ethernet and the rats can't chew through it ;-)
They can't even make the errors user friendly!
Server Error in '/' Application.
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.
Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".
<!-- Web.Config Configuration File -->
Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.
<!-- Web.Config Configuration File -->
<customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
In Exchange 2010 maybe some are there but even then the WAN clustering is not active/active and depends on the OS that you are using. Oh and we cannot use 2010 because some of the estate is on 2003 (meanwhile in Domino land 5, 6, 6.5, 7, 8, 8.5 all coexist perfectly.
Notes 8.5 F5 is refresh, html rendering is as good as IE7, nowhere near Firefox/Chrome but that's another rant!
8.5 can be slower than Outlook (ie is uses more memory) but if you have thousands of mails in your inbox (not in folders) then Outlook is slower that Notes - maost of our users do!
I think the licensing issue for MS users should now largely have disappeared due to the increased performance per physical host now available.
WIth a dual socket 54xx or 55xx Intel server it is now more cost effective to buy Windows Datacenter licences than Standard or Enterprise. This licence allows unlimited virtual instances and has made a huge difference for us at least.
Biting the hand that feeds IT © 1998–2020