Today I received a new batch of Wombat boards from my manufacturing partner. Too bad none of them work! Connected devices aren’t recognized, in either ADB or USB input modes. Oops.

After some lengthy investigation, I discovered that the main crystal oscillator speed on these new boards is about 3.69 MHz, but it should be 8.0 MHz. At 3.69 MHz the board will not work. But the oscillator seems to be an 8 MHz one (at least it has “8.0” in the part number stamped on it), and the associated capacitors and resistors measure roughly the same in-circuit values as a known-good board, so it’s unclear why I’m getting 3.69 MHz oscillation.

Problems happen, but this particular problem should have been caught by the testing procedure that I designed, before the boards were ever shipped to me. I re-ran the test procedure here, using a copy of the test harness that I previously gave to the manufacturer, and sure enough all five of the boards I tried failed the test. So either there’s some discrepancy between how I’m testing and how they’re testing, or they did the tests incorrectly, or didn’t run the tests at all.

The hardware and the test process are identical to the previous three Wombat batches made by the same manufacturer, but the person overseeing the project changed this time.

This is my nightmare scenario, and I’m not sure where to go from here. With some more bench time, I could probably determine exactly why the oscillation speed is 3.69 MHz. Perhaps these boards could be fixed with some hot air rework and component replacement, but who’s going to do that? I’m not about to desolder and replace crystal oscillators on hundreds of boards by hand, to fix someone else’s mistake. Returning the whole batch for rework in China would be prohibitively expensive in shipping and tariff costs. Even if the manufacturer agrees to stump for a complete re-do of the manufacturing, I’ll still be out roughly $750 for the cost of ICs I purchased and provided to them.

Read 17 comments and join the conversation 

I’ve been struggling with unexplained Windows 10 crashes ever since I got a new computer in May. See part 1 and part 2 for the backstory. The symptoms were mysterious crashes and reboots that happened every day or two when I was not using the computer. From examining crash dumps and event logs, I found that most of the problems seemed related to the graphics display or window manager. I suspected that something about the computer’s handling of my external monitor was buggy – either in the Windows driver, the computer’s firmware, or the computer hardware itself.

I’m now more confident than ever that the external monitor is somehow causing the problem. On July 5, I swapped in a different external monitor and made a few other graphics changes, and since then I’ve gone 11 days with zero crashes or unexplained reboots. Unfortunately this new-and-stable config is not the config I actually want, so I still need to do more testing, but I think I’m getting close to a solution.

The computer is an HP EliteBook x360 1030 G2 laptop. It has a built-in 1920 x 1080 display. A second external monitor is connected by HDMI cable.

The crashes-every-day configuration was an ASUS PB258Q 2560 x 1440 monitor, connected with a no-name HDMI cable, and running at its native resolution. The Windows 10 Display control panel was set to “duplicate”, showing the same image on the external and internal monitor (scaled down). Scaling was set to 125% to make text more legible on the high-DPI external monitor.

The new-and-stable configuration is an ASUS VE228 1920 x 1080 monitor, connected with an Amazon Basics HDMI cable, and running at its native resolution. The Windows 10 Display control panel is set to “show only on 2”, effectively disabling the internal display. Scaling is set to 100%. Everything else is the same as before – same graphics driver version, etc.

Now I can do some A/B testing, and try to determine which of these differences is causing problems. Could it be something as stupid as a bad HDMI cable? Does the computer’s firmware not correctly handle scaling when the external monitor is a different resolution than the internal one? Could the 2560 x 1440 monitor actually cause crashes somehow, due to a bug in its firmware (I think HDMI is bidirectional) or electrical faults?

Read 5 comments and join the conversation 

My new computer continues to experience unexplained freezes and reboots, and I’m running out of ideas for fixing it. A few weeks ago I wrote about crashes in the Intel integrated graphics driver, and the symptoms have since changed, but problems continue. I’m now looking at either

1. reinstalling Windows and all my applications, which would be a huge undertaking and might not fix anything
2. replacing the whole computer and reinstalling all my applications, which would also be a huge undertaking
3. resigning to accept a computer that can’t go more than a few days without crashing.

My previous Windows 7 computer easily ran for weeks without trouble, so this kind of instability is disappointing.

The new computer is a Windows 10 laptop (HP Elitebook x360 G2 1030). I use it with the lid closed, connected to an external monitor, keyboard, and mouse. I suspect this is the root cause of my problems. While this setup should work and does work most of the time, running a laptop with the lid closed doesn’t seem 100% robust. The computer sometimes seems to lose communication with the external monitor, or gets confused because the primary (internal) monitor is off. I see occasional event log entries like “A pointer device has no information about the monitor it is attached to”, window manager crashes, and other graphics related errors. And all of these problems happen while I’m away from the computer, when the external monitor is in power-save mode, but the computer is not asleep. When I return to the computer later, I sometimes find that it has frozen or unexpectedly rebooted.

I should emphasize that the computer rarely sleeps and never hibernates, so I don’t believe this is a sleep-related problem.

 
History

