![[H]ard|Forum](/styles/hardforum/xenforo/logo_dark.png){kind=logo}
Years and years ago, Microsoft and 3Com created NDIS. https://en.wikipedia.org/wiki/Network_Driver_Interface_Specification
omg, I think I talked to you years ago about buying those corsairs for my dad's p4. Since that time, my mom is gone, my dad is gone, my mom's system's power supply went (I think--haven't diagd it yet), but my dad's system is still alive and running. You still looking to give those modules a good home? Neat to know about all the other variants of led activity meters on ram and how they panned out over the years.
Pretty cool to know the original NDIS 2.0 I was trying to understand while using a packet driver is still around. I still don't know everything about binding and why stuff worked the way it did when I changed it. I don't even really remember what I was doing to be honest--I think trying to run IPX and Lantastic's Netbeui at the same time--and it worked with a packet driver since I could bind two protocols (I think?), but I didn't know why the changes I made worked since I didn't understand one of the config files (protocol.ini or the other one?). This is literally 30yr+ ago, so probably wrong on some of the details.
I think the only thing I know that's stuck around that long is the SCSI command set created by Adaptec which is still used on SAS drives and somewhat in today's SATA.Wow sure brings back memories, right? I put those in a FX60 build in the summer of 2006 to hold me over until Conroe!omg, I think I talked to you years ago about buying those corsairs for my dad's p4. Since that time, my mom is gone, my dad is gone, my mom's system's power supply went (I think--haven't diagd it yet), but my dad's system is still alive and running. You still looking to give those modules a good home? Neat to know about all the other variants of led activity meters on ram and how they panned out over the years.
Wow sure brings back memories, right? I put those in a FX60 build in the summer of 2006 to hold me over until Conroe!
I should dig it out and put 64bit XP on it and post a video on my youtube channel. Those were the Corsairs.
This was a custom system I built circa 2010 for a high maintenance client featuring the Crucial Ballistix Tracer DDR2 modules in blue:
(that is their channel, not mine)
TBH I kind of do miss activity LEDs on RAM especially with all slots filled. As long as they actually fire depending on activity and not just some programmed sequence like an amusement park ride!
Call it nostalgia back from sitting next to VAXs full of cards with activity lights.
I'm surprised they haven't integrated a nostalgia mode for old nerds in such that disk activity fires a piezo speaker simulating seek activity of spinning rust! I know someone has made a kit that you can install to do just this and I have experimented with a few tricks but newer versions of Windows have i/o patterns that are considerably different from the NT days.
The materials may be, but I'm sure there still is some engineering time that went into it.
Actually, SASI was invented by some engineers at Shugart Associates Shugart Associates Standard Interface. But Shugart's management did not want the company to go into the business of adapter boards, so a few months after a meeting where this idea was presented, those engineers founded Adaptec. Later on, the name was changed to remove the reference to one company. I was at that meeting.Pretty cool to know the original NDIS 2.0 I was trying to understand while using a packet driver is still around. I still don't know everything about binding and why stuff worked the way it did when I changed it. I don't even really remember what I was doing to be honest--I think trying to run IPX and Lantastic's Netbeui at the same time--and it worked with a packet driver since I could bind two protocols (I think?), but I didn't know why the changes I made worked since I didn't understand one of the config files (protocol.ini or the other one?). This is literally 30yr+ ago, so probably wrong on some of the details.
But this is a solid example of a standard being picked up and carried on the shoulders of giants for a long time.I think the only thing I know that's stuck around that long is the SCSI command set created by Adaptec which is still used on SAS drives and somewhat in today's SATA.
Yes if the system halts the LEDs were in a frozen pattern. Sometimes one or more would be dim or appear to be driven at a frequency low enough to have perceivable flicker.Nice! It actually almost makes sense to have leds on ram as a diagnostic. Imagine running memtest and physically seeing exactly where it gets stuck. Oh, if they made a seek sound for today's Windows that hammers the drive continuously it would end up sounding like a bad drive from the old days.
Totally badass!! I stand corrected my friend.
I do remember some reference in the old SCSI to Seagate like Seagate Computer Systems Interface changed to Small Computer Systems Interface, but didn't remember all the details and even what I typed isn't what I remembered from the past either. Adaptec was one of my favorite companies of the 'heyday'. It almost boggles my mine that LSI is the king now since they barely had a presence on lower end stuff back then.Yeah that video was really neat in that you could recognize the patterns being run by watching the physical patterns on the leds--pretty sweet.Yes if the system halts the LEDs were in a frozen pattern. Sometimes one or more would be dim or appear to be driven at a frequency low enough to have perceivable flicker.
And the seeking noise, I remember the first Cheetah X15s. Sitting next to a rack of a few dozen of those between the off zero beat throbbing of spindle motor hum and the waves of crunching noise coming and going you really need something to block it out after a while! Sitting at a workstation at home with "just" four X15LPs it was far gentler much like spending a day at the range shooting an MP5 all day (who can afford that now?!) and coming home to plink at beer cans with a bb gun!