Skip navigation
All People > ScottOrzechowski > The Red Eye

The Red Eye

11 posts

Windows stuff

Posted by ScottOrzechowski Employee Jul 28, 2016

HaHA, I'm back!  I was just sending the support team some info on performance troubleshooting and third-party tools we commonly use.  Here's some of it.


Technet's Sysinternals was created by Mark Russinovich and Bryce Cogswell of Microsoft.  The site includes:



I happen to use Process Monitor and Process Explorer most often, but there are plenty of other handy tools.  The webcasts include real world use cases. 


Also check out the Technet Ask The Performance Team blog for more on Windows performance, and here are some technical Windows links I have pulled at random from my bookmarks.

Windows sockets error codes, values, and meanings

How Active Directory Searches Work: Active Directory

How can I get Outlook to restore previously-open message windows when restarting? - Super User

Memory Limits for Windows and Windows Server Releases (Windows)

Registry Redirector (Windows)

System Error Codes (0-499) (Windows)

Advanced Query Syntax (Windows)



...and here's a picture of a double angler.



and you thought I had left the company!      It was only writer's block.


I just ran across this post.  I had been looking for this functionality.  Maybe you have too:



Downloading Docs as PDFs

Kiran DiwakarContributor

Hello Team,

Just wanted to call out this update. You all have been telling us that while the new docs wiki is great, there is no easy way to download docs, both as individual files or all of them at a single go.

We have now made changes and the docs workflows will suit your needs better..


The Download PDFs (all zipped and individual PDFs) option has been enabled in the Download PDF by Sections page.

  We’ve also updated the Features and Enhancements section and embedded the YouTube feature videos


Special shout out to our docs team who followed up diligently on all our feedback and got this done!



Kiran Diwakar

Shunt the deuterium from the main cryo-pump to the auxiliary tank!

Maybe you already use this, but I just realized you can merge packet captures that occurred simultaneously into one view in Wireshark.  This is useful when troubleshooting connectivity, security or firewall issues, when you want to see whether some packets didn't arrive at their destination, or you want to see a TCP stream in the context of communication with other machines (like proxies, other servers, etc.).  Load one pcap, and go to File -> Merge.  Choose the pcap from the other machine.  Wireshark will highlight packets based on which file they came from.


There is so much information coming at us - especially in the IT industry - that it can easily make you seize up and let your limbic system take over.  The first order of business is evaluate your mission - what are you charged with?  Next is to filter out everything that is impertinent.  That still leaves a mountain of data and not enough time to go through it.


I've started reading The Organized Mind, by Daniel J. Levitin.  He presents evidence that humans are ill-equipped for multi-tasking.  Think, for example, of when you're driving somewhere and looking for street signs,  You turn down the radio, because it is competing for your attention, making it more likely that you will miss the sign.  He suggests triaging information into what needs to get addressed right away, what needs to get addressed soon, and what ideally needs to get addressed some time in the future.  Another tactic is to externalize information - make use of resources available so that the information can be retrieved if and when needed.  You can store reminders on your phone, for example, or ask your spouse to remind you.  The goal is to move as much of the mountain of information out of sight and out of mind, and focus on the one thing that really needs your attention now.  When you have addressed that, you can go on to the next priority - refilling your coffee cup.

"network management.  You know when you log into your computer at work, and it has to authenticate with another server, but you can't get there because the switch is down - a switch is a thing that sends packets to - a packet is a..."


"computer stuff.  I do computer stuff."


Please hear me out, because you are going to see two words that could turn you off from reading the rest of this post.

Regardless of how long you have been using Spectrum, do yourself a favor and read through the Getting Started section of the Spectrum docs.  I think we would scare fewer people away if we called it something less patronizing, but all I can think of is Spectrum Guts, and that is not really an improvement.


We used to put this stuff in a couple standalone guides, like the concepts guide and the knowledge base guide.  It was the first stuff I read when I started.  It lays out the fundamentals of Spectrum – database architecture, client-server communication, and most importantly, modeling technology and intelligence.  What more elegant prose is there than:


“The CA Spectrum design is based on the client/server model. Its primary server, the SpectroSERVER, is responsible for collecting, storing, and processing data. The SpectroSERVER uses Inductive Modeling Technology (IMT) to perform these functions.  IMT combines an object-oriented database and the intelligence of inference handlers. The object-oriented database contains model types…” 



I’m going to stop there, because I’m starting to sweat.

Seriously, I did find it very interesting when I first read it.  In any case, if you make it through the whole Getting Started section – all the way through “Relation Descriptions,” Spectrum will fall into place for you conceptually and probably make your life easier.

Spectrum never crashes!


Core dumped

Fallen over


Seg faulted


Up and died

Given up the ghost

Gone belly up

Checked out


Bought it

Bought the farm

Bitten the dust

Popped off



The Red Eye


This is a self-serving, self-indulgent blog.  I plan to post brain detritus as a distraction from reality.  I am guessing that it might serendipitously allow others to take a break from the battering context switching required of a network manager.  Either way, it makes me look like I’m working, and it pumps up my ego.  Sometimes you might find something useful here.  I will try (but not today).


My computer science expertise started and stopped in the mid eighties.  I used my dad’s Commodore  64 (the 64 refers to 64 K of RAM) for four things:

  • Printing to the dot matrix printer.  It actually made tiny burn marks on the paper.  That’s pretty close to playing with fire, and that was cool.
  • Playing One on One with Larry Bird and Dr. J.   If you drove a layup just right, you could shatter the fiberglass backboard. 
  • Writing programs involving number guessing and flashing colors
  • Playing Zork - a text-only role-playing game

It had a modem, which made it capable of hacking into the Pentagon to initiate bilateral thermos-nuclear annihilation of the United States and USSR.


When I was thirteen, I became a Spectrum Product Support Engineer.  Maybe I was twenty-eight.

Armed with my degree in Environmental Science, I moved across New Hampshire, from area code 603 to area code 603, and joined my brother and sister-in-law at Cabletron.  The Spectrum Orzechowski dynasty began.  My brother was doing PR for Craig Benson, who later became governor and installed EZ-Pass on New Hampshire highways.  My sister-in-law was team leader of the Spectrum product support Management Modules team.  Nepotism.

But eighteen years later, how many Orzechowski’s are left working with Spectrum?  Uno.  Credentials be da*ned, I have staying power.


Anyway, the whole frivolous point is to explain the name of the blog.  The latest release when I started was Spectrum 4.0 rev3.  If you started the SpectroSERVER 4.0 rev3 from a control panel on IRIX, my sister-in-law’s voice would tell you, “Your SpectroSERVER is ready."  When you launched the SpectroGRAPH (there was no OneClick), the VNM icon stared at you with a menacing eyeball like the one on the dollar bill – Rob Kettles uses it for his communities avatar. Thus the name of the blog.


To come: colloquial crash terminology