JJWild

Oh, no. Jim Wild has died. This news is hitting me hard.

Jim was a computer system integrator who I worked with frequently and closely for 25 years, from 1982 until he sold his company, JJWild, Inc., to Perot Systems in 2007. Although I didn’t work for Jim, I visited his computer lab so often that he had an employee badge made up for me, so I could come and go freely, as needed. (Perot, later acquired by DELL, wasn’t so accommodating.) Jim had a quiet way about him as he pulled resources together from multiple technology companies to make things happen. He was one of those people who never seemed to be in a hurry, and yet everything was done promptly. Jim Wild was a rarity in the business, wanting to please everyone he could and, in every instance I can think of, succeeding.

I enjoyed every one of my countless dealings with Jim, and the feeling seemed to be mutual. The last time I saw him was at a social gathering in August, 2019.

Audio Nostalgia

A few of you might remember me playing records on one of these, long ago. A JVC VL-5 turntable.

I bought a VL-5 in 1974. It was my turntable in college and beyond. There it is on my right, with the dust cover raised, in this old photo of my post-college basement dungeon.

I sold the VL-5 circa 1982, when I switched to German turntables with straight, low-mass tonearms, as was the trend. A year later, the Compact Disc was introduced in America, a mere 25 years after the introduction of stereo records.

On a whim, yesterday I searched for a VL-5 on Craig’s List, and there one was, in very good condition at a reasonable price. So, yielding to the impulse, I bought it. Now it’s in my office, 50 years old and working almost as if new.

I still have the small Pioneer amp in that photo, purchased from Brad, who some of you know, of course. The larger amp is a Philips 384. It’s something else from my audio past that I sold and might look for.

Coffee, Darlin’

In early 1988 I was about to close on buying my first house1 and then get married, but I couldn’t take any time off from work. I needed to go on a business trip to install a medical laboratory system at a hospital in Baton Rouge, Louisiana.

The plane’s approach into Baton Rouge was rough because of a snow storm. Yes, snow in Louisiana. The turbulence was strong enough that everybody applauded when we landed safely. That flight was the one and only time I ever needed to use a barf bag.

Driving from the airport to the hospital took me past the palatial estate of the now deceased televangelist con artist Jimmy Swaggart. Saying “con artist” after “televangelist” is, of course, redundant.

https://opplehouse.com/jimmy-swaggarts-home-a-complete-tour-of-the-ministers-private-estate/

The hospital was the field test site for my employer’s new, proprietary computer terminal. It cost significantly less than what customers would have had to pay for a PC in those days. I quickly found a problem that had been missed during development of the device. I called the lead developer to tell him the bad news, and I’ll always remember what he said. “Oh, damn. I forgot to double-buffer the UARTs!”2 Well, it was funny at the time. Guess you had to be there.

I had about a dozen of those terminals on hand to do what I needed to do that week, but they weren’t going to work as delivered. The developer scrambled to edit the firmware he had written for the device, and he pressed one of the other developers into service to burn enough PROMS3 with the updated code for my purposes that week.

That meant waiting for a Federal Express shipment that would bump out my schedule by a day, so I would return home on Saturday, rather than on Friday. I explained the situation to the lab manager, a very competent woman who doubled as a computer system supervisor.

To tell this story I must emphasize that she was very attractive, well-dressed, and not much older than myself. By “well-dressed” I mean “flattering” more than “conservative.” Her manner was totally professional, which made me wonder why her appearance was more about her being a woman than a manager.

Having some extra time on hand, I asked her about the system I was replacing. She said there were lab instruments the other software vendor had never been able to get interfaced. They had to laboriously transcribe results manually from the machines into computer terminals. Their technician from the instrument service company was there now, and could I see if there was something I could do? Sure.

Long story short, I got the instruments working on the competitor’s system to make the lab manager’s life easier until our system went online. She was very appreciative, and said her boss, the hospital’s CFO, wanted to meet with me. Okay.