The first problem was crashes in the Intel integrated graphics driver igdkmd64.sys while I was away from the computer. Nearly every day, I’d return to the computer in the morning to find that it had crashed and rebooted sometime since its last use. Here’s what’s happened since then:

June 15 – I forced an update to the latest Intel graphics driver version 26.20.100.6890. This required completely uninstalling the HP-provided graphics driver first. Since then, I have not seen any more crashes in igdkmd64.sys.

June 16 – The computer was still running since the day before, but the Start menu and Cortana did not work. I restarted the computer and Start/Cortana began working normally again.

June 17 – The computer fan was blowing 100%, but both the external and internal screens were dark. I could tell that Windows was still running, because I heard the Windows disconnection sound effect when I unplugged USB devices, but nothing I did would get an image to appear on any screen. I forced a reboot with the power button. The event log showed several prior errors about the embedded controller (EC) not responding. In light of this, I disabled the 3rd-party program Notebook Fan Control. After rebooting, the computer hung on the boot screen with the HP logo, and did not proceed into Windows. After rebooting a second time, all seemed normal.

June 18 – The computer was still running since the day before, but once again the Start menu did not work. I used the task manager to terminate WindowsShellExperienceHost.exe, which then automatically restarted and restored normal Start menu functionality. Afterwards I fully uninstalled Notebook Fan Control. Following a tip related to broken Start menus, I also turned off the Windows option for Settings -> Accounts -> Sign in Options -> Use my sign-in info to automatically finish setting up my device and reopen my apps after an update or restart.

June 19 – All OK. The computer was still running since the day before, with no problems.

June 20 – All OK.

June 21 – All OK.

June 22-23 – Didn’t use the computer.

June 24 – All OK.

June 25 – The computer was still running since the day before, but again the Start menu did not work. I terminated WindowsShellExperienceHost.exe to get the Start menu working again.

June 26 – All OK.

June 27 – Didn’t use the computer.

June 28 – The computer fan was blowing 100%, but both the external and internal screens were dark. Nothing I did would get an image to appear on any screen. I had to hold the power switch to reboot the computer. The event log showed lots of errors in the preceding hours, including multiple desktop window manager crashes, and an application hang error from Microsoft.Photos.exe every 15 minutes stretching on for hours, all during a time when I wasn’t using the computer.

June 29 – The computer fan was blowing 100%, but both the external and internal screens were dark. Nothing I did would get an image to appear on any screen. I had to hold the power switch to reboot the computer. Nothing interesting was found in the Windows event log.

I don’t understand what’s going on here, but it’s a hot mess.

Read 16 comments and join the conversation 

Do you miss the iconic sounds of mechanical click-clacking from original Apple II floppy drives? Does the familiar rattling of a boot floppy bring a smile to your face? Today I’m introducing a new product called Noisy Disk. This board uses a mechanical relay to create authentic-sounding disk head movements for the BMOW Floppy Emu disk emulator. Sure it’s useless, but it’s useless fun.

The Noisy Disk board attaches inline with your existing Floppy Emu cable, using the provided 6-inch extension cable. When Floppy Emu is configured to emulate a 5.25 inch Apple II floppy drive, the Noisy Disk onboard relay snaps open and shut whenever the emulated disk steps from one track to the next. It creates a symphony of disk noise that will bring back memories of 1979.

Noisy Disk is compatible with Apple II family computers while using Floppy Emu in 5.25 inch emulation mode. Nothing will be harmed if Noisy Disk is used with other computers or emulation modes, but you’ll hear strange clacking noises that don’t match the disk activity. It’s recommended to use Noisy Disk in 5.25 inch emulation mode only.

The product includes the Noisy Disk board with 2 x 10 pin rectangular input and output connectors, and a 6-inch extension cable for connecting to your Floppy Emu board.

Noisy Disk is available now at the BMOW Store.

Read 6 comments and join the conversation 

I’m forecasting an extended out-of-stock period this summer for the Wombat ADB-USB Keybord/Mouse Converter. One of the Wombat’s parts is currently out of stock everywhere, and the manufacturer is advertising 16 weeks lead time for delivery of more parts. There are still enough Wombats on hand to cover a few more weeks of typical sales volume, but then it will probably be October before more are available. If you’ve been considering getting a Wombat, you should order it now or be prepared to wait until autumn.

The Wombat is a bidirectional ADB-to-USB and USB-to-ADB converter for keyboards and mice.

• Connect modern USB keyboards and mice to a classic ADB-based Macintosh, Apple IIgs, or NeXT
• Connect legacy ADB input hardware to a USB-based computer running Windows, OSX, or Linux

No special software or drivers are needed – just plug it in and go. Now you can finally use a modern optical mouse with your vintage Macintosh, or amuse your coworkers with a retro ADB keyboard on your work machine. ADB-USB Wombat is an indispensable tool for Apple collectors and enthusiasts.

Read 2 comments and join the conversation