We went in the CFO’s office. There were two leather chairs in front of his desk, and we sat down. He leaned back, and in a condescending Southern drawl he said, referring to the snow, “Well……….. it looks like y’all brought some of that Yankee weather down ‘heah’ with ya.” I chuckled and replied, “Yeah, sorry about that.”

“I hear y’all have a problem and are waitin’ on sumthin’ from Boston.” I was about to answer when he looked at the lab manager and told her, “Would ya git us some coffee, darlin’?” His tone implied, “Why haven’t you already offered to do this?”

As if a switch had been flicked, she smiled and said “of course.” She immediately stood up and headed for a coffee tray that had been set up in back of the office.

I couldn’t believe the sexist power trip I’d just heard and how she had responded so readily to it. I’d brought more than Boston’s winter weather with me, I’d come with a sense of propriety regarding how to address women. I said I’d get my own coffee and I followed her to the tray on the table in back of the office.

The rest of the meeting was polite and perfunctory. I explained the problem and I thanked him for his understanding and the hospital’s willingness to be the test site for the new product. She explained how I had gotten those lab instruments working on their soon-to-be-replaced system.

The next morning, waiting for the FedEx package so I could swap out the PROMs, I met with the manager in the hospital cafeteria. Nothing at all about her or the CFO gave me the slightest inkling they had any sort of a personal relationship, but I wouldn’t have been surprised if he’d made overtures and been rejected. She simply seemed to be filling her subservient female role as she was expected to do, in both her dress and manner.

I tactfully commented that chief financial officers were usually the ones who made the final decision on computer system purchases. She took the hint and explained in a tone of weary acceptance, “I know how different it must seem to you here, but this isn’t Boston.” We understood each other, and we left it at that.


1 I had negotiated the final purchase price over the phone from a hotel room in Butler, PA, where I was installing a system at the same hospital where Trump was taken after the assassination attempt a year ago.

2 UART – Universal Asynchronous Receiver-Transmitter

3 PROMS – For Programmable Read-Only Memory, not the BBC summer music festival.

Hardcore Hardware

I posted this on the Lyrion Music Server community forum:

https://forums.lyrion.org/forum/user-forums/squeezebox-touch/1775323-squeezebox-hardware-with-verizon-routers

I never determined why my Squeezebox devices started falling off my Verizon G1100 (Quantum Gateway) Wifi network. The workaround was to install IOGEAR GWU637 Ethernet-to-802.11n Wifi adapters.

ethernet dongle

Recently, Verizon sent me a G3100 router. After switching over to that, the Touch and the three Radios worked for a few days, but then they started losing their assigned IP addresses and they couldn’t find the DHCP server to renew their leases. Recycling power on the IOGEAR adapters put them back online, but only temporarily.

Verizon Fios G3100

I switched one of the Radios back to its native 802.11g Wifi and, unlike what happened with the G1100, it worked reliably. So I returned the other two Radios to their own Wifi. The Touch, however, is “unable to find the Wireless hardware.” From other reading I’ve done here, this is apparently caused by updating the Community Firmware while the Touch is on Ethernet.

I figured out what was breaking within DHCP, and the short answer is the G3100 doesn’t like the IOGEAR adapter having the IP address 192.168.1.254. The address is within the router’s DHCP scope, and there’s no way to exclude individual IP addresses from being handed out to clients. So two nodes on the network having the same IP address would be a possibility.

The solution is to take 192.168.1.254, the last IP address in the range, out of the router’s DHCP scope. Alternatively, changing the IOGEAR’s IP address to a localhost loopback, 127.0.0.1, also works. The Touch has stayed online long enough that I’m confident this is the fix. If it isn’t, I’ll have to do a follow-up. I won’t bother speculating on why this isn’t a problem with the G1100.

NOTE: The IP address is on the Touch, but the MAC address that’s needed for LAN communication comes from the adapter. So IOGEAR appears on the G3100’s active device list and the Touch is seen as enabled, but offline